# tCAM-Mini Clone

## Hardware Information

### WEMOS TTGO ESP32 board



https://daniel-strohbach.de/esp32-oled-battery-thing

### FLIR Lepton Breakout Board v1.4


https://www.pureengineering.com/projects/lepton


https://github.com/groupgets/LeptonModule/tree/master/hardware/LeptionBreakout
https://github.com/groupgets/LeptonModule/blob/master/hardware/LeptionBreakout/LeptonAdaptorSch.PDF

### FLIR Lepton Breakout Board v2.0

https://groupgets.com/campaigns/645-flir-lepton-breakout-v2-0-with-lepton-3-5/show


https://media.digikey.com/pdf/Data%20Sheets/FLIR%20PDFs/250-0577-00_DS_1-2021.pdf

### tCam-Mini

https://de.aliexpress.com/item/1005003575421251.html

https://github.com/danjulio/lepton/tree/master/ESP32

https://hackaday.io/project/159615-lepton-35-thermal-imaging-camera/log/188980-tcam-mini-and-desktop-app-pushed-to-github


https://github.com/danjulio/tCam/blob/main/tCam-Mini/hardware/documentation/rev_4/tcam_mini_schem.pdf

### FLIR Lepton 2 Module

# Compatibility

## Hardware Compatibility

- SPI and I2C pins OK
- Beakout power supply is OK
- Breakout is missing VSYNC
- Breakout is missing LEP_RESET transistor and connection (on-board RC network only)


## Software Compatibility Lepton v2 vs. v3

### VSYNC Output

https://www.reddit.com/r/AskElectronics/comments/89w7db/anyone_work_with_the_flir_lepton_3_camera/

Q:

I'm trying to get some thermal images, using the FLIR lepton 3 camera.

I am having trouble with SPI synchronization. I am not using the
I2C/CCI interface, so it should be just defaults.

basically, at the same time each bootup, i lose synch.
Scope timings are good (150Hz per 60 segments).

What happens is, a new "discard" frame starts, however it
starts early (< 82 16-bit words later). That screws up the synch
because all the info i read suggests reading the exact packet
length (82 16 bit words). Also, the data comes in eventually
shifted by 9 bits! i mean wtf.

A:

This is a known problem with the Lepton 3. Your best bet to
guarantee synchronization every time is to use the Vsync
output (I believe it's on GPIO3, check the data sheet to set
up output) to synch up your VOSPI frames, else the packet engine
is going to bork up very frequently. Best part about using
this technique is you don't need to dick around with
discard packets. You get a pulse, clock in the frame, wait for a pulse.

In a nutshell, VoSPI doesn't work as advertised.
It can be a real headache, especially with the Lepton 3.

### VoSPI Protocol Differences And Similarities

https://cdn.sparkfun.com/assets/f/6/3/4/c/Lepton_Engineering_Datasheet_Rev200.pdf


### LePi library

https://github.com/cosmac/LePi