
fisha

Hi
My problem is related to firmware update (Version 16.6) in my private network connected of course to internet via router. In my home network I have subnet addressed 10.10.10.0. All my devices have ip adresses from this network. I set ez-b in client mode with address 10.10.10.15 - and I can get to ez-b via web browser. When I tried to make a firmware update, I have only one address to choose from drop down list: 192.168.1.1:23 and the com ports - how to change the address to real one from my home subnet. Of course I can reset the ez-b to default settings with proper 192.168.1.1 address, but in this case I will not have the internet access, because this is subnet not addressed in my network. The question is what is the problem and if my pc should have internet access during update?
Have you viewed the "how to" video in the Learn section on how to connect the V4 to your network/ARC?
Connecting to EZB4
If you are in client mode, then you will need to use the scan tool in ARC to find your ezb4 then connect to it...
The reason I am asking is it sounds like you are flooding the bandwidth that you have available to the V4.
The issue may be with your access point. The reason I say this is that in AP mode, the EZ-B and the computer communicate without an issue. The most likely other item in this chain that would be causing issues is the access point.
There are may posts on similar issues on this community. Do some searching.
Good luck.
It sounds like it could be a power problem, what are you using to power the EZ-B?
And yes it is normal to hear a bit of static that coming from the EZ-B speaker when the camera is connected as the audio gets amplified going to the speaker, changes in the power supply change the noise floor that gets amplified.
For something to run great for any period of time, and then degrade over time would lead me to believe that the device is working fine, but there is a limitation to power or bandwidth that becomes worse with even a short period of time.
I know that I had lockup issues when I wasn't supplying enough power to the ez-b when using 14 motors, camera and about 5 sensors. I added 2 7.4V 2000mah batteries in parallel. I allow the EZ-B to have 7.4 V and then limit the other devices to either 5V or 6V amps depending on what they need. 3.3 V is handled from the board. I think the issue originally was that I was drawing too many amps when going through a single UBEC for the UBEC to handle, so I split things out to provide 3 paths for electricity from the batteries. 1 UBEC set to 5V up to 5A, 1 UBEC set to 6V up to 5A and then a straight shot to the battery without any power control that goes to the EZB providing 7.4V. This solved my similar issue.
Good luck!
Alan
Yeah it looks like the camera may have any issue. Please try disconnecting and reconnecting the JST cable from the EZ-B end and the camera end, and try removing the camera board from the camera Add-on board and re-seat it. If those suggestions don't work please send a message with our Contact Us page and we will start the replacement process, thanks!
Now, let me review the video and take a look to see what could be happening. One minute...
To help remove the chance of there being an issue with your router or network configuration, please follow these steps...
1) Can you please reset the EZ-B v4 with the Reset Button. Here are the instructions on resetting the EZ-B.
2) Connect to the EZ-B via AP Mode (default network mode)
This AP Mode method will provide more detailed error logging. Please provide us with a video of the camera not working under AP Mode so we can identify the issue.
It is from debug when ez-b is connected to my network:
EZB 0: 2014-09-18 00:28 - Error Initializing Camera: System.TimeoutException: The operation has timed out.
at EZ_B.EZBv4Video.Start(EZB ezb, String ipAddress, Int32 port)
at EZ_B.Camera.StartCamera(ValuePair videoCaptureDevice, Control processedPreviewControl, Control realtimePreviewControl, Int32 captureWidth, Int32 captureHeight). Resolution: 320x240
2014-09-18 00:28 - Object Recognition loaded.
2014-09-18 00:28 - TCP Server stopped
EZB 1: 2014-09-18 00:28 - TCP Server stopped
EZB 2: 2014-09-18 00:28 - TCP Server stopped
EZB 3: 2014-09-18 00:28 - TCP Server stopped
EZB 4: 2014-09-18 00:28 - TCP Server stopped
2014-09-18 00:29 - Attempting connection on 10.10.10.15:23
2014-09-18 00:29 - Connected to 10.10.10.15:23
2014-09-18 00:29 - EZ-B reports EZ-B v4 OS
2014-09-18 00:29 - Welcome to EZ-B v4 Beta!
2014-09-18 00:29 - EZ-B v4 ID: 25-54-0-0-47-255-61-58-58-37-37-37
2014-09-18 00:29 - Connected
2014-09-18 00:29 - Setting battery monitor voltage: 6.6
2014-09-18 00:29 - Setting battery protection: True
2014-09-18 00:29 - Setting i2c rate: 100000
2014-09-18 00:30 - Camera Initialized: EZB://10.10.10.15 @ 320x240
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - error camera: System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Stream stream)
at EZ_B.EZBv4Video.(Byte[] )
at EZ_B.EZBv4Video.()
2014-09-18 00:30 - 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.()
2014-09-18 00:30 - Camera Disabled
and of course I will do the same for default ez-b ap connection:
2014-09-18 00:42 - Attempting connection on 192.168.1.1:23
2014-09-18 00:42 - Connected to 192.168.1.1:23
2014-09-18 00:42 - EZ-B reports EZ-B v4 OS
2014-09-18 00:42 - Welcome to EZ-B v4 Beta!
2014-09-18 00:42 - EZ-B v4 ID: 25-54-0-0-47-255-61-58-58-37-37-37
2014-09-18 00:42 - Connected
2014-09-18 00:42 - Setting battery monitor voltage: 6.6
2014-09-18 00:42 - Setting battery protection: True
2014-09-18 00:42 - Setting i2c rate: 100000
2014-09-18 00:42 - Camera Initialized: EZB://192.168.1.1 @ 320x240
2014-09-18 00:44 - Camera Disabled
2014-09-18 00:44 - Camera Disabled
2014-09-18 00:44 - Camera Initialized: EZB://192.168.1.1 @ 640x480
2014-09-18 00:44 - 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.()
2014-09-18 00:44 - Camera Disabled
What are the specifications of your computer? Perhaps we are dealing with a driver hardware issue.
Videos help a lot because it gives me a PoV experience.
We will figure this out
i had this thismorning.and i unplug averything from router to wifi hub.
waited 5 min and start back plug in one at the time.my internet is,
beter then ever.
It specifically would lock up when I turned the camera on. Without the camera on, everything was fine. I tried ap mode and client mode. Same results.
It might not be it but It might be worth a shot to try the bot in a different location.
I know that with my V3 I plugged a servo into the gnd port and every time I tried to move the servo ARC would lock up and the Ez-b would short out. Could this be happening in the V4 somewhere?
Inspect everything. open up the v4 and make sure there's no faults or visible shorts. I have a couple what I call "bridges" from the top to the bottom of the board chipped so it might be possible with yours.
And in mode 320x240 the same error:
2014-09-18 19:08 - Attempting connection on 192.168.1.1:23
2014-09-18 19:08 - Connected to 192.168.1.1:23
2014-09-18 19:08 - EZ-B reports EZ-B v4 OS
2014-09-18 19:08 - Welcome to EZ-B v4 Beta!
2014-09-18 19:08 - EZ-B v4 ID: 25-54-0-0-47-255-61-58-58-37-37-37
2014-09-18 19:08 - Connected
2014-09-18 19:08 - Setting battery monitor voltage: 6.6
2014-09-18 19:08 - Setting battery protection: True
2014-09-18 19:08 - Setting i2c rate: 100000
2014-09-18 19:09 - Camera Initialized: EZB://192.168.1.1 @ 320x240
2014-09-18 19:09 - 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.()
2014-09-18 19:09 - Camera Disabled
Camera is working once for a 5s and once for a 20s
2014-09-18 19:21 - Attempting connection on 192.168.1.1:23
2014-09-18 19:21 - Connected to 192.168.1.1:23
2014-09-18 19:21 - EZ-B reports EZ-B v4 OS
2014-09-18 19:21 - Welcome to EZ-B v4 Beta!
2014-09-18 19:21 - EZ-B v4 ID: 25-54-0-0-47-255-61-58-58-37-37-37
2014-09-18 19:21 - Connected
2014-09-18 19:21 - Setting battery monitor voltage: 6.6
2014-09-18 19:21 - Setting battery protection: True
2014-09-18 19:21 - Setting i2c rate: 100000
2014-09-18 19:21 - Camera Initialized: EZB://192.168.1.1 @ 320x240
2014-09-18 19:21 - 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.()
2014-09-18 19:21 - Camera Disabled
Customer Support is not Technical Support. The forum is for Technical Support and the Contact Us is for customer support. Customer Support (aislinn, etc) are not technical and unable to assist you with technical questions.
The Forum is for technical support
Now that we have determined it may be a hardware defect, it is time for you to Contact Us. Use the Warranty Claim selection in Contact Us and provide a link to this thread.
Here is an example of how to Contact Us for warranty replacement...
Please check your email. We have already contacted you about replacing your camera, on Wednesday. Did it go to the spam folder?
I'm glad you know the process better now, but there's really no need! We're already processing your warranty request, so please check your email for our notice which we sent a couple days ago...
Thanks for being patient with us! We're shipping it out tomorrow. It shouldn't normally be so long but we had a lot of orders that shipped lately so we had a lot of them to deal with
Every electronic product (or even non electronic product) that is shipped will have some out-of-box failures regardless of how good the quality control and manufacturing are. I was in a market research group from Verizon for 10 years, where they sent us phones (smart and dumb) every few months just before or just after they were released to get our feedback. This was not Beta testing, but production ready devices that they hoped we would talk about and review online, as well as provide feedback to them on a private forum to help them make decisions for future devices.
There were 50 active members. Every time we got a new phone, at least one member would have one that wouldn't work at all, and one or two others would experience serious hardware or software issues that the rest of us didn't see (this doesn't include the fact that we always found bugs that should never have made it past Beta, but that is a different conversation). So, basically, we were seeing a 6% failure rate on phones from the top manufacturers in the world, and we were assured by our contacts at Verizon, that this was not unusual.
I used to work for a company that makes hardware and software for the Contact Center industry. We developed a new T1 card, and our Alpha and Beta testing went great, but when we went to manufacturing, we were seeing a >20% failure rate in fixture testing (where we test the card just before boxing it for shipping to customers). Of the 80% that passed, we still had about a 5% first 6 month failure rate at customers, so we had to redesign the card to make it easier to manufacture correctly.
The fact that EZ-B has shipped thousands of EZ-B's v4's and we have only heard reports here of 3 or 4 that needed to be returned, I think is phenomenal. If I didn't already know the level of quality and support from EZ-Robotics from having some V3's, I would have waited for the second manufacturing run before ordering to let them work out the kinks, but I am very happy to have pre-ordered given the low likelihood that I will experience a problem when my Roli arrives.
Alan
Definitely Contact Us again and reference this thread and we will get you a replacement EZ-B and we'll have you send one of your cameras and the EZ-B in question back to us.