On 2014-07-08 11:21, Gavin Lambert wrote:
Though one of my original questions remains:
If it's not supposed to work, shouldn't the master just select a
smaller size if it doesn't support large sizes? While it's supposed
to respect the slave's preference, ultimately the master is in control
of
On 2014-05-20 22:00, etherlab-users-requ...@etherlab.org wrote:
what is the limit for the maximum supported mailbox size? Either in
EtherCAT in general or in EtherLab in particular?
ETG1000.5 V1i02 page 43 indicates that the mailbox can be from 38
to 1486 bytes.
Best regards -
on demand only. Once in the
equivalent of RUN mode, rescans generally do not offer much value,
outside of support for fast hot connect. The application needs to
observe the working counter fault, return to a safe state, and then
rescan, if required.
Best regards - Dave Page
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
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 channel AI) also uses offset 6 with an 8-bit entry.
Regards,
Steven
From: Dave Page dave.p...@gleeble.com mailto:dave.p...@gleeble.com
Date: Wednesday, April 9, 2014 5:07 PM
Hi,
Yes.
These questions can be answered by visiting the manufacturer page,
and finding the process data or commissioning information in the product
datasheet.
https://www.beckhoff.com/english.asp?fieldbus_box/ep2338.htm?id=74619916800719
So, for the EP2338, there are 8 bits of
remains to be done to make
it completely usable. Regardless, I am using it with an internal
project, and the output works for me (and I don't have to ever look at
an XML file when I change a PDO).
Best regards - Dave Page
