My experience with a laptop GT1

[katit]

Originally Posted by weasel56

You can see button status in the "diagnostics request" section of "control module functions", and with the real GT1 that has oscilloscope functionality you can actually monitor the bus signals, but the laptop GT1 doesn't have that measuring system as a functional option.

That is what I thought. But oscilloscope is just "seeing" signal, not actual digital messages, correct?

[Weasel]

Correct. There is no way to interpret what signals are being sent, just that something is indeed being sent. (digital signal = binary code to the control modules) But in the diagnostic requests you can usually see what is being done.

[katit]

Originally Posted by weasel56

Correct. There is no way to interpret what signals are being sent, just that something is indeed being sent. (digital signal = binary code to the control modules) But in the diagnostic requests you can usually see what is being done.

Yes, in training materials I've seen what oscilloscope can be used for. Mostly for troubleshooting BUS line condition, shorts, etc.

I think I need to get that GT1 thingy and get out of the dark. Right now CarSoft does good for me showing codes but I think I'm ready for more data. Oscilloscope function is what it is, oscilloscope. If needed I can get real oscilloscope and use it.

[Weasel]

For a good ocilloscope I just use the good 'ol Snap-on vantage, which is all over eBay for less than $500 now. It is a truely good graphing multimeter/ocilloscope. (I've been using mine for years)

[katit]

Originally Posted by weasel56

For a good ocilloscope I just use the good 'ol Snap-on vantage, which is all over eBay for less than $500 now. It is a truely goos graphing multimeter/ocilloscope. (I've been using mine for years)

I do sometime work on other electronics (not car related) so even desktop oscilloscope will do just fine when I need it once in lifetime. I'm not field mechanic, so..

[TwinsPoppa]

Hey weasel ... could you help me interpret these screens?

As we spoke about prior, I had a bunch of faults showing that were not cleared before. So, I did a Quick Delete and re-started Diagnosis.

First question:
After module discovery, it initially indicated "?" on certain modules. What does the "?" mean? See screenshot below:


Second question:
After running Short Test, I received an "X" on DME Motor Electronics. I Quick Deleted it twice but it still comes up. After the Short Test I continued to several screens but it doesn't seem to lead me to anything. It just brings me back to the Symptoms screen. What should I do from here? See progressive screenshots below:

Originally Posted by weasel56

The ?'s next to the modules on the list indicates that there are more than one option of which one is installed, it knows after doing a short test which it has and puts an ! next to it. Normal, nothing to worry about there.

The X next to the DME means there is a fault stored, the fact that it doesn't clear means it is currently present. The fault showing is DME not yet encoded... Did you replace or reprogram the DME recently? Either way, you can encode it with the DIS V43 you have via the programming path, just click on DME and select encode. Programming sets up certain software guidelines for the system to operate by, tells it what to do essentially. (which is why so many problems on modern vehicles are fixed with programming) What encoding does is burn into the DME the VIN# and what other modules/options are installed in the vehicle, known as the vehicle order, personalizes the module to the specific vehicle.

And for the headlight problem, it has ot see the fault a few times before it sets the fault. But sometimes it is a failing part that the computer doesn't see that won't throw a fault, then you need a good understanding of how it works. The beauty of the GT1 is you can still choose a test plan to run even if there are no faults stored for it, and the test plan also gives you a functional description and wiring schematic to look through.

Tried to clear the fault a different way to see if that would work.

(EDIT - Fault returned) SOLUTION 1- Clear through Control Module Functions instead of Quick Delete:

1) De-highlight & re-highlight DME to run individual short test: OK -> 2) DME displays "X" indicating the fault is still there.


3) Select: Control-Module Functions -> 4) DME Module shown with "X"


5) Highlight Module to display Functions -> 6) Select: Clear Fault Memory -OK


7) Fault cleared (no more "X") -> 8) Select: End, Quit, Quick Delete, Terminate.


9) Results after re-running complete ShortTest (no faults).



No joy. So tried to encode the DME as suggested by Weasel.

EDIT (Re-coding unsuccessful) SOLUTION 2 - Re-code DME:

