Low spin on wedges tested against flightscope

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Snaphook
    Advanced Member
    • Dec 2014
    • 324

    #1

    Low spin on wedges tested against flightscope

    So i got myself a 2nd hand gc 2 unit with SN about 7500 and firmware version 3.5.1.0
    Just some info about myself: I'm currently a 4 hcp and practice a lot on Trackman and flightscope so i have a good understanding of my numbers.
    I tested it at home first and got very low spin numbers with wedges and irons from 8 and down. Thinking maybe it's the flash , so i changed it. (i got a spare one in the deal, but how do i know if it's used?)

    Took it to the the range and set it up together with a flightscope to test.

    Driver/3wood/hybrid/4.5.6,7 irons were all showing pretty matching numbers on GC2 and FS

    8iron to SW were way of with the SW being worst. Some examples:
    GC______FS
    GW 4460 - 10684 This was a brand new prov1
    PW 5672 - 11250
    SW 3666 - 8617
    SW 2790 - 5355
    SW3249 - 6378
    It was only the spin numbers that were off, launch and BS were matching the FS

    What is my next course of action? Tilt calibration, update FW?


  • Stingreye
    Advanced Member
    • Aug 2016
    • 489

    #2
    Wow, those are some low spinning wedges. My gc2 with lob and sand wedge are routinely 10k. Your display is showing total spin not back spin right? There is a menu option to change total spin to just backspin.

    Comment

    • Stingreye
      Advanced Member
      • Aug 2016
      • 489

      #3
      Also were the carry numbers way off? I imagine a sw with 2800 spin goes really far.

      Comment

      • Snaphook
        Advanced Member
        • Dec 2014
        • 324

        #4
        Yes it's set to show total spin with axis.
        And it's giving me about 15-20 meters more carry.

        Comment

        • andygg1986
          Super Member
          • Jan 2016
          • 627

          #5
          I'm not sure what it means but I would point out that several of those are almost exactly half of the flightscope spin number. Might be a clue for someone who knows more than me.

          Both the tilt calibration and updating the firmware are easy and worth a shot.

          Comment

          • mthunt
            Ultimate Member
            • Aug 2014
            • 4746

            #6
            Firmware won't do anything. That's really strange. I find my spin numbers deadly close when I run it next to a trackman or FS which I do from time to time. Tilt is worth a try.
            My Courses:
            World Par 3's by mthunt
            Toronto GC (L) mthunt
            Burlington G&CC by mthunt
            Weston G&CC by mthunt
            London Hunt Club L mthunt
            Park CC Lidar mthunt
            Sunningdale GC Robinson L
            Sunningdale GC Thompson L
            Muirfield Village (liDAR) First Ever Lidar course
            Country Club of Castle Pines (liDAR)
            The Sanctuary GC ProTee L
            The National GC L mthunt
            Mississaugua GC L mthunt
            Shaughnessy G&CC L mthunt
            Markland Woods CC mthunt
            Hidden Lake Old L mthunt
            Magna GC L mthunt
            Barrie CC L mthunt
            mthunt Range

            Comment

            • kinitex@gmail.com
              Member
              • Aug 2014
              • 80

              #7
              Tried cleaning the lenses? Let me know if you ever figure this out as I feel mine reads a bit low too, but not nearly as bad as yours.

              Comment

              • Snaphook
                Advanced Member
                • Dec 2014
                • 324

                #8
                So i did run the tilt calibration and also upgraded to 4.0 FW.
                First shot with a 60 degree showed 9560 spin :-) And it keeps giving me what i expect to be the right numbers. Don't know what was wrong but now it's working so i am very happy.

                Will try it again with the flightscope in a few days just to be sure. (will report back)

                Thanks for your help!

                Comment

                Working...