I didn’t read everything, and am trying to get up to speed on what to help test/verify when board arrives today hopefully.
Is AI’s summary of this chat close?
JackPot V2 – Issues Summary (Past Month)
| Status | Problem | Cause (Suspected/Confirmed) | Fix (Planned/Attempted) | Workaround |
|---|---|---|---|---|
 Open |
Pendant causes boot/current issues | Pendant pulls on strapping pins (GPIO12/15), protection chip interaction, or boot sequence conflict | Testing pull-down resistors, bypassing/removing chip, scope analysis | Run board without pendant at boot; add pigtail for isolated testing |
 Ongoing |
High current draw (1.2A vs 0.6A idle) when pendant connected at boot | Suspected protection IC drawing load, possibly UART/power sequencing conflict | Hot-air removal of suspect chip + jumper bypass tests | None yet; avoid pendant connection during boot |
| Ongoing |
Macros don’t run, pendant disconnects (FluidNC 3.9.8) | Firmware bug in FluidNC pendant integration | Report upstream / test other firmware | Don’t use macros with pendant; run commands manually |
| Ongoing |
WiFi AP mode unstable (Windows/Ubuntu drop connection due to “no internet”) | OS network managers auto-switch away from captive-portal style AP | None yet (possible firmware or OS config tweak) | Use a router/hotspot with internet; disable auto-switching in OS |
 Clarified |
Antenna options confusion | Misunderstanding: V1 already supports external antenna, V2 only needed one style | Dropped redundant antenna variant | No action required |
| Resolved |
Diag pins looked unprofessional, not useful | Initially left in for StallGuard tests, but proved unreliable | Removed in latest design | N/A |
Summary:
Boards are electrically sound, but pendant integration + FluidNC firmware are the main blockers. Boot/power stability and macro handling are not reliable yet. WiFi usability still frustrates some users. Hardware tweaks (removing diag pins, better copper, antenna simplification) are already implemented going forward.