Hello,
I'm looking to standardize the setup on all of the robots my company commissions. I have written a setup guide to help people commission their robots but it's long and takes a bit of time to complete.
Does anyone know if there is a file that stores the System/Config settings and the I/O config settings that I could keep a copy of on our network? Then when we receive a new robot we could just load the files instead of punching in all of the settings at the teach pendant.
Thanks!
Robot Standarization
-
Dpreston -
September 19, 2017 at 5:42 PM -
Thread is marked as Resolved.
-
-
The system config is stored in SYSVARS.SV, but this file is unique to each robot and should not be copied, as it also contains all of the servo parameters which will be different for each mechanical unit.
DIOCFGSV.IO stores all of the i/o data and can be copied, if the i/o hardware is the same.
-
That's what I guessed. I wonder if there is a "custo" that can be written and loaded at control start that would setup the system config... Any experience with custos?
-
You can create a TP or Karel program that modifies the system variables you desire and run it on all new robots.
-
I like the idea of creating the Karel program. This way you can modify the variables if you ever want to change what the config is. Then run it. Any idea what system variable[s] are used to store the config data?
-
Here is an example of a few that I use. Look at the system variables starting with SHELL_CFG to see what else is available. This code is for TP.
: $SHELL_CFG.$CONT_ONLY=1 ;
: $SHELL_CFG.$USE_ABORT=1 ;
: $SHELL_CFG.$CSTOPI_ALL=1 ;Sent from my SM-G930V using Tapatalk