
chas9000c

I just received the Roli with EZ-B v4. I successfully connected via AP mode and loaded the EZ-B v4 admin page in a web browser. Using the admin page, I changed to client mode, entering my wifi SSID and password. The EZ-B v4 is now successfully connected to the wifi network. I no longer connect my PC directly to it, but instead have my PC connect to the wifi as just another client. When the EZ-B v4 starts up, it goes through its usual sounds, ending with saying that it has successfully connected to the network. Its light is green. It is assigned IP 192.168.1.5. I can use a browser to go to the IP address (http://192.168.1.5/) and successfully load the admin page again. I can even ping the diagnostics by calling various URLs via my browser. For example, if I load http://192.168.1.5/button.cgi?10 I reset servos successfully back to 90 degrees. Or loading http://192.168.1.5/button.cgi?0 will cause the EZ-B v4 to play the first diagnostic sound.
So...obviously the EZ-B v4 is successfully connected to my wifi network, and my PC is able to communicate with it via that network by calling URLs at its IP address.
However, the problem is this: If I open ARC and use the "Scan for EZ-B v4" dialog box, here's what happens: When the scan hits the correct IP address (192.168.1.5) the robot makes a little chime. (I assume this is its response to getting pinged.) However, ARC does not log the IP in the "Found IPs" list. In fact, it will go through the entire range of possible IPs (1...254) and find no valid IPs to list in the "Found IPs" list.
What's going wrong? Why can't the scan identify the IP?
If I abandon the scan and instead just enter the IP directly into the 0 row in the "Connection" dialog box and click the "Connect" button, I get an error message that reads, "Could not connect to the EZ-B. Would you like to view the Getting Started tutorials?" The debugger info at the bottom of the screen then shows this:
EZB 0: EZB 1: EZB 2: EZB 3: EZB 4: 11/10/2014 10:33 AM - TCP Server stopped 11/10/2014 10:33 AM - TCP Server stopped 11/10/2014 10:33 AM - TCP Server stopped 11/10/2014 10:33 AM - TCP Server stopped 11/10/2014 10:33 AM - TCP Server stopped 11/10/2014 10:37 AM - Attempting connection on 192.168.1.5 11/10/2014 10:37 AM - Connection Failed: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 192.168.1.5:6666 at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult) at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 11/10/2014 10:37 AM - Disconnected 11/10/2014 10:38 AM - Attempting connection on 192.168.1.5 11/10/2014 10:38 AM - Connection Failed: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 192.168.1.5:6666 at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult) at EZ_B.EZB.Connect(String hostname, Int32 baudRate) 11/10/2014 10:38 AM - Disconnected
What is going wrong? How can I connect ARC to the EZ-B v4?
Thanks.
Thanks @Chas9000c for sharing your solution! I'm kicking myself about not asking about that, because it's something we've seen in the past.
Edit: If you need to give someone credit for this thread, please give it to Richard
Thanks Jeremie, but I really didn't help much....
S'all good, I figure that sometimes people get mixed up and give @Rich credit instead of you so you deserve a little extra credit every now and again
Avast connection issued are documented in this diagnostic lesson: https://synthiam.com/Tutorials/Lesson/14
When connection attempt is made, a window will inform you that it was not successful. It asks if you would like to see diagnostic help. If you press yes, it will bring you to that page.
For future reference or anyone else experiencing connection issues.
I guess what threw me off was that @chas9000c was able to connect via AP mode with Avast running but not client mode, I hadn't heard of that before.
Thanks Jeremie...
Thanks again guys. Just posting this so I can mark as resolved.