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
My regrets for this lengthy post but it may help with further trouble shooting:
Just to be sure I am using Firmware V16 and Release 2014.01.07.00 I know there was a I2C Write Read fix on Release 2013.07.24.00
I tried this I2C command as well(No device) I2CRead(0,Auto,0x03,2) It responded "with syntax error: unknown command" I also tried the other ack's as well, True,False.
I2CWrite(0,0x09,244)This variation also failed(decimal) I2CWrite(0,0x09,0x02,0x05,0x06) This was ran 5 times before Blue light went out. This script was run and failed on the second I2CWrite, just after the 2000 delay. I2CWrite(0,0x09,0x02,0x05,0x06) sleep(2000) I2CWrite(0,0x09,0x02,0x05,0x06) sleep(2000) I2CWrite(0,0x09,0x02,0x05,0x06) sleep(2000) I used a different address this time. This ran nicely until the last command and failed. I2CWrite(0,0x03,0x02,0x05,0x06) sleep(2000) I2CWrite(0,0x03,0x02,0x05,0x06) sleep(2000) I2CWrite(0,0x03,0x02,0x05,0x06) sleep(2000) I2CWrite(0,0x03,0x02,0x05,0x06) sleep(2000) I2CWrite(0,0x03,0x02,0x05,0x06) sleep(2000) I2CWrite(0,0x03,0x02,0x05,0x06) I ran this script again and failed on the first command.
And this command failed first time I2CWrite(0,0x03,0x02)
Is that with the BlinkM plugged directly into the I2C port on the EZ-B or do you have wires between the two?
It may also pay to check the underside of the EZ-B for any shorts between the SCL and SDA of the I2C port.
@Rich (No Device) bare board with no other devices plugged in. I did go over the underside of the board with a plastic spudder probe and a magnifying glass no apparent shorts. Electrically with the ohm meter it read 8k across the SCL and SDA. SCL to grd 5k. SDA to grd 5k. Only 4 k SCL and SDA to the 5volt pin! (I2C port) ...and 1k across the grd and 5v (I2Cport).
Without another EZB to compare readings I don't know if these are normal or not(hardware issue or software) Perhaps DJ may have another insight when he gets back from the big apple
Thanks again for your time @Rich
Glen
Just out of interest (and confusion) why are you trying I2C commands without the device attached?
When I get chance I'll measure the voltages and resistances of one of my EZ-Bs, although I don't know when I will get the chance so don't hold your breath for that one.
@ Rich I would like to determine if its the device causing the issue or the software or the board. If you or anyone else can take some simple resistance readings that would pretty much conclude what is the issue. I know the device works in the "other board so it must be either the EZboard or the software. It seems strange that the I2CRead command is not being recognized as well!? I am using the exact same example in the Script descriptions!? You have spent far too much time trouble shooting my issue and I appreciate that greatly
If the board is hooped then its a matter of getting another. Perhaps a reload of the software or Version upgrade may take care of the I2CRead.
Did you try I2CRead with quotes around Auto? Also, it needs to put the returned data somewhere so it needs to be $variable = I2CRead()
I can't say I've used I2CRead so the above is pure guess work based on what I know of EZ-Script rather than the specific command.
Indeed! I did try the command with the $variable as per the example given in the Script commands. The examples don't show Auto with quotes so no I didn't but will try this right away! and with the $variable = I2C Read() as you suggested.....
No Joy
..... The variable addition had no effect