Harry's GPS Suite Forum

If I remember right "D" should have "self-learning" ability, am I correct? It worked for me for a long time (on several cars) until I´ve tried it on my new company car which is on "new" VW MQB platform (Skoda Fabia 3gen model year 2018) Same App, same OBD (same FW in it), nothing changed in settings. After that, "D" stopped working propertly even on my older Octavia 2010. I dont want to reset all settings in HLT because I have settings for cars, lap times etc. in app :/

I have HLT on 2 devices, so maybe I will sacrifice settings in one of them for test.

Whether throttle is available in the standard position or D, etc, depends on the car, not the adapter or app version. You need to test which one is working for your car. Please always start with the standard PID. Throttle is going through calibration, to get a proper 0-100% display, you will need to have the car in full throttle for some time (no problem on track).

- Harry

Today I tried all PIDs for throttle, no one worked, except "Standard" but this displays irelevant datas - so its unusable. On all other PIDs was nothing :/

Im not a programer, but if I checked sensor list, I see this. So, OBD can read PID "D" from car, but app shows nothing

This means the ECU responds to AppD. This does not mean your Skoda delivers anything useful. In addition, at least for the point in time you created the snapshot, LapTimer didn’t use AppD but some other PID. PIDs actually requested will show a response time in brackets.

When changing an Expert Setting, it is a good idea to refresh the sensor from Sensor List, this will restart all sensor integration and use the changed settings.

In case you want to see what your Skoda actually responds, you can trace the dialog. See “Debugging OBD Connections” in the FAQ section.

Harry

Ok Ill try it. but what I do not understand is that it worked fine before (aprox 6 months ago). On this car, with same OBD (i´ve tried FW 4.3.0 and 4.3.2) and same app (older version). What changed? :/