[ Vfdmod ] An easy VFD control over MODBUS RTU

I have found several problems with this component. First, it takes as feedback to the spindle the values reported by the control, but not by an encoder, for example from the spindle of a lathe, therefore the pyvcp is designed to obtain information from the readings via RS-485 but not from an encoder. external, therefore some files have to be modified so that spindle at speed is used with this feedback and not the original one. Another problem that I found is that the override control of the Axis GUI no longer responds, when the speed of the spindle is varied with this control in Axis, to vary its speed it does not respond even though the values in HAL do vary between what has been set in the ini file, the spindle speed only responds to G code commands or + or - in the Axis GUI, but not to the slider in the Axis GUI. Finally, when I controlled the VFD with +10 volts, the G96 code worked in CSS mode, now with control by 485 the speed of the spindle is always the same and the spindle does not accelerate as it does. diameter is smaller, nor does the feed increase.

Nothing is ever plug and play, why would an example config demonstrating vfd use include encoder feedback? You need to adapt it to include your encoder.
Linuxcnc tells the vfd what speed it wants so if its not getting that right in g96, you may not have set the spindle up correctly
Ref  linuxcnc.org/docs/stable/html/man/man9/m....html#SPINDLE%20PINS

I don't have an encoder or lathe, Everything works perfectly for me but I migrated to qtdragon long ago.
I know I had problems initially because I did not fully understand how to set up the spindle.

On my VFD voltage and rs485 control are mutually exclusive.

  The spindle.0.speed-in pin, which is necessary to use G96 (constant surface speed) and G95 (feed per revolution) modes, is connected to my HAL through the spindle encoder at:
net spindle-velocity-feedback-rps encoder_SPD.velocity => spindle.0.speed-in.
The custom.hal file that is automatically generated by Vfdmod connects the vfdmod pin vfdmod.spindle.rpm-in to splindle-cmd-rps. I don't know if I'm wrong but the problem would be that the spindle.0.speed-in pin is not connected to splindle-cmd-rps.
I attach my hal files. and custom hal.

Yes, the config creates the signal and its up to you to connect it to the right pin in your hal
You are almost on the right track except vfdmod supplies revs per minute and linuxcnc requires revs per second.
The solution is to use the scale component to scale rpm to rps
linuxcnc.org/docs/stable/html/man/man9/scale.9.html
I do this in a custom gearbox component so don't have an example

The VFDMOD component does not work with g code G96. When a code that contains that G code is executed, it automatically writes to the vfdmod.speed-in PIN the value declared in parameter D of G96. While in the other pins the speed change is reflected, which indicates that CSS is working. I think that since this component is designed for VDF of milling machines where lCSS is not used, for that reason it is not very useful when used to control the speed of a lathe motor. In the photos you can see that the commanded speed is different from the commanded output of the component, which always adjusts it to the maximum of parameter D of G96. I don't know if the same thing happens with the MB2HAL component.

       

I'm not convinced vfdmod won't work. Linuxcnc is controlling the spindle speed so it does not care about G96 or what kind of machine you have or even how you control your VFD. A spindle is a spindle. As long as your X axis is touched off on the centre line of the spindle, G96 should work if your config is correct.

I found this thread helpful when I set up mine. Please review the first post on page 2
forum.linuxcnc.org/qtvcp/45552-need-help...-qtdragon-hd?start=0