hal-core

Hi,

If you want to deliver a machine like a cnc-bandsaw you could consider to use the hal-core code with
your own component or components.

When not to use :
- If you need a linuxcnc nml interface, linuxcnc's motion planner, linuxcnc gtk or qtvcp gui's.
- If you like Python.

When considering to use:
- If you like small software package's.
- If you like C and C++
- If you like Qt-c++ gui's

Further info:
- No real coding knowlegde is needed.
- Start learing to write a component. Examples included with source.

github.com/grotius-cnc/hal_core

Hi Andy,

You can do this with a stock LinuxCNC installation. (And I often do).
Yes, that is ok. The disk space is not as important for me.

If a company or individual want's to build something from scratch and needs in fact only a hal platform without
any entanglement with nml, tcl, python, etc. Then this becomes useful.

My strategy is to build and provide future program's from this empty hal template.
It now build's outside of qt. I will try to create a qt project of this repository.

What i did is removed everything except a working rtapi / hal environment and included a example how to build realtime components with the gcc command instead of the python-halcompile.

I had to remove the nml interface from some hal source files. Also the tcl (gtk based stuff) source is removed.
It is configured for uspace.

I just updated the repository code again. It is quite clean now. The filesize is 6.8Mib.

It can be a useful startpoint if you want to build something from scratch.
In my previous attempt's i failed trough complexity during the cleanup process.
You have to constantly check if it builds etc, otherwise you are lost. Now i succeeded quite easely.







 

@Grotius
The HAL has  pin to send the encoder act pos over  nml RCS_CMD to the cnc.
I realy could use that. 

Best rgds

Hi Udo,

Please not spread the same questions around different topics.
And halcore is free of NML, python, etc.

Hi Grotius,

I have been trying to get this to work on a fresh install of Debian 11, I have all the make files working.
The problem is when I try to run the halrun script, I get the following errors when I run it as sudo or regular

Not sure what to do, the halcmd program seems to work, but it won't load any thread modules



 

Hi,

Halcore is by default installed in the /opt/ dir, i see you did this oke.

After the configure scripts you have to do a trick.
To insert kernel modules as user in the future, you have to type : "sudo make setuid"
This will give the user "superuser" privileges for inserting kernel modules.

Info:
github.com/grotius-cnc/hal-core/blob/main/src/configure
Line 11152 :  " sudo make setuid "

github.com/grotius-cnc/hal-core/blob/main/src/readme.md
Install by makefile:

Info:

For the trajectory planner i will make an update coming time.
Current code : github.com/grotius-cnc/hal_trajectory

The trajectory planner has a s-curve motion profile implemented, this works oke with hal-core.

However,

What i really miss is a path optimizer algoritme to optimize speed in small corners, small circles, high velocity path's, etc
in such a way the machine off path stay's minimal, like zero mm.
It's like sampling the machine's g-force to optimal result.

Today i worked out a concept that samples the path planner to optimal results.
I will implement this algo as look ahead function. I think it should work, it only takes time to implement the code.

 

This might help. I have a branch here github.com/rodw-au/linuxcnc/tree/arc-radius
that extends state tags to report the arc radius in real time as a hal motion pin.
You should be able to calculate the maximum velocity for a given acceleration and arc radius.
The Khan Academy loop de loop is a humourous way to describe the maths required.

Thanks Grotius,

Running those commands manually with $USER replaced with my name fixed the problem. It seems to be working now.

One thing I had to do to get everything to compile was add include statements to halcmd_completion.h for ctype.h and string.h, not sure if this is something that needs to be changed on the github code or it was just me?