Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

raspberry pi 4 - pure thermal 2 - chromium #47

Open
rvegele opened this issue Nov 11, 2022 · 1 comment
Open

raspberry pi 4 - pure thermal 2 - chromium #47

rvegele opened this issue Nov 11, 2022 · 1 comment

Comments

@rvegele
Copy link

rvegele commented Nov 11, 2022

Hi,

I'm trying to get this module to work with a Raspberry pi 4. Being quite new I was wondering if I should be able to work just through a USB connection or do I need to connect it differently? I'm running Bullseye.

When usb is plugged in I just get a lot of noise from the 'shutter'(?) of the lepton module. Not what I get when using it on my PC.
Looking at chrome://device-log the device seems to be connected / disconnected every few seconds apart.

Thanks.

@rvegele rvegele changed the title raspberry pi 4 raspberry pi 4 - pure thermal 2 - chromium Nov 15, 2022
@rvegele
Copy link
Author

rvegele commented Nov 15, 2022

I've managed to get my hands on the PT2 in order to do a firmware update. I believe I'm getting somewhere. But I'm faced with the following issue:

https://groups.google.com/g/flir-lepton/c/88PrZI1-A8I

Is there a way somewhere in the firmware to adjust the value range I'm receiving as my image is also very "black". With minor gray-ish areas in the hot spots.

From one of the posts
"I looked through this really quickly and I didn't see any normalization done in there. When you're dealing with thermal data, you have to contrast-extend the images if you want to see something. On a Lepton 2.5/3.5 your 16-bit values represent temperatures in centikelvin (kelvin * 100), so for example, a pixel that is at 29.5C would be a value of 30265, which is right around 0.45 * 65535, the values you're seeing. The whole scene is going to be around this temperature, so you have to scale these values up so that you have contrast in the range you're interested in seeing. You can do this based on max/min in the scene, or you can set a fixed max and min, and make those values be 0.0 and 1.0, then offset and scale the data into that range."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant