Log Files

We are implementing a plant wide password system with USB keys, and we have two major goals.

1. Keep people from making changes that they have no business making.
2. Track who, when, and what every time a change is made above the operator level.

1. Pretty well taken care of just by the raw implementation of the password system.
2. Partially taken care of with the password log, however the limited number of lines is a problem.

To address the limited number of lines, i have a few questions.
2.1. Can i specifically disable certain items that would normally be recorded in the log to save lines? I don't really need to know every time the user is forced to Full or Quick menus. Can the reported items be customized in any way.
2.2. Can i extend the number of rows that can be reported and maintained without overwrite? If i could bump this up, we could justify devoting a little extra memory to this.
2.3. Is there a method with Karel to run an AutoBackup on command, or better yet to specifically pull the ERRPWD.ls file? We are looking into ways via PLC to accomplish or augment whatever limits we have with the robot.

Any suggestions or recommendations are welcome!

Update on item 2.1, using the Error Table, i can mute certain items and keep them from taking up log space.

I used the Error Severity Table (Under Menu -> Setup). In it, you can choose any error code, then you can change its severity (upward only) and you can change what is done with the error code. All the details are in the HandlingTool Manual in Section 5.10, with the facility codes details in Section A.2.2 (Error Codes and Recovery).