Gen 2 AZE0 2018 SOC request

My Nissan Leaf Forum

Help Support My Nissan Leaf Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

mafify

Member
Joined
Sep 3, 2021
Messages
18
Hello, everyone I am wondering if anyone faced the issue of not updating SOC, Ah and Charge data when the battery is standalone. I am facing this issue only with the gen2. I found 1F2 ID, it has a keep_soc_request but unfortunately it doesn't work or maybe I am generating the code wrong. The SOC only updates when I toggle the +12 and +ING on the battery pack but looks like it enters a sleep mode immediately after it turns on. Other data as voltage, amps and temp are updating correctly. Any help would be appreciated. Thank you all!
 
Sure, when starting you need to send this to the battery

Send HCM_WakeUpSleepCommand = 11b.
Send CHG_STA_RQ = 01b.
Send CANMASK = 1.
Set CRC and PRUN.

Then wait that battery replies with:
Send LB INTERLOC = 1.
Send LB_FRLYON = 1.

After that you can confirm the following
Confirm LB_FAIL = 0.
Confirm LB_STATUS = 0.
Confirm LB INTERLOC = 1.
Confirm LB_FRLYON = 1.

Then put pre-charge relay on

Send RLYP = 1 after confirming that MAIN RLY N is
ON or after 60 ms pass.
Wait (100 ms or more from the PRE CHARGE RLY ON command).

MAIN RLY N (-) ON
Wait (Stabilization of the high voltage line voltage).
MAIN RLY P (+) ON

Send BTONFN = 1 after confirming that MAIN RLY P
and N are ON or after 60 ms pass.

Wait (300 ms or more from the MAIN RLY ON command)
PRE CHARGE RLY OFF

Note that all steps might not be needed in order to read SOC continuously (probably just the HCM_WakeUpSleepCommand is needed), but this is how to start the sequence for using the battery in standalone mode.
 
I am actually sending the 50B ID as a static msg "000006c0000000" every 100 ms, which mentioned in your excel. I am also following the relay sequence and I can charge and discharge smoothly. But still SOC doesn't update
 
Interesting, try sending the 0x50C message also, it contains the ALU_QUESTION_FOR_LBC

I haven't seen anyone successfully using this method, so nice to hear what works and what doesn't!
 
I will test this out tomorrow and come back to you with the results! Thank you for the feedback :D
 
Dala said:
Interesting, try sending the 0x50C message also, it contains the ALU_QUESTION_FOR_LBC

I haven't seen anyone successfully using this method, so nice to hear what works and what doesn't!

I did many tests in hope to bring the interlook, SOC Awake to refuse to sleep to get the SOC updates it's value

First I sent 50B as a static message: 50b#000006C0000000
I am also sending the 1F2 to make sure it's in normal charge mode and Keep SOC is on with making sure that my CSUM and EPRUN is correct as following:

1F2#646432A0000A008F

1F2#646432A0000A0180

1F2#646432A0000A0281

1F2#646432A0000A0382

I also sent the 50C with a correct CRC

50C#0000005DC8
50C#0000015D5F
50C#0000025D63
50C#0000035DF4

Until now, I didn't successfully make the SOC updates itself.

will keep trying and update if I get it to work out!
 
I would try and generate all the VCM messages just to be sure
28v3Q3l.png


Here you can find a log file from a charging session: https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/Slowcharging1800WAZE0.log
 
Dala said:
I would try and generate all the VCM messages just to be sure
28v3Q3l.png


Here you can find a log file from a charging session: https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/Slowcharging1800WAZE0.log

I just ran all the VCM ID at the same time, I can see a change in ID 55B for the first time in the LB_ALU_ANSWER but SOC is still static. I will try to discharge and see if SOC start to change.
 
mafify said:
I just ran all the VCM ID at the same time, I can see a change in ID 55B for the first time in the LB_ALU_ANSWER but SOC is still static. I will try to discharge and see if SOC start to change.

And just to be sure, you are generating these messages periodically at the correct update rate?
 
Dala said:
mafify said:
I just ran all the VCM ID at the same time, I can see a change in ID 55B for the first time in the LB_ALU_ANSWER but SOC is still static. I will try to discharge and see if SOC start to change.

And just to be sure, you are generating these messages periodically at the correct update rate?

Thank you for the follow up. Yes, I am following the 100 ms and 10 ms period for the msgs. Also make sure about the EPRUN, CSUM and CRC. Just to clarify, I am testing on 4 different packs 24, 30, 40, 62 kWh batteries. I will take a look again on my code if I have any mistake in the calculations and come back with a feedback.
 
