PR33-31 4-20mA I2C No Longer Detected

Hardware
1

Hello,

I am working on a datalogger project using the PR33-31 current receiver module, a Raspberry Pi and the PR2-2 I2C port hat for the Pi. I was able to read from the current receiver and log the data to a database for around an hour, and then the current receiver stopped working.

I have not connected any current loops and was simply reading the open loop ADC value and logging it to ensure the I2C connection between the pi and the MCP3428 was working. I have attached the images showing the setup I am using currently and the data that was successfully logged.

dataloggersetup
dataloggersetup1920×2560 353 KB

rawcurrentdatalogged
rawcurrentdatalogged1862×702 36.7 KB

I have ensured the pull-up resistors are working, and I have tried setting the I2C clock speed to 1kHz-10kHz-50kHz-100kHz-400kHz rebooting the pi after each and attempting a few “i2cdetect -y 1” commands. The current receiver address should be 0x68 but is still not detected.

The code I am using samples each analog channel once (taking around 250ms per channel sample as I am not concerned with speed right now) every ~15 seconds, after which the ADC value is scaled to a current reading (open loop reading is 0-1 and results in a microampere reading after scaling using the provided 4-20mA min and max ADC readings in the product description). I have attached data points to show the ~15 second spacing between logged sets.

fourloggedrawcurrentwithnextset
fourloggedrawcurrentwithnextset1871×371 19.8 KB

Any help in figuring out what is wrong with my setup would be greatly appreciated.

2

was there any power glitch or static that might have damaged the ADC?

3

I had it plugged in at my desk with the enclosure sealed shut while connected in remotely to the Pi, so definitely no static to my understanding. I am also pretty confident there was no power glitch as nothing else shutdown or rebooted as I was connected to the Pi, the data simply stopped logging, and then I was given an I/O error in my terminal indicating the module was no longer recognized on the i2c bus.

4

The MCP3428 might be damaged. I will recommend sending it back for repair