This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

GPCCEDV: GPCCEDV report: Deviation is so high that it is most likely due to anomaly in the data

Part Number: GPCCEDV

Hi

My customer use GPCCEDV tool to calculate the parameters.

But they have learned several times but have the same report. Deviation is so high that it is most likely due to anomaly in the data.

Attached the data and report.

4048.GPCPackaged-report.zip2465.GPCPackaged.zip

Please give some suggestions.

Thanks

Star

  • Star,

    Can you please upload your raw data to be reviewed. Also please let me know the two different rates you used for the two different log files?

    Thanks,

    Eric Vos

  • 上述文件就是给的原始数据,放电速率是重载4A,轻载2,2A,谢谢!目前是轻载2.2A下不同温度下SOC误差差异大

  • The above file is the original data. The discharge rate is 4A for heavy load and 2,2A for light load. Thank you!  At present, the SOC error varies greatly under the light load of 2.2A and different temperatures  

  • My apologies, I missed the 2nd link of the raw data in the post. I will review this tomorrow and have a response by Friday. 

  • ChaoChao,

    I have reviewed a few of the log files. Room temps and the cold high rate and see a few issues. I did not review all the files once i came accross the issue #2. 

    1) In the room files there are sections where the voltage that spike up to 65K or 32K which seem like a logging issue.

    2) in the cold highrate file the log stops when current is still being applied. It is very critical that each log file is a Charge, Rest, Discharge, then Rest. 

    I think a few of the logs might need to be retaken to meet this format. 

    Thanks,

    Eric Vos

  • VOS,

    Hello!  The voltage reached 65K or 32K at room temperature was caused by the equipment, and the report was calculated after I modified the voltage. Does CEDV require complete data of charging, standing, discharging and standing?  Before, I only uploaded complete discharge data and returned reports with small errors. I re-log the data according to your requirements, but the error of this data is too big. I have done it several times but I can't do it.  Thank you very much!

  • ChaoChao,

    1) I do believe this was a logging issue on the 65K and 32K, and are not real. Our tools may or may not process this correctly so it is best to delete them from the file just to be safe.

    2) No you do not need a charge full charge cycle. the discharge is the critcal one

    3) The biggest issue is the cold temp data's last row still had current flowing at -4K. If you can just retake any files that are cutoff like this to include the rest after the discharge it should greatly improve the result. At this point we cant even really look into the result as is. 

    Thanks,

    Eric Vos