FIRST Robotics Competition Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Proper use of example VI’s

Today I needed to simply read encoder counts so I jumped into the Motor with Encoder Example VI. As instructed in the VI I changed the IP to our cRIO IP address, selected the proper DIO and PWM ports saved the VI and ran the example. The compile and target process looked ok. The VI ran but absolutely nothing happened; no motor, no encoder on a tested platform. It smelled of Watchdog or FRC Framework/Driver Station. What is the proper way to use these examples?

tx –still scratchin.

0 Kudos
Message 1 of 3
(3,666 Views)

Did you enable the driver station? You must enable to get any motion from the system. It's a safety thing.

0 Kudos
Message 2 of 3
(2,696 Views)

I find the Robot Signal Light very helpful for indicating if the robot is enabled or not.  From the Control System Introduction document:

Robot Signal Light – this amber light allows teams to troubleshoot their robot while on the field. There are 5 states:


  • Solid ON = Autonomous Enabled
  • Solid ON, but blinks OFF every 1.5s = Teleoperated Enabled
  • Slow Blink (900ms on / 900ms off) = System Disabled; caused by system watchdog, user watchdog, or Driver's Station set to disabled
  • Fast-Slow Blink (200ms on / 900ms off) - Low battery (<12 Volts) or no user code and system disabled either by system watchdog, user watchdog, or Driver's Station set to disabled
  • Fast Blink (200ms on / 200ms off) - System error: No driver's station communication, bad cRIO Image, bad team ID, extensive communication errors.

geoff

Geoff Schmit

Team 3061

Naperville North High School

--
Geoff Schmit
Huskie Robotics, FIRST Team 3061 Lead Mentor
http://team3061.org/
@team3061
0 Kudos
Message 3 of 3
(2,696 Views)