Sitelet https://web.archive.org/web/20201115190642im_/https://github.com/slowtec/tokio-modbus/issues/40
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for function 43 / 14 Read Device Identification #40

Open
psztoch opened this issue Jan 31, 2020 · 3 comments
Open

Support for function 43 / 14 Read Device Identification #40

psztoch opened this issue Jan 31, 2020 · 3 comments
Assignees
Milestone

Comments

@psztoch
Copy link

@psztoch psztoch commented Jan 31, 2020

No description provided.

@flosse flosse added this to the v0.4.1 milestone Mar 7, 2020
@flosse
Copy link
Member

@flosse flosse commented Mar 7, 2020

@psztoch Would you mind to implement this?

@ptasz3k
Copy link

@ptasz3k ptasz3k commented Apr 19, 2020

I can try it. I'm learning rust, using modbus professionally and probably will implement that function in my c and c# modbus libs. I think that it will be good exercise.

Any hints where should i start?

@flosse
Copy link
Member

@flosse flosse commented Apr 20, 2020

I can try it.

awesome!

Any hints where should i start?

You can find an example described on page 43 in the Modbus Application Protocol Specification (PDF).

Screenshot_2020-04-20 MODBUS Application Protocol 1 1 b - Modbus_Application_Protocol_V1_1b3 pdf

So here are some possible steps to implement it:

  1. Define the Request & Response
  2. Write test(s) with the given example
  3. Implement the processing algorithm
  4. Extend the public API
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.