Board works, now struggling with interference, as soon the spindle starts, everything goes haywire. Trying some twisted pair / shielded network cable but until now that doesn’t make much difference. As soon as the spindle starts, I get error messages and my laptops touchpad starts acting weird.
The cheaper the spindle the worse the EMI. Last I heard it was more of a grounding issue than anything. Ground the spindle body as well as using shielded control cables. Run the spindle wires completely separate of any endstop or stepper wires. Ground the power supply
I was curious about the speed_map so I looked it up in the FluidNC wiki. Glad I did as that is really well explained there. I’ll be perusing that a lot as more and more machines are switched over. Well done.
What error messages?
Are you using the laptop to control over USB?
As a troubleshooting measure, what happens if you only connect to the Jackpot over WiFi and use the GUI to control things? Better/worse?
Second UART shouldn’t be a problem if it’s not a second input console, so RS485 should be okay.
And even when it is a second input console (or pendant) it’s relatively minor unless you turn up the debug messages. The debug messages get multiplied across all the consoles and with the TMC2209 status it really adds up. The next FluidNC release will decrease the TMC2209 debug messages so it will be less of an issue in the worst case.