Hal files: MesaCT vs. PNCconf - help please
- slowpoke
- Away
- Elite Member
Less
More
- Posts: 171
- Thank you received: 25
18 Mar 2024 21:28 - 18 Mar 2024 21:33 #296256
by slowpoke
Hal files: MesaCT vs. PNCconf - help please was created by slowpoke
I have a VERY fuzzy picture of how .hal files interact with LinuxCNC.
I'm using Axis with a Mesa 7195t
My limited (possible incorrect) understanding is as follows:
1) hal files act as a txt file based definition of how various hardware points (inputs, outputs etc.) are configured and linked to the LinuxCNC software
2) hal files are/can be generated by using configuration programs such as PNCconf or MesaCT, or they could be written from scratch or edited with a text editor.
3) If a hal file generated by PNCconf or MesaCT is edited with a text editor to add functionality that functionality (lines added using the text editor will likely be lost if MesaCT or PNCconf is used again to tweak or add some other functionality.
4) I think when LinuxCNC starts it reads the .hal files to know how to interact with the hardware?
5) I think there can be multiple .hal files that get read on startup?
6) It's really unclear what type of configuration items go in what.hal files or how one would know which .hal file and where in that .hal file changes should be made?
7) I presently have a io.hal as well as a main.hal that were generated by mesaCT. I'm not sure if I should also have a .hal file generated by PNCconf?
8) I would like to assign encoder0 to a linear scale (hopefully that I can then view somewhere in Axis to see if I have the scaling correct and compare to my external DRO.
If any of my assumptions above are incorrect, please let me know.
Much appreciated
I'm using Axis with a Mesa 7195t
My limited (possible incorrect) understanding is as follows:
1) hal files act as a txt file based definition of how various hardware points (inputs, outputs etc.) are configured and linked to the LinuxCNC software
2) hal files are/can be generated by using configuration programs such as PNCconf or MesaCT, or they could be written from scratch or edited with a text editor.
3) If a hal file generated by PNCconf or MesaCT is edited with a text editor to add functionality that functionality (lines added using the text editor will likely be lost if MesaCT or PNCconf is used again to tweak or add some other functionality.
4) I think when LinuxCNC starts it reads the .hal files to know how to interact with the hardware?
5) I think there can be multiple .hal files that get read on startup?
6) It's really unclear what type of configuration items go in what.hal files or how one would know which .hal file and where in that .hal file changes should be made?
7) I presently have a io.hal as well as a main.hal that were generated by mesaCT. I'm not sure if I should also have a .hal file generated by PNCconf?
8) I would like to assign encoder0 to a linear scale (hopefully that I can then view somewhere in Axis to see if I have the scaling correct and compare to my external DRO.
If any of my assumptions above are incorrect, please let me know.
Much appreciated
Last edit: 18 Mar 2024 21:33 by slowpoke.
Please Log in or Create an account to join the conversation.
- JT
- Away
- Administrator
Less
More
- Posts: 860
- Thank you received: 450
19 Mar 2024 08:56 - 19 Mar 2024 08:58 #296292
by JT
Replied by JT on topic Hal files: MesaCT vs. PNCconf - help please
Mesa CT will not overwrite the ini file or any custom hal files, it will overwrite the main.hal and io.hal files.
In Mesa CT go to the Options tab then the HAL tab and you can tell Mesa CT to generate and connect to more hal files like custom.hal, postgui.hal and shutdown.hal. These file will not be overwritten.
JT
In Mesa CT go to the Options tab then the HAL tab and you can tell Mesa CT to generate and connect to more hal files like custom.hal, postgui.hal and shutdown.hal. These file will not be overwritten.
JT
Last edit: 19 Mar 2024 08:58 by JT.
The following user(s) said Thank You: tommylight, Unlogic, slowpoke
Please Log in or Create an account to join the conversation.
Time to create page: 0.205 seconds