# TSYS01 Reading error

**URL:** <https://discuss.bluerobotics.com/t/tsys01-reading-error/6918>\
**Category:** Sensors\
**Created:** [February 21, 2020, 2:36pm UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918 "2020-02-21T14:36:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![wje](https://avatars.discourse-cdn.com/v4/letter/w/3ec8ea/32.png) [@wje](https://discuss.bluerobotics.com/u/wje)\
**Post date:** [February 21, 2020, 2:36pm UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/1 "2020-02-21T14:36:03Z")

</div>

Hi, I have a fast temperature probe I am installing in a water sampling device.

I have set up a bar30 and it works fine. The fast T is reading 0.00, however.  
 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/e/edeeca57e43d67597674d35d294836d4d6b87780.png)

I have tried in on an adafruit m0 feather, a 328 based board and a 32u4 feather. All give the same result.

With an I2C scanning program, I find it on 0x77, so its connected correctly.

Not sure if I’ve fried it somehow? I have a second fast T that I hook up with the same result. (I could have fried them both, however).

Any help would be great.

Bill

---

<div class="post-metadata">

**Author:** ![jwalser](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jwalser/32/2234_2.png) [@jwalser](https://discuss.bluerobotics.com/u/jwalser)\
**Post date:** [February 22, 2020, 12:42am UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/2 "2020-02-22T00:42:15Z")

</div>

Can you show us a picture of how everything is wired up? We test these libraries on 328 boards, so that will be best moving forward with troubleshooting.

---

<div class="post-metadata">

**Author:** ![wje](https://avatars.discourse-cdn.com/v4/letter/w/3ec8ea/32.png) [@wje](https://discuss.bluerobotics.com/u/wje)\
**Post date:** [February 22, 2020, 6:58pm UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/3 "2020-02-22T18:58:17Z")

</div>

![IMG_20200222_135035](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/2/29e45805466a8f2155de91fc64825ca36b968d1e.jpeg)  
I have the sda and scl with 5v and ground to the level converter, from there to a pullup resistor to 3.3v (10k, in the orange, though I tried 2 and 5k also), and to the Fast T probe.  
The little board is just a piece of soldered breadboard with posts to share the scl and sda among the several probes i will hook up (bar30-which works with this setup, plus later a conductivity probe we are working on) and pullup resistor.

Thanks!

---

<div class="post-metadata">

**Author:** ![rjehangir](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/rjehangir/32/671_2.png) [@rjehangir](https://discuss.bluerobotics.com/u/rjehangir)\
**Post date:** [February 22, 2020, 7:15pm UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/4 "2020-02-22T19:15:22Z")

</div>

Hi @wje,

As far as I can tell that looks right, but it’s a bit hard to tell in the picture. I’d verify that the SCL and SDA lines didn’t get switched at some point. Did you ever operate it at 5v without a level converter?

The wires are a bit long and I2C tends to be very sensitive to that. You could try slowing down the I2C bus to reduce the chances of that. Here’s some code to do that on the 328:

```auto
// Add these two lines in "setup()" to slow I2C clock to 12.5kHz from 100 kHz
// This is best for long wire lengths to minimize errors
TWBR = 158;  
TWSR |= bit (TWPS0);

```

-Rusty

---

<div class="post-metadata">

**Author:** ![wje](https://avatars.discourse-cdn.com/v4/letter/w/3ec8ea/32.png) [@wje](https://discuss.bluerobotics.com/u/wje)\
**Post date:** [February 22, 2020, 7:39pm UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/5 "2020-02-22T19:39:59Z")

</div>

Ok, thanks. The same setup works fine with the bar30 so we likely did something bad to it. I’ll order another couple.

---

<div class="post-metadata">

**Author:** ![rjehangir](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/rjehangir/32/671_2.png) [@rjehangir](https://discuss.bluerobotics.com/u/rjehangir)\
**Post date:** [February 22, 2020, 7:40pm UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/6 "2020-02-22T19:40:35Z")

</div>

Okay - let us know how that goes! If the same problem persists we can help out.

---

<div class="post-metadata">

**Author:** ![wje](https://avatars.discourse-cdn.com/v4/letter/w/3ec8ea/32.png) [@wje](https://discuss.bluerobotics.com/u/wje)\
**Post date:** [February 22, 2020, 11:39pm UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/7 "2020-02-22T23:39:07Z")

</div>

Thanks

---

<div class="post-metadata">

**Author:** ![Pierre021](https://avatars.discourse-cdn.com/v4/letter/p/f1d935/32.png) [@Pierre021](https://discuss.bluerobotics.com/u/Pierre021)\
**Post date:** [February 26, 2026, 4:16am UTC](https://discuss.bluerobotics.com/t/tsys01-reading-error/6918/8 "2026-02-26T04:16:56Z")

</div>

I just got this one tonight. Celsius fast temperature giving me 0.00. I know it was working since I tried the sensor by itself with a pi0. I use this link from the forum for [0.00 reading](https://discuss.bluerobotics.com/t/depth-celsius-fast-response-sensor-problem/15533). First think was to run “i2cdetect -y 1” cmd:

 ![Screenshot 2026-02-25 at 18.50.40](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/3X/9/6/964663a2ce469b11643062bebc9c0777ced5f605.png)

How many sensors do I have ? 5. I guess everybody will know what is the other well know temperature sensor running these addresses at the bottom… Yep, the BME280.

Troubleshooting is done, let’s get a multiplexer.
