mafify
Posts: 17
Joined: Fri Sep 03, 2021 3:53 pm
Delivery Date: 03 Sep 2018

Gen 2 AZE0 2018 SOC request

Fri Sep 24, 2021 4:36 pm

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!

User avatar
Dala
Posts: 366
Joined: Sun Oct 28, 2018 11:24 am
Delivery Date: 01 Jan 2015
Leaf Number: 316851
Location: Finland
Contact: Website

Re: Gen 2 AZE0 2018 SOC request

Mon Oct 04, 2021 12:39 am

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.

mafify
Posts: 17
Joined: Fri Sep 03, 2021 3:53 pm
Delivery Date: 03 Sep 2018

Re: Gen 2 AZE0 2018 SOC request

Mon Oct 04, 2021 5:07 pm

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

User avatar
Dala
Posts: 366
Joined: Sun Oct 28, 2018 11:24 am
Delivery Date: 01 Jan 2015
Leaf Number: 316851
Location: Finland
Contact: Website

Re: Gen 2 AZE0 2018 SOC request

Wed Oct 06, 2021 5:23 am

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!

mafify
Posts: 17
Joined: Fri Sep 03, 2021 3:53 pm
Delivery Date: 03 Sep 2018

Re: Gen 2 AZE0 2018 SOC request

Wed Oct 06, 2021 5:33 pm

I will test this out tomorrow and come back to you with the results! Thank you for the feedback :D

mafify
Posts: 17
Joined: Fri Sep 03, 2021 3:53 pm
Delivery Date: 03 Sep 2018

Re: Gen 2 AZE0 2018 SOC request

Tue Oct 12, 2021 11:43 am

Dala wrote:
Wed Oct 06, 2021 5:23 am
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!

User avatar
Dala
Posts: 366
Joined: Sun Oct 28, 2018 11:24 am
Delivery Date: 01 Jan 2015
Leaf Number: 316851
Location: Finland
Contact: Website

Re: Gen 2 AZE0 2018 SOC request

Wed Oct 13, 2021 12:55 am

I would try and generate all the VCM messages just to be sure
Image

Here you can find a log file from a charging session: https://github.com/dalathegreat/EV-CANl ... 0WAZE0.log

mafify
Posts: 17
Joined: Fri Sep 03, 2021 3:53 pm
Delivery Date: 03 Sep 2018

Re: Gen 2 AZE0 2018 SOC request

Wed Oct 13, 2021 11:24 am

Dala wrote:
Wed Oct 13, 2021 12:55 am
I would try and generate all the VCM messages just to be sure
Image

Here you can find a log file from a charging session: https://github.com/dalathegreat/EV-CANl ... 0WAZE0.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.

User avatar
Dala
Posts: 366
Joined: Sun Oct 28, 2018 11:24 am
Delivery Date: 01 Jan 2015
Leaf Number: 316851
Location: Finland
Contact: Website

Re: Gen 2 AZE0 2018 SOC request

Thu Oct 14, 2021 2:19 am

mafify wrote:
Wed Oct 13, 2021 11:24 am

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?

mafify
Posts: 17
Joined: Fri Sep 03, 2021 3:53 pm
Delivery Date: 03 Sep 2018

Re: Gen 2 AZE0 2018 SOC request

Thu Oct 14, 2021 9:15 am

Dala wrote:
Thu Oct 14, 2021 2:19 am
mafify wrote:
Wed Oct 13, 2021 11:24 am

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.

Return to “Engineering”