Re: [etherlab-users] Accessing same PDO for both read and write

2013-01-24 Thread Yan Prochazka
Hi Graeme, thanks for the advices! We are going to try the "safe for real time" SDO approach. However I have looked at ecrt_slave_config_reg_pdo_entry() implementation and adding some kind of Rx/Tx distinguishing flag should be relatively simple because sync_configs[] already know whether it

Re: [etherlab-users] Accessing same PDO for both read and write

2013-01-24 Thread Gavin Lambert
For some odd reason I didn't receive the message below, only the replies. But in any case: I haven't tested this myself, but I think you can still use it as read/write from a single domain. Remember that the EtherCAT main loop consists of: 1. Read previously received incoming packet. 2

Re: [etherlab-users] Accessing same PDO for both read and write

2013-01-24 Thread Graeme Foot
Hi, As another possible workaround (completely untested) you could try putting them in two separate domains. You might need to queue the read domain before the write domain to ensure you are reading the slave updated value rather than the newly written value. If this works, the write value

Re: [etherlab-users] Accessing same PDO for both read and write

2013-01-24 Thread Thomas Nelson
On Jan 23, 2013, at 11:21 PM, Graeme Foot wrote: > Hi, > > I don't know the answer to the question, but as a workaround you could set up > reading the value via PDO and write the value via an SDO. Writing via SDOs > take approx 30ms for CoE. > > Regards, > Graeme. > > From: etherlab-user