Jufe-384 Exclusive

The controller stores the last 256 fault events in a circular buffer. Use the Web UI → Diagnostics → Fault Log page for a quick visual overview.

Once I have those details, I’ll craft a solid, tailored guide that hits exactly what you need. Looking forward to your clarification! JUFE-384

| Symptom | Likely Cause | Diagnostic Step | Remedy | |---------|--------------|------------------|--------| | | Power supply absent/incorrect polarity | Measure voltage at the DC‑IN pins (should be 24 V ±10 %). | Re‑connect correct supply, add fuse if missing. | | Motor stalls, encoder counts frozen | Driver over‑current protection triggered | Check driver fault register via controller.read_faults() . | Reduce load, increase current limit, verify wiring. | | Ethernet timeout | IP conflict or cable fault | Ping the controller IP; use a known‑good CAT‑5e cable. | Assign a unique static IP or enable DHCP. | | Unexpected jitter in position | Encoder ground loop or EMI | Observe encoder signal on an oscilloscope; look for noise spikes. | Use shielded twisted pair, add ferrite beads, improve grounding. | | E‑stop does not halt motion | E‑stop wiring polarity reversed | Verify E‑stop logic in firmware ( controller.set_estop_polarity() ). | Re‑wire or change polarity setting. | | Firmware update fails | Bootloader not entered (USB/ETH not recognized) | Hold BOOT button while powering on, then reconnect. | Ensure correct boot mode; use the provided bootloader utility. | | Fault log fills up quickly | Repeated over‑temperature or undervoltage events | Read fault log ( controller.read_fault_log() ). | Check ambient temperature, improve cooling, verify supply regulation. | The controller stores the last 256 fault events