-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kinda vfd support #501
Comments
No, the difference is if a specific board has support for the UART (serial) port required.
More or less so, if there is a standard many do not adhere to it.
If you can use the MODVFD driver, which is configurable via settings, then no. If not a new driver has to be added. |
Thanks! Is there any manual/tutorials on how to configure MODVFD? Settings - you mean, recompile firmware or those $462-$471 parameters listed on https://github.com/grblHAL/Plugins_spindle ? |
Not that I am aware of, except that it has been adapted from LinuxCNC so this thread may cointain some pointers.
I think MODVFD could be used since command codes 3 and 6 are used, settings $462-$471 has to be set up to match the VFD. |
When I look here https://github.com/grblHAL/drivers?tab=readme-ov-file - specifically, at spindle modbus support line - there's a bit of confusion for me. Is it done artificially, or is there any fundamental reason for a firmware for an stm32f407 or stm32f411 not to support modbus spindle control?
Then, there's another question - on choosing the right option in web-configurator. Initially I thought they (vfds) are using the same application-level protocol, so to say, and a common instruction set. But after looking through that part of code it looks like implementation is different for each make. I am using the KD200-00220S2 from Kinda. Does it mean, I have to provide a pull request to get it supported by firmware?
The text was updated successfully, but these errors were encountered: