Davefocus

IIRC Dashcommand doesn't handle the scripts (yet!) and PCMScan does.

Dave

__________________

MP3Car.com

 

thunderfox5

Awesome graphics! Is it possible I can have them?

TonyWare

Something interesting is going on. While the Engine Load is correctly displayed using the Centrafuse OBDII, it doesn't show when using DashCommand Lite (the $10 software deal from mp3car.com). Pics below. I am gessing that for other values, such as air flow, I have different "PIDs", so both software packages can't read it. But I can't understand why one software reads the Engine Load and the other doesn't. Any ideas?





Thats from my 03 v6 Accord (j30a4 engine) that have recently re-purchased... long story (sold it to a guy, he gets deployed to Afganistan, sold it back to me - lol)

PS. Forgive me if I missed anything in a 17 page thread that perhaps gives me the answer.

PPE

There are a couple different parameters that report engine load. I think that the dashboard layout you are using with DashCommand Lite has been designed to use one of the load PIDs that is not supported by your vehicle and Centrafuse is using a different load PID that is supported.

It's really easy to fix though, just open the dashboard in the DashXL editor and find the object for the load gauge. Then switch the OBD-II PID to the other one for load. These are the two possible load PIDs:

SAE.LOAD_ABS
SAE.LOAD_PCT

That should fix it!

__________________
Brian @ Palmer Performance Engineering, Inc.
http://www.palmerperformance.com

TonyWare

Yep! There are a few of these PIDs that need to change. The "%" right above the "0" says SAE.RPM. That doesn't sound right either? With google as my best friend (lol) I am going hunting for PID values. Thanks for the hint, nice new toy you got me to play with over here

deanb2

SAE.RPM is the default value that gets filled in the ODB-II PID field.

'Use ODB-II Value' has to be checked just above that for it to use the ODB-II value, otherwise it uses what ever is in the Format String property - In your example that would be %. All the other text fields should look similar, with SAE.RPM in the PID field, but the 'Use ODB-II Value' field unchecked.

Dean

nemo1

Hi, I tried to use the gtr gauges in dashcommand but it doesn't work. Only the RPM works. I read this thread so in pcmscan -> PID config I validate PIDs and a list of PID appear. I checked the script editor i.e the SCRIPT.GEAR and it seems to need SAE.VSS .RPM and .TP to work. When I validate the PIDs the 3 mentioned PIDs appears but I am still not able to get the gear. What I did is in Dashboards tab I clicked on DashXL, navigate to fuel, engine gear .dxl then press F2 for monitor but the gauges still don't work. Only the RPM works. When I validate the PIDs I get a lock and tick (green colour) icon, can it be that I could not use the PIDs. I read that from the help files. Anyone can help out.

TIA

PPE

If you have not yet purchased the full version of DashCommand then you will only be able to see Engine RPM. To unlock the full functionality you will need to buy a license key.

__________________
Brian @ Palmer Performance Engineering, Inc.
http://www.palmerperformance.com

MP3Car.com

 

xsputnikx

ive read through a lot of post on this thread and I wanted to ask is there any software that you guys know of that will work like this for 0bd1

TonyWare

I noticed that the GTR gauges by asmpbm are .dxl files but the demo version of DashCommand only opens .dxls files.

Question 1: Is it because it is just the demo version or the file formats have changed?

Question 2: With the new DashCommand, do I get scripts and the "1" to "G" buttons to show and work ?

Question 3: I think I read somewhere that I can import the entire .rar file (or zip was it?). Do I zip all these script and dxl files up and import or something?

I won't spend $ to by DashCommand if this doesn't work right or at least someone has some solution that works with these GTR gauges. The Lite version has been fun so far but time to move to something better.


Thanks.

deanb2

The .dxls file is a dash set. Download the skin editor, create a new set, click on Dashboard1, then on Edit Dashboard and the dash editor starts. Do a File -> Import From File and load the .dxl file. Save Dashboard, Exit, Save and you have a brand new .dxls file.


Load the scripts in Dashcommand with Settings -> Scripts
The buttons will work if they are programmed to work. Download the examples on dashxl.net to see what has already been done.


Not sure about that. I have only seen a single .dxl file import.


I attached my quick import of the GTR gauges into a .dxls. In Dashcommand, go to Settings -> DashXL to load a skin set. I added the next/prev buttons and Objects needed from another dashboard on dashxl.net.


You're welcome.

Dean

Attached Files

	GTR Gauges.zip (345.0 KB, 23 views)

TonyWare

Thanks Dean! Much appreciated. Now I have way more info that before. I guess I'll have to move the buttons on top, somehow, but so far so good. Thanks again!

MP3Car.com