Slots 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.
The Target InoDrive’s resources go to the Local Slot, which is the default location for resources (like motors, instructions, inputs, etc) to be stored for InoDrive’s use. More slots are required if you have multiple InoDrive Modules to send resources to, which would then require a slot for each module.
| The InoDrive unit which you are writing a program for is called the Target Module . The Slots Resource lists the Target’s slot in a pre-defined default, named Local. Click the Slots item under the Resources list to view all of the defined Slots. In this example the only one we have is Local. Again, Local refers to our Target module which will be the InoDrive that we send the program to primarily. |
![]() |
Creating a Slot
| 1. Click the Create New button to open the dialog. Enter a valid name and specify which InoDrive module you’d like to function as a Remote Slot. Generally we recommend using Serial Number, but if you have Named your module, or plan on using static IP addressing in your network, these options are also available. |
![]() |
| 2. Ensure your Slot is enabled by clicking the toggle here or use the Network Block Set Slot to specifically enable the module later on in your program. Click Create to create the Slot. |
![]() |
| 3. With multiple slots configured, take care to be sure that you select the right module each time |
![]() |
| 4. Here you can see how the same block is used twice, executing the same function for both slots. |
![]() |
