Part 1: MapEV Diag

[prj]

Any chance this software can clear codes or code other Porsches?

Coding I will never do. Adding support for fault decoding on others is possible but the Ethernet gateway is only in the newest models.

I do have the capability from 1999 until today, but needs different interface and then there's a bit more overlap with my commercial software than I'd like.

That said, I don't have too much interest in doing this, because it's EV focused. I'm going to add MEB and Audi e-tron/Q8 e-tron soon as well.

Sponsored

 

[Caraholic]

No problem thanks for all the support on our model

 

[angry4nus]

Hello, seeking some advice. The car (2020 4S) is having an intermittent issue with "all wheel drive and engine control error". These are all yellow errors that clear upon shutting down the car. Took it to the dealership but they could not reproduce the problem in a road test drive so they returned the car to me. Fast forward a week later I finally got the right cables and adapters to use MAPev which works wonderfully. I used MAPev to scan and found the following faults.

How should I approach the dealership with this information? Can the dealership pinpoint the issue with these numerical DTC numbers? I'm sure they saw it the first time I took the car in. Hope to fix this before ordering a modified ASG. Thanks!

There is also an airbag fault that doesn't go away even after clearing codes with mapev


System name: 74 - Chassis Control
Workshop ID: J775
Software number: 9J1907553R
Software version: 1510
Hardware number: 9J1907553B
Hardware version: H21
ASAM ID: EV_ChassContrContiPO513
ASAM version: 004
FAZIT: TSR-K7418.02.2000000618
VIN: WP0

4 DTC entries:

733399 Display of all wheel drive failure
B19C300 not active
00001000 confirmed
MIL off

733400 Drivetrain control
U190200 Subsequent error due to all wheel drive
00001000 not active
confirmed
MIL off

733451 Function restriction
C10C200 not active
00001000 confirmed
MIL off

733398 Display of fault in all wheel drive
B19BEF0 active
00001000 not active
confirmed
MIL off
------------------------------------------------------------------------
System name: CE - Drive Motor Control Module 2
Workshop ID: J944
Software number: 9J1907124AM
Software version: 0021
Hardware number: 9J1907124L
Hardware version: H04
ASAM ID: EV_PWR2HIAMSPO513
ASAM version: 001
FAZIT: HJH-00101.11.1920010010
VIN: WP0

1 DTC entry:

44284 Internal Control Module Torque Performance
P061A00 not active
00101100 active at least once in current or last driving cycle
confirmed
active at least once since DTC's cleared
MIL off
-------------------------------------------------------------------------
System name: 01 - Engine Control Module 1
Workshop ID: ESCP5
Software number: 9J1909101DH
Software version: 0021
Hardware number: 9J1907522
Hardware version: H02
ASAM ID: EV_VCU00XXX0209J1909101XX
ASAM version: 001
FAZIT: SJ8-FST19.02.2000100182
VIN: WP0

1 DTC entry:

44081 Control module for power electronics 2
U178A00 Message: only coasting possible
00101100 not active
active at least once in current or last driving cycle
confirmed
active at least once since DTC's cleared
MIL off
--------------------------------------------------------------------------
System name: 15 - Airbag
Workshop ID: J234
Software number: 992959655D
Software version: 3303
Hardware number: 992959655C
Hardware version: H46
ASAM ID: EV_AirbaVW31SMEAU65x
ASAM version: 001
FAZIT: YNF-GDL26.01.2015620251
VIN: WP0

1 DTC entry:

12618240 Vehicle Communication Bus G Performance
U008A00 active
00001001 confirmed
MIL off

 

[prj]

PIWIS has guided fault finding, and they have factory support. You pretty much have to bring it back and push them.

Don't clear the codes anymore though, better if all the codes are stored, then take it in. They don't have to reproduce the problem on a drive - they can do guided fault finding because the faults are stored. Not sure why they are messing around.

One thing that can be useful for them (if it is a warranty thing), is take a photo with your phone of the error on the dash when it occurs.

 

[Solid]

