Search found 22 matches

Finally, FoxESS have recognised the depth of this issue. New parameters are now available to limit import and export at the grid which then shapes charging and discharging limits at the inverter(s). Remember, there devices are parallel compatible hence the need for defining each limit.

https://i ...

Regarding floor insulation atop concrete flooring. My minimum recommendation is 25mm rigid waterproof insulation with 12mm OSB on top and some batons to allow airflow underneath the pack. I’ve had very large packs laid out on this arrangement without issue.

Keep it low and simple.

Quick update. Fox did address this in a firmware update and the new limit appears to be 100A despite the cloud settings showing a ceiling of 50A.

Are you charging the EV off the Inverter (solar/battery) itself ?, if not it’s better to keep the EV charger in front of the inverters CT so that it doesn’t see the load.

I’m not sure on the gridchargelimit - I can see why it’s a good idea for the European markets with PeakShaving etc.. (i’ll ...

Will, this is 100% a bug for FoxESS. Note the effects of the EVSE starting near 00:30. 12kW is grid volts at 50A which is the ceiling for that setting.

Dave, I need to have my CT config as is for many reasons inc solar divert.

https://i.ibb.co/LS5S24J/image.png
https://i.ibb.co/tD7NM8k/image ...

Hi,

Has anyone raised the "GridChargeCurrentLimited" issue with FoxESS UK? This feature creates soft limit to the maximum current draw as measured by the CT. The range offered on the web configuration is capped at 50A (~12kW) however this significantly throttles the KH battery charge rate when ...

Probably best to open a new post.

That has been done as a HA add-on. You can check it out here https://github.com/nathanmarlor/foxess_em

Also using Grafana.

Can you post your json configs for the dash? I'd like to improve my own.

Can't comment on RS485, but on CT vs Modbus meter the CT wins. Reaction to changes in phase conditions is much faster from what I can tell as the sampling rate is higher. Normally I would prefer to use an Eastron (I have on in circuit) over CT but having switched to the FoxESS platform my mind has ...

Quick update, Modbus TCP -> RTU has now been implemented and works with the standard HA setup as a USR-W610. If someone wants to test a prototype let me know.

Ethernet ports are vulnerable by their mere availability. Having embedded controllers available on a network is always a problem, communications on ethernet uses up valuable resources on the tiny Arm Cortex MCUs that runs the entire inverter. Mess with that port and you can bring the whole lot down ...

V2 is a knowledge void for me. I can only demonstrate what I know based on how my own kit presents (fw < 1.50).

There are two communication buses at play here, master to inverter and master to slaves. I do not have any information on the latter.

I'm happy to look at the V2 in detail but I need can ...

Users who wish to decode the can bus messages sent between the BMS and inverter can find a suitable dbc file here: https://github.com/rand12345/solax_can_bus/tree/dbc_codegen

When used in conjunction with a can bus sniffer (SavvyCan), this file will decode each can message into human-readable ...

Much appreciated.

Quick update.

I have the LilyGo CAN485 running with dual can bus. Pretty nice unit.

Edit: Some screenshots from Home Assistant from BMS can comms (MQTT)

Yes, it will be the exact same data but with a ~2 second refresh rate. I can knock some basic PoC up once the boards arrive. Can bus will be set to listen only so it’s a pretty safe system that should not require the BMS cables to be unplugged. I have an assumption that BMS and Com share the same ...

If Python is your thing I should be able to give you some PoC code for monitoring the raw values coming out of the BMS (Com) which can be pushed to MQTT (HA hosted Mosquitto) or modbus TCP. It will help with local rapid data measurements of charge rates, high and low cell volts, temps, etc ...

Could you describe the problem in a bit more detail? Screenshots or photos could help if it's data related.

Looks like the NW is well represented here, quite a few of us now!

Appols for the late reply, didn't enable notifications!

As I see it, the operation of such a device would be transparent as the primary goal would be to map the RTU registers to TCP. Configuring the HA integration would be a matter of setting it up as per the TCP template. There may be one or two ...

Hi StealthChesnut

Reaching out on here regarding this post on your HA repo https://github.com/StealthChesnut/HA-FoxESS-Modbus/discussions/50#discussioncomment-4818239

Would you be interested in a collaborative project to develop a custom interface? There appears to be quite a few V2 issues that ...

Will,

Would you consider a dedicated topic to can bus communications? This would bridge both battery (agnostic) and inverter and may suit its own section.

The reason for the request is to reach out to other techs and devs who would be interested in patching many of the new V2 issues that have been ...