Conflict during reading of measurement block data from the MSG

Hallo Leute!

Ich bin gerade dabei, mich an der VAGCOM Software einzulernen. Versuche, Daten auszulesen klappen bestens. Nur ein Steuergerät linkt mich. Das Motorsteuergerät meines VW T4 mit dem ACV Motor macht mir Probleme. Je Sitzung, läßt sich das Steuergerät nur einmal über den "MOTOR" Button öffnen. Es erscheinen alle Daten des Steuergerätes, also VW Nummer, Codierung etc. Wenn ich dann versuche, die Messwertblöcke auszulesen, bricht die Verbindung ab. Jeglicher weiterer Versuch in das Steuergerät zu kommen scheitern anfangs mit der Meldung wie "Anderung der Baudrate auf 10" mnachmal liegt der Wert bei 11 oder auch bei 0, dann ist die Verbindung so wie so weg. Dann geht nix mehr. Turn the ignition on and off, then you can re-enter, but then the error code "17978 (P1570) E" appears."Engine control Module Blocked)". I almost got angry when I saw the message. The error can be cleared, and the car functions exactly as before, so there are no apparent changes, thank goodness. Other measurement blocks, such as Climatronic and central locking, can be read without any problems. Then I tried logging into the engine control unit. I logged in with 12233, opened the measurement blocks, and then I tried to start the car, but it wouldn't start. Okay, everything is disconnected now, and the car runs normally again. I really want to learn how to use VAGCOM , what am I doing wrong? Can anyone help me, please?

Greetings, Mc_Givertechnik (Peter)

Hi Peter,

Sometimes, adapter problems only become noticeable in a single component, and that with the strangest error messages .

Which adapter are you using?

Hello Ulf!

Well, if I knew exactly. There's no manufacturer listed on it. I bought it online. It's a black casing, essentially a VAG connector, with an RS232 interface at the end. From this RS232 interface, I connect to my laptop (Acer Aspire P4, 1.7 GHz, 256 MB RAM, Win2K) using a USB adapter cable that works perfectly with all other serial devices (modem, phone, etc.).
"Other control units are working fine. Should I take a look inside to see what's installed there, or if there's a manufacturer's name printed on the circuit board?"

Basic question: Do I need to log in to the control unit before I can read out measurement data blocks?

Greetings,

Peter (Mc_Givertechnik)

Hello,

No login code is required to read measurement data blocks.
If you're not sufficiently knowledgeable, I believe it's best to avoid experimenting haphazardly with diagnostic systems, login codes, or basic settings. Instead, it's better to first thoroughly explore the forums and articles available.

Hello Michael!

Das habe ich auch getan, habe mich durchs Forum geackert, habe mich bei meinen VW Leuten schlau gemacht etc. So ganz planlos bin ich nun auch wieder nicht. Meine Reparaturerfolge scheiterten in letzter Zeit immer nur am Auslesen der Daten. Wenn ich da mehr wüßte, täte ich mir wesentlich leichter. Ich habe weder vor, herum zu experimentieren, noch irgendwelche grundlegenden Verstellungen vor zu nehmen. Aber wenn ich nicht irgendwann damit beginne, wie sollte ich es sonst erlernen? Ihr habt es ja auch nicht von Kind auf gewußt, oder? Wie die Dinge funktionieren ist mir weitgehend klar, jedoch bin ich eher der ehrgeizige Typ und möchte immer alles Wissen (was natürlich nie geht). Ich hoffe nun auf die Hilfe der hier anwesenden Profis. DaSure, here's the translation:

"Thank you in advance."

But regarding the question of why I cannot access my engine control unit (ECU), no one has been able to explain it to me yet .

Greetings,

Peter.

Hello Peter,

Quote:

"I then tried logging into the engine control unit with a login code. I used '12233' to log in, then opened the data blocks, and then I tried to start the car, but it wouldn't start. Okay, I disconnected everything, and the car is running normally again."

"I'm sorry, but that sounds like a lot of experimentation to me."
The meaning and implications of error code/knowledge base entry 12233 are clearly explained in the database. It should be evident from that information that "adaptation" is something different than simply reading measurement values.

Hello Michi II!

Of course, I read the article about the Login 12233, and even printed it out. I've also created a binder that contains not only the instructions for VAG COM, but also most of the tips and tricks from the knowledge base. I always carry this binder with me.

"Ulf suggested it might be due to the adapter. I'll check the adapter to see if it has an optocoupler or not; that might explain some things."

I am grateful for any help.

Peter.

Mc_Givertechnik wrote:

