Kat,
It appears we have a gap in our tools for bq27510-G3 that we are working on.
EVSW, as you may know, is a legacy tool. For some older products, it is the only tool available. It works well enough for bq27510-G3, except for bqEasy which is hardcoded to look for some parameters that don't exist, which is why you get those error messages.
I would recommend that you instead use GaugeStudio for now. It is itself a transitional tool that is being replaced by our latest GUI that should eventually support all of our latest products.
The latest tool, and one which we will be focusing on exclusively going forward is called Battery Management Studio (aka bqStudio). All new products are being launched with bqStudio as the only tool necessary. Currently the installer only supports a handful of our latest products, but as we test with each existing older product, we will add support over time. As of the time I'm posting this, bqStudio doesn't support bq27510-G3, but it will be added in the near future.
In the meantime, GaugeStudio is the latest tool that does support bq27510-G3. However, GaugeStudio doesn't have a full equivalent of bqEasy. It does have a Chemistry plugin to program the chemID. It does have a plugin called Golden Files, but it simply reads out the flash contents as-is and does not change any flags or copy any learned data to other profiles. This is different from the button in bqEasy, which resets everything and sets flags and other learned parameters to be ready for production.
So...
Temporarily this is what I recommend you do to manually "goldenize" your file after a learning cycle:
After you get a successful learning cycle where Update Status is 02 (for system-side gauges like bq27510 or bq27520) or 06 (for pack-side gauges like bq2754x or bq2774x), you will need to copy the learned data to a few other locations and change some flags.
- The system-side gauges have four Qmax locations. Find the one that updated from your learning cycle (probably Qmax 0) and copy it to the other three locations (Qmax 1 as well as two more Qmax locations within the OCV Tables). Pack-side gauges only have one Qmax, so just leave it as the learned value.
- Change Update Status values.
- For system-side gauges, change all four Update Status values to 02.
- For pack-side gauges, change Update Status from 06 to 02 if you plan to send the IT_ENABLE command in the pack production line or leave it at 06 if you want to leave IT enabled and skip sending the IT_ENABLE command in production.
- Update Ra tables
- System-side gauges:
- There are six Ra tables (Def0, Def1, Pack0, Pack1, Pack0 Rax, and Pack1 Rax).
- Both Pack0 Ra or Pack0 Rax should have been updating during the learning cycle. Find the one with the most recent update (Ra Status and Ra Flag will be 00 / 55) and copy the values of Base, Gain, and all points in the table to the other five tables. Change all Ra Status and Ra Flag values to 00 / 55, except leave the two Rax tables at FF / FF.
- Pack-side gauges:
- There are only two Ra tables. Find the one with Ra Flag = 0055 and copy those values to the other table.
- Change any cycle counters or reset counters to 0.
- Update any Manufacturer Info Block data to your desired values for version control or other purposes.
- Update any other parameters you want, for example
- Change calibration values to the average values taken from samples of your actual production boards.
- Set Avg I Last Run and Avg P Last Run to typical system load values so that the gauge will initialize using those loads for predictions.
- Set SOH Load I to either a typical system load or a maximum system load.
That looks complicated when typed out, but it's basically just reviewing all of your parameters before exporting the golden file. Let me know if you have any questions.
