On 15 July 2014, quoth J. van der Wulp: > - when a frame exceeds the 128 byte threshold then increasingly often > the latency of the response frame increases (seems a 100microsecond > offset) but our time budget (time between send() and receive()) is 100 > microseconds. This is the cause for working count 0 errors. > - as long as the process data is such that frame size stays below ~128 > bytes there is no problem, the working counts stay stable and response > latency is more or less constant
Sure you're not getting a 10Mbit link instead of 100Mbit? 128 bytes of data at 5kHz will just about saturate a 10Mbit link. > - use the generic module when operating at 5Khz (only tested with 1.5.2 > with frame size less than ~128 bytes) gives the same working count 0 > symptoms, for our application we really seem to need the patched > drivers... The generic driver is rarely stable over 1kHz; sometimes not even that. _______________________________________________ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
