Re: [etherlab-users] CoE Example

2013-11-05 Thread Sebastien Blanchet
Hi, This is a CoE example with Kollmorgen AKD servo drive. http://lists.etherlab.org/pipermail/etherlab-users/2012/001684.html regards --- sebastien On 11/05/2013 11:29 PM, Steve Hartmann wrote: Hi Folks, I've been experimenting with the master stack for a few weeks now. I used the provided

Re: [etherlab-users] Looking for Slave firmware update example

2013-11-05 Thread Gavin Lambert
Ah, I missed that in the docs. I suppose it could be needed for the device to finalise something about the upload internally, though that would seem unusual. But IIRC those particular devices have to be sent SDO parameters before they’ll accept going to OP anyway. The docs look like generic (not

Re: [etherlab-users] Looking for Slave firmware update example

2013-11-05 Thread Graeme Foot
Thanks. The documentation for this module (from Beckhoff) doesn't mention that a filename should be set so I will go with the default .efw filename. The documentation says to change to OP at the end. I can't see that it would be necessary either. Graeme. From

Re: [etherlab-users] Looking for Slave firmware update example

2013-11-05 Thread Gavin Lambert
The change to OP seems wrong, but otherwise the procedure below looks about right. One thing to note is that the foe_write command takes two filenames – the other you’ve left unspecified (and so will default to the .efw filename) is the internal name sent to the device. You’ll have to check wi

[etherlab-users] CoE Example

2013-11-05 Thread Steve Hartmann
Hi Folks, I've been experimenting with the master stack for a few weeks now. I used the provided examples as a starting point for some simple programs to communicate with several different beckhoff slices. All that was pretty straight-forward. Now, I need to do some work with a Copley Accelne

[etherlab-users] Looking for Slave firmware update example

2013-11-05 Thread Graeme Foot
Hi, I want to update the firmware on an EtherCAT slave (an EL6021 module). I'm using the latest 1.5.2 master. I take it that I need to use the "ethercat foe_write" command but I haven't been able to find what "output-file" name I should be using. Should it be the name of the .efw file (or no

Re: [etherlab-users] Problems with Pdo entry with index 0x0000

2013-11-05 Thread Florian Pose
Hello, On Mon, Nov 04, 2013 at 05:40:52PM +, Thomas Bitsky Jr wrote: > // Register startup configuration for the hardware > // > > ecrt_slave_config_sdo8( sg->sc, 0x1C12, 0, 0 ); /* clear sm pdo 0x1c12 */ > ecrt_slave_config_sdo8( sg->sc, 0x1C13, 0, 0 ); /* clear sm pdo 0x1c12 */

Re: [etherlab-users] Problems with Pdo entry with index 0x0000

2013-11-05 Thread Florian Pose
Hello, On Tue, Nov 05, 2013 at 04:36:26PM +0100, Richard Hacker wrote: > I understand your problem when registering gaps. Actually the code > in the ethercat master does not do the right thing by testing on > index. Actually it should be testing for reg->bit_position instead. > I will communicate

Re: [etherlab-users] configure: error: kernel 3.8 not available for 8139too driver!

2013-11-05 Thread Jeroen Van den Keybus
I'm currently running ec_master/ec_generic kernel 3.8.13. No compile issues. J. 2013/11/5 Richard Hacker > Sorry, at the moment e100 is only supported for kernel 3.4 natively. Your > luck may vary using the generic driver, but as you see it is broken for 3.8 > (VM_RESERVED is not defined any

Re: [etherlab-users] Problems with Pdo entry with index 0x0000

2013-11-05 Thread Jordi Blanch
Hello Richard, thank you very much for your answer. We will solve the issue as you mention. Best regards. On Tue, 05 Nov 2013 16:36:26 +0100, Richard Hacker wrote: > Hello, > > I understand your problem when registering gaps. Actually the code in > the ethercat master does not do the right thi

Re: [etherlab-users] working counter error after long time running

2013-11-05 Thread Richard Hacker
That looks like timing issues. It could also be hardware, but since you say this happens after process start, I think this is not really relevant. Try to figure out your jitter or even overruns. You could increase debugging level and try to figure out what the master says Am 11/04/2013 10:55

Re: [etherlab-users] configure: error: kernel 3.8 not available for 8139too driver!

2013-11-05 Thread Richard Hacker
Sorry, at the moment e100 is only supported for kernel 3.4 natively. Your luck may vary using the generic driver, but as you see it is broken for 3.8 (VM_RESERVED is not defined any more in 3.8). You will need to drop down to earlier versions unfortunately. Am 11/05/2013 06:24 AM, schrieb Muh

Re: [etherlab-users] Problems with Pdo entry with index 0x0000

2013-11-05 Thread Richard Hacker
Hello, I understand your problem when registering gaps. Actually the code in the ethercat master does not do the right thing by testing on index. Actually it should be testing for reg->bit_position instead. I will communicate this with the developer. Meanwhile you could use ecrt_domain_reg_p

Re: [etherlab-users] Problems with Pdo entry with index 0x0000

2013-11-05 Thread Jordi Blanch
Dear Thomas, thank you for your answer, but I think I haven't explained clearly enough. Our problem is not how to create the ec_pdo_entry_info_t array, we create it from the xml file and the result is exactly the same you have included in your email, our problem is that after passing this ec_pdo_e