expose endianness and float representation

Open
#40 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

Start by tracing how connect requests are parsed and how protocol options are represented in the C stack; the issue names no specific files or tests. Determine where endianness and float representation can be retained and exposed to the application, then verify that applications can distinguish the supported scenarios.

Written by the indexing model from the issue text.

Description

enhancement

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.

Dominant language
C
Stars
599
Forks
234
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rtlabs-com/p-net

All issues in rtlabs-com/p-net

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.