emc-developers — Developer specific. For issues of interest to users see emc-users list (below)

Re: [Emc-developers] Tool Data Synchronization (Smooth-Core)

[Nicklas SB K. <nk...@nk...>]

Guess store in database with some kind of standard protocol would be a very good solution. If I understand it correct
SQL is a standard "language" to access database. However not sure if possible to use SQL against common databases if run
on a server or locally.

Nicklas Karlsson


ons 2025-11-05 klockan 12:02 -0600 skrev Brad Collette:
> Hey guys,
> 
> A few weeks ago in the video meetup we started talking about co-development
> of a better tool synchronization solution.  I took some time to dig into
> this and was amazed at how bad the state-of-the-art appears to be.
> 
> I don't think the solution belongs in either LinuxCNC or in FreeCAD.
> Rather, I think it's a perfect opportunity to start a new open-source
> project.
> 
> I've put together a new Github organization (loobric) and started work on
> several repos within it.
> I'd love to get some feedback on this direction and would REALLY love to
> get some help.
> 
> There's a blog post
> <https://loobric.com/blog/introducing-smooth-tool-data-sync> that describes
> the big picture
> For developers, the main repo is at https://github.com/loobric/smooth-core and
> the README should be enough to explain what's going on.
> 
> Let me know what you think or if there are glaring questions that I've
> failed to answer in the blog post or readme.
> 

[Emc-developers] Tool Data Synchronization (Smooth-Core)

[Brad C. <sho...@gm...>]

Hey guys,

A few weeks ago in the video meetup we started talking about co-development
of a better tool synchronization solution.  I took some time to dig into
this and was amazed at how bad the state-of-the-art appears to be.

I don't think the solution belongs in either LinuxCNC or in FreeCAD.
Rather, I think it's a perfect opportunity to start a new open-source
project.

I've put together a new Github organization (loobric) and started work on
several repos within it.
I'd love to get some feedback on this direction and would REALLY love to
get some help.

There's a blog post
<https://loobric.com/blog/introducing-smooth-tool-data-sync> that describes
the big picture
For developers, the main repo is at https://github.com/loobric/smooth-core and
the README should be enough to explain what's going on.

Let me know what you think or if there are glaring questions that I've
failed to answer in the blog post or readme.

-- 
Brad Collette
573-427-7132

Re: [Emc-developers] Infrastructure (was Re: Documentation)

