In Roboguide HandlingPRO v8 revM, I created a new virtual robot from a backup from a plant I am working with. The backup is said to be 2 weeks old on a system that hasn't changed in months.
It is a unique system with specific DCS and IO names.
However, the configs don't match reality. (I have pictures I took of EtherNet/IP configs, DI/DO configs, and the full I/O pages.)
1. My pictures of the actual robot from a few weeks ago show DI configured to 3072, using racks 89, slot 1 AND 2, and rack 36 slot 6 (in the 2000 range)
1b. The Roboguide robot from AoA backup shows only the default 512 inputs, but it does have a rack 89 slot 1 and 2 still configured within that range.
2. Similar for outputs, I observed and have pics of the outputs configured with 3072 outs, and some IO ranges configured above 512 that are now blown away.
3. EtherNet/IP (rack 89) config has changed drastically: This was a Scanner (master) robot with a Turck IO rack as 'slave' on connection 1, and a secondary Fanuc robot as slave on connection 2, hence the IO configs using rack 89 slot 1 and 2.
3b. The EtherNet/IP config is now reduced to one configured connection set as adapter (slave). It is enabled, but it is set to the default settings (4 bytes), and the scanner IP field is unused/unset.
These are the major differences I've spotted, but DCS, among other things, are screwed because expected IO in the ranges above 512 are non-existent in the Roboguide robot.
Q: Is this a known issue that can happen by user error? Roboguide didn't throw any errors at creation time, but am I supposed to manually force it to use a certain virtual robot controller version or something? I'm just grasping at straws and would like to know if there is a way to get this backup into Roboguide correctly. The system is currently in production, so I know for a fact (photo evidence), that the actual robot does have its IO configured properly and is working without issues.
Thanks