|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||||
|
|||||
|
_mode flag summary??
I searched, but I did not find...
Can someone definitively describe the various "_mode" flags in the code, such as autonomous_mode and competition_mode (now called disabled_mode this year, to better reflect the polarity of the bit!) and any similar flags? See below: Code:
/* *----------------------------------------------------------------------------------------------------- *---------- Aliases for User Modes ------------------------------------------------------------------ *----------------------------------------------------------------------------------------------------- * These bits tell you what mode your robot is currently in. * 1 = in <X> mode; 0 = not in <X> mode */ #define user_display_mode rxdata.rc_mode_byte.mode.user_display #define autonomous_mode rxdata.rc_mode_byte.mode.autonomous #define disabled_mode rxdata.rc_mode_byte.mode.disabled I am particularly interested in how they are controlled by the Match Computer. I have a dongle, but that doesn't tell me under what circumstances which flag is in what state. This year is especially interesting. For example: 1. What happens when the human player steps off the switch pad? Do any flags indicate this? 2. How do I make a timer that measures match time, including the time the human player is off the pad? Last year I simply had a counter in Default_Code(), but that ran all the time, even before the match started. 3. There is a dead time between autonomous and manual mode during each match for the officials to award tetras, etc. How can my software know when that is the state? 4. How can I code a "software reset", so that all the "time counters" can be reset without having to press the "reset" button on the RC? This is especially important for the second run of practice matches. If someone could describe an example match and how it is reflected in the _mode bits, that would be really helpful. Thanks all! |
|
#2
|
|||
|
|||
|
Re: _mode flag summary??
Quote:
2. Use an onboard timer that starts couting when auto mode starts. Increment one variable every timer click (or every 10 timer clicks, depending on the resolution). Then, increment one other variable only when the robot is in auto mode or user mode. Take the difference to know how much time the robot was in disabled mode. 3. Look for when the mode flag changes from auto to disabled, then call whatever. 4. map a button on the joystick to a function that resets your timer variables, stops the hardware timer, then retarts the process. Hope this helps. |
|
#3
|
|||||
|
|||||
|
Re: _mode flag summary??
Last year we reset our autonomous whenever the robot was disabled. The drivers didn't have to remember to reset for the second practice match.
Last year the actual sequence at the SBPLI Regional was:
|
|
#4
|
|||
|
|||
|
Re: _mode flag summary??
I has occured to me that with the code running, and the Camera not controlled thru the RC outputs, the camera can be operating and searching for a target before the match starts. Is this right?
This would allow a robot to scan for the vision tetras before things start. Control of the camera is all through the serial port. |
|
#5
|
|||
|
|||
|
Re: _mode flag summary??
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Exec. summary question | lilszek24 | Chairman's Award | 2 | 22-01-2005 12:15 |
| [OCCRA]: Rules Question: Can the flag move the arrow? | wbhsAndy | OCCRA Q&A | 1 | 27-10-2004 11:01 |
| Regarding Executive Summary Form | Petey | Chairman's Award | 3 | 22-02-2004 16:49 |
| Yet another time limit question (about exec summary) | Caroline | Chairman's Award | 1 | 06-02-2002 17:14 |
| Competition Detail Summary | kmcclary | Off-Season Events | 3 | 15-11-2001 11:30 |