Hi Gavin,
On Wed, Apr 9, 2014 at 3:40 AM, Gavin Lambert gav...@compacsort.com wrote:
On 8 April 2014, quoth Jun Yuan:
Thank you so much for the test. I am sorry for the formatting error.
I should test it before send it out but I didn't have the chance.
I think this was actually from the
Dear Ethercat users,
During my tries to get the ethercat driver working, I got stuck on two
computers.
The first computer is a raspberry pi. Here, I run a ported kernel especially
for raspberry pi.
My problem: I can perfectly do a ./ethercat restart. The ethercat driver
stops and comes back
Dear helper
Sometimes in a couple of hours or more we receive this messages in
the syslog :
Apr 7 07:31:33 (none) kernel: EtherCAT 0: Domain 0: Working counter
changed to 0/113.
Apr 7 07:31:33 (none) kernel: EtherCAT DEBUG 0: Skipping datagram
8802111b8828 (state=FRMW node=1
On 09/04/14 14:49, Martin Troxler wrote:
On 09.04.2014 14:02, pier wrote:
Dear helper
Sometimes in a couple of hours or more we receive this messages in
the syslog :
Apr 7 07:31:33 (none) kernel: EtherCAT 0: Domain 0: Working counter
changed to 0/113.
Hi Pier
If your realtime tasks
Hi all,
I have written some code to parse the generated XML file from ethercat xml
and use that to configure the ethercat stack. The problem I am having is the
output from ecrt_slave_config_ret_pdo_entry produces overlapped offsets. I
also tried using ecrt_slave_config_reg_pdo_entry_pos with
Hi Dave,
Thanks for the reply. I am not using TwinCAT at all. Also, please forgive my
ignorance, but what is the LRW command.
I'm not sure how to deal with this with the etherlab stack. If it give me a
domain offset of 3 for two different slices (one input and one output), how do
I deal
In order to reduce process data size, TwinCAT overlaps the RxPDO
and TxPDO for each module, then uses the LRW command to effect the
transfer. So, I believe what you're seeing is normal.
Best regards - Dave Page
On 09-Apr-14 15:41, etherlab-users-requ...@etherlab.org wrote:
Hi Dries,
I seem to remember that the latest Linux kernel the master works on is 3.4.
Damien
From: etherlab-users-boun...@etherlab.org
[mailto:etherlab-users-boun...@etherlab.org] On Behalf Of dries geentjens
Sent: Wednesday, 9 April 2014 9:04 PM
To: etherlab-users@etherlab.org
Subject:
Another confusing thing I see is ecrt_slave_config_ret_pdo_entry() reports
offsets as large as 10, but when I call ecrt_domain_size(), it reports a size
of 7. Since the PD buffer is a pointer to uint8_t, I am assuming the size
reported is in bytes.
Thanks,
Steven
From: Steven Hartmann
It also returns an error if something does not byte-align and you provide
NULL for the bit_position argument. So you shouldn't see any overlapping
offsets as a result of this unless you're throwing away data.
From: etherlab-users-boun...@etherlab.org
Hi Steve,
Typically you don't need to worry about data overlaps at all. I'm not sure
if the Etherlab master generates them in the first place (though your XML
output suggests that it does), but even if it does it should only do so in
cases when it is safe. (In particular, if you have a
Hi Dave,
I do use the bit_position argument. The first slice (16 channel DI) uses
offsets 2 3, bit positions 0-7 of each. The second slice is a 4 channel DO
and uses Domain offset 3, bits 0-3. Also,, the third slice (2 channel AO) has
an entry at offset 6, 16 bits while the next slice (2
Hi Gaven,
So, the reason I started down this road is because it does not work for the
most part. I can get the DO channels to work, but nothing else seems to work.
So, if an input and and output PDO have the same offset into the process data
image that I grabbing data from and poking data
Not sure. It is not uncommon to have 'gap' or 'pad' data which is
otherwise unused. As to the overlap, ecrt_slave_config_reg_pdo_entry
(see master/slave_config.c:739) just scans all the PDOs in order summing
their lengths until the argument PDO is reached. Thus, the logical
address
14 matches
Mail list logo
