There’s two places to disable the battery monitor

• the web interface for the iotiny. That disables the alarm on startup

• the connection control in arc. That disables the alarm when ARC connects

I always disable the battery monitor in the web interface. That keeps the EZB or IoTiny from saying the warning completely.  I found that If I only disable the battery monitor in the connection control in ARC that warning will happen until ARC boots and stops it.

When you say the IoTiny still "cuts out" do you mean they both still disconnect or do they just not respond? Hopefully by disabling the warning the issue will resolve like Jeremie said.

I had a connection set up much like yours except: Port 0 : IoTiny configured in AP Mode as master Port 1: EZB via USB Port 2: EZB configured in Client Mode connected to Mater IoTiny

This worked good for me but when I added Port (Connection) 3 in ARC with another EZB in Client mode connected to the Master IoTiny in AP mode I had problems. The IoTiny couldn't keep track of the the Two EZB's connected to it. When ARC would start and connect, the EZB's listed in the port (connection) slots they would always be in the wrong place. I tried switching the IoTiny with one of the EZB's, making the EZB the Master in AP mode I had the same problem.

I wanted to get My robot off my WiFI home router so I ended up connecting all EZB's and the IoTiny through USB to the onboard computer. Much better and simpler. Is it possible for you to attach all your units to USB connection?

Thanks guys! It was the battery monitor setting in the web interface for the Tinys. Turning off the battery monitor in ARC didnt help, but the internal one solved it.

Sorry for continually rebooting this thread. But the problem remains. I can get about 45 seconds of servo commands before both IoTinys disconnect. Both are getting 6V at the terminals. Both have battery monitor off in ARC and internally. I sent another Diagnostic report. Is it possible its not getting enough current?

From my understanding, I am unable to connect the Tinys via USB? The Tx/Rx option apparently only works for the EZ-B, and not TIny, apparently?

@elektrophunktronic

1. The battery monitor on both sides matters, if you don't adjust in on the ARC side you will see unresponsiveness and the low battery warning as well.

2. Brown out (not enough supply current which causes voltage sag and reboots the electronics) is very common in robotics. We recommend using a LiPo battery or high current (3Amps or greater) 7.5V or 5V power supply. You can also stagger servo movements with a small delay which helps combat inrush current.

3. Correct the IoTiny doesn't have the wired option that the EZ-Bv4 does

Woops, Sorry for the misinformation. I somehow forgot the IoTiny cant connect to the computer through USB. Because of this I actually removed the IoTiny out of my robot. I rerouted control of the devices that were connected to it to an existing EZB already in use in the robot. Even though I have more wires where I didn't want, things are simpler overall.

I hope you find the issue. This sounds like a current issue. The servos may be starving the IoTiny and browning it out. What kind of power supply are you using to power you robot? In your OP you say power supply. Is it a Wall Wart or a good switching power supply? It needs to be rated for the peek amp draw of all your devices added together plus about 25% more for overhead? Stay away from the Wall Warts. A good power supply needs to supply enough current when the Servos start moving along with all the other devices needs that are on that circuit.  Are you powering the servos through the IoTinys? If so run your power around the IoTinys to the servos, straight from the power supply. Aviod powering power hungry motors and servos directly from EZB's and IoTiny's.