Asked — Edited

Disconnecting

I've received my EZBv4 and changed to Client mode and found the new IP address (192.168.1.15:23), but ARC for windows connects (and i hear sound on EZBv4) but keep disconnecting after a second or two.

Any help would be greatly appreciated - we are trying to use EZBv4 in a science project.

Thanks so much! :)


ARC Pro

Upgrade to ARC Pro

Join the ARC Pro community and gain access to a wealth of resources and support, ensuring your robot's success.

#1  

Try adding the Debug window to your EZB program and capture the error messages and post them here.

#2  

@Will2829, If able assign a static IP address in your router for your EZB. How old is your network router? Others here including myself had to buy a newer router. Have a read through this thread I started when I was struggling with this issue. My setup is running like a clock now:

Connecting To Two V4 Ezb's

#3  

You might need a better router.... I had the same problem (constant disconnects). I solved it by upgrading my router........

#4  

EZB 0: 8/30/2014 1:58 PM - TCP Server stopped 8/30/2014 1:59 PM - TCP Server stopped

EZB 1: 8/30/2014 1:58 PM - TCP Server stopped 8/30/2014 1:59 PM - TCP Server stopped

EZB 2: 8/30/2014 1:58 PM - TCP Server stopped 8/30/2014 1:59 PM - TCP Server stopped

EZB 3: 8/30/2014 1:58 PM - TCP Server stopped 8/30/2014 1:59 PM - TCP Server stopped

EZB 4: 8/30/2014 1:58 PM - TCP Server stopped 8/30/2014 1:59 PM - TCP Server stopped

8/30/2014 2:01 PM - Attempting connection on 192.168.1.15:23 8/30/2014 2:01 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[] ) 8/30/2014 2:01 PM - BbytesToExpect: 1 8/30/2014 2:01 PM - U Received: 8/30/2014 2:01 PM - Disconnected 8/30/2014 2:01 PM - Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 8/30/2014 2:01 PM - Disconnected

#5  

Router is pretty new (< 1yr)...Netgear high end

#6  

Another piece of information that might be useful is that I can connect via my web browser at the 192.168.1.15 IP address just fine and do diagnostics (activate sounds remotely).

PRO
Canada
#7  

Hi @Will2829,

What do you have running within your ARC project when you try to connect?

#8  

Disconnect and no connect issues:

On top of checking your router, you will want to look into your anti-virus software also. I have discovered that AVAST hates ARC.

Avast will:

  1. Block the download of the ARC EXE
  2. Block .dll's when trying to run ARC, even when adding the entire folder of ARC to the exclusion list.
  3. Prevent the connection of ARC to an EZB V4 (EZB V3 no problems).

This has been confirmed on 2 Windows 7 64bit computers and 1 Windows 8 computer.

AVG Anti-virus has no issues with ARC

#9  

VIPRE, is another anti-virus platform that has no issues with ARC.

#10  

This is Will's dad...we disabled the anti-virus...We've now tried to go back to Access Point mode. When trying to connect from ARC for Windows, we get:

8/31/2014 12:48 AM - Attempting connection on 192.168.1.1:23 8/31/2014 12:48 AM - Connected to 192.168.1.1:23 8/31/2014 12:48 AM - EZ-B reports EZ-Robot OS v25.5 8/31/2014 12:48 AM - Welcome to EZ-B v3! 8/31/2014 12:48 AM - Connected 8/31/2014 12:48 AM - Comm Err: System.Net.Sockets.SocketException (0x80004005): An established connection was aborted by the software in your host machine at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at EZ_B.EZB. (Int32 , Byte[] ) 8/31/2014 12:48 AM - BbytesToExpect: 1 8/31/2014 12:48 AM - U Received: 8/31/2014 12:48 AM - Disconnected 8/31/2014 12:48 AM - Disconnected

#11  

