Application Notes

Learn how SEM products may be applied in your motion system.

Home > Resources > Application Notes

Select Topic
Getting started tutorials

The output setup (Os) command is used to set the functionality of the outputs. The parameters define the output point to be configured, the desired functionality, and the active control state high or low.

The input setup (Is) command is used to set the functionality of all inputs, digital and analog. The parameters define the input point to be configured, the desired functionality, and the active response state high or low.

This Application Note covers the topic of writing MDrive MCode programs using the programmable I/O points both as a single I/O point, or as a bank of 4 I/O points as a group.

A sourcing device provides the power or a positive potential to an I/O point. Sourcing devices ‘push’ the current through the load. Other terms used to describe sourcing devices include PNP, Open Emitter, Normally Low, and IEC Positive Logic.
Note that sourcing outputs are only available on Motion Control devices equipped with Plus2 expanded features.

For this part of the tutorial we will use the same hardware configuration examples as was used in the Connecting Power and I/O tutorial to show the configuration of I/O points to various I/O uses.

A sinking device provides a path for the current to ground. Terms used to describe sinking devices include NPN, Open Collector, Normally High, and IEC Negative Logic.
For this part of the tutorial, we will use the same hardware configuration examples as was used in the Connecting Power and I/O tutorial to show the configuration of I/O points to various I/O uses.

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 Lexium MDrive and MDrive motion products.

This Application Note covers the basic structure and programming conventions of the MCode language, The differences between Lexium 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 Lexium MDrive products and the MDrive/MForce products. The only variation is with the value scaling for encoder based move commands, as the Lexium 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.

Previous
Next

When it comes to your form, fit and function requirements, don’t settle. Get precisely what you need working with us. We know motion.

Contact us with any questions about how we can help you with your motion application or for assistance with your SEM products.

Browse our resource section and find the most useful tools and documents for all our products.