The problem: cycler data stuck in CSVs
Battery cyclers export large files per cell. Comparing a full build means stitching those files together by hand.
A cycler run produces a large CSV per cell, with its own column layout. Comparing a full build means opening each file, aligning columns and stitching them into one chart by hand.
What this demo shows
- Upload pouch cell PC-B-06's cycling file, a CSV with one row every 25 cycles out to cycle 1,000.
- Check the data before it saves.
- Compare capacity retention across every cell in the build.
Why it matters
Cycle life data decides which cell design moves forward. Uploading cycler files straight onto the cell record, with a check before saving, keeps that data accurate and connected.
Comparing every cell in the build in one chart shows which design keeps the most capacity, without the spreadsheet work.
See it with your own data
This video is part of Uncountable for batteries. To see how it would work with your own formulations and records, request a demo. Our team replies within 30 minutes during business hours.
Read the transcript
Uncountable stores each cell's test data on its own record. Start with one cell cycler export. Drop it on the cells record and an uploader reads the columns. Check the capacity retention curve before it saves. Files can also arrive on a schedule from SFTP or S3. Compare curves plots every cell of the build.
Design B keeps the most capacity. Its one change from design A is the FEC electrolyte. From cycler file to cycle life chart in Uncountable.
