Re: [etherlab-users] EL6692 connector

2013-11-21 Thread jasper2
Hello Richard, Yes I have added the product code and revision numbers in the xml and in the generic block mask in Simulink. EL6692 The command below shows all my pdo, whereas ethercat -p9 pdo only shows TxPDO. Why are the two commands showing me such different information? Best Regards, Jasper

[etherlab-users] waiting for received frames

2013-11-21 Thread Martin Troxler
Hi I watched that discussion about the need for a API to wait (poll) for received frames. I still don't get it why that is nessessary. Here is a clarification of how ethercat (process data transfer) works: - Process Data should be regarded as idempotent states, which means it doesn't matter how

Re: [etherlab-users] waiting for received frames

2013-11-21 Thread Armin Steinhoff
Ian, your view is true for single core CPUs ... if you have a multi core CPU you can assign a single core for polling of incoming frames. I'm planning to use Intel's DPDK as a networking base for EtherCAT ... it's time to get rid of the dependency to kernel versions. --Armin Steinhoff Ian Procha

Re: [etherlab-users] waiting for received frames

2013-11-21 Thread Shahbaz Youssefi
This is going to be repetition of some very old discussion. First, to answer Jeroen: yes, what holds me from just calling ecrt_master_receive as a kind of poll is that it doesn't provide me with an answer to the following question: "Has all the packets of the domain arrived yet?". The whole point

Re: [etherlab-users] waiting for received frames

2013-11-21 Thread Ian Prochazka
Sometime the issue is that etherCAT master loop does not need and should not be running as tight as possible, because the computer needs to do also some other tasks. But at the same time, the master needs to react to slave data as quickly as possible. So master initiates transaction with fake/n

Re: [etherlab-users] waiting for received frames

2013-11-21 Thread Martin Troxler
On 21.11.2013 14:06, Jeroen Van den Keybus wrote: > I'm just wondering if the need for receipt notification would e.g. arise when > someone would send an EtherCAT frame A > for gathering data and, as soon as that frame returns, do some calculations > and send a second frame B to apply process >

Re: [etherlab-users] waiting for received frames

2013-11-21 Thread Ian Prochazka
Exactly!!! Thank you Shahbaz for great summary and reiteration. And even more useful than function ecrt_domain_received() that would need to be polled, seems to me or ecrt_master_receive() that would block and wait till data are available or any kind of asynchronous notification "data are avai

Re: [etherlab-users] waiting for received frames

2013-11-21 Thread Jeroen Van den Keybus
Is there anything holding you from just calling ecrt_master_receive() early as a kind of poll ? I'm just wondering if the need for receipt notification would e.g. arise when someone would send an EtherCAT frame A for gathering data and, as soon as that frame returns, do some calculations and send