[John O'B. <joh...@gm...>]

To be fair, the documentation is not *completely* silent on tuning a
PREEMPT_RT system. If I'm understanding it correctly, there is a bit about
it at the bottom of
https://linuxcnc.org/docs/stable/html/install/latency-test.html, though
granted it could be expanded.
-----------------

>
> Message: 3
> Date: Wed, 5 Nov 2025 05:10:42 +1000
> From: rodw <ro...@ve...>
> To: "EMC developers" <emc...@li...>
> Subject: Re: [Emc-developers] Infrastructure (was Re: Documentation)
> Message-ID: <b7388064-7aff-46a8-a9d7-6159eee38967@diskstation2>
> Content-Type: text/plain; charset="utf-8"
>
> I built the 2.94 ISO.
> There is no reason to continue with the ISO now the release version is in
> Debian Trixie.
> Users today want and expect to be able to run the latest version of ?
> Debian.
> They also want and need a simple way to install the development version.
> Some GUI's require this. Please extend workflows to 2.10
> The ISO exposes us to Debian bugs (like the raspberry pi firmware bug in
> the Debian build system that was never resolved for the life of bookworm)
> We get blamed for these bugs outside of our control
> It forces us to deal with issues that are outside of our core expertise
> when we are already stretched for development resources.
> With the mainline release, Users just need to be capable of a one line
> install at the command prompt or use synaptic.
> They also can obtain linuxcnc on other architectures that Debian builds
> for.
> ?
> I've created a video guide to installing Trixie and 2.94. ?
> https://youtu.be/_4Ryh37wU2o ?
> The bigger issue that can't be resolved in an ISO is the need to tune a
> PREEMPT_RT system and our documentation is totally silent about that, This
> requirement has been well known in the Linux Real time community for a long
> time but documentation on settings is sparse. ?  Newer ? operating systems
> make this more necessary than in the past. ? We have never addressed this
> in our docs.
> ?
> Rod.
> ?
> ?
> ?
> On 2025-11-04 23:28, Morten Hanasand  <mo...@ha...>  wrote:
> > I think keeping the .ISO is hugely important to lowering the barrier to
>
> > entry.
> >
> > Has there been any further discussion about the idea of a foundation or
>
> > similar to allow funding contributions which could pay for things like
> > dedicated build, web, forum, backup servers, testing hardware, foot
> > massages etc? Think there might be a surprising amount of willingness
> to
> > contribute financially.
> >
> > If that's too daunting, there are things like this, which take some of
> > the scary legal stuff out of the equation while still clarifying
> > ambiguity, and allowing for raising funds,
> > https://commonsconservancy.org/how/
> > Think they also have some functionality for preserving essential
> > information should someone withdraw or disappear from the project
> abrubtly.
> >
> > Morten
> >
> > On 04/11/2025 10:14, andy pugh wrote:
> > >
> > >  At the moment I think I come down on the side of keeping our custom
> > >  .ISO, as many of our potential users are very much not Linux
> > >  enthusiasts, and we should make installation as simple as possible,.
> > >
> > >  (However, the latest .ISO I created doesn't actually install on one of
> > >  my tests PCs, and distributing an ISO that doesn't work is probably
> > >  worse than distributing no ISO at all.)
> > >  (If anyone want to try it, I think it is this one here:
> > >  https://www.linuxcnc.org/iso/linuxcnc_2.9.6-amd64.hybrid.iso It
> should
> > >  install Trixie but seems to not show the correct splash-screen in UEFI
> > >  mode (minor issue) but also, on my N100-DC, crashes to a pink flashing
> > >  screen in the last stages of the install, leaving a system that boots
> > >  to a grub prompt)
> > >
> >
> >
> > _______________________________________________
> > Emc-developers mailing list
> > Emc...@li...
> > https://lists.sourceforge.net/lists/listinfo/emc-developers
>
> ------------------------------
>
> Message: 4
> Date: Wed, 5 Nov 2025 10:26:42 +0000
> From: andy pugh <bod...@gm...>
> To: EMC developers <emc...@li...>
> Cc: Steffen M?ller <ste...@gm...>, pe...@hu...
> Subject: Re: [Emc-developers] Debian Release
> Message-ID:
>         <
> CAN...@ma...>
> Content-Type: text/plain; charset="UTF-8"
>
> On Mon, 3 Nov 2025 at 21:54, Steffen M?ller via Emc-developers
> <emc...@li...> wrote:
> >
>
> > You may have seen it already - I have uploaded 2.9.7. The build demons
> https://buildd.debian.org/status/package.php?p=linuxcnc had no problems,
> it should soon be available on the Debian mirrors
>
> Marvellous, thanks.
>
> It's a bit untidy that it shows build failures on some architectures
> (not any that we claim to support) and rather surprising that the
> issue is not something half-expected like realtime kernel
> availability, but the absence of python3-pyqt5.qtwebengine.
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> ? George Fitch, Atlanta Constitution Newspaper, 1912
>
>
>
> ------------------------------
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
>
> ------------------------------
>
> End of Emc-developers Digest, Vol 235, Issue 6
> **********************************************
>

Re: [Emc-developers] Debian Release

[andy p. <bod...@gm...>]

On Mon, 3 Nov 2025 at 21:54, Steffen Möller via Emc-developers
<emc...@li...> wrote:
>

> You may have seen it already - I have uploaded 2.9.7. The build demons https://buildd.debian.org/status/package.php?p=linuxcnc had no problems, it should soon be available on the Debian mirrors

Marvellous, thanks.

It's a bit untidy that it shows build failures on some architectures
(not any that we claim to support) and rather surprising that the
issue is not something half-expected like realtime kernel
availability, but the absence of python3-pyqt5.qtwebengine.

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

Re: [Emc-developers] Infrastructure (was Re: Documentation)

[rodw <ro...@ve...>]

I built the 2.94 ISO.
There is no reason to continue with the ISO now the release version is in Debian Trixie.
Users today want and expect to be able to run the latest version of    Debian.
They also want and need a simple way to install the development version. Some GUI's require this. Please extend workflows to 2.10
The ISO exposes us to Debian bugs (like the raspberry pi firmware bug in the Debian build system that was never resolved for the life of bookworm)
We get blamed for these bugs outside of our control
It forces us to deal with issues that are outside of our core expertise when we are already stretched for development resources.
With the mainline release, Users just need to be capable of a one line install at the command prompt or use synaptic.
They also can obtain linuxcnc on other architectures that Debian builds for.
 
I've created a video guide to installing Trixie and 2.94.   https://youtu.be/_4Ryh37wU2o  
The bigger issue that can't be resolved in an ISO is the need to tune a PREEMPT_RT system and our documentation is totally silent about that, This requirement has been well known in the Linux Real time community for a long time but documentation on settings is sparse.    Newer   operating systems make this more necessary than in the past.   We have never addressed this in our docs.
 
Rod.
 
 
 
On 2025-11-04 23:28, Morten Hanasand  <mo...@ha...>  wrote:
> I think keeping the .ISO is hugely important to lowering the barrier to   
> entry.
>
> Has there been any further discussion about the idea of a foundation or   
> similar to allow funding contributions which could pay for things like   
> dedicated build, web, forum, backup servers, testing hardware, foot   
> massages etc? Think there might be a surprising amount of willingness to   
> contribute financially.
>
> If that's too daunting, there are things like this, which take some of   
> the scary legal stuff out of the equation while still clarifying   
> ambiguity, and allowing for raising funds,   
> https://commonsconservancy.org/how/
> Think they also have some functionality for preserving essential   
> information should someone withdraw or disappear from the project abrubtly.
>
> Morten
>
> On 04/11/2025 10:14, andy pugh wrote:
> >
> >  At the moment I think I come down on the side of keeping our custom
> >  .ISO, as many of our potential users are very much not Linux
> >  enthusiasts, and we should make installation as simple as possible,.
> >
> >  (However, the latest .ISO I created doesn't actually install on one of
> >  my tests PCs, and distributing an ISO that doesn't work is probably
> >  worse than distributing no ISO at all.)
> >  (If anyone want to try it, I think it is this one here:
> >  https://www.linuxcnc.org/iso/linuxcnc_2.9.6-amd64.hybrid.iso It should
> >  install Trixie but seems to not show the correct splash-screen in UEFI
> >  mode (minor issue) but also, on my N100-DC, crashes to a pink flashing
> >  screen in the last stages of the install, leaving a system that boots
> >  to a grub prompt)
> >
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Infrastructure (was Re: Documentation)

[Robert S. <rm...@un...>]

Am Dienstag, dem 04.11.2025 um 10:14 +0000 schrieb andy pugh:
> I am nervous of putting 2.10 debs in GitHub "Releases" as they are
> not
> "released".

according to 
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
a release can be marked as "pre-release" and not ready for production.
e.g. FreeCAD also has their latest "stable" next to their weekly dev-
build on github releases.

-- 
Robert Schöftner <rm...@un...>

Re: [Emc-developers] Infrastructure (was Re: Documentation)

[Morten H. <mo...@ha...>]

I think keeping the .ISO is hugely important to lowering the barrier to 
entry.

Has there been any further discussion about the idea of a foundation or 
similar to allow funding contributions which could pay for things like 
dedicated build, web, forum, backup servers, testing hardware, foot 
massages etc? Think there might be a surprising amount of willingness to 
contribute financially.

If that's too daunting, there are things like this, which take some of 
the scary legal stuff out of the equation while still clarifying 
ambiguity, and allowing for raising funds, 
https://commonsconservancy.org/how/
Think they also have some functionality for preserving essential 
information should someone withdraw or disappear from the project abrubtly.

Morten

On 04/11/2025 10:14, andy pugh wrote:
>
> At the moment I think I come down on the side of keeping our custom
> .ISO, as many of our potential users are very much not Linux
> enthusiasts, and we should make installation as simple as possible,.
>
> (However, the latest .ISO I created doesn't actually install on one of
> my tests PCs, and distributing an ISO that doesn't work is probably
> worse than distributing no ISO at all.)
> (If anyone want to try it, I think it is this one here:
> https://www.linuxcnc.org/iso/linuxcnc_2.9.6-amd64.hybrid.iso It should
> install Trixie but seems to not show the correct splash-screen in UEFI
> mode (minor issue) but also, on my N100-DC, crashes to a pink flashing
> screen in the last stages of the install, leaving a system that boots
> to a grub prompt)
>

[Emc-developers] Infrastructure (was Re: Documentation)

[andy p. <bod...@gm...>]

On Tue, 4 Nov 2025 at 08:00, Sebastian Kuzminsky <se...@hi...> wrote:
>
> I think the buildbot has very little utility now that uspace is the norm.

Firstly, relieved to hear from you Seb, I was starting to get a little
worried about you when emails went unanswered.

One place that the builbot(s) do have utility is in uploading the
docs, I think? (ie, the subject of this thread)

I am curious who is still using RTAI (other than me). I have
occasionally hand-crafted RTAI debs (since the Buildbot RTAI builders
were superseded)

It should be fairly easy to move the stable branch docs updates to
Github (as Github currently creates .debs and so I imagine that the
requisite files exist at some point and can be copied across.)
Probably the dev docs exist at some point too?
I don't _think_ that the current script is publicly visible? The
various scripts in LinuxCNC/infrastructure on Github seem to be rather
older?

I am nervous of putting 2.10 debs in GitHub "Releases" as they are not
"released".

Another place where the Buildbots are useful (only to me) is in
putting all the right files for a release into the correct structure
for our debian repository. Updating the repository using files from
Github involves quite a lot of renaming and placing individual files
in place (also some things, like "Changes" files are not generated).

There is a broader discussion to be had about whether we should
continue to run our own Debian repository, and to offer the installer
ISO and the Pi images. We could suggest that folk install the base
Debian ISO and then get LinuxCNC either from the Debian repository, or
manually from the .debs on GitHub.

At the moment I think I come down on the side of keeping our custom
.ISO, as many of our potential users are very much not Linux
enthusiasts, and we should make installation as simple as possible,.

(However, the latest .ISO I created doesn't actually install on one of
my tests PCs, and distributing an ISO that doesn't work is probably
worse than distributing no ISO at all.)
(If anyone want to try it, I think it is this one here:
https://www.linuxcnc.org/iso/linuxcnc_2.9.6-amd64.hybrid.iso It should
install Trixie but seems to not show the correct splash-screen in UEFI
mode (minor issue) but also, on my N100-DC, crashes to a pink flashing
screen in the last stages of the install, leaving a system that boots
to a grub prompt)

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

Re: [Emc-developers] Documentation

[Sebastian K. <se...@hi...>]

I think the buildbot has very little utility now that uspace is the norm.

I suggest focusing on building in containers on our forge host (github), 
so that the community can maintain it.

-- 
Sebastian Kuzminsky

On 11/3/25 23:27, rodw wrote:
>   
> Buildbot2 needs to   start building for Trixie.   Currently there is no way to   install master branch (2.10) on Trixie without compiling from source.
> Alternatively the new Git workflows should be extended to build for 2.10
> Rod
>   
> On 2025-11-04 14:39, Sebastian Kuzminsky  <se...@hi...>  wrote:
>> Buildbot2 should be making forward progress again.
>>
>> --
>> Sebastian Kuzminsky
>>
>> On 11/3/25 07:54, Andy Pugh wrote:
>>>>   On 3 Nov 2025, at 12:13, Greg C  <gre...@gm...>  wrote:
>>>>
>>>>   It seems like whatever process posts the updated documentation to the actual documentation website is not working.
>>>   I am not sure what the process is, but I suspect it involves the buildbot (or buildbot2)
>>>   Buildbot2 appears to be broken, build 3750 00-checkin has been running for almost 2 weeks.
>>>
>>>   I (or anyone) can terminate that build via the IRC bot, but I would just expect it to get stuck again.
>>>
>>>
>>>
>>>
>>>   _______________________________________________
>>>   Emc-developers mailing list
>>>   Emc...@li...
>>>   https://lists.sourceforge.net/lists/listinfo/emc-developers
>>
>> _______________________________________________
>> Emc-developers mailing list
>> Emc...@li...
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Documentation

[rodw <ro...@ve...>]

 
Buildbot2 needs to   start building for Trixie.   Currently there is no way to   install master branch (2.10) on Trixie without compiling from source.
Alternatively the new Git workflows should be extended to build for 2.10  
Rod
 
On 2025-11-04 14:39, Sebastian Kuzminsky  <se...@hi...>  wrote:
> Buildbot2 should be making forward progress again.
>
> --   
> Sebastian Kuzminsky
>
> On 11/3/25 07:54, Andy Pugh wrote:
> >
> >>  On 3 Nov 2025, at 12:13, Greg C  <gre...@gm...>  wrote:
> >>
> >>  It seems like whatever process posts the updated documentation to the actual documentation website is not working.
> >  I am not sure what the process is, but I suspect it involves the buildbot (or buildbot2)
> >  Buildbot2 appears to be broken, build 3750 00-checkin has been running for almost 2 weeks.
> >
> >  I (or anyone) can terminate that build via the IRC bot, but I would just expect it to get stuck again.
> >
> >
> >
> >
> >  _______________________________________________
> >  Emc-developers mailing list
> >  Emc...@li...
> >  https://lists.sourceforge.net/lists/listinfo/emc-developers
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Documentation

[Sebastian K. <se...@hi...>]

Buildbot2 should be making forward progress again.

-- 
Sebastian Kuzminsky

On 11/3/25 07:54, Andy Pugh wrote:
>
>> On 3 Nov 2025, at 12:13, Greg C <gre...@gm...> wrote:
>>
>> It seems like whatever process posts the updated documentation to the actual documentation website is not working.
> I am not sure what the process is, but I suspect it involves the buildbot (or buildbot2)
> Buildbot2 appears to be broken, build 3750 00-checkin has been running for almost 2 weeks.
>
> I (or anyone) can terminate that build via the IRC bot, but I would just expect it to get stuck again.
>
>
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Debian Release

[Steffen M. <ste...@gm...>]

Hello,

You may have seen it already - I have uploaded 2.9.7. The build demons https://buildd.debian.org/status/package.php?p=linuxcnc had no problems, it should soon be available on the Debian mirrors. The new version is already mentioned on https://tracker.debian.org/pkg/linuxcnc. To upload, I made only minimal changes to the tarball, i.e. the -1 suffix to the version d/changelog and "unstable" as a release, added d/source/format. No upload to salsa or linuxcnc-gbp.  Maintainer is Andy, so this is a sponsored upload, not a team-upload as before, which is preparing for Andy to get upload privileges himself, too.

Best,
Steffen

> Gesendet: Montag, 3. November 2025 um 18:20
> Von: "Steffen Möller via Emc-developers" <emc...@li...>
> An: emc...@li...
> CC: "Steffen Möller" <ste...@gm...>, pe...@hu...
> Betreff: Re: [Emc-developers] Debian Release
>
> 
> > What does it take to get 2.9.7 into the next Debian release? 
> 
> At the very moment, it is Petter, me or Seb uploading it.
> I shall discuss offline with Petter how to render the updates of Debian a bit more instant than how we are arranging it now.
> 
> One of the bits holding me back is that I did not fully grasp how to properly use the https://github.com/LinuxCNC/linuxcnc-gbp repository, so I did not use it :-/ And something in me thinks that we do not really need it in the first place but should rather use the GitLab instance that Debian provides via salsa.debian.org.
> 
> An appearance of LinuxCNC on Debian's infrastructure would increase the chance to attract extra helping hands from the community, which I woudl appreciate since there are quite a few Lintian warnings (https://udd.debian.org/lintian/?packages=linuxcnc) that I am unlikely to find the time to address.
> 
> Steffen
> 
> 
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

[Emc-developers] linuxcnc_2.9.7-1_source.changes ACCEPTED into unstable

[Debian F. M. <ftp...@ft...>]

Thank you for your contribution to Debian.



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 22 Oct 2025 23:43:13 +0100
Source: linuxcnc
Architecture: source
Version: 1:2.9.7-1
Distribution: unstable
Urgency: low
Maintainer: LinuxCNC Developers <emc...@li...>
Changed-By: andypugh <an...@bo...>
Changes:
 linuxcnc (1:2.9.7-1) unstable; urgency=low
 .
   * [ci] publish releases with artifacts - GitHub now builds release debs
   * Revert 7d9ee66  to address #3583 - halui functions stop working in 2.9.5/6
   * Merge pull request #3512 from Sigma1912/patch-1
   * Gmoccapy: Fix arrow key up/down bug in tooleditor
Checksums-Sha1:
 01268abaa37f4a5e2317c92b3487b06103bec59c 3368 linuxcnc_2.9.7-1.dsc
 142a86dc940c61c953a58c735cdbe22a24a9b437 93551769 linuxcnc_2.9.7.orig.tar.gz
 f68ab13cb53d737b42d64125fd58134dacb7db3f 155200 linuxcnc_2.9.7-1.debian.tar.xz
 d58acc5e6205283af65b76dbfa98677df9c78e55 22880 linuxcnc_2.9.7-1_source.buildinfo
Checksums-Sha256:
 4a491432fd3df5dbc0e49993f48408267b00ec035a76487f8178a4d81248cb62 3368 linuxcnc_2.9.7-1.dsc
 cda481b5d35d9286d9dba31a994c26f571ea6a4b4c68aab3cb30737d2421d795 93551769 linuxcnc_2.9.7.orig.tar.gz
 4ee5ef589e688670ca9dc52a4cf935b0fc697026a9d248420a7d07baf0888765 155200 linuxcnc_2.9.7-1.debian.tar.xz
 15c2f2a642fd89e39ef35507359ed0fe2a294800c3be6451eb658cc5b4930099 22880 linuxcnc_2.9.7-1_source.buildinfo
Files:
 fd77d9e1a5007af765511cf958bdf23b 3368 misc optional linuxcnc_2.9.7-1.dsc
 8a0cf863fcce552140accf3e779445ad 93551769 misc optional linuxcnc_2.9.7.orig.tar.gz
 d8e363949320761e24bf8619da789b14 155200 misc optional linuxcnc_2.9.7-1.debian.tar.xz
 9e50c7bc52eafd40f5ccf48342e824a1 22880 misc optional linuxcnc_2.9.7-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3z4uQkp+J5wuSwI6ucKa7rL0UKcFAmkJFO8ACgkQucKa7rL0
UKcz8A/8DzDbhRWbTdm0a7CeAzvSu/vZo9Ro6jBHTXyUtBio/+Zvcfz0bCVERqsT
E7hXdMK1Ao9I1SXIEVgXbKTheKSUgbNIUnNKv+fwoncJ7N4QYvIb7nxoRYwU+e/2
QqjhkgcAjTJVZk5DW3HKGoQc4LgoTMv4aqHK6sTd7beSUXaNKKUM0vH+GvHsNQHk
2egt0aM2FyKeAqbc3LjwsNXBPe9Ro/3yZUCM6Qu0wZ4lHG5xveOevO5tUZ+D5Ub9
Ige87mpXZL7A16TWArKh/v28CMwDmm/ld/jQe8uDAu/j8g4lU0GaUBiVLRZ6FB8A
JkxX7Awx4Z7Biunqe9v2hgD7dFjtaoIn4j8DCFH+19ZbSs5bKBzfSrPvpik7aLFm
CSRyoMrUIEdpjMhJ0TuvKo5JbmXl+kZxfgPIvqftXSATEZ2nhSO+xgXvdX6MpZKE
lxcAZB0f/LUpS8TELx6pTSWtaJ0QbaARWys8S1gWeKT5JxBdsp34cJTxTWE6o8sO
AvzNWG8kbXDsOsPgwVXXe+rDKa+oL5k8en35mmRmvPAUp17KVfM3TJb0AnljCqyD
l2tUM5rOYiYXJ7UrTRjLyO1ZM2w7MICl9jiDRU0vQ0Zedd44irdM1KB0U/icYDil
cEYNhVkpOgWbylRyLdyiMUz53Z/L0lb5/r3Gq4OdsmFPzSLj7j4=
=PNYQ
-----END PGP SIGNATURE-----

[Emc-developers] Processing of linuxcnc_2.9.7-1_source.changes

[Debian F. M. <ftp...@ft...>]

linuxcnc_2.9.7-1_source.changes uploaded successfully to localhost
along with the files:
  linuxcnc_2.9.7-1.dsc
  linuxcnc_2.9.7.orig.tar.gz
  linuxcnc_2.9.7-1.debian.tar.xz
  linuxcnc_2.9.7-1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)

