On 5 July 2017 at 12:14, Les Newell wrote:
> The next question, is it possible to repeat sections? For instance in
> [RS274NGC] I have different parameter files for each config. All other
> values are the same. It would be nice to have a [RS274NGC] section in my
> main config to specify the parame
Thanks Andy, I was going to ask if there was an include function for ini
files. My lathe runs two configs, one with the tool turret installed and
one without. My turret is tiny and only suitable for a few jobs. It is
so small it can be mounted on one of the QC tool holders. Currently I
run two
On 5 July 2017 at 02:43, John Kasunich wrote:
> Kind of a kludge, but the streamer/ halstreamer system could do what you are
> describing.
Another way:
INI files can use #INCLUDE
http://linuxcnc.org/docs/2.7/html/config/ini-config.html#_include_files
{.ini file}
[KINS]
#INCLUDE corrections.inc
Kind of a kludge, but the streamer/ halstreamer system could do what you are
describing.
The component that wants to use the data would export a clock pin and one or
more input pins.
Each edge of the clock pin delivers a value (or set of values) from an external
file.
In this application, it wo
For probe compensation batch reading would be far more useful than compiled in,
then it becomes simple to read the compensation file for any stylus
you change too.
Dave Caroline
--
Check out the vibrant tech community on
On 3 July 2017 at 13:59, Les Newell wrote:
>
> On my lathe I will probably keep with using kinematics as it is then before
> backlash compensation rather than after.
It seems likely to be a very simple kinematics module, and so will
probably compile easily with halcompile.
At that point it might
On 03/07/2017 13:15, andy pugh wrote:
There is a HAL module for that:
http://linuxcnc.org/docs/devel/html/man/man9/offset.9.html
So I see. I missed John's original link to the offset module. Doing
something similar to that worked on my lathe but I did have some homing
issues. That was on a v
On 3 July 2017 at 11:16, Les Newell wrote:
> You need to go both ways. You need to offset the command and do a reverse
> offset on the feedback.
There is a HAL module for that:
http://linuxcnc.org/docs/devel/html/man/man9/offset.9.html
Or there is an exerimental branch with the option built-in
h
Hi Andy,
Putting the Z axis position into the input of "lincurve" could give
you an output to apply as an offset to the X position command.
You need to go both ways. You need to offset the command and do a
reverse offset on the feedback. Yes, I could use the generated offset
then add extra m
On 2 July 2017 at 09:07, Les Newell wrote:
> The problem is that bed wear or spindle misalignment causes cross-coupling
> between the X and Z axes, which is why it needs to be done in kinematics.
Putting the Z axis position into the input of "lincurve" could give
you an output to apply as an off
By ugly I was talking about setting up shared memory communications
simply to pass config values once at startup. It is also untidy from
the user's viewpoint. They need to load two modules even though one is
going to simply read from a file, squirt those values to the HAL
module then exit.
Hi John,
The problem is that bed wear or spindle misalignment causes
cross-coupling between the X and Z axes, which is why it needs to be
done in kinematics.
Les
On 02/07/17 01:47, John Kasunich wrote:
How many points do you need? If 16 or less, check out the lincurve
component
http://linu
On Fri, Jun 30, 2017, at 05:46 PM, Les Newell wrote:
> Is it possible for a real time HAL module to read config values from
> disk? I guess I could do it the ugly way and have two modules, one in
> user space to read the disk and pass values to the mealtime module.
>
> My lathe is pretty worn
On 30/06/17 23:05, Chris Albertson wrote:
That is not "ugly" is the common why things are done in real-time
systems.
You try as hard as you can to push everything you can into user space.
What you describe is actually "best practice".
Look even at the normal Linux kernel. Typically an inte
On Fri, Jun 30, 2017 at 2:46 PM, Les Newell
wrote:
> Is it possible for a real time HAL module to read config values from disk?
> I guess I could do it the ugly way and have two modules, one in user space
> to read the disk and pass values to the mealtime module.
>
That is not "ugly" is the comm
On 06/30/2017 03:46 PM, Les Newell wrote:
Is it possible for a real time HAL module to read config values from
disk? I guess I could do it the ugly way and have two modules, one in
user space to read the disk and pass values to the mealtime module.
Realtime modules can not do file I/O.
If you
Is it possible for a real time HAL module to read config values from
disk? I guess I could do it the ugly way and have two modules, one in
user space to read the disk and pass values to the mealtime module.
My lathe is pretty worn near the headstock so it tends to turn tapers
when working near
17 matches
Mail list logo