About ctrlXnovo

ctrlX OS - 2.4.0, ctrlX Motion - 2.4.3, ctrlX PLC - 2.4.0, ctrlX PLC Engineering - WRK-V-0204.1, CXA_MotionInterface - 2.4.0.0, MotionInterfaceUser - 2.4.0.0 I think this condition is a result of making many program changes in different states.  We are commissioning a machine and the error is not consistent.  A "Reset Cold" on the PLC always seems to bring it back.   But my original question was about where to find documentation.  As I commission the machine and run into errors I am wondering if my commands are wrong.  The suggestion to Retrigger the OpMode is helpful but I'm not sure what this does exactly or why it is needed.  The only mention of it I can find is in the library documentation where it simply says "Restart the same OpMode again".  Is there any description of why to use the RetriggerOpMode command, or what state that it is intended to recover from?  I was hoping there was a description of how the drives interact with the kinematic.  In some cases, one drive of the three coordinated axes will enable but not the others.  I'm not sure why.  But again, it could be because we are making many program downloads and online changes.   ... View more

I appreciate the information and I had found these too.  But I was looking for something directly related to the interface commands.  To explain the specifics of my problem, if I have an EStop on my system, it puts the drives in STO.  I have not figured out a way to re-attach them to the kinematic after this.  The drives are stuck in AB after this event.  No command of the drive, for example to ModeAH has an effect.  The kinematic commands also have no effect, moving from Mode_Coord_AB to _AH or _Standby, etc.   My thought is that when an STO event occurs on the axes that are joined to the kinematic, that I need to command the kinematic in a certain way to follow the actual drive state.  And then, I'm suspecting, there is a sequence to recover from the STO state once the safety controller releases the drive from STO.  But I have not found a way to do this yet.  Right now, the only sure way is to Cold Stop the PLC which is similar to a power cycle.  Then the kinematic works as expected to coordinated the axes correctly. ... View more

This morning I logged in to the ctrlX CORE, set the diagnostics to "Developer View" and tried the registration again...and this time it worked, first time I tried!  I have been trying for weeks.  I was able to add the device and activate it.  One difference is that I figured out how to delete old instances of devices in my online account and removed those.  I did that yesterday and the registration did not work immediately.  But maybe the system updated overnight and this is why it worked this morning?  I don't know, but I'm happy it is working now. ... View more

The suggestions above did not work.  Today I am back on site and able to connect to the CORE directly.  There are no error or warning messages in the main diagnostic log.  Is there some other diagnostic log that you are interested in?  The behavior I see is that when I enter in the Company ID code that I copy from my account on the IXON website, the code simply disappears and the interface returns to looking like this: I have verified that I have internet access on the CORE.  I'm not sure what else to check...   ... View more