|
|
|
 As my boy Macklemore once said, "The greats weren't great because at birth they could paint, the greats were great because they paint a lot". - Andrew_L [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| As my boy Macklemore once said, "The greats weren't great because at birth they could paint, the greats were great because they paint a lot". - Andrew_L [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||||
|
|||||
|
Synchronizing with 26.2 ms communication
I'm having difficulty trying to tune a velocity PID loop, and I've come to the conclusion that part of my problem is that the PWM outputs aren't changing at a predictable time relative to the PID sample time. They're not even changing at the same rate.
Is there a way to detect when the User and Master CPUs have exchanged their information? Or does EasyC even use the same "every 26.2 ms" scheme that the IFI default code has? So much is hidden behind the scenes and I don't know how to peek behind the curtain. EasyC is easy for simple stuff, but I'm apparently fighting it when I want to try more advanced coding. I can't believe that I have to jump through so many hoops to do things that aren't predefined, and I have to think I'm just failing to see the "right" way. |
| 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