sophienyaa/NodeRenogy

Question - Is it possible to specify the modbus address?

Opened this issue · 7 comments

SP410 commented

I found out that my controller lives at address 17; not 1 which is typical for renogy controllers.

kamkelsey commented

did you ever get anywhere with this? i have a renogy wanderer with address 255

sophienyaa commented

adding modbusClient.setId(17) before the read might resolve this. If you're able to test and let me know I can add this as an enhancement.

whuang0705 commented

where, which file, should this modbusClient.setId(17) be added?

sophienyaa commented

Between lines 159 and 160 of renogy.js. I've not tested this so you may need to make additional changes.

oBorks commented

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.

CzarDestructo commented

I was able to get my Rover 40A controller working on address 16 by adding the following between lines 187 and 188:

        try {
            modbusClient.setTimeout(500);
            modbusClient.setID(16); 
            await modbusClient.connectRTUBuffered(args.serialport, { baudRate: args.baudrate });
            logger.info('Connected to controller!');
        }

Very happy to have my controller working, thanks for all your hard work on this repo :)

  • 👍1
ColbyBurkett commented

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.