- Posts: 111
- Thank you received: 0
Spindle speed scaling
Please Log in to join the conversation.
there are multiple
and see if the settings is 0-10V or 0-5V as it can also be a case
Please Log in to join the conversation.
Please Log in to join the conversation.
I have an issue now with the at-speed pin on the gs2-vfd component. It doesn’t ever turn on. I figured that maybe I’m breaking something by scaling the speed but I also tried it without scaling the speed and it still won’t turn on. Has anyone gotten it to work?
Please Log in to join the conversation.
The code is here:
github.com/LinuxCNC/linuxcnc/blob/master...comps/gs2_vfd.c#L392
I would have expected a bit of "fuzz" on that comparison.
Do you see the freq-cmd and freq-output HAL pins becoming exactly equal?
Please Log in to join the conversation.
At-speed sometimes turns on immediately, sometimes after several seconds, and sometimes not at all.
Sometimes the vfd stops responding altogether and I need to cut the power to make it stop if it’s running. In order to get the communication up again, I need to unplug the usb-rs232 converter and restart Linuxcnc. I’ve tried two different usb-rs232 converters and they both behave the same.
I’m thinking its either an EMI or a ground loop issue. Or maybe something is wrong with the VFD.
Please Log in to join the conversation.
- tommylight
-
- Away
- Administrator
-
- Posts: 22010
- Thank you received: 3
Please Log in to join the conversation.
tommylight wrote: You can try lowering the communication speed of the RS232, but it is much more advisable to check the grounding and shielding.
Yeah. I assumed that the negative pin on my usb-rs232 converter was grounded and used that to ground the shield on my cable.
It’s not:
Attachment not found
And grounded:
Attachment not found
The noise all seems to be coming from the vfd.
Please Log in to join the conversation.
andypugh wrote: I wonder if at_speed actually works?
The code is here:
github.com/LinuxCNC/linuxcnc/blob/master...comps/gs2_vfd.c#L392
I would have expected a bit of "fuzz" on that comparison.
Do you see the freq-cmd and freq-output HAL pins becoming exactly equal?
If you would, could you direct me to how I would modify the maximum RPM to something that works for me, instead of using the scaling hack. I could just change that number before I compile it as I am currently running 2.8 compiled from source. How would I then handle future upgrades without breaking my build?
Please Log in to join the conversation.
Please Log in to join the conversation.
