Setting up the hardware interface for the MDrive I/O only represents half of the battle. Before it can function it must be configured in software using the “S” command.

This Application Note: covers the basic functions and capabilities of the MDrive communicating over Ethernet.

This Application Note covers a small program for a motion sequence. It is developed in a fashion that no I/O is used. The only thing needed to be connected is power and communications. There is no difference in function between Liberty* MDrive and MDrive motion products.

This Application Note covers the basic structure and programming conventions of the MCode language, The differences between Liberty* MCode and MDrive MCode is primarily found in the syntax of the I/O instructions.

This tutorial covers the basic variables and instructions impacting motion. The motion commands are common between the Liberty* MDrive products and the MDrive/MForce products. The only variation is with the value scaling for encoder based move commands, as the Liberty* MDrive closed loop products have a 1000 line (4000 counts) encoder, where MDrive motion products with an encoder have a 512-line (2048 count) encoder.

This Application Note covers the connection of the I/O points for Liberty* MDrive and MDrive Plus, MDrive Linear Actuator and MForce products. The I/O differs in connection and application between the two product families in that the MDrive Plus I/O is non-isolated and programmable as an input or an output. The Liberty* MDrive I/O is fixed function is input or output.

When choosing a power supply for a stepper motor driver, there are performance and sizing issues that must be addressed. An undersized power supply can lead to poor performance and even possible damage to the stepper motor driver, which can be both times consuming and expensive. However, bipolar chopping stepper motor drivers are quite efficient and may not require as large a supply as you might suspect.

Electrical noise is the source of many issues in motion systems. Following best practices with wiring and cabling can prevent or eliminate the impact of electrical noise on a motion system.

This tutorial covers the basics of connecting and using the I/O points on your IMS motion control products.

This basic tutorial covers the following concepts as they apply to the Liberty* MDrive and MDrive/MForce.

1. Sinking I/O
2. Sourcing I/O
3. I/O cabling best practices

Though the design of the I/O points differ between Liberty* MDrive and MDrive MForce products, these basic concepts are relevant to both product families.

This tutorial will guide you through the initial process of connecting to your IMS serial product using the Motion Control Programmer (MCP) application, part of the Software Suite.

This process is the same for any product communicating over a serial datalink, or using MCode over Ethernet.