Voting resources, early voting, and poll worker information - VOTE. ... Adafruit is open and shipping.
0

No Responses?
Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.

No Responses?

by jameschin on Tue Jul 28, 2020 2:51 pm

I posted a question a week ago and have yet to receive a response. It is stated quote, "We will answer questions in a timely manner (generally within 2 business days)." on the contact us page. It has been more than 2 business days.

Here's a link to my question, followed by a copy of my previously made post.

viewtopic.php?f=63&t=167573

I have a Grand Central connected to an Adafruit VL53L0X over SDA1 and SCL1 (24 and 25), but it keeps giving me the following errors:
OSError: [Errno 5] Input/output error
RuntimeError: SDA or SCL needs a pull up

It will give me the first one, and then every time I reset the board it will give me the second error. The time of flight sensor has built in pull up resistors, but I tried added some and they didn't work.

The reason it's connected over SDA1 and SCL1 is because the SDA and SCL pins don't work (it doesn't see a device at the default address). I looked up some other forums and using pin 24 and 25 was recommended and once I tried that the Grand Central was at least capable of seeing the time of flight sensor at the default address.

Before anyone asks, yes, the board is connected correctly (I've tried VIN to both 3.3v and 5v, GND to GND, SDA to SDA/SDA1 and SCL to SCL/SCL1). And yes, the time of flight sensor does work, I've tried three of them on the Grand Central and none of them work, but they all work on an Arduino Mega.

The time of flight sensor will only work if I unplug and replug them into power/the Grand Central in random ways. There is no rhythm or reason to what makes them start working again. But once they start working it will only work for a few seconds before hitting an error.

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by adafruit_support_carter on Tue Jul 28, 2020 4:08 pm

Those errors seem to indicate a connection issue. Please post a photo of your setup showing how you have everything connected.

adafruit_support_carter
 
Posts: 16922
Joined: Tue Nov 29, 2016 2:45 pm

Re: No Responses?

by jameschin on Thu Jul 30, 2020 1:30 pm

Time of Flight to Grand Central:
VIN to 5V
GND to GND
SHDN to 44
SDA to SDA1
SCL to SCL1

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by adafruit_support_carter on Thu Jul 30, 2020 1:43 pm

Please post a photo of your actual setup. It's the only way we can verify the state of the hardware.

adafruit_support_carter
 
Posts: 16922
Joined: Tue Nov 29, 2016 2:45 pm

Re: No Responses?

by jameschin on Thu Jul 30, 2020 3:59 pm

Time_of_Flight_to_Grand_Central.png
Time_of_Flight_to_Grand_Central.png (759.62 KiB) Viewed 117 times

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by jerryn on Thu Jul 30, 2020 4:12 pm

Just an FYI -- I use pins 20/21 for I2C 21-> SCL 20-> SDA
https://learn.adafruit.com/adafruit-grand-central/pinouts#logic-pins-3015122-8

jerryn
 
Posts: 1299
Joined: Sat Sep 14, 2013 9:05 am

Re: No Responses?

by adafruit_support_carter on Thu Jul 30, 2020 4:40 pm

Thanks for the photo. A couple of things to try and check:

Move VIN to 3V. The GC is a 3V board and VIN sets the logic level on the SCL/SDA lines.

Remove the SHDN wire. It's not needed at this point. There is a pullup on the breakout that will hold the pin in the ON state by default.

It's odd that you had issues with the primary SCL/SDA pins. It may be related to the VIN, but you mention trying both. We can continue to try using the secondary I2C pins as per your current wiring. Make the wiring changes above and then try this basic I2C scanner and see what happens.

Here's what I got:
Code: Select all | TOGGLE FULL SIZE
Adafruit CircuitPython 5.3.1 on 2020-07-13; Adafruit Grand Central M4 Express with samd51p20
>>> import board
>>> import busio
>>> i2c = busio.I2C(board.SCL1, board.SDA1)
>>> i2c.try_lock()
True
>>> i2c.scan()
[41]
>>>

adafruit_support_carter
 
Posts: 16922
Joined: Tue Nov 29, 2016 2:45 pm

Re: No Responses?

by jameschin on Fri Jul 31, 2020 9:36 am

I've tried both the 3.3v pin, the 5v pin next to it, and the 5v pins that I'm using right now.
I have also tried removing the SHDN wire.

I have also tried the i2c scanner, which sometimes sees the device and sometimes doesn't.

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by adafruit_support_carter on Fri Jul 31, 2020 6:44 pm

To possibly help with testing - Do you have another main board other than the Grand Central? Do you have another I2C device other than the VL53L0X.

Let's continue to check for potential connection issues. Can you post another photo that more clearly shows the soldering job on the header pins for the VL53L0X.

adafruit_support_carter
 
Posts: 16922
Joined: Tue Nov 29, 2016 2:45 pm

Re: No Responses?

by jameschin on Mon Aug 03, 2020 8:49 am

I have tested our three time of flight sensors with our two Grand Centrals. I have also tried the time of flight sensors with Arduino Mega boards. The Mega does not output the same error as the Grand Central, but the sensors will sometimes freeze on one value (sending a constant stream of a single value).

The time of flight sensors seem to be running a little better now, when it is the only thing connected to the Grand Central. I have tested another i2c device (DS3231 RTC) as well, and it seems to be fine. However, whenever I connect another device to the Grand Central (specifically a Pololu dual motor driver, https://www.pololu.com/product/1213), the Grand Central will run for a few seconds, and then output the same error.

20200803_083431_600x800.jpg
20200803_083431_600x800.jpg (115.51 KiB) Viewed 91 times


The time of flight sensors appear to be erratic, working sometimes but not always, and never working consistently when the Grand Central needs to control any other board (we are using two PWM signals to control the Pololu Dual Motor Driver Board, the motor power is isolated from the Grand Central).

I have yet to try the alternate i2c device with the Grand Central in conjunction with the motor control board, I will be doing that today.

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by jameschin on Mon Aug 03, 2020 11:18 am

I have tested the i2c RTC with the Grand Central and the motor driver. For the moment, it appears to be working. I am currently letting it run to see if it freezes or locks up at any point.

This leads me to believe that the issue may be the time of flight sensor.

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by adafruit_support_carter on Mon Aug 03, 2020 11:41 am

In general, these all sound like connection issues. And with the motor, possibly also motor noise affecting things.

To sanity check the VL53L0Xs, we need to test those in isolation. Let's move back to the primary I2C port on the Grand Central and run the basic check above again. And do this for each of the 3 VL53L0X sensors.

Set up like this:
  • 3.3V to VIN
  • GND to GND
  • SCL to SCL
  • SDA to SDA
gc_vl53l0x.jpg
gc_vl53l0x.jpg (456.33 KiB) Viewed 80 times


And then run this check for each sensor:
Code: Select all | TOGGLE FULL SIZE
Adafruit CircuitPython 5.3.1 on 2020-07-13; Adafruit Grand Central M4 Express with samd51p20
>>> import board
>>> i2c = board.I2C()
>>> i2c.try_lock()
True
>>> i2c.scan()
[41]
>>>

and post the output you get here.

adafruit_support_carter
 
Posts: 16922
Joined: Tue Nov 29, 2016 2:45 pm

Re: No Responses?

by jameschin on Mon Aug 03, 2020 2:47 pm

I've included a picture of my setup as well as the result of the i2c scan.

20200803_142854_2_800x600.jpg
20200803_142854_2_800x600.jpg (216.41 KiB) Viewed 74 times


i2c scan.PNG
i2c scan.PNG (22.48 KiB) Viewed 74 times

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by jameschin on Mon Aug 03, 2020 3:45 pm

In my previous reply I posted pictures of my setup and the results. This was exactly the same for all three time of flight sensors, and another i2c device (RTC DS3231, please note that the breakout I used is NOT the Adafruit breakout).

jameschin
 
Posts: 63
Joined: Sun Jan 05, 2014 8:04 pm

Re: No Responses?

by adafruit_support_carter on Tue Aug 04, 2020 11:13 am

Thanks for the screen shot. The error looks like it's happening between your PC and the Grand Central, since it's a Putty communication error. So not something I2C related.

From the screen shot, can see that you are running older CircuitPython firmware. Let's go ahead and update things and see if that helps at all. You can get the latest CircuitPython firmware for the Grand Central from here:
https://circuitpython.org/board/grandce ... 4_express/
and the latest Library Bundle from here:
https://circuitpython.org/libraries

Do that and then repeat the above test with the VL53L0X.

adafruit_support_carter
 
Posts: 16922
Joined: Tue Nov 29, 2016 2:45 pm

Please be positive and constructive with your questions and comments.