MDrive/MForce troubleshooting guide

Technical product questions?
Please contact Applications Support by submitting a support request.
  • Communications
  • Connections
  • Programming

 

Symptom   Possible problem and solution

Cannot communicate with MDrive when using 64-bit Windows Operating System.

  

The current version of communications drivers does not support any 64-bit Windows operating system. At the current time only 32-bit versions of the Windows operating systems will work with the MD-CC40x or MD-CC30x Communications Convertors.

If you are using a Windows 64-bit operating system a workaround for this issue is available: Windows 64-bit Systems.

Unit does not communicate using IMS Terminal.

Detailed instructions:

> Loop back test procedure

   Be sure that your unit is powered and the communication cable is connected securely on both ends.

The MDrive’s default baud rate is 9600 baud. Be sure that the IMS Terminal baud rate is set to 9600 baud.

Check to be sure that in the lower right hand corner of the terminal window it shows Connected. If it shows disconnected, then double-click the word Disconnected or click on the appropriate phone icon. See Loop Back Test Procedure.

It appears that communications is intermittent and the unit is not responding appropriately.   The MD-CC200-000 cable has a five-volt DC input, which should be used if intermittent or no communication is encountered. Use a 5 VDC regulated power supply with at least 50 mA current. The power jack is for a 2.5 mm diameter plug center polarized connector.

Be sure to check the baud rate set in IMS terminal, and be sure it is the same as the MDrive’s baud rate setting.
No communication once PY=1 is set.   To start communicating to the MDrive, it is necessary to issue an initial Ctrl J to activate communication. Once activated, each subsequent immediate command does not require an initial Ctrl J.

The terminal window returns unusual characters when entering an immediate command.   Be sure that IMS terminal is for the proper device. To set the device select Edit in IMS interface. Next select Preferences, then select the Comm setting tab. Once there select the device MDrive.

The unit may still be in upgrade mode. If so, the upgrade must be completed or unusual characters will appear.

 

Symptom   Possible problem and solution
An input was made but not recognized during program execution.   Be sure connections are secure and wired correctly.

Check to see that the appropriate settings are made for S1–S4 and S9–S12 commands based on the I/0 type needed.

Check to see if the correct active state parameter is set. If S1=0,1 with the input not being recognized, then change the active state to 0 (S1=0,0). 

 
The motor does not have enough torque; it can be stopped with ease.   Be sure to check your motor run current setting (PR RC)–the default is 25%. At stand still, the holding torque (PR HC) has a default setting of 5%. If there is not enough torque, increase the percentage for more torque.

 
Multiple MDrives connected to the same power supply and one unit keeps stalling or has a fault.   The power supply being used may not have enough voltage or current available for multiple drivers. Be sure that the power supply has enough current for each MDrive.  
     

 

Symptom   Possible problem and solution
The program does not seem to function as intended.   To troubleshoot the program, you can single-step through the program by using EX <addr/label>, <mode>. Select Mode 2 which will allow you to see program execution by single-stepping through the program.

Trace mode can be used to watch program execution.

Use print statements to help troubleshoot the program. Print statements can be used to report information as the program is running.  

When the program is being loaded question marks are returned.   Before downloading your program, be sure to clear memory space using the FD (factory default) command. Then type S for saving factory default.

If a question mark is seen after a command, then there is a problem with that command's syntax.  
The unit is setup in party mode. When attempts are made to communicate nothing seems to happen.   Be sure to use Ctrl J, then type device name, and then the command; example: ^JAMR 100000^J. If the device name is forgotten, then use the asterisk (*) symbol; example: ^J*PR VR^J.  
I cannot fully download my program. It downloads halfway and stops.   Make sure that long comments are not being used. The limit is 62 characters including spacing and the command per line. If longer comments are needed, save your file with a .txt extension. Use the file with the .mxt for downloading the program with minimal comments.  
The MDrive runs OK in open loop; in closed the motor keeps stalling.   Be sure the move profile adjusted to encoder counts when EE=1. The stall factor (SF) may be to low. Increase to SF=20. This will help eliminate nuisance trips. Depending on the application stall factor, adjustment may be needed based on acceptable position tolerances.

 
Motor does not complete move.   Check mechanical system to be sure there is no mechanical binding or increased friction.

If the acceleration rate or the run speed is too high, values should be adjusted lower. The motor stalling due to the motion profile being used means not enough torque is available. Increasing the run current may eliminate stalling.   
The program contained the startup label (SU). After downloading the program the power was turned off then on. The program did not start running.    The program was not saved after downloading. Download the program again, then type S in the terminal window to save it. Turn the power off then on, and the program will execute.