On 09/10/2012 13:27, Florian Pose wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 08.10.2012 16:42, schrieb Thomas Bitsky, Jr.:
What you're proposing would be a mistake. The value coming back is
the value of that object in the field. You send out a value, the
slave reads it, then puts in the value that is actually there. If
it just took your value and never did anything with it, you'd be
blind to what is going on out in the field. The fieldbus isn't your
personal memory buffer; it's feedback of what is going on in the
real world.
That's not true. A slave will *never* change RxPDO-only data in the
frame. For pure RxPDOs (master -> slave) you will receive exactly the
data you were sending.
This is exactly what I mean.
Data set to 1 comes back to 0 if I stop "forcing" it to 1 state.
None of the fieldbus I've played with have never behaved in this way
So if I stop writing I get back different data respect what I wrote.
Even if I've yet workarounded this buffering my output area I still
consider this a sort of mistake.
_______________________________________________
etherlab-users mailing list
[email protected]
http://lists.etherlab.org/mailman/listinfo/etherlab-users