Humm, interesting. The debug report says "Welcome to EZ-B v3!". Your son said he had a version 4 EZB. Are you running the latest version of ARC? Uninstall the version of ARC you have on your computer through the Control panel "Programs and Features" icon and then download and re-install the latest version here and give it another try:

Download latest version

#12  

@Dave, I think is/was probably just an oversight in the program... Although it says EZB3 it is definitely connecting (or trying to connect) via wifi .... I mean, as opposed to a com port... Oh, and the OS version reported is a dead give away that it is (the software) not dealing with an EZB3 but rather an EZB4

#13  

OK @Richard, I'm not real good at reading debugging messages. It's just something that jumped out at me and advice I'd give myself if I read that. Good thing there are better minds around here then mine. I'm more if a troubleshooter then an annalist I guess. I always say; "what I don't have in my mind I end up making up in my feet , time and wallet".

Good luck with the connection issue guys. Your in good hands. ;)

#14  

Running 6-22-2014 Version. Appears to be the latest.

PRO
Canada
#15  

Hi @boutonce

Couple of questions that might help narrow down your issue:

What version of windows are you running? And what are you running hardware wise? Ex: Sony Vaio laptop windows 8.1

How far is it from the EZ-B to the computer you are connecting to? Is there possibly a large 2.4GHz RF source or multiple walls between the two?

Are you using battery power or a DC power adapter connect to the power base? How's the voltage level? Did you disable the low battery monitor?

PRO
Canada
#16  

Just thought of another quick question, do you have a wired Ethernet connection going to the PC/laptop you are using?

If so, it may be possible that the router you are connected to could have the same default IP as the EZ-B and causes conflict.

PRO
Synthiam
#17  

If the EZ-B v4 is in "Client Mode", the error you are receiving is because you are connecting to the incorrect IP Address of the EZ-B v4. In Client Mode, you must "scan" to find your EZ-B v4. Please follow the LEARN section of this website to learn how to use Client Mode. I recommend not using Client Mode until you fully understand how to use the EZ-B v4 - or you have followed the detailed LEARN Section of this website.

If the EZ-B v4 is in "AP Mode", the error you are receiving is because you are not connected to the EZ-B Wi-Fi Network. The ARC software is confused because the IP Address that you are attempting to connect to is actually your router. This is because you are not connected to the EZ-B v4, and instead connected to the Wi-Fi router for your network.

Please follow the instructions on the Learn section of the website. You can access the Learn section by pressing the Learn button at the top menu of this website. The step-by-step tutorials will help you understand how to...

  1. reset the ez-b to default settings

  2. load ARC

  3. connect your PC to the EZ-B v4 over Wi-Fi

  4. connect to ARC to EZ-B v4

Those are the steps you need to execute - please use the Learn section to access the tutorials which will help you connect to your EZ-B v4.

If you do not change the settings and use the EZ-B v4 in default Access Point mode, that will be the easiest. Start with the easiest and most basic configuration before attempting complicated Infrastructure Wi-Fi connectivity.

#18  

Thank you, DJ, and everyone sending comments. I have Windows 7 and a PC hard wired to a router (versus laptop/PC with a wireless adaptor - which is what I should be using it sounds like). I followed Learn guides (very helpful) and tried changing IP of my router to no avail. Should I just buy a laptop or wireless adaptor for my PC? Would this be an easier route?

#19  

In order to initially connect to your ezb4 when it is in WP mode (comes from the factory this way) you will need a PC with wifi... Later, once you get the EZB4 in client mode (part of your network) you will be able to connect to it with any PC on your network whether it be "wired" or "wireless"....

#20  

If you have any WiFi device with a web browser (Android or iPad) you can connect it to your EZ-B in AP mode, and then connect the web browser to http://192.168.1.1 and you can then configure the EZ-B to connect to your network. After that, you will be able to connect from your wired PC through your wireless router.

See Rich's tutorial here https://synthiam.com/Community/Questions/5593 for how to configure the EZ-B to your network.

