VMC related HAL questions.
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
You will need to tune the PID values in the INI file.Tried a M3 S100 but It doesn't compensate at all? Am I missing something here?
Your ini file has [SPINDLE_9] Whereas the HAL is using [SPINDLE]
These need to match.
The fact that LinuxCNC starts at all with that misconfiguration makes me wonder if it is finding the right spindle.hal file.
M33.1 Does not do anything ether.
Odd. Was the spindle turning? Has G33.1 worked before? The HAL connections seem correct.
Please Log in or Create an account to join the conversation.
- thewho
- Offline
- Premium Member
-
- Posts: 128
- Thank you received: 2
Did it right after that and then I got that error message and Linuxcnc does not start.
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
Linuxcnc does not start.
At a guess that is the [SPINDLE] / [SPINDLE_9] thing.
Please Log in or Create an account to join the conversation.
- thewho
- Offline
- Premium Member
-
- Posts: 128
- Thank you received: 2

EDIT: Added Error, HAL and INI files
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
You have already loaded 3 x PID for the axes in the first HAL file.
loadrt pid names=pid.x,pid.y,pid.z,pid.s
You need to load them all at the same time.
So remove the "loadrt pid..." from spindle.hal and make the main HAL file line read:
loadrt pid names=pid.x,pid.y,pid.z,pid.0,pid.1
It is lucky that the main HAL file uses names= or there would be a lot more editing to do.
(It might have been nice to have called the spindle ones pid.v and pid.p to keep the pattern consistent, but that's more editing)
Please Log in or Create an account to join the conversation.
- thewho
- Offline
- Premium Member
-
- Posts: 128
- Thank you received: 2
addf pid.s.do-pid-calcs servo-thread
But now it complains about an unknown symbol in module, spindle.hal:8
EDIT: Fixed that one by myself

Got a few more, but I'll try to fix them myself
Please Log in or Create an account to join the conversation.
- thewho
- Offline
- Premium Member
-
- Posts: 128
- Thank you received: 2
Now it´s that "motion.spindle-on" is already linked to "velocity-mode" At line 80
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
Delete line 80 (net spindle-on <= motion.spindle-on )
Please Log in or Create an account to join the conversation.
- thewho
- Offline
- Premium Member
-
- Posts: 128
- Thank you received: 2

A couple of questions:
Will G33.1 aka Rigid tapping work when I get this running?
And can you get the PID-parameters changeable in the calibration tool? I have a 4th tab but it's empty.
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
Will G33.1 aka Rigid tapping work when I get this running?
It should.
And can you get the PID-parameters changeable in the calibration tool? I have a 4th tab but it's empty.
I tried, and it is possible, but I am not sure it is worth the trouble. You need to move the PGAIN_I and PGAIN_V into existing [AXIS_N] sections and then change the HAL file to look in those sections.
It is not a lot harder to open a terminal, type "halcmd -kf" and then start typing "setp pid.v.Pgain 100"
"show pin pid.v*" will show the current values.
When it all seems to work, just note the numbers and put them in the INI by hand.
Please Log in or Create an account to join the conversation.