APIs, concepts, guides, and more
rsiconfig

XML configuration and ENI generation utility.

🔹 What is XML configuration?

The RMP Motion Controller is software-based and does not have flash memory, nor are its configurations stored in a file.

XML Configurations give your application the most flexibility for configuring the RMP as needed at runtime. This is better than using hard-coded values in your RapidCode application. Is also useful when upgrading to a new RMP version.

🔹 Why use the rsiconfig.exe utility?

Using the rsiconfig.exe utility will help guarantee that your RMP is correctly configured and ready to run before your RapidCode application starts. It allows you to keep hard-coded constants out of your source code. It also can help you generate XML configurations for your current settings, get the serial number, check the RMP license and generate ENI files.

🔹 Usage

Image

🔹 Use Cases

Generate XML Configurations

After you have your network started and all Axis settings configured via RapidSetup, use ‘rsiconfig.exe -generate’ to generate XML files:

Image

This creates the file ‘**settings.xml**’ which is used to apply configurations to a freshly-started RMP in the future. It also creates the two Axis XML files (Axis 0.xml and Axis 1.xml).

Initialize and restore from XML files

To initialize a system and restore from XML files, use rsiconfig settings.xml

Image

Here you can see that the expected node types and Axis settings were configured. rsiconfig.exe will return non-zero if there are unexpected nodes or an error restoring configurations.

Generate ENI file

To generate the ENI file, EtherCAT.xml, use rsiconfig -eni on Windows. In Linux, you must specify the CPU affinity (for the RMP) and the Primary NIC (for RMP network) sudo rsiconfig -eni --cpu-affinity 3 --primary-nic enp5s0

This will first attempt to discover EtherCAT nodes on the network. If it finds any, it will (using the ESI files) generate the ENI file, EtherCAT.xml. If you have added any ESI files to the ESI directory, you may need to delete the ESICache.xml file to force a refresh.