|
|
Post by dv52 (Australia) on Jul 14, 2020 7:52:45 GMT
I'm intrigued by what appears to be a new data field in the iOS software; it seems that adaptation channels now have a trailing number in brackets - see screen-shot below. I'm not sure if this new number field only appeared in the latest iOS SW version, but it doesn't appear in the latest Android release
The odd thing about this number seems to be that it only applies to the "Parent" adaptation channel descriptor. If I click on any of the entries, none of the 19 x "Child" adaptation channels that are associated with any of the Leuchte-sets in the screen shot above appear to have a trailing number. I'm not completely sure, but it looks like the number is decimal (not hexadecimal)
At first I thought that the new OBD11 number might be the same as the "Tag numbers" that VCDS reports for adaptation channels, but a quick comparison soon disproved this hypothesis.
So - please, can someone explain these numbers; what are they, why do they only appear for "Parent" channels, where do they come from and how are they helpful for us users?
Thank-you in advance
Don
|
|
|
|
Post by newty on Jul 14, 2020 9:34:38 GMT
That is the Adaptions Memory Address. VCP shows this, too. I do not know about VCDS.
Right now, OBD11 represents them in Hex Format, while VCP shows them in decimal. Maybe you can convert them too and check if this matches the VCDS Tag.
I have already submitted a request to convert them to decimal in the next releases so people using multiple tools are able to compare!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 14, 2020 10:25:55 GMT
Gents it would be nice if new features such as this were commented in the Release notes, firstly for testing purposes but also so we all know what extra features are availiable.
Secondly (and yes I have said this several times before) my expectation is you would keep IOS and Android functionally the same, whilst I fully appreciate while you are building all the stuff Android has it will be a while to catch up but if you add new stuff to IOS it should also be in Android at the same time. Just a personal thought / moan.
|
|
|
|
Post by dv52 (Australia) on Jul 14, 2020 23:04:39 GMT
That is the Adaptions Memory Address. VCP shows this, too. I do not know about VCDS. Right now, OBD11 represents them in Hex Format, while VCP shows them in decimal. Maybe you can convert them too and check if this matches the VCDS Tag. I have already submitted a request to convert them to decimal in the next releases so people using multiple tools are able to compare! ^^ ^ thanks. OK - it make sense that the number is in hex if it's a memory location (why do you want this in decimal?) - but if the facility is to be useful, isn't the missing part of the memory address going to be a problem?
To explain further - as I have said, if I select any of the memory locations in my picture, I will access 19 x "Child" channels that are associated with a particular Leuchte-set,
For example. -Leuchte 0 BLK VL B36 which is @ address hex0550 has the following Child channels: Lichtfunktion A 0
Dimmwert AB 0
Lichtansteuerung HD AB 0
Lichtfunktion C 0
Lichtfunktion D 0
Dimmwert CD 0
Dimming Direction CD 0
Lichtfunktion E 0
Lichtfunktion F 0
Dimmwert EF 0
Dimming Direction EF 0
Lichtfunktion G 0
Lichtfunktion H 0
Dimmwert GH 0
Dimming Direction GH 0
I assume that each of these child channels live at subordinate memory locations in hex0550xx. The two "xx" digits mean that there are 32 x available memory locations at address hex0550 - but there are only 19 x child channels. To make the new memory location useful, why not provide the complete address by also declaring the subordinate addresses of the child channels?
Don't get me wrong, I reckon that the new facility of reporting the memory location is a good thing and it ties-in quite neatly with the new nextgen EEPROM facility - except that the EEPROM function only appears in the Android SW and the new memory location is only found in the iOS SW version (odd??)
Don
|
|
|
|
Post by Thirsty on Jul 15, 2020 7:32:07 GMT
This information is only available for users with specific app permissions like us moderators.
It is needed to create one click apps, which we currently can't but sooner or later there will be a possibility for us.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 15, 2020 8:02:55 GMT
Thanks for the update and I know you are just passing on the information for which we a very grateful but it is odd (as one click apps are supposed to be rolled out on both Android and IOS at the same time) that this feature is only on IOS.
|
|
|
|
Post by Thirsty on Jul 15, 2020 9:52:04 GMT
As far as i know this will be included in android aswell but this process will take some time.
|
|
