T6 allowed me to complete "All-wheel drive/VTG oil change" successfully where I couldn't w/ VAS clone.
I needed to install the driver through PIWIS, installing it externally from an exe. file I down loaded from their website did not work (it installed, but PIWIS did not recognize the driver). Hope this helps the next guy/gal. I would not even waste my time w/VAS, just go straight to T6. T6 is much faster too!

 

So I recently purchased an autel off Amazon, it apparently was previously used and already registered so it is getting sent back, but before I do I so not see how to code any of the stuff I can do with the x431 ? It's like it's missing a menu option, anyone that is using the autel care to point me in the right direction.

It's almost like the model doesn't have the ability to code even though it's bidirectional the model is MX900

Maybe someone can provide a screenshot of their menu for comparison. Example, I enter into instrument cluster and it has a special function that just lets me manipulate about 5 items and read / clear dtcs or get lice data that's it

 

So I recently purchased an autel off Amazon, it apparently was previously used and already registered so it is getting sent back, but before I do I so not see how to code any of the stuff I can do with the x431 ? It's like it's missing a menu option, anyone that is using the autel care to point me in the right direction.

It's almost like the model doesn't have the ability to code even though it's bidirectional the model is MX900

Maybe someone can provide a screenshot of their menu for comparison. Example, I enter into instrument cluster and it has a special function that just lets me manipulate about 5 items and read / clear dtcs or get lice data that's it

I think that Autel is just for diagnostics and maintenance on the vehicle. Coding is done with Launch or PIWS.

The Autel is useful but not for coding.

Bidirectional ability just means you can activate solenoids and receive signals if they opened or closed.

 

So I recently purchased an autel off Amazon, it apparently was previously used and already registered so it is getting sent back, but before I do I so not see how to code any of the stuff I can do with the x431 ? It's like it's missing a menu option, anyone that is using the autel care to point me in the right direction.

It's almost like the model doesn't have the ability to code even though it's bidirectional the model is MX900

Maybe someone can provide a screenshot of their menu for comparison. Example, I enter into instrument cluster and it has a special function that just lets me manipulate about 5 items and read / clear dtcs or get lice data that's it

I think that Autel is just for diagnostics and maintenance on the vehicle. Coding is done with Launch or PIWS.

The Autel is useful but not for coding.

Bidirectional ability just means you can activate solenoids and receive signals if they opened or closed.

You can do as much coding with Autel as you can do with X431.

1. In main screen, Select Control Unit

2. Then select the control unit you want to code (for this example I’m selecting Instrument Cluster):

3. Select Coding

4. Select Coding without Rules

5. Is going to ask you to connect to the Internet (this is the difference between X431 and Autel). Autel will need to backup all the data in the cloud (kind of a ValLog) which you can retrieve later if you have issues. This is a one time kind of deal and is going to take some time to do this, but then after the second time you can skip the backup and go rather quickly to coding.

6. Select the option you want to code (for this example I selected Onboard computer menu configuration 2:

7. Code. This is the feature I like the most from Autel in comparison to X431, and is that it displays a full list with drop down menus with the options and you can change more than one at a time.

Also, one thing I found is that Autel is more true to PIWIS naming conventions than X431 is.

BTW, I have PIWIS, Autel and X431, so I’m talking from experience here. Lately, my go to tool for coding is Autel. Although I ocassionally use X431. I only use PIWIS for complex maintenance and calibration procedures. Almost never for coding, unless I want to verify something.

 

Thank you @Santirx for some reason I do not have all those options. I only have manual scan or auto scan. My Porsche software also only says 1.80 and there are no available updates, I see yours shows 5.46, so my assumption is this is not supported on the MX900.

 

Yeah, saw specs of MX900 and ECU coding is not supported. For the same price of the Autel MX900 you could get the Otofix D1 which is manufactured by Autel but for DIY’ers. Have same Autel software with same capabilities and you can do ECU Coding.

Don’t get Autel, get Otofix.

 

Some great deals for prime day on autels and otofix , most are 20% off theres and 808BT that has 2 years for 650 but it won't do can-fd or doip , fine if you're just doing the Porsche but I have too many other cars I have to work on.

 

Keep in mind Otofix is always going to be cheaper than the Autel equivalent. And they are the same thing. Otofix is powered and manufactured by Autel for the DIY’er rather than shops (which is what Autel is aimed to).

 

For anyone considering either option, I called autel.com/us they do not support otofix as this is strictly a chinese market unit, they actually told me they would just say "we don't support otofix and would hangup on you" also they will not warranty the autels purchased off Amazon, those have to go through the chinese channel for warranty and they said "good luck with that"


They did state that for support you can use the US channel for autel units purchased off Amazon so long as they're registered through pro.autel.com and have an active subscription.


To be honest the whole conversation was pretty off-putting between autel US customer support and technical support as a potential customer but I guess this is what you can expect these days, the lowest bar possible to meet.

I may return both and just update my out of support x431 through the Russian channels but I'll still play with both anyway.

 

First observations of the mp900-bt, extremely slow, painfully slow to where I forget which ecu module I selected by the time it finally gets into the module. I'm not sure why this is, maybe it'll speed up more after I go into modules. I did the initial backup for codings and it takes anywhere from 3-5 minutes to get into any component. Doesn't matter if it's AC or Instrument cluster etc.

Once you're in the translations and the way they allow you to see everything on one page is far superior to the launch ala @Santirx pointed out in #7 above.

I have the same problems with similar codings on the autel vs launch so that's a bummer. I was hoping the autel would work where the launch wasnt and I could say aha! It's worth the extra money for two separate tools.

I did try to do the coding piece before registering the tool but you cannot do that which worries me that at the end of expiration they will force me to buy their total package support in order to do customization codings.

The main reason honestly was that their online support shows "oil fill level" as a function. It is not there for a 2022 macan so this, and the otofix, will more than likely be returned as I'm not gathering the benefit over the autel vs launch and I'm already 1K into the launch which is way faster to code with between the BMWs or Porsches. I'm going to email support on this oil fill.


I'm going to keep farting around with the autel and move into the BMW but with how slow this thing is for their $1k tool compared to the 10" launch idk it's a pretty lousy tablet, you'd think they would get one with some horsepower.

I need to see if I can find oil levels and play around with the diagnostics next but it's got a + and - against the launch. I think they kind of even each other out. I did move back to the launch just to see if it was that slow, and while it's faster it's more difficult to navigate each menu in comparison to the autel.

 

So a few questions, I have an Autel/Otofix programming device and a 2020 Macan GTS.

* I want to be able to close the hatch with my key-fob but it keeps giving me access denied. From what I can tell I need to enable the acoustic alert for that function first, but I can't seem to find that option on the Autel, there is one setting for sound that has a bunch of bit flags in the rear hatch/rear electronics (I forget which) section, but they don't have meaningful names so I'm unsure if that is it and am afraid to mess with it.

* I noticed in Headlamps (Central) there is an option for City Distribution that is disabled, I turned it on, it seemed that when I was in the neighborhoods the lights pointed down more and were wider, but I can't 100% confirm that's the case can anyone else?

* In the Headlamps (Central) there is also an option to raise the lights during heavy breaking, I'm guessing the goal is to keep them level, has anyone tried that setting? How was it?

* In PCM there is an option for Joker - Left and Joker - Right, I'm guessing that would let me assign the diamond button to left or right on the PCM, potentially letting me skip songs in CarPlay with the button? Has anyone tried to see if that works?

 

The trunk with keyfob we have all wanted. I opened a ticket with launch and they never got back to me on it. I would suggest opening a ticket through the scantool help for the key fob opening / close not writing as well. You'll have to attach the diag logs with the ticket.

This was one of the first things I tried when the autel came in and it didn't work. So I've opened a ticket if more people do it the sooner it'll get fixed.

 

...Regarding keyfob and trunk, did you try to code the hidden keyfob button #4 for that purpose. I remember vaguely there was some option in the key menues when I coded the long press on key #3 (1200ms delay) for trunk opening.
My keyfob supports 4 buttons electrically incl. switch, but only 3 are mechanically accessible. With the right plastic and rubber parts that 4th button may be activated properly...

 

I'll take a look at that, but even with that I think the issue is you have to enable the Acoustic Alert which I can't find.

 

It may not be there with the autel. I've noticed, when I tested against a bmw with the autel that a ton was missing from the "hidden features" menu in comparison to the launch x431. Launch was more aligned with the esys for bmw where it appears the autel is more aligned with piwis for Porsche as @Santirx stated.

I'll check later today for the acoustic setting in autel. It should either be in rear end electronics or rear lid. If it's not I'll try re-enabling the acoustic with the x431 and code the close with fob or interior button again on the left door. I know that with the launch no combination worked.

 

Great comparison between the two. I have not gone that deep into a comparison between the 2, but I find myself hopping between one and the other. I do like Autel/Otofix for fault scanning, is faster, but that could be a function of the unit itself as my X431 is 2.5 years old. Autel/Otofix does a data backup before initial use for coding and that takes a long long time… Then it gives you the option. But I’m not sure how would that be helpful or how to recover it honestly… I haven’t had the need to try that. But coding seems easier with the Autel/Otofix.

For example, yesterday I changed the way I adjusted the height of my air suspension Macan. Started with a recalibration using PIWIS to return my Macan to stock height, and then went to coding and lowered the Macan through correction values in PASM/Level coding. Then, I went out with my X431 to do some additional corrections, and I wanted to test it too, and found that I needed to go to 4 different field options, and write each wheel one by one.

While with the Autel/Otofix, it was very similar to PIWIS in which you input all 4 wheel height correction values in a single screen and them write all of them at the same time.

I’m sure it will work either way, but it was odd to try to do this with X431.

In any case, thanks @justdostuff for taking the time to compare these systems.

 

The Otifix was easy, but it sounds like the X431 gives you access to more?

The backup/restore seems to work well btw, when I was messing with my headlight coding I accidentally turned off the cornering function because there were multiple conflicting fields for it. I restored just that module and then re-coded it to what I wanted. That was a life saver actually.

I was originally going to get the Launch, but it doesn't support coding my wife's GLE450, and hers has multi-beam LED lights that aren't enabled since it wasn't yet legal in the US, so that's a project for another weekend.

Maybe I'll end up getting a Launch as well, but the $$$

 

Alright, so I see that on mine but all of them are already set as active except automatic run and vit.

 

I played with a combo of on offs and could not get closing from interior button one touch to code. Just says write failed and I can't upload a data log for some reason to autel.

 

I played with a combo of on offs and could not get closing from interior button one touch to code. Just says write failed and I can't upload a data log for some reason

I was able to grab a data log and just submitted it, so hopefully something comes of it. Now if anyone has ideas on my other questions.

 

I have never had a problem getting software support from autel in China for the unit I purchased from Amazon. When I asked about how to get a replacement charging cable, however, not so much. Therefore, I performed a llttle surgery so that I can use off the shelf USB-C cables.

 

The Otofix I purchased has USB-C so I'm in luck there!

 

Btw., I am currently fighting the notorius low battery charge state in, or better said after driving in normal mode, leaving the battery voltage close to the point, where the manufacturers say, it needs to be charged to avoid loss of lifetime.
In sport/sport+ modes the battery seems always kept properly charged and no gimmick micro-hybrid operation takes place.
It would be interesting to turn off that micro-hybrid operation also in normal driving mode.

- Do you remember having seen any BMS settings somewhere, is that hosted in the rear electronics, the DMSE or elsewhere???

 

Btw., I am currently fighting the notorius low battery charge state in, or better said after driving in normal mode, leaving the battery voltage close to the point, where the manufacturers say, it needs to be charged to avoid loss of lifetime.
In sport/sport+ modes the battery seems always kept properly charged and no gimmick micro-hybrid operation takes place.
It would be interesting to turn off that micro-hybrid operation also in normal driving mode.

- Do you remember having seen any BMS settings somewhere, is that hosted in the rear electronics, the DMS or elsewhere???

I don't, but next time I'm in there I'll look. FWIW I have a 2020 and I noticed in the last 6 months my stater cranks just a little longer and when I had my Otofix plugged in the voltage dropped more rapidly than I would have expected. For me it might just be time for a new battery.

 

...My battery is about a year old, tested OK (by the Porsche shop and myself) and shows the same behaviour in normal drive mode.
Critical charge state reached (12.4-12.5V) after opening doors or hatch a few times or short engine operation (idle voltage measured some hours afterwards)...

 

On Launch, the Amazon listing makes it look like you can't get updates if you don't buy a Launch Tech USA version since it talks about using a VPN to connect to China - anyone have insights?

 

...not in Germany...btw. new Launch Porsche Version:

some ADAS upgrade mentioned for the Macan...

 

...not in Germany...btw. new Launch Porsche Version:

What does the online coding give you that coding without rules doesn't?

 

Regarding battery charge status:
Realized that the so-called recuperative braking function causes the battery management system to maintain a battery charge state not at full, but at some 60-70% (or below) to have enough headroom left to charge the battery through the generator while braking. This happens only in normal driving mode, but not in Sport/Sport+ modes.
If you open and close the car a few times after engine-off a lower threshold idle voltage is easily reached (<12.4-12.5V; idle voltage measured after several hours without touching the Macan), which was identified by Varta and Banner as a cause of premature aging of AGM batteries.

In the Gateway module (where the battery sensor is connected) I found 2 settings (see below) to stop the Macan from recuperative braking in normal mode, which has the side effect of a constant battery voltage at 14.4-14.5V, which improves the charge level significantly and gives more reserve for long term parking and battery aging.

Both REK values set from Activated to Not Activated

...did a 20Km test drive, no drop in charging voltage occured, therefore also no recuperative braking.

 

came across this the other day when looking up battery related things..

has anyone else done this?
I have PIWIS.

 

Did someone know PIWIS param for Coding-Exterior lighting-DDL Specification | Disable DRL with Light Switch Off from the google sheet? I want to disable all exterior light when switcher in off position but have no luck yet.
BTW who is maintainer for sheet? I found most of codings from LAUNCH X431 in PIWIS so we could update

 

Did someone know PIWIS param for Coding-Exterior lighting-DDL Specification | Disable DRL with Light Switch Off from the google sheet? I want to disable all exterior light when switcher in off position but have no luck yet.
BTW who is maintainer for sheet? I found most of codings from LAUNCH X431 in PIWIS so we could update

have you tried to request edit access? the original owner of the file might not be around any more. but if he/she isn't around, save the file and modify and put in the new codes. and if possible, throw it back up on the cloud

 

Hello,
I have problem with my Macan GTS MY17 (original US, converted to EU).

After my small test with coding through PIWIS I mess up something and now I have few issues:

• In cluster Macan S logo instead of Macan GTS
• LDW not work
• Entry & Drive not work anymore
• No Boost gauge in cluster
• Bunch of errors like below - last is know issue, but question is it makes problem with Entry&Drive or it's independent. Maybe in history it was coded different way to prevent VTS to mess with codes and now it show up again and make E&D not working.

Before my "work" there was only old error about low voltage. Nothing else.

• Device No 5: Instrument Cluster
  • Porsche Part Number
    Diagnostic SW Number
    000018
    • a000 - Read out warning logger (maintenance/repair)
    • c11005 - Instrument cluster, function restriction
    • 10052 - Instrument cluster, function restriction
• Device No 23: Body Control Module Rear
  • Porsche Part Number
  • 7PP959551GN
  • Diagnostic SW Number
  • 020031
    • 8c2502 - VTS, battery condition weak
• Device No 24: Headlight central
  • Porsche Part Number
  • 7PP941572AB
    Diagnostic SW Number
    304000
    • b500 - Left static cornering light - open line
    • c500 - Right static cornering light - open line

 

What exactly you did? Automatic coding?

 

@Jng ua I try to code PDLS+ according to instruction:

Selected Instruments, Front BCM, Headlights and FrontCamera. I change option, but i not make scan before...

I just "need" my GTS logo back and working Keyless. If it can by done manualy with PIWIS2 in Engineering mode or something - i could Try, I can even make TeamViewer connection to make it with someone with more knowledge and experience than me. Before I done a lot of mods with VAG (add cameras, Lane Assist, reprograming etc), but here coding is much different story than there.