Hi,
There is probably problems with the priority of the interrupts. If you
use the normal library (that you modifiy for using timer 2 and 3) for
the motor it will not work. Use the "advance one timer", it should be
better. You can also try to remove the "shadow" option of all iterrups
that are not for the camera, should also works.
If not send the all code.
Regards
Michael Bonani
Le 30.11.2011 15:13, Duarte Dias a écrit :
Hi,
I have an e-puck program that captures images (timers 4,5), moves the
robot (timers 2,3), periodically generates odometry measurments (timer
1), process captured image and sends a small buffer with results (48
bytes) to bluetooth after the capture is done (I do not wait for the
transmission to be complete). The odometry measurments are processed
while the capture is being done (while we wait for the end of the
capture).
All works well speratly (just capture, only movement with odometry,
etc), but when I plug all of this together in the main loop, the
e-puck starts to crash and the funxtions generating silly data. Since
the functions do not generate silly data when capture is off, I assume
that the problem is when I plug the capture, and not in the functions.
Does the camera has some problems with capture, while doing more stuff
in between the capture, ex. moving (other timer events), performing
operations (while wating for the end of the capture), etc.?
If not the camera, what could be the problem?
Regards,
Duarte Dias
_______________________________________________
E-puck-user mailing list
[email protected]
https://mail.gna.org/listinfo/e-puck-user
_______________________________________________
E-puck-user mailing list
[email protected]
https://mail.gna.org/listinfo/e-puck-user
