Mlx90614 not see i2c

When I say i2c list, the address of the device does not appearWhen I say i2c list, the address of the device does not appear
i2cproblem

hello mustafagoksu02,

it usually a regulator issue, you should provide correct power supply to the device to have i2c communication works.

Hello,
I have the same problem. Im provide 3.3 V from 1st pin (I have MLX DCI version - 3 V supply), but sensor don’t respond.

hi bmajdosz ,

please review your device tree property settings, and you should also probe the signaling to confirm the power supply had assigned correctly.

Hey JerryChang,
I used i2cget function (sudo i2cget -y 0x5a 0x0e) that’s what I received.
I2cdetect still dont work. Sorry for low quality.

hello bmajdosz,

please check you’ve assign correct i2c-bus to the command line,
i.e. i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]

Hi,
I assign to 1 bus:

bm@BM:~$ sudo i2cdetect -y -r 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
bm@BM:~$ sudo i2cget -y 1 0x5a 0x20
0x93
bm@BM:~$ sudo i2cget -y 1 0x5a 0x20
0x93

I have also received date using adafruit library, but if try read 2nd time it's Error.

hello bmajdosz,

could you please access Jetson Nano Product Design Guide, and please check [Figure 11-1. I2C Connections].
please confirm which pin you’re used to setup I2C communications.
thanks

Hello JerryChang,
I,m using 3 and 5 pin for I2C communications, 1, 6 for 3.3 V and GND.

hello bmajdosz,

they’re GEN2_I2C_SDA/GEN2_I2C_SCL, it’s general I2C 1 Clock. there’s 2.2kΩ pull-up to 3.3V on the module.

Hello,
Thanks for all Jarry.
I tried with and without additional pull up resistor but nothing change. Anyway when I read object temperature for the first time all is correct but when i call program 2nd time i get:

/usr/bin/python3 /home/bm/FaceRecAndBdyTmpMes/openCV/testi2c.py
Traceback (most recent call last):
File “/home/bm/.local/lib/python3.6/site-packages/adafruit_bus_device/i2c_device.py”, line 154, in __probe_for_device
self.i2c.writeto(self.device_address, b"")
File “/home/bm/.local/lib/python3.6/site-packages/busio.py”, line 159, in writeto
return self._i2c.writeto(address, buffer, stop=stop)
File “/home/bm/.local/lib/python3.6/site-packages/adafruit_blinka/microcontroller/generic_linux/i2c.py”, line 49, in writeto
self._i2c_bus.write_bytes(address, buffer[start:end])
File “/home/bm/.local/lib/python3.6/site-packages/Adafruit_PureIO/smbus.py”, line 314, in write_bytes
self._device.write(buf)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/home/bm/FaceRecAndBdyTmpMes/openCV/testi2c.py”, line 11, in
mlx = adafruit_mlx90614.MLX90614(i2c)
File “/home/bm/.local/lib/python3.6/site-packages/adafruit_mlx90614.py”, line 108, in init
self._device = i2c_device.I2CDevice(i2c_bus, address)
File “/home/bm/.local/lib/python3.6/site-packages/adafruit_bus_device/i2c_device.py”, line 50, in init
self.__probe_for_device()
File “/home/bm/.local/lib/python3.6/site-packages/adafruit_bus_device/i2c_device.py”, line 160, in __probe_for_device
self.i2c.readfrom_into(self.device_address, result)
File “/home/bm/.local/lib/python3.6/site-packages/busio.py”, line 149, in readfrom_into
return self._i2c.readfrom_into(address, buffer, stop=stop)
File “/home/bm/.local/lib/python3.6/site-packages/adafruit_blinka/microcontroller/generic_linux/i2c.py”, line 58, in readfrom_into
buffer[i + start] = readin[i]
TypeError: ‘NoneType’ object is not subscriptable
Exiting…
Cleaning up pins

Is it something wrong with closing bus ?

hello bmajdosz,

could you please review power-on/off sequence,
it should 2nd trial did not power-on correctly to cause connection timed-out.

Hello Jerry,
In the USB analyzaer look like this:


The weirdest think is that happen every 2nd time. I mean at the 1st time is fail , 2nd its ok and the 3rd fail and 4th also ok.

hello bmajdosz,

suggest you should refer to Jetson Nano Product Design Guide to review the design. thanks