Forums
Forums
Notifications
Clear all
Topic starter
Hi there, i've been one of the unfortunate people that have paid the $100 for kiwibluetooth adapter + full version of torque only to find its not compatible with the australian 2002 VX commodore/berlina. *sighs* . My car does have the OBD2 connector but from what i read in australia GM use a ALDL protocol which is a (OBD1 with a GM twist)?... Anyway just thought i'd post this in case there is a trick to getting it to work on my holden ?
I have a HTC desire HD, android 2.2, kiwibluetooth, paid ver torque. Phone is paired with the pdX adapter, in the obd2 screen in the torque application everything is ticked and passed other than one warning saying cant read ECU. I can however get my phone and torque working %100 if i plug it into a 2008 holden captiva so that indicates to me the adapter is fine ... anyway no doubt youve heard this a million times so thought id ask incase you had a work around for it ... thanks
Posted : 13/11/2011 12:01 am
Hi!
ALDL was prior to OBD1 - it's a different type of protocol and signalling from what I can see, so it's unlikely to work with the standard OBD2 adapters.
Torque can now talk other protocols than OBD2 - the latest update added all the support for talking any protocol format, so the only hurdles to adding support are needing an adapter that can interface to the diagnostics correctly, and a vehicle to spend a couple of weeks on working out how to talk to it. At the moment, as ALDL needs a different type of signalling, it's unlikely to have support added to it though
Posted : 13/11/2011 10:52 am
what do you mean Torque can talk to other protocols? Like what?
Posted : 15/11/2011 3:11 pm
At the moment it can talk SSM (Subaru select monitor, which requires an SSM capable bluetooth adapter) , in addition to plain old OBD2.
However it can talk any protocol required, provided there's an interface adapter to support it and some information freely available on the protocol
Posted : 15/11/2011 4:07 pm
Mine is a 2003 vy ss commodore, it apparently uses the J1850 VPW Protocol, but I still don't get the error show up. I am getting the engine fault light.
Posted : 31/03/2012 11:46 pm
Hi
There was some work done in the latest pro versions fault code reporting to retrieve faults on some holdens, so make sure you are on 1.5.50 as this should (hopefully) work for you now
Posted : 01/04/2012 7:46 am
unfortunately it has not 🙁
Posted : 01/04/2012 10:59 am
Hi
Just to confirm - this is a 'Check Engine' light, and not an ABS/Airbag light, yes?
Posted : 01/04/2012 1:13 pm
Yeah definately the check engine light, this model car comes up with the check engine symbol and also says check engine in text on the LCD display.
Posted : 01/04/2012 10:23 pm
Hi guys,
I have a 2005 WL statesman and have no problem getting the OBDII working to talk to the ECU. Unfortunately however the car is a bit of a hybrid when it comes to the comms, it still uses ALDL for other functions such as windows, air con, abs, stereo etc.
I'd like to get access to the ALDL side of things too. As well as be able to use Torque for communicating with my 1998 VT commodore.
Ultimately I'd like to be able to send and recieve commands over the ALDL to lock/unlock doors, raise electric windows, adjust the clock without the use of the radio (the clock is a standalone unit which is adjusted using the statesmen radio which sends commands to the clock via ALDL.
There is a guy here ( http://www.techedge.com.au/vehicle/aldl8192/8192hw.htm)that has a simple circuit to convert ALDL to RS-232, which I was then going to convert to bluetooth and cross my fingers that it works with Torque and WinALDL (may have trouble with baud rate being 8192)....
The guys at carmodders.com have some usefull readying on talking aldl to a pc as well as the folks at delcohacking.com
Posted : 22/01/2013 11:45 pm
