voxi
Hello everybody, I have the following problem with my JD. Every time I turn it on and the W-Lan connection is ready, I go into the ARC and click on connect, following happens.
I use the Example of JD in ARC
EZB 0: EZB 1: EZB 2: EZB 3: EZB 4: Screen Resolution: 1280x720 (96x96 dpi) Version: 2017.01.29.00 Object Recognition Initialized. Object Recognition loaded. You have no microphone inputs. The Microphone Control is disabled. Attempting connection on 192.168.1.1:23 Connected to 192.168.1.1:23 Reports EZB v4 OS With Comm 1 EZ-B v4 ID: 68-50-0-0-46-255-59-56-57-38-38-38 Setting battery monitor voltage: 7 Setting battery protection: True Setting i2c rate: 300000 EZ-B voltage is 7.778942076 EZ-B temperature is 24.94538180761402188C Connected Camera Initialized: EZB://192.168.1.1 @ 320x240 Comm Err: System.IO.IOException: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. ---> System.Net.Sockets.SocketException: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 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.M3jweGrVXK(Int32 , Byte[] cmdData) BbytesToExpect: 2
Received: 0 0 Disconnected
stress stress stress
I have tested it on two pc's. Both of these errors occur. 1x Win 10 and win 7
Can anyone help me please
Check the cable to the JD Eyes and make sure it has a good connection.
Find the JD-No Eyes sample project and try that (or just try a connection with no project loaded).
If any I2C object tries to initialize and can't find the device, the EZ-B will lock up and disconnect.
Alan
Try reconnecting the camera cable at the ezb. Make sure you have a good connection there.
Hello,
thanks for the hints. I will test it later and give my feedback
Hi,
it works ! the reason was the cable of the I2C port.
Embarrassed that I did not find this error myself.
Thanks for your quick help !