- Posts: 52
- Thank you received: 0
Stepconf HAL: ERROR: duplicate component name 'hal
Stepconf still to put "HALUI = halui" in my ini file. This is my configuration:
Attachment not found
Because in my custom.hal file I put this:
loadusr halui -ini custom_halui.ini
when I run linuxcnc I get:
HAL: ERROR: duplicate component name 'halui'
I read several guides on how to customize the configuration of LinuxCNC but unfortunately after that I can no longer launch stepconf because the changes are deleted.
Please Log in to join the conversation.
nicokid wrote: loadusr halui -ini custom_halui.ini.
If you really need to load HALUI with a different INI file than the default (Are you sure you need to do this?) then you will have to
unloadusr halui
first.
Or. better, remove the HALUI=halui from the main INI file and switch to hand editing the HAL and INI.
Just consider that Stepconf has now done its job, and the most effective place to tweak is now directly in the config files.
Please Log in to join the conversation.
Chris M
Please Log in to join the conversation.
I know, but my problem is to be able to edit the files produced by stepconf so that they are not deleted when I run again stepconf.andypugh wrote: Or. better, remove the HALUI=halui from the main INI file and switch to hand editing the HAL and INI.
Just consider that Stepconf has now done its job, and the most effective place to tweak is now directly in the config files.
Please Log in to join the conversation.
Please Log in to join the conversation.
Yes, I tried but it seems that LinuxCNC loads halui (but there is no HALUI command in the ini file) before my command loadusr.cmorley wrote: ok that's a bug. but can you just not add that line in your custom hal file?
I can try to unload halui in custom.hal before loadusr as suggested andypugh (thanks).
Eventually I want to use this setup that I found online for my stepcraft 840:
Please Log in to join the conversation.
You are right, but I'm a beginner and I need some graphical tool for learning.andypugh wrote: I am saying it is time to park Stepconf, and not use it again now you have a config that is close.
Chris Morley still develops stepconf? I noticed that everything is written in python and should not be too difficult to change. But the author takes far less time :laugh:
Nicola.
Please Log in to join the conversation.
The comes a point when Stepconf stops making things easier and starts to make things harder. I think you are probably at that point.
Please Log in to join the conversation.
Thanks, Nicola.
Please Log in to join the conversation.
nicokid wrote: Ok, but I want to play some more before 'throw in the towel'..
Think of it not so much as "throwing in the towel" as "grasping the nettle"
I don't know how well that translates to your locale.
Please Log in to join the conversation.
