Ok so just for future info. I did figure this out. The beckhoff drives are programmed in big endian so all data is essentially reversed from network byte order. The way that twincat software dumps xml is the proper format for linuxcnc-ethercat driver.
Thanks, Curtis On Wed, Oct 9, 2019 at 8:45 AM Curtis Dutton <curtd...@gmail.com> wrote: > I have successfully built and configured master, ethercat drivers and > linuxcnc-ethercat and applied the pll timing patch on debian buster. > > Converting and existing machine. Ethercat working, all io boards > talking....Ethercat here we go! > > The next step was to configure the SDO's on the beckhoff AX5000 drives. So > naturally I loaded up the Twincat on windows and exported the xml > configurations for the drives. > > After configuring the slaves to use the initialization xml from twincat, I > get errors and the drives won't go into operational mode. > > After half a day of hair pulling I think that I found out that the byte > ordering from twincat xml files is little endian (intel byte ordering) and > that linuxcnc-ethercat takes data in big endian (network) endian. Yes I > read through the epic 10000 post forum thread to find this out. > > Is that correct? If I reverse the data values in the sdo config to big > endian my drives will initialize? > > Thanks, > Curtis > _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
