|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#10
|
|||||
|
|||||
|
Re: Making Debugging Easier
Our software read one of the otherwise unused joystick wheel inputs (yes, we used the old reliable black joysticks for the driver this year) and used its value to select among a set of User_Byte outputs to be viewed by a dashboard program. With the wheel at one end of its travel, it sent (the low 16 bits of) the three encoder wheel values. At the other end, it sent arm potentiometer feedback. Intermediate positions gave internal state information for the arm and drivebase control routines.
A separate "debug mode" switch selected between all of that and the regular "drive mode" dashboard data, which was basically monitoring the autonomous mode selection, the vision tetra detection, and a few feedback bits such as air compressor status. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Making your robot drive easier | ufa_mike | Control System | 32 | 28-04-2004 21:35 |
| Wiring Diagram for making a Joystick | Nick Fury | Control System | 0 | 10-02-2004 23:10 |
| Team Communication - Making it easier | Balbinot | Website Design/Showcase | 3 | 10-02-2004 13:50 |
| What's easier? Last year or this year? | archiver | 2001 | 2 | 23-06-2002 23:33 |
| FIRST, BattleBots & Marketing of Robotics | Mike Soukup | General Forum | 12 | 12-12-2001 18:46 |