Welcome Guest,Register Now
Log In

ANT Forum

Welcome guest, please Login or Register

   

Unknown MesgNum

Rank

Total Posts: 2

Joined 2015-04-15

PM

I'm using the FitSDKRelease 14.20 in Java. I record my bike tracks with the Garmin Edge 1000 (SoftwareVersion 280).

While working with its generated .fit files I encountered several unknown message numbers. By unknown I mean that I can't find them in the enum MesgNum.java. The numbers are 13, 79, 113 and 147.

Does anybody know what messages/events they stand for and whether they can be converted in a "XYMesg" class so I can access their data fields?

Thanks!      
Avatar
RankRankRankRank

Total Posts: 296

Joined 0

PM

Please search the forum. This or a similar question has already been asked and answered at least once.

Cheers,
OMB      
Rank

Total Posts: 2

Joined 2015-04-15

PM

Right, I did and I found some answers like this one here (which hasn't been answered yet):
http://www.thisisant.com/forum/adopter-zone/viewthread/4283/

I didn't find all of the numbers I'm looking for as well as I don't know whether they can be converted in Mesg classes in order to access their data (if they have any own fields).      
Avatar
RankRankRankRank

Total Posts: 296

Joined 0

PM

For sure there are other posts with answers.      
Avatar
RankRank

Total Posts: 40

Joined 2009-03-20

PM

There are a lot of fields in Garmin FIT files that are not in the published standard:

markrages@qountdown:~/fit_json-0.1$ ./fit_json.py -lemmon-2013-12-31.fit grep -'"unknown_field_.*"' sort uniq 
"unknown_field_000_of_unknown_message_022"
"unknown_field_000_of_unknown_message_079"
"unknown_field_000_of_unknown_message_104"
"unknown_field_000_of_unknown_message_113"
"unknown_field_001_of_unknown_message_022"
"unknown_field_001_of_unknown_message_079"
"unknown_field_001_of_unknown_message_104"
"unknown_field_001_of_unknown_message_113"
"unknown_field_002_of_unknown_message_022"
"unknown_field_002_of_unknown_message_079"
"unknown_field_002_of_unknown_message_104"
"unknown_field_002_of_unknown_message_113"
"unknown_field_003_of_unknown_message_022"
"unknown_field_003_of_unknown_message_079"
"unknown_field_003_of_unknown_message_104"
"unknown_field_003_of_unknown_message_113"
"unknown_field_004_of_unknown_message_022"
"unknown_field_004_of_unknown_message_079"
"unknown_field_004_of_unknown_message_113"
"unknown_field_005_of_unknown_message_022"
"unknown_field_005_of_unknown_message_079"
"unknown_field_005_of_unknown_message_113"
"unknown_field_006_of_unknown_message_022"
"unknown_field_006_of_unknown_message_079"
"unknown_field_007_of_unknown_message_022"
"unknown_field_007_of_unknown_message_079"
"unknown_field_008_of_device_info"
"unknown_field_008_of_unknown_message_022"
"unknown_field_009_of_device_info"
"unknown_field_009_of_unknown_message_022"
"unknown_field_015_of_device_info"
"unknown_field_016_of_device_info"
"unknown_field_027_of_lap"
"unknown_field_028_of_lap"
"unknown_field_029_of_lap"
"unknown_field_030_of_lap"
"unknown_field_072_of_lap"
"unknown_field_081_of_session"
"unknown_field_253_of_unknown_message_022"
"unknown_field_253_of_unknown_message_079"
"unknown_field_253_of_unknown_message_104"
"unknown_field_253_of_unknown_message_113" 


So there are 42 unspecified fields in my example file.