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
Device ID as Slave #260
Comments
Please porvide a debug log and also enable the enhanced debug in settings |
here is the log:
|
Thats not the reason for the issue but: If row 42 is changed to |
By the way, I solved it for me like this: In the file modbus-server-tcp.js
into:
if your slave has a different ID, of course you have to enter this ID instead of the 1. |
Hallo, ich habe auch das Problem. Adapter läuft als Slave...bei ID kann ich reinschreiben was ich will, er antwortet auf alle IDs. Kann das Problem gefixt werden? |
It seems that the adapter as slave does not make a difference between the device ID´s.
I configured the Adapter as slave and choose device ID 1
Holding register 11 is set to 45.
I can read the holding register and it seems to work fine but the adapter is answering every request comming at right IP and Port. Regardlessly of what is set as device ID (in the request telegram). Here you can see the Modbus Adapter answering to a request comming in as device ID 3.
The text was updated successfully, but these errors were encountered: