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

EmonModbusTcpInterfacer Docs missing details #180

Open
g0lgs opened this issue Oct 27, 2022 · 4 comments
Open

EmonModbusTcpInterfacer Docs missing details #180

g0lgs opened this issue Oct 27, 2022 · 4 comments

Comments

@g0lgs
Copy link

g0lgs commented Oct 27, 2022

The Docs / Examples for EmonModbusTcpInterfacer appear to be missing the information of how to set the Modbus unit ID.

From what I can find in an old forum thread you need to do:

   [[[runtimesettings]]]
        register = 305, 306, 314, 321, 0xA001
        # unit number for each Register
        nUnit = 2, 2, 2, 2, 2

This seems to have worked.

@alexandrecuer
Copy link
Contributor

@g0lgs
Copy link
Author

g0lgs commented Oct 27, 2022

The Doc might be, but it does not cover the setting I am refering too.

@glynhudson
Copy link
Member

What device are you reading data from? The modbus ID needs to be set on the device

@g0lgs
Copy link
Author

g0lgs commented Oct 28, 2022

I am using a Orno WE-515 (not that it matters) and I have the Device ID set to 2 (as I am testing a setup where I will use multiple devices).

The Docs / Examples for the Interfacer do not appear to show how to configure the ID to match and defaults to 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants