Measured Value Search Function? Genius!

Just came across another ODIS feature that's making life easier for me, so thought I'd share it...

I've just had a Q5 in with a customer concern regarding the engine power.
After launching GFF a large number of event memories were stored in the vehicle, a lot of which that were OB5 gearbox related.

Anyway, having looked at the customer statement in the DISS report, (which you now do in ODIS ;-) ), it turns out the vehicle is 'surging', rather than losing engine power, which I have experienced before.

With this in I decided to check the measured values of the DSG, as this is a typical symptom of the over-heat / protection mode, and there is usually a measured value that displays how many times the gearbox has over-heated.

This seemed like a good idea until I opened the list of values in self diagnosis...
The downside is, the control unit was a UDS version, meaning all the typical measured values that I'm used to (value 64 for example) have changed!
Anyway, after spending what seemed like an eternity of scrolling, I noticed a text box at the bottom of the screen called 'Filter'.
I had no idea what this was, but decided to push my luck and type into the text box, and sure enough - it turns out that this is a search function within measured values... you beauty!
I typed in 'temperature', and there it was! Shame I hadn't noticed this 5 minutes ago :-(

Back to the problem - sure enough, the measured value had logged that the gearbox had reached the maximum temperature value quite a few times - now to find out why...

Seeing as I had a new search toy to play with, I typed in the next logical (or maybe suspicious) value title... 'launch control'.
And what do you know - the fact that this vehicle has used launch control 64 times may have something to do with it!!! ;-)

Search functions in measured values... pure genius!!!

DISS coding

So, in my previous Blog, I mentioned how I've now started using the new version of the customer complaint test plans, which helped me fix a tricky air-con problem first time. Well, this is how it works...

When you start GFF with ODIS, it takes you to straight to a 'DISS' page.
This displays any DISS reports created by the Service Adviser when they listened to the Customer's complaint. It also shows you any relevant TPIs that relate to the complaint!

In this instance there was no DISS report created, but this page can still be really handy, and this is why; after speaking to the Service Adviser, and then contacting the customer again :-/ we got their statement of what was not happening. Then I could code the complaint in on the DISS page of ODIS (just like you would on a DISS report in ElsaPro). The great thing about this is that as you have coded the complaint, it then offers you relevant TPIs (just like ElsaPro would). No going to a separate PC, all the TPIs were there listed in ODIS!

Anyway, I can honestly say in experience this doesn't normally get done properly, as it can all prove too hard. Not now.

Back to the problem - it turns out that there is a relevant TPI, so I now used a new feature to 'extend the test plan', which basically means turning the TPI into a test plan (or selecting a test plan relevant to the TPI). Either way, I had gone from working on a car with no fault codes - to now following a test plan based on the Customer's concern.

 

The test plan checked out the performance of the air-con, and helped me locate the problem of a blocked condenser, that I don't honestly think I would have found as quickly on my own.

The best thing to come out of all this, is that my Service Manager and Adviser have both agreed that we should be doing this DISS creation every time, the worst thing is that we ruined such a good result by having to ring the customer back which made us look a bit unprofessional :-(

Test plans

Been using the new software for Odis for a few days now, and have seen quite a few improvements, mainly in the Test plan area.

Previously there have been 3 ways of choosing test plans:
1. Via fault codes
2. By selecting your own
3. By selecting via a customer complaint or TPI

In my experience I mainly picked them via fault codes, and if not, then by selecting my own, but as for the 3rd option - there was never really much to choose from, and the TPI list was always incomplete and out of date.

Not now though! Since using ODIS I assumed this would be the same story, and stuck to selecting fault code generated test plans or ones manually selected, but recently I have come across the new version of customer complaint / TPI generated test plans, and it works fantastic!

 More importantly it's just really helped me fix someone's car first time!

I'll find out all the details and explain how it works in the next Blog

Cheers

More benefits

Just tried the latest ODIS software, and am happy to confirm that it works on Skodas and SEATs now too. Am happy to say this - as after using this for a few weeks now, I am absolutely sold on it.

Forgetting all the sales talk, I now have first hand experience of ODIS being A LOT QUICKER and WAY MORE EASIER to use than VAS PC! So the more vehicles this works on - the better.

And to think that not that long ago, I was worried about having to learn it all over again, and (if being completely honest), would have preferred sticking to the old software.

So, it turns out I'm not a dinosaur after all (but it's looking like VAS PC is)!

Back soon...

New software!

Just been on my holidays, and am returning to new software. Apparently I should see quite a few updates, so will test it out thoroughly tomorrow and will post my findings!