I apologize if I am overlooking something obvious, but I have reread the installation instructions multiple times and am still unable to successfully connect to GSPro. After clicking on the gspro-r10 file the "connection" screen opens and goes through a bunch steps before it seems to fail after going through the "Tilt" step. I have included a portion of the boot screen with debugging turned on in hopes that will help provide some insight on the issue I am having. There is also a line halfway through the boot log that state "Failed to get response for proto 4."
In an attempt to override what I perceived as an error with the Tilt calibration, I also tried turning the "calibrateTiltOnConnect" to false. However, that didn't fix the issue.
Again, I apologize if I am making a stupid mistake. I just purchased GSPro after having my Garmin R10 for almost 2 years during which time I had been using E6 without issue, but got tired of the cost and the lack of quality.
I apologize if I am overlooking something obvious, but I have reread the installation instructions multiple times and am still unable to successfully connect to GSPro. After clicking on the gspro-r10 file the "connection" screen opens and goes through a bunch steps before it seems to fail after going through the "Tilt" step. I have included a portion of the boot screen with debugging turned on in hopes that will help provide some insight on the issue I am having. There is also a line halfway through the boot log that state "Failed to get response for proto 4."
In an attempt to override what I perceived as an error with the Tilt calibration, I also tried turning the "calibrateTiltOnConnect" to false. However, that didn't fix the issue.
Again, I apologize if I am making a stupid mistake. I just purchased GSPro after having my Garmin R10 for almost 2 years during which time I had been using E6 without issue, but got tired of the cost and the lack of quality.
I appreciate any help that can be provided.
12:05:27.668 R10-BT >> { "service": { "shotConfigResponse": { "success": true } } } 12:05:27.669 R10-BT || Device Setup Complete: 12:05:27.670 DEBUG || <- 8813B41300030000000000000000 (raw) 12:05:27.672 R10-BT || Model: Approach R10 12:05:27.674 DEBUG || <- 12008813B41300030000000000000000C3F3 (framed) 12:05:27.675 R10-BT || Firmware: 4.30 12:05:27.677 DEBUG || <- 000212058813B41302030101010101010103C3F300 (encoded) 12:05:27.678 R10-BT || Bluetooth ID: C837136FDA27 12:05:27.679 DEBUG || <- 000212058813B41302030101010101010103C3 (ble write) 12:05:27.680 R10-BT || Battery: 58% 12:05:27.681 DEBUG || <- F300 (ble write) 12:05:27.682 R10-BT || Current State: Error 12:05:27.684 R10-BT || Tilt: { "roll": -0.099037886, "pitch": 19.880442 } 12:05:29.622 DEBUG || -> 0100022104B4130201010101020D0101020D0101 (ble read) 12:05:29.624 DEBUG || -> 0109F2010A12080A0608071202080816E400 (ble read) 12:05:29.626 DEBUG || -> 022104B4130201010101020D0101020D010109F2010A12080A0608071202080816E4 (encoded) 12:05:29.629 DEBUG || -> 2100B4130200000000000D0000000D000000F2010A12080A0608001202080816E4 (decoded) 12:05:29.630 DEBUG || <- 8813B41300020000000000000000 (raw) 12:05:29.631 DEBUG || <- 12008813B41300020000000000000000CE63 (framed) 12:05:29.632 DEBUG || <- 000212058813B41302020101010101010103CE6300 (encoded) 12:05:29.635 DEBUG || <- 000212058813B41302020101010101010103CE (ble write) 12:05:29.637 DEBUG || <- 6300 (ble write) Error 2.txt