I've hit a brick wall getting my vfd to communicate through rs485 to the xpro v5. Can't figure out how to do it through pwm. SPAM tech support has a language barrier. I tried github, posted my problem, tried the solutions there: set the power supply to 220 (no change) swapped the wires (went from only red to only green lights) upgraded to fluidnc (that was a mistake) resistors everywhere (no change) ferrites everywhere (no change) grounded everything (no change) xpro in a grounded case (no change) after trying several commands to get the spindle going openbuilds control just tells me [MSGBG: VFD setState:0 SpindleSpeed:0] [22:51:38] [ ] [MSGBG: RPM:0 mapped to device units:1] [22:51:39] [ ] [MSG:INFO: VFD Queue Full] spark concepts hasn't seemed to respond to anything on github in months and neither have they responded to my emails. So unless one of you wonderful people has an idea of what to fix I'm about to return this xpro and get the blackbox32 but it's not something I want to do if there is something else going on that it still won't work with the blackbox. Any thoughts?
The Blackbox X32 uses the simpler 0-10v control system (instead of modbus/rs485) which is usually a lot easier to configure. See docs:blackbox-x32:connect-vfd [OpenBuilds Documentation] 0-10v is industry standard, but refer your VFDs manual on how to set Run / Freq Source to Voltage, set that as 0-10v (some has jumpers to switch between 4-20mA, 0-5v or 0-10v). Then configure Min Freq to act as protection/stop (turn off spindle if commanded RPM is less than 7200). The spindle specific VFD values are something best advised by the spindle manufacturer. Keep in mind VFDs create a lot of EMI: docs:blackbox-x32:faq-emi [OpenBuilds Documentation] You will definitely want to use Xtension Limit Switch Kit to combat some of that EMI A simpler alternative exists as well: RoutER11 CNC Kit (much less complicated to get going, way less EMI, no need to work through a book of badly translated parameter instructions)