Dashhawk needs your help!

I have an Omega Watch that has been broken for three years, I still love it, lol.

I'm with kingpin here. Just doing my research, how accurate are we talking. Is it pretty spot on? I'm not looking to spend to much more on my car (full exhaust, wheels, Forge or HKS), but if this thing is spot on, I may forgo one of those other goodies for this.


Its very spot on to the cars sensors !! MSD support is excelent. Read the thread lol

Right now we are able to read the Factory WB02 and boost in PSI and a ton more non popular off the DH and it has been tested against other aftermarket WB and is spot on. I have a AEM for my last car and it reads .001 difference. Boost is spot on with my prosport guage....DH refresh rate 28ms(very fast) MDS had a MS3 in there shop for a sensor dump on the 21st and picked up lots of Mazda specific sensors such as (knock INJ-pw boosted air temps and a lot more) Go over the the MDS board there is a MS3 thread quickly growing lots of info and all the data you want over there. KEN is there support guy and gives such great effort in ANY issues wit hthe DH in most cases there is updated for DH users 2-3 times a month adding more and more goodies.
 
Last edited:
how reliable/accurate is the dashhawk?

Like any OBD2 scan tool, the DH receives data from the ECU and scales it.

In the case of manufacturer specific data, the exact scaling may not be known in which case someone would have to make a guestimate.

Since the DH folks are asking for data logs, they obviously don't know the correct scaling for several parameters.
 
It does look like a nice unit and does pretty much what the DH does plus more. The only reasons I can see the DH coming out on top is cheaper price ($275 vs $375-425), bigger LCD, Color LCD, and the constant stream of firmware/software updates from Ken at MSD). Other than that it probably just comes down to personal preference.

I noticed the DH will log 6 channels for 3-5 minutes which is probably adequate for most applications, the Dashdyno will log 16 channels for 10-20 hours on a 128Mb SD card and it will take a 1Gb card. You can also connect directly to the OBD through the Dashdyno with a laptop for really big full color displays and practically unlimited storage.

Sorry for the hijack, back to your regularly scheduled thread.
-enganear
 
Like any OBD2 scan tool, the DH receives data from the ECU and scales it.

In the case of manufacturer specific data, the exact scaling may not be known in which case someone would have to make a guestimate.

Since the DH folks are asking for data logs, they obviously don't know the correct scaling for several parameters.

the data logs are for the NEW sensors that they picked up when one of the members went for a pid dump!!!!!!! NOT ITS CURRENT READING PID's
 
I noticed the DH will log 6 channels for 3-5 minutes which is probably adequate for most applications, the Dashdyno will log 16 channels for 10-20 hours on a 128Mb SD card and it will take a 1Gb card. You can also connect directly to the OBD through the Dashdyno with a laptop for really big full color displays and practically unlimited storage.

Sorry for the hijack, back to your regularly scheduled thread.
-enganear

Nice man looks like a great tool .......Im happy with my DH so i think ill keep it.
 
Originally Posted by matsuda
The ECU has no way to measure it. It is an inferred value.

Try this:

After normal driving, note the temperature reading before shutting off your car.
After shutting off your car, start it again a few seconds later and note the new temperature reading.

The DashHawk will give you the same reading as any other scan tool.

There's no pyrometer in the cat then? What is it inferring it from? Rear 02 sensor? I'll give your test a try. I assume its going to read a temp far below what it should be since the ECU reset but obviously the cat didn't cool down very much.

I just tried the test... My cat temp was at 900-1100, I shut her down, went inside real quick, came back out (about 2-3 mins), and started her back up and the temp indicated 800-900...

Seems like its monitoring it. I know hardware wise there is only a WB O2 pre-cat and a O2 post cat. I wonder if the O2 sensors have temp sensors also... Maybe thats why it cost $400 to replace the O2...?
(scratch)
 
its not monitoring it. Drive the car and get it up to 1200-1300 degrees, turn it off and turn the key to on right away, it will be somehwere in the 800's. Temps don't drop 400 degrees in 2 seconds
 
So is this reading inaccurate?

I would say so. I just did this test and yep it went from 1200F to 900F when I turned the key (didn't start the engine). And it just kinda stayed at 900F for a minute or two then started going up.

I don't put any faith in those readings at all. 1600F is way too hot anyways.
 
the data logs are for the NEW sensors that they picked up when one of the members went for a pid dump!!!!!!! NOT ITS CURRENT READING PID's

That is exactly what I was saying.

They don't know the correct scaling for manufacturer specific data so they are attempting to "guestimate" it by reading data logs.

The scaling for all standard OBD2 parameters are published as ISO and SAE standards. Of course the DH can read boost pressure and AFR correctly because manufacturer specific data is not used for these parameters.
 
That is exactly what I was saying.

They don't know the correct scaling for manufacturer specific data so they are attempting to "guestimate" it by reading data logs.

The scaling for all standard OBD2 parameters are published as ISO and SAE standards. Of course the DH can read boost pressure and AFR correctly because manufacturer specific data is not used for these parameters.


Ok!

I think its a little more then just "guestimate" IMO

No one is saying the DH cures cancer; Simply that its users can help the cause.
 
Last edited:
Update for all Dashhawk users!!!

Ken @MSD said:
Just a quick update folks ... we've been on the road the end of last week, but I did get a chance to play a little with the data while in the airport and such.

I think I have an idea for another "round" of scaling for the various Mazda stuff. Also, I think we see what's going on with the Mazda VIN logic and we'll have a fix for it.

In the meantime, here's the plan going forward...

We're going to try to "button up" v2.4 and move it into the production code download area. All the questionable Mazda values (and ones we are working on like the PW and MAF voltage stuff) will roll over into the next round of Beta releases (v2.5 Beta 1) and we'll keep plugging away.

The VVT stuff is really whacky, so we'll probably have some interesting things to try with it, which will take time.

Again, as mentioned above, we KNOW that some of this stuff is totally whacked (like the MAF voltage for example ... that is just debug numbers being passed up without any appropriate scaling). It'll take a while to figure out the encoding, scaling, and precision of each variable.

THANKS A MILLION! You guys are making this happen!
 
are there any kind of sensors for speed6 guys AWD?

Thans a good question ill ask over there.... Or dada can answer hes got a DH ??

Maybe a speed-6er can stop by MSD and have em take a look if its worth it?
 
Last edited:
You have to install the new version of the software v2.4beta9 IIRC. Then "upgrdade" your DH using the software. You should see the mazda specific stuff right after sensor PIDs.
 
Back