EMC2_Integrator_Manual.pdf
29 Apr 2010 00:08 #2741
by WildRice
EMC2_Integrator_Manual.pdf was created by WildRice
The EMC2_Integrator_Manual, section 7.2.1, lists only 2 Keywords for the [EMC] section
but my [EMC] section:
Do I have too many or does the Doc have too few keywords?
VERSION
MACHINE
but my [EMC] section:
[EMC]
MACHINE = Millie
NML_FILE = emc.nml
DEBUG = 0
Do I have too many or does the Doc have too few keywords?
Please Log in or Create an account to join the conversation.
29 Apr 2010 01:06 #2742
by WildRice
Replied by WildRice on topic Re:EMC2_Integrator_Manual.pdf
Same question for the [TASK] section. What does TASK=milltask do?
#
# TASK settings used by the task controller
#
# CYCLE_TIME=0.001
#
# The period, in seconds, at which EMCTASK will run.
# This parameter affects the polling interval when waiting
# for motion to complete, when executing a pause instruction,
# and when accepting a command from a user interface. There
# is usually no need to change this number.
#
[TASK]
TASK = milltask
CYCLE_TIME = 0.010
Please Log in or Create an account to join the conversation.
29 Apr 2010 12:01 #2752
by BigJohnT
Replied by BigJohnT on topic Re:EMC2_Integrator_Manual.pdf
Hi,
I found the answer to your question from a developer and will update the manual for those that want to know.
[06:52] <jepler> JT-Dev: [EMC]TASK specifies the name of the "task" executable. "task" does various things, such as communicate with the UIs over NML, communicate with the realtime motion planner over non-HAL shared memory, and interpret gcode.
[06:52] <JT-Dev> is there more than one tast executable?
[06:53] <jepler> JT-Dev: in the current time there's only one that makes sense for 99.9% of users, milltask
[06:53] <JT-Dev> ok thanks
[06:53] <jepler> in the dim mists of time (before hal), it was frequently the case that an integrator would have to build a modified version of things like task, io, and motion for a specific machine
[06:57] <jepler> debug flags are usually only useful to developers. the meaning of the flags can be found in the source file emcglb.h. in general, entering a value besides "0", "0x0" or the like will cause lots of information to be printed when emc is run in the terminal
[06:57] <JT-Dev> ok, thanks I'll put something in the manual for those that want to know
[06:58] <jepler> er, earlier I said [EMC]TASK but of course it's [TASK]TASK
John
I found the answer to your question from a developer and will update the manual for those that want to know.
[06:52] <jepler> JT-Dev: [EMC]TASK specifies the name of the "task" executable. "task" does various things, such as communicate with the UIs over NML, communicate with the realtime motion planner over non-HAL shared memory, and interpret gcode.
[06:52] <JT-Dev> is there more than one tast executable?
[06:53] <jepler> JT-Dev: in the current time there's only one that makes sense for 99.9% of users, milltask
[06:53] <JT-Dev> ok thanks
[06:53] <jepler> in the dim mists of time (before hal), it was frequently the case that an integrator would have to build a modified version of things like task, io, and motion for a specific machine
[06:57] <jepler> debug flags are usually only useful to developers. the meaning of the flags can be found in the source file emcglb.h. in general, entering a value besides "0", "0x0" or the like will cause lots of information to be printed when emc is run in the terminal
[06:57] <JT-Dev> ok, thanks I'll put something in the manual for those that want to know
[06:58] <jepler> er, earlier I said [EMC]TASK but of course it's [TASK]TASK
John
Please Log in or Create an account to join the conversation.
29 Apr 2010 12:14 #2753
by WildRice
Replied by WildRice on topic Re:EMC2_Integrator_Manual.pdf
Thanks John! As always, you do an excellent job of keeping the doc up-to-date. It is appreciated.
Please Log in or Create an account to join the conversation.
Moderators: HansU
Time to create page: 0.087 seconds