Oak Axis Fault In Invert

[bizarrecustoms]

I am currently retrofitting a Cincinnati Arrow1000. The old Acramatic 2100 system utilized Vickers (Kollmorgen) BDS4 drives for the axis motors. I have gotten my flying lead wired in. I have working position tracking, drive enable signal, and jog function. My problem is the the BDS4 output fault line I need to use for the Oak fault in (XAxisDriveOK_M in realtime I/O display) is inverted from what the Oak wants. Oak wants to see it pull up for fault and the BDS4 pulls down for fault. I've looked around the parameter definitions in the manual but don't seem to be finding what I need. In Is there a parameter to invert this field?

I have it disconnected right now to make the oak happy while I continue other parts of the install. Worse case I believe I can just pick up a transistor and invert the signal. But, would obviously prefer to just switch a parameter setting.

[cncsnw]

You can invert it easily enough in the PLC program.

In the fault-checking section in MainStage, look for a block of lines something like this:

Code: Select all

IF !Axis1DriveALM_M THEN (Axis1DriveOk_M)
IF !Axis2DriveALM_M THEN (Axis2DriveOk_M)
IF !Axis3DriveALM_M THEN (Axis3DriveOk_M)
IF !Axis4DriveALM_M THEN (Axis4DriveOk_M)
IF !Axis5DriveALM_M THEN (Axis5DriveOk_M)
IF !Axis6DriveALM_M THEN (Axis6DriveOk_M)
IF !Axis7DriveALM_M THEN (Axis7DriveOk_M)
IF !Axis8DriveALM_M THEN (Axis8DriveOk_M)

And change it to read like this:

Code: Select all

IF Axis1DriveALM_M THEN (Axis1DriveOk_M)
IF Axis2DriveALM_M THEN (Axis2DriveOk_M)
IF Axis3DriveALM_M THEN (Axis3DriveOk_M)
IF Axis4DriveALM_M THEN (Axis4DriveOk_M)
IF Axis5DriveALM_M THEN (Axis5DriveOk_M)
IF Axis6DriveALM_M THEN (Axis6DriveOk_M)
IF Axis7DriveALM_M THEN (Axis7DriveOk_M)
IF Axis8DriveALM_M THEN (Axis8DriveOk_M)

This assumes, of course, that your drives actively pull the line low in case of fault (rather than a PNP output that just pulls it high when all is well).

[bizarrecustoms]

.

[bizarrecustoms]

You can invert it easily enough in the PLC program.

In the fault-checking section in MainStage, look for a block of lines something like this:

Code: Select all

IF !Axis1DriveALM_M THEN (Axis1DriveOk_M)
IF !Axis2DriveALM_M THEN (Axis2DriveOk_M)
IF !Axis3DriveALM_M THEN (Axis3DriveOk_M)
IF !Axis4DriveALM_M THEN (Axis4DriveOk_M)
IF !Axis5DriveALM_M THEN (Axis5DriveOk_M)
IF !Axis6DriveALM_M THEN (Axis6DriveOk_M)
IF !Axis7DriveALM_M THEN (Axis7DriveOk_M)
IF !Axis8DriveALM_M THEN (Axis8DriveOk_M)

And change it to read like this:

Code: Select all

IF Axis1DriveALM_M THEN (Axis1DriveOk_M)
IF Axis2DriveALM_M THEN (Axis2DriveOk_M)
IF Axis3DriveALM_M THEN (Axis3DriveOk_M)
IF Axis4DriveALM_M THEN (Axis4DriveOk_M)
IF Axis5DriveALM_M THEN (Axis5DriveOk_M)
IF Axis6DriveALM_M THEN (Axis6DriveOk_M)
IF Axis7DriveALM_M THEN (Axis7DriveOk_M)
IF Axis8DriveALM_M THEN (Axis8DriveOk_M)

This assumes, of course, that your drives actively pull the line low in case of fault (rather than a PNP output that just pulls it high when all is well).

I did this in Notepad++ (configured per TSB) and after compiling and relaunching CNC12 I get a time out and application close upon "Initializing MPU" when starting the program. I even reverted the changes back and recompiled and same. I assume I missed something stupid. I will have to play around and figure out what I messed up so I can confirm.

[cncsnw]

I do not think there is anything you can do in the PLC program that will cause a "Timeout: MPU not responding" condition on startup.

Check your Windows firewall settings. There needs to be an exception to allow c:\cncm\cncm.exe through the firewall.

Also verify your ethernet hardware connection with "ping 10.168.41.2".

[bizarrecustoms]

I do not think there is anything you can do in the PLC program that will cause a "Timeout: MPU not responding" condition on startup.

Check your Windows firewall settings. There needs to be an exception to allow c:\cncm\cncm.exe through the firewall.

Also verify your ethernet hardware connection with "ping 10.168.41.2".

Yea i managed to dig up an old post where someone had a similar issue:
https://centroidcncforum.com/viewtopic. ... mpu#p28788

Checked and sure enough my firewalls had turned back on. Turned them back off and it fired right up. Was also successful on getting a proper inverted fault signal through the PLC programming changes suggested and therefore an enable signal to the drive.
Thanks for all the help.

[tblough]

Microsoft will continue to turn the firewall back on at random times. As CNCSNW mentioned you need to add an exception to your firewall to allow CNCM.exe access.

[cnckeith]

solving com errors info is here.
https://centroidcncforum.com/viewtopic.php?f=61&t=1451