No clue- Sounds like you just changing values without understanding what they supposed to be doing. This software you talk about and the arbitrary values. (They recommend 25Mhz) Did you provide that? I suspect they did not include a crystal in the LEPTON to keep the size down and embedded devices usually have access to some kind of constant clock any way. python raspberry-pi opencv c-plus-plus dropbox i2c image-processing octave spi thermal-imaging flir raspberry-pi-zero thermal-camera. Now we know Raspbian is not very great at generating consistent clock rates consistently so you may be experiencing problems with this - The same way may other FLIR'ers are experiencing. Front-end application which downloads thermal images from DropBox and carries out multiple image processing and manipulation techniques to produce an output for the user. I assume you got it hooked up to SPI correctly but one of the problems seems to be the Input Clock rate. So looking around really I noticed the protocol used on the Lepton is VoSPI (Video over SPI) Frankly never heard of that before but its plausible because the frame size is 80 x 60, which is not a crazy amount of data with some kind of AGC applied format which is selectable (Did you select the correct one?)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |