ricknegg
Lifetime Supporting Member
Hello,
I am in the commissioning stage of a retrofit using RSLogix 20.01.00, Control Logix 1756-L72, and Kinetix 6500 drives. We had this configuration working in our lab (wired properly), but having some issues with the shop installation. We are in the process of verifying the shop installation wiring, and this could very well be an issue.
The problem I am running into is that although the drives show no faults/errors - I am unable to turn the drive on with the MSO direct command and get the following error:16#0052 - Drive is not in the correct state to allow the current operation. The MSF, MASR, and MAFR will all execute with no errors.
I noticed that bit "0" of axisname.CIPAxisState is set to "1" [Unconnected], but have been unable find documentation as to what causes this bit to get set. Any ideas??
This is my first motion project so please excuse me if I am overlooking something very simple.
Thank You,
Rick
P.S. – I think this is a great site! I just upgraded my membership to lifetime, but it hasn’t taken effect yet apparently.
I am in the commissioning stage of a retrofit using RSLogix 20.01.00, Control Logix 1756-L72, and Kinetix 6500 drives. We had this configuration working in our lab (wired properly), but having some issues with the shop installation. We are in the process of verifying the shop installation wiring, and this could very well be an issue.
The problem I am running into is that although the drives show no faults/errors - I am unable to turn the drive on with the MSO direct command and get the following error:16#0052 - Drive is not in the correct state to allow the current operation. The MSF, MASR, and MAFR will all execute with no errors.
I noticed that bit "0" of axisname.CIPAxisState is set to "1" [Unconnected], but have been unable find documentation as to what causes this bit to get set. Any ideas??
This is my first motion project so please excuse me if I am overlooking something very simple.
Thank You,
Rick
P.S. – I think this is a great site! I just upgraded my membership to lifetime, but it hasn’t taken effect yet apparently.