Vcds communication error ошибка - Решение и исправление самых разных ошибок на TopOshibok.ru

Добрый день!
Ранее писал о покупке отличного кабеля vcds с алика, однако, вчера подключил машину к компу забыв выключить вайфай, и теперь по мере считывания ошибок раз 100 выпадает «communication error». Ошибки по блоку ДВС почему-то не читает, пишет что-то вроде «у вас нет прав», и так же не дает удалить ошибки. Пробовал несколько раз переустанавливать все строго приложенных инструкций-безрезультатно.
В общем, товарищи прошу помощи разобраться с этой бедой/
Кабель вот такой: OBDII 16 Pin Диагностический кабель 1St ATMEGA162 + 16V8 + FT232RQ Артикул: 1St-Multi-189,
ссылка на алишку: aliexpress.ru/item/400003…042311.0.0.1cfd33edETJoXk

PS/ Ранее до нового года все подключалось, все работало

Пробег: 135 000 км

Источник

Hi
I have installed latest release 15.7.0 but now I have problems communicating with the Controllers.
I made the auto scan which took a very long time (more than 1 hour) and several Controllers that I know have fault codes says «No Faults Found or not supported by controller or a communication error occurred»
When selecting a controller, controller info appear after a few seconds but it retries to connect and after 20 second or so a box wit communication error appears.
I have 3 usb-ports on my computer and it`s the same on all of them.
Any suggestions?

Viggo

Uwe

Benevolent Dictator

I haven’t seen any other reports like that.

What kind of computer? Make, model, CPU, RAM, and version of Windows please.

Computer: Packard bell Dot M.
Possessor: Intel(R) Atom(TM) CPU Z520 @1.33GHz
Ram: 2.0 GB
Windows version: Windows 7 Ultimate N.

I had no problem with the previous version (12.12.3).

Autoscan with communication errors which took very long time to perform :

Code:

Saturday,08,August,2015,18:45:48:09577
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 7 x86(VMWare)
VCDS Version 15.7.0.1
Data version: 20150729
www.Ross-Tech.com


VIN: WVGZZZ7LZ5D048285   License Plate: PX47262
Mileage: 203570km-126492mi   Repair Order: 



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 7L (7L - VW Touareg (2003 > 11/2006))
Scan: 01 02 03 05 06 08 09 11 13 15 16 17 18 19 1C 22 29 32 34 36
          37 39 3C 46 47 55 56 57 64 65 68 69 6C 6D 6E 75 76 77
 
VIN: WVGZZZ7LZ5D048285   Mileage: 203570km-126492miles
-------------------------------------------------------------------------------
Address 01: Engine        Labels: Redir Fail!
   Part No SW: 070 906 016 BL    HW: 028 101 185 9
   Component: R5 2,5L EDC G000AG  A001  
   Revision: 12345678    Serial number: VWZ3Z0D1284054
   Coding: 0011175
   Shop #: WSC 31414 000 00000
   VCID: 5BB593B19900E9E663-FFFF

   Subsystem 1 - Part No: 070 906 016 BL
   Component: R5 2,5L EDC G000AG  A001

2 Faults Found:
18049 - Please check DTC Memory of A/C Controller 
            P1641 - 000 - 
18057 - Powertrain Data Bus 
            P1649 - 000 - Missing Message from ABS Controller - Intermittent
Readiness: N/A

-------------------------------------------------------------------------------
Address 02: Auto Trans        Labels: 09D-927-750.lbl
   Part No: 09D 927 750 BP
   Component: AL 750 6A           0596  
   Coding: 0004136
   Shop #: WSC 69752 124 09147
   VCID: 7DF1FD2927D407D63D-5141
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 03: ABS Brakes        Labels: 7L0-907-379-MK25.lbl
   Part No: 7L0 907 379 G
   Component: ESP ALLRAD MK25     0203  
   Coding: 0006402
   Shop #: WSC 31414 000 00000
   VCID: 3D713D296754C7D67D-5141

No Faults Found
  or DTCs not supported by controller
  or a communication error occurred

-------------------------------------------------------------------------------
Address 05: Acc/Start Auth.        Labels: None
   VCID: 55A18589BF243F9655-5141
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 08: Auto HVAC        Labels: None
   VCID: 55A18589BF243F9655-5141
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 09: Cent. Elect.        Labels: 7Lx-937-049-V1.clb
   Part No: 7L6 937 049 M
   Component:                     3001  
   Coding: 0122093
   Shop #: WSC 31414 000 00000
   VCID: 468352C53282840E2C-5141
   Note: Excessive Comm Errors

No Faults Found
  or DTCs not supported by controller
  or a communication error occurred

-------------------------------------------------------------------------------
Address 15: Airbags        Labels: 
   VCID: 55A18589AC243F9655-515D
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 16: Steering wheel        Labels: 7L6-953-549.lbl
   Part No: 7L6 953 549 D
   Component: Lenksäulenmodul     3301  
   Coding: 0000031
   Shop #: WSC 31414 000 00000
   VCID: 408F44DD10A6AA3E16-515D
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 17: Instruments        Labels: 7L6-920-xxx-7LA.lbl
   Part No: 7L6 920 881 A
   Component: KOMBIINSTRUMENT RB8 3135  
   Coding: 0007111
   Shop #: WSC 00790 218 69060
   VCID: 366322054262148EBC-5141

1 Fault Found:
01316 - ABS Control Module 
            004 - No Signal/Communication - Intermittent

-------------------------------------------------------------------------------
Address 18: Aux. Heat        Labels: 7L6-819-008.lbl
   Part No: 7L6 819 008 G
   Component: Standheizung E1MAC   
   Coding: 0000000
   Shop #: WSC 00000 000 00000
   VCID: 3A7B3635767AF0EE58-5141

   Subsystem 1 - Part No: 7L6 819 008 G
   Component: Standheizung E1MAC 

No Faults Found
  or DTCs not supported by controller
  or a communication error occurred

-------------------------------------------------------------------------------
Address 19: CAN Gateway        Labels: 6N0-909-901-19.lbl
   Part No: 6N0 909 901 
   Component: Gateway K<>CAN      0101  
   Coding: 0000006
   Shop #: WSC 00790 218 69060
   VCID: 70EFD41D60867ABEA6-5141

   Subsystem 1 - Part No: 6N0 909 901 
   Component: Gateway K<>CAN      0101

1 Fault Found:
01316 - ABS Control Module 
            004 - No Signal/Communication - Intermittent

-------------------------------------------------------------------------------
Address 1C: Position Sensing        Labels: 7L6-919-879.lbl
   Part No: 7L6 919 879 A
   Component: JCI PathPoint       2200  
   Shop #: WSC 00000 000 00000
   VCID: 458155C90F848F1625-5141

No Faults Found
  or DTCs not supported by controller
  or a communication error occurred

-------------------------------------------------------------------------------
Address 22: AWD        Labels: None
   Part No: 0AD 927 755 BE
   Component: TRANSFERCASE        0122  
   Shop #: WSC 00000 000 00000
   VCID: 7F0D07212DD815C62F-FFFF


-------------------------------------------------------------------------------
Address 29: Left Light        Labels: 
   VCID: 55A18589AC243F9655-515D
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 34: Level Control        Labels: 7Lx-907-553-34.clb
   Part No: 7L0 907 553 F
   Component: LUFTFDR.-CDC- 3C3P1 3081  
   Coding: 0015521
   Shop #: WSC 31414 000 00000
   VCID: 366322054262148EBC-5141

1 Fault Found:
01316 - ABS Control Module 
            004 - No Signal/Communication - Intermittent

-------------------------------------------------------------------------------
Address 37: Navigation        Labels: 7L6-919-887-CD.lbl
   Part No: 7L6 919 887 K
   Component:      Navigation     0634  
   Coding: 0000002
   Shop #: WSC 31414 000 00000
   VCID: 4E936AE5DAF24C4E94-5141

No Faults Found
  or DTCs not supported by controller
  or a communication error occurred

-------------------------------------------------------------------------------
Address 39: Right Light        Labels: 3D0-909-158.lbl
   Part No: 3D0 909 158 
   Component: EVG GDL+AutoLWR(r)  0001  
   Coding: 0000003
   Shop #: WSC 31414 000 00000
   VCID: 67DDBF415548BD06F7-5123

No fault code found.

-------------------------------------------------------------------------------
Address 46: Central Conv.        Labels: 7L0-959-933.lbl
   Part No: 7L0 959 933 E
   Component: FJ HSG              0201  
   Coding: 0000069
   Shop #: WSC 00790 218 61895
   VCID: 3E733A256A52DCCE64-4B03

   Subsystem 1 - Part No: 7L0 959 701 G
   Component: Tuersteuergeraet FS 0201

   Subsystem 2 - Part No: 7L0 959 702 G
   Component: Tuersteuergeraet BF 0201

   Subsystem 3 - Part No: 7L0 959 703 C
   Component: Tuersteuergeraet HL 0201

   Subsystem 4 - Part No: 7L0 959 704 C
   Component: Tuersteuergeraet HR 0201

No fault code found.

-------------------------------------------------------------------------------
Address 56: Radio        Labels: 7L6-035-186-CD.lbl
   Part No: 7L6 035 186 A
   Component:        Radio        0634  
   Coding: 0007447
   Shop #: WSC 31414 000 00000
   VCID: 31691119AB0C33B6E9-5141

No Faults Found
  or DTCs not supported by controller
  or a communication error occurred

-------------------------------------------------------------------------------
Address 68: Wiper Electr.        Labels: 7L0-955-119-V2.clb
   Part No: 7L0 955 119 K
   Component: Front Wiper         4027  
   Coding: 0000855
   Shop #: WSC 31414 000 376832
   VCID: 3C77302D7C4ECEDE4A-515D

   Subsystem 2 - Part No: 1K0 955 559 M  Labels: 1K0-955-559-AF.CLB
   Component: RegenLichtSens 005  0605  
   Coding: 00217125
   Shop #: WSC 31414  

No fault code found.

-------------------------------------------------------------------------------
Address 6E: Ctrl Head Roof        Labels: 7L6-919-044.lbl
   Part No: 7L6 919 044 J
   Component: DACHDISPLAY         0538  
   Revision: 00700538    Serial number: 2009266.06    
   Shop #: WSC 31414 000 00000
   VCID: 3E733A256A52DCCE64-5141

No fault code found.

-------------------------------------------------------------------------------
Address 76: Park Assist        Labels: Redir Fail!
   Part No: 7L0 919 283 F
   Component: 0E Einparkhilfe     1107  
   Shop #: WSC 00000 000 00000
   VCID: 39792939737CFBF651-5141

   Subsystem 1 - Part No: 7L0 919 283 F
   Component: 0E Einparkhilfe     1107

No Faults Found
  or DTCs not supported by controller
  or a communication error occurred

-------------------------------------------------------------------------------
Address 77: Telephone        Labels: Redir Fail!
   Part No: 7L6 035 729 E
   Component: CIB PAH  HW 203 SW  0307  
   Coding: 0000364
   Shop #: WSC 00000 000 00000
   VCID: 387F2C3D4876E2FEAE-5141

No fault code found.

End-------------------------(Elapsed Time: 24:59)--------------------------

Last edited by a moderator: Aug 10, 2015

Uwe

Benevolent Dictator

Hmm….

— Windows Based VAG/VAS Emulator Running on Windows 7 x86(VMWare)

If you’re running in a VM, that would explain much.

Why is it running on VMware?
It is installed on the computer in the same program file as the old version was installed.
VMware is installed on the computer but in a different program file.
Do I have to remove the VMware from the computer to make it work or is there a different way to do it?

Uwe

Benevolent Dictator

Running in a virtual machine is explicitly «Not supported». If it works for you, fine. But if it doesn’t, please don’t ask us why you’re having problems or how to make it work.

Eric

Ross-Tech Employee

Let’s see if we don’t have a false positive here due to VMWare being installed on your computer and having its virtual adapter active. Go to Options, set debug to 1024, save, try to connect to engine. Exit out of and send DEBUG01.DLM from the Debug subfolder of to support@ross-tech.com . Also I take it you don’t have your Dell Latitude to test on anymore?

Eric

Ross-Tech Employee

Well I am a little confused by your debug files… none indicate having detected a VM. Aside from that, I do see comms issues. The netbook stops seeing messages from the in the middle of the session, similar to what you’d experience if USB or something on your computer went to sleep. The Latitude just doesn’t see anything on the bus. Was the ignition on? For the netbook, check FAQ 2.5 . I see you skipped release 14.10, what is the story behind that? Did you not use the netbook for a long time (so lots of updates were installed recently), or did you just not use for a long time?

Источник

06.03.2014, 19:27

#1

0

проблема при сканировании шнуром VAG COM 11.11.2

приветствую всех!!!
приобрёл на АлиЭкспресс шнурок 11.11.2 драйвера установились, но при сканировании полностью или отдельного элемента выдаёт сообщение : «too many communication error» . если при полном сканировании программа ещё пытается что то делать и сообщение появляется только после 40% выполненного процесса, то когда пытаешься сканировать отдельный элемент то получаю сразу же. в поиске нашёл только как перепрошивать версию VAG COMа, а может кто сталкивался с такой же проблемой и ему удалось вылечить ЭТО?

passat B5 — 1.6 — AHL — 1997 чёрный — чёрный
passat B6 — 2.0 — BVZ — 2006 графит — чёрный
06.03.2014, 20:13

#2

1

Сообщение от старнник

приветствую всех!!!
приобрёл на АлиЭкспресс шнурок 11.11.2 драйвера установились, но при сканировании полностью или отдельного элемента выдаёт сообщение : «too many communication error» . если при полном сканировании программа ещё пытается что то делать и сообщение появляется только после 40% выполненного процесса, то когда пытаешься сканировать отдельный элемент то получаю сразу же. в поиске нашёл только как перепрошивать версию VAG COMа, а может кто сталкивался с такой же проблемой и ему удалось вылечить ЭТО?

побереги себе нервы — сдай (отошли) шнурок продавцу взад. я после похожего попадоса тупо купил оригинал от росс-теча, и не парюсь. если бабосы жалко — ищи тут на форуме продавцов проверенных.

VW Pas B5 1.6l AHL MT `98 _[3B23C5]
^{WVWZZZ3BZXP079831}
07.03.2014, 01:03