It's a black housing, essentially a VAG connector, at the end of which is an RS232 interface. From this RS232 interface, I use a USB adapter cable, which works perfectly with all other serial devices (modem, mobile phone, etc.), to connect to my notebook (Acer Aspire P4 1.7 GHz, 256 MB RAM, Win2K). Andere Steuergeräte funktionieren ja einwandfrei.

Oh no, another unknown device in the hardware chain.

We've already had reports here that one USB-to-COM adapter works with VAGCOM, while another doesn't... -> Search function.

I would start by getting or borrowing a computer with a COM port and trying it out with that.

Hello Ulf!

Thank you, I'll give it a try.

Thank you.

Hello Michi II!

For your information, I am a trained general mechanic (with experience in turning, milling, welding, and the production of special parts and prototype components for Styer Daimler Puch AG - All-Wheel Drive technology, as well as being involved in the development of the first viscous couplings for the Golf Syncro, etc.). Later, I became a foreman specializing in mechanical engineering and industrial technology, and now I work as an IT systems administrator in an insurance company. That's my professional background. In my free time, I have so far restored three vehicles to roadworthy condition, of course, with the highest quality (a VW T4 2.4D, a Renault Espace J63, and most recently a Ford Galaxy 1.9 TDI that is still driven by a colleague today).
I hope this demonstrates my technical understanding of automobiles and that you will take me seriously. Otherwise, I repair vehicles for all my acquaintances and friends, with a preference for VW and Audi.

Greetings,

Peter (Mc_Givertechnik)

Mc_Givertechnik wrote:

Ich hoffe nun, dir damit mein technisches Verständis bezüglich KFZ dar gelegt zu haben um vielleicht doch ernst genommen zu werden.

Hi Peter,

Traditionally, automotive mechanics and similar professions are considered "hands-on" jobs. Being skilled in these areas doesn't necessarily mean that one is proficient in using digital diagnostic systems.
The forum is full of such experiences, even with so-called "VAG experts."

Perhaps Michael interpreted some things differently than what you intended.

War ja nicht böse gemeint , ich will ja damit nur andeuten, lernen zu wollen und bitte euch darum um Hilfe.
I would never dare to claim that I am knowledgeable about diagnoses, but I want to learn .

Having worked in the IT industry for 10 years, moving towards diagnostic systems is a natural progression, especially because without diagnostics, very little else can be done. Frankly, I'm no longer interested in things like bent fenders.

However, when it comes to circuits, I'm completely clueless. Unlike Ulf, who seems to be an expert in this area, I only know a few of the components, and their function is mostly unknown to me.

I've managed to get hold of an older laptop (an Olivetti P120 with 16MB of RAM and Windows 98SE). I hope it will work.

I still hope for your help and send you greetings from Graz.

Peter.

Mc_Givertechnik wrote:

War ja nicht böse gemeint , ich will ja damit nur andeuten, lernen zu wollen und bitte euch darum um Hilfe. I would never dare to claim that I am knowledgeable about diagnoses, but I want to learn

.

Hi Peter,

Okay.
Here in this forum, we've already encountered quite a few people with poor manners and, to put it mildly, limited knowledge.
They hardly contribute anything positive and can be quite annoying at times.
Therefore, one can react quite negatively to such supposed beginnings...

Quote:

. . . kein Profi, wie es Ulf auf dem Gebiet zu sein scheint.

Hehe, my bluff seems to still be working... I'm also not a professional, but I do these things purely as a hobby .

Okay!

"But what am I supposed to do with my adapter now if it stops working again? What version of VAG COM are you using? Maybe the problem is related to the software version. The version on mine is Ver 1.0.1, which doesn't seem to match the versions mentioned in your posts. Is that a problem?"

Greetings,

Peter.

Mc_Givertechnik wrote:

Aber was mach ich jetzt mit meinem Adapter, wenn es wieder nicht geht?

Hi Peter,

I'm not sure about that either...
Unfortunately, even quite bad adapters are recognized by VAGCOM, which can cause problems in the actual communication process .

Do you have a two-channel oscilloscope available? If so, I could email you some test software to measure the adapter's signal behavior and timing characteristics.

Quote:

What version of VAG COM are you using? It might be related to that. My version is labeled "Ver 1.0.1," which doesn't seem to match the versions I've read about in your posts, possibly indicating an error.

Hmm... which version are you referring to, and when was it released?

Oscilloscope? Me? Noooo, I don't have one, unfortunately.

Can I buy a working adapter from any of you, at a reasonable price, of course ?

Greetings,

Peter.

Mc_Givertechnik wrote:

Kann ich bei irgendwem von euch einen funktionierenden Adabter kaufen, günstig versteht sich ?

Hi Peter,

Don't you think it's premature to rule out the USB-to-serial adapter as a potential cause before it has been thoroughly investigated?

Does the VAGCOM adapter also not work with a standard COM port?