FWIW, I had no problem scanning codes and reading the ASG using a Windows 11 on ARM virtual machine running on a macOS host in UTM. I spun up a new VM using UTM, having it download the install ISO using crystal disk, then installed with no windows license, patched windows, downloaded the mapev client, connected another NIC and ran the mapev.

 

[prj]

I did a small update for the tool.

It is now much more tolerant to timeouts or modules not responding than before, the entire scan doesn't get broken anymore if a module doesn't reply or doesn't want to answer with a fault code list.

Still no SoH, but I'll do it soon also.

 

[dooby]

FWIW, I had no problem scanning codes and reading the ASG using a Windows 11 on ARM virtual machine running on a macOS host in UTM. I spun up a new VM using UTM, having it download the install ISO using crystal disk, then installed with no windows license, patched windows, downloaded the mapev client, connected another NIC and ran the mapev.

I'll second this but add that an Apple USB Ethernet Adapter won't work :-( Spent a while chasing down drivers for Windows on Arm but no luck even from Asix, the Taiwanese vendor of the underlying chipset. In the end I had to grab a StarTech USB-C to Ethernet Adapter (C22G-USB-ETHERNET specifically) which lists support for ARM (Snapdragon)

DTCs scanned & cleared ready to monitor for return. Thank you prj for the helpful tool!

 

[prj]

If someone wants to port it to Avalon UI and Mac then that can be done quite easily... Because only the UI really needs to be ported and the deployment. All the logic and other C# code should run just fine on Mac.

I just have so many other things to do that I can't get around to it...

 

[Porsche-Guru]

If someone wants to port it to Avalon UI and Mac then that can be done quite easily... Because only the UI really needs to be ported and the deployment. All the logic and other C# code should run just fine on Mac.

I just have so many other things to do that I can't get around to it...

Are you looking to publish the code maybe on GitHub or someplace? There will likely be someone who will port this to MacOS, iOS, etc….

 

[prj]

Are you looking to publish the code maybe on GitHub or someplace? There will likely be someone who will port this to MacOS, iOS, etc….

No, I do not want to publish it at this time, there is too much proprietary stuff there that has overlap with my commercial stuff.
If I ever stop supporting it, I will make it open source, but for now it will stay closed.

If someone wants to port it to Mac OS then we can work something out though, but I find the likelihood to be quite low.

 

[chun]

Any update on the SoH @prj ?

Finally got my cable from temu... longest delivery time ever.
Quite a few error codes. Just a few stuck after a clear.

OTAFC:

and

Quick google search returns some hydraulic unit as part. So seems to be one of the many hydraulic pumps valves /flaps in the shitshow that is the cooling system of taycan. I suspect this error is just a software glitch resulted from the 3 or 5 revisions Porsche did on the cooling block on taycan thought the years.

Initial shitshow

New replacement since my2022 is some sort of metalic monoblock similar to below, can't find picture:

There is a non-zero chance most cars that went through a heater replacement had this mono block also changed, resulting in some valve sensors remaining useless, hence the error above.

Never went under my car to confirm however; so could also just be the complete opposite, where a manifold is expected in the software, but instead you have the old shitshow.

I'll just leave all the codes gather from now, and see what porsche says.

 

[prj]

I updated the diag tool. The biggest change is that it supports the whole VAG MEB platform now.
Not Taycan related - I know, sorry.

Next will add SoH readout to the BMS.

 

[ze_shark]

Next will add SoH readout to the BMS.

Is that still coming and will it work with J1.2 as well as J1.1 ?
You'd be the first solution to offer a SOH reading for J1.2.

 

[prj]

The interesting thing is that in Porsche measuring data there is no SoH present that I can see.
Seems like a "non-official" DID or it was removed later.

I'll add it when I have time, I was on vacation past 3 weeks and just getting back on track.

 

[ze_shark]

Isn't that a standard reading which forms the basis for assessing the battery against the 80%/70% warranty thresholds ? Would it mean that it is computed by PIWIS instead of read from the BMS ?

Sponsored