how, exactly, do you turn off Tele Aid via MB Star DAS ?
#26
Junior Member
Join Date: Jul 2024
Location: SoCal
Posts: 64
Likes: 0
Received 3 Likes
on
3 Posts
90 VW Corrado g60, 07 New Beetle Vert triple white & 09 Escalade ESV Plat LOL!
Whoa, thanks for that info Dean. Delving into purchasing a W203 with the possibility it may have the old analog teleaid installed. Good info to have.
There’s so much heartache on MBZ offering it and then pulling the plug. VW had OnStar offer their services to them, sold them the equipment and then pulled the rug out. “Whoops, we’re going to digital equipment, too bad you’re analog.”
There’s so much heartache on MBZ offering it and then pulling the plug. VW had OnStar offer their services to them, sold them the equipment and then pulled the rug out. “Whoops, we’re going to digital equipment, too bad you’re analog.”
#27
Junior Member
Whoa, thanks for that info Dean. Delving into purchasing a W203 with the possibility it may have the old analog teleaid installed. Good info to have.
There’s so much heartache on MBZ offering it and then pulling the plug. VW had OnStar offer their services to them, sold them the equipment and then pulled the rug out. “Whoops, we’re going to digital equipment, too bad you’re analog.”
There’s so much heartache on MBZ offering it and then pulling the plug. VW had OnStar offer their services to them, sold them the equipment and then pulled the rug out. “Whoops, we’re going to digital equipment, too bad you’re analog.”
#28
Junior Member
Sos telaid
#29
Junior Member
I will try to answer this best I can. Please understand, when doing these mods involves using sections of Xentry/DAS that are technically not even *supposed* to be accessed by dealerships. That said, if documentation was already scarce on using Xentry/DAS - you can imagine how scarce using the factory-only features will be.
Disclaimer aside, I will try to help you best I can.
The first and most important thing to remember when dealing w/ Xentry/DAS and (especially) the Developer Data adaptations is this: the are more often than not DIFFERENT between Chassis. So some intuition must be applied - and some rist must be assumed.
I have disabled the SOS light on a few vehicles (mainly ML), but years ago I do recal doing this on a car - cannot remember which specifically. In all except one instance (that I can recall), the option to disable the SOS feature was in the airbag module.
The best thing you can do is get google translate app installed w/ the "camera" feature.. Go into the Airbag module, enter Developer Data and carefully crawl through all options there with the camera app. Some intuition unfortunately must be applied here.
In one instance, it seems that I recall having to also (or exclusively) go into the Instrument Cluster and disable the SOS there.
Sometimes, all the *current* values that are enabled for each given option that can be changed will already be highlighted, other times (various chassis), the select/dropdowns will just have a "-". In this case, you may or may not be able to tell which value is currently programmed -vs- which one you want to try.
While I have personally never had to do it (knock on wood), if you have the offline mode stuff installed, you can always backup your SCN data - store it and just play with the settings at-will. Worse case scenario, things get screwed up and you just re-write the SCN coding back to the module (should overwrite any custom adaptations you screwed up).
I can not stress enough that applying some intuition really applies here. I think most of us who have tweaked and changed factory settings have made blind leaps at one point or another to experiment and see how things work.
On the W163 chassis vehicles, the only 4 modules involved with SOS are: Cluster, Airbag, Radio and SOS module itself. In the case of the W163, the SOS and Airbag module inter-communicate directly. From there, it seems the Airbag module "boadcasts" the status to the radio and cluster. So in my example previous posted, simply turning off that broadcast stops the ABS module from reporting the SOS data (referred to in Dev Data as "Crash Data" - even if no accident happened, it is all part of "Crash Data").
Depending on your chassis, you may ALSO have some option called "Crash Data, digital in" or "SOS, digital data", etc. Those additional options may also need to be disabled. I am just offering sugestions here to help aid you.
If you are less of a rist taker, you may try reaching out to the guys on MHH (just google search, I will leave it at that). There are often a lot of deep-dive hackers on that forum. More often than not, they will be non-english-as-first-language, so understand that. But it is a source for detailed answers to these more involved Dev Data questions IMO.
All that aside, here is the best help I can offer here:
1) Ensure the Teleaid module itself is disconnected (important!). If it is still connected, it will continue to "report" to Airbag or any other applicable module
2) Go into each of the following: Airbag, Cluster. For each, dive into the Dev Data / Explicit Coding section. Look around with Google Translate camera app and look for anything that references Crash Data, Teleaid, SOS, etc.
3) If you find something that seems obvious, look at the available options. Feel free to take pics of these if you like and post them here before making changes - I will try to give my personal feedback as to if it is worth trying or not.
Regarding the code K12.. not sure? Is it asking you for a secret key? If so, that is something you will need to search for outside this public thread :-). DAS does require a secret key for some chassis/modules when entering Dev Data section.
Again, ensure you have completely disconnected that TeleAid module (not just the fiber!) and search all the Dev Data options. Take some pics and post back here if you want - I will try to help best I can.
If anyone else has more expecience with this chassis/application, please feel free to chime in
-Dean
Disclaimer aside, I will try to help you best I can.
The first and most important thing to remember when dealing w/ Xentry/DAS and (especially) the Developer Data adaptations is this: the are more often than not DIFFERENT between Chassis. So some intuition must be applied - and some rist must be assumed.
I have disabled the SOS light on a few vehicles (mainly ML), but years ago I do recal doing this on a car - cannot remember which specifically. In all except one instance (that I can recall), the option to disable the SOS feature was in the airbag module.
The best thing you can do is get google translate app installed w/ the "camera" feature.. Go into the Airbag module, enter Developer Data and carefully crawl through all options there with the camera app. Some intuition unfortunately must be applied here.
In one instance, it seems that I recall having to also (or exclusively) go into the Instrument Cluster and disable the SOS there.
Sometimes, all the *current* values that are enabled for each given option that can be changed will already be highlighted, other times (various chassis), the select/dropdowns will just have a "-". In this case, you may or may not be able to tell which value is currently programmed -vs- which one you want to try.
While I have personally never had to do it (knock on wood), if you have the offline mode stuff installed, you can always backup your SCN data - store it and just play with the settings at-will. Worse case scenario, things get screwed up and you just re-write the SCN coding back to the module (should overwrite any custom adaptations you screwed up).
I can not stress enough that applying some intuition really applies here. I think most of us who have tweaked and changed factory settings have made blind leaps at one point or another to experiment and see how things work.
On the W163 chassis vehicles, the only 4 modules involved with SOS are: Cluster, Airbag, Radio and SOS module itself. In the case of the W163, the SOS and Airbag module inter-communicate directly. From there, it seems the Airbag module "boadcasts" the status to the radio and cluster. So in my example previous posted, simply turning off that broadcast stops the ABS module from reporting the SOS data (referred to in Dev Data as "Crash Data" - even if no accident happened, it is all part of "Crash Data").
Depending on your chassis, you may ALSO have some option called "Crash Data, digital in" or "SOS, digital data", etc. Those additional options may also need to be disabled. I am just offering sugestions here to help aid you.
If you are less of a rist taker, you may try reaching out to the guys on MHH (just google search, I will leave it at that). There are often a lot of deep-dive hackers on that forum. More often than not, they will be non-english-as-first-language, so understand that. But it is a source for detailed answers to these more involved Dev Data questions IMO.
All that aside, here is the best help I can offer here:
1) Ensure the Teleaid module itself is disconnected (important!). If it is still connected, it will continue to "report" to Airbag or any other applicable module
2) Go into each of the following: Airbag, Cluster. For each, dive into the Dev Data / Explicit Coding section. Look around with Google Translate camera app and look for anything that references Crash Data, Teleaid, SOS, etc.
3) If you find something that seems obvious, look at the available options. Feel free to take pics of these if you like and post them here before making changes - I will try to give my personal feedback as to if it is worth trying or not.
Regarding the code K12.. not sure? Is it asking you for a secret key? If so, that is something you will need to search for outside this public thread :-). DAS does require a secret key for some chassis/modules when entering Dev Data section.
Again, ensure you have completely disconnected that TeleAid module (not just the fiber!) and search all the Dev Data options. Take some pics and post back here if you want - I will try to help best I can.
If anyone else has more expecience with this chassis/application, please feel free to chime in
-Dean