Hi Chuan,
A scalable way of managing your own ECM parameters for the Battery Builder generated battery block is to leverage an automatically generated centralized script for parameterization.
If you build a battery pack using the Battery Builder App, during the last step of "Create Battery Library," change how you want to define the "Mask Parameters" from "NumericValues" to "VariableNamesByType" or "VariableNamesByInstance".
Similarly, if the battery pack block is generated by API, in the buildBattery call to generate the block, you can change how you want to define MaskParameters. For example,
buildBattery(pack,LibraryName="batteriesVariableNames",...
MaskInitialTargets="VariableNamesByInstance",...
MaskParameters="VariableNamesByType")
When you specify the MaskParameters argument as "VariableNamesByType" or "VariableNamesByInstance", the function generates a parameterization script that you can use to manage the run-time parameters of the modules and cells inside your system.
For more details, please refere to Manage Battery Run-Time Parameters with Centralized Script - MATLAB & Simulink (mathworks.com).
To read more about the buildBattery function, especially the "MaskParameters" name-value explanation, please see Build custom library blocks from battery objects - MATLAB buildBattery (mathworks.com).
Best wishes,
Xiangchun
