Skip to content

expose endianness and float representation #40

Open
@ToSa27

Description

@ToSa27

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions