Quote:
|
Originally Posted by Alan Anderson
Pwm outputs 13-16 are special. They're generated by the user processor and can be updated more often than the 26.2 ms communication burst. But you need to call the Generate_PWMs() function in order for them to work. The line with that function call is present in Kevin's camera code, but it has been commented out.
They also have a reputation of being prone to "twitchiness" if you have lots of interrupts going, or if you call the Generate_PWMs() function repeatedly with too short a delay.
|
I've had a few quesions on this and Putdata, maybe you can clear them up
How long does Generate_PWMs() take to return? Can I call it from within a timer ISR?
If I call Putdata more than once every 26.6ms, will it update the PWMs faster?
How long does it take to return?
And finally, the master processor seems to allow the user processor
more than 26.6ms?!??
This makes no sense, but our code is definitely taking longer than 26.6ms (because of serial communications bogging us down) and yet I do not get the BRLOD?!??
Thanks for any light you can shed on this!
__________________
CMUCam not working? Tracks sporadically? Try this instead:
http://www.falconir.com!
PM me for more information if you are interested (it's open source!).
Want the FIRST Email blasts? See here:
http://www.chiefdelphi.com/forums/sh...ad.php?t=50809
"The harder the conflict, the more glorious the triumph. What we obtain too cheaply, we esteem too lightly; it is dearness only that gives everything its value."
-- Thomas Paine
If it's falling apart it's a mechanical problem. If it's spewing smoke it's a electrical problem.
If it's rampaging around destroying things it's a programming problem.
"All technology is run on 'Magic Smoke' contained within the device. As everyone knows, whenever the magic smoke is released, the device ceases to function."
-- Anonymous
I currently speak: English, some German, Verilog, x86 and 8051 Assembler, C, C++, VB, VB.NET, ASP, PHP, HTML, UNIX and SQL 