Search results

Lifepo4 batteries are pretty good for charging without loss, so 99% is usually ok, you can just play with it to get the battery SOC accurate, but drift does happen and i haven't found a real accurate way to keep it in sync, it's a best effort.

What's your charge efficiency set in the battery part of the shunt?

The shunt drift should be loss, I.e. soc reports lower than actual. You need to tweak your shunt to reset to 100% on the following Battery voltage over xx.x Current under xx For time of say 15/20 mins. Along with the current divider you should be able to pretty much get this working well...

Currently it wouldn't work, CAN Bus has like a master slave relationship, and your 2nd inverter would respond same time as first - every packet gets a response from the inverter.

Code isn't reporting any amount of cells, but it is in the spec to be able to inform the inverter, I suspect that your inverter is defaulting to a lowest value it would accept. I don't know the settings for your inverter but try disabling pylontech and force charge, and with pylontech and tell...

The pylontech protocol switch changes the behaviour of the code. With it enabled it uses the modbus flags to tell the inverter to force charge. Without the pylontech protocol enabled, it doesn't send some flags and uses an alternative way of force charging, which is the sending a false SOC to...

@ChrisG @ScrotusGobbleBottom Glad you have worked things out, am sorry that I've not been around, I had some illness and life that took over for quite a while. As well as the web GUI the code also runs on Core and Core2 M5Stacks...

Wiring diagram, but note the CS pin is GPIO2 in the code, change in the config.h the line #define CAN_CS_PIN 2 // CAN CS PIN if you want to use GPIO5 instead.

The pylontech protocol full enabled doesn't seem to work on my inverter anymore since it had a firmware update from Solis, turn the protocol off in the code, and use user-defined on the inverter works fine.

The CAN adapter is a SPI device, you wire it as per the SPI instructions for your board. The only pin that the programmer can control is the CS (Chip Select) which i used GPIO2.

Your CS pin must be GPIO2 unless you change the line #define CAN_CS_PIN 2 // CAN CS PIN in config.h The serial info should show if the CAN is detected, then will start showing if it's sending CAN messages and if it's successful or not. Make sure to be running it in full...

was going to be either 3 x 3.5kwh or 2 4.8kwh pylontech's, single can't cope with the continuous 100A demand. Have actually canned this project, got to complicated where customer (who's a friend) wanted also a design with solar edge, his dad questioned what i put on a quote (i used a website to...

Am currently about to install a rhi solis 6kw for someone, the customer already has 3.68kw on a solar edge system and fit so can't be touched but the design I've done is to put the Solis in and it should use the surplus from solar edge plus the extra solar that's being added to the system. A...

I take it the disappointment is because I didn't give you the answer you wanted to hear? Multiple BMS's and Battery packs isn't actually that difficult to do, just don't mix battery types use only one in all the battery packs, I have multiple BMS's and Battery packs for almost a year without...

not for battery data (as far as am aware) can't see an option for it. Seplos has rs485 and CAN comms, so possibly CAN to Solis and then monitor over the 485?

You wouldn't need $3000 for it. Buy the BMS and attach it to your current batteries and then develop against that, I don't see the need for anything else?

ok... so for those of you with a spare esp32 and want to experiment there is now a testing branch, this is the latest code but NOT production ready as am still fixing some bits and rearranging the code, it's a bit messy at the moment due to different ways of trying things, but thought those that...

The Solis uses can bus for battery data.

Fair enough, I've never looked at the pylontech batteries in any detail, I just copied there protocol for my application. All DIY builders I know do 16 series cells, and reviews of the seplos BMS is with 16 cells, so going with 15 could have unintended consequences as the charge voltage might...

Am guessing pylontech batteries isn't using lifepo4 batteries then?....

Voltage has nothing to do with pylontech, pylontech batteries talk a protocol over can bus, a lot of companies copy the protocol and implement it as it's quite well supported by various manufacturers.

Fyi = for your information. Lifepo4 configuration for a 48v system is 16 cells, you don't do the calculation as 48 divide by 3.2.

Just a fyi, it's 16 cells for lifepo4.

The BMS will disconnect the power flow to the batteries, the draw will be available but the inverter if it's in alarm may not take any, no need for manual intervention as it will sort it self out but if I remember rightly while the alarm is in play the inverter stops until recovered i.e. battery...

The inverter will go in to alarm if your BMS disconnects the batteries, this can then mean the inverter won't use the batteries whilst it's in this state.

Can you please start your own thread and not spam this one that's for my solution please.

Looks like it supports pylontech which is supported by the Solis.

I don't think it's a code issue, I've seen the Daly stop responding on the 485 port when it's hot, it's bizarre but as soon as it all cools down it's able to communicate again, funny thing is the 232 port seems to always work.

try increasing the delay() between reads, but i did find if the BMS was hot it timed out and is why i moved away from the Daly BMS. There is my version which is slightly modified but am guessing will timeout the same, worth trying: https://github.com/sijones/M5Stack-Daly-Solis I moved to this...

Maybe your not getting any communication from the BMS, have you tried swapping tx / Rx around?

Is it just that one cmd or multiple. You can comment it out in the code, or comment out this - goto fail. 0x94 hex is 148 decimal. if (!bms_rx(0x94)) { //goto fail; } else { _bat_cycle = bms_word(5); // charge discharge cycle }

What code are you using from where?

If it supports pylontech batteries over can bus then yes it should work fine.

Quick peek to what's coming, the web page will work with the esp that is already in use, the display support requires an m5stack core or core 2. And hopefully this release won't require any programming knowledge as you'll just be able to use the esp flasher and then configure everything after...

i'd say am down to a couple of weeks, just need to rewrite the Wifi and MQTT code, implement the reduced charging current stages and the real time webpage updates, the wifi code is the biggest part.