DashCommand not working with Innovate OT-2 as advertised

[Weston@PPE]

kaptincocoa2,

I responded to your email about this.

[BlackRoseRacing]

I skimmed through this topic quick and I'll post my 2 cents....
I had the OT-2 for approximately 3-4days, working with Innovative, I could only monitor 2-3pids at a time. Innovative stated it was because the protocol on my 2002 Dodge was slow. I returned the OT-2 and went back with my Elm327 adapter.

[Dan.lewis]

Having the same issues!!!!

Paid £29.99 for it logworks works fine but Dashcommand wont see anything wont even get the VIN.

Emailed techlog to support.

Its a 2004 Skoda Octavia 1.8t so the same as a golf gti.

Using IPhone 3gs on lastest 4.2.1 non jailbroken

[Pault5]

Hi,

New to the forum, but I'm having the same problem with Dashcommand and the Innovate OT-2, when I try and use it on a 2009 VW T5 Transporter.

Works just fine on a 2010 Ford Mondeo using the Ipad, but none of the gauges work on the VW.

Seems strange as the Innovate "Logworks" app works fine, but is not really suitable on the Ipad.... so I'm not sure if the problem is with Dashcommand, or with the signals the VW puts out (even tho' it should be OBD-II compliant???).

Has anyone else had issues using it with a VW???

Have sent a log to Support, but no news as yet.

Regards,
Paul

[Pault5]

Hi again,

An update on the above...

I tried the same thing using ScanXL on a laptop (connected to the VW)... and got a similar response....

[18:31:48.470] Opening OBD-II Connection...
[18:31:48.490] ERROR: Unknown diagnostic system:
[18:31:48.490] ERROR: Using this diagnostic system instead: OBDII_GENERIC
[18:31:48.490] Searching for Innovate interface...
[18:31:48.710] Found OT2  interface!
[18:31:48.710] Found Innovate interface on USB!
[18:33:27.873] OBD-II connection successful!
[18:33:27.903] Retrieving VIN...
[18:33:28.443] Detecting Vehicle Information...
[18:33:29.835] Detected 1 on-board modules.
[18:33:29.835] Finished detecting vehicle information.
[18:33:37.476] Detecting Supported PIDs...
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.SPARKADV
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.SHRTFT2
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.LOAD_ABS
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.LONGFT1
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.MAP
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.LONGFT2
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.TP
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.MAF
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.SHRTFT1
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.VSS
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.IAT
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.ECT
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.LAMBDA
[18:34:37.102] Warning: Not scanning unsupported parameter: SAE.RPM

So the problem isn't just in Dashcommand.

Maybe Dan.Lewis and myself have the same issue trying to connect to a VAG vehicle?

Regards,
Paul.

[BrianP]

I'm not surprised that you are seeing the same problem in ScanXL, if you are seeing it in DashCommand - under the hood both software applications share the same codebase for OT-2 connectivity.

I'm also not surprised that some of you are reporting that LogWorks is working and DashCommand is not, and vice versa. You see, our software uses the OT-2 in "expert mode" and LogWorks is simply listening to the streaming MTS data from "normal mode". Since our software and LogWorks are operating in different modes, the problems and symptoms are not directly comparable, because our software may exhibit a bug and you wouldn't see that in LogWorks and/or the OT-2 may exhibit a bug only in expert mode and you also wouldn't see that in LogWorks.

We are currently looking into these issues, and working with the guys at Innovate to figure out where any problem areas are. We should hopefully be submitting a new version of DashCommand to the app store soon with many improvements.

[Pault5]

Thanks very much for the reply BrianP,

That makes sense now.

Have you any idea when the upgraded  app will be available and will it definitely fix the problem?.
Will the underlying Codebase for Scanxl also have to be changed to work with the OT-2?

Kind regards,
Paul.

[J-R]

Just bought the DashCommand APP to use it on my 2005 BMW 1-series. It connects fine to the OT-2, but are unable to read anything from it. I get the same errormessages as Pault5:
"Warning: Not scanning unsupported parameter:..."
Logworks is functioning ok, but I think DashCommand lokks like a better app

I hope you will fix this issue and be able to read more OBD parameters. Otherwise the app is useless to me

[kaptincocoa2]

I guess i'm back here BECAUSE i have paid my $49
And with the news posts, filling page 3 just a quick thought or 2.
1st (Weston)  i have received your e-mail and the refund from Apple, i really have no idea what to expect from them, if anything, time will tell.
2nd i believe it' Brian here with the mention of an update, someday, YES THAT IS A MUST, if you want to sell to the Ipad as there is another coming soon and because the Ios4 across the board.That includes the new phones and Touchs.
3rd  the new people/owners of this app i wish you luck but it's clear PPE is saying it's Innovate and so in the meantime i'm letting them work it out.
Now as to what Innovate has done for me,, A REFUND check(minus the tax, fair enough?)

So after all these months i am back to square 1,, with DC and no hardware soooooooo back to the shopping!
Ps i'll be keeping an eye here why not i'm no "hater" so if anyone on knows/hears anything on Apple's positon on this or any of their app, i thank you now.
glenn

[Pault5]

Fixed the problem..... by sending back the OT-2 and buying a OBD-Link (wifi) instead!.
In fairness, the chap at Innovate where I bought the OT-2 was really helpful and gave me a full refund. Nice chap

Plugged in the OBD-Link, and now Dashcommand is working fine 

Thanks to the chaps at Palmer (and this forum) for pointing me in the right direction.

Cheers,
Paul.

[e8ay t]

I am in the same boat, what disappoints me, is that these posts date back to oct 29th 2010, in nov' palmer acknowledge there's an issue, yet today (21st feb 2011) there is still no mention on the app store that there trying to fix these issues, so a couple of weeks ago i bought the innovate ot2 and dashcommand to use with my iphone 4 - expecting something spectacular, but am feeling very unimpressed as i've been trying to get it going for hours and hours over days and days, expecting it to be user error, only now that i've resorted to the forum have i found i've wasted both time and money.
Maybe it's time to leave feedback on the app store, with guidance towards these posts!

[kaptincocoa2]

Hello,
It's been a month since i posted here.
And the only two posts HERE are e8ay t and it seems like you just took a 180 and left Innovate, well i did too and yes, a refund, i don't think they need the headaches, till PPE re-works DC for the new Ipods etc.
And next paul 5 i think it is, yes it it is terribly disappointing because at the Apple apps it sounds SOOOO great, "GAUGES GAUGES" and as you point out, WHY won't PPE make some kind of a statement, when they will release an update.
Btw. where are the "moderators"?

[Weston@PPE]

We are currently looking into ways to improve connectivity with the OT-2 from our software, but these take time to complete. Keep in mind that we have many customers asking for new features, bug fixes, etc. and we are doing our best to keep everyone happy. Thank you for your patience with DashCommand.

We are hoping to release a new version soon.

[carriso]

Hi,
I have the same problem !!! OT-2 + DasCMD doesnt work with my Honda Civic. Please help me...
Greetings,
Carlos

[e8ay t]

I'm currently being patient, and settling for the logworks package. i have managed to gain a connection to my s2000 but no useful data is shown.
i am however going to leave feedback on the app store, with reference to this issue!