-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I suppose I'll answer my own question in case anyone else is ever curious about this.
The method I used to integrate the FB1111-0142 Piggy Back Controller is as follows: (1) Pull configuration from slave at position 5 'ethercat xml -p 5 >> FB1111_EtherCATInfo.xml' (2) Use the generic slave block from the EtherLab Simulink Blockset (3) Convert the xml file to matlab object and save it to the workspace >> FB1111_EtherCATInfo = EtherCATInfo(/some/path/FB1111_EtherCATInfo.xml); >> save FB1111_EtherCATInfo (4) Populate the EtherCATInfo field in the mask properties for the generic slave with '/some/path/FB1111_EtherCATInfo)' Easy enough. As a follow on, are there any known limitations to this technique? Obviously you're at the mercy of the factory configuration. Clearly I'm new to both RTW and EtherCAT/Etherlab, so I'll thank you all in advance for any advice or tips. Matt Jackson Hardware Engineer JT3 LLC - RDESI -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktXuVUACgkQuvUgL4oki55xMQCghKGyMhHw6kJNVMRY44KhGm9Q tZIAoIpYvJemVNS2JpcEY1F5GgA1HPHL =d7S9 -----END PGP SIGNATURE----- _______________________________________________ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
