February-7th-2019, 07:36 AM
Got your point Jamie.
But what you need to know is that with the EtherCAT slave stack provided ALL process data objects are handled bytewise internally. There are not such things like FLOAT , UNT32 or others that could be defined. So in the end netX treats all data transparently as a kind of buffer byte by byte in adjacent order.
If this scheme is clear now of course in the application on top of the stack you can easily overlay some data types yourself. But the master on the other side will still see bytes .... or 4 bytes in a row if they shall contain a float or 2 bytes in a row containing an INT16 or so. But as far as I know you can bundle bytes in a master as well to a float or int.
Thx
But what you need to know is that with the EtherCAT slave stack provided ALL process data objects are handled bytewise internally. There are not such things like FLOAT , UNT32 or others that could be defined. So in the end netX treats all data transparently as a kind of buffer byte by byte in adjacent order.
If this scheme is clear now of course in the application on top of the stack you can easily overlay some data types yourself. But the master on the other side will still see bytes .... or 4 bytes in a row if they shall contain a float or 2 bytes in a row containing an INT16 or so. But as far as I know you can bundle bytes in a master as well to a float or int.
Thx
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
