S1100 - S1199

we are working hard to document every message and error if any message is not described or the description is incomplete, contact us for more detailed information s1111 motion segment transfer failed the system was not able to send the movement data to the controller the controller could not be reached because the communication was lost check that the usb or ethernet cable is firmly inserted on both sides check the indicators on the controller to see if the controller is still powered and active when using usb, be mindful that certain devices (vfds, motor drivers) emit large amounts of emi and can interfere with the signal always route the cable as far away from these devices as possible s1112 laf runcycle failed if this error occurs when using our software directly, please contact us with a detailed description and a support archive s1114 motion segment transfer failed the system was not able to send the movement data to the controller the controller could not be reached because the communication was lost check that the usb or ethernet cable is firmly inserted on both sides check the indicators on the controller to see if the controller is still powered and active when using usb, be mindful that certain devices (vfds, motor drivers) emit large amounts of emi and can interfere with the signal always route the cable as far away from these devices as possible s1115 laf runcycle failed if this error occurs when using our software directly, please contact us with a detailed description and a support archive s1117 motion segment transfer failed the system was not able to send the movement data to the controller the controller could not be reached because the communication was lost check that the usb or ethernet cable is firmly inserted on both sides check the indicators on the controller to see if the controller is still powered and active when using usb, be mindful that certain devices (vfds, motor drivers) emit large amounts of emi and can interfere with the signal always route the cable as far away from these devices as possible s1118 laf runcycle failed if this error occurs when using our software directly, please contact us with a detailed description and a support archive s1120 motion segment transfer failed the system was not able to send the movement data to the controller the controller could not be reached because the communication was lost check that the usb or ethernet cable is firmly inserted on both sides check the indicators on the controller to see if the controller is still powered and active when using usb, be mindful that certain devices (vfds, motor drivers) emit large amounts of emi and can interfere with the signal always route the cable as far away from these devices as possible s1122 motion segment transfer failed the system was not able to send the movement data to the controller the controller could not be reached because the communication was lost check that the usb or ethernet cable is firmly inserted on both sides check the indicators on the controller to see if the controller is still powered and active when using usb, be mindful that certain devices (vfds, motor drivers) emit large amounts of emi and can interfere with the signal always route the cable as far away from these devices as possible s1135 fifo underrun edingcnc controllers use a buffer on the controller to cache movement data in advance this buffer must never run empty, or the machine will come to an immediate standstill this error occurs when no further movement data is presented to the controller while there was still more data expected the most likely reason is that the computer was interrupted for a while the most common culprit is automatic windows updates, which we recommend turning off however, other applications on the host computer may result in similar behavior ensure that no other applications are running, and turn off unneeded background processes s1139 communication with gpio card lost the controller was unable to communicate with the external io device for the rly8 io and other modbus rtu devices, it is important to check the wiring these devices may benefit from using shielded cables ideally, avoid running the cables too close to devices that emit large amounts of emi, like vfds, solenoids, or motor drivers s1140 set cpu position failed the system was not able to set the position of the controller the controller could not be reached because the communication was lost check that the usb or ethernet cable is firmly inserted on both sides check the indicators on the controller to see if the controller is still powered and active when using usb, be mindful that certain devices (vfds, motor drivers) emit large amounts of emi and can interfere with the signal always route the cable as far away from these devices as possible s1141 forward kinematic failure the operation could not be completed because the kinematics could not resolve a cartesian position for this point s1142 timeout the motion task did not update in time if this error occurs when using our software directly, please contact us with a detailed description and a support archive s1143 no cpu communication possible if this error occurs when using our software directly, please contact us with a detailed description and a support archive s1144 cpu enable motion failed, e stop still active the controller could not start its movements because the e stop is (still) active resolve the e stop first and retry s1145 cpu enable motion failed the controller could not start its movements if this error occurs when using our software directly, please contact us with a detailed description and a support archive s1161 communication with cpu lost the controller could not be reached because the communication was lost check that the usb or ethernet cable is firmly inserted on both sides check the indicators on the controller to see if the controller is still powered and active when using usb, be mindful that certain devices (vfds, motor drivers) emit large amounts of emi and can interfere with the signal always route the cable as far away from these devices as possible s1164 home switch guard triggered, please reset the home switch was triggered unexpectedly this guard is activated by either the docid\ pz1uvdx3jtizhbciowrvi interpreter command or the docid\ oq4cfrz kl6qi1rwto2ls setting