If you have no WiFi devices and no friends with one that could come visit, then you can probably get a cheap USB connected WiFi card for you PC and use it for this set up and if you ever need to factory reset the EZ-B.

Alan

#21  

Thanks. What's interesting is that I had connected with my iPad successfully and changed the EZB4 mode to Client and scanned for its new IP and Builder connected initially but then disconnected. I understand Client mode can be more finicky / challenging

#22  

Once you have it connected to your router in client mode, log onto your router and assign the IP address it assigned to the EZ-B permanently to the EZ-B's MAC address. Then you don't need to have ARC search, you just tell it the address, and everyone who has done this says that the connections have been rock solid (I don't have my V4 yet, so can't speak from experience, but I have done this with other devices with similar concerns and it has always been a good solution for me).

Alan

PRO
Canada
#23  

Hi @boutonce,

If you'd like via adhoc (direct connection) I would definitely investigate a WiFi USB adapter, some can be found for about $10 at places like amazon or adafruit.

Otherwise, just like Alan mentioned, client mode is another viable option.

#24  

I had tried logging into my router and assigning IP to MAC of ezb4 and still wouldn't stay connected. Maybe it's my router, although it's new. Or I missed something else.

#25  

I had problems with it disconnecting when I first tried the new EZB4 out as well. It turned out to be my power supply to the EZB4. Make sure it has a good power supply and if you need to change the minimum voltage you can do it in the Connections Settings.

#26  

I'm using a DC adaptor and likely noisy so I will switch to battery and give that a try. Thanks. I'll report back.

#27  

Still can't resolve issue. I switched to battery and moved EZB4 more than 10 feet from router. I set to client mode, added MAC to router with static IP, and all of that works. In fact i can connect to static IP from web browser and even by hitting the button within ARC and it connects fine and i can do diagnostic sounds, etc. However, when i try to connect by hitting connect button within ARC, it connects briefly, dings, and then immediately disconnects.

#28  

will2829,

Try disabling your Anti-virus software. That was exactly the behaviour when I was using Avast Antivirus. I switched to AVG and have no problems now.

#29  

I was having the exact same problem, a few minutes ago I uninstalled Avast Antivirus and downloaded AVG and now I can connect to my new V4 and it stays connected, that solved my problem quickly :-} So I would check your antivirus program, that could be your problem.

#30  

Still having trouble. I uninstalled antivirus (and spybot) and still connecting (hear ding) then disconnecting. Here's the message:

9/13/2014 9:00 AM - Attempting connection on 192.168.1.56:23 9/13/2014 9:00 AM - 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[] ) 9/13/2014 9:00 AM - BbytesToExpect: 1 9/13/2014 9:00 AM - U Received: 9/13/2014 9:00 AM - Disconnected 9/13/2014 9:00 AM - Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 9/13/2014 9:00 AM - Disconnected

Ireland
#31  

May I suggest you login into your router ( I presume you are in client mode in EZB) check you client list from drop down menu, identify EZB ip ,open port forwarding and setup EZB ip and port

while you may not be interested in using web login at this stage use link below to test router this will show exact ip and port of EZB

https://synthiam.com/Community/Questions/6227

I find this test invaluable as I can see exactly if EZB is connected and its port .

Sometimes my EZB is located in another room by using this simple test I can see if its actually powered up

Obviously antivirus issues may arise as alerady discussed but at least you now know its a pc issue . Pat

PRO
Synthiam
#32  

Can you verify that it still freezes when in AP Mode?

AP Mode is the default mode for the EZ-B v4. Press the RESET button on the EZ-B v4 when powered up and connect to it.

#33  

Yes, it freezes in AP Mode as well. I've tried several times and from my laptop now too. Same issue.

PRO
Canada
#34  

Hello @Boutonce, what brand of PC and Laptop do you have?

Have you had a chance to try a USB WiFi dongle at all?

PRO
Synthiam
#35  

Can you provide a video of it freezing in AP mode please? A direct connection should return a detailed error.