Another Update. The Gen 1 pack "24 kWh" responded to the 50C and 50B msgs and updated the SOC but the gen 2 packs didn't take the 50C and 50B. I figured out that the 50C msg in your log was actually changing the msg 55B "LB_ALU_ANSWER" between 55 and AA
 
So glad you got it working with the AZE0 packs! Yes the ZE1 packs (40/62kWh) are a completely different thing. These packs require many more messages in order to be happy.
 
I uploaded some ZE1 can logs that you can try to get the 40/62kWh packs working in standalone:

https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/EV_can-bus_from_62_ZE1.txt

https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/EV_can-bus_from_62_ZE1_QCcharging.txt
 
Dala said:
I uploaded some ZE1 can logs that you can try to get the 40/62kWh packs working in standalone:

https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/EV_can-bus_from_62_ZE1.txt

https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/EV_can-bus_from_62_ZE1_QCcharging.txt

Thank you so much! I was logging in today to tell you I brought a ZE1 model to collect some data and try out, but you already have it here! I will try them out and let you know for sure. Thank you again!
 
Dala said:
I uploaded some ZE1 can logs that you can try to get the 40/62kWh packs working in standalone:

https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/EV_can-bus_from_62_ZE1.txt

https://github.com/dalathegreat/EV-CANlogs/blob/main/Nissan%20LEAF/EV_can-bus_from_62_ZE1_QCcharging.txt

I removed the Battery CAN ID's and added a separate delays on all other reported msgs. I can confirm that the 40 kWh SOC got updated but the 62 kWh didn't update. I am not sure if it might be a BMS issue from the Pack itself. I will see if I can find another 62 kWh anywhere
 
mafify said:
Another Update. The Gen 1 pack "24 kWh" responded to the 50C and 50B msgs and updated the SOC but the gen 2 packs didn't take the 50C and 50B. I figured out that the 50C msg in your log was actually changing the msg 55B "LB_ALU_ANSWER" between 55 and AA

mafify said:
New Update: I got it updating also on the 30 kWh pack. But the 40/62 kWh didn't.

@mafify
How did you get on with SOC continuing to report back the SOC
Was it just the 50B message that was need being sent or was their others needed ?
 
mafify said:
Another Update. The Gen 1 pack "24 kWh" responded to the 50C and 50B msgs and updated the SOC but the gen 2 packs didn't take the 50C and 50B. I figured out that the 50C msg in your log was actually changing the msg 55B "LB_ALU_ANSWER" between 55 and AA

Can you shed some light on how you got it working?
So far I'm sending 50B, 1F2 and 1D4 to the BMS (AZE0). But doesn't seem to update. You have some code/github you could share or?
 
TrueSoln said:
mafify said:
Another Update. The Gen 1 pack "24 kWh" responded to the 50C and 50B msgs and updated the SOC but the gen 2 packs didn't take the 50C and 50B. I figured out that the 50C msg in your log was actually changing the msg 55B "LB_ALU_ANSWER" between 55 and AA

mafify said:
New Update: I got it updating also on the 30 kWh pack. But the 40/62 kWh didn't.

@mafify
How did you get on with SOC continuing to report back the SOC
Was it just the 50B message that was need being sent or was their others needed ?


Did you have any success figuring it out?
 
shano said:
Did you have any success figuring it out?

Yes, just this hour got message coming and reporting SOC
Just sending 1DA, 1F2 at 10ms and 50B at 100ms

Its working for a Gen1 battery, have to try Gen2 battery

50B message = {0xF7, 0x00,0x00, 0xc0,0x00,0x00,0x00 };


1D4 message = {0x07, 0x00,0x00, {ctr of 0,1,2,3} ,0x44,0x01, {CRC} }; (From Gen1 logs)


1F2 messageData1[8] = {0x60, 0x64, 0x64, 0xA0, 0x00, 0x31, 0x00, 0x0A };
1F2 messageData1[8] = {0x60, 0x64, 0x64, 0xA0, 0x00, 0x31, 0x01, 0x0B };
1F2 messageData1[8] = {0x60, 0x64, 0x64, 0xA0, 0x00, 0x31, 0x02, 0x0C };
1F2 messageData1[8] = {0x60, 0x64, 0x64, 0xA0, 0x00, 0x31, 0x03, 0x0D };

And getting the 55B message with SOC reading coming in
Just have to clean up the mess and the hard coded test been doing
 
Back
Top