ak
New Member
Posts: 2
|
Post by ak on Mar 22, 2020 18:50:41 GMT
Hi,
just got my NextGen with OBD pro. Installed the app paired the dongle with my Samsung A50, all good. Tiguan Allspace accessable can read and write, clear errors, etc..
When doing long coding it does not show up in history, changes done via adaptation do... Anyone an idea why? Filter is not set, even when mailing the history it is just showing the changes done through adaptation.
BR
Andreas
|
|
fwj
Junior Member
Posts: 99
|
Post by fwj on Mar 22, 2020 20:21:46 GMT
I have the same issue since OBDeleven version 0.11.2 so far:
And I'm very surprised because no one else has reported on it until today.
In the meantime I got a Samsung Galaxy S10 (still using Android 9), new gen dongle and OBDeleven version 0.19.0. Nothing has changed. Adaptations are always saved correctly in the history.
In order to document any changes (including the codings), at least I always do a backup of a control unit before and after the coding.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 22, 2020 21:03:48 GMT
My MQB Platform car is showing long coding in history both on the main screen and in the specific control unit, I will do some more testing in the morning but I can certainly see changes that were done via long coding (both Byte/Bit level and the shortcut versions)
|
|
fwj
Junior Member
Posts: 99
|
Post by fwj on Mar 23, 2020 7:59:04 GMT
So it depends on something. Perhaps also on the data previously stored by older OBDeleven versions for the same car in the cloud?
Since the error occurred from version 0.11.2 onwards, it's still the same car (Tiguan MK2 (5N), MY 18). I have also considered, whether I should delete the car from the OBDeleven garage and read it in again. That probably doesn't do much good, since it won't delete the car history for the VIN in the cloud completely?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 23, 2020 8:24:27 GMT
So it depends on something. Perhaps also on the data previously stored by older OBDeleven versions for the same car in the cloud?
Since the error occurred from version 0.11.2 onwards, it's still the same car (Tiguan MK2 (5N), MY 18). I have also considered, whether I should delete the car from the OBDeleven garage and read it in again. That probably doesn't do much good, since it won't delete the car history for the VIN in the cloud completely? deleting car from garage just hides it from view i am afraid. i will test it again today and confirm if it works on my old cat
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 23, 2020 15:47:20 GMT
Just did it again and I got the same problem, Coding worked but no history update.
But I can see stuff I did on the 5th March so its a recent problem.
|
|
fwj
Junior Member
Posts: 99
|
Post by fwj on Mar 23, 2020 17:23:56 GMT
Somehow reassuring that it is not an individual case. But what does it depend on, that's the question.
It is certainly not due to the current OBDeleven version. I've seen this issue since version 0.11.2 as mentioned before.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 23, 2020 17:34:39 GMT
Thats the odd thing, mine has been working for a while and I certainly have changes recorded in early march. There was an issue with stuff i had archived not moving and that cleared up after you logged off and back on but does not seem to work with this one.
I will raise it as another new bug.
|
|
fwj
Junior Member
Posts: 99
|
Post by fwj on Apr 20, 2020 12:31:27 GMT
Good news. Obviously this issue (long codings missing in history) has been fixed with new OBDeleven Vers. 0.20.0. But didn't have a chance to test it yet. -> forum.obdeleven.com/post/38033/thread
|
|
ak
New Member
Posts: 2
|
Post by ak on May 23, 2020 12:09:57 GMT
Yes, just used ist yesterday and long coding is showing up as well... v0.21.4
|
|