Vdash with Scanmatk3
-
I tested with Scanmatic 2 and it works perfectly on P3 platform.
So scanmatic 3 wil lwork well there. I am not sure if newer stuff works on scanmatik 3 but if anything will work it it likely that. Scanmatik 2 worked perfectly with VIDA2014D as it was designed for so I might be a question to ask the developer or test yourself.Scanmatik SM3 Pass-Thru adapter is a successor of SM2Pro adapter with CAN-FD and DoIP protocols. It offers widest support for SAE J2534-1/2 and TMC RP1210 standard features.
-
I have a faulty - 2016 XC90 D5 - D4204T11 engine 2.0L four-cylinder twin-turbo diesel - Diagnostics Cable
I've made a cable that does both CAN and DOIP and written some software to interrogate the Volvo XC90 MK II D5 AWD, it is in early test but looking promising, and it runs on Ubuntu Linux.
My motivation for doing this is that my XC 90 that I owned from new has had some issues and is in Turtle / Tortoise mode with the only error P0100 Pending (MAF Malfunction)
I've recently fixed all leaks around oil pipes near turbo and had Exhaust Manifold gasket replaced because bolts came loose. It had a new Inlet Manifold under warranty at 97K Miles, and now at 140K has had Walnut Blasting, EGR Valve and Cooler replaced, Pressure Sensor Replaced.
My diagnostics is showing an imbalance of Block temp to thermostat temperature on cooling system which I think is main issue now, 1st I will bleed and top up system
If anyone knows what the DID codes represent below that would be very helpful.
- 0x40E2
- 0x4311
- 0x42ED
- 0x42EE
- 0x411D
- 0x438B
Parts required for the cable -
510 Ohm Resistor
Female RJ45 Connector.
ODB2-Cable
CAN AdapterUse a small straight through RJ45 cable 0.5m to your laptop.
Option 1 - ODB 2 to - Female RJ45
Pin 3 (RX+) - 1 - on the Female RJ45
Pin 11 (RX-) - 2
Pin 12 (TX+) 3
Pin 13 (TX-) - 6
The Resistor goes between pin 8 Activation and 16 is 12v this is needed to bring the IP live.For the CAN - DSD TECH SH-C31G Isolated USB to CAN Adapter with FD Support Based on Canable 2.0 Pro
GND is Yellow and Orange ODB2 pins 4+5
CAN-H is Green - ODB2 - pin 6
CAN-L is Red/White - ODB2 - pin 14IMPORTANT - Use a Multi-meter to check wires against pins, suppliers colours may change.
I was hoping I could program keys and maps with this set up but it seems Volvo locked it down and I need other things.
Will the cable I made work with VDASH for my 2016 SPA?
I've written basic software for Ubuntu Linux to diagnose the car, I record history of all feeds from cable every 1s then analyse.
- 0x40E2
-
@Ctrl-alt-delete if your cable 100% supports the DoIP, or the J2534-2 protocol (including compatible Windows J2534-2 drivers), you should be able use it with vdash or orbit. But as it sounds more like you have made a CAN bus sniffer, I doubt it.
To program keys, you will need several security pins to get write access to several ecus. Not 100% sure what is needed on the SPA plattform, but IMMO and KVM pin are definitely needed, and can't be cracked with Vdash. Maybe you also need the CEM pin, which has a 50/50 chance to be crackable with Vdash with a really good J2534 adapter and lots of patience.
There are even more pins in your car, and all if them are unique for your car. The only way to extract most of them is on the bench or by using man-in-the-middle techniqes while the car is being programmed with a legit version of VIDA. On SPAs/CMAs from 2022 onwards it became even worse because of a hardware firewall behind the OBD socket. -
@T5-T6-Schnappi yes, it is a sniffer and a DOIP reader. My main aim when I started was to read info and faults from the car, I have lots of data now and an ongoing issue that I am hoping replacing the MAF will solve. Volvo original is over £400 GBP, I tried one cheaper off eBay and the values were higher than the faulty one.
I am consistently getting P0100 fault pending and turtle
-
I will try and figure out other things. What makes the J2534-2 protocol different from what I made?
I have another ECU I got from a scrap car to play with on bench going to see what I can do.
-
@Ctrl-alt-delete before you start to fire the parts canon, you should know that 90%of all MAF codes are follow up errors of other problems. Old/weak batteries, dirty MAP sensor, dirty throttle body, carbon build up in the EGR/EGR cooler. There is also a technical journal about a design flaw in the EGR cooler of older VEA diesels, that triggers P010000 and requires replacing EGR and cooler with redesigned parts.
The data you have collected is also not really useful, unless you find the signal specifications of the ECM, to check if everything is in the desired range. This data can be found in the online version of VIDA which is not accessible for private user, unless you live in the US. VIDA also has detailed explanations what triggers code XYZ and an associated fault trace with things to check, to find the cause for the code. This kind of vital information can hardly be found in the internet.
You also should know that Volvos don't like aftermarket sensors. Replacing the MAF with an aftermarket part might not solve your issue, if it's really the MAF.
Your first step should be to get a good Volvo capable diag tool and scan the car with that. Not only the ECM, all ecus. A dead battery for example will trigger several communication codes in several ecus. You should also take a look at the freeze frame data, that is stored together with the code and consists of a set of data/parameters that happened in the moment when the code was stored, which could be helpfull to identify some problems.The J2534 is a complicated SAE standard that describes/specifies all kinds of communication protocols between all ecus in your car and a computer through a VCI. Dataformats, bitrates, commands, timings, signaling specifications and what not for programming, diagnostics, activations and so on. Substandards are J2534-1 for ECMs, J2534-2 for all other ecus. Without J2534 compatible firmware/drivers/software, your cable won't be usable for the things you want to do.
-
@T5-T6-Schnappi thanks, here is the history leading to this, In October at around 135K I had the haldex service, oil change and gearbox oil changed, the car had a squeak that I thought was a belt squeaking. I took it in had timing and belts done. The squeak remained. The guy at the time said he could blank the EGR and have the ECU map it out. I had a LR Disco 2 and this same procedure was done there so I agreed. Car ran OK for a short spell then codes started appearing of which the same tech managed to remove but the performance was not correct.
I had them remove the blank and at the same time I had the squeak sorted, this turned out to be Manifold Gasket and loose bolts. At the same time all oil seals were replaced at back of engine. Car ran well for a short time and then same performance issues, so I had the stock Map put back on ECU from the back up.
Since then the turtle. I took to a different garage and they put a scope into the Inlet and carbon was bad, so we replaced the EGR Valve and Cooler and did a Walnut Blast. Still the tortoise and P0100.
I tried a MAF from Ebay, same issue, It then got a new MAF from Volvo same issue and the logging I am doing says the EBAY MAF and the New MAF are very much the same.
The Scanner used was Autel and this only registers the P0100 fault, I will check with the garage again to see if any thing else appears.
The only aftermarket sensor is the MAP, thats a Bosch one, I replaced because original was coked up, but no fault reading for that one.
I am capturing the RAW HEX, I will run capture after clearing all adaptions and see what I can get as the fault appears.
-
This is the latest run after clearing the P0100 and the adaptions on Throttle and EGR:
the exact fault sequence with raw hex:
17:56:48 — EGR still working (54.5%, raw 8B), MAP at 255 (FF), speed 53 mph
17:56:54 — EGR drops to 2.35% (raw 06), EGR Error -3.91% (raw 7B), MAP drops to 110
17:56:59 — EGR goes to 0.0% (raw 00) — this is the kill moment. RPM 2700, MAP 221, MAF 109.6 g/s, pedal 49%
17:57:05 — EGR stays 0.0%, Engine Load drops to 0.0% (raw 00) — tortoise mode active, speed 49 mph but decelerating, pedal
releasedThe exact trigger sequence at raw level:
-
-
The problem seems to start when to the EGR is closing. As your MAF is reporting different values, this part is working and not the cause of your problem. Your data is lacking the pressure from the MAP sensor(s). There is one in the intake manifold that you should a look at as described here https://d5t5.com/article/vea-d5-clogged-boost-pressure-sensor and there is maybe a second one in the intercooler, that you should also clean. Then you should do a smoke test of whole intake and charge pipe system. There seems to be leak, or it's just the MAPs are dirty, also take a closer look at the EGR pipes. These are known to crack from time to time.
-
It's also possible that your EGR isn't working properly or stuck open when the ECM demands it to be fully closed.
-
Thanks, We just replaced the EGR Valve and Cooler, cleaned all pipes, it has been smoke tested and the MAP sensor is a new Bosch Sensor in the intake manifold. I will give that a clean and perhaps get a Volvo one.
Smoke test was done the only leak and very slight was oil filler cap, I can replace that also, I have replace the rubber seal, but while better tiny bit of air passing by it.
-
@Ctrl-alt-delete what's the mileage of the car? Maybe the PCV is leaking or clogged.
-
140K that was done also its inside the plastic Valve / injector cover that was also replaced, this was done with all other work. I also checked receipts for parts the oil filler cap was replaced.
I am going to have to book into Volvo, it pains me to do so but I don't think I have another option.
