Problems during initial setup of kit B1

Hello, I've been searching this forum for hours, but I can't find a solution to my problem. It's about Rainer's DIY kit. I assembled it and then ran the LED test with versions 311.2 (English) and 409.1 (German). Both tests were successful. So, the 3 LEDs light up 5 times quickly, then 10 times slowly, and then 5 times quickly again. However, my 4th LED is constantly lit. The 4th LED also lights up even without the ignition being on and without a connection to the laptop. When I then run the COM test with version 311, the 3 LEDs disappear and reappear when an error message appears with the following text: 'COM Port Status: OK. Interface Status 3. n.a or not found.' With version 409.1, nothing happens to the LEDs. They remain constantly lit. If no test is performed, all 4 diodes are on without blinking. This means that nothing happens during the 409.1 test. Error message: 'Port:O Interface not found or ready.' I'm running the device in K1/K2 mode. I've measured which position the switch must be in. What could be the cause? I have an AUDI A3 8L, manufactured in May 2003.

I have also performed troubleshooting as described in the document. Besides the fact that it was 7V instead of 5V, everything was fine.


Thank you for your help.

CU moby.

[Edit Admin: Topic title changed to be more accurate]

Quote:

Except that it was 7V instead of 5V, everything was okay.

Okay, good night. Think about what a 5V voltage regulator is used for and how much voltage such an IC can handle. My suggestion: The voltage regulator might be installed incorrectly.

Best regards, Rainer.

Okay. Okay, I'll take a look at it today.

CU moby.

Rainer K. wrote:

My tip: The voltage regulator was installed incorrectly.

Or perhaps measure the voltage between the voltage regulator and 12V, instead of between the voltage regulator and ground?

Hello, we seem to have mixed up something with the OBD cable. But it still doesn't work.
'When I plug the OBD cable into the MSTG, all four lights stay on continuously. Then, when I connect the RS232 cable to the laptop and test the COM ports (I checked all 4), the diode for voltage continues to light up, but the other three go out for about 10 seconds. Then, I get the error message 'Interface Status 3: Not Found or Not Ready.' When the PC starts up, all three diodes blink. What's the problem? This happens with all baud rate settings in VAG-COM. I've also followed the instructions carefully, because I'm starting to lose patience and I want to rule out any human errors. Could it be a problem with the switch?' We weren't entirely sure what the problem was, so we tested the switch and found that it should actually be working correctly. But who knows...

Sure, here's the translation:

'CU Thomas' translates to 'See you, Thomas' or 'Bye, Thomas' in English.

hello

Hello, we probably mixed something up with the OBD cable. But it still doesn't work.

Perhaps you damaged the kit by messing with the OBD cable .

greetings

hb2000

Hi,

Please check if the connections/cable colors of your RS232 cable are not reversed, and refer to the pin designations in the schematic diagram.

Best regards, Rainer.

Hello, the problem still persists. I only did the soldering myself, but an electrician told me what to do, and he was present the whole time. He checked everything in the car. This was in a Golf 3 from 1997, not my Audi A3. All the voltages are correct. You can't check it more than 5 times *g*. Could it be the laptop? Will the USB adapter help? It sounds a bit illogical, because the diode test works. However, I still haven't found a clear answer on the correct sequence for the LED test. How many times should each LED light up? I hope you can help me. Can the component be damaged and still have the correct voltage readings?

Sure, here is the translation of the text from German to English:

'Cu moby' is a phrase that is often used in online communities and forums. It is a playful and informal way of saying 'goodbye' or 'see you later.' It is also sometimes used as a way to express affection or friendship.

The phrase 'cu moby' is believed to have originated in the early 2000s, and it is thought to have been popularized by the online gaming community. It is now widely used by people of all ages and backgrounds.

Here are some examples of how the phrase 'cu moby' can be used:

* 'Cu moby, everyone! I'm going to go offline for a while.'
* 'Cu moby, my friend! I'll see you later.'
* 'Cu moby, and have a great day!'

The phrase 'cu moby' is a fun and lighthearted way to say goodbye or see you later. It is a great way to show your friends and family that you care about them.

Hello.

Quote:

When I plug the OBD cable into the MSTG, all four lights illuminate continuously.

That's not okay at all; only the red LED, which indicates the power supply via the OBD connector, should be lit.
Therefore, the problem is likely not related to the laptop or any baud rate settings; the error is clearly within your interface. It's probable that repeatedly swapping wires or components has caused an integrated circuit (IC) to fail. "Why don't you also check those to make sure everything is in the right place? Maybe you'll get lucky and everything will still be intact."
When working on electronics projects (and not just there), precision is extremely important. If you're not sure what you're doing, it's better to buy a pre-made component, as it will not only save you a lot of time, but also a lot of frustration.
I hope you manage to get it working, as it's a really great interface.
I've been using it for a while now without any problems whatsoever; it's absolutely reliable.
Best regards,

Hi, I wanted to buy it back then! But it wasn't available in the shop... I was also surprised... maybe it was unavailable for a few days... But since I have an electrician I trust, I just went with it. Surely he should be able to tell if an IC is defective, right? We've checked the whole thing together at least 10 times, and we haven't been able to find any problems or defects. Unless it's in the cable.


CU moby.

moby wrote:

[...] Will the USB adapter help me? [...] Cu moby

.

Hi Moby,

I also had problems with the kit. The culprit was my USB-to-serial adapter. So, if possible, try it on a desktop PC or an older laptop with a serial port. I solved it using a (expensive) PCMCIA card.

Best regards and good luck!

Hi, so the laptop is definitely about 4 years old. It's just one of those cheap things you buy from Lidl, you know. Not from me... I would never buy something like that *g*.

CU moby.

Hi, I finally got the thing working with version 311.2... it was about time. Next time, I should probably pay more attention to the person who's soldering the RS232 cable *laughs*. He probably misread the numbers there and connected the wrong cable. Arghhhh...
Okay, here's the translation:

'But now there's still a problem. I can select and read the MWB without any issues, BUT the other functions aren't working correctly. With the Audi A3 8L and Golf 3, both from 1997, I always get the message 'ECU does not respond.' Sometimes it connects to certain menu items, but only after several attempts, and sometimes it connects immediately. First, it shows 'BAUD 0 Try 1,' then it immediately switches to 'BAUD 1 Try 1,' and then some sub-items become accessible. What should the sample rate be? I've also tried adjusting the baud rate, but it hasn't improved anything. For example, with the Audi, I can access the parking system / 'Arkingsystem' (that's how it's labeled), but not other modules like the sound system or radio. Are all the target values correct in the MWBs?' 'I'm also seeing significant discrepancies with the Golf and the Audi A3. It's showing an idle speed of 700-800 RPM. I'm getting around 910 RPM. With the Golf, the actual value was deviating from the target value by 300 RPM. So, I'm generally wondering if these values can be taken as completely accurate. I think I've read several times here that the target values often differ from the actual values, but that this doesn't necessarily indicate a problem.' Later, I'll try out the 409 error codes to see exactly what kind of errors they trigger.

What does it mean when the test says 'FAST SYNC non compatible'? Otherwise, everything seems to be okay. Status 0.. found and ready.


Why does he always install the English version? I download the multilingual version from the 'dieselschrauber' website, but it doesn't even ask for the language during installation. And both are supposed to be German. Operating systems, one instance of XP Home and one instance of Windows 2000.

cu moby