So the first question is - is the JDM version OBD2 compliant?
Thanks
![Cool 8)](./images/smilies/icon_cool.gif)
Jubaeg wrote:Thanks for the intel.
Interesting regarding FreeSSM. I think I'll pass for the moment on that one though as it is computer (WIn/Mac/Linux) based and not Android and I was hoping to stick with my Android. They also say that you should use the "Vag-Com KKL 409.1" cable which although can do a USB connector you'd need an Android device that has a host-USB port and most don't - well mine doesn't anyway.
Given OBDKey are in the UK why don't you contact them directly and ask - you never know you may be able to drive to them and try before you buy?
Good luck.
Matthew
- Now is that what we need???Supports Subaru SSM (4800) protocol
Hi - I have just recently got interested in this type of product to use with my Subaru Legacy 2.0 GT Spec B (JDM twinscroll) 2004 - I have tried 'Torque' with my HTC Desire HD using an ELM327 BT Module. It does not seem to be able to read the ECU although it says it is connected...
Your web documentation says that your system can read 'Subaru SSM (4800) protocol' will this then work with my JDM Legacy?
The other thing that may have an influence is that my ECU is EcuTeK mapped - would that have an influence on readability?
I have tried to phone you to discuss this but could not get an answer.
I await your comments with interest, I have posted on various Subaru enthusiast forums to find out how we can show the engine data on android apps - it would be great to start getting somewhere with some real answers...
Thanks for your time
WiFi Configuration Technical Information - Ad hoc Mode
SSID: OBDKey WLAN
IP: 192.168.0.74
Subnet: 255.255.0.0
Port: 23
Antenna: Internal
Power Consumption: 0.240 Watts
Wifi Standard: 802.11b/g
Jubaeg wrote:I see no reason why the Wifi version wouldn't work with Android in that Android can work with wireless networks and you are just connecting to a fixed IP address for the device being:WiFi Configuration Technical Information - Ad hoc Mode
SSID: OBDKey WLAN
IP: 192.168.0.74
Subnet: 255.255.0.0
Port: 23
Antenna: Internal
Power Consumption: 0.240 Watts
Wifi Standard: 802.11b/g
But I'm just guessing and don't know 100%.
Will be interesting to see if you get anywhere further on the Torque forum.
Did you get any response from OBD-Key? I guess if they have a return policy if it doesn't work then that would make it slightly more palatable...
OZ trip - you're welcome to ship to me!
Return to 2.0T engine specific
Users browsing this forum: No registered users and 4 guests