New and naive with 40kwh of Renault Zoe batteries

Status
Not open for further replies.
It appears we are dangerously close to a pointless pissing match over reading comprehension. As I understand it, the original post is about whether or not the guy should buy back his total-loss vehicle in order to use the battery pack in a DIY powerwall type project. I think my edit is very much on point with some of the issues affecting that analysis -- they may be obvious to you and me, but perhaps not so to others. Everyone was new to this stuff at one time. My gut hunch is that the OP would be better off junking his crashed car and buying cells appropriate to whatever goals he has for his project, but only he has the data to sort out whether that is correct or not.

Wow I don't understand all the confusion???
If you look at Woleg's footer it just about explains it all....

HVDC 36kWh Renault (ZE40) -> Renault BMS/PWM Contactors -> Custom gateway -> FoxESS 5kW AC (Jul 2022)
HVDC 52kWh Renault (ZE50) -> Renault BMS/PWM Contactors -> Custom gateway -> FoxESS 6kW H1 (Jan 2023)
I'll help you with your statement posing as a question: the unavailability of Woleg's "custom gateway" (or any information necessary to replicate its functionality) is exactly the problem for the OP. Perhaps you have a solution to that which you are inclined to share? Woleg has basically stated that he won't share, ostensibly to keep us all safe from ourselves, so a big piece of the original question remains unanswered. Maybe you are more disposed to sharing knowledge which would benefit MANY people in similar situations. Until there's any kind of a standard for communication protocols between myriad inverters, batteries, and BMS systems -- and I see little market incentive for any such standard to form -- these questions are going to remain major issues for DIY project builders and hobbyists.

Cheers, John
 
I'll help you with your statement posing as a question: the unavailability of Woleg's "custom gateway" (or any information necessary to replicate its functionality) is exactly the problem for the OP. Perhaps you have a solution to that which you are inclined to share? Woleg has basically stated that he won't share, ostensibly to keep us all safe from ourselves, so a big piece of the original question remains unanswered. Maybe you are more disposed to sharing knowledge which would benefit MANY people in similar situations. Until there's any kind of a standard for communication protocols between myriad inverters, batteries, and BMS systems -- and I see little market incentive for any such standard to form -- these questions are going to remain major issues for DIY project builders and hobbyists.

Cheers, John
The fundamental issue I have been grappling with has been resolved, the best way forward is to release the protocol information and let hobbyists take safety into their own hands. I'm in the process of documenting what I know and releasing that. No code, just message definitions and procedures that need to be performed to enable communications. What hobbyists do with that information is their business.

The ZE40 protocol is now partially documented here.
 
Last edited:
The fundamental issue I have been grappling with has been resolved, the best way forward is to release the protocol information and let hobbyists take safety into their own hands. I'm in the process of documenting what I know and releasing that. No code, just message definitions and procedures that need to be performed to enable communications. What hobbyists do with that information is their business.

The ZE40 protocol is now partially documented here.
Hi Woleg

Would you be available to published message definitions and procedures that need to be performed to enable communications with the Foxess inverter?

Thanks in advance.
 
No problem.


I’m still awaiting on community help for V2 BMS can logs.
Hi and thank you
As follow what I manage to decode until now.
Hope that with the help of V1 to decode more Data

I think I need messages from V2
Can ID messages are:
Inv. Request
00001871
BMS response
00001872 (Batt_V_max/Batt_V_min/Batt_Chg_max/Batt_chg_min)
00001873 (batt_cur_V/_/SOC/_)
00001874
00001875 (Bat_Temp/Nr_Batt/_/_)
00001877
00001878
00001879
00001881
00001882
00001883
 
If you simply want the inverter to work then that dbc file is fine. Send frames from 0x1872 to 0x1877 when you receive 0x1871 0x1 0x0 0x1 0x0 0x0 0x0 0x0 0x0

The full implementation of V1 is here and I think it is overkill for communicating with a FoxESS, they are pretty relaxed about what is received.

If you can send me the full can bus log from a V2 with batteries connected I can write a second protocol dedicated to that. The biggest difference is cell volt and temp monitoring. I will assist if you require any help doing this
 
Last edited:
Status
Not open for further replies.
Back
Top