USA
Asked — Edited

Ez-B Camera Not Connecting To Camera Device Control

Skip to comments   Jump To End

You can see error below. It has never successfully connected to the camera. ARC can connect to ez-b. Under Advanced Settings for the EZ-B HTTP page, Camera Transmit Nagle: disabled Camera Transmit Max Packet Size: 1152 EZ-B Transmit Nagle: disabled EZ-B Receive Buffer Size: 4000

Wi-fi client mode

Camera has solid LED

Any diagnostics that I can run? Any test?

Attempting connection on 192.168.1.140:23
Connected to 192.168.1.140:23
Reports EZB v4 OS With Comm 2
EZ-B v4 ID: 58-49-0-0-46-255-60-58-58-37-37-37
Setting battery monitor voltage: 7
Setting battery protection: True
Setting i2c rate: 100000
EZ-B voltage is 12.603122142
EZ-B temperature is 24.55025960369194128C
Connected
Camera Initialized: EZB://192.168.1.140 @ 320x240
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.dr0AP6qn6r(Int32  , Object  )
Camera Disabled

ARC Pro

Upgrade to ARC Pro

ARC Pro is your passport to a world of endless possibilities in robot programming, waiting for you to explore.

PRO
Synthiam
#1  

Dassey, put your ezb back in Adhoc mode. You're trying to connect to an up address of 192.168.1.140, which ARC is clearly telling you is NOT an Ezb

17/2017 6:37:36 PMConnected to 192.168.1.140:24 3/17/2017 6:37:36 PMReports 74 3/17/2017 6:37:40 PMConnection Failed: System.Exception: This device is not an EZ-B. Please follow the online tutorials on the EZ-Robot website. at EZ_B.EZB.hWAaYE4tpK()

Your ezb has been working totally fine in adhoc (default) mode. For example on 3/11/2017, you connected successfully to the ezb in adhoc mode. Go back to that made or follow the tutorials to correctly learn how to put the ezb in client mode.

Press the reset button on the ezb and DO NOT CHANGE SETTINGS. Get the ezb to work in default adhoc mode to eliminate any local network configuration issues first. One step at a time...

/11/2017 4:28:55 PMVersion: 2017.02.20.00 3/11/2017 4:29:05 PMAttempting connection on 192.168.1.1:23 3/11/2017 4:29:06 PMConnected to 192.168.1.1:23 3/11/2017 4:29:06 PMReports EZB v4 OS With Comm 2 3/11/2017 4:29:07 PMEZ-B v4 ID: 58-49-0-0-46-255-60-58-58-37-37-37 3/11/2017 4:29:07 PMSetting battery monitor voltage: 7 3/11/2017 4:29:07 PMSetting battery protection: True 3/11/2017 4:29:07 PMSetting i2c rate: 100000 3/11/2017 4:29:07 PMEZ-B voltage is 12.371376102 3/11/2017 4:29:07 PMEZ-B temperature is 25.07708920892138208C 3/11/2017 4:29:07 PMConnected 3/11/2017 4:33:30 PMDisconnected 3/11/2017 4:33:39 PMNew version of software is available!

Then at 5:00 on the same day, you began loading ar parrot drone projects and trying to connect to ar parrot drone cameras. And then began attempting to connect to 192.168.1.140 for some reason.

Maybe you can start by telling us what you're attempting to do? And also check the tutorials - as ezrobot has made fantastic tutorials. Absolutely everything is covered.

#2  

I hate rebooting the damn thing because I never know if it will remember the wifi settings because it's a btch to get them back in. It keeps locking up and I have to plug and unplug it and try again. At some magical point it will decide that I did it just right and keep the wifi settings. It's not just the wifi settings though. It's any button on the http page. If I click a button 70% of the time it locks up and I have to plug/unplug it and try again.

Regardless; it's a valid point. Verify that the adhoc connection also does not work. That will eliminate the majority of networking issues. I know the fw on the machine itself has been opened. Perhaps it's one of the routers.

Will update thread with results.

DM

#3  

Well, I thought it was toast for half the day. Just kept flashing white LED and saying communication error. Removed both plastic cases and plugged in (using same power source) and it still didnt work. Pushed and prodded, looked for anything popping or whatever. Nothing seemed out of place. Plugged it in again and it works. When I say it works I mean it allowed me to connect to the adhoc network.

Hopefully you can see the logs. Seems pointless to post the logs again as it is the same issue.

I went to client mode and rebooted (still no shell) and low and behold it saved the settings. I rebooted a few times just to see and it seems to be saving the settings now.

But still unable to connect to the camera.

I will put the shell back on and see if it continues to power up and remember settings. I guess I can take the shell off the camera and see if that does something

DM

#4  

Ya, no. Same issue. Its flaky as can be. The camera seemed to pull a blurry image for a single frame, but I am not sure, it was too fast. That was while on my wifi, not adhoc. This thing is so flaky. Thats all I need. Remotely mowing the grass and it stops transmitting.

Login to post a comment