It sounds like you're experiencing a disconnection issue with your EZ-B v4 controller when running actions that heavily involve the SSC-32U servo controller. Here are a few steps and checks you can perform to troubleshoot and potentially resolve this issue:

1. Power Supply Check: Ensure that your power supply is adequate and stable. Insufficient power can cause the EZ-B v4 to reset or disconnect, especially when multiple servos draw high current simultaneously. Verify that your power supply meets the voltage and current requirements for all connected devices.

2. Overheating: Check if the EZ-B v4 or any other component (like the SSC-32U) is overheating. Overheating can lead to performance issues or disconnections. Ensure that your setup has proper ventilation and consider adding additional cooling if necessary.

3. Cable and Connection Check: Inspect all cables and connections for any signs of damage or loose connections. A poor connection can cause intermittent disconnections. Ensure that all connections are secure.

4. Firmware and Software Updates: Make sure that your EZ-B v4 firmware is up to date. Also, ensure that you are using the latest version of ARC. Updates can resolve bugs and improve stability.

5. USB Connection: If you are connecting via USB (for initial setup or other reasons), ensure that the USB cable is in good condition and securely connected. USB ports can sometimes be a source of connection issues due to power saving settings on the PC. Check your computer's USB power settings and disable any settings that allow the computer to turn off the USB port to save power.

6. Script and Command Review: Review the scripts or commands that are running when the disconnection occurs. Look for any commands that might be causing excessive load or incorrect signals being sent to the servos.

7. Log and Error Messages: Check the ARC console for any error messages or logs that occur around the time of the disconnection. This information can provide clues about what might be causing the issue.

8. Isolation Test: Try isolating the problem by reducing the number of active servos or simplifying the actions. If the disconnections stop, gradually add more complexity to identify the threshold or specific action causing the issue.

9. Electrical Noise and Interference: Consider whether there might be electrical noise or interference affecting your setup. servo motors, especially in large numbers, can generate significant electrical noise. Ensure that wiring is neat and that signal wires are kept away from high-current power wires.

If after these checks the problem still persists, you might want to consider reaching out to the community forums or support for more specific guidance, especially if there might be a hardware fault with the EZ-B v4 or SSC-32U controller.

Does the EZB just disconnect from WIFI or does it completely shut down and reboot?

If it reboots then it's probably browning out due to current draw from the servos. When a servo starts to move it pulls a lot of current and can "starve" the EZB. The solution to this is to run the power wires directly to your power source and not to the EZB. Also make sure your power source can provide enough amps to your servos and the ezb at peak load.

A brown out will cause the WIFI to disconnect also. If the EZB is not rebooting you may have a WIFI issue. Make sure you have a strong signal and a uncluttered channel. A lot of traffic on your channel (like other household devices and other networks using the channel) can cause disconnects. Use a WIFI analyser app on your phone to find a low use channel and change the EZB over to that one.

Check out the Support sections of Synthiam and also RZ Robot for more info on overcoming these issues.

Dave, you've provided some excellent insights into troubleshooting the disconnection issues with the EZ-B v4 controller. Here's a summary and additional advice based on your suggestions:

1. Power Supply Check: As you mentioned, a brownout due to insufficient current supply when servos are activated is a common cause of the EZ-B v4 rebooting. Ensuring that the power supply can handle peak loads is crucial. It's recommended to use a dedicated power source for the servos that can provide adequate current without relying on the EZ-B's power output.

2. Direct Power Connection for Servos: Connecting the servos directly to the power source instead of routing power through the EZ-B can help prevent voltage drops that lead to brownouts. This setup ensures that the EZ-B only handles signal processing and not power delivery.

3. WiFi Stability and Strength: If the EZ-B is not rebooting but merely disconnecting from WiFi, checking the WiFi environment is essential. Using a WiFi analyzer to select a less congested channel can improve connection stability. Ensure the router is within a good range and there are minimal physical obstructions that could degrade the signal.

4. Firmware and ARC Updates: Keeping the EZ-B firmware and ARC software up to date can help resolve known bugs and improve overall stability.

5. Network Settings: Adjusting your router settings to prioritize traffic to the EZ-B or setting up a dedicated IoT network can reduce WiFi disconnections due to network congestion.

6. Documentation and Community Support: The Synthiam support section and community forums are valuable resources. Engaging with the community can provide insights from other users who might have faced and resolved similar issues.

By following these steps and considering both power management and WiFi connectivity, you can enhance the reliability of your EZ-B v4 setup. If problems persist after these adjustments, it may be helpful to consult with Synthiam support or consider potential hardware issues with the EZ-B or connected components.

If there is indeed a problem with browning out the power supply, one trick you can try is to do a sequential initialization of the servos. This way you can prevent the combined in-rush current of multiple servos from browning out the supply. The idea is that you would initialize each servo one at a time (it can be quickly) so the power supply only sees the inrush current of one servo rather than them all combined (1 Amp versus 5 Amps).

This EZ-Script example initializes each servo to 90 degrees with a 100mS delay between them:

$pos = 90
$delay = 100

servo(d0, $pos)
sleep($delay)
servo(d1, $pos)
sleep($delay)
servo(d2, $pos)
sleep($delay)
servo(d3, $pos)
sleep($delay)
servo(d4, $pos)
sleep($delay)