|
Sashik259
|
 |
« on: January 14, 2012, 03:06:33 am » |
|
Hi
It's very sadly to be charged about $50 but get nothing.
Anybody help me please to configure my DashComand?
What to do to make some gauges work?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
Sashik259
|
 |
« Reply #2 on: January 14, 2012, 12:37:57 pm » |
|
First of all, It's not bad to get stable connection. Establishing connection may lasts from 2 to 5 minutes and 9 of 10 times it ends with the message "Error detecting OBD-II protocol"
Secondly, If there is a miracle and connection was established, the only function that works is scanning DTC-codes. All the gauges show no information (even VSS & RPM sensors show "NO DATA"). If I need to add some PIDS and go to Data Logging -> add PID -> all the PIDS have X-symbol!
Thirdly, connection shouldn't be lost.
I hope for your help.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #3 on: January 14, 2012, 03:33:38 pm » |
|
What kind of OBD-II hardware interface do you have?
It sounds like it might be a defective unit. It should be able to connect more quickly than that.
Also, is it dropping the connection after it connects? How long does it hold the connection before dropping?
As far as no supported PIDs, you may need to re-validate the PIDs. In the vehicle manager, there is a button to validate the PIDs. Try that to see if your PIDs are supported.
|
|
|
|
|
Logged
|
|
|
|
|
Sashik259
|
|
« Reply #4 on: January 14, 2012, 09:48:59 pm » |
|
I have Iphone 4S IOS 5.0 with installed DashComand ver.2.9.1 (Build 2435) and it connects through Innovate OT-2 OBD-II adapter via WIFI to my car (AUDI A6 C5). The same composition of hardware & software connects to Mercedes GL 500 model year 2009 without any connection delay or spontaneous disconnection, I can see all the gauges I need. The same OT-2 adapter works fine with Logworks software and my car AUDI A6, but Logworks' capabilities are very limited. I have techlog in which you can see how it connects and disconnects. Connection failure occurs in 3-5 minutes. As for re-validating PIDS, I have already done it one or two times but no result: supported PIDS only what begining from CALC (There's no reason to read these PIDS because they are calculated I suppose). I think VSS & RPM sensors might be read at least.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #5 on: January 14, 2012, 09:58:55 pm » |
|
Yeah. Calc PIDs are calculated, not read from the sensors. Did you send the techlog to support@palmerperformance.com? If not, please send one and reference this thread. We'll take a look at it. Thanks. |
|
|
|
|
Logged
|
|
|
|
|
Sashik259
|
|
« Reply #6 on: January 14, 2012, 10:02:39 pm » |
|
Yes, I did.
BTW, only one PID named SAE.DTC_CNT tells me that 0 DTC stored in memory (It's truth)
|
|
|
|
|
Logged
|
|
|
|
|
Sashik259
|
|
« Reply #7 on: January 17, 2012, 08:32:28 am » |
|
Hi.
Is there any solution?
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #8 on: January 17, 2012, 11:01:03 am » |
|
Hi. Our support team is looking at the techlog. There is some discussion as to what the problem is. I hope we will have an answer by the end of today or tomorrow.
Thanks.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #9 on: January 17, 2012, 06:22:30 pm » |
|
We did some testing on this today, and as far as we can tell the problem has to do with the OT-2 and your AUDI A6. We use a different, more advanced connection mode with the OT-2, than Logworks uses. Which is why Logworks works okay, but also cannot display as much data.
We're contacting the people at Innovate to work out the issue with them.
Hopefully we will have an answer for you soon, but I think this might take a long time.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #10 on: January 19, 2012, 05:40:20 pm » |
|
We are able to reproduce the connecting issue in our lab, using the engine of a similar vehicle. The next step will be to figure out exactly what the issue is, then probably release a fix in DashCommand, or in the Innovate firmware. Depending on where the problem lies.
|
|
|
|
|
Logged
|
|
|
|
|
Sashik259
|
|
« Reply #11 on: January 20, 2012, 03:50:12 am » |
|
Thank you for your kind thought of my problem, and I hope it will be not a long wait.
|
|
|
|
|
Logged
|
|
|
|
|
Sashik259
|
|
« Reply #12 on: January 20, 2012, 04:46:18 am » |
|
I did some tests with mercedes E-class model year 2011 with 271-EVO engine. I've got the same connection problem several times (Error detecting OBD-II protocol). But since the connection have been established - the next connections are established without any failures...
|
|
|
|
|
Logged
|
|
|
|
|
Weston@PPE
|
|
« Reply #13 on: January 20, 2012, 08:39:50 am » |
|
This problem with the OT-2 seems to be the worst on vehicles that use the ISO protocol. What model year is your Audi? If its older than 2008, it will likely use ISO -- where the new Mercedes probably uses CAN.
|
|
|
|
|
Logged
|
|
|
|
|
Sashik259
|
|
« Reply #14 on: January 20, 2012, 08:47:15 am » |
|
So your advice is to change my OT-2 adapter to another one, for example GL1 Diagnostic Cable by "GoPoint Technology" will work fine I suppose?
|
|
|
|
|
Logged
|
|
|
|
|
