Asked
Resolved Resolved by DJ Sures!

ARC Wont Connect To EZB

I pulled an EZB -v4 out of the closet today wanting to use it as a bench tester for my robot. I cant seem to have ARC connect to it over Wifi. ARC can find it but won't connect. Here's the debug info I get. Can you guys see anything? :

Attempting connection on 192.168.0.64:23
Connected to 192.168.0.64:23
Reports EZB v4 OS With Comm 2
Firmware 'EZ-B v4.x/2 Native Firmware' on 'EZ-Robot EZ-B v4.x/2' supports the following capabilities:
 - ADC with 12 bit Resolution
 - Can stream Audio v4 codec
 - Reports battery voltage
 - Reports CPU temperature
 - Read/Write Digital I/O Ports
 - Hardware UART TX/RX with DMA buffer and adjustable baud rate
 - I2C Master
 - LIPO battery protection & shutdown
 - PWM Duty on digital ports
 - PWM servos on digital ports
 - PWM servos on digital ports can release their position
 - servo speed for PWM servos on digital ports
 - Has NVRam configuration and can be restored to default settings
 - Transmit Uart TX on all digital ports
 - Adjustable I2C clock speed
 - Configurable UART TX digital port baud timing
 - Ultrasonic Ping distance sensor support
 - 12 Byte Unique Identifier
 - Can stream video v4 codec
 - Native UART Connectivity from ARC
 - Native WiFi Connectivity from ARC
 - Broadcasts to ARC's PnP network scanner

Comm Err: System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at EZ_B.EZB.g0qHi7NcyEbtdq3wbUG(Object , Object , Int32 , Int32 )
   at EZ_B.EZB.ibC1Y96W0m(Int32  , Byte[] cmdData)
BbytesToExpect: 12

Received: 0 0 0 0 0 0 0 0 0 0 0 0 
Disconnected
EZ-B v4.x/2 Native Firmware ID: 0-0-0-0-0-0-0-0-0-0-0-0
Connected

Related Hardware EZ-B v4
Related Control EZB Connections

ARC Pro

Upgrade to ARC Pro

Stay on the cutting edge of robotics with ARC Pro, guaranteeing that your robot is always ahead of the game.

#9  

It's a dead unit. I probably ruined it and didn't know it long ago. Thanks for the help.

#10  

Hey Dave, I did something like that too with my very first Ez4, I was trying to find a power issue and bypassed the Fuse,then forgot to take out the bypass. Found just a wire was not connected,fixed it.Then recently still using it ,added too much voltage. The fuse was still bypassed! Blew the bottom board,sound everything! Always keep a fuse there !Glad to say it is now still working with new bottom board.:D

#11  

Agreed. Fuses rock. They have saved my butt many times. I have a bad habit of pushing the limit and trying to find out how much things will take. Then I get excited and go too fast. BOOM, FRY, SMoke. LOL.

Thanks goodness that these devices are cheep (mostly).