I had made some changes in my note file names to add .txt file
extension. Its liklye best the use the main link to navigate to my notes
and other info when posted.
https://github.com/auto-mation-assist/LinuxCnc-OpenDDS-Work
After running the 6 tests it completed so far makes me confident
On 12/18/22 18:24, Johannes Fassotte wrote:
I had a chance to do some work on OpenDDS while waiting for parts for
another project. I installed OpenDDS with its depends on my Linux Mint
20 development computer and made some notes on how I installed it and
all the depends. I have not checked
I had a chance to do some work on OpenDDS while waiting for parts for
another project. I installed OpenDDS with its depends on my Linux Mint
20 development computer and made some notes on how I installed it and
all the depends. I have not checked out the built in tests yet described
in the
Le ven. 16 déc. 2022 à 16:09, Steffen Moeller a écrit :
>
> I sense that there is an agreement that everyone would like such a
> distribute CNC meta-layer to emerge. Should this thread not somehow be
> transferred into some wiki page or so such that we can operationalize a
> bit on what needs to
I sense that there is an agreement that everyone would like such a
distribute CNC meta-layer to emerge. Should this thread not somehow be
transferred into some wiki page or so such that we can operationalize a
bit on what needs to be done and to find volunteers to address the
identified tasks?
Let us know if anyone find any negatives to openDDS besides some complexity.
On 12/6/22 15:41, Nicklas SB Karlsson wrote:
Read that DDS include application programming interfaces (APIs) and
libraries of implementations in among others ADA and that's great.
Read that DDS include application programming interfaces (APIs) and
libraries of implementations in among others ADA and that's great.
tis 2022-12-06 klockan 13:55 -0600 skrev Bari:
> On 12/5/22 15:21, Johannes P Fassotte wrote:
>
> >
> > On 12/5/2022 6:10 AM, Bari wrote:
> > > A pdf that
On 12/5/22 15:21, Johannes P Fassotte wrote:
On 12/5/2022 6:10 AM, Bari wrote:
A pdf that explains where DDS fits in to industry
https://www.dds-foundation.org/sites/default/files/RTILunchAddressOMG2014v2.pdf
If we use DDS it might make LCNC compatible with the industry of the
future. Is
> Thanks for correcting my outdated information!
My statement:
" The commit 2dbb2f640f changed the interface between
EMCIO and TASK to use a memory mapped interface."
was incomplete and not really accurate.
To clarify:
The tooldata interface was altered to use a memory mapped
interface
On 12/5/22 16:18, Steffen Möller wrote:
I see a distributed control system. Many units that know the units that are
neighboured (i.e. that they cooperate with) but do not need to see the complete
world. And if the neighbours are allowed to be dynamic, then tis would then
even work with
On 12/5/22 15:18, Steffen Möller wrote:
It would make some good sense to me not to use DDS that currently runs in the
base thread.
The base thread and servo thread both currently do not communicates via
NML, and I don't think anyone(?) is suggesting changing that.
NML communication is
> Gesendet: Montag, 05. Dezember 2022 um 21:12 Uhr
> Von: "Bari"
> An: emc-developers@lists.sourceforge.net
> Betreff: Re: [Emc-developers] A vision for working now to LinuxCnc version 10
>
> On 12/5/22 10:57, Steffen Möller wrote:
>
> >
> > I guess any such industrial decision making is
On 12/5/2022 6:10 AM, Bari wrote:
A pdf that explains where DDS fits in to industry
https://www.dds-foundation.org/sites/default/files/RTILunchAddressOMG2014v2.pdf
If we use DDS it might make LCNC compatible with the industry of the
future. Is everyone jumping onto the DDS bandwagon? Which
On 12/5/22 10:10, Bari wrote:
A pdf that explains where DDS fits in to industry
https://www.dds-foundation.org/sites/default/files/RTILunchAddressOMG2014v2.pdf
If we use DDS it might make LCNC compatible with the industry of the
future. Is everyone jumping onto the DDS bandwagon? Which
On 12/5/22 10:57, Steffen Möller wrote:
I guess any such industrial decision making is equally based on the "unknown"
when it comes to interoperability. The EU funds (did fund?) COST actions for this purpose
- bring industrial and academic partners together and squeeze something like a joint
> Gesendet: Montag, 05. Dezember 2022 um 17:33 Uhr
> Von: "Johannes Fassotte"
> An: "EMC developers"
> Betreff: Re: [Emc-developers] A vision for working now to LinuxCnc version 10
>
> DDS looks very interesting and I will plan to look into it more today. Thanks
> for the link to DDS. Future
DDS looks very interesting and I will plan to look into it more today. Thanks
for the link to DDS. Future compatibility with other industrial work is very
important and highly desirable.
Johannes -
Fairbanks, AK 99712
> On Dec 5, 2022, at 6:13 AM, Bari wrote:
>
> A pdf that explains where
A pdf that explains where DDS fits in to industry
https://www.dds-foundation.org/sites/default/files/RTILunchAddressOMG2014v2.pdf
If we use DDS it might make LCNC compatible with the industry of the
future. Is everyone jumping onto the DDS bandwagon? Which messaging
system will gives us the
> Gesendet: Montag, 05. Dezember 2022 um 03:16 Uhr
> Von: "Bari"
> An: emc-developers@lists.sourceforge.net
> Betreff: Re: [Emc-developers] A vision for working now to LinuxCnc version 10
>
> On 12/4/22 19:08, Steffen Möller wrote:
>
> >
> >> Gesendet: Sonntag, 04. Dezember 2022 um 23:39 Uhr
>
On 12/4/22 19:08, Steffen Möller wrote:
Gesendet: Sonntag, 04. Dezember 2022 um 23:39 Uhr
Von: "Chris Morley"
An: "EMC developers"
Betreff: Re: [Emc-developers] A vision for working now to LinuxCnc version 10
My work on this will continue, initially getting the required network
code in
> Gesendet: Sonntag, 04. Dezember 2022 um 23:39 Uhr
> Von: "Chris Morley"
> An: "EMC developers"
> Betreff: Re: [Emc-developers] A vision for working now to LinuxCnc version 10
>
>
>
> >My work on this will continue, initially getting the required network
> >code in place for both TCP and
>My work on this will continue, initially getting the required network
>code in place for both TCP and UDP connections and also the Redis base
>to handle the distribution of Cmd, Status and Error data to where ever
>it is needed. Once that is done change my routing commands away from the
>NML
On 12/4/22 08:16, Dewey Garrett wrote:
A correction:
NML is used between the GUI(s) and Task, and between Task and IO.
The commit 2dbb2f640f changed the interface between
EMCIO and TASK to use a memory mapped interface.
This facility has been in use in the master branch
since its
A correction:
> NML is used between the GUI(s) and Task, and between Task and IO.
The commit 2dbb2f640f changed the interface between
EMCIO and TASK to use a memory mapped interface.
This facility has been in use in the master branch
since its incorporation in January 2021 and is
currently
On 12/3/22 19:20, Jon Elson wrote:
Underneath HAL there is NML that links major sections of LinuxCNC
together and makes the state of major components available. NML exports
the ENTIRE state of everything to all clients. This is doable on a
single computer system, but causes issues on
On Dec 3, 2022, at 10:58 AM, Chris Morley
wrote:
Have you looked at machinekit code? Is that similar to what you
want?
On 12/3/22 17:06, Johannes Fassotte wrote:
> I think that this will get done individuals like me that get together
> and see the advantages that this offers. I usually get
lör 2022-12-03 klockan 21:22 +0100 skrev Steffen Möller:
> Hello,
>
> > My goal for LinuxCnc is to provide a way for any user to interface
> > any
> > UI to LinuxCnc with a secure TCP network connection.
>
> There are remote shells to HAL but I agree - would also like to see a
> bit more of
lör 2022-12-03 klockan 16:57 -0800 skrev chris morley:
>
> On 2022-12-03 16:06, Johannes Fassotte wrote:
> > I’m fairly familiar with machine kit and it has nothing to do with
> > that. It has strictly to do with modernizing the built in remote
> > interface that Linuxcnc was born with..
>
> ok
On 12/3/22 18:57, chris morley wrote:
I am not sure why you are hostile. I am really trying to
understand exactly what you want. Machinekit did work on
networking, though I think it was just HAL. It's why I
mentioned it.
Underneath HAL there is NML that links major sections of
LinuxCNC
I could see this being implemented in lights out machining facilities which
would be fantastic! Even low end 3d printers are utilizing this type of
remote interface which is great for letting machines run on there own and
keeping users updated as to issues or completion of prints so that the
On 2022-12-03 16:06, Johannes Fassotte wrote:
I’m fairly familiar with machine kit and it has nothing to do with that. It has
strictly to do with modernizing the built in remote interface that Linuxcnc was
born with..
ok You must realize almost no one uses the networking capability of
I’m fairly familiar with machine kit and it has nothing to do with that. It has
strictly to do with modernizing the built in remote interface that Linuxcnc was
born with..
I think that this will get done individuals like me that get together and see
the advantages that this offers. I usually
Hello,
> My goal for LinuxCnc is to provide a way for any user to interface any
> UI to LinuxCnc with a secure TCP network connection.
There are remote shells to HAL but I agree - would also like to see a bit more
of remote control. My motivation is less about the distance than it is about
Have you looked at machinekit code? Is that similar to what you want?
Chris
Sent from my Galaxy
Original message
From: Johannes P Fassotte
Date: 2022-12-03 11:48 a.m. (GMT-08:00)
To: emc-developers@lists.sourceforge.net
Subject: [Emc-developers] A vision for working now
On Fri, 2 Dec 2022 at 18:43, Johannes P Fassotte <
johan...@automationassist.com> wrote:
> I also feel
> that there is way to much resistance by the LinuxCnc developers to
> implement what many of us may see as a absolute requirement.
1) This is the first time that I have heard this
Johannes,
Thank you for your thoughts and time to put this in writing.
I mostly agree with a few exceptions.
NML should be changed to DDS for easier compatibility with ROS2
https://www.ros.org/
LCNC development is all voluntary and the current devs are already
capacity with their time,
36 matches
Mail list logo
