Before you begin The following prerequisite steps are required before performing a firmware upgrade the MCode Operating System on your LMD Programmable Motion Control or Ethernet TCP/IP product. Download and install the LMD Software Suite. Download and extract the MCode OS Firmware file. From the LMD Software Suite main screen install, then open, the Motion […]
Before you begin This upgrade procedure is for Liberty* MDrive models with a Kinetis K64 processor using the 2.4.x.x firmware. The following prerequisite steps are required before performing a firmware upgrade on your Liberty* MDrive Ethernet TCP/IP product. Download and install the Liberty* MDrive Software Suite. Download and extract the Ethernet Application Firmware file. From
Upgrading the Liberty MDrive Ethernet TCP/IP Application Firmware Read More »
Before the Liberty* MDrive can be installed into a network, the TCP/IP parameters, namely the IP address and the subnet mask must be changed to match the network settings. Before you begin you should have completed the steps found in the following tutorial: Setting up your Ethernet adapter for MDrive Ethernet TCP/IP products Step-by-step For purposes of
Liberty* MDrive Ethernet products ship from the factory with the TCP/IP parameters defaulted to the following settings: IP Address: 192.168.33.1 Subnet mask: 255.255.0.0 These need to be changed to meet the configuration of the network that these will be installed into. This procedure covers setting up the adapter card in your PC to initially connect
Setting Up Your Ethernet Adapter for MDrive Ethernet TCP/IP Products Read More »
USB to SPI converter The MD-CC30x-001 USB to SPI converter is a plug-n-play device, which uses a Virtual COM Port (VCP). Drivers will typically automatically install on an Internet connected PC, notebook or Windows tablet when the device is connected to a free USB port. If automatic installation fails, or if you need to download
The below example sets typical motion profile commands a system would configure1, enabling the motor power2 and the four different move types3supported in Profile Position Mode using SDOs with Node ID 41h. 1Typical motion profile commands could be set each time on power up from host or set using a configuration file and stored to
Os – Output setup 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. When applied to outputs 1 – 2 the output setup command is utilized thus: Os=<output #>, <function>,
Is – Input setup command 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. Digital inputs Usage When applied to the digital inputs 1 – 4 the
Global or Local variables Like All MDrive variables, the I/O point configuration can be declared two ways: Globally Locally Global: Global I/O configurations, are declared outside the main body of the program. These are more typical and are used when you want the I/O point to have the same function at all times. Local: Local
PNP Input In this example case we will assume that we need a PNP Sensor connected to an input to trigger events within an MDrive program. Thus we will configure I/O point 1 as a General Input which will activate when HIGH. The command:
1 | S1=0,1,1 |
will set I/O1 to function as we desire: S1=: setup
