[ Vfdmod ] An easy VFD control over MODBUS RTU

It seems communication settings wrong (error code 110), check parameters in RS485 group. And please show your ini file here.

Attachment m INI file and the DEBUG serial USB

In debug output I see everything is fine, there is no modbus errors, so communication MUST be established and error count MUST be zero. But in your previous screenshot error count is not zero, is that screenshot was made with different (wrong) config?

If connection established (I guest it is so) but start/stop commands are not working, then check signal names in main HAL file:

Are these signals exist?

I see someone changed the title of this topic to "[ Vfdmod ] not control". Is it joke or I did something wrong? How can I fix it?

* updated *
Fixed by itself after my reply! Probably some kind of bug...

Someone else changed the subject when they replied, but when the original poster replies it goes back to the original subject.
It has been mentioned here several times not to change the subject when replying.

It is not clear to me. I am enclosing my hal file for you to verify.
Another question: do these instructions go in the main hal file or custom.hal:?
net spindle-speed-cmd => vfdmod.spindle.rpm-in
net spindle-at-speed <= vfdmod.spindle.at-speed
net spindle-cw motion.spindle-forward => vfdmod.spindle.run-forward
net spindle-ccw motion.spindle-reverse => vfdmod.spindle.run-reverse
Can you post your main hal file for comparison?

When checking again, and executing a g code, there is control of the VDF, that is, it starts adjusting the speed and when it finishes executing the g code, it stops. But it is not possible to control it from the MDI.

COFHAL wrote: It is not clear to me. I am enclosing my hal file for you to verify.
Another question: do these instructions go in the main hal file or custom.hal:?
net spindle-speed-cmd => vfdmod.spindle.rpm-in
net spindle-at-speed <= vfdmod.spindle.at-speed
net spindle-cw motion.spindle-forward => vfdmod.spindle.run-forward
net spindle-ccw motion.spindle-reverse => vfdmod.spindle.run-reverse
Can you post your main hal file for comparison?

Where is no strong instruction how HAL pins should be connected, because depending of LinuxCNC version (I mean Stepconf & Pncconf version when you created your machine configuration) HAL pin & signal names can be different, what's why my HAL file may be useless for you.

Ok, I guess I know what you should to try:
1. Find and uncomment this line in your main HAL file:
2. Add to your custom.hal these lines:

Documentation moved to Github Wiki: github.com/aekhv/vfdmod/wiki

DEB packages also moved to GitHub: github.com/aekhv/vfdmod/releases

P.S. Build for Armbian Buster (armhf) added to releases, so vfdmod is ready to work with Orange Pi ! :woohoo: