Post by Sebastian Kuzminsky Post by Sebastian Kuzminsky
No, .base-freq was an Out pin, it got read from the VFD and
reported to HAL, but never used in the hy_vfd driver.
Did the OP have some Hal circuitry that depended on it maybe?
He appears to want to set it from HAL. (Because he has one VFD
connected to either of two motors, I think for either a low speed
(50Hz) or high speed (400Hz) spindle.
Many VFD motor-configuration registers, including PD005 "Maximum
Operating Frequency", can be set by hy_vfd at startup based on
command-line arguments. None of them can be changed at runtime via
The little booklet that came with mine, seems to assume it has a working
rs-485/22 interface. There are sequences of data that could be sent
thru that interface, to select the PDxx register and then write to it.
I'd have to assume that this could be done in real time since I can
manipulate it while its running the motor from its own front panel. That
is not a hal job unless hy_vfd can access a file for all that data, and
the hal pin switched then would cause it to (re)load one of the two
profiles to run the given motor. 2 pins would allow 4 profiles etc.
However, he would be taking a high chance of destroying the vfd when
switching motors while its live since they do NOT like loose connections
or switches whose conacts bounce on their outputs, and they ALL do. And
if he is actually switching the motor in its mounts on the same machine,
I'd think he would be far safer by just having two configs, loading the
one for that motor. Thats only a small slice of time compared to
physically switching out the motor itself.
There's a guy named Murphy watching such things carefully, just waiting
to stick out a foot and trip us up. No use tempting him.
Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>