I am running an Arduino due + WINC1500 shield + Motorshield V2.3 to control a mecanum wheel bot.
Motors tested fine and have run fine while I have adjusted other functions for a week or so, with all three pieces stacked.
Power supply is 3X 18650 at 12.4V avg full.
Motors all have 3x ceramic caps on each to eliminate noise.
Today, I loaded new code to include wifi connection and test out remote controls, and suddenly the motor Shield will not communicate over I2C, even with a previously working bare test code loaded back on. I2C scanner cannot locate it also, suddenly. No wiring has changed, as there is no wiring for the communication (stacked). Power light still lights up brightly when the 12V terminals are fed.
I have removed the shield and tested it connected to a different unused Due with an i2C scanner, and it cannot be found still.
Motor specs, soldering photos of the project, and photos of the board on the test Due are attached.
Is it likely I have burned out this board somehow, or that it is defective? Should I be lowering the voltage or maximum speed of these motors more than I am? (12.4V max 200 PWM value).
Problems did not start until the wifi shield was first used, then after that point communication would not restart even with a bare bones DUE board and nothing but an i2C scanner code.
Thanks
Motor Shield V2.3 I2C issues
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- chavoD
- Posts: 8
- Joined: Fri Oct 14, 2022 10:39 am
Motor Shield V2.3 I2C issues
- Attachments
-
- IMG_20221029_123454.jpg (165.56 KiB) Viewed 310 times
-
- Screenshot_2022-10-29-12-42-56-78_92460851df6f172a4592fca41cc2d2e6.jpg (474.83 KiB) Viewed 310 times
-
- Screenshot_2022-10-29-12-46-01-22_92460851df6f172a4592fca41cc2d2e6.jpg (799.02 KiB) Viewed 310 times
- chavoD
- Posts: 8
- Joined: Fri Oct 14, 2022 10:39 am
Re: Motor Shield V2.3 I2C issues
In addition, default i2C address is being used as there are no other i2C modules. Logic jumper to 5V is cut and 3.3V logic trace has been confirmed good still.
- adafruit_support_bill
- Posts: 88098
- Joined: Sat Feb 07, 2009 10:11 am
Re: Motor Shield V2.3 I2C issues
The WINC1500 shield does not have any pins in common with the motor shield, so I don't think stacking it would have affected the motor shield at all.
The soldering job looks excellent, so that should not be an issue either.
Do you have a non-Due Arduino to test with? The Due is notorious for i2c problems.
Also note that your motor specs are somewhat marginal for use with the shield. A stall condition @4.5A would be a severe overload condition for the driver chips. Although it could cause damage to the drivers, it should not affect i2c communication.
The soldering job looks excellent, so that should not be an issue either.
Do you have a non-Due Arduino to test with? The Due is notorious for i2c problems.
Also note that your motor specs are somewhat marginal for use with the shield. A stall condition @4.5A would be a severe overload condition for the driver chips. Although it could cause damage to the drivers, it should not affect i2c communication.
- chavoD
- Posts: 8
- Joined: Fri Oct 14, 2022 10:39 am
Re: Motor Shield V2.3 I2C issues
I have a spare UNO I can test with, will report back.
Thanks Bill
Thanks Bill
- chavoD
- Posts: 8
- Joined: Fri Oct 14, 2022 10:39 am
Re: Motor Shield V2.3 I2C issues
Hi Bill
On the UNO, it was indeed able to find 0x70 and 0x60. I believe one is the i2C group and one is the board, yes?
Is there a workaround to get this happy with the DUE? Odd that it worked, and then didn't!
Thanks Bill
On the UNO, it was indeed able to find 0x70 and 0x60. I believe one is the i2C group and one is the board, yes?
Is there a workaround to get this happy with the DUE? Odd that it worked, and then didn't!
Thanks Bill
- chavoD
- Posts: 8
- Joined: Fri Oct 14, 2022 10:39 am
Re: Motor Shield V2.3 I2C issues
Double checked, my sketch as is is 126% for the UNO- sidenote.
Thanks
Thanks
- adafruit_support_bill
- Posts: 88098
- Joined: Sat Feb 07, 2009 10:11 am
Re: Motor Shield V2.3 I2C issues
Yes, 0x70 is the 'all call' address and 0x60 is the default address for the PCA9685.
This thread on the Arudino forum pretty much sums up the state of i2c on the Due. We stopped carrying them a long time ago due to all the problems with it: https://forum.arduino.cc/t/i2c-on-ardui ... ing/975986
If you need the extra GPIO pins, there is the Grand Central M4 which has the same header layout as the Due & Mega. https://www.adafruit.com/?q=grand+centr ... =BestMatch
This thread on the Arudino forum pretty much sums up the state of i2c on the Due. We stopped carrying them a long time ago due to all the problems with it: https://forum.arduino.cc/t/i2c-on-ardui ... ing/975986
If you need something with more memory & processing power than an UNO, there are the Metro M0 and M4. https://www.adafruit.com/?q=metro&sort=BestMatchIt is advised to NOT buy the Due. It is no longer actively maintained. It has bugs. It has design mistakes. It has troubles.
If you need the extra GPIO pins, there is the Grand Central M4 which has the same header layout as the Due & Mega. https://www.adafruit.com/?q=grand+centr ... =BestMatch
- chavoD
- Posts: 8
- Joined: Fri Oct 14, 2022 10:39 am
Re: Motor Shield V2.3 I2C issues
Thanks Bill
I'll give the M4 grand central a go for an easy swap. On order.
Have a great day
I'll give the M4 grand central a go for an easy swap. On order.
Have a great day
- tkudog
- Posts: 16
- Joined: Sun Aug 16, 2020 12:48 pm
Re: Motor Shield V2.3 I2C issues
Hello, I am about to try this myself. Did the M4 grand central work for you? Any issues?
Please be positive and constructive with your questions and comments.