Re: [Emc-developers] EtherCAT, read esi *.xml file
Parsing of ESI files, *.xml files would probably be A good idea. I ran hardcoded now and at a first glance it seems source code below also do this. I have seen siitool parse xml file and it would probably not be to hard to reuse code from this tool. As position out and encoder in plus a few other signals is the only thing I need I stay with hardcoded right now but at the time I get the need for other signals buying an Ethercat module and add parsing of esi file I will probably do. On Mon, 25 Mar 2019 13:56:48 + andy pugh wrote: > Whilst I think we have decided that it is not possible to distribute > an EtherCAT driver with LinuxCNC[1] it seems that some users are using > it extensively and successfully. > > Which leads me to wonder if we should include a section in the > documentation about its use and where to download the enabling > software? > > [1] Though where the license-break is is not clear: > Sascha's HAL driver is GPLv2: > https://github.com/sittner/linuxcnc-ethercat but I seem to recall that > actual use of EtherCAT involves an implied compliance with the > Beckhoff terms. > There is a summary here in an old machinekit discussion: > https://groups.google.com/forum/#!search/machinekit$20beckhoff/machinekit/yxQxqNbMvtc/UsaYVfAarCsJ > > -- > 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, 1916 > > > ___ > 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
Re: [Emc-developers] Update-ini script
FYI -Original Message- From: Chris Morley Sent: mercredi, 27 mars 2019 01:56 To: EMC developers Subject: Re: [Emc-developers] Update-ini script According to the note in 2.8 : http://linuxcnc.org/docs/devel/html/config/ini-homing.html#_home_sequence Not specifying the sequence at all will make it not respond to ALL Home Where as in 2.7 either not specifying it or setting it to -1 did the same. So it seems if you see -1 in a 2.7 config you must remove the line for it to be the same in a 2.8 config. Chris M From: andy pugh Sent: March 25, 2019 9:55 PM To: EMC developers Subject: [Emc-developers] Update-ini script I have just realised that the current (2.7) docs suggest a home-sequence value of -1 to disable homing of a joint. With JA in 2.8 that is no longer a particularly good idea. I think that the update-ini script needs to treat that situation specially. But what should it do? It's non-trivial in the current structure of the script to set home search velocity to zero in the INI if the sequence number is -1. But I think that is what I might need to do. Or would a number not-contiguous with the homing sequence have the same effect? -- 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, 1916 ___ 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 ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
