Introduction to InoWorx

The InoDrive and InoWorx ecosystem allows you to utilize multiple InoDrive modules to create multiple axes of motion control. A typical example would contain a single InoDrive unit that will contain the User’s Program and this program can connect and have access to the drive control and I/O of its network connected InoDrive units.

Typical Example of a Multiple InoDrive System

Target	This is the InoDrive unit that will contain the User’s Program . This program can utilize the drive control and I/O of both its Local unit as well as the other connected InoDrive units on its network
Slot	These are all the InoDrive units on the network including the Target unit. The Target unit’s drive and I/O resources are identified as Local in the User’s Program. The other InoDrive units can be identified to the Target unit by IP address or relative location or hops from the Target units A and/or B network ports.
Axis	This is defined as motion producing mechanism attached to the InoDrive unit. At a minimum an Axis is a DC motor with Hall Sensor or Encoder feedback. Each Axis has a definition selectable within InoWorx specific to the motor/mechanical parameters and characteristics. Each Axis requires a Slot, but not all Slots require an Axis .

About This Manual

Using the Programming IDE