Re: [Emc-developers] Debian Release

[Steffen M. <ste...@gm...>]

> What does it take to get 2.9.7 into the next Debian release? 

At the very moment, it is Petter, me or Seb uploading it.
I shall discuss offline with Petter how to render the updates of Debian a bit more instant than how we are arranging it now.

One of the bits holding me back is that I did not fully grasp how to properly use the https://github.com/LinuxCNC/linuxcnc-gbp repository, so I did not use it :-/ And something in me thinks that we do not really need it in the first place but should rather use the GitLab instance that Debian provides via salsa.debian.org.

An appearance of LinuxCNC on Debian's infrastructure would increase the chance to attract extra helping hands from the community, which I woudl appreciate since there are quite a few Lintian warnings (https://udd.debian.org/lintian/?packages=linuxcnc) that I am unlikely to find the time to address.

Steffen

Re: [Emc-developers] Documentation

[Andy P. <bod...@gm...>]

> On 3 Nov 2025, at 12:13, Greg C <gre...@gm...> wrote:
> 
> It seems like whatever process posts the updated documentation to the actual documentation website is not working.

I am not sure what the process is, but I suspect it involves the buildbot (or buildbot2)
Buildbot2 appears to be broken, build 3750 00-checkin has been running for almost 2 weeks. 

