Skip to Content

Changes for page BMS Main X

Last modified by Admin on 2025/02/19 08:28
From version 1.2
edited by Admin
on 2024/11/22 09:00
Change comment: There is no comment for this version
To version 5.1
edited by Admin
on 2024/12/25 14:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,34 @@
1 +(% class="box infomessage" %)
2 +(((
3 +BMS Main X firmware update procedure is described [[here>>doc:Battery management systems.BMS Main X.5\. Firmware update.WebHome]].
4 +)))
5 +
6 += v2.6.3 =
7 +
8 +[[BMS_Main_X2_v2.6.3.srec>>FileManager.BMS_Main_X2_v2\.6\.3\.srec]]
9 +
10 +== Improvements ==
11 +
12 +* adaptation of the device to the production test bench
13 +
14 += v2.6.2 =
15 +
16 +[[BMS_Main_X2_v2.6.2.srec>>FileManager.BMS_Main_X2_v2\.6\.2\.srec]]
17 +
18 +== Fixes ==
19 +
20 +* resolving the problem of saving device parameters
21 +
22 += v2.6.1 =
23 +
24 +[[BMS_Main_X2_v2.6.1.srec>>FileManager.BMS_Main_X2_v2\.6\.1\.srec]]
25 +
26 +== Fixes ==
27 +
28 +* resolving the issue of preparing battery module states written to Modbus registers
29 +* resolving the problem of writing the device's working time to a non-volatile memory very often
30 +* resolving the problem of returning error states when saving device parameters (mainly via Wi-Fi)
31 +
1 1  = v2.6.0 =
2 2  
3 3  [[BMS_Main_X2_v2.6.0.srec>>FileManager.BMS_Main_X2_v2\.6\.0\.srec]]
... ... @@ -11,6 +11,10 @@
11 11  * new assignments "Charging", "Precharging", "Discharging", "Charging/Discharging", "Main contactor", "Critical error" and "General error (modules)" for the discrete outputs (see the "Signals - Output discrete signals - Assignments" section)
12 12  * new assignments "Critical error" and "General error (modules)" for the relays (see the "Signals - Relays - Assignments" section)
13 13  
14 -Improvements
45 +== Improvements ==
15 15  
16 -
47 +* rearrangements in the settings sections, which are made to simplify the setup process
48 +
49 +== Fixes ==
50 +
51 +* resolving the problem of device hanging due to high activity on the CAN bus during startup