Do I need to change anything on the build if I want to use the MLX90640 IR camera? I plan to use the pcbway board as I will be using 12v from the car.

Due to mounting restrictions, I need to use a 120 FOV camera, but finding a reliable source is proving difficult. Melexis recommend not using 'MLX90621' for new builds and that "Similar functionality provided by the MLX90640". Also, I figure it's best to use the latest version?

https://www.melexis.com/en/product/mlx90621/far-infrared-sensor-array- . . . .

I've searched and read about people successfully using the 90640, but also mentioning that some components aren't necessary?

Post #3, "Another upside of this sensor is the VDD, its 3.3V which renders the additional diode unnecessary"
https://rejsa.nu/forum/viewtopic.php?t=116275

I want to be sure I'm ordering the right components and not overlooking anything. Electronics and coding are not my specialist subjects, and maybe beyond my simple racing driver brain!

Thanks!

Safest bet is of course using the old Melexis but this version https://github.com/MagnusThome/RejsaRubberTrac/tree/develop support the newer ones.

The pcb though is not really for the newer sensors. One issue is that Melexis rotated the pinout on the newer sensors 90 degrees. But as long as you are aware of that it should still be doable. Second issue is a higher supply voltage, but that's an easy fix: replace D3 with a jumper so 3,3V is supplied directly to the sensor. This should be all but I don't know anyone that has actually done this so it is a bit of uncharted territory

I seen you mention the different pin orientation in another thread, strange they decided to change it, but that and the D3 jumper shouldn't be an issue.

I'll try to find someone who has successfully used the 90640, I'm very limited on space and the higher resolution will likely help me.

It's a shame they don't come with pcb boards like the aliexpress versions

Whatever Melexis you choose the Rubbertrac code uses 16 pixels over the tyre width.

Interesting. So, aside from supply, there is no benefit going with a newer sensor?

kevtalbot137 skrev:

Interesting. So, aside from supply, there is no benefit going with a newer sensor?

No benefit

I can't seem to find the BAA version of the older sensor, so will try with the newer type

Magnus Thomé skrev:

Safest bet is of course using the old Melexis but this version https://github.com/MagnusThome/RejsaRubberTrac/tree/develop support the newer ones.

Just to confirm, this version will still work with the nRF52 board?

kevtalbot137 skrev:

I can't seem to find the BAA version of the older sensor, so will try with the newer type Magnus Thomé skrev: Safest bet is of course using the old Melexis but this version https://github.com/MagnusThome/RejsaRubberTrac/tree/develop support the newer ones. Just to confirm, this version will still work with the nRF52 board?

Yes

So, I've been doing more research and discovered another variable..

The BCA and BAA are both 110FOV, but the BCA has the "TGC is disabled and may not be enabled"

Can you see this being an issue? I have no idea if it requires more/different code.

https://media.melexis.com/-/media/files/documents/datasheets/MLX90641- . . . .

I've been using A versions. So that is the safest bet. I've never dug down into the Melexis driver code to see if TGC is used or not though.

The issue I'm having is nowhere has stock of the old BAA sensor versions

Also, I made a mistake. It's the BAA versions that have "TGC is disabled and may not be enabled". The BCA are "TGC is enabled", implying it can be disabled if need be?

Seems MLX90640 BAA is available on Aliexpress though?

They are, but then we run into "uncharted territory". I wanted to try and keep to the tested path if possible, but it seems I have made things more complicated in doing so

Ok, update.

I have built a board using MLX90640 BAA as I couldn't find any stock of the MLX90621

I had some bootloader and driver issues, but the board is now behaving itself.

I could only upload the original version of 'main.ino', not any of the fork versions. The board is working, but only giving data from the distance sensor.

When I try to upload the newer versions with 90640 files, I'm getting errors due to missing files.

'Compilation error: Tasker.h: No such file or directory' is the first error, but I can see that other files listed in the '#include' list are also missing.

Am I doing something wrong?

kevtalbot137 skrev:

Ok, update. I have built a board using MLX90640 BAA as I couldn't find any stock of the MLX90621 I had some bootloader and driver issues, but the board is now behaving itself. I could only upload the original version of 'main.ino', not any of the fork versions. The board is working, but only giving data from the distance sensor. When I try to upload the newer versions with 90640 files, I'm getting errors due to missing files. 'Compilation error: Tasker.h: No such file or directory' is the first error, but I can see that other files listed in the '#include' list are also missing. Am I doing something wrong?

Sounds like you haven't installed all necessary libraries. I don't remember of the top of my head which are used and needs installing but check the includes at the beginning of main.ino

Tasker.h is one of the includes, but doesn't feature in the main folder

kevtalbot137 skrev:

Tasker.h is one of the includes, but doesn't feature in the main folder

You need to install that library in the Arduino IDE

So far I've had success in searching for the missing 'include' files, but unfortunately I'm now stuck on 'sdkconfig.h'

Nothing comes up when I search for sdkconfig.h in the manage libraries section

In what file is that set as an include?

My guess is misconfig of esp vs nrf board somewhere?

It's an error when I try to upload the main.ino from the develop fork

https://github.com/MagnusThome/RejsaRubberTrac/tree/develop

In file included from C:\Users\^_^\Dropbox\Car\Rejsa Rubber\RejsaRubberTrac-develop\main\ble.h:5,
from C:\Users\^_^\Dropbox\Car\Rejsa Rubber\RejsaRubberTrac-develop\main\main.ino:8:
c:\Users\^_^\Documents\Arduino\libraries\ESP32_BLE_Arduino\src/BLEDevice.h:10:10: fatal error: sdkconfig.h: No such file or directory
10 | #include "sdkconfig.h"
| ^~~~~~~~~~~~~
compilation terminated.
exit status 1


Compilation error: exit status 1

Its in the ESP32 boards own code.

Looks maybe a misconfig somewhere between nrf and esp board choices. Either in the IDE or the choices in the RejsaRubberTrac code configurations.

You can also double check using an older ESP32 board library. Sometimes there are breaking changes when the boards code is updated.