Hi there,

Thanks for reaching out about your JD robot connectivity issues with your EZ-B v4. Let’s break down the two concerns:

1. Red LED on the JD Robot

• Normal vs. Fault Indicator:
  On JD robots, a red LED (especially in the top left corner) isn’t typically part of the "normal" powered-on state. Many JD units display other colors (or no LED) when in a standard operating mode. A persistently red LED may indicate that the robot is reporting a fault condition or is in a standby/error state.

• What to Check:
  Robot Manual: Consult the JD robot manual (if available) or the EZ-Robot product support pages for any mention of LED status indicators.
  Error Codes/Behavior: Sometimes, a red LED might be accompanied by error messages or abnormal behavior in ARC. Note if there is any additional information on screen or if any skills (like the JD robot skill) provide LED/error status feedback.

2. EZ-B v4 Disconnecting from ARC

Disconnections after a few seconds can be due to several factors. Here are some troubleshooting steps:

• Power Supply Issues:
  Current Draw: Make sure your power supply is rated to handle both the motors/servos and the EZ-B board. High current draw (especially during startup or heavy movements) might cause a brown-out triggering a disconnection.
  Battery Monitor: Check the battery monitor settings in ARC (Settings > Battery Monitor) and consider overriding or adjusting the minimum voltage if your power source is known to be stable.

• WiFi Connection & Interference:
  Signal Strength: If you’re connecting wirelessly, ensure that your WiFi channel isn’t crowded. Tools like the WiFi Scan Tool (available on the Synthiam website) can help assess interference.
  Alternate Connection: For diagnostic purposes, if possible, try connecting via USB (or a different connection method) to see if the issue persists.

• Wiring and Loose Connections:
  Confirm that all cables, especially those connecting the JD robot parts and the EZ-B v4, are secure. Intermittent connections can cause periodic dropouts.

• Diagnostic Information:
  Utilize the Connection Diagnostic skill in ARC to review verbose logs. Look for timeout messages or any errors that correspond with the disconnection event.
  Are you seeing any error messages or unusual log entries in the diagnostic window?

Next Steps

1. Investigate the LED:
   Verify with JD robot documentation or any available online support information if the red LED indicates a specific error.
   If the documentation isn’t clear, consider if the LED behavior aligns with other symptoms of disconnection.

2. Check Power and Connection Stability:
   Examine your power setup to ensure the EZ-B is not browning out.
   Test on a more stable connection method if available.

3. Review Diagnostic Logs:
   Use the Connection Diagnostic skill to capture logs during the disconnect. This information can point to whether a communication timeout or another issue is at play.

4. Follow-Up:
   Let me know if you notice any specific error messages within ARC or any additional symptoms.
   Are you using WiFi or a USB connection for your EZ-B v4? This detail will help narrow down if the issue is interference related.

Feel free to ask for clarification on any of these steps or provide additional information. I’m here to help you get your JD robot running smoothly with ARC!

For more information on troubleshooting connections, you can also review our EZB Disconnecting documentation.

Looking forward to your update!

@athena

thank you i found it myself for ones .

the init script was not correct . i had change the camera settings to of . i removed the hole camera setting in the script .

Hi Nomad_6R,

That's great news! I'm happy to hear you tracked down the issue with the init script and resolved the camera settings problem.

If you need any further assistance or run into any other questions while working on your project, feel free to ask. Are there any other customizations or skills you’re looking to adjust or implement in ARC?

Keep up the great work!