mlx90632-library icon indicating copy to clipboard operation
mlx90632-library copied to clipboard

EEPROM version register documentation mismatch with library ?

Open linkineo opened this issue 2 years ago • 1 comments

We're using both Medical/Extended-grade and standard versions of the sensor.

In the library during initialization, the following check is performed in the EEPROM version register 0x240b https://github.com/melexis/mlx90632-library/blob/0b1be08be1191f7244b3b65eac74a1614edaf3b8/src/mlx90632.c#L467

with https://github.com/melexis/mlx90632-library/blob/0b1be08be1191f7244b3b65eac74a1614edaf3b8/inc/mlx90632.h#L192

Yet the latest datasheet from your website does not document this register. It however documents the product code like this:

image

Questions: Is the magic 0x0500 always reflecting a medical-grade device or which meaning does it have ? Why not use in the library the product code as a way to identify a medical-grade device ?

linkineo avatar Jun 23 '23 13:06 linkineo

0x0500 does not mention anything about medical-grade device, so I am not sure why you would think this is connected?

The extended range is read at initialization (https://github.com/melexis/mlx90632-library/blob/0b1be08be1191f7244b3b65eac74a1614edaf3b8/src/mlx90632.c#L446) from EE_VERSION (https://github.com/melexis/mlx90632-library/blob/master/inc/mlx90632.h#L87) which is on address 0x240B and it defines the eeprom content variation which enables us to keep some backwards compatibility with older versions as well as with newer extended range versions. The product code you are referencing is not present in older devices.

Letme avatar Jul 31 '23 08:07 Letme

I am cleaning up the open issues and this seems to be resolved.

Letme avatar Oct 01 '24 07:10 Letme