fre 2023-11-17 klockan 20:47 + skrev andy pugh:
> On Fri, 17 Nov 2023 at 19:29, Rod Webster
> wrote:
>
> > Finally, I might add that if you are competent in C and the core of
> > your requirement is real time, why complicate it by adding a non-
> > real
> > time Python component. it sounds
Sam-
yes the pins behave in realtime but the two example components I was
discussing
https://github.com/cnc-club/linuxcnc-engraving-comp/blob/master/compensation.py
and
https://github.com/scottalford75/LinuxCNC-3D-Printing/tree/master/compensation
are userspace python and *not* realtime.
are you talking e-offset pins? Those are realtime.. I am using a realtime
comp to do spindle synced motion... It works great..
https://www.youtube.com/shorts/nViXP9SsdWc
sam
On Fri, Nov 17, 2023 at 10:39 AM Ted wrote:
> On 11/17/2023 10:49 AM, andy pugh wrote:
> > Is this related to
On 11/17/2023 10:49 AM, andy pugh wrote:
Is this related to wanting to do height mapping, or laser rastering,
or something?
The end result is a multi-layer z-height and x-y-z-thermal compensation
system. (Yes, I know we have the "compensation" components, but both
offerings present by
On Fri, 17 Nov 2023 at 15:44, Ted wrote:
> I am looking to be able to share some large [fixed] co-ordinate value
> arrays between a realtime component, but source it from an external flat
> file (via a complementary userspace component).
Is this related to wanting to do height mapping, or laser
Good morning -
I am looking to be able to share some large [fixed] co-ordinate value
arrays between a realtime component, but source it from an external flat
file (via a complementary userspace component).
I was looking at the streamer and sampler, however I don't need the
iterative nature
