Known I2C address but device failed identification

I recently purchased a varied assortment of Sparkfun Qwiic environmental and other sensors of interest with some MUX and a couple of OpenLog Artemis boards so that I could explore the I2C world and start to delve into basic programming for the first time. The Qwiicsystem was especially interesting as it would allow baseline verification of the data logger and single or multiplexed sensors without having to step into the programming world.

After several evenings connecting up the various sensors I was somewhat dismayed to find considerable variation in my ability to make the sensor boards work, or rather communicate.

Here is the synopsis.

Of the two Openlog Artemis, one works completely i.e. the ICM-20948 works in every aspect and it connects and logs data to modules with I2C: while on the 2nd board, the ICM-20948 fails to initiate. The board does however communicate with other Qwiic sensor modules, both through direct communication and through a MUX. So, is the IMU on the second board faulty as it fails to initiate?

Now for the sensors that work to demonstrate to you that I was able to get some of the system functioning.

I was able to make completely operational a Lidar SEN-14722; a Pressure sensor SPX-14767, and to connect and calibrate a SEN15242 to a load cell. All three of these sensors have been logged through a MUX and over 50ft of ethernet CAT5 cable using two differential I2C breakout interface boards. So all good.

What I have not been able to connect to the Artemis are the following sensor boards and I given my total lack of programming knowledge and all of little Arduino terminal exposure, I would appreciate some guidance to make these sensors work, as ironically they are the ones I need. I have looked quite extensively on-line and in the forums for an answer and have not found any.

The sensors are : SEN16304 (TMP102) - digital temperature sensor (qty 4); SEN15112 (SCD30) - CO2 Humidity and temp sensor (qty 2); and, SEN-1376 Humidity and Temperature Sensor (qty 2).

TMP102 - digital temperature sensor

Upon connection to an TMP102 either directly or through the MUX both individually or with other working sensors the terminal responds for all four boards with:

“Identifying Qwiic Devices…

Known I2C address but device failed identification at address 0x48

Autodetect complete

BeginQwiicDevices: No devices detected”

As the I2C address appears to be correct, and as on one board I was able to change the address to 0x49, I assume the I2C comms is working correctly on all four boards. I also changed the pull-up resistors of 4.7K (stock) to 10K, 2K and cut the I2C pads from ground or disconnecting the pull ups as discussed in the documentation without any effect. I am now stuck as to what to do next.

SEN15112 - CO2 Humidity and temp sensor

When either of two boards are connected to the Artemis the terminal reads:

“Identifying Qwiic Devices…

Known I2C address but device failed identification at address 0x61

Autodetect complete

BeginQwiicDevices: No devices detected”

Again I am presuming the I2C comms is working as the correct address is indicated as per the interface document. I have not done any mods to this board because of its cost. At first I thought the module might not be Qwiic system compatible but a check of the product description states ” SCD30 Humidity and Temperature Sensor can also be automatically detected, scanned, configured, and logged using the OpenLog Artemis datalogger system. No programming, soldering, or setup required!”

Lastly, the SEN-1376 Humidity and Temperature Sensor. When connected to the Artemis it connects with I2C correctly, but I only get 0 degC or 32 deg F temperature readings and no humidity reading either in the data or on the header. I have not been able to find a configuration in the settings that provides the correct temp and a humidity data stream

Any help would be appreciated to solve the interface to these last three boards.

Of the two Openlog Artemis, one works completely i.e. the ICM-20948 works in every aspect and it connects and logs data to modules with I2C: while on the 2nd board, the ICM-20948 fails to initiate. The board does however communicate with other Qwiic sensor modules, both through direct communication and through a MUX. So, is the IMU on the second board faulty as it fails to initiate?

OK, that’s likely a defective Openlog Artemis, fill in the form [on this page with your order number and a link to this forum post and we can get that fixed for you.

What I have not been able to connect to the Artemis are the following sensor boards and I given my total lack of programming knowledge and all of little Arduino terminal exposure, I would appreciate some guidance to make these sensors work, as ironically they are the ones I need. I have looked quite extensively on-line and in the forums for an answer and have not found any.

The sensors are : SEN16304 (TMP102) - digital temperature sensor (qty 4); SEN15112 (SCD30) - CO2 Humidity and temp sensor (qty 2); and, SEN-13763 Humidity and Temperature Sensor (qty 2).

OK, the TMP102 and Si7021 are not on the list of boards that work with the Openlog Artemis so unfortunately those are not going to be compatible. The SCD30 is on the list but you probably need to do a firmware update to get that operational. You can find directions for updating the firmware [here in the hookup guide.](https://learn.sparkfun.com/tutorials/openlog-artemis-hookup-guide/updating-firmware)](Return Policy - SparkFun Electronics)

Thanks for your comments back, I will follow through with your suggestions and also get a Redboard to try the incompatible sensors

I am having this same problem. Wired up an SCD30 to an OLA. I had previously updated OLA firmware to V18.bin. The logger was working correctly and I was able to see data from IMU on the OLA. I took the next step and plugged in the SDC30 (I have checked and rechecked to see that SDL and SDA are correct polarity). SCD30 has a slow on and off orange LED, so it powered up. But on OLA power up or on reset the SCD is not recognized by the OLA. I get this error: “Known I2C address but device failed identification at address 0x61”. When I try to configure/detect the sensor manually, I get the same error. I tried diddling with the I2C resistors, (1.5k default) and this did not change outcome. I have no way of knowing if I have a defective OLA or defective SCD or some other issue. Suggestions?

I am having the same issue as TS-Chris, but I only have one Openlog artemis. I’m able to connect and log with the load cell (NAU7802) but I can’t log with the ICM-20948 IMU. I get: ```
Known I2C address but device failed identification at address 0x69


<QUOTE>

> OK, that's likely a defective Openlog Artemis

</QUOTE>
I'm wondering if I have a defective board as well, but I noticed that the [[documentation for the Artemis](https://github.com/sparkfun/OpenLog_Artemis) doesn't list ICM-20948 as supported for automatic logging. Is it possible the sensor is simply not supported for this activity? If so, is there something that can be done about it?](https://github.com/sparkfun/OpenLog_Artemis)

Not seeing the ICM-20948 on the list of compatible Qwiic devices.

If so, is there something that can be done about it?

The documentation you link too has direcions for adding sensors.