PTI Lidar Plugin icon PTI Lidar Plugin — Pineapple Technology Industries Capstone plugin adds a secretive LiDAR unit to ARC for distance measurement. Try it →

ARC Pro

Upgrade to ARC Pro

Synthiam ARC Pro is a new tool that will help unleash your creativity with programming robots in just seconds!

#1  

Are you able to connect to his wifi from the pc or android?

#2  

We need more info...

  1. Is the battery charged?
  2. Does JD turn on ... make the musical boot up chime
  3. Can you connect to him via your PC or Android?
#3  

Yes I have wifi connection, battery is charged, JD turns on.

#4  

When you click connect on connection 0, what happens?

#5  

It shows "connected", but JD does not respond to commands.

#6  

Are you using any scripts or just the standard JD sample? Under options, there is a debug button. Click that and a window should slide up from the bottom of ARC. Click the copy button and paste the results into this forum.

#7  

Using JD sample: Below is debug results.

6/3/2015 1:44 PM - EZ-B reports EZ-B v4 OS 6/3/2015 1:44 PM - Welcome to EZ-B v4 Beta! 6/3/2015 1:44 PM - EZ-B v4 ID: 31-54-0-0-47-255-58-60-57-37-37-37 6/3/2015 1:44 PM - Connected 6/3/2015 1:44 PM - Setting battery monitor voltage: 6.6 6/3/2015 1:44 PM - Setting battery protection: True 6/3/2015 1:44 PM - Setting i2c rate: 100000

#8  

EZB 0: EZB 1: EZB 2: EZB 3: EZB 4: 6/3/2015 1:41 PM - TCP Server stopped 6/3/2015 1:41 PM - TCP Server stopped 6/3/2015 1:41 PM - TCP Server stopped 6/3/2015 1:41 PM - TCP Server stopped 6/3/2015 1:41 PM - TCP Server stopped 6/3/2015 1:42 PM - Attempting connection on 192.168.1.1:23 6/3/2015 1:42 PM - 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 System.IO.Stream.ReadByte() at EZ_B.EZB.(Int32 , Byte[] ) 6/3/2015 1:42 PM - BbytesToExpect: 1 6/3/2015 1:42 PM - U Received: 6/3/2015 1:42 PM - Disconnected 6/3/2015 1:42 PM - Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 6/3/2015 1:42 PM - Disconnected 6/3/2015 1:42 PM - Camera Initialized: EZB://192.168.1.1 @ 320x240 6/3/2015 1:42 PM - Object Recognition loaded. 6/3/2015 1:42 PM - You have no microphone inputs. The Microphone Control is disabled. 6/3/2015 1:42 PM - TCP Server stopped 6/3/2015 1:42 PM - TCP Server stopped 6/3/2015 1:42 PM - TCP Server stopped 6/3/2015 1:42 PM - TCP Server stopped 6/3/2015 1:42 PM - TCP Server stopped 6/3/2015 1:42 PM - Attempting connection on 192.168.1.1:23 6/3/2015 1:42 PM - 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 System.IO.Stream.ReadByte() at EZ_B.EZB.(Int32 , Byte[] ) 6/3/2015 1:42 PM - BbytesToExpect: 1 6/3/2015 1:42 PM - U Received: 6/3/2015 1:42 PM - Disconnected 6/3/2015 1:42 PM - Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 6/3/2015 1:42 PM - Disconnected 6/3/2015 1:43 PM - EZ-B v4 Camera Error: 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.EZBv4Video.() 6/3/2015 1:43 PM - Camera Disabled 6/3/2015 1:43 PM - Attempting connection on 192.168.1.1:23 6/3/2015 1:43 PM - Connected to 192.168.1.1:23 6/3/2015 1:43 PM - EZ-B reports EZ-Robot OS v25.5 6/3/2015 1:43 PM - Connection Failed: System.Exception: This device is not an EZ-B. Please follow the online tutorials on the EZ-Robot website. at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 6/3/2015 1:43 PM - Disconnected 6/3/2015 1:44 PM - Attempting connection on 192.168.1.1:23 6/3/2015 1:44 PM - Connected to 192.168.1.1:23 6/3/2015 1:44 PM - EZ-B reports EZ-Robot OS v25.5 6/3/2015 1:44 PM - Connection Failed: System.Exception: This device is not an EZ-B. Please follow the online tutorials on the EZ-Robot website. at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 6/3/2015 1:44 PM - Disconnected 6/3/2015 1:44 PM - Attempting connection on 192.168.1.1:23 6/3/2015 1:44 PM - Connected to 192.168.1.1:23 6/3/2015 1:44 PM - EZ-B reports EZ-B v4 OS 6/3/2015 1:44 PM - Welcome to EZ-B v4 Beta! 6/3/2015 1:44 PM - EZ-B v4 ID: 31-54-0-0-47-255-58-60-57-37-37-37 6/3/2015 1:44 PM - Connected 6/3/2015 1:44 PM - Setting battery monitor voltage: 6.6 6/3/2015 1:44 PM - Setting battery protection: True 6/3/2015 1:44 PM - Setting i2c rate: 100000