I have the Renogy DCC50S with the BT-2 bluetooth monitor and the RMS-DCDC monitoring screen and I'm trying to get the 2 monitoring units to work with the DCDC charger.
I don't need the BT to work while I'm driving but would like to use the monitoring screen so my idea was to use a 4PDT relay to switch the screen in with ignition and have the BT unit working through the NC contacts when engine is shut off.
I'm only using contacts 1-4 as shown in the PDF as I assumed the Canbus contacts could be ignored but it doesn't work.
I notice the the RJ45 pin numbering on the image in the PDF seems to be reversed i.e. numbering from 8 to 1 from the left. Do the numbers & allocations in the list actually correspond to the numbers shown on the plug?
Thanks for any enlightenment or guidance!
Hello,Sorry to revive an ooooold thread. Wondering what cable you guys might recommend for this today? I cannot buy the Renogy official cable.
Looking at Renogy Document for the cable - https://www.renogy.com/content/RSCB1.8M24/SCB-Manual.pdf
It references using the "FT232RL" chip.
Would something like this work: https://www.amazon.ca/gp/product/B07N1LZSBN/ref=ox_sc_act_title_1?smid=A1SRKLXY0XF9L5&psc=1
Its suppose to be the same chip. Just no guess on the pin out. I am trying to wrap my brain around it.
I want the cable to do a couple things.
- I have a few of these batteries and they are on a few different firmware versions. I am hoping to update them all to the same.
- I have seen the dbus-serialbattery project ( https://louisvdw.github.io/dbus-serialbattery/ ) that I should be able to add the BMS directly to my Cerbo (Raspberry Pi).
Any advice is appreciated.
I paused the project for other higher priority stuff for me... In the end I can use the renogy bluetooth for what I need. Saying that I would like to get it working. It looks like though all I need is to install the dbus software and a renogy official cable for programming an updating the batteries. I could not find one to order though so I have to make my own and could not find any good info short of guessing a little.Hello,
did you manage to connect Renogy LiFePo4 to Venus Pi? I want to by 3 of these batteries but I didn't find any info about connecting more than one battery to Victron Venus.
Thanks
Hey there. I'm going to give this a shot with a Cerbo and see what happens. I'm going to use a generic RS485 to USB interface since it appears the Renogy model is no longer available. I think the problem I am likely to run into is that each battery will somehow need to be assigned an individual address/drop number. It appears that this uses modbus protocol, and I would expect that each battery would be factory assigned the same address. If I want to connect to multiple batteries with the same connection (in my case 4), then I would need to figure this out. A workaround would be to put an RS485 to USB on each battery and run them to the Cerbo individually, but that seems like a messy set-up when you can daisy chain the batteries together and use a single connection.Sorry to revive an ooooold thread. Wondering what cable you guys might recommend for this today? I cannot buy the Renogy official cable.
Looking at Renogy Document for the cable - https://www.renogy.com/content/RSCB1.8M24/SCB-Manual.pdf
It references using the "FT232RL" chip.
Would something like this work: https://www.amazon.ca/gp/product/B07N1LZSBN/ref=ox_sc_act_title_1?smid=A1SRKLXY0XF9L5&psc=1
Its suppose to be the same chip. Just no guess on the pin out. I am trying to wrap my brain around it.
I want the cable to do a couple things.
- I have a few of these batteries and they are on a few different firmware versions. I am hoping to update them all to the same.
- I have seen the dbus-serialbattery project ( https://louisvdw.github.io/dbus-serialbattery/ ) that I should be able to add the BMS directly to my Cerbo (Raspberry Pi).
Any advice is appreciated.
Hey MatthewWaking up an old thread again... I have a Renogy battery and was wondering if anyone had made progress? With regards to the device address,
the linked document doesn't appear to state anywhere what defaults might be, but for "PDU"s you can apparently read and change it with the register at 0x1A. I'm waiting for an RS485 interface but presumably I can then poll all device addresses to find out what address my battery has, and then scan register addresses to find undocumented ones, and if the contents of one is the same as the device address it's a good indication that it might be.
Hey all, an interesting follow up to this.
One of the developers of the driver posted a fix for this yesterday, so I downloaded it to test first thing yesterday morning. Initially it did not work, but as I was testing it I was in contact with the developer, who ultimately ended up remoting into my system to test and debug, ultimately getting the driver working. This took him most of the afternoon, and considering I'm in Northern Alberta and he's in Italy, he worked until around midnight his time sorting this out.
The last few posts in this discussion explain where to go to download the updated driver (not an official release yet) and instructions for install.
Please donate to mr-manuel if you find this driver useful. He donated a large portion of his time toward development of this functionality.