Need to look into "/usr/sbin/eclicmd.pl" more - looks like it could be useful.
If you want to find a copy of the .pkg (used for software upgrades and such) of a box you already have, check out "/rollback/usr/local/amc/app/updates/".
To capture a standard snapshot you can run this from the CLI...
/usr/bin/perl /usr/bin/capture_snap_shot.pl -a -c -f /tmp/snapshot.tgz
The robot in the i2000 is powering up and moving. It's getting caught up in a few places and I'm getting a low voltage warning too. Gotta figure out if it's the cable chain, the tracks (bottom bar was bent up a bit), or the robotics module that has all of the motor controllers in it.
In the interest of being a good netcitizen I've removed some of my i2000 and i6000 related posts. Baring any issues I'll probably repost them on/before 2019-01-14.
If you're using a Quantum, Dell, or ADIC Scalar product you should check to see if the password of the GUI's 'service' account is static. If it is then there is a pretty trivial way to get into the system using the vendor's maintenance account. The one system I have access to, an i2000, has a login of service:10101100.
If you're using a Quantum, Dell, or ADIC Scalar product you need to make sure the 'service port' isn't remotely accessible. If it is then there is a pretty trivial way to get into the system as 'root'. The port is explicitly listed in the manual as not for "normal" use.
tl;dr If you aren't plugging in stuff you shouldn't (per manual) then the risk isn't that bad.
Checked all of the fuses and they're all good - Looking more and more like the LMD is bad.
Looks like the buttons are both fine - Once I got it apart and tested it with a multi meter it became apparent that the robotics enable button is just momentary - it's a different kind of switch from the power switch. Based on the LEDs on the LMD (Library Motor Driver) it looks like that might be the problem. I'm going to check the rest of the fuses first though.