#3

Знатный Перец Клуба VW Passat B5!

0

Сообщение от Алеksандр

тупо купил оригинал от росс-теча

Поддерживаю! Купил и забыл о каких-либо проблемах.
По теме могу сказать, что именно версия 11.2 была сама по себе глючная. Вышла она позапрошлым летом. На сайте auto-intern.de прямо говорилось о том, что 11.2 с дефектом, поэтому по возможности пользуйтесь предыдущей версией или ждите обновления.
Я установил её тогда и у меня начались траблы в виде «хочет свяжется с ЭБУ, хочет не свяжется». Снёс, установил 11.1 и всё прошло.
Может здесь тоже подобный случай?
07.03.2014, 06:16

#4

0

спасибо за помощь!!!
попробую сегодня поставить 11.1 и проверить, так же у друга есть софт для 11.2 поставлю его и посмотрим что будет. если появиться положительный результат, отпишусь. вдруг ещё кто столкнётся с этим.

passat B5 — 1.6 — AHL — 1997 чёрный — чёрный
passat B6 — 2.0 — BVZ — 2006 графит — чёрный
07.03.2014, 21:15

#5

0

Недавно поймал такую же ошибку на 311.2, просто рестартнул программу и помогло.

Passat B5 1.8 ADR 98 год МКПП седан — продан, Audi A5 2.0TFSI — продан, VW Golf GTI 7 МКПП

Ваши права

Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
[VIDEO] код Вкл.
HTML код Выкл.

Правила форума

Источник

I have a 2003 Jetta it was a gas 1.8 now alh . Starts and runs but can not check timing. I can read codes with vagcom with key on but when I start engine it goes to too many communication errors to continue. Timing and I are out of adjustment. Everything else in car works fine
Help please

What version of VCDS are you using?
What does all of the writing on the interface say?

I’ll check tomorrow. VCDS works on all the other cars I’ve worked on

Its a 11.11.5 version. I can read and auto scan codes with engine off, once started them too many comun. errors.
did a autoscan codes 17970 16612 17654 17762 00849 01064 00625 01330 01336 01299 01314 01177 00771

Is there anyway to buypass to set engine timing and IQ?

11.11.5, way out of date. Lets first try a fresh install with the current version. Here is our web page to download the latest version:

http://www.ross-tech.com/vcds/download/current.php

Once you get the current version, let us know if it helps. If not, we’ll see about getting a debug report from the current version of VCDS, that might yield some clues.

One other point: What computer and what operating system are you using? Is this the same computer you have used before with VCDS? I have heard of multiple communications problems with newer laptop and tablet computers with Windows 10 relating to the computers power management. Look into power management and look at the advanced settings and look for power settings related to USB. Computers trying to reduce power usage (save batteries) can cause VCDS communications issues if they try to cut USB power.

