This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sync Virb with Express

Hi
Everytime I sync my Virb Elite with Garmin Express I get an failure. Please try again.
Some fit files do upload to GC.
Last time I tried to sync I got the same failure. I then went to activity folder and erased all fit files an then sync with no problems.
Today I turned on the Virb for a ride. Did no videos, only a ride. And when I got home, I turned the Virb off.
Connected the Virb to my mac for sync and the same problem appeared.
Looked in to the folder again and saw 4 fit files. 3 small about 5 to 15 kb and 1 big around 500 kb. Erased them one by one and sync each time. Still same problem.
Only when the folder is empty for fit files. Sync is the okay.
But GC do get the ride :confused:

So does anyone have the same problem?

Garmin Express V. 3.2.6.0
Garmin Virb V. 3.70
MacBook Air OS X 10.9.3
  • I did fully deleted Express from my Mac, and cleaned up the Virb related files in Garmin folder in Application Support, and clean install again; no success yet. The deletion of all aforementioned files didn't help as well...


    Try delete all the fit file with the size of 375 bytes inside the Virb Camera. Theese files are created when you plug in the USB if the Virb is off.
    And next time, turn on the Virb before you plug in the USB.
    This fixed my sync problem for now...
  • TRUSTDK

    The VIRB shouldn't create a 375 KB .FIT each time it starts up. If you delete the contents of the Garmin\Activity folder then it should remain empty until the VIRB is in a spot to acquire satellites. It might create a 1kb flie but the files should only grow in size when the VIRB has acquired satellites and is moving. I suggest you do a master reset on the VIRB which show clear all user data and see if it recreates that 375 KB file.

    How do I perform a master reset on my VIRB or VIRB Elite?

    Curt
  • TRUSTDK

    The VIRB shouldn't create a 375 KB .FIT each time it starts up. If you delete the contents of the Garmin\Activity folder then it should remain empty until the VIRB is in a spot to acquire satellites. It might create a 1kb flie but the files should only grow in size when the VIRB has acquired satellites and is moving. I suggest you do a master reset on the VIRB which show clear all user data and see if it recreates that 375 KB file.

    How do I perform a master reset on my VIRB or VIRB Elite?

    Curt

    Please listen to me.

    Did a Master reset here this morning. Turned on my Virb and plug in the USB. No problems there.
    But if the Virb is turned off and you plug in the USB, the Virb turns on automatically then the problem happens. Unsuccessfully Sync with Garmin Connect.
    I've attached the new created FIT file with the size of 375 bytes. This file must be erased before I can do a Sync with success.
    So I say it again. For me, I have to turn on the Virb before I plug in the USB and there must not be any FIT files with the size of 375 bytes inside the VIRB.
    This FIT file I am referring to, is only created, when the VIRB is off and you plug in the USB
  • Hi, Interesting indeed, when I removed a 375 bytes FIT file from the Virb before syncing, it worked and the activity showed up in GarminConnect.
    Best regards,
    Gert Jan
  • Ciao Customer Care :)
    Is it possible to get some info regarding the issue :confused:
  • Would indeed be interesting to see a response from Customer Care, since the error is fairly easy to reproduce; probably time for an update on virb or so?
    Issue is open for some time now.
  • One question.
    I know that my english isn't perfect, but have I missed something at school. Customer Care how is that translated to Danish in your company?
    My teacher told me that it means caring for customers and not ignoring them... :(
  • New update for VIRB 3.80 but no fix for the 375 Byte FIT file :(
  • Same for me, I'm at this very moment e-mailing with product support, see if they can act :-(
  • We are currently investigating this issue, we will update this post when we have a solution.


    Rowan