Vectra C 2005 'No Communication with ECM' Opcom

[justathome]

Hi everyone,

I have a new opcom V2.
Freshly installed win7 laptop no other software except opcom.
Software installed, and installed the drivers from the drivers folder.
Ran test interface and updated to V1.39. and now tests all ok.

When running diagnostics to the car ( vectra C 2005 ) all I get is a click and 'there is no communication with the ECM'

I'm stuck, any advice. I have an emissions (engine)warning light on and trying to diagnose.
EDIT

Further testing by scanning each individual ECU came up with the following results.
Any help would be appreciated.
---

These come up as 'SWCAN' scans..

OP-COM 090821d - PC based diagnostic tool

Please add your workshop
name in the settings window

OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Body|BCM (Body Control Module)


Read Info...

Identifier: 0x0208
VIN: W0L0ZCF6841119024
Part Number:13168783
Software version number: C12C93 08041404
Hardware key number: ÿÿÿÿÿÿÿÿÿÿ
System description: TEMIC04
Variant programming : 0x20202020202020303030363638343839
Alpha code: EJ
Manufacturing date: 000400050008
Code Index and version:


Total number of fault codes: 3

B3057 - Security Code Not Programmed
(00) - Intermittent

B0967 - Park Pilot Switch Circuit Open or High Voltage
(05) - Present

B3916 - No Communication With Alarm Siren
(0F) - Not present

OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Body|Instrument


Read Info...

Identifier: 0x0102
VIN: W0L0ZCF6841119024
Part Number:13165955
Software version number: 8.39 16/03
Hardware key number: 0000000000
System description: VDO 0400
Alpha code: MB
Manufacturing date: 040510
Code Index and version: 001 05


Total number of fault codes: 1

U2105 - CAN-Bus No Communication with ECM (Engine Control Module)
(7F) - Not present

OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Body|PAS (Park Pilot)


Read Info...

Identifier: 0x0101
Hardware number:50
System name: PAS
Part Number:13181070
Software version number: 0000002D
Programming Date: 20041904
Hardware key number:
System description: BOSCH0400
Alpha code:
Code Index and version: 009 01


Total number of fault codes: 3

U2139 - CAN-Bus No Communication with CIM (Steering Column Module)
(00) - Not present

U2107 - Invalid Data from BCM (Body Control Module)
(71) - Present

B0952 - Loudspeaker Circuit Open or Low Voltage
(06) - Present

OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Body|SDM (Airbag)


Read Info...

Identifier: 0x0101
VIN: W0L0ZCF6841119024
Part Number:13170590
Software version number: 0C0C3303
Variant programming : 0x41533035393053303330383238384720
Alpha code: DW


Total number of fault codes: 1

U2139 - Invalid Data from CIM (Steering Column Module)
(00) - Not present


OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Infotainment System|TID (Triple Info Display)


Read Info...

Identifier: 0x0306
Hardware number:13190895
Part Number:13190970
Software version number: 08.08.17.00
System description: VDO 0400
Alpha code: WZ
Manufacturing date: 040429
Code Index and version: 002 02


Total number of fault codes: 1

U2103 - No Communication with CAN-Bus (Mid Speed)
(00) - Not present

These are the one that won't comunicate (time out and no communication errors)
and come up as'HSCAN' scans

OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Engine|Z 22 YH


No stored codes!


OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Chassis|ABS/TC/ESP


No stored codes!



OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Body|Immobilizer


No stored codes!


OP-COM - CAN Communication Window> 2004|Vectra-C / Signum|Body|CIM (Steering Column Module)


No stored codes!

---
As you can see alot of errors relating to CIM, would these be related to my inability to scan both it and engine/abs ecu's?

Any advice would be appreciated...

Justin

 

[MikeS]

if you were having problems with the CIM the car would not even start

ABS / Tc ecu is a different ecu to the engine

i know that enginecheck by gendan interfaces with the Vectra C canbus

as for opcom i am still waiting to see one in action as the units i have acquired never worked

 

[dodger]

Is the ignition on position 2?, when a member on AOC connected mine up it didn't read any ECU info until the ignition was on.

 

[justathome]

Yep, IGN on and running. No difference..

 

[dodger]

what was your interface firmware version, i'm guessing it was 1.33, might be worth going back to this version

 

[justathome]

That did cross my mind, or maybe there is a newer driver version which I could test.
I just find it strange that basically out of all listed ECU's only 3 wont respond. Wish there was someone local that I could test there's
to eliminate what has the issue.
Been contemplating disconnecting the battery for 15-30 mins and seing If a reset would cure it...

 

[rushy]

Just be aware mate that if this is a hacked ebay one and not a proper £400 version they can really mess up a working Vec C. Its happened before quite a few times. This is why they wont allow Opcom threads on the Vec C site unless its confirmed a proper version. Duncan the forum owner owns a real one, so if yours is legit then drop him a PM and he'll talk you through what you need top do, or just use opcoms own support, thee very good.