AEK_POW_BMS63EN Fault_L_line_status is always 1

[bitBuddy]

Dear Community members,

I have connected 2 node in ring configuration, and working on an custom pcb for BMS.

In registers Faults1, Fault_L_line_status is always 1, while all other fields of Faults1 and Faults2 registers are 0. 

Also the OVRLATCH is not detected. 

What could be cause to set 'Fault_L_line_status' 1 and where could I check to diagnose.

screenshot for expression view is added for reference for both nodes 1 and 2.

Regards,

bitBuddy

[Max VIZZINI]

Hi,

Let's exclude that you have an electrical issue.

There are several conditions triggering the Fault_L even without the OVRLATCH = 1. These conditions are reported in page 76 of the datasheet.

In the latest version of the BMS driver present in AutoDevKit, we have added a specific structure for the purpose of this check: AEK_POW_BMS63CHAIN_fastDiag_t  

Here you are the function call:

AEK_POW_BMS63CHAIN_fastDiag_t AEK_POW_BMS63CHAIN_node_getFastDiag(AEK_POW_BMS63CHAIN_chain_name_t AEK_POW_BMS63CHAIN_chain_name, AEK_POW_BMS63CHAIN_node_devName_t AEK_POW_BMS63CHAIN_node_devName);

Best Regards,

AutoDevKit Team

[bitBuddy]

Hi Max,

In L9963E data sheet, in Table 21 MISO2 where frame no. is 2 (0b10), is this referring to burst response frame no. 1 in Table 24, 25, 26 ?

[Max VIZZINI]

Hi,

The answer is Yes.

Best Regards,

AutoDevKit Team

[bitBuddy]

Hi Max,

seems it is a documentation error.

with regards,

bitBuddy

[Max VIZZINI]

Hi,

There is one more message described in the miso1 row.

Best Regards,

AutoDevKit Team

[bitBuddy]

Hi Max,

As per observation in logic analyser, in burst(0x78) command feedback frame(MISO1 in table 21), data field is for frame 1 of Table.24 and burst response frame MISO2(in table 21) where frame no. is 2 (0b10) referring to frame 2 of table 24.

Hence we get max of 18 frame (MISO18 : Frame Num-18 (10010) in table 21) . 

Regards,

bitBuddy