Why are some of my FIT files not converting?

EDIT: After converting cycling.fit to csv, I found the offending lines in the csv file. Lines 4 to 7 where it is encoding developer data. These lines mostly look ok when I compare to "activity_developerdata.csv" from the docs. A couple of the fields are written in a different order. For example, in my file the "developer_data_index" precedes "application_id", whereas in the example csv file they are declared the other way around. I moved the order of these fields (and corresponding value and units) but this didn't seem to make a difference. My csv file also has a field called "scale" which I deleted, and this didn't help either.

____________________

I'm trying to develop a web app for converting and editing some FIT files. The files are originating from Suunto devices. I have two files here, cycling.fit and windsurf.fit. Both files will convert from fit to csv. Converting back to fit, only windsurf.csv will work. When I convert cycling.csv back to fit I get errors:

FIT CSV Tool - Protocol 2.0 Profile 21.54 Release
Exception in thread "main" com.garmin.fit.FitRuntimeException: Incompatible Protocol Features
        at com.garmin.fit.FileEncoder.write(FileEncoder.java:166)
        at com.garmin.fit.FileEncoder.onMesgDefinition(FileEncoder.java:151)
        at com.garmin.fit.csv.CSVReader.read(CSVReader.java:260)
        at com.garmin.fit.csv.CSVTool.run(CSVTool.java:257)
        at com.garmin.fit.csv.CSVTool.main(CSVTool.java:332)

The windsurf.fit file uses GPS tracking while the cycling.fit file uses GPS and data from an HR sensor and a power sensor.

zip file with the two fit files

Perhaps someone can tell me what is "wrong" with the cycling.fit file?

Top Replies

user_ken over 4 years ago in reply to shmish +1

I'm having the same issue. I take fileA.fit convert it to fileA.csv and if I try to convert back I'm getting the same error. Have you been able to solve this?

All Replies

0 nwillink over 4 years ago

Your FIT files are not corrupt BUT contain corrupt latitude and longitude data with each set to zero, thus spiking to 0,0 on the equator off Africa.

You can see the effect using FITConverter 4.

0 shmish over 4 years ago in reply to nwillink

I don't know what happened with those two files, but I see what you're saying. Not all of my files have that gps problem, I happened to pick two that did.

Here is another file that shows the error I get above (no corrupt latitude and longitude data as far as I know). The problem is that I want to convert it to a csv, modify some data, and re-convert to fit. It won't reconvert even if I leave the csv file unmodified.

0 user_ken over 4 years ago in reply to shmish

I'm having the same issue. I take fileA.fit convert it to fileA.csv and if I try to convert back I'm getting the same error. Have you been able to solve this?

0 Ben FIT over 4 years ago in reply to user_ken

When converting the file from FIT to CSV use the -u option, which will ignore the unknown fields in the file and the file should have a better chance of being converted back to FIT. The -u and other command line options for FITCSVTool can be found here.
developer.garmin.com/.../

0 Former Member over 3 years ago in reply to user_ken

Same problem here with a FIT file generated from the Wahoo app.

My workaround is to delete all the field definitions at the top but it means i lose the "charge" and "workout_type" values. But it's the only way I can move forward and convert those CSV files to FIT.