Classmate questions

[Ryutso]

Our classmate has a couple things wrong with it that are more annoyances than actual problems, but they're annoying enough to want to fix:

1. Our classmate automatically logs into the Driver account on start up from a full shutdown. What should we change to stop that from happening?

2. When we log out of (not "Switch Users") the developer account, it goes to a black screen and doesn't respond.



Also, there's nothing in the rules about this, but we were hoping to upgrade the classmates RAM to 2GB before the championship so we can get faster code deployment and quicker boot times. Has anyone done this successfully or is this not legal?

[Alan Anderson]

Our classmate has a couple things wrong with it that are more annoyances than actual problems, but they're annoying enough to want to fix:

1. Our classmate automatically logs into the Driver account on start up from a full shutdown. What should we change to stop that from happening?

Change nothing. That is the desired behavior. :rolleyes:

If you want to log into the Developer account on startup, hold down the Shift key to force the system to present the login screen instead of automatically logging in as Driver.

2. When we log out of (not "Switch Users") the developer account, it goes to a black screen and doesn't respond.

That is a problem. You should probably restore the Classmate to its original state using the provided "RESTORATION KEY" flash drive (and then apply the latest LabVIEW and Driver Station updates). If you've been using the Classmate for software development, make sure you have saved all your work on an external disk or flash drive first!

Also, there's nothing in the rules about this, but we were hoping to upgrade the classmates RAM to 2GB before the championship so we can get faster code deployment and quicker boot times. Has anyone done this successfully or is this not legal?

There is something in the rules about it. <R60> prohibits any modification of the Classmate PC, with the exception of part A: "User programmable “dashboard” code in the Classmate PC may be customized." and parts I: "Fasteners may be used to attach the device to the OPERATOR CONSOLE or ROBOT." and J: "Labeling may be applied to indicate device purpose, connectivity, functional performance, etc."

[joek]

Change nothing. That is the desired behavior. :rolleyes:

If you want to log into the Developer account on startup, hold down the Shift key to force the system to present the login screen instead of automatically logging in as Driver.



That is a problem. You should probably restore the Classmate to its original state using the provided "RESTORATION KEY" flash drive (and then apply the latest LabVIEW and Driver Station updates). If you've been using the Classmate for software development, make sure you have saved all your work on an external disk or flash drive first!



There is something in the rules about it. <R60> prohibits any modification of the Classmate PC, with the exception of part A: "User programmable “dashboard” code in the Classmate PC may be customized." and parts I: "Fasteners may be used to attach the device to the OPERATOR CONSOLE or ROBOT." and J: "Labeling may be applied to indicate device purpose, connectivity, functional performance, etc."
technically, it's not a modification, the ram could be considered a separate device, therefore, you are not modifying the class mate, but the RAM

[Vikesrock]

technically, it's not a modification, the ram could be considered a separate device, therefore, you are not modifying the class mate, but the RAM

Will the Classmate run without RAM? Don't cause stress for your team and your inspectors by doing this.

Q&A it if you think there is any chance it would be ruled legal.