Renogy Adventurer Li 30A raspberry pi

My guess is that you don't have the wires connected correctly, or what you're doing right now isn't set up for RS-232 communication.

This thread is very similar to what you are doing. If it doesn't help you, tell us how you have your wires connected to your raspberry pi and what you are using to convert the RS-232 signal to something the pi can read.

renogy.boards.net/thread/535/using-rj11-cable-connect-raspberry

EDIT: Wait, I just read that you're using the included serial to USB, so now you can ignore the above.

I recommend checking out libraries made for the rover that already exist to see why the communication doesn't work. Such as: github.com/KyleJamesWalker/renogy_rover or github.com/wildmountainfarms/solarthing (my own)

Hello

It's very interesting that you got a response of all zeros. You are in RTU mode so that's correct. One good thing is that it is detecting a serial port.

Do you have the same pinout as described here: renogy.boards.net/thread/119/rover-monitoring-using-raspberry-pi

renogy.boards.net/attachment/download/60

Yeah, the data won't be readable. But, with how Modbus works, you shouldn't be getting ANY data from the serial port unless you request it. Your computer has to be the one to initialize the communication. So, if you are getting random data like you said and you aren't requesting it, something is wrong with your adapter.

I am unfamiliar with the Pimoroni but after doing a ctl+f on that page, RS232 doesn't come up anywhere on that page. If we go back to talking about the USB to serial adapter, which you stopped using, do you know if that used RS232? The RS232 adapter is the most important part for getting this to work.

And got a new error msg:

Modbus Error: [Input/Output] Modbus Error: [Invalid Message] Incomplete message received, expected at least 2 bytes (1 received)



This is from using the following code:

import time, datetime, os
UNIT = 0x1

# Import Pymodbus
from pymodbus.client.sync import ModbusSerialClient as ModbusClient

client = ModbusClient(method='rtu', port='/dev/ttyUSB0', timeout=1,baudrate=9600)
client.connect()
rr = client.read_holding_registers(0, 1, unit=UNIT)
client.close()
print(rr)

And another modbus client with more debug info.

This was done on a fresh install of the raspberry will all updates applied and only the minimalmodbus package for python installed.

>>> import minimalmodbus
>>> instrument = minimalmodbus.Instrument('/dev/ttyUSB0', 1, debug = True)
MinimalModbus debug mode. Create serial port /dev/ttyUSB0
>>> instrument.serial.baudrate = 9600
>>> print(instrument.read_register(2, 4))
MinimalModbus debug mode. Will write to instrument (expecting 7 bytes back): '\x01\x03\x00\x02\x00\x01%\xca' (01 03 00 02 00 01 25 CA)
MinimalModbus debug mode. Clearing serial buffers for port /dev/ttyUSB0
MinimalModbus debug mode. No sleep required before write. Time since previous read: 1577454319875.52 ms, minimum silent period: 4.01 ms.
MinimalModbus debug mode. Response from instrument: '\xff' (FF) (1 bytes), roundtrip time: 50.4 ms. Timeout for reading: 50.0 ms.

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/minimalmodbus.py", line 447, in read_register
payloadformat=_PAYLOADFORMAT_REGISTER,
File "/usr/local/lib/python2.7/dist-packages/minimalmodbus.py", line 1170, in _generic_command
payload_from_slave = self._perform_command(functioncode, payload_to_slave)
File "/usr/local/lib/python2.7/dist-packages/minimalmodbus.py", line 1244, in _perform_command
response, self.address, self.mode, functioncode
File "/usr/local/lib/python2.7/dist-packages/minimalmodbus.py", line 1699, in _extract_payload
MINIMAL_RESPONSE_LENGTH_RTU, response
minimalmodbus.InvalidResponseError: Too short Modbus RTU response (minimum length 4 bytes). Response: '\xff'


It looks like the adventurer is not responding with a properly formatted modbus reply.

Might try another USB to serial adapter just to be sure.