If experiencing difficulty with serial communications with MDrive Motion Control unit, it is often helpful to perform a loop back test with the communications cable to better understand where in the communication link the problem exists. A non-functional personal computer RS-232 port, improperly installed USB drivers, improperly configured IMS Terminal, defective IMS communication cable or an MDrive malfunction all show the same symptom: no communication with the MDrive indexer.

A good way to test the cable up to the MDrive is to perform a loop back test on the MD-CC200-000 or MD-CC400-000 ribbon cable connector. Disconnect the IDC cable from the MDrive communication port and add jumpers as shown in the drawing below. If characters now echo to the terminal screen, there is a communication problem with the MDrive. If typed characters are still not visible, there is a problem with the IMS adapter cable, IMS Terminal configuration, or personal computer communication port.

Party Mode Exception

If the loop back test results indicate a functioning communication link, there is still a chance that the MDrive is communicating properly, but configured in the party mode and you don't know the device name. The following command sequence will retrieve the MDrive's name. There maybe no terminal feedback while typing the characters. Type: [CTRL + J]*PR[space]DN[CTRL + J]. The MDrive should return its name in quotes. Further communication then can be carried out by properly addressing the unit by name. The following command sequence will place the MDrive in the factory default state: [CTRL + J]*FD[CTRL + J]. All parameters will be replaced with the factory defaults and all programs erased. There will be no terminal feedback while typing the reset characters and the IMS copyright sign on message will be the result.