Have Fun!

Don

a debug report from the current version of VCDS, that might yield some clues.

2X, important next step.

The computer is an old Dell with XP. It works fine on all other cars, not this one. Swapped ECU no change.

It works fine on all other cars, not this one.

Yup, so something’s going on specific to this car… a dump of the VCDS log will be very helpful in tracking this down, as posted above.

Running on batteries or ? I seem to recall someone having flaky comm running, iirc, power to the laptop from the car or some such . . . If not running fromthe laptop battery, it might be worth a try . . .

couldn’t load new version. Windows says remote device or resource won’taccept the connection

tried another laptop with 11.11.5, same results can read codes till I start the car then t-m-c-errors

Please post the debug logs you’re getting with your *current* version of VCDS… the version that’s giving you all the communication errors.

Otherwise everyone’s just batting at smoke.

I’d still like you to answer my question regarding power source for the laptop . . .

— Tim

anyway I can bypass something so I can set timing and IQ?

Looking at the logs could fix your issues permanently… what’s the issue?

Please post the debug logs you’re getting with your *current* version of VCDS… the version that’s giving you all the communication errors.
Otherwise everyone’s just batting at smoke.

Not sure how to load the logs on here. Which ones would be helpful?

Jef can suggest any specific logs he had in mind, I was thinking start with the line-by-line readout you get doing an autoscan.

Cut-n-paste to here will work fine, and probably best to <S>ave the scan to a file on your computer and then cut from that file… if you just try to grab it off the screen as it scrolls by something might get missed.

Jef can suggest any specific logs he had in mind, I was thinking start with the line-by-line readout you get doing an autoscan.

Cut-n-paste to here will work fine, and probably best to <S>ave the scan to a file on your computer and then cut from that file… if you just try to grab it off the screen as it scrolls by something might get missed.

An autoscan might help but I am not sure. It couldn’t hurt to post it.

However, I doubt that much more help will be coming from Jef. The latest versions of VCDS require a firmware update for the interface cable itself. If the OP’s interface won’t accept the connection from the latest version, it is probably not a genuine Ross-Tech interface cable (or else he has Windows USB issues or a faulty cable). If I am correct and it is not a genuine R-T interface cable, I would not expect much help from R-T support people. If the problem is with a Chineseum interface cable, support will have to come from the thieves who sold him the cable (and cracked software version 11.11.5) in the first place.

Have Fun!

Don

Ah, but posting the auto scan will clear up the providence of the interface once and for all. And, if it’s an off-shore clone that in itself is likely a strong possibility as to the comm issues and potentially diminished returns to troubleshoot deeper.

I don’t think the problem is with VCDS, since it works fine with 10 others cars. What I need most is to be able to set timing and IQ.

Well, you need a functioning interface to talk to the ECU to read the timing and set the IQ., and not to put too fine a point to it… but I think it boils down to:

— if it’s a genuine interface…that’s one possibility eliminated (ie it’s not flaky offshore hardware with cracked firmware/software, that’s struggling a bit in an engine swap situation) and a bunch of folks here will likely be happy to help further

— if it’s a cloned interface with pirated software…that could be the problem in and off itself, and as this forum does not condone piracy any further discussions to further troubleshoot are best taken up with the seller of the hardware/software, as posted above.

Not saying one or the other is the case… just pointing out that the road forks at this point.

I have a friend that has a commercial VCDS. Maybe he will let me borrow it over the weekend

Let start with this, on the interface, the part you plug up to the car is a sticker. What is the information on that sticker? A photo would be fine.

It would be correct to assume that we (Ross-Tech) are not inclined to invest any effort for some one who is using a clone product.

With some of your statements provided, I have my doubts you are using a legitimate Ross-Tech interface. But before any one passes final judgement, I think it is fair to ask for some proof to show you have the real deal.

Last edited: Oct 18, 2016

I bought the cable and program from someone either here or Vwvotex
Not knowing or care what its origin as long as it worked. Been using it for 5 years.
Like I said I’ll try my friends original business quality

I bought the cable and program from someone either here or Vwvotex
Not knowing or care what its origin as long as it worked. Been using it for 5 years.
Like I said I’ll try my friends original business quality

Yes, but Jef is saying if it’s an authentic cable, he’ll provide some support

OK tried the official Ross-Tech cable with the current program. Same too many communication errors.

Источник

Location Offline
V.I.P

Reputation:
1,042

Thanks Given: 463
Thanks Received: 3546 (2407 Posts)

Posts:
5,812
Threads:
145

Joined: Apr 2013

1

09-07-2017, 09:53 PM

I have here MED9.5.10

Golf 5 1.4 FSI

Customer said car dont start.

I take a look and no engine light comes on when ignition is on.

When i try to communicate with the ecu, i cant, » to many communication error to continue » is what vcds said.

I take the ecu out off the car and see that someone else have use some silicone.[/align]

I think one of the components is broken, but witch one ? 30471 — 30397 ?

