|
Mark Kline
|
 |
« on: January 24, 2012, 06:07:19 pm » |
|
works great on go point ,i down loaded dash comand . but it wont work on my 2005 nissan titan. check it on newer nissan and it work. also works well newer cars and truck like ford and chevy. So what am i doing wrong or is my truck to old
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #1 on: January 25, 2012, 10:54:51 am » |
|
What problem are you seeing exactly?
|
|
|
|
|
Logged
|
|
|
|
|
Mark Kline
|
|
« Reply #2 on: January 25, 2012, 12:49:17 pm » |
|
it reads vin an light green but no gauges work...like i say it works on regular go point app , but wont work on dash command app. do i need differrent pids
|
|
|
|
|
Logged
|
|
|
|
|
|
|
Mark Kline
|
|
« Reply #4 on: January 25, 2012, 01:49:34 pm » |
|
if it auto connects and light turns green but all gauges read N/A , even tach and speed.If all that works on the go point app why would it not auto read on dashcommand.....auto connect is on...... OB2 interface type is on Go Point tech.....ob2 data iport is on auto....aux input none......pid i left alone .....im using an i pone with an gl1 plug. but i will doudle check it again. I used the dash command on other cars like my girlfriend 2010 truck , and everthing gauge works perfect. But nothing for 2005 my 2005 nissan titan
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #5 on: January 25, 2012, 02:15:13 pm » |
|
Mark, there is some relevant information in the troubleshooting guide. I will post it here: What if you’re missing a value that isn’t calculated, like RPM or vehicle speed? This is usually not an issue unless you are using a GoPoint GL1 (iPhone only) with an older vehicle. The GL1 is constantly requesting engine RPM from the vehicle, and in some cases it delays the vehicle’s response to DashCommand long enough for DashCommand to think that a PID isn’t supported. To fix this, (before you connect) go to the go to the vehicle settings for your car. Decrease the ISO/KWP Keep Alive Interval slightly, around 2000 would be good. And increase the OBD-II Timeout to 400. Then go connect to the vehicle. After you’ve connected, press the Validate PIDs button near the bottom of the vehicle settings. |
|
|
|
« Last Edit: January 25, 2012, 02:15:55 pm by Weston@PPE »
|
Logged
|
|
|
|
|
Weston@PPE
|
|
« Reply #6 on: January 25, 2012, 02:17:21 pm » |
|
As a side note, we have added some new things to DashCommand that will automatically fix these settings (only for the GL1) for you in the next version. You should see the next update within a week or so.
|
|
|
|
|
Logged
|
|
|
|
|
Mark Kline
|
|
« Reply #7 on: January 25, 2012, 02:29:59 pm » |
|
Thanks for ur help , i will try thes things and let yall know if i can get it to work  |
|
|
|
|
Logged
|
|
|
|
|
Mark Kline
|
|
« Reply #8 on: January 26, 2012, 06:13:39 pm » |
|
Ok i set the iso/kwp to 2000 and the ob2 time out to 400, press the valdate pids button and that seem to work alot better...but some gauges still not workin like temp, load ,fuel. what i did notice when i look at my pids only the MAF has the SAE in bold letter.The Map and Lambda's both dont have any bold words in them. So does that mean ther not reading pids corectly or not at all. i filled in ever blank in specifications and thers bold words in all catergories except map and lambda (actual pid) and (command pid) thanks for ur help.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #9 on: January 26, 2012, 06:26:29 pm » |
|
The bold lettering doesn't mean anything.
Not all vehicles will have all PIDs available over OBD-II. In the Select PIDs screen, the supported PIDs for your vehicle will have a green checkmark. The unsupported PIDs have a red X.
|
|
|
|
|
Logged
|
|
|
|
|
Mark Kline
|
|
« Reply #10 on: January 26, 2012, 07:17:56 pm » |
|
yes i do see that......and i do have a green check mark on a few gauges like FRP that are not working....when i add that to my pid list , it just makes other gauges stop working like my fuel trim gauge and the FRP doesnt work neither. Thanks for the info and ill try some more settings on it tonite and see what happens.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #11 on: January 27, 2012, 09:40:17 am » |
|
Selecting a PID shouldn't affect the Dashboard gauges. I don't understand why FRP would cause fuel trim to stop working.
Can you please explain exactly what you were doing?
|
|
|
|
|
Logged
|
|
|
|
|
Mark Kline
|
|
« Reply #12 on: January 27, 2012, 12:59:41 pm » |
|
well like for instint when i add pids to my list like a lambda it make other gauges stop working, its like they dont match ther catergories. Like my coolant gauge wont work unless i put a fuel pid in ther. And when you add a coolant pid to it, its work sumthing other than coolant gauge... if i delete Calc.fuel_consumption from pid my coolant gauge stops working and reads N/A..its like a guessing game ....sorry to confuse u i think i confused now  |
|
|
|
|
Logged
|
|
|
|
|
Mark Kline
|
|
« Reply #13 on: January 27, 2012, 01:06:17 pm » |
|
There only 6 pid in my list . (sae.rpm) (sae.vss) (calc.trip) (sae.heat_sup) (const. lambda_actually) and like i saying (calc.Fuel_consumptiom) witch no fuel gauges work but if i delete from pid my coolant gauge stop working
|
|
|
|
|
Logged
|
|
|
|
|
|
|
