VMC related HAL questions.

More
05 Jun 2015 23:34 #59489 by andypugh
Replied by andypugh on topic VMC related HAL questions.

Tried a M3 S100 but It doesn't compensate at all? Am I missing something here?

You will need to tune the PID values in the INI file.
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.

More
05 Jun 2015 23:38 #59490 by thewho
Replied by thewho on topic VMC related HAL questions.
Ignore what I was wrote earlier. I replaced the wrong config folder so there was literally no change to before.

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.

More
05 Jun 2015 23:39 #59491 by andypugh
Replied by andypugh on topic VMC related HAL questions.

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.

More
05 Jun 2015 23:47 - 05 Jun 2015 23:57 #59492 by thewho
Replied by thewho on topic VMC related HAL questions.
Changed every [SPINDLE_9] to [SPINDLE] but I still get the same error. :(

EDIT: Added Error, HAL and INI files
Attachments:
Last edit: 05 Jun 2015 23:57 by thewho.

Please Log in or Create an account to join the conversation.

More
06 Jun 2015 00:08 - 06 Jun 2015 00:08 #59493 by andypugh
Replied by andypugh on topic VMC related HAL questions.
Ah I see the problem.

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)
Last edit: 06 Jun 2015 00:08 by andypugh.

Please Log in or Create an account to join the conversation.

More
06 Jun 2015 00:45 - 06 Jun 2015 00:54 #59494 by thewho
Replied by thewho on topic VMC related HAL questions.
Some progress, got another error but I solved that by removing:
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 :laugh:
Got a few more, but I'll try to fix them myself
Last edit: 06 Jun 2015 00:54 by thewho.

Please Log in or Create an account to join the conversation.

More
06 Jun 2015 01:01 #59495 by thewho
Replied by thewho on topic VMC related HAL questions.
Well I got to feel like I somewhat knew what I was doing..

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.

More
06 Jun 2015 02:11 #59498 by andypugh
Replied by andypugh on topic VMC related HAL questions.
Yes, sorry, my error.

Delete line 80 (net spindle-on <= motion.spindle-on )

Please Log in or Create an account to join the conversation.

More
06 Jun 2015 04:40 #59501 by thewho
Replied by thewho on topic VMC related HAL questions.
Gonna try that first thing tomorrow ;)

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.

More
06 Jun 2015 04:52 #59502 by andypugh
Replied by andypugh on topic VMC related HAL questions.

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.

Time to create page: 0.235 seconds
Powered by Kunena Forum