Motion Control and Motor Drives

cancel
Showing results for 
Search instead for 
Did you mean: 

UMI interlock issue

Solved!
Go to solution

I just had a setup moved from one location to another and I can't make it work anymore.

 

The setup is a PCI-7330 controller, a UMI-7772, a P7000 series driver on axis 1 (currently not connected) and a custom driver on axis 2.

 

The issue seems to be with the intelock since this LED on the UMI-7772 doesn't turn off so the axis DISABLE LED stays ON.

 

When I test the controller it passes the test, when I initialize it  I receive an OK message and the ''shutdown'' box is unchecked in my controller settings. I tried some connect/disconnect of the controller cable on both controller and UMI sides but the Interlock LED stays ON. I also tried with my emergency switch in both position and disconnecting it from the global stop connector.

 

Any idea or suggestion on what might be the issue?

 

Thanks,

 

Ben

0 Kudos
Message 1 of 3
(3,619 Views)
Solution
Accepted by topic author ben64

Ben,

 

the interlock LED should indicate that the host bus voltage (+5 V) is not present. Typically that means, that the PC is not turned on. In your case this seems to indicate a hardware issue with either the 7330, the 7772 or the cable.

Please check for bent pins and if you have connected the cable correctly. In fact the pins of the high densitiy motion cables are quite robust, but with a decent amount of force it's possible to plug the cable onto the connector the other way round.

If this is not the reason for your problem, you should try to track the +5 V signal from the board's connector to the end of the cable. If you can't find the source of the issue, please try to switch individual components of the system, but of course this is only possible, if you have spare components of the same type.

 

If nothing works, you should contact your local NI branch. Maybe they can loan you a board, a cable and a UMI, so you could find out the broken component.

 

Regards,

Jochen Klier

National Instruments

0 Kudos
Message 2 of 3
(3,609 Views)

Thanks Jochen,

 

Effectively there was a problem with the cable, using a spare one solved the issue.

 

Ben

0 Kudos
Message 3 of 3
(3,602 Views)