[vmax549]

Teh thing I have seen with HY type VFDs is they could be anything pretending to be a HY. On the zone is an example now of a counterfit HY vfd that has different internals(non HY) but was sold as a HY (;-) In that example it did not even have a Comport to talk to (;-)

as to teh User number range THAT is going to be an on going problem. No Matter what number you pick someone will possibly pick teh same number after all there are only 1000 possible numbers .

I can garrantee that I have already walked over everyones number ranges with teh experiementing I have done with Macros.MacroWizards,Plugins,MacroLoops.

I have even walked all over some of my OWN numbers may times forgetting what I had already used.

I have come up with several ways around it BUT without some standards being developed and used that to is worthless (;-)

One thing you may want to check on is CAN teh HY ouput teh actual RPM values in any form ??. Pulses. freq,values ,analog ???

(;-) TP

[Dan911]

One thing you may want to check on is CAN teh HY ouput teh actual RPM values in any form ??. Pulses. freq,values ,analog ???

(;-) TP

Using a RS485 connection to receive RPM from the HY VFD is to send a function read RPM command and it returns the current running frequency. I monitored the 2 Mach3 plugins and Spindle Talker and all use this only method. I seen it as a waste of resources to have the VFD and plugin continually reading and writing to receive the same Frequency that it was set to. The only gain was to see the frequency(RPM) accelerate to its set speed and decelerate when shutting down. That's why I aborted implementing RPM. If the spindle was ever under load and actually slowed RPM the HY VFD will never show this because it still going to be sending set frequency.

What was needed is to see your RPM when using spindle override, because the Sset field wouldn't change. That's what the Sact field shows.

Sorry for making an essay out of a sentence...lol

Dan