You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API seems to lack the ability to get the endianness and float format information from e.g. the connect requests. With the stack not executing any data manipulation (which I think is the right design choice), the application layer would need to know these details to properly assess the content. For now I'm working with S7-1500 which appears to always leverage little endian and IEEE float representation but as the protocol supports different options I would want the app to be able to react to different scenarios.
The text was updated successfully, but these errors were encountered:
The API seems to lack the ability to get the endianness and float format information from e.g. the connect requests. With the stack not executing any data manipulation (which I think is the right design choice), the application layer would need to know these details to properly assess the content. For now I'm working with S7-1500 which appears to always leverage little endian and IEEE float representation but as the protocol supports different options I would want the app to be able to react to different scenarios.
The text was updated successfully, but these errors were encountered: