iphone 4 + dashcommand + legacy 2005 = no data

[henrylegacy]

hi guys

I am having trouble getting data from my 2005 legacy BL5, its from Japan. I am connecting it to my iphone thru elm wifi unit.

I managed to get the volt meter and reading engine codes but nothing else, not evening rev. Gone thru the user guide but no luck.

These guys managed to get it working....any ideas?

http://legacygt.com/forums/showthread.php/oem-nav-hack-performance-gauges-movies-and-more-137185.html?t=137185&highlight=wifi+obd

[John@PPE]

What elm WIFI unit are you using?

First suggestion I would try is to increase the OBD-II timeout to the maximum and revalidate the PIDs. This can all be done in the vehicle manager screen.

Then if it still isn't working, take a look at the console to see if there is any information therein.

[henrylegacy]

I don't know the brand but I know it is elm327

I will try that when I can a chance, the info from console is like "unable to read unsupported parameters sth.rpm" I will post a proper one but that's pretty much the error message from console.

[henrylegacy]

adjusted the interval and no luck 

the console said

Warning: Not scanning unsupported parameter:SAE.RPM
Warning: Not scanning unsupported parameter:SAE.VSS
Warning: Not scanning unsupported parameter:SAE.BARO
Warning: Not scanning unsupported parameter:SAE.FLI
Warning: Not scanning unsupported parameter:SAE.AAT

any ideas?

[John@PPE]

It sounds like your vehicle might not be OBD-II compliant. If that is the case, then DashCommand will not be able to get any PIDs for your vehicle.

Can you please take a look at this link. https://www.scantool.net/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=2&nav=0

This will help you figure out whether you have OBD-II in your vehicle.

[henrylegacy]

I will check that when I get home but I managed to get the rev info by pluging in Pivot X3gauage to obd2 and it reads water temp and rev fine.

[John@PPE]

It might be an incomplete implementation of OBD-II, or an earlier variant. Which is the case in some Japanese cars from the period.

Or it could be an issue between the hardware and DashCommand. If you can determine the brand that also might suggest some ideas, assuming your car supports it.

[henrylegacy]

I took a picture of it and compared with the link you sent me

it has pin 4,5,7, 11 and 16.

it is ISO9141/14230

thanks a lot for your help and advice so far 

[henrylegacy]

I found some data about the ecu setting

ecuexplorer.googlecode.com/files/ssm.pdf

this pdf doc says the subaru uses ISO9141 interface and uses UART setting, if you have time have a look the pdf file above 

[John@PPE]

It appears that your car is OBD-II, so we should be able to get this working.

Can you set the OBD-II Timeout to 500, and the ISO/KWP Keep Alive Interval to 1000. That's a little different than before.

Then go into the console and enable debugging.

Go into Vehicle Manager and validate the PIDs, then test to see whether you get any data.

If not, email us a techlog from the console before exiting and we'll look at it.

If you send an email, mention this thread in the email.

[henrylegacy]

no luck

sending you guys the log now

Thanks:)