Password Protection Setup

Notes regarding the transfer of one robot's password configuration to another.

1. Apparently, the source robot and the target robot need to have the same software version and revision. All other information seems to be transferred with no issue, but the password data itself gets mangled.

2. Building off of this, before getting the above information from Fanuc, i did some testing and discovered that if you activate passwords on one machine, log in, take a backup, activate passwords on a second robot, log in, and load the password config file, it WILL change the Install level password right out from under you. In my case, with a corrupted ascii abomination of my password.

3. For recovery, there are a few options, depending on what you have available.
- The built in recovery method, calling fanuc with a key code from the password option.
- Restore an image backup from before the passwords were enabled.
- Use the passunlocker karel tool on this forum to break in and create a new Install user.

Note on 3.2: Passwords can disable the ability to cycle power at the pendant, but they can not stop you from cycling power with the power switch.
Note on 3.2: With the corrupted password at least, immediately after attempting to log in as the Install user with the NON corrupted password, it seemed to affect my permissions and allow me to cycle power at the pendant. I am not sure how long this vulnerability lasts after an attempted log in, or if it was caused by using the non corrupted version of a corrupted password. Further testing required.
Note on 3.2: Passwords DO protect both Controlled Start and Maintenance Start, but do NOT affect the Boot Menu, so restoring images is always an option.
Note on 3.3: Must have the program, or password permission to install the program, must have the Karel option, and must have the system variable for Karel enabled. It will then display the corrupted version of the password (not something likely to be typable with the built in keyboard), and the Admin soft key will create a new Install user and log you in. You can then disable passwords.

Have now tested with V8.30P/40 to V8.30P/40 and have the same result. Passwords still corrupted in transfer, presumably in the loading process. Still a few posible tests to try, with Controlled Start, to see if that affects the file.

Quote from cobenson

If you have the original core software, you can load a blank password file from it. Do a search here, there are a ton of information on how to do it.

This doesn't really apply to the current situation. I have set up 30 custom users on one robot. I am able to easily load identical password level configurations with the password.xml file, however my problem is with transferring the syspass.sv file from the fully setup robot to a new one that still needs to be set up. All of the names, levels, and time out settings transfer perfectly, but the passwords themselves become corrupted. Meaning, the password i set a specific user up under on the first machine no longer works on the second machine. I am not trying to clear the passwords, i have plenty of ways to do that, i need to transfer a fully setup configuration to a new robot, and right now i am not having any luck. Fanuc suggested it might be because of the differing software revision levels, so i updated the new robot to match the setup robot, but the transfer still corrupted the passwords.

I appreciate it! Currently, the setup robot is v8.30p/40 and the test robot was v8.30p/11. Transfer did not work. Seemed to corrupt the passwords. Everything else transferred fine. User names, number of users, default time outs, and user levels all transferred correctly, but the original passwords no longer worked.

Updated target robot to match v8.30p/40, and still have the same issue. Currently waiting on response from Fanuc.