FS3000 not working with Arduino Giga R1

I just purchased an FS3000-1005 Air Velocity Sensor and have it connected to an Arduino Giga R1 board and a Giga Display. I’m using a Qwiic connector on the sensor board and header pins on the R1 board. The header pins are connected as follows:

  • black to GND,
  • red to 3.3V,
  • blue to SDA (pin 20), and
  • yellow to SCL (pin 21).

I’m running the Example code from the SparkFun_FS3000_Arduino_Library that I’ve modified slightly for the Giga Display. When I run the code, it does print out “Sensor is connected properly" and does show the 3 different readings from the FS3000 board. The problem is that all 3 readings are essentially maxed out even though there is no air flowing through the sensor. The Raw output is varying from sample to sample, but is pegged close to 4070. If I blow through the sensor in the reverse direction, the displayed readings actually go down.
Any suggestions?
Thanks in advance
Dan

You might try putting very slight pressure on the wires inserted into the R1’s headers while in-use to see if there might be an intermittent connection

But my main guess is that the combined i2c pull-up resistance is too high; the Giga R1 has internal upll-ups for that i2c bus (20&21), the sensor also has a set…I’d advise severing the traces between the pads on the backside of the sensor to disable its set

Using an x-acto knife (or something similarly sharp) you can simply cut the 2 small lines between those 3 pads. As a side note, this is easily reversible by placing solder blobs to reconnect them should you need to in the future

Then re-test and see how it goes

Russell
Thanks for the quick response.

  1. When I plugged the system in this morning, it was behaving a bit differently. The sensor output was now randomly bouncing between full-scale and zero velocity. The sensor was still responding when I blew through it, but not accurately.
  2. I put slight pressure on the leads going into the headers, but this made no difference.
  3. I cut the 2 small lines for the I2C jumpers on the back of the board (and verified that the pads were isolated with an ohmmeter), but this also made no difference.
    What do you suggest next?
    Thanks
    Dan

It sounds like a defective sensor

Was it purchased from us? If so head over to Return Policy - SparkFun Electronics (contact vendor if purchased elsewhere) and we’ll get ya squared away