Devantech SRF08 device adress issue?
 

Our team is attempting to use a Devantech SRF08 ultrasonic sensor for the first time. We are using the default example code and receiving the following errors in the dashboard, ERROR -44095 occurred at The I2C sensor identification string did not match. The expected sensor is not at the address and bus specified. The sensor was expected to return "
" but instead returned ""
WPI_I2CVerifyString.vi>>WPI_SonarSRF08_I2C_Open.vi >>Devantech SRF08 Sonar.vi>>Robot Main.vi
FRC: Invalid I2C sensor ID.
I have triple checked and had someone else check that my wiring was correct. Can someone explain to me what the problem is as well as possible solutions. And as always thanks for the help.

Re: Devantech SRF08 device adress issue?
 

What language are you using? Which I2C bus (On-Board or MXP)? If LabVIEW, try running the I2C ENUM vi, which will discover all the devices by address on the bus. This way you can confirm that you're using the correct address (which is usually specified in hex), and that it's wired correctly.

Re: Devantech SRF08 device adress issue?
 

I am using labview and the daventech is plugged into the i2c port in the roborio. I'll try and run the vi you suggest Monday when I can get back to the lab. I noticed that on the device data sheet the sensor was listed as having a hex address but when you call it out in labview it Eames a device number (ex dev0). What's up with that?

Re: Devantech SRF08 device adress issue?
 

Sounds like you're wired to the roboRIO On-Board I2C bus (there's another one within the MXP).

It's sounding like you haven't set the sensor address. The example Front Panel "Device Address" selections (Dev0 - Dev15) correspond to I2C address values. You can view these assignments by opening the Device Address Type Def (right click menu), then selecting Edit Items (right click menu again, from the Type Def's control). One of those values, when expressed in Hexadecimal format, corresponds to your sensor (hopefully).

I'm not familiar with this sensor, but judging from the code design it seems that it is a device that has selectable hex I2C addresses (guessing).

Easiest way might be to run the example at each setting on Device Address.