I (or anyone) can terminate that build via the IRC bot, but I would just expect it to get stuck again. 

[Emc-developers] Documentation

[Greg C <gre...@gm...>]

To whom it may concern,

It seems like whatever process posts the updated documentation to the actual documentation website is not working.  Changes I pushed to qtplasmac docs yesterday are not showing up :(

Have a great day,
Greg 

[Emc-developers] Debian Release

[Andy P. <bod...@gm...>]

What does it take to get 2.9.7 into the next Debian release? 

[Emc-developers] Fixing some typos in the documentation

[John O'B. <joh...@gm...>]

Hiya,

I'm new and am going through the documentation for the first time. I have
noticed some typos so figured I'll fix them while I'm here.

As per
<http://linuxcnc.org/docs/stable/html/code/contr...rview_of_the_process>
linuxcnc.org/docs/stable/html/code/contr...rview_of_the_process
<https://linuxcnc.org/docs/stable/html/code/contributing-to-linuxcnc.html#_overview_of_the_process>
,
this is my attempt to communicate with the project developers and let you
all know what I am hacking on, explain what I am doing and why.

I've forked the repo and will submit a pull request with some changes as
soon as I figure out how to do that.

I've also posted a message to the forum. Please let me know if anyone has
any objections or concerns.

Regards,
John

Re: [Emc-developers] 2.10 Proposals

[Bertho S. <lc...@va...>]

On 10/29/25 12:34 AM, andy pugh wrote:
> There are three things that I would like to see in 2.10, only one of 
> which is likely to be uncontentious.[snip]
I think the HAL name length should be increased from the current 47 to 
something more substantial, like 127 or 255. I've run into and over the 
limit several times.

And, running over the limit can cause some interesting crashes where you 
would not expect it (and hard to debug). Sure, the length checks should 
have been there everywhere, but they are not. The error tests and 
controls are apparently too lax.

That also invites the thought that many components need to be updated to 
perform proper and consistent error checking, through and through. 
Possible errors at module load/init time are not always handled or 
handled properly.


While we're at it, the shared mem size could also be upped (maybe to 48M 
or 64M) as there are no longer real issues with physical memory pressure 
anyway. The data sets have also become larger with the transition to 
64-bit systems.

-- 
Greetings Bertho

(disclaimers are disclaimed)

Re: [Emc-developers] 2.10 Proposals

[Jon E. <el...@pi...>]

On 10/29/25 12:33, andy pugh wrote:
> On Wed, 29 Oct 2025 at 17:00, Jon Elson <el...@pi...> wrote:
>
>> Yes, this is what I'm concerned about.  How does a negative
>> signed 32-bit value get converted to 64-bit?  There are
>> 32-bit encoder counts
> There won't be when I have finished.
> At least not inside LinuxCNC drivers.
> There may be 32-bit input sources, but I am not aware of any. ppmc
> appears to sign-extend 24 bits to 32. That will be expanded to 64.
> There are 16-bit input sources (Modbus and Smart-serial for example)
> but those are already sign-extended (and in many cases are _already_
> internally 64-bit)

Specifically in my ppmc encoder driver section, I remember 
some fancy footwork looking at the sign of the 24-bit values 
and the sign and next bit of the 32-bit extension, to decide 
when a rollover is required.  This took some hard thinking 
and testing to get right.

Jon

[Emc-developers] Trajectory planner velocity, non trivial kinematics?

[Nicklas SB K. <nk...@nk...>]

Have looked on the general serial kinematics module and it seems the jacobian  is calculated but never used. Also
started to read thru the code for the trajoctory planner. Got the impression the trajectory planner does not handle
velocity constraints for joints velocities or accelerations properly?

If this is the case. Anyone know if someone started a branch for this? Any other documents like for example scientific
articles or similar on the topic?



Regards Nicklas Karlsson

Re: [Emc-developers] 2.10 Proposals

[rodw <ro...@ve...>]

Ref:   https://linuxcnc.org/docs/stable/html/config/ini-config.html#sub:ini:sec:traj

TPMOD =   alternate_trajectory_planning module   [tp_parms=value]

The   TPMOD   variable is optional. If specified, use a specified (user-built) module instead of the default (tpmod). Module parameters (tp_parms) may be included if supported by the named module. The setting may be overridden from the command line using the -t option ($ linuxcnc -h).

Its very easy to modify the build system to include an extra folder.
Rod
 
On 2025-10-29 22:11, andy pugh  <bod...@gm...>  wrote:
> On Wed, 29 Oct 2025 at 07:57, rodw  <ro...@ve...>  wrote:
> >
> >  Given the TP is supposed to be a stand alone module, why don't you deploy the Tormach planner (lets call it TTP) to /src/emc/ttp and allow users to experiment with it on real hardware by changing their ini file settings?
>
> Are you sure this is the case? Which INI file setting?

Re: [Emc-developers] 2.10 Proposals

[andy p. <bod...@gm...>]

On Wed, 29 Oct 2025 at 17:00, Jon Elson <el...@pi...> wrote:

> Yes, this is what I'm concerned about.  How does a negative
> signed 32-bit value get converted to 64-bit?  There are
> 32-bit encoder counts

There won't be when I have finished.
At least not inside LinuxCNC drivers.
There may be 32-bit input sources, but I am not aware of any. ppmc
appears to sign-extend 24 bits to 32. That will be expanded to 64.
There are 16-bit input sources (Modbus and Smart-serial for example)
but those are already sign-extended (and in many cases are _already_
internally 64-bit)
 (in fact in smart-serial there can be 8-bit encoder counter values
extended to 64)

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

Re: [Emc-developers] 2.10 Proposals

[Peter W. <pc...@me...>]

On Wed, 29 Oct 2025, Robert Schöftner wrote:

> Date: Wed, 29 Oct 2025 17:46:45 +0100
> From: "Robert [ISO-8859-1] Schöftner" <rm...@un...>
> Reply-To: EMC developers <emc...@li...>
> To: emc...@li...
> Subject: Re: [Emc-developers] 2.10 Proposals
> 
> Am Mittwoch, dem 29.10.2025 um 09:17 -0700 schrieb Peter Wallace:
>>
>> Yes, many components/drivers have parameters rather than pins for
>> this reason.
>>
>> In many cases, parameters are not expected to change at run time and
>> if
>> changed may cause issues.
>>
>>
>
> Even now you can change parameters at runtime ("setp" in halcmd)
>
> It's not like the concept of a parameter will be removed. It is a HAL-
> internal change that will allow the code to get rid of a bunch of
> pin/parameter checks und duplicated slightly different code.
>
> rene_dev could probably tell a bit more...
>


As long as its just internal changes, but changing the external hal pin type 
removes a way of indicating statics which are used in many components and 
drivers.

>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

Peter Wallace
Mesa Electronics