Cant connect to ECU

[wrobsongtc]

Hi guys,

To cut a long story short, I bought a bluetooth OBD2 reader to get a fault code read, app said it couldn't connect to my ECU it also sent loads of warning lights away and the rev counter starting going between 1000rpm and auto start/stop, so I sacked it off as cheap kit and took my car to a local garage to have the fault code read and when the code reader was attached to the OBD2 port it also couldn't read any fault codes. 

Does anyone have any ideas about this?

I've checked all the fuses and the OBD2 port does power the readers that have been used so is working.

Car is 62 reg astra GTC 2.0cdti

Thanks,

Will

[Rusty2009]

If it couldn't read any codes it could be because there is none stored.

What equipment did the garage use alot of these generic scanners won't pull anything.

[Big Dave2]

My mates Bluetooth reader didn't bring up any fault codes on my 2.0CDTi Astra when the SVS message was being displayed.

But my Opcom that I previously bought to diagnose problems with my old Vectra-C worked fine on my Astra-J and diagnosed a faulty glow plug.

[wrobsongtc]

If it couldn't read any codes it could be because there is none stored.

What equipment did the garage use alot of these generic scanners won't pull anything.

The garage used a snap on scanner not sure of any other specifics

[Rusty2009]

If it couldn't read any codes it could be because there is none stored.

What equipment did the garage use alot of these generic scanners won't pull anything.

The garage used a snap on scanner not sure of any other specifics

That should of pulled any codes that were stored then.

[wrobsongtc]

went to another garage, plugged into a newer reader and got 2 code readings back:

ABS pump and ABS sensor front drivers side.

Pulled the sensor out gave it a clean and good as new! 

Faults have cleared and stayed off so far, cheers for the input and confirming that cheap OBDII readers are trash 

Cheers,

Will