Complete

WERETECH-8593

We were unable to reproduce this issue, but we can investigate further if we receive more complaints about this issue.

Fit files created by simulator no longer able to be converted to csv using FitCSVTool.jar

I am using SDK 3.1.7 and FitSDKRelease_21.22.00.

I run the simulator and create some data using Simulation->FIT Data->Simulate Data.  After running this I select Stop and then select 'Save FIT session' which asks me for a filename etc.

In the past I could then convert the FIT file into a csv by running:

java -jar /.../FitSDKRelease_<nn_nn_nn>/java/FitCSVTool.jar -b <file>.fit <file>.csv

but this is now returning the following error:

FIT CSV Tool - Protocol 2.0 Profile 21.22 Release
Exception in thread "main" java.lang.RuntimeException: com.garmin.fit.FitRuntimeException: FIT decode error: File is not FIT format.  Check file header data type. Error at byte: 24
    at com.garmin.fit.csv.CSVTool.run(CSVTool.java:246)
    at com.garmin.fit.csv.CSVTool.main(CSVTool.java:332)
Caused by: com.garmin.fit.FitRuntimeException: FIT decode error: File is not FIT format.  Check file header data type. Error at byte: 24

I am using macOS Mojave v.10.14.6

vaughan
Parents
  • in reply to Stephen.ConnectIQ

    Sorry if I chime in here. But it's unknown for me whether OP has already responded or not, e.g. via e-mail.

    As I've already mentioned I'd exactly the same issue as OP. In the meantime this issue is largely solved, as can be seen and reproduced in

    forums.garmin.com/.../remarks-about-saving-replaying-a-fit-with-sim

    The reason for this issue is mainly an operation error of the user with using the sim. If the activity isn't explicitely saved, the .fit isn't properly finalized or something else. This causes to abort FitCVSTool.jar with error, or if replaying the .fit with the sim nothing happens.

    Since it's always possible that a user not properly saves a .fit, I think it's a good idea for a RFE. It make sense to support/warn the user to generally prevent this issue. IMHO this can be done by forcing the finalizing of the .fit, or blocking the saving of the .fit by greying out the save option, or at least output a warning message if saving a corrupt .fit.

Comment
  • in reply to Stephen.ConnectIQ

    Sorry if I chime in here. But it's unknown for me whether OP has already responded or not, e.g. via e-mail.

    As I've already mentioned I'd exactly the same issue as OP. In the meantime this issue is largely solved, as can be seen and reproduced in

    forums.garmin.com/.../remarks-about-saving-replaying-a-fit-with-sim

    The reason for this issue is mainly an operation error of the user with using the sim. If the activity isn't explicitely saved, the .fit isn't properly finalized or something else. This causes to abort FitCVSTool.jar with error, or if replaying the .fit with the sim nothing happens.

    Since it's always possible that a user not properly saves a .fit, I think it's a good idea for a RFE. It make sense to support/warn the user to generally prevent this issue. IMHO this can be done by forcing the finalizing of the .fit, or blocking the saving of the .fit by greying out the save option, or at least output a warning message if saving a corrupt .fit.

Children
No Data
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries