You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 2 spindles, one PWM and the other is via ModBus VFD. For some reason, there is a single set of parameters (speed, frequency etc) which affects all spindles. This doesn't seem right. For example, my PWM spindle needs a speed settings of 0-1000, while my Modbus spindle needs 1200 to 24000 rpm. There really needs to be dedicated settings for each spindle.
The text was updated successfully, but these errors were encountered:
There really needs to be dedicated settings for each spindle.
Nope, RPM range should be read from the VFD, like this, and the VFD drivers that currently do not should be updated.
If settings were to be added for VFD drivers then the setting values has to be transferred to the VFD, and currently I do not have any to test against.
Ah, OK. So VFD/modbus spindles don't use the rpm setting in grblhal, only the PWM spindle? I could have sworn that changing those parameters affects the speed of my vfd spindle as well. My vfd is HY type connected over modbus. My other spindle is a laser that I believe requires 0 to 1000 rpm setting.
Which version are you running (build date in the $i output)?
If a relatively new version $spindlesh can be used to output details about the spindles, min/max RPM is output as the two last values for active spindles.
For VFDs the reported RPM range is taken from $30 and $31 initially, and changed to the actual values after reading min/max from the driver.
I have 2 spindles, one PWM and the other is via ModBus VFD. For some reason, there is a single set of parameters (speed, frequency etc) which affects all spindles. This doesn't seem right. For example, my PWM spindle needs a speed settings of 0-1000, while my Modbus spindle needs 1200 to 24000 rpm. There really needs to be dedicated settings for each spindle.
The text was updated successfully, but these errors were encountered: