I have been using an MC2 as a control module for an excavator attachment. It was working fine until I added tried to add some CAN communication to send pressure sensor pressure values and joystick inputs to a Data Acquisition System. There were 9 signals. I attempted to load the file on, and at the end of the load it through an error saying something like "no return handshake from Master Module." I tried to reconnect to the system repeatedly but it would not establish a connection. I attempted to use the attachment and the MC2 was not sending out any signals.
After turning the power supply on and off and trying to reconnect unsuccessfully, I tried to read the lights. The following sequence repeated:
-2 long yellow followed by 3 short yellow. While not exact (extra long yellow), does this mean "Waiting for Restart"?
-4 Short Red followed by 1 short yellow: Internal Error
-18 short yellow - is this just the "there is something abnormal going on"?
I read this thread: http://forum.iqan.se/topics/98-mc2-cause-of-internal-errorose/ which seems to describe a similar issue. It seems like the advice is to short the ID pins and start in "safe" mode.
If the "waiting to restart" error keeps appearing even after cutting power and repowering, does that mean I need to try and start the program in "safe" mode and reload the program?
Anyone have a nice clean way to short the ID pins? Should I just put 2 clips on the end of a single wire? And what happens once I successfully reload the program? Should I cut power and then remove the shorting wire so it does not restart in "safe" mode?
It looks like there was an error in the software: I specified it try to broadcast the CAN data out over the wrong bus. The CAN data was also unconnected. In this case the information was not vital to the operation, but I am thinking this would be enough to throw an internal error and cause problems. Can someone confirm or deny that a module shut down could be due to a CAN comm error due to incorrectly spec'd bus OR unconnected CAN Comm cable?
Thank you, Graham
Customer support service by UserEcho