Frequently Asked Questions
Which devices are supported?
rubiTrack supports many kinds of devices via direct sync which imports activities directly from the device connected to your Mac. In addition rubiTrack supports activity file import for other devices that do not support direct sync.
|Device||Model||Direct Sync||File Import|
|Apple Watch||Series 1, Series 2, Series 3 GPS, via rt2go||•|
|Garmin Forerunner||935, 920XT, 910XT, 735XT, 630, 620, 610, 235, 230, 225, 220, 210, 310XT, 410, 405, 405CX, 35, 25, 15, 10, 110, 70, 60, 50, 205, 305, 201, 301||•|
|Garmin Edge||1000, 820, 810, 800, 520, 510, 500, 200, 705, 605, 305, 205, 25, 20, Touring||•|
|Garmin||fēnix 5, 3, fēnix 2, fēnix, SWIM, GPSMap 62, Dakota, Oregon, Colorado, eTrex||•|
|Suunto||Ambit 3, Ambit 3 Peak, Ambit 3 Run, Ambit 2, Ambit 2s, Ambit with Moveslink2||•|
|Suunto||T6, T6c, T6d, X9i, X9Mi, X10||•|
|Polar||V800, M400, V650, M450 via file import||•|
|Polar||RC3 GPS via HRM/GPX||•|
|Polar||RCX5, CS500, FT40, FT60, FT80, RS300X via HRM/GPX, polarpersonaltrainer.com XML, RS800, RS800CX, S610, S610i, S625X, S710, S710i, S720i, S725, S725X, S810, S810i, CS600, E600, AXN500, AXN700, Sport Tester, Vantage XL, Vantage NV, Accurex Plus, XTrainer Plus, Coach||•|
|TomTom||Runner Cardio, Runner, Multi-Sport||•|
|Amod||3080 GPS Tracker||•|
|Timex||GPS Global Trainer||•|
|Sigma||Sigma Rox FIT & CSV||•|
|Daum||Daum Ergometer CSV||•|
|Withings||WiFi Body Scale||•|
Which file formats are supported?
rubiTrack supports the following file formats. If you have a file format you would like to see supported by rubiTrack email us.
|File Format||Import||Export (Mac)|
|FIT (Activity, Weight)||•|
|TCX (Garmin Training Center)||•||•|
|Sporttracks FITLOG (Activities)||•|
|Sporttracks LOGBOOK (Athlete Log)||•|
|NMEA GPS Log||•|
|Polar polarpersonaltrainer.com XML||•|
|Suunto Movescount XML||•|
|Sigma Rox FIT & CSV||•|
|Daum Ergometer CSV||•|
|General purpose CSV import for trackless activity history and athlete log data||•|
Which cloud services are supported?
rubiTrack supports the following cloud services.
|Withings (Body weight and health data)||•|
|Fitbit (Body weight and health data)||•|
I have a problem accessing Garmin Connect, what can I do?
If you have trouble accessing Garmin Connect, first make sure you're using the latest version of rubiTrack (the latest version is 5.0.6).
If this doesn't fix the problem, log into Garmin Connect using your web browser and change your password. Now re-authorize rubiTrack in the Sync Manager. Everything should work fine now.
If syncing with Garmin Connect still does not work, please let us know about the problem.
Can I import activities I have stored in SportTracks?
Yes! You can export existing activities from SportTracks to the FITLOG format which you can then import into rubiTrack.
I have data in a spreadsheet, how can I import it?
You can use tabular CSV data to import both activity summary data (activities without track or GPS data) and athlete log records.
Activity Summary CSV
- The field separators are either semicolon ";" or tab, comma cannot be used as a separator.
- The order of columns is arbitrary.
- All fields except date are optional.
- Some values like distance and temperature are interpreted according to the current unit setup in rubiTrack's Unit preferences.
- If country code, division and city are given and they are contained in the rubiTrack database, weather information will be looked up automatically.
- All numbers with decimal digits use the dot "." as decimal separator.
|date||2015-11-12 14:40:43-0800||The activity start timestamp (mandatory)|
|timezonename||America/Los_Angeles||Unix time zone name|
|countrycode||US||ISO2 or ISO3 country code|
|activitytype||Trail Running||Activity type, must match one of the activity types (English)|
|equipment||Asics 43X, Garmin FR 620||Comma-separated list of equipment names|
|notes||Too late for my taste||Notes|
|tags||hot,lots of traffic,late||Comma-separated list of tags|
|temperature||26.7||Temperature in degrees Celcius or Fahrenheit (depending on unit setup)|
|weather||partly cloudy||Weather condition, must match one of the weather conditions rubiTrack supports (English, lower case)|
|totalduration||1:20:23||Total duration in D:H:M:S|
|duration||1:19:51||Active duration in D:H:M:S|
|totaldistance||14.78||Total distance in kilometers or miles (depending on unit setup)|
|distance||14.78||Active distance in kilometers or miles (depending on unit setup)|
|avgspeed||10.4||Average speed in kilometers per hour or miles per hour (depending on unit setup)|
|minspeed||4.2||Minimum speed in kilometers per hour or miles per hour (depending on unit setup)|
|maxspeed||14.6||Maximum speed in kilometers per hour or miles per hour (depending on unit setup)|
|ascent||234||Ascent in meters or feet (depending on unit setup)|
|descent||231||Descent in meters or feet (depending on unit setup)|
|avgheartrate||165||Average heart rate in BPM|
|minheartrate||120||Minimum heart rate in BPM|
|maxheartrate||178||Maximum heart rate in BPM|
|calories||789||Calorie expenditure in kCal|
|avgcadence||90||Average cadence (cycling rpm) or steps per minute (one foot)|
|mincadence||30||Minimum cadence (cycling rpm) or steps per minute (one foot)|
|maxcadence||100||Maximum cadence (cycling rpm) or steps per minute (one foot)|
|avgpower||81||Average power in watts|
|minpower||0||Minimum power in watts|
|maxpower||413||Maximum power in watts|
|totalenergy||4310||Total energy in kJ|
|trainingintensity||1.12||Training intensity in percent (1.0 = 100%)|
|trainingstresslevel||252||Training stress level|
Athlete Log CSV
- The field separators are either comma ",", semicolon ";" or tab.
- The order of columns is arbitrary.
- All fields except date are optional.
- Fields can be filled in one line and not in another, it doesn't have to be consistent (except for date which has to be filled in every line).
- For all weight related columns there are 3 versions, for example weight, weight_kg and weight_lbs. If the first version is used, rubiTrack determines the unit of the value based on the setting in the preferences. The other two versions pre-set the unit for the import. Only one of the three variants should be used in one single CSV file.
- All numbers with decimal digits use the dot "." as decimal separator.
|date||2015-11-05 09:20:37||Timestamp in local timezone (mandatory)|
|weight||81.7||Weight in kilograms or pounds (depending on unit setup)|
|weight_kg||81.7||Weight in kilograms|
|weight_lbs||165.2||Weight in pounds|
|fatmass||8.3||Fat in kilograms or pounds (depending on unit setup)|
|fatmass_kg||8.3||Fat mass in kilograms|
|fatmass_lbs||17.2||Fat mass in pounds|
|fatmass_percent||7.1||Fat mass in percent|
|hr_min||56||Minimum heart rate|
|hr_max||180||Maximum heart rate|
|hr_rec||102||Recovery heart rate|
|bodywater||43||Body water in percent|
|bmr||1398||Basal metabolic rate|
|amr||3201||Active metabolic rate|
|metabolic_age||35||Metabolic age in years|
|bonemass||15.1||Bone mass in kilograms or pounds (depending on unit setup)|
|bonemass_kg||15.1||Bone mass in kilograms|
|bonemass_lbs||32.8||Bone mass in pounds|
|musclemass||37.1||Muscle mass in kilograms or pounds (depending on unit setup)|
|musclemass_kg||37.1||Muscle mass in kilograms|
|musclemass_lbs||71.7||Muscle mass in pounds|
|visceralfatmass||1.2||Visceral fat in kilograms or pounds (depending on unit setup)|
|visceralfatmass_kg||1.2||Visceral fat in kilograms|
|visceralfatmass_lbs||2.6||Visceral fat in pounds|
|visceralfat_percent||8||Visceral fat in percent|
|skinfold||13||Skinfold in centimeters|
|bpsys||120||Systolic blood pressure|
|bpdia||80||Diastolic blood pressure|
|sleep||7||Sleep in hours|
Where is my rubiTrack file?
If you can't remember where your rubiTrack file is located on your hard disk:
rubiTrack 5 Pro, rubiTrack 4 Pro
- Start rubiTrack Pro (your file will be opened automatically).
- Select "File > Show In Finder" from the main menu.
- Start rubiTrack (your file will be opened automatically).
- Hold the COMMAND key and click into the filename in the title bar of the rubiTrack main window.
- A menu will open that shows the full path.
- Select the first folder in the menu to switch to Finder.
How can I upgrade my old rubiTrack file to rubiTrack 5 Pro?
All you need to do is open your rubiTrack 4 Pro, rubiTrack 3 or rubiTrack 2 file in rubiTrack 5 Pro via "File > Open…" from the main menu.
First you need to know where your put your old file (see Where is my rubiTrack file?).
- Start rubiTrack 5 Pro.
- Select "File > Open…" from the main menu.
- Select your old rubiTrack 3/2 file.
- rubiTrack 5 Pro will offer to upgrade the data, click "Upgrade".
- When the upgrade is finished, select "File > Save As…" to save it under a new name.
Depending on the size of the data, the upgrade process and saving the new file for the first time may take some time to complete.
Syncing with TomTom
In order to direct sync with your TomTom device, you need to set up the TomTom MySports Connect software appropriately.
- Install the TomTom MySports Connect software.
- Set up TomTom MySports Connect to export FIT files on the "UPLOAD & EXPORT" page (Click "ADD" and select "FIT-format for training applications").
- Make sure you're not exporting multiple file formats as this will lead to duplicates in rubiTrack.
- If you changed the name of your TomTom watch, go to rubiTrack's advanced import preferences and enter the name of your watch (via "rubiTrack > Preferences >> Advanced" from the main menu).
- Download activities from your TomTom device using the TomTom MySports Connect software.
- When finished, you can use rubiTrack 5 Pro to sync the data.
What if I find a bug?
If you find a problem please do not hesitate to let us know and email us. We appreciate your feedback!
rubiTrack 5 Pro is compatible with macOS High Sierra (10.13, 64 bit) and macOS Sierra (10.12, 64 bit). WiFi sync requires a Mac built 2012 or later.
rt2go is available for iPhone running iOS 11 or later.
Is there a trial version?
Yes, you can try rubiTrack 5 Pro for 14 days. With the exception of file saving, the trial version is functionally identical to the full version.
Do I get updates for free?
Yes, all updates to 4.x versions are free.
I'm in a running/cycling team. Do you offer bulk licenses?
Yes we do! If you want to purchase 10 or more licenses for members in your club or team, please contact rubiTrack support.
Do I get a discount on new major versions?
Yes, you will receive a discount for upgrading to a new release when it becomes available.
Do NOT put rubiTrack files in your Dropbox!
Your rubiTrack file will get damaged if you do!
Dropbox does not handle Mac package files (which is a folder containing other files and folders) correctly when you put them into the Dropbox sync folder. rubiTrack for Mac uses such a package file format. Under certain circumstances, Dropbox will corrupt such files, which can cause some or all data to be lost or become unreadable. This is a problem known to Dropbox for many years and it affects not just rubiTrack but hundreds of Mac apps that use a package file format.
Do NOT use Dropbox or similar sync service with your rubiTrack for Mac file. If you want to sync multiple Macs using Dropbox, create a ZIP'd copy of your rubiTrack for Mac data file and put that into your Dropbox instead.
Why are rubiTrack's measurements different from my device's measurements?
rubiTrack calculated measures are not necessarily wrong, they're just different from what the device shows you (which sometimes is definitely wrong).
Differences part 1: Calculation vs. Copying
Whenever possible rubiTrack calculates all values it displays based on the data the device reports for the workout. The data usually consists of a stream of GPS data and heart rate, cadence, power values, and so on.
Garmin Training Center (and others) use the device-calculated averages and absolute values (like distance, duration and average heart rate) unverified. This often leads to a displayed distance that does not agree with the GPS data.
rubiTrack allows the display of calculated data or original device data. You can easily switch between the two at any time (Activity > Update Activity > Using Original Device Data).
Differences part 2: Calculation errors
In many cases the distance the device calculates is slightly different from what rubiTrack calculates. rubiTrack uses a high-precision algorithm that works very reliably, more reliable than what a device could possibly calculate given its very limited computing power. Also, in some cases the distance can differ significantly because - like any other computer - GPS devices have bugs. And those cause rather big errors in distance calculations on the device from time to time.
In both cases a difference in calculated distance will cause a - possibly significant - discrepancy in average speed, pace and other values.
Differences part 3: Different Algorithms
There are also other reasons for values being different. Those are not necessarily errors in calculations, instead they are caused by different methods of how they are calculated.
One example is maximum speed. Largely because of the very coarse time base GPS coordinates are timestamped with, calculating a maximum speed value between 2 points only leads to incorrect results. Values calculated this way would be unrealistically high if the timestamp induced error is large enough - which tests show they are.
This is why we use a running average over a couple of points to calculate the maximum speed. Garmin also does this on the device. You can verify this by watching the speed measure on the device when you stop. You will notice that the speed reported by the device will not jump to zero instantly, instead speed will drop to zero gradually. This is because it's an average over the last couple of points recorded by the device.
The reason why the values differ between rubiTrack and your device is that the way these running averages are build differ. They are calculated in different ways, both are correct.
Differences part 4: Too many unknowns
One other popular example is the calorie calculation. If you are using a heart rate monitor, chances are that the number rubiTrack calculates is different from the number your device calculated. Again, this is because the device uses a different algorithm than rubiTrack in order to calculate the calories burned. Unlike in the above maximum speed example though, there is a very high probability that both rubiTrack and the device got it wrong. This is because it's incredibly difficult to calculate burned calories with only a handful of data that is available for the calculation. Regardless of where the value is coming from, always know that this is only an estimation and it's very likely not what the real calorie expenditure was.
So, while rubiTrack does not agree with the device on the burned calorie value, neither of the calculations give you an accurate number, both are estimations.