The purpose of this issue is to document the requirements for adding an override for some values of MotorOutputSim that reads from NetworkTables instead of following the simulation. The use case for this would be simulating non-ideal dynamics and intentional disturbances. For example, "simulating" a current spike from a game piece contacting a motor-driven element would involve using an override for the MotorValues statorCurrent field.
Each override should have two entries in NetworkTables: a boolean indicating whether the override should be used (because users should be able to choose when the simulated values are used and the overriden values), and a double for the actual value. The override should also be created with a unique name used as a prefix.
The purpose of this issue is to document the requirements for adding an override for some values of MotorOutputSim that reads from NetworkTables instead of following the simulation. The use case for this would be simulating non-ideal dynamics and intentional disturbances. For example, "simulating" a current spike from a game piece contacting a motor-driven element would involve using an override for the MotorValues statorCurrent field.
Each override should have two entries in NetworkTables: a boolean indicating whether the override should be used (because users should be able to choose when the simulated values are used and the overriden values), and a double for the actual value. The override should also be created with a unique name used as a prefix.