No. That command is used to generate a file containing the PDO structure of an existing slave on the network for consumption by the EtherLab higher-level MATLAB/Simulink app (not the master itself). It’s not an input file.
The Etherlab master does not support use of ENI or ESI XML files in any way at present. They are all just text files, though, so it’s possible to manually convert one to the other, or to write a tool that does so. But I am not aware of any existing tools that do this. From: Erik Euving Sent: Tuesday, 21 February 2017 10:29 To: etherlab-users@etherlab.org Subject: [etherlab-users] Twincat XML description file to Matlab Hello all! For those with strong memory, you will recognise the subject from this email in 2015: <http://lists.etherlab.org/pipermail/etherlab-users/2015/002829.html> http://lists.etherlab.org/pipermail/etherlab-users/2015/002829.html I have Yorick's exact question: can I use the > ethercat pdos --skin etherlab <name>.m with an existing xml file rather than a slave? My slave (the D1-N Drive by Hiwin) provides a rather inadequate xml file, so I made my own using the Ethercat Configurator tool. And now I wonder whether I can produce the wanted m-file from this. I looked into every email from 2011 to 2017 and did not find something I understood, so hopefully someone is willing to help me out! Thanks, and apologies if I'm missing the obvious! Cheers, Erik
_______________________________________________ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
