
irobot58

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
Can you run your script repeatedly ? Also take some voltage and ohmage readings on your I2C port to compare with Richs if its convenient.
Thanks so much Herr Ball!
The one that comes with EZB with the 3 different color sliders.
Although I have several servos attached to the board, nothing was running at the time but the BlinkM script.
As I stated, I can run either BlinkM and the board does NOT brownout now!
NO changes where made from the time of brownout till tonight.
I just don't understand why it started working here.
As for board readings, all mine are close to Rich's.
I do get on the sda to scl = 7.22k, thats a little off from his.
Getting late here, will try again tomorrow.
Hopefully I'll have some time this weekend to dig a little deeper and see what's what. I don't think Brownout is the correct term for what is happening but the more info we can get together the easier it will be to solve. It may be something simple although my concern is Melvin wouldn't work and my PC hasn't changed at all other than updating ARC, on the wiring side of things Melvin hasn't changed either but I'll double check that as I can't be 100% sure something hasn't come loose inside him.
I haven't tried it on the current release so it may have been updated and fixed for all I know however I would say that everything is pointing towards the release I used when I made the video has an error with the I2CWrite. When my memory card turns up for the Acer W3 I'll try it on that with both 2013.06.06 and the current version using the same project and same robot with no changes to anything other than the version of ARC being used, this will pinpoint if it is a software error.
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.
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!
i am facing this problem please help me
What type of power source are you using? It needs to be big enough to handle the load demands (your wiring also)
What devices or motors are you using when this issue occurs? Something may be drawing power away from the device or EZB you are trying to get to work.
Have you checked to make sure all connections are tight and properly made? i2c connections are notorious for failing if there is a lose connection.
How are you connecting to ARC? If using WIfi are you using the default EZ-B v4 Wi-Fi setting , AP Mode (also called Wi-Fi Access Point or AdHoc) or are you using client mode? Either way make sure you have a good strong signal. If in client mode make sure you are on an uncluttered channel. Here's a connection troubleshooting guide:
connecting-and-troubleshooting HTML
Good luck.