Newer JBD versions (tested with firmware 0x28) appear to have more dsgoc2_delay values than documented. I have 2 BMS that have Byte 1 of 0x38 set to 0x90 and 0xC0, indicating that dsgoc2_delay has more values beyond 1280ms. The size (4 bits) for this confirms this suspicion, because only 8 of 16 values are documented.
However, 0xC0 would mean a value of 12 for dsgoc2_delay, which would be 40960ms. And it absolutely makes no sense to set a overcurrentprotection delay to almost 41 seconds, so I believe there is something different going on.
Affected code of JBD_REGISTER_MAP.md
Newer JBD versions (tested with firmware 0x28) appear to have more dsgoc2_delay values than documented. I have 2 BMS that have Byte 1 of 0x38 set to 0x90 and 0xC0, indicating that dsgoc2_delay has more values beyond 1280ms. The size (4 bits) for this confirms this suspicion, because only 8 of 16 values are documented.
However, 0xC0 would mean a value of 12 for dsgoc2_delay, which would be 40960ms. And it absolutely makes no sense to set a overcurrentprotection delay to almost 41 seconds, so I believe there is something different going on.
Affected code of JBD_REGISTER_MAP.md