On Wed, Feb 17, 2010 at 12:21:55AM +0100, Mladen Knezic wrote: > I'm using the latest EtherCAT version found in etherlab.org/download section > (ethercat-devel-r1284).
You mean 1824? The development version can now be found on SourceForge. I think I will remove all development releases from the download section. Does anyone have an objection? > Screenshot that shows error message in Simulink is attached as well as output > of EtherCATInfo() function in Matlab. > > I also found some differences between actual xml file generated (that I sent > in previous post) and the output of 'ethercat xml' command (attached as .txt > file) in which the famous 'Invalid bit length 2' messages appear on lines 111 > and 119 (this is also shown when 'ethercat xml -p0 >> > FB1111_EtherCATInfo.xml' command is used). Ok, we'll check that. > One more question: Why, for example, already included block device's xml file > (such as EL1004) cannot be included in generic device block? Is there some > kind of code that prevent this or is it something else (this try results in > xml file being ignored by generic block)? The vendor slave description XMLs usually contain a number of variants of PDO configuration etc., that have to be chosen by the user. For using the generic slave block, the best input is a file containing a device with a fix PDO configuration (like generated by 'ethercat xml'). -- Best regards, Florian Pose http://etherlab.org _______________________________________________ etherlab-users mailing list [email protected] http://lists.etherlab.org/mailman/listinfo/etherlab-users
