still struggling with the Arduino.I've found that arduino libraries are a great resource,
Wait what?Hi Jasnon,
still struggling with the Arduino.
Can manage to read the stuff with python, see link ealier Gitlab. post #57Post #57
Could you point me to the library which you are using?
Thanks T
Can you connect the mega to the DCC50S, and also connect your PC to the RS485, then run Slave Simulator on the PC. You should be able to see the message MEGA>>DCC50S and the reply DCC50S>>MEGAI do not get any right messages from Renogy via Arduino Mega (clone) and MAX485.
working with the raspberry and usb rs485 and python.
Sometimes in the internet there a several library version of same library around.
Can also read messages from Master simulator and Renogy.
Maybe the Mega is broken or the MAX485.
Thanks t
I am using modbusMaster.h, I gave you my code, you must be using the same library?!
. This is the advantage of the bus system of RS485Can you connect the mega to the DCC50S, and also connect your PC to the RS485, then run Slave Simulator on the PC. You should be able to see the message MEGA>>DCC50S and the reply DCC50S>>MEGA
I've sent you the DCC50S modbus info, which is all I have. Somewhere in this thread,I think a member (maybe Boopzz) was asking about renogy batteries, but I don't know if they managed to get/create a map.Hi T6Jay, You wrote, You have got some Information about RS485 Protocol of Renogy Products. Where ca I find these Information or a snipplet of Sourcecode. I've got a renogy Battery and want to read the Battery state but I cannot find any information at all. Can You help me?
Hi boopzz, I'm looking for Modbus protokol of the Battery "RBT100LFP12S-DE" too. Canu get me some Information about device number and Registers? I only want to reed registers to get the state of the battery. If You have some information, can You send me to arnold.beck@web.de?- @TD21 I have the modbus mappings so can get those across, just PM me your email.
- I have asked for the Smart Battery mappings and got refused, so assume they will stick to this. Realistically it shouldnt be too hard with the right kit. We need some kind of device that can sniff the data channels for the RS485. This depends on how the display polls. If it polls everything it could be time consuming, if it polls when the screen is selected then it should be ok. If its the latter you select the field on the display, the sniffer should capture the request address and the reply, you can then input into a spreadsheet what the request, reply and also what the display shows and this should show you the unit. In the modbus mappings for temp for example its a 7 bit register and the 7th bit is the polarity so that throws into a mix some complexity!
- Yes I'd like to complete the python script and turn it into a proper driver with every value available, partly why I tried to keep the repo seperate from a full stack for the van but pull from it
Would love to see what youve cobbled together? How have you been able to get this far, Im keen to collaborate!Hi, unfortunately Renogy wouldn't give out the battery mappings due to safety concerns . I have got a Python driver to get a load of stats but it's not quite refined as not all the mappings are in there yet. It outputs the data to an MQTT Subscriber but could be anything I guess
Hi, unfortunately Renogy wouldn't give out the battery mappings due to safety concerns . I have got a Python driver to get a load of stats but it's not quite refined as not all the mappings are in there yet. It outputs the data to an MQTT Subscriber but could be anything I guess
hmm, interesting... I have not had time to switch A and B (D+ and D-) on the RS-485 yet, nor mimic master from PC over USB TTL, but will give it a go tomorrow hopefully.I remembered something else.
I had an occasion when my arduino was working with a PC slave simulator, as you did, but the same setup just would not work with the DCC50s.
It turned out that the arduino modbus library worked great with an arduino leonardo, but when I ran it on a nano33ble (a faster micro) the switch from tx to rx happened too soon, the result was that the final byte of the frame never left the 485max, this byte is part of the CRC. I then discovered that the slave sim software I was running simply ignored the CRC, and gave a 'valid' reply. The DCC50S however refused to respond to a frame missing half of the CRC.
The modbus libray I used was ModbusMaster by Doc Walker. The fix was to add a 2ms delay after the final byte was transmitted, and before the switch to RX.
Could this be your issue?