We’re experiencing problems controlling servos using the KOP servo and Labview. We connected the servo (PWM6, black wire facing out, jumper pin inserted) to the digital sidecar (DIO Slot 4) and ran the “Servo Example”. The project deploys and the cRIO communicates with our laptop, but moving the servo control indicator does nothing.
All three power status lights are on. When we short the associated 6V power enable pins on the DSC using a screw driver, the servo jumps a single step and then goes dead again. The shorting jumper we used is definitely electrically sound, and is shorting the pins.
Is this a fried DSC? What debugging should we do, and what steps should we take to ensure not to fry another?
Thanks for the quick response. Does this apply to Labview “Example” VI’s that are directly deployed and run from the programming computer? If so, then the question was far less silly than the answer will be.
As a side note, the reason we went back tot he “Servo Example” VI is because we could not control the servo to work in a full robot code deply.
The driver station must be enabled for any code of any kind to produce any actuation. Actuation includes servos, solenoids, and speed controllers (PWM or CAN).
You can run the driver station from the developer account using the Start menu. If there is not a shortcut in the Start menu, the exe is in the program files directory in a folder called FRC Driver Station. Make your own shortcut and put it onto the desktop or wherever you like.