|
Post by legend868 on May 29, 2020 23:05:10 GMT
I just recently purchased the pro version to this device but when I get to long coding its all in German, I have my settings set to English but it doesn't seem to help, any advice or guidance would be extremely appreciated.
|
|
|
Post by dv52 (Australia) on May 30, 2020 1:57:53 GMT
^^legend: Are you sure that you mean "long coding" and not "adaptation channels"? In any event, it doesn't matter if you set the language to English in the OBD11 software because this only applies to native OBD11 screens.
The way that the descriptors about the module values are returned (like long code and adaptation channels) is determined by what's actually in the module firmware; it's not determined by the Language setting. Clearly, because VW cars are designed in Germany, there are lots of German-language descriptors in the modules! But Mr Google can help you translate this stuff
Don
|
|
fwj
Junior Member
Posts: 99
|
Post by fwj on May 30, 2020 6:46:44 GMT
I just recently purchased the pro version to this device but when I get to long coding its all in German, I have my settings set to English but it doesn't seem to help, any advice or guidance would be extremely appreciated. There are two possible language settings in OBDeleven, for the application and the database. Did you set both settings to English?
|
|
|
Post by overtaker on May 12, 2023 13:04:00 GMT
I can only find the one setting. where do I find the setting for the database?
|
|
|
Post by whataboutthis on May 12, 2023 13:17:58 GMT
This however applies to the Android version and can be found in Settings and you have Application and Database language.
BUT BUT BUT Remember this changes the languages of the non VW Bits so the actual field names inside the control unit will still be in the original language (EG German or English).
This is kept like this as you will see all coding sharing is done using the same field names.
However in Long Coding the descriptions by and large are User derived so changing the database Language means you get to see other folks labels that you would not see in your language.
Hope that makes sense.
And Further point like the rest of us you will soon be fluent in German
IOS in my view is very poor all round but only supports one language but again field names will stay in whatever they were coded by VAG group.
|
|
|
Post by grazuncle on May 13, 2023 20:11:17 GMT
I too was a little surprised at this when trying to search, in English, fruitlessly.. LOL
however I read a comment on a review of a Chinese made battery tester a German citizen purchased.. the gist was that he liked the item very much but them complained about the supplied instructions being 'only' in English. then in bracket he put (is the lawful?)
I chuckled to myself.. most, if not all, Germans I have spoken to have had an excellent grasp of English - spoken or written - whereas my command of German is pitiful and slow (not schnell)
|
|
duppy
New Member
Posts: 5
|
Post by duppy on Jan 21, 2024 20:22:42 GMT
Hello Don, I too have been struggling to use obdeleven because German language menus keep popping up. I was surprised that you suggested that the the menu text was encoded in the actual modules. Surely if this were the case then all menus would be in German? I think it more likely that the text of menu options is held on obdeleven's database, and what we have is an incomplete internationalisation implementation. It seem a shame that such an excellent tool should be let down by poor language support. Kind regards, Duppy
|
|
|
Post by dv52 (Australia) on Jan 21, 2024 21:39:24 GMT
Surely if this were the case then all menus would be in German?
Duppy: I'm in NO way associated with the deities on the OBD11 mother-ship, so I share your frustration with the long-code descriptors.
I was a longtime participant on the Ross-Tech forum - but I am no longer because I was censored by Uwe Ross for not supporting his ultra-right wing views on US gun culture - we were discussing what should be done about the senseless carnage of innocent American school children given the intransigent stance of many gun-toting US citizens to their second amendment rights. Anyway,I decided that my value-set was diametrically opposed to the way that Uwe ran his so-called public forum.
So, from happier times on the Ross-Tech forum, I had understood that the third-party diagnostic device industry was able to purchase a kind-of "wholesale" database that provided the descriptors for VAG's long-code software switches. As I say, this is my understanding - I have NO direct evidence for this contention! There is evidence for my contention - if you look at the descriptors on other diagnostic devices (for example, the VCDS "YELLOW" long-code helper screens and VCP), you will find that there is a curious equivalence of words amongst competing manufacturers!!
That said, some diagnostic device manufacturers do indeed create their own long-code descriptors - for example, the VCDS "GREY" long-code helper screens). However, I suspect that creating and maintaining these customized, in-house databases is a non-trivial exercise (particularly given the number of new modules produced)
The more cost-effective approach that VOLTAS (and many other diagnostic device manufacturers) appears to have adopted is to make a distinction between VAG information and OBD11 specific information. The latter, is subject to the language settings within the OBD11 software (as discussed in previous responses). The former is the stuff contained within the actual modules - this data is presented to OBD11 users in its raw form-alas!!
Don
|
|
|
Post by whataboutthis on Jan 21, 2024 23:09:09 GMT
I would add just a small extra bit of information.
On Android device you have the ability to set the app and database language.
The Long coding descriptions are created as Don said in two places there are the manufacturers provided ones and there are the user defined ones.
So if you have the App in English but Database set to German all the Long Coding descriptions will be show in German but then so will the Live Data, Adaptations etc.
In long coding specifically you have the ability to look at a Long Coding description and then using a drop down list see if its shown in any other languages.
Again as Don said the Adaption data is the same across the range so I assume this is taken from the actual control unit (but happy to be wrong) however you will also note that some of these items are in English (thats down to VAG Group).
The IOS App however does not support the two language feature so the only way you can see user defined descriptions you have to change the app language.
Edit if I have it wrong just let me know.
|
|
duppy
New Member
Posts: 5
|
Post by duppy on Jan 22, 2024 10:25:09 GMT
Many thanks for the replies and the Airplane reference (Ah, still a classic).
As I understand it CANbus is a binary communication system whereby the the only data exchanged is defined by binary (address,value) tuples, and not by symbolic label strings. The relationship between the (address,value) numbers and the symbolic descriptors is the symbol table for the system. This is compile time database that I believe VAG have had to publish to avoid infringing competition laws. It's interesting that much of the menu texts are strings of German words connected by the underscore character: this is just how a programmer defines his symbols.
There may be a couple of ways of implementing long coding menus: either at compile time or at run time. At compile time the menu texts are read from the database and hard coded as values in the program, whereas at runtime the App would consult the mother-ship's database to provide the menus. I have no idea how its done in obdeleven but in either case the database needs translating from a programmer's symbol table into a range of languages. I fear that this has not happened as it would not be priority in bringing the product to market.
So I'm wondering what I might have to do to get the obdeleven company to finish-off the job properly? Thanks for taking an interest, Duppy
|
|
|
Post by whataboutthis on Jan 22, 2024 13:19:57 GMT
Long coding descriptions on UDS Control units comes from two places.
1/ The part manufacturer
2/ User Community
I think the part manufacturer will show in the language you have selected (so it changes according to what you ask to see) and also you will see a lot of underscores between words.
The Bit descriptions are maintained by user community (eg you and me) and it will be in the language that you use but you do see in english for example Polish descriptions as the person who created it did not change or understand the language process. There are also some downright stupid descriptions (people just playing)
If you want OBD11 to make changes then you need to do one or all of the following
1/ Contact Support - via in app help function, email (support@obdeleven.com)
3/ in the app you can select the 3 button menu option (top right) and use the report error feature.
|
|
|
Post by grazuncle on Jan 22, 2024 15:14:13 GMT
I find it all ironic.. English is he most spoken and translated language.. full stop. Even airline plots have to learn the international language.
Also ironic was a comment on a well known Chinese purchasing site.. a German buyer lambasted (that IS a word) the seller in his feedback for only including Chinese and English instructions.
Then to add insult to injury then said 'is this even legal? (meaning not to include his language!) No offense the any Germanic person.. you can get the same inane feedback by Brits often.. LOL
|
|
duppy
New Member
Posts: 5
|
Post by duppy on Jan 23, 2024 14:39:03 GMT
Well, I've dropped support@obdeleven.com a line and asked when the menus are to be internationalised. We'll see what response that gets. Duppy
|
|
|
Post by dv52 (Australia) on Jan 23, 2024 20:41:23 GMT
.............................................................................................................................................................................................................
|
|
|
Post by dv52 (Australia) on Jan 23, 2024 21:08:21 GMT
grazuncle : hmm......... I'm trying to understand the rationale for the argument that these long-code descriptors should be anglicized! Of course I have a personal preference for your and duppy positions because I am an English speaker - but putting that aside, what is the basis that VOLTAS should use if the company adopts a proposal to change the language in their long-code screens?
If I'm reading your words correctly (my apology if not) - I understand that your rationale is that English is the most spoken language. I'm definitely NOT skilled at this topic - but a brief look at the Ethnologue statistics suggests that there is a close race between English and Chinese as the most spoken languages (it varies across websites - but the numbers for the 2 x languages appear to be close).
However, VOLTAS is a commercial enterprise with a globally accepted and unsurprisingly unremarkable single-driver: a rate of return on investment for the shareholder(s)! This means that for the deities on the OBD11 mother-ship, a decision to change the language of the long-code descriptors (if made at all) needs to add to this business imperative.
I'm not sure of the ethic breakdown of global sales for OBD11 devices - but It's not at all clear to me that using the principle of "most spoken language" is necessarily compatible with the shareholder's objectives!!
Don
|
|
|
Post by whataboutthis on Jan 23, 2024 22:51:20 GMT
|
|
duppy
New Member
Posts: 5
|
Post by duppy on Jan 24, 2024 14:39:35 GMT
Well I wrote to support the following:-
To whom it may concern, I was unable to configure my Golf MK7 lighting via OBDeleven. All the menus and options were in German, irrespective of the language settings. Reading the online forums I see the lack of internationalisation on your product is frustrating for many other users. In these days of computer translation it seems beyond belief that this problem continues. Could you please tell me if and when internationalisation of OBDeleven will be completed? Regards
And got this reply:-
thank you for your message. The car you are using is made in German. All the information in the adaptations you are looking at regarding the control unit is also provided in German, and that information is coming straight from your vehicle's control unit, not our device or application. All the people in the world that are doing any coding on the VAG cars, need to learn those Leuchte channels, this is just how it is with any diagnostic tool you will pick.
-- So there's the answer: its not happening so get used to it.
Two things seem silly about all this, firstly does CANbus really communicate by identifiers and not binary code, and if so why do we have byte and bit addressing? Secondly, there seems to be a lack of will to want to improve the product, and we all know what happens if you don't keep pace with consumer expectations.
So, there it is, Duppy
|
|
|
Post by whataboutthis on Jan 24, 2024 15:17:09 GMT
No idea about how CANbus commuicates but they are somwhat correct about the German in as much as all the main (VCP, VCDS, OBD11 Etc) use the same descriptions so the Adaptation labels are used by the whole community and we can therefore share coding from one device to another. If OB11 Went to English (or any other Lanuage) then you would not be able to use coding from other tools (which we use a lot)
With regards to Long coding as I have stated before these are created by the user community and they decide the language its stored under so nothing OBD11 can do about that.
I would also agree that you get used to thinking and talking in German in regards to the coding of your car.
Where I disagree with support is not all the Adaptation labels are in German some of them are in English so VAG Code in multiple languages.
|
|
|
Post by newty on Jan 24, 2024 18:01:05 GMT
The Data VAG provides is German, English or both. I do not know about their usage policies, maybe any translation is not allowed.
Even when it is allowed, it is a hard task to translate, maintain and verify this massive database in several languages. Let alone the terms a German engineer translated very bad.
I myself am a native speaker and having some general engineering background and even then some labels need imagination and deep dives into VAGs very own language. They were never ment to be read by someone not familiar with the development and integration process.
Some of my favorites: PSAD - PanoramaSchiebeAufstelldach (Panoramic sunroof with opening function) SPN - SchlüsselPositionsNachbildung (Key Position Reproduction - a feature inside kessy which mimics the turning of a physical key through ACC, IGN and Starter) LDS - LichtDrehSchalter (Light switch activated by turning - do not mix it up with the Blinklichtschalter - the switch for activating the turning lights)
Coding and adaptions of course do not work with any speaking labels, but just throwing and reading strings from adresses (And have nothing to do with CAN datagrams at that level)
|
|