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.

Re: No Responses?

by jameschin on Tue Aug 04, 2020 1:04 pm

i2c scan 2.PNG
i2c scan 2.PNG (16.34 KiB) Viewed 43 times

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

Re: No Responses?

by jameschin on Tue Aug 04, 2020 1:13 pm

"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."
The USB cable has a solid connection. There is no possible way the issue could be the connection between the PC and the Grand Central if it works in every other case except during the i2c scan.

Plus I have the same issues with the time of flight i2c, even if the board is not connected to a computer.

In the latest test, the scanner managed to not fault out, but it returned an empty list. I am using the latest firmware and library bundle.

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

Re: No Responses?

by adafruit_support_carter on Tue Aug 04, 2020 1:16 pm

Let's go back and check soldering again. Can't quite make it out in the one photo you posted:
solder.jpg
solder.jpg (9.14 KiB) Viewed 41 times


Please post another one more zoomed in on the soldering.

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

Re: No Responses?

by jameschin on Tue Aug 04, 2020 1:43 pm

It's not the soldering. Why would it be the soldering if every single one of three completely separate time of flight sensors, all with a solid soldering connection, cannot be seen on the Grand Central I2C bus, but can sometimes been seen on the I2C1 bus. None of the connections are loose, and all of the pins have a generous enough amount of solder connecting the header its respective pad on the breakout board.

This picture was taken at the minimum focus distance available with my camera.

20200804_132752_800x600.jpg
20200804_132752_800x600.jpg (115.4 KiB) Viewed 38 times

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

Re: No Responses?

by adafruit_support_carter on Tue Aug 04, 2020 1:59 pm

It may still be soldering. And it may be a similar thing happening with all the breakouts.

solder2.jpg
solder2.jpg (19.76 KiB) Viewed 32 times


The SCL pin looks good in that photo. But some of the others look like they might be cold soldered and not wetted out on the pad enough. See here:
https://learn.adafruit.com/adafruit-gui ... n-problems

Try reflowing the pins and see if that helps

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

Re: No Responses?

by jameschin on Tue Aug 04, 2020 2:55 pm

All 21 of the joints for three time of flight sensors have been resoldered. Macro shots of all three have been included.





The results were the same.

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

Re: No Responses?

by jameschin on Tue Aug 04, 2020 2:55 pm

This was the result.

MicrosoftTeams-image.png
MicrosoftTeams-image.png (28.2 KiB) Viewed 30 times

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

Re: No Responses?

by adafruit_support_carter on Tue Aug 04, 2020 3:23 pm

Thanks. That soldering looks excellent!

OK, now let's try switching back to the secondary I2C port again and see what happens. Simply move the SCL wire to 24 and the SDA wire to 25 like this:
gc_test2.jpg
gc_test2.jpg (301.71 KiB) Viewed 27 times


And then try this test:
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: 16938
Joined: Tue Nov 29, 2016 2:45 pm

Re: No Responses?

by jameschin on Tue Aug 04, 2020 3:50 pm

It returned [41] for all three sensors!

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

Re: No Responses?

by adafruit_support_carter on Tue Aug 04, 2020 4:00 pm

Yeah, some success. OK, so it seems like there may be an issue with the Grand Central's primary I2C pins. Reading back, it sounds like this is a new board and this is your first time trying to use those I2C pins?

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

Re: No Responses?

by jameschin on Tue Aug 04, 2020 4:02 pm

That is correct.

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

Re: No Responses?

by adafruit_support_carter on Tue Aug 04, 2020 4:09 pm

OK. We can replace it. But let's double check to make sure first. Try simply moving back to the original I2C pins SCL/SDA and run the original test again. Verify you still don't get a response. Just in case it was lose connection.

It's passing the pull up resistor check, since you aren't getting the:
Code: Select all | TOGGLE FULL SIZE
RuntimeError: SDA or SCL needs a pull up

message any more. So at least that much is working.

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

Re: No Responses?

by jameschin on Tue Aug 04, 2020 4:12 pm

I still get that line when I run the time of flight sensors with my motor driver (using the secondary i2c pins).

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

Re: No Responses?

by adafruit_support_carter on Tue Aug 04, 2020 4:14 pm

That's a secondary issue. Post another photo of your setup showing how everything is connected with the motor driver.

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

Re: No Responses?

by jameschin on Tue Aug 04, 2020 4:22 pm

It appears to be working with the main i2c pins now. It returns [41].

The problem with the motor driver setup is that the issue only comes up when the whole crane is moving. If I take all of the electronics off the crane and run everything separately, it doesn't appear to have an issue. However, when I run the entire thing with another i2c device (namely, the clock I mentioned before), there doesn't seem to be any problems, even when the crane is moving.

You mentioned that it could be a connection issue, and I thought it might have to do with the sensor losing connection to the Grand Central for a moment, but the same wire setup was used with a Beaglebone Black, and it never lost its physical connection (using the exact same wires and setup). Today, I resoldered the pins onto the time of flight sensors, like you suggested, and I remade the wires so that they would be sturdier, and I added strain relief to all of the sensors. It is still having the same issue.

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

Please be positive and constructive with your questions and comments.