Before you try again.

leave EZ-B unplugged for now.

Open ARC.

In the Connection object, click on the gear icon. In the next dialog, click on the settings button on the top left. Under Battery Monitor Settings, click the Enable Battery Monitor Override, then un-check the "enable battery monitor" check box next to EZB #0 (or all 5 of them).

Save. You will see a warning about selecting this can damage LiPos. Click Yes.

Now, up in the top ribbon, go to the options tab. Far left item, select Debug. The debug window will open. If not already checked, check the Always Show checkbox. Now debug won't close after displaying.

Now, plug in the EZ-B and try to connect. Note that the low voltage warning disable is project specific, so save this project (assuming you get working again).

Note: the RALink WiFi issue with some Compaq and HP computers is solved in recently shipped EZ-Bs, so if you bought in the past 6 months, unlikely to be an issue, and since you have connected successfully in the past, definitely not an issue.

Are you running Avast Internet Protection? The Avast firewall will cause EZ-Bs to disconnect. You either need to disable it, make ARC an exception, or make port 23 an exception (other firewalls could also be an issue, but virtually every complaint I have seen so far has been Avast except for one user who when prompted by Windows firewall to make an exception said no, and then needed instructions on how to change their mind).

Alan

Plugging in a different power supply: 12V18A...

Turning off ARC. Powering up EZB. Green flash LED, chimes, Blue Flash LED.

Connecting to Windows 10 WiFi on Compaq Presario CQ41 (The computer I've been using for messing around with the EZB for months).

Windows says connected but EZB still flashing Blue...

Opening ARC. Clicking Connect on 0...

Clicking Always show on green writing window...

Connect button has become green Disconnect button. Green writing says Battery Monitor Voltage is set to 7 and battery protection is true, setting i2c rate: 100000, Connected.

Clicking the cog to see if the settings actually reflect the green script...

Cog>Settings. Yes, as I suspected, the settings show that battery monitor override is NOT selected. This software is massively flawed. Clicking the checkbox to test green writing...

Enable Battery Monitor Override Now checked. Altering Min Voltage on all EZBs down to 3v from 7v...Save button.

'WARNING! You have selected a battery monitor voltage that is lower than our recommended voltage of 7v. Changing this feature will damage LiPo batteries which may cause an explosion. Are you sure?'

Yes. Idiots. Hobby servos are mainly rated between 4.8 - 6v worldwide. Look it up.

The green script confirms my ignorance with its warning and says they're all set to 3v now.

Clicking project history item 'JD'...

A ton of writing appears in the script area, red light goes on EZB with blue flashing light. Disconnected. Just like that. 12V with no servos connected. The green writing says voltage limit is now 7 and set to true. I didn't change it back. It says it timed out as well. Oh, and it tells me the camera is disabled.

Alan, I did what you said but the EZB cannot connect while the red button is lit. It must be unplugged and plugged back in again every. single. time. I will read the rest of what you wrote now.

PS Saving projects only results in error messages when I try to load them, and voltage is set to a contrary reading to the settings if you follow my methodology. Unless there's been a software update, this program is clearly faulty.

Firewalls can be inspected later, clearly not the reason everything stopped working since this morning. No Avast, No Virus protection. This is a dedicated EZB laptop. My main one is a Macbook Pro (on which I'm typing).

did you read my question about Avast? What did the "green writing" say? Copy and paste it here.

Note: Insulting the design of the software, which works for 10's of thousands of users and has protections built in that prevent safety issue with 7.4v LiPos which are used by the vast majority of users (along with EZ-Robot 7.4v HD servos) , is not going to make you friends here..... Are there flaws, sure, but the CEO of the company and the designer of the software participates in the forum, and fixes things that we point out are broken, so take a chill pill, answer the questions asked of you, and there are a bunch of us who will help troubleshoot. Continue complaining about "idiots" and you will quickly be ignored.

Alan

What kind of pill would you recommend in this situation? This is my business that's on the line. Stress causes premature death. etc. Let me complain, I have a right. I'm the downtrodden in this situation, not the accused. Claiming thousands of customers is not proof of a bug-free product. It needs to be fixed. My foot's caught in a bear trap and you're beating me with a bat for swearing.

EZB 0: 
EZB 1: 
EZB 2: 
EZB 3: 
EZB 4: 
Attempting connection on 192.168.1.1:23
Connected to 192.168.1.1:23
Reports EZB v4 OS With Comm 1
EZ-B v4 ID: 58-54-0-0-48-255-57-56-55-38-38-38
Setting battery monitor voltage: 7
Setting battery protection: True
Setting i2c rate: 100000
Connected
Setting battery monitor voltage: 3
Setting battery protection: True
**WARNING: The low battery warning monitor value is set LOWER than the recommended default of 7v. Your voltage monitor set for 3v. If using the LiPo batteries from a Revolution EZ-Robot, for battery longevity and your safety we highly recommend that you change the low battery monitor back to 7v. This setting can be found in the Connection Control Config Menu.
Setting i2c rate: 100000
Object Recognition Initialized.
Camera Initialized: EZB://192.168.1.1 @ 320x240
Object Recognition loaded.
Setting battery monitor voltage: 7
Setting battery protection: True
Setting i2c rate: 100000
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.eO4EQE3BZF(Int32  , Object  )
Camera Disabled
Setting battery monitor voltage: 7
Setting battery protection: True
Setting i2c rate: 100000
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 EZ_B.EZB.tx9G6XA9AV(Int32  , Byte[] cmdData)
BbytesToExpect: 2

Received: 0 0 
Disconnected
Attempting connection on 192.168.1.1:23
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 EZ_B.EZB.tx9G6XA9AV(Int32  , Byte[] cmdData)
BbytesToExpect: 1
U
Received: 0 
Disconnected
Connection Failed: System.Exception: Controller Not Responding
   at EZ_B.EZB.nK0GoWWRVJ()
   at EZ_B.EZB.Connect(String hostname, Int32 baudRate)
Disconnected

I sure would appreciate any help despite my bad attitude about the software. I was excited about the product and I was grateful to DJ for all his help, and I know software development is hard - trust me. But I got a business to run, and I need to know if I can trust this product because I was intending to buy hundreds of units if it all works well.

edit: [typed before you followed up posting the debug window. will leave for now, but may edit or delete after I look at your previous message]

I am telling you that the way you are asking for help is going to drive away those who might want to help you. Yes, you are experiencing an issue. It is a complex piece of hardware, and complex software, and built by a startup company with limited time resources, so as a hobbyist product, you may need to work a bit, and have some patience while we try to assist in figuring out what is wrong.

We have ruled out insufficient amps because you are using high quality switching power supplies.

We have ruled out your servos because the issue occurs with none plugged in.

There are dozens to hundreds using the EZ-B on 6volts, so that isn't likley the issue, you do need to do some steps to turn off the LiPo warning (which was put in there, along with the multiple ways to force you to use the tutorials, because many users bought EZ-Robots, started using them without reading anything, and toasted their LiPo batteries or burned out their servos by stressing them beyond their tolerances. Forcing you to take the action to read about the product and turn off the alarm is both a safety issue and reduces arguments about whether abuse to the parts constitute warranty or not).

We haven't yet ruled out a firewall problem, nor have we rules out any other problems since you neither answered my question about your firewall, not pasted in the debug window results (note: use code tags when pasting the results for better readability).

You can also run a diagnostic report and submit it to EZ-B and they may be able to see something else about your computer or software that could help explain the issue you are seeing.

I find Xanax works well for stress....

Alan

To simplify the log, disconnect the camera and try again. It is hard to see what is failing the EZ-B connection when the camera connection is failing too.

I still suspect firewall (or something failed in the EZ-B itself), but there is another test we can do too.

Instead of connecting with ARC, go back to the EZ-B web page (open a browser and connect to 192.168.1.1), and go to the diagnostic page. Try to send tones and move a servo from there and see if it resets its connection.

Alan