Forgot your password?
No account? Register one!
March 27, 2011
University of Portland
Product SEN-10061 |
about 3 years ago
We were successfully able to receive a picture!! What we did was read the whole picture at once, normal baud rate, and read all the data in one read call. The trick was that we were not receiving 0x11 or 0x13 due to XON/XOFF flow control. This was fixed with the following command:
stty -F /dev/ttyS2 -ixon. Shout out to cmooney who helped us out a lot!
Could anyone send me a picture they took with this camera at compression rate 36 and size 160*120. We are trying to check the header information that we are receiving to see what we are missing. Please send any pictures to email@example.com. It would be greatly appreciated!
Hi, I am having similar issues to those on here; I am not able to open images read from the camera. I have confirmed that the values that I am receiving from the camera are correctly saved into the .jpg file using a hex editor. I am worried that we are not receiving complete pictures from the camera. After sending each command we have to sleep for three seconds before we are able to successfully read from the camera. We get correct responses after sending commands and such, but it is still odd that we have to do this. Another issue that we found is that the size returned from the JPEG file size command does not match the actual amount of bytes read from the camera’s memory (usually 20-40 bytes less). Here are some common errors that we have received when trying to open the file:
Corrupt JPEG data: 5 extraneous bytes before marker 0xc0
Bogus marker length
Bogus DQT index 9
We have followed some instructions from cmooney in that we are now reading the picture in one big chunk and have attempted slower baud rates. Any help in this matter would be greatly appreciated!
No public wish lists :(