Well I got a new tune from Intertia Motorsports and we had a cool front come in last night that dropped the temps down to 70 degrees and the DA was only about +300 or so. I know the dashawk is not 100% accurate so what I am looking for are those who have backed up their track times with the dashawk to give me some idea with decent DA and weather what I might be running now with the new tune. I did 2 back to back runs to be sure and video taped my run as well so here you go guys. 1st run: 2nd run: No waiting after 1st run Video of first run: What I noticed on Friday watching the video of me running the TBSS that after 80mph I actually started to close the gap a little look at the vid from 85-100 it goes by fast to me
I usually run 2/10ths slower at the track. Both times I've tested this were in similar conditions, although on different days.
That sounds right when I correct for DA and conditions from my 13.12 pass on Saturday it puts the corrected times at 12.78 I'll take that anyday for the mods that I have
This is my latest Dashhawk screen capture but the conditions were very cold and slippery at the track which had no prep so I couldn't beat a 13 flat, but it was at 111+. I was hoping to run a 12.6999999 lol..
Last summer I made a few passes at the Dragstrip comparing actual timeslips to the Dashhawk. Everytime the Dashhawk has shown better number than reality. .2sec better in the 1/8 mile and at least .3 better in the 1/4 mile, but 1.5 mph slower than actual, just as if would stop counting a bit before the finish line. On one typical run the timeslip says [email protected] with 1/8 at 7.96 and 60' at 1.759. Dashhawk showed [email protected] with 1/8 at [email protected] and 60' at [email protected]. Claude
Couldn't we calibrate somehow to match more closely? Never tried. I do notice my 0-60 times go to 60.2mph.
Dashhawk always clocks at 60.2 mph but I've seen some at 60.9. I think it's pretty good at measuring speed according to the PCM's data but when measuring distance it probably takes wheelspin as distance travelled and so it cuts it short at the end of 1320 ft. Just my toughts from what I've noticed, no scientific data here. Claude
[dammit, reply got bit bucketed again... here it is again] The time is corrected to 60.0 mph. This is because of the sample rate. They can't poll the PCM continuously (they're polling for rpm and speed on zero-sixty runs) or it would swamp the PCM and/or the bus. So there is a fixed sample rate. I knew what the sample rate was once but I forgot. It's in the milliseconds. So they sample until they get a speed of 60 mph or above. Now they have the last two samples with one being below 60 mph and one being above. They know the time at each sample and the speed at each sample so they can calculate the time back to 60.0 mph. They do this. Why they chose to display the mph of the last sample I don't know. By the way, you can open the .z60 (or .qtr) files with exel or notepad and see the samples. All the performance and data logs have 3 files (each with a different extension). File for the samples, file for the display parameters? and a file for something else.
That's correct. The DashHawk has no knowledge of wheel spin and counts it as distance traveled. There are some other small differences from the track. (remember all the DashHawk stuff is corrected for between samples). - The DashHawk starts the run instantly on movement. Tracks have a rollout of 8" to 12"? So at the track you get a tiny running start. You might expect your Dashawk 60' times to be a bit slower. - The DashHawk "traps" mph at the very end when you've traveled the exact distance. Tracks average your mph over the last 100'? You might expect your DashHawk mph to be a bit higher. - The DashHawk does not know about wheel spin. It will calculate distance traveled exactly like your odometer does. 1/4 mile runs are distance based so wheel spin will have an effect - the dashawk thinks you've gone 1/4 mile when you're not quite there yet. 0-60 runs are mph based so wheel spin doesn't effect those. As long as you're hooked up when you cross 60 mph they're going to be accurate.
By the way Milan, you can select 2 different PIDs to log during quarter mile runs instead of your narrowband O2 sensors. Logging your narrowband O2 sensors in the quarter mile is not interesting. In WOT mode it's open loop and there is fuel being added. The narrowbands will be pegged rich. You can change those 2 PIDs to something more interesting like Spark Advance and Knock Retard :grin:
Oh crap...there's a version 2.4? Is that firmware also? The last time I updated to V2.3 was kind of a nightmare. Very unclear. I may try it on the DH itself.
Both. http://www.msdignition.com/forum/forumdisplay.php?f=24 Looks like they're up to 2.5 Beta right now.
