BQ27Z561-R2: bq27z561-R2 filestream file defintions

Thanks, Nick

We're using both the bq27z561-R2 and the bq35100...


Can you confirm BOTH these devices are flash gauges?

I think the gm.fs file is bonus file...I don't recall getting that out the bq35100 device.

So for upload on both devices...bq.fs should be sufficient?

We're getting ready to put units in the field in the next week, and just need this process down.

Thanks,

Craig

Thank you. I don't think that gauge communication guide (slua801) adequately describes the differences between the files. 

Reading the the bq27z561 reference manual here is what I think they are:

All .fs files are permanent save for the gm.fs file --which writes the data to RAM and then is cleared on reset. So you can try out different settings.

Inferring that from the bq27z561 description here (does not mention the .fs files):

11.1 Manufacture Testing
To improve the manufacture testing flow, the gas gauge device allows certain features to be toggled on or
off through AltManufacturerAccess() commands (for example, LifetimeDataCollection(), CalibrationMode(), and
Gauging()). Enabling only the feature under test can simplify the test flow in production by avoiding any feature
interference. The AltManufacturerAccess() command that toggles ManufacturingStatus()[CAL_EN], [LT_TEST]
will only set the RAM data, meaning the conditions set by this command will be cleared if a reset or seal
is issued to the gauge. The AltManufacturerAccess() commands that toggle ManufacturingStatus()[LF_EN],
[GAUGE_EN] will be updated to data flash and synchronized between ManufacturingStatus() and Mfg Status
Init. ManufacturingStatus() keeps track of the status (enabled or disabled) of each feature.


This sound logical?