I am using the latest gSender and the modvfd plugin for spindle.
It seems to be working at controlling the spindle properly from the console, and the slider also controls the spindle at (I believe) the correct speed.
The issue is that the slider shows a range of 10k - ~40k?, although my spindle is configured for 3k-16k. I canât drag the slider beyond my configured max, but that max is less than half way along the slider.
@marcoose Iâd check that youâre actually on the latest version which is 1.5.4, since otherwise the spindle dropdown shouldnât say âDefault Spindleâ it should say âMODVFDâ. If you change the toggle to the correct one, then the range should become correct too
Well shoot⊠I would have sworn I was on the latest, but it was 1.5.2. Iâve since updated to 1.5.4, and now the âDefault Spindleâ does say âMODVFDâ.
Outside of that, though, I seem to have the same issue with the slider. It goes from 10,000 at the lowest, to 18,000 at the highest, which is less than 1/2 way along the slider.
I was too new to post more than one picture before, but here are my settings;
Itâs just a minor display issue right now, as setting the speed from the console or a gcode program works fine. I donât really expect to use the slider for any ârealâ purpose beyond rare manual tinkering/testing.
I spent a good amount of time looking at this issue trying to help someone on the FB group. Here is what I have deduced after a fair amount of testing. In 1.5.4, no matter what I set the minimum rpm to in gsender or on the vfd, the slider will not go below 9000 on my install. The person I was trying to help was 10000. It is an open question to me as to whether the SLB/Gsender is polling the vfd for itâs minimum frequency. I believe I changed my min on the vfd to 10000 and the slider range changed but I canât be sure. There was a lot of things going on. I decided to compare to 1.4.11. In that version the min on the slider was whatever the min rpm was set to in the slb firmware and the min in the program options had no effect on the slider no matter what it was set to whether it matched the firmware setting or not. I agree it is just a display issue as M3 works down to whatever the min is set to.
Weâve since made some more updates to the 1.5.7 release that should better address this issue if @marcoose or @Kerryh2012 you can update and let us know
Currently my spoilboard is covered with parts for a CNC plasma build. I will try to verify the fix sometime this weekend.
1 Like
Itâs fixed in 1.5.7 as far as I can tell 
Thanks!
2 Likes