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 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 best chance at fitting into factory > > > automation, CNC machines and robotics of the near future (next 20 > > > years)? Will this best solve the issues of separating the > > > controls > > > from the GUI over the network as well as connect LCNC to factory > > > controls and robot material handlers? Is this mission creep or > > > killing two birds with one stone? > > > > Bari, > > > > I tend to agree that this is a good solution. In looking at the > > openDDS project I see that the project has been forked 408 times on > > github including my own fork. It also has a good developers guide > > that > > contains some 249 pages of information and also has the required > > support package for TOA available which has development guide that > > has > > some 1262 pages. OpenDDS seems like it has good documentation on > > its > > own and thus only requires LinuxCnc documentation to be added on > > how > > to get it to install and get it working with LinuxCnc. > > > > I think that working on this is much more beneficial to LinuxCnc > > than > > my previous concept which obviously does not have a lot of support > > so > > I may as well forget about working on that. But that does not mean > > that the requirement for improved network capability does not > > exist. > > > > OpenDDS has its own own development team which thus requires less > > support from the LinuxCnc development team. All that needs to be > > done > > is to get it working within LinuxCnc. So my intention is to work on > > helping to accomplishing that. OpenDDS uses CorBa instead of Redis > > so > > Redis will most likely not be required. > > > > My starting point for this project is to get openDDS working > > inside > > and in parrallel with current LinuxCnc master code, without > > changing > > LinuxCnc code and to only add the code required to make openDDS > > functional within LinuxCnc. Once it is functioning and able to run > > simple self tests then start working on routing individual > > LinuxCnc > > commands along with the status data of those into openDDS and route > > those to an prior developed Labview based UI running on a Windows10 > > computer. That will be helpful with checking the networking > > functions > > and any debugging work. Labview has some tools that are very handy > > for > > doing that but others joining the project could decide use any UI > > that > > has remote ability for there own testing. > > > > This seems like an excellent project to undertake and I'm somewhat > > excited about getting started on this project. OpenDDS appears to > > have good support and is already being used for such purposes. I > > have > > downloaded what I believe to be all required items for installation > > and will get my Debian development system set up to start doing > > work > > on this before the end of the year. > > > > > Sounds great. Let us know when you have a public repo so that we can > follow your deep dive into this. > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