2 Pictures from pcb in att..

VAG 100% SOLUTIONS

VAG IMMO OFF + CLONING SERVICE

Thanks given by:

kokolo
Location Offline
Junior Member

Reputation:
3

Thanks Given: 38
Thanks Received: 29 (22 Posts)

Posts:
111
Threads:
10

Joined: Feb 2013

2

09-08-2017, 01:14 PM

I think that somebody writed this ecu obd,read flash and check

Thanks given by:

MK2-VRT
Location Offline
V.I.P

Reputation:
1,042

Thanks Given: 463
Thanks Received: 3546 (2407 Posts)

Posts:
5,812
Threads:
145

Joined: Apr 2013

3

09-08-2017, 01:17 PM

No i check it, read it by Bdm and all original.

VAG 100% SOLUTIONS

VAG IMMO OFF + CLONING SERVICE

Thanks given by:

Auto-IC
Location Offline
Junior Member

Reputation:
1

Thanks Given: 7
Thanks Received: 13 (8 Posts)

Posts:
31
Threads:
1

Joined: May 2017

4

09-08-2017, 01:34 PM

I think you may need open the ECU to check if there is somthing broken, by the way 30471 — 30397 we have. http://www.auto-chips.com

ECU chips, relays, resistors,MCU,EEPROM,capacitors, transponders, test platforms.

Thanks given by:

kokolo
Location Offline
Junior Member

Reputation:
3

Thanks Given: 38
Thanks Received: 29 (22 Posts)

Posts:
111
Threads:
10

Joined: Feb 2013

5

09-08-2017, 06:08 PM

(09-08-2017, 01:17 PM)MK2-VRT Wrote: No i check it, read it by Bdm and all original.

Are you checked eprom?

Thanks given by:

wolek14
Location Offline
Senior Member

Reputation:
35

Thanks Given: 162
Thanks Received: 142 (102 Posts)

Posts:
294
Threads:
50

Joined: Aug 2017

6

09-08-2017, 09:05 PM

Any reaction for temperature? How much current does it take?

Thanks given by:

acmotor
Location Offline
Senior Member

Reputation:
171

Thanks Given: 1100
Thanks Received: 725 (547 Posts)

Posts:
1,727
Threads:
31

Joined: Jun 2014

7

09-09-2017, 09:58 PM

(09-07-2017, 09:53 PM)MK2-VRT Wrote: I have here MED9.5.10

Golf 5 1.4 FSI

Customer said car dont start.

I take a look and no engine light comes on when ignition is on.

When i try to communicate with the ecu, i cant, » to many communication error to continue » is what vcds said.

I take the ecu out off the car and see that someone else have use some silicone.[/align]

I think one of the components is broken, but witch one ? 30471 — 30397 ?

2 Pictures from pcb in att..

Hi sir, i think you need to start with wiring, fuse and relay. or power supply and ground connections. since you can read with BDM and no engine check light. for sure there is power supply faulty. try OBD diagnos on table and check if VCDS has communication with ECU.

Thanks given by:

Reputation:
19

Thanks Given: 97
Thanks Received: 127 (33 Posts)

Posts:
254
Threads:
93

Joined: Dec 2014

8

09-09-2017, 10:33 PM

I would try to get communication with it on the bench via OBD.

and please if you found this info useful

Thanks given by:

MK2-VRT
Location Offline
V.I.P

Reputation:
1,042

Thanks Given: 463
Thanks Received: 3546 (2407 Posts)

Posts:
5,812
Threads:
145

Joined: Apr 2013

9

09-09-2017, 10:37 PM

Thx for helping, but i use this ecu on bench now, no communication possible, so i think there is a component on pcb defect, but witch one is the question..

VAG 100% SOLUTIONS

VAG IMMO OFF + CLONING SERVICE

Источник

Uwe

Benevolent Dictator

Uwe

Benevolent Dictator

Uwe

Benevolent Dictator

Eric

Ross-Tech Employee

Eric

Ross-Tech Employee

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://passatworld.ru/images/icons/icon1.png" alt="По умолчанию" /> проблема при сканировании шнуром VAG COM 11.11.2

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://passatworld.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://passatworld.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://passatworld.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://passatworld.ru/images/icons/icon1.png" alt="По умолчанию" />

Похожие темы

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://passatworld.ru/images/pw_style/buttons/collapse_40b.png" /> Ваши права

проблема при сканировании шнуром VAG COM 11.11.2

Ваши права