forum.cncdrive.com

I have a small issue with controlling my Huanyang VFD with the plugin , not sure if its a setting in the VFD or something I have missed in the plugin or wrong version.

I am using Hyplugin14 v 1.0014 with Uccnc 1.2112 and I have the VFD working correctly but I have always had a issue where intermittantly it will not turn off the spindle via a G5 command in the gcode. Works 90% of the time but sometimes it fails.

I have Uccnc configured to also switch off a relay on a G5 command to shut off misting as well.

When the problem occcurs at tool change when a G5 is commanded the mist shuts off , Uccnc shows the spindle button is off but spindle is still running . I then need to manually press the spindle on and then spindle off on the screen to get the spindle to stop . When its in the middle of a tool change macro I have now added a wait for confirmation manually that spindle is actually stopped before continueing with tool change.

Is thos a known bug or is there a setting in the VFD I need to change so it sees the signal uccnc send via rs485.

Do you mean M5?

Can't help with the plugin, and haven't seen Dan post anywhere in several months.

Have you looked at the diagnostic page and checked the output for the relay to see if it's displaying the state correctly?

Last time I had my test rig running, I was using HY12, and using a relay for on/off, with no issues. But that was also with an older version of UCCNC.

Relay which controls spindle cooling on a M5 command is workling fine every time , just the M5 sent via the usb to the VFD is not activating every time - 90% of the time it works fine. doing another m5 does not seem to work , need to do a M3 then a M5 to get spindle to turn off when it happens

Relay which controls spindle cooling on a M5 command is workling fine every time , just the M5 sent via the usb to the VFD is not activating every time - 90% of the time it works fine. doing another m5 does not seem to work , need to do a M3 then a M5 to get spindle to turn off when it happens

That is the problem with using M3/M5 to turn a spindle on and off via modbus if you have an intermittent connection.....

Maybe try slowing down the communication speed as modbus should be run slower anyway (according to the original protocol specification which may in turn align with your hardware and cable etc)..... Also you may have noise affecting your transmission hence why it misses the first M5 but catches the second