irobot58
Resolved by DJ Sures!
This is the first time I have tried using the I2C command and port. The EZ-B browns out (blue tooth is still blinking) when I run the command with nothing attatched at the port. Sometimes it fails right away running the script once and sometimes it takes 3 to 4 times for it to fail. No brownouts occur when not running the script!
I2CWrite(0,0x09,"n",0x00,0x00,0x11) ran Script 2
2/14/2014 3:46 PM - Comm Err: The operation has timed out. 2/14/2014 3:46 PM - BbytesToExpect: 1 2/14/2014 3:46 PM - Received: 2/14/2014 3:46 PM - Disconnected 2/14/2014 3:46 PM - Disconnected 2/14/2014 3:46 PM - Disconnected
second attempt, ran script 4 times and EZ-Board crashed.. following dbug info 2/14/2014 3:47 PM - Attempting connection on COM3 2/14/2014 3:47 PM - Connected to COM3 at 9600 2/14/2014 3:47 PM - EZ-B reports EZ-Robot OS v16 2/14/2014 3:47 PM - Welcome to EZ-B v3! 2/14/2014 3:47 PM - Connected 2/14/2014 3:47 PM - Setting battery monitor voltage: 6 2/14/2014 3:47 PM - Setting battery protection: True 2/14/2014 3:47 PM - Disgard incoming buffer (This usually means your EZ-B requires more power or the communication is unstable) 2/14/2014 3:48 PM - Comm Err: The operation has timed out. 2/14/2014 3:48 PM - BbytesToExpect: 1 2/14/2014 3:48 PM - Received: 2/14/2014 3:48 PM - Disconnected 2/14/2014 3:48 PM - Disconnected 2/14/2014 3:48 PM - Disconnected
I checked the underside of the board for any "shorting issues" at the I2C area with a magnifying glass and found none. I did take a plastic spudder probe and gently rubbed in between all 4 pins. Topside at the prcessor looked clean and free of any possible contaminates. I also, while the EZ was powered up checked voltages at the +5 volts and ground at the I2C pinouts. There was 5 volts at the SCL and SDA pinouts to ground. I dont know if that is normal?! When the EZ-Board was powered downd I measured 70K between SDA and SCL pinouts. The BlinkM type works fine on my "other" board . This is the first time I have tried using the I2C command and port.
I hope someone can verify my voltage readings at the SDA and SCL points to compare my findings. I am not sure what else I can do to further trouble shoot, any ideas would be greatly appreciated
Thanks for any assistance,
Glen
@shamon thanks for your input! The plot thickens....Rich said his I2C works with an earlier version (thread #48) , a version before I2C issues were fixed. hmmmm ........... What version are you using?
I am using the most current software version and the Ez b 3 with the firmware version 16. The newest one. I am thinking this has to be a software issue from all the forum talk.
@shamon I am thinking of contacting " Contact us" as the I2CWrite issue has not been resolved. They may provide more insight. There are 3 boards that are doing the same malfunction and it now seems to be pointing to the software. Rich has done his best to test from his end. I know DJ is extremely busy with the V4 release but perhaps one of his team members can check it out. If I had saved an earlier version that is known to work per Rich , we could at least test it as well.
I've mentioned it to Jason just on the off chance that nobody at EZ-Robot had picked it up.
I'll still be testing one more thing later which is to use 2013.06.06 (known working version) and the latest on my Windows tablet, same PC, same robot, no change other than the version of ARC, that should pretty much pin point if it is software based.
Hey guys,
Sorry we have been quite busy these days with the wave of interest that came after the Toy Fair. I have just verified the bug and will pass it on to DJ to squash when he has a spare moment. Thanks for the heads up on it!
Excellent. That saves me having to downgrade ARC to test it (since updates rarely break things I wanted to be sure before passing it over to DJ).
Once again Thank you Rich and @skater!
This is my second thank you to DJ for resolving this issue ! My full joy and gratitude is expressed in DJ's Release Thread!