From the Coding/Programming main screen.

1) Select: ZCS/FA Coding -> 2) Displays ZCS/VO version


3) Displays Warning -----> 4) Select: E53 series


5)Select: Recoding ------> 6) Wait


7) Displays List (upper) --> 8) Scroll down, Select: Motronic


9) Confirm selection, YES -> 10) Preparation instructions


11) Start autocodinng, YES -> 12) Auto Coding active


13) Coding complete but no changes!

[Weasel]

Originally Posted by TwinsPoppa

Hey weasel ... could you help me interpret these screens?

As we spoke about prior, I had a bunch of faults showing that were not cleared before. So, I did a Quick Delete and re-started Diagnosis.

First question:
After module discovery, it initially indicated "?" on certain modules. What does the "?" mean? See screenshot below:


Second question:
After running Short Test, I received an "X" on DME Motor Electronics. I Quick Deleted it twice but it still comes up. After the Short Test I continued to several screens but it doesn't seem to lead me to anything. It just brings me back to the Symptoms screen. What should I do from here? See progressive screenshots below:

The ?'s next to the modules on the list indicates that there are more than one option of which one is installed, it knows after doing a short test which it has and puts an ! next to it. Normal, nothing to worry about there.

The X next to the DME means there is a fault stored, the fact that it doesn't clear means it is currently present. The fault showing is DME not yet encoded... Did you replace or reprogram the DME recently? Either way, you can encode it with the DIS V43 you have via the programming path, just click on DME and select encode. Programming sets up certain software guidelines for the system to operate by, tells it what to do essentially. (which is why so many problems on modern vehicles are fixed with programming) What encoding does is burn into the DME the VIN# and what other modules/options are installed in the vehicle, known as the vehicle order, personalizes the module to the specific vehicle.

And for the headlight problem, it has ot see the fault a few times before it sets the fault. But sometimes it is a failing part that the computer doesn't see that won't throw a fault, then you need a good understanding of how it works. The beauty of the GT1 is you can still choose a test plan to run even if there are no faults stored for it, and the test plan also gives you a functional description and wiring schematic to look through.

[TwinsPoppa]

Originally Posted by weasel56

The fault showing is DME not yet encoded... Did you replace or reprogram the DME recently? Either way, you can encode it with the DIS V43 you have via the programming path, just click on DME and select encode. Programming sets up certain software guidelines for the system to operate by, tells it what to do essentially. (which is why so many problems on modern vehicles are fixed with programming) What encoding does is burn into the DME the VIN# and what other modules/options are installed in the vehicle, known as the vehicle order, personalizes the module to the specific vehicle.

Hell no .. at least not me ... maybe the dealer. I know you told me how to see the date when the fault came up I believe. Let me see if I can find a date stamp.

I'm concerned because its the DME ... do you think this fault is something I should take to the dealer or you think I should be okay?

BTW .. not holding you responsible if some crap happens andI blow the X up!

Thanks for the insight.

[Weasel]

It not being encoded wouldn't really affect the running of her, but should be dealt with. And why pay the dealer 1 hour labor to encode it when you are now equipt to do so yourself? I'd give it a try! Just go through the programming button on the main start page instead of clicking diagnosis, click zcs coding (I think that's what they call is, been a while since I used that software) Select encoding, select DME, and follow the instructions. It is pretty easy, and the encoding goes real quick. You should be able to figure it out easily! Then go back into diagnosis and the fault should be not present and able to clear on the first try. And a hint to save time, don't do a full short test, just click on DME and short test that module individually, then clear fault memory through control module functions. Easy as 1-2-pie!

[01 BMW_X5]

Originally Posted by weasel56

The beauty of the GT1 is you can still choose a test plan to run even if there are no faults stored for it, and the test plan also gives you a functional description and wiring schematic to look through.

I've tried this. Because there were no errors, I could not proceed any further.
On the 2nd screen, when I selected a control module and tried to interrogate it, it said something about no errors cannot proceed or something.

How about an example test plan that Jose/Steve can run to show us this feature and post the screens.