![]() No, you're forgetting the overhead of start and stop bits. run-length encoding) so that you have less to actually send. You could probably help by compressing the data (eg. ![]() Almost certainly it is spending a lot of its time in the interrupt routines doing the actual drawing. However - and this is probably your problem - the TVout library uses interrupts heavily to draw things to the screen using exact timing as required by the video hardware. But if you send a byte per pixel that is 849 mS. I'm using the tvOut library to render the pixels.Ĭan you clarify if you are sending a byte per pixel or a bit per pixel?Īssuming a bit per pixel, it would take 12228/115200 seconds (106 mS) to send that many. Right now I'm just sending on/off data per pixel, not worrying about coordinates (just to test for speed) and it takes about 3 seconds to send a char for each pixel to the Arduino, but by my estimates at 115200 bps, it should take less than a second. It is a 128x96 black and white image, so 12,228 pixels. I'm doing a project that sends real time video data to the Arduino.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |