Overview:
When SimpleConnect is utilized and devices are added to the “My Network” screen, the selections and assignments are saved to a binary file. The file is called “Mapping.bin” and is stored in SRAM on the YRC1000. The file itself isn’t readable or editable outside of the robot pendant, but the importance of that file is key to the operation of SimpleConnect. Hence, we’re going to explain the contents, the importance, and the portability between various systems.
Contents:
The “Mapping.bin” file is utilized at launch of the SimpleConnect app to properly display all of the various settings that were made when previously setting-up your devices on the network. The file contains the following details:
- Robot controller IP-address and MAC address
- SimpleConnect module type(s) (FEN20-****)
- IP-Address for each module(s)
- MAC Address for each module
- The program (ARGEE) pushed into each module
- The input and output location of where that device/module resides in the robot IO along with instance #’s and RPI rates
- If there is a “secondary” device attached to the “primary” device, the “Mapping.bin” also contains the MAC address and IP-Address of the secondary device
- Assignments of that device to robots within the system
Extracting & Loading “Mapping.bin” File:
The “Mapping.bin” file resides in the “User Defined File” area under both the “SAVE” and “LOAD” option of “Ex Memory”. It can be loaded and saved as would any other robot file.
IMPORTANT: A newly loaded file will not take effect until the YRC’s power is cycled. Don’t open SimpleConnect after having just loaded a “Mapping.bin” file as you will not see the contents of the recently loaded file!
CMOS handing of “Mapping.bin”:
When a CMOS backup of SimpleConnect system is created or loaded, the “Mapping.bin” file and other SRAM files are part of that backup/load. That means you don’t need to manually save or restore the file when performing a CMOS save or restore.
Portability of “Mapping.bin” file:
Each “Mapping.bin” file is very unique and tied to the hardware of the system where it originated. MAC addresses are unique to each piece of hardware, this fact makes it impossible to move a “Mapping.bin” from one system to another. Even if a Turck module or a YCP01 board is replaced since the last backup of the “Mapping.bin”, that will cause the file to be unusable.
For details on replacing a YCP01 board see the following article: