|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#7
|
|||||
|
|||||
|
Re: Synchronizing with 26.2 ms communication
First, we perform the PID calculations based on a timer every 26 ms instead of the 20 ms we had been using.
Second, and more important, we switched from trying to control the wheel velocity and went to a position-based PID scheme instead. Now the control parameter is the desired robot location (and orientation) instead of the desired speed (and turn rate). The PID constants take care of making the velocity what it needs to be in order to get to the right location without overshooting. For manual driving, the joystick input constantly sets the desired position in front or in back of the current location, and when that point is set farther away, the robot travels faster. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Need Help With Maplab C programming on serial communication | loveheb3 | Programming | 0 | 04-06-2007 21:24 |
| Labview and communication with peripheral device help | jaijaidin | LabView and Data Acquisition | 3 | 26-01-2007 19:17 |
| Serial Communication Problems with LabVIEW FRC Toolkit | Jon236 | LabView and Data Acquisition | 1 | 28-12-2006 11:57 |
| Methods of communication???? | aviv | Chairman's Award | 3 | 18-02-2006 20:10 |
| organized way of communication with FIRST? | archiver | 2001 | 0 | 24-06-2002 04:20 |