Search found 19 matches

by spaRTan
Tue Mar 04, 2014 6:56 pm
Forum: Trouble Shooting
Topic: Inconsistent GPS update rate on XGPS160
Replies: 13
Views: 5512

Re: Inconsistent GPS update rate on XGPS160

Thank you Harry.
I wanted to contact them myself tonight - now I won't have to. :)

I'm very eager to receive their opinion on this topic.
I don't understand how everybody else can use the device without any hassle.
by spaRTan
Tue Mar 04, 2014 5:21 pm
Forum: Trouble Shooting
Topic: Inconsistent GPS update rate on XGPS160
Replies: 13
Views: 5512

Re: Inconsistent GPS update rate on XGPS160

Any ideas now that you've seen it on the HLT-screenshot?
The peaks are rolling in every 1 second all time long.
by spaRTan
Tue Mar 04, 2014 11:44 am
Forum: Trouble Shooting
Topic: Android & BT1A - error message
Replies: 9
Views: 3203

Re: Android & BT1A - error message

Harry wrote:No update rate shown means 0 Hz. This in turn means LapTimer does not receive a full set of PIDs. Please check the Debugging OBD thread here on the forum.
Thanks Harry - will do so. :)
by spaRTan
Tue Mar 04, 2014 10:11 am
Forum: Trouble Shooting
Topic: Android & BT1A - error message
Replies: 9
Views: 3203

Re: Android & BT1A - error message

There is no update rate showing in the sensors list. The sensor is connected and HLT shows a green lamp. I then tried RaceChrono and there the update rate is 1Hz for the slow channels (temperatures) and between 10Hz and 13,5Hz for the fast channeln (throttle, RPM). [Sorry for comparing to other apps...
by spaRTan
Sun Mar 02, 2014 8:13 pm
Forum: Trouble Shooting
Topic: Inconsistent GPS update rate on XGPS160
Replies: 13
Views: 5512

Re: Inconsistent GPS update rate on XGPS160

Today I updated the firmware of the XGPS160 to 1.2. Sadly it didn't improve the situation. I took comparable logs using HLT Rookie and RaceChrono on my Nexus 5 (see screens below). Conclusions: 1. The velocity sent by the XGPS is crap in both apps. 2. In RC it's a bit more smooth but way too bad to ...
by spaRTan
Sun Mar 02, 2014 11:22 am
Forum: Trouble Shooting
Topic: Inconsistent GPS update rate on XGPS160
Replies: 13
Views: 5512

Re: Inconsistent GPS update rate on XGPS160

Thought #3 was my first one as well. As you can see the original screenshot from HLT shows the same behaviour. At first i thought it's a problem of bad GPS quality or dropouts but it's always there (I had 13 satellites and a perfect signal position-wise). The graph section of born2race uses all the ...
by spaRTan
Sat Mar 01, 2014 6:21 pm
Forum: Trouble Shooting
Topic: Android & BT1A - error message
Replies: 9
Views: 3203

Re: Android & BT1A - error message

I've tested it on a 2013 BMW M135i using a cheap vGate ELM. Here is a link: http://dynamic.de.focalprice.com/ER1957W/Vgate_Bluetooth_ELM327_Mini_OBD2_Car_Diagnostic_Scanner_White_.html?Currency=EUR As said before Torque and DashCommand are working fine. It would be great to get it to work. Can I see...
by spaRTan
Sat Mar 01, 2014 6:16 pm
Forum: Trouble Shooting
Topic: Inconsistent GPS update rate on XGPS160
Replies: 13
Views: 5512

Re: Inconsistent GPS update rate on XGPS160

Please have a look at the second acceleration graph of the Porsche Turbo. Speed isn't rising consistently as the car accelerates but rises, stays, rises again and so on. This is (of course) not how my cars accelerate at all. Thus there are only few options left: 1. The XGPS160 offers less quality GP...
by spaRTan
Thu Feb 27, 2014 7:39 pm
Forum: Trouble Shooting
Topic: Inconsistent GPS update rate on XGPS160
Replies: 13
Views: 5512

Inconsistent GPS update rate on XGPS160

After having successfully used HLT with a XGPS150A for a long time I upgraded to the XGPS160. Now I'm getting weird results and massive "lag" in the velocity graph. The faster the acceleration the bigger the lag. Could it be that HLT cannot process the information fast enough? I haven't tr...
by spaRTan
Thu Feb 27, 2014 6:46 pm
Forum: Trouble Shooting
Topic: Android & BT1A - error message
Replies: 9
Views: 3203

Re: Android & BT1A - error message

I've got an ELM327 BT device and I get the same error on my Nexus 5.
DashCommand and Torque are running without any problems.
In the experts setting when clicking on "Info" I can see the PIDs sent by the OBD-device.

What could be wrong?