|
Post by macadam on Mar 23, 2021 12:52:22 GMT
Hello, I received my standard (not pro) ODBeleven yesterday and I started to run a full scan. I also explored the app and I discovered the "History" list. Then I found in the history a Long Coding which changed 1 bit in the dashboard unit and this seems very strange because I should not be able to perform long coding as I bought the basic version. Could someone confirm if this is normal, please? Is this long coding something automatically performed? I'm worrying because my Nav system doesn't work anymore...
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 23, 2021 13:03:26 GMT
If you have used a one click app then the history file will show the app being used and then if there is long coding changes the Long coding changes.
|
|
|
Post by macadam on Mar 23, 2021 15:12:02 GMT
I'm not sure I understood what you meant. So if I'm using a 1-click app and this 1-click app uses long coding then I'll see the 1-click app + the long coding in the history file?
I tried with the dashboard Needle Swap app and only the app appeared in the history file. I'm surprised the long coding timestamp shows it happened ~30 seconds after the full scan beneath.
As I wrote, I have the basic ODBeleven version so I shouldn't be able to execute long coding myself. I wonder if selecting something in the app could trigger this.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 23, 2021 15:32:34 GMT
I'm not sure I understood what you meant. So if I'm using a 1-click app and this 1-click app uses long coding then I'll see the 1-click app + the long coding in the history file? yes that is correct you don't see the other changes but you do (OR LAST TIME I CHECKED) see long coding and yes it has a different time stamp no idea why according to this forum.obdeleven.com/thread/6930/obdeleven-coding-itc-forumStaging [WORKING] Not working on the Virtual Cockpit 1. Control Unit 17 (Dashboard) 2. Long coding 3. Staging: change value to "Yes" [Standard: "No"] OR: 3. Byte 1 4. Check Bit 0 The change on byte 1 from A4 TO A5 is the above coding According to the above page and from what I have seen on Seat forums this does not work on the new digital dash.
|
|
|
Post by macadam on Mar 23, 2021 15:52:23 GMT
Aaaah Staging means "Gauge test-needle sweep". This makes sense, it matches with what I did. Thank you very much!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 18, 2021 12:02:40 GMT
Just to add to this thread, the Android Release 36 has put in a fix so you no longer get the long coding shown when you do a one click app.
|
|
|
Post by dv52 (Australia) on Apr 18, 2021 21:32:29 GMT
@testeronline : Why would OBD11 developers delete these records?
Have the developers not read the tales of woe on this forum recounting how folk have not been unable to unwind the changes that Apps have made to their cars?
I would have thought that the opposite should happen; the records of changes to long-code by Apps should be extended to include adaptation channels too!!
What special kind of madness has inspired this decision?
Don
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 19, 2021 4:24:00 GMT
The special madness is that many people get confused when they see changes that they do not recognize as per this thread.
There are many users who only do one click apps and the extra information causes confusion and support calls.
I would compare the one click app process with tools like caristaapp where user does not have access to code or see underlying changes.
|
|
|
Post by dv52 (Australia) on Apr 19, 2021 19:46:39 GMT
@testeronline : hmm......... so, if my understanding is correct - OBD11's solution to the confusing data is analogous to chopping-off an arm because a finger on its hand has been scratched!!! Utterly unbelievable!!
Wouldn't a better solution have been to tag each of the long-code change records with the name of the APP that caused the change? The cause of the confusion was that these entries just appeared in the history file without any explanation.
Sorry - I'm not blaming you for the idiocy - I just can't believe that something that we fought hard to get has been so foolishly abandoned for such an idiotic reason!!
Don
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 19, 2021 20:17:03 GMT
dv52 (Australia) Don we will have to agree to disagree, whilst I understand you view, personally I think this solution is fine as it keeps the non pro user profile clean and simple.
|
|
|
Post by dv52 (Australia) on Apr 19, 2021 20:33:56 GMT
@testeronline : It's OK that we don't agree - yes, the solution does keep the non pro user profile clean and simple- but the price for this cleanliness is paid by pro users who are unable to unwind Apps
Again, no offense intended - but IMO, this is a classic case of dealing with a problem by addressing its effect, rather than its cause.
But hey - ain't a problem that will impact me because I don't use APPs - ironically because they make changes that are (now, again) never disclosed.
Don
|
|
pt16a4
Junior Member
Posts: 80
|
Post by pt16a4 on Apr 24, 2021 11:10:47 GMT
Not being able to follow what the apps change, is why I personally do not use them.
Would be very tricky to undo what you are unaware has been changed.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 24, 2021 12:52:26 GMT
Agreed but this just highlights how important it is to make regular backups so that you can see whats changed and sometimes much easier to unpick than going through the history.
|
|
pt16a4
Junior Member
Posts: 80
|
Post by pt16a4 on Apr 24, 2021 15:02:47 GMT
On the topic of backups, am I correct in that this is essentially the total history file for each individual/all control units?
That is what I have used as a "backup".
In the individual units,any time I make a change, I email mself a fresh history file.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 24, 2021 16:13:19 GMT
OBD11 Has two features.
History, this is the file that shows you all the individual changes you have made one by one which is great but if like me you make lots of changes and revert stuff or change it again then the history file can get full very quickly.
It is possible to Archive (android only) some of these items (your choice which ones) and this works like GMAIL Archive the data is not lost just removed from your main view and some values by default are not ticked as this would fill up the history view (again data not lost just needs to be selected) but that only applies to Android.
Further there are two small bug's in that if you clear a fault then the clear is not posted to history file and if you run a scan and cancel it then IOS Shows what was completed but Android does not
However a great and very helpful information source.
The BACKUP procoess can be run against a single control unit or all control units. The difference is this does not show you the changes it is just a historical record of how the car was setup at that point in time.
Personally I use this a lot because I can then do a compare in Excel and confirm the changes to settings that I have made, the big advantage of this backup is that if you use an app then the history file will just show you have used app xxx and change setting to y but comparing the History extracts you can compare and see what Adaptations and Long coding changes have been made.
Hope that makes sense.
I would stress there is no right or wrong way but the advantage of OBD11 is the full history is kept online anyway so you can always go check out historical changes using either method.
UPDATE - Just noticed that they have posted a blog item on this subject
|
|
|
Post by dv52 (Australia) on Apr 24, 2021 20:40:45 GMT
Agreed but this just highlights how important it is to make regular backups so that you can see whats changed and sometimes much easier to unpick than going through the history. @testeronline : Hi. Please forgive my interruption of your discussion with OP - but I felt it important to make a few observations regarding what is being said about backups in the context of the recent decision to delete the confusing "App change records".
First, I need to say that the value of backups is unquestionable; they are and always have been (and they will remain) an invaluable reference source of information which can be used for multiple purposes. So, I fully support the practice of creating backups - especially for vehicles in their virgin state.
BUT, the unalienable truth about the value of backups does not make them a reasonable substitute for the new inability of OBD11 users to access actual App change records - and any attempt to argue this is drawing a very long bow indeed - IMHO, of course!
As I understand, the rationale for deleting the previous "App change records" was that it was confusing to non PRO users. If this is correct, how is it any less confusing to expect these same users to search through the "before" and "after" back-up files to identify changes made by Apps?
As we all know, the record count of code-able items in a backup is highly dependent on the options that have been fitted to the car - but on modern vehicles, it is not unusual for just the adaptation channel count to be around 5,000 and this excludes the large number of software switches that reside in each module's long-code.
Now, of course there are many database management tools that can be used to undertake comparisons between database records and this might the suggested answer to my question above.
BUT, as we have discussed before, OBD11's obsession to make backups look pretty (i.e. to turn what is effectively a relational database into a readable document) means that the task of parsing the information into a flat file (which is a requirement for using these tools) is not a trivial task!! Now, I'm aware that you have this expertise - but again, it is drawing a very long bow to expect the same confused non-PRO users to be so skilled. And I suggest PRO users have exactly the same problem
So, what this means in practice is that for everyone but the most determined non-PRO and PRO user, the daunting task of searching through the huge amount of data in the back-up file (by manually reading each record and laboriously comparing before after values) simply won't happen - even if the user has created the before and after backups!!
So, in summary - I invite that OBD11 consider that while backups are a most wonderful facility, this truth does not make backups a reasonable substitute for having access to actual records of the changes made by Apps (IMHO, of course)
Don
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 24, 2021 22:16:36 GMT
Don dv52 (Australia) My view and I suspect that this is OBD11 View as well is that this application has 3 distinct user profiles. Non Pro User - There are many tools out there for this class of user they just want a simple process to make changes Mid range Pro User - This is people like me who like to tinker and understand what is going on. Semi Pro - Guys like yourself who use OBD11 and other tools and have a deeper understanding of the car setup. Non pro users don't have the ability to make changes other than using the apps so even if history was fully displayed they could not make any changes to fix any problems. If stuff don't work they should be talking with support to fix it in my view With regards to many Pro users we see on this site a lot of Pro users are very clear they do not use the apps, I use them for simple stuff like reset service intervals as a) they are meaningless on my car as my service schedule is very different to VAG and i just want warning gone, b) I already tested the code changes and happy I know what has changed. Further I do like to share the coding the apps use and pass that info back to other forums I am on. We are never going to agree on the history showing the data but I would stress that there are a number of tools (excel being one but there are other free ones) that do not require the flat file structure. I personally copy and past the output file directly into a column and have a simple if statement that tells me if a change has been made. I agree for many this is to much hassle but it is not hard. And as a result of the above process that i have used I have been able to identify very quickly why the backups on my control unit 09 are showing bad numbers and missing data for Adaptions and live data although its still not fixed yet. I think we have turned off most users on the forum now so I will close with have a good weekend
|
|
|
Post by Art1990 on Feb 12, 2024 11:43:19 GMT
Will bring the old topic up.
I have VW Scirocco 2009, which has also got some strange behavior with history data. The log appeared in the history when I did not have any subscription (PRO nor Ultimate), only credits and I tried the credits apps after few hours.
The log: Long coding Control unit: 42 Driver Door Old value: 3232048 New value: 0020535 Mileage: 124750 km Date: 2024-01-09 16:09
App Name: Cornering Lights Old value: Original New value: via Fog lights Mileage: 124790 km Date: 2024-01-09 22:52
Did some search for the old logs of VCDS, I have found one dated 02.2018. The coding is the same as “new value” of OBD11. Address 42: Door Elect, Driver Coding: 0020535
Any ideas why OBD11 found some random code and replaced it with the actual one?
|
|
|
Post by whataboutthis on Feb 12, 2024 12:32:50 GMT
I can only guess that the previous change (if there was one) was in the cars history so it showed this.
I would drop support a line via the in app help function or live chat (they can take up to 24 hours to reply)
|
|
|
Post by Art1990 on Feb 12, 2024 17:45:38 GMT
I can only guess that the previous change (if there was one) was in the cars history so it showed this. I would drop support a line via the in app help function or live chat (they can take up to 24 hours to reply) There was one, but it was long time ago (2016) and the car had something like 22000 km on the odometer. I doubt he had any interest in modifying the car, when for 7 years he managed to drive 22k.
|
|
|
Post by whataboutthis on Feb 12, 2024 21:58:46 GMT
As I say only a guess but drop support a line, they might be able to throw some light on it.
|
|