XGPS160 (Beta V3.4.5) Causing Status Not Ready

Help on issues you run into with LapTimer; in case you have a question on how to use LapTimer, use the forum "Using LapTimer" instead
Post Reply
asaed330
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 2
Joined: Sun Jun 02, 2019 9:16 am

XGPS160 (Beta V3.4.5) Causing Status Not Ready

Post by asaed330 » Sun Jun 02, 2019 9:24 am

I was at Thunderhill this weekend and tried to use my XGPS160 with the beta FW 3.4.5 and it would cause my Harry's app overall status to be NOT READY. This in turn caused my first session to not record because the timer never started possible because it could not lock a location. So during my debug process back in the pits, when I disconnected the Bluetooth connection to XGPS160, it went to All Set. So the app worked great for the rest of the day with the phone's GPS, but not the XGPS160. I really want to use the XGPS160 because of the higher sampling frequency. I am using Harry's v23.0.1 Petrolhead Edition on iPhone6 on iOS 12.0.1.
asaed330
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 2
Joined: Sun Jun 02, 2019 9:16 am

Re: XGPS160 (Beta V3.4.5) Causing Status Not Ready

Post by asaed330 » Thu Jun 06, 2019 2:18 am

Harry, could you please provide some guidance for debug to help resolve this issue?
User avatar
Harry
Site Admin
Site Admin
Posts: 9365
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: XGPS160 (Beta V3.4.5) Causing Status Not Ready

Post by Harry » Thu Jun 06, 2019 6:05 am

Is 3.4.5 a beta firmware and has it been installed using Dual’s app?

While connected, what do you see in LapTimer / Administration / Sensors?

Please make sure you kill the Dual app, it will block access for LapTimer even when running in background.

Harry
Image Image Image Image
Post Reply