That’s the setting I was thinking about.

If you’re putting this in a public place - at the least test now with a WiFi password on the ezb.

You might want to consider asking someone here to whip up a USB adapter for you to connect the ezb. I mention that because when you’re in a public place, the WiFi may cause interference with the camera.

Lastly, is the camera only disconnecting or is the entire computer disconnecting from the WiFi?

Oh, thanks a lot DJ. Way to rain on my parade, lol. You know, though, I had it at my school for almost a month with no wifi interference troubles and we have good wifi. Of course that doesn't mean much. I scanned the article you linked to about making the USB connection. It seemed pretty straight forward and I have most of the parts already. And again, yes, you're right. I'll need to secure the EZB with a password before the show. Good call.

Oh, and yeah, it's the EZB disconnecting, not just the camera. Furthering the idea that it was that windows setting.

Looking forward to hearing if there is any improvement.

Well guys, no luck. It disconnected again last night. It ran fine from about 10 AM until 2:30 AM and then disconnected the same as always. I read a fellow's post that said he was having the same trouble with Win 10 on a surface Pro 1 and the only thing that fixed it was rolling back to Win 8.1. Since the soul purpose of this Surface is to run iRobot, I think that's my next step. But I'll need to make an image of the current drive first. I've never done that without a disc drive so this should be a learning experience. Wish me luck...

Here's the error. Still looks like the Surface is disconnecting to me.

11/4/2018 2:40:06 PM - Saved C:\Users\reset\Desktop\iRobot_Final.EZB 11/5/2018 2:30:36 AM - EZ-B v4 Camera Error: System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine 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.zhDAFhUutB(Int32 , Object ) 11/5/2018 2:30:36 AM - Camera Disabled 11/5/2018 2:30:37 AM - Comm Err: System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) at EZ_B.EZB.nM1edIYc5k(Int32 , Byte[] cmdData) 11/5/2018 2:30:37 AM - BbytesToExpect: 2 11/5/2018 2:30:37 AM - Received: 0 0 11/5/2018 2:30:37 AM - Disconnected

You probably searched Google already. I did also and found this:

An established connection was aborted by the software in your host machine

That is a boiler-plate error message, it comes out of Windows. The underlying error code is WSAECONNABORTED. Which really doesn't mean more than "connection was aborted". You have to be a bit careful about the "your host machine" part of the phrase. In the vast majority of Windows application programs, it is indeed the host that the desktop app is connected to that aborted the connection. Usually a server somewhere else.

The roles are reversed however when you implement your own server. Now you need to read the error message as "aborted by the application at the other of the wire". Which is of course not uncommon when you implement a server, client programs that use your server are not unlikely to abort a connection for whatever reason. It can mean that a fire-wall or a proxy terminated the connection but that's not very likely since they typically would not allow the connection to be established in the first place.

You don't really know why a connection was aborted unless you have insight what is going on at the other end of the wire. That's of course hard to come by. If your server is reachable through the Internet then don't discount the possibility that you are being probed by a port scanner. Or your customers, looking for a game cheat.

Could it be something in a script in your ARC project? I've found that if I send a command through the Uart port that's wrong, not having the target device powered up or not initializing the port first I will get a disconnect and need to reboot the EZB. I've never used a camera with EZB but have heard about a lot of issues with bad commands and connections causing issues. Can you recheck your connection, camera cable and run a new, clean project to see if you still get a disconnection?

Sometimes starting with a clean project, known good working devices and wiring will at least rule out problems with your setup and then you can look at Windows and your Wifi. Sectionalize to troubleshoot, start at the beginning and work back to the end. Power, structure, devices.

EDIT: also try disabling your firewall and antivirus.

Hardwire the ezb