Hello,
Because the supplier of our slaves told us that their SII information will
never fit in the slave (the SII binary is 3kb and the slave only has a 2kb
memory location) and we're stuck with 14 of them I've cleaned up the hack to
read the SII information from a binary file and made it work in combination
with other slaves. If someone is interested I can make a patch to the most
recent master code.
I've adjusted the fsm_slave_scan state machine to works as follows
- Read vendor id + product code from slave
- Use the kernels firmware_request to load ec_${vendor_id}_${product_code}.bin
/lib/firmware/${uname -r}/ethercat (or whatever path your distribution uses)
If firmware is found,
use that to load the SII information
else
read SII information from the slave
I think this can be used as starting point for reading XML files. I'm thinking
of the following solutions
- Make a separate user space program that compiles the XML files to SII
binaries and stores them in /lib/firmware
- Store the XML file in /lib/firmware and parse it in the master module
- Create a separate communication between the kernel and user space that
requests slave information from a daemon/udev.
Maybe someone on this list can voice their opinion what would be the neatest
way to do it.
Regards,
Jesper
Op donderdag 25 augustus 2011 16:13:02 schreef Jesper Smith:
> Thank you for this information. I just found out I cannot even set the
> station alias, even from twincat. I hacked ethercat to use a binary eeprom
> file instead of reading it from the slave and that seems to work, aka I can
> talk to the slave.
>
> Regards,
>
> Jesper
>
> Op donderdag 25 augustus 2011 15:36:56 schreef Andreas Stewering-Bone:
> > Hello Jesper,
> >
> > sorry, but that is question for florian.
> >
> > Best regards
> >
> > Andreas
> >
> > Am 25.08.2011 15:14, schrieb Jesper Smith:
> > > Hello Andreas,
> > >
> > > Unfortunatly the slave doesn't accept a new Eeprom (it accepts the
> > > data
> > > fine, but doesn't update anything). I'm trying to contact the
> > > manufacturer but they are hard to reach. Also, I suspect the Eeprom
> > > is
> > > 2048kb, but the data from the XML file takes 3072kb.
> > >
> > > How hard would it be to have Etherlab use XML files instead of
> > > reading
> > > the SII information?
> > >
> > > Best Regards,
> > >
> > > Jesper
> > >
> > > Op donderdag 25 augustus 2011 09:02:14 schreef Andreas Stewering-Bone:
> > >> Hello Jesper,
> > >>
> > >> It is always the same I think.
> > >>
> > >> TwinCAT works without reading the Slave Eeprom.
> > >>
> > >> Our master tries to read out some information form the Eeprom.
> > >> Only a small amount of slave producer build up their Eeprom
> > >> content
> > >> properly.
> > >> Here the final end tag is missing.
> > >>
> > >> You can do
> > >>
> > >> - Backup the Eeprom via ethercat sii_read -p slaveid> file
> > >> - Build up a new Eeprom content in TwinCAT based on the XML
> > >> Description.
> > >> - Save this file to the Slave via ethercat sii_write -p slaveid
> > >> filename
> > >>
> > >> Power down the bus, restart everything.
> > >>
> > >> See if the message is gone.
> > >>
> > >> Best regards
> > >>
> > >> Andreas
> > >>
> > >> Am 24.08.2011 21:02, schrieb Jesper Smith:
> > >>> I'm testing an Elmo Gold Guitar Solo in combination with
> > >>> Ethercat.
> > >>> Using TwinCAT I can get it to work. Using SOEM (simple open
> > >>> ethercat master) I'm able to read the configuration (SDO),
> > >>> however
> > >>> when I connect it to the Ethercat master I get the following
> > >>> error
> > >>>
> > >>> EtherCAT WARNING 0-0: SII size exceeds 4096 words (0xffff
> > >>> limiter
> > >>> missing?).>
> > >>>
> > >>> What is wrong with the slave or is it an error in etherlab?
> > >>>
> > >>> Regards,
> > >>>
> > >>> Jesper
> > >>> _______________________________________________
> > >>> etherlab-users mailing list
> > >>> [email protected]
> > >>> http://lists.etherlab.org/mailman/listinfo/etherlab-users
> > >>
> > >> Mit freundlichem Gruß
> > >>
> > >> Andreas Stewering-Bone
> > >
> > > _______________________________________________
> > > etherlab-users mailing list
> > > [email protected]
> > > http://lists.etherlab.org/mailman/listinfo/etherlab-users
> >
> > Mit freundlichem Gruß
> >
> > Andreas Stewering-Bone
>
> _______________________________________________
> etherlab-users mailing list
> [email protected]
> http://lists.etherlab.org/mailman/listinfo/etherlab-users
_______________________________________________
etherlab-users mailing list
[email protected]
http://lists.etherlab.org/mailman/listinfo/etherlab-users
