|
|
|
 While searching is not as glamorous, I'm certain you could find a lot of good resources related to this topic. - Katie_UPS [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| While searching is not as glamorous, I'm certain you could find a lot of good resources related to this topic. - Katie_UPS [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#2
23-01-2008, 10:40
|
||||
|
||||
|
Re: Synchronizing with 26.2 ms communication
The easiest way to fix this is use a timer to execute the PID every 26ms. This is what I've done for PIDs with mechanisms and steering. I was having trouble with tuning also without the timer.
We are also planning to post a new version of easyC with a logging feature in the terminal window so you can format PrintToScreen in CSV format and use excel to graph data. |
| 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 |
Threaded Mode