-
Notifications
You must be signed in to change notification settings - Fork 13
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
Question - Is it possible to specify the modbus address? #6
Comments
did you ever get anywhere with this? i have a renogy wanderer with address 255 |
adding |
where, which file, should this modbusClient.setId(17) be added? |
Between lines 159 and 160 of |
I have the same issue of needing to change the address to 16 for our Wanderer. I tried adding the line to renogy.js, but when I tried to run it I got an error that modbusClient.setId is not a function. |
I was able to get my Rover 40A controller working on address 16 by adding the following between lines 187 and 188:
Very happy to have my controller working, thanks for all your hard work on this repo :) |
I've been using this with my Rover 60A & RS232 for a few months now... works perfectly. Much appreciated. I also have a Rover 40 Li w/RS232 that I'll be spinning up... I expect no issues. Now, I am purchasing a Renogy 12V 30A DC to DC Charger w/RS485 port. I am grateful to those blazing the trail on the RS485 side.... hope it won't be too painful. |
I found out that my controller lives at address 17; not 1 which is typical for renogy controllers.
The text was updated successfully, but these errors were encountered: