Well, I've just spent my first weekend with my new Discovery (my first) and am overjoyed to find that it behaves perfectly - for now 
and has not left a mass of fluids on my drive.
Now, one thing that took me by surprise was that I tried to use the Android app Torque Pro it connected to the bluetooth OBD dongle correctly but came up with the 'Cannot speak to ECU' error. There is power coming from the ODB socet and the power lights on the dongle work fine.
Prevoius reading led me to belive that the Disco 2 was fully OBDII compliant so I was a bit struck as to why I was receiving this error.
My plan was (is) to use a Tesco Hudl tablet as the in car sat-nav, music player and trip computer via OBD.
I have also seen the other trip computers on offer such as Scan Guage and Ultra Guage which Disco 2 users seem to be using without issue and may be on the cards if I can't get Torque to work.
So, what is the problem I may have getting an OBDII adaptor to talk to the Disco correctly?
Any help greatly appreciated
and has not left a mass of fluids on my drive.Now, one thing that took me by surprise was that I tried to use the Android app Torque Pro it connected to the bluetooth OBD dongle correctly but came up with the 'Cannot speak to ECU' error. There is power coming from the ODB socet and the power lights on the dongle work fine.
Prevoius reading led me to belive that the Disco 2 was fully OBDII compliant so I was a bit struck as to why I was receiving this error.
My plan was (is) to use a Tesco Hudl tablet as the in car sat-nav, music player and trip computer via OBD.
I have also seen the other trip computers on offer such as Scan Guage and Ultra Guage which Disco 2 users seem to be using without issue and may be on the cards if I can't get Torque to work.
So, what is the problem I may have getting an OBDII adaptor to talk to the Disco correctly?
Any help greatly appreciated
Last edited:
