OBD FUSION APP Working OK in one car but not in other

[Turbo_Boss]

Hi guys,

Maybe any of you can help me since our cars are similar.

I am using a Wifi OBD Tool that I got from ebay. I am including a picture of it. http://i85.photobucket.com/albums/k57/Turbo_Boss/OBDTOOL_zps1ff32a40.jpg

I have use this same OBD Tool in a 2002 VW Jetta with 2.0 engine and works OK and I can see all the dashboard indicators working. I also try it on a 2007 Toyota Prado and its working too.

But it does not work on my 2002 Skoda 1.8T

I am pretty sure my car is OBD2 compliant. I have VCDS Lite from http://www.ross-tech.com/vcds-lite/ and I connected with my laptop with a inexpensive cheap OBD cable I got from ebay and I can read my car computer and erase MIL light.

This is the OBD to USB cable that I use to connect my car with VCDS: http://i85.photobucket.com/albums/k57/Turbo_Boss/VAGCOM_zps76cec2f1.jpg

Dont understand why the OBD FUSION Aap is not working with my car. This is the message I got: http://i85.photobucket.com/albums/k57/Turbo_Boss/CANTCONECT_zpsb34a8b47.jpg

What OBD Gadget and Aap you are using in similar car

Thx for your time and help,

Isaac

Here is the Debug File I got from the Fusion Aap when trying to connect to my car


<----- General Information ----->

OBD Fusion

2.16.0.791

<----- Device Log ----->

Opening communications: 192.168.0.10:35000

Port Open

?: [??]

ATZ: [ATZ ELM327 v1.5]

Interface connected

ATE0: [ATE0
OK]

ATL0: [OK]

ATRV: [11.7V]

Trying Protocol: SAE J1850 PWM (41.6 Kbaud)

ATSP 1: [OK]

01 00: [BUS ERROR]

01 00: [BUS ERROR]

01 00: [BUS ERROR]

Trying Protocol: SAE J1850 VPW (10.4 Kbaud)

ATSP 2: [OK]

01 00: [NO DATA]

Trying Protocol: ISO 9141-2 (5 baud init, 10.4 Kbaud)

ATSP 3: [OK]

01 00: [BUS INIT: ...ERROR]

Trying Protocol: ISO 14230-4 KWP (5 baud init, 10.4 Kbaud)

ATSP 4: [OK]

01 00: [BUS INIT: ...ERROR]

Trying Protocol: ISO 14230-4 KWP (fast init, 10.4 Kbaud)

ATSP 5: [OK]

01 00: [BUS INIT: ERROR]

Trying Protocol: ISO 15765-4 CAN (11 bit ID, 500 Kbaud)

ATSP 6: [OK]

01 00: [CAN ERROR]

Trying Protocol: ISO 15765-4 CAN (29 bit ID, 500 Kbaud)

ATSP 7: [OK]

01 00: [CAN ERROR]

Trying Protocol: ISO 15765-4 CAN (11 bit ID, 250 Kbaud)

ATSP 8: [OK]

01 00: [CAN ERROR]

Trying Protocol: ISO 15765-4 CAN (29 bit ID, 250 Kbaud)

ATSP 9: [OK]

01 00: [CAN ERROR]

Trying Protocol: Automatic

ATSP 0: [OK]

01 00: [SEARCHING...
UNABLE TO CONNECT]

ATRV: [11.6V]

Connected to the scan tool but unable to connect to the vehicle.

ATSP 0: [OK]

ATZ: [ELM327 v1.5]

<----- Message Log ----->

Error, Connected to the scan tool but unable to connect to the vehicle.=

 

[sockpuppet]

I use the odb2 bluetooth dongle from ebay and registered torque app for android. At under £20 for both they are excellent.

 

[Turbo_Boss]

After reading a post in otro forum that my 2002 Skoda 1.8T is not OBD II Compatible, I went out with my laptop/VCDS Lite and conect it to my 2002 Skoda 1.8T and it say the car is not OBD compliant.

I now I undertand why the OBD Gadged and Aap Fusion dont work in my car.

The VW Jetta is a MK4 year 2009. VW still produce this model in Mexico.

Well, thx for your time and help.

Isaac

Here are the VCDS Lite images were it say my car is not OBDII Compatible.