-
Notifications
You must be signed in to change notification settings - Fork 192
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
mlx90641 drivers work, mlx90640 drivers don't... bad temperature conversion? #89
Comments
Hi, I tried the driver on several random MLX90640 devices and it is working. Vdd = 3.305 You mentioned that you started off of the MLX90641 deriver working. Is it possible that you somehow mixed-up the two drivers? Best regards |
Thank you very much for your time, I could focus on libraries since my reading is correct and I realized the T0 computation screws calculation when it starts using kTa and Kv arrays. In fact those arrays doesn't look right at all. I will look better into their calculation, maybe my C dialect makes something wrong, but I have a big doubt: according to the excel file with example values, kTa and kV should be both 0.something, so float, but in the params struct their type is actually int8_t. If I force those data to zero in the T0 calculation the reading is very good, probably with little errors here and there. Any idea why they are int in the params struct instead of float, as the excel example suggest they should be? |
HI, indeed the xls file is not valid anymore - since the update for reducing the RAM footprint. Best regards |
Hello. I'm trying to implement the mlx90640 on a CC2538 texas instrument and a Contiki os.
I successfully implemented the mlx90641 getting an output like this:
But when i switched on the mlx90640 (of course with new main libraries, while i2c library is almost the same) i'm getting some strange results:
eeprom and frame looks like reasonable values, but after the To conversion only some pixel are getting 22-23 degree that is correct reading, all the other are strongly out of range. I also tried "lookup table method" but i'm getting same results.
I have several sensors and several boards, so i already tried to change batteries, board or sensors, but I got same mistakes in same pixels.
CC2538 has only 32kB ram but "size" command gives:
text data bss dec hex filename
81868 1970 22452 106290 19f32 host.elf
So it looks like ok.
Any suggestions?
The text was updated successfully, but these errors were encountered: