Sign up for our newsletter! 
Home News Products Downloads Forum Distributors Store Contact Us
PPE User Forum
January 19, 2018, 06:16:43 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Dash command v2.6.0 for iphone and Subaru  (Read 8572 times)
0 Members and 1 Guest are viewing this topic.
betch
Newbie
*
Offline Offline

Posts: 10


View Profile
« on: September 24, 2010, 09:33:15 am »

 I have loaded the latest mpgLINK from the itunes store and upgraded my GOLink firmware as was suggested.
Still cannot get any data in dash command on my 2003 Subaru Outback.
Works fine on the 2002 Chevy Suburban and a 2000 Chrysler 300M.

The goLINK software and mpg Link software works just fine.

What gives here?
I paid good hard earned money for Dashcommand!
I expect it to work as advertised with the goLink interface.

Please Help!
WHAT'S THE NEXT STEP?
« Last Edit: September 24, 2010, 09:35:12 am by betch » Logged
BMCJunkie
Newbie
*
Offline Offline

Posts: 15


View Profile
« Reply #1 on: September 27, 2010, 04:15:45 pm »

Hi Weston,

same issue as betch.  Nothing has changed for me.  I have the new goLink firmware loaded, new dash command 2.6.0, new iOS 4.1 (as of today) and still at the most can only get intake temp and MAF... I had MAP at least once before I reloaded everything from scratch, which was this morning.  Attached is the log from a clean install.  Two attempts are logged... 1) brand new vehicle added, debug enabled, connection attempt, dashboard loaded, disconnect. 2)re-connect, dashboard loaded.

Not sure why ISO KWP is not working.  If you remember, all my gauges used to work under 2.5.0... however it took me several times to connect, which has been fixed BTW with new goLink firmware update.  It seemed that Dash Command is broken and has remained broken since the first time I used it to check the CEL.

Could the CEL reset have damaged my ECU or the cable somehow?  Should I try and get another cable from Brennan?

Please help, I would really like to get this working after 3 months of it not working.

Thanks,
Edgar

* techlog.tr (103.69 KB - downloaded 136 times.)
Logged
betch
Newbie
*
Offline Offline

Posts: 10


View Profile
« Reply #2 on: October 11, 2010, 08:14:48 am »

Back to the Top!
Still not working with the 2003 Subaru Outback.
Now Dash Comand will not connect to mu 2002 Suburband either?HuhHuhHuhHuhHuhHuh?
Golink and mpglink both work with both vehicles.
Seems to be a Dash Command problem!!!!!!!!!!!!!!!!!!!!!!!!!!

What am I to do?HuhHuhHuh?
Logged
Weston@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: 2234


View Profile
« Reply #3 on: October 11, 2010, 04:23:44 pm »

betch,

You say DashCommand stopped working with your Suburban? Did this stop when you updated DashCommand or when you updated the goLink firmware?
Logged
betch
Newbie
*
Offline Offline

Posts: 10


View Profile
« Reply #4 on: October 11, 2010, 06:18:26 pm »

Dashcommand worked with the Subaru when I first launched it. Also worked with the Suburban. I think my problems started when I shut off the Subaru without shutting off dashcommand first.  Dashcommand hasn't worked with either vehicle since!
Logged
betch
Newbie
*
Offline Offline

Posts: 10


View Profile
« Reply #5 on: October 11, 2010, 07:00:05 pm »

Sooooo... Sorry for the harassment!
I'm so stupid.  I had the wrong interface selected in the settings.
A users manual would help avoid dumb errors like mine!
Logged
Weston@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: 2234


View Profile
« Reply #6 on: October 12, 2010, 04:24:10 pm »

Responded to your other post:
http://www.palmerperformance.com/forum/index.php?topic=2732.msg8922#msg8922
Logged
BMCJunkie
Newbie
*
Offline Offline

Posts: 15


View Profile
« Reply #7 on: October 13, 2010, 07:22:45 am »

Hey Weston,

any luck with my issue?  Was the techlog that I posted any help?  For giggles, I hooked up my friend's 2005 Outback and DC worked like a charm.  Then I connected my goLink cable back to my 2004 WRX using his Outback profile and it works fine!

What's the deal?  Can DC not talk properly to the goLink when initializing the profile for a KWP2000 vehicle? or maybe it's the other way around.  For now I have a temporary workaround, but I would like to get this working properly.

Would a new techlog with my car using the Outback profile help?

Thanks,
Edgar
Logged
Weston@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: 2234


View Profile
« Reply #8 on: October 13, 2010, 12:06:01 pm »

It sounds like just creating a new vehicle for your WRX would fix it. The Vehicle Manager saves a lot of things like which protocol the vehicle connected on and which PIDs were supported, it may have saved some protocol information from back when the goLink had problems with ISO.

Try creating a new vehicle and let us know how it goes.
Logged
Gaitskell
Newbie
*
Offline Offline

Posts: 3


View Profile
« Reply #9 on: October 18, 2010, 09:09:06 pm »

I have a Subaru Impreza Outback Sport 1999. I had problems getting a anything but rev counter to connect, following a fresh install. The VIN in the profile created for car will not fill in.

I can read many more parameters from Subaru , if I set up a profile with another car and then connect to Subaru.

A fresh install of app allows me to connect to Jeep without any problems

Other OBD GoLink apps work fine with Subaru.

Should I submit a problem log to help with diagnosis of problem with Subarus?

Rick
Logged
betch
Newbie
*
Offline Offline

Posts: 10


View Profile
« Reply #10 on: October 19, 2010, 06:27:49 am »

Gaitskell,

I am having much the same problem with my Subaru.
Dashcommand seems to work just fine when connected to the Subaru using the Chevy Suburban Vehicle set-up.
When I validate the PIDS while connected to the Subaru using the Subaru Vehicle set-up things like RPM, Speed, Engine Temp and the MPG Screen do not work.
I tried validating the PIDS while connected to the Subaru and running the Chevy Suburban Vehicle Connections.  Lo and Behold after Validating the PIS the Suburban Vehicle
stopped responding and acted just like the Subaru Vehicle when connected to the Subaru?

Sounds confusing???

As soon as I get some free time, I'll set up a new vehicle and connect to the Suburban, make a log, then connect to the Subaru using the Suburban Vehicle, make a log, Make a New Subaru vehicle, Make  Log then validate PIDS on the subaru using each profile, Make logs.

I think there is a problem after validating the PIDS while connected to the Subaru.

Will probably be later in the week till I can have time to experiment.

I'll send Weston the logs as soon as I can get to it!

Steve Boettger
Logged
Weston@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: 2234


View Profile
« Reply #11 on: October 19, 2010, 12:32:00 pm »

Yes, please get us tech logs of this! Be sure to enable debugging in the Console before you connect or validate PIDs.

I'm not aware of anything that would cause this. Are all 3 of you using the goLink?
Logged
Gaitskell
Newbie
*
Offline Offline

Posts: 3


View Profile
« Reply #12 on: October 19, 2010, 12:41:38 pm »

 I have emailed my log to support@ address.
Rick
 
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.13 | SMF © 2006-2011, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.101 seconds with 20 queries.
Home | News | Products | Downloads | Forum | Distributors | Store | Contact Us
Copyright © 2013 Palmer Performance Engineering, Inc. All Rights Reserved.