V5 motor configuration upon reconnect

[jpearman]

@nenik

But if your program starts w/o the motor (and your code still blindly blasts the commands to a port), then the motor, upon reconnection, starts working OK, though your initial attempted configuration is lost.
We have observed this under PROS, not sure if the behavior gets any different under VexCode.

It’s a feature (bug really) of PROS. vexos keeps the configuration for flags like reverse if the motor is not present when user code starts or is unplugged, however, PROS doesn’t send it though on startup if it thinks there is no motor, VEXcode however does. The things we keep backup values for are

brake mode
encoderUnits 
gearset      
reversed     
currentLimit 
voltageLimit 

One reason for keeping these values is safety, I didn’t want a motor running at full power when user code had asked for low current and the motor was disconnected and then reconnected.