[etherlab-users] Slave development: automated generation of ESI and SSC files

Dave Page dave.page at gleeble.com
Mon Dec 16 20:45:58 CET 2013


Hi,

     To make Beckhoff SSC (ET9300) project creation and maintenance a 
little easier, I put together a python script which inputs a .mesi (Meta 
ESI) file and outputs ESI XML,SII EPROM, SSC CoE C and header files. The 
.mesi file is a C-like description of the CoE objects and other 
configuration information. The goal is to automate EtherCAT compliance 
to the extent practicable and provide a DRY (don't repeat yourself) 
automated build for the required files.

     Project is here:
https://sourceforge.net/p/mesicat/wiki/Home/

     The C code generation uses mustache templates. Potentially, other 
slave stacks could be supported with new template files. Further, 
template files could be generated to at least sketch out slave device 
support for custom master modules under etherlab -- this is something I 
will be doing eventually.

     This project is alpha quality, and much remains to be done to make 
it completely usable. Regardless, I am using it with an internal 
project, and the output works for me (and I don't have to ever look at 
an XML file when I change a PDO).

         Best regards - Dave Page

------------------------------------------------------------------------
David Page, Chief Embedded Architect
Dynamic Systems Inc.
PO Box 1234
Poestenkill, NY 12140
Telephone: +1 (518) 283-5350 | Fax: +1 (518) 283-3160 |
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20131216/5ed95a1e/attachment-0002.htm>


More information about the Etherlab-users mailing list