Hmm, that's feasible I think. If it isn't a PITA to keep, I'll try to. These revisions will require a significant amount of editing so it won't be anything immediate. I just want to minimize the amount of tabs that people need to sift through in order to enter all of their data. Plus I want to add a tab with the average curb weights of most of the vehicles I will have preset in the dropdown list.

 

Ok, thanks guys. I'll create a separate tab for Weather Correction Sure seems like you got some knock that pulled some timing at peak torque on that hot day!


REVISED LIST:

File Type: (Dropdown List)
Evoscan Datalog
DSMlink Datalog
AEM Datalog (working on it)

Unit of Measure: (Dropdown List)
Imperial
Metric

Vehicle: (Dropdown List)
All Vehicles listed on the 'Vehicle List' page

Gear Selection: (Dropdown List)
3rd Gear
4th Gear

Actual Vehicle Weight: (Manually Entered by User)


Total Occupants Weight: (Manually Entered by User)


Tire Diameter: (Manually Entered by User)


Dyno Type: (Dropdown List)
Any Dyno Type that will be listed on the 'Dyno Corrections' page

Current Correction Factor:
Just Displays the Dyno Correction Factor currently being used

Max RPM Trim: (Dropdown List)
From 6.5k RPM to whatever the highest RPM that was recorded in your datalog (50 RPM increments)

Smoothing Factor: (Dropdown List)
1 to 29 (Increments of 1)

I will move the 'USER Description' part from the 'USER SETTINGS' page to the 'DATA ENTRY' page.

The new list of Tabs on the bottom will be:

DATA ENTRY
DYNO GRAPH
TIRE SIZE CALCULATOR
WEATHER CORRECTION
VEHICLE LIST
DYNO CORRECTIONS
DIRECTIONS
DONATION

I tried to setup the tabs in the order of importance and the ones most frequently used. If anyone would prefer a different order, tell me your suggestions. Thanks guys!

 

I'd REALLY love a way to add a button that could take a snapshot of ONLY the dynograph so users could easily save a snapshot of their results for uploading. If there is someone ambitious enough to see if that's even possible with excel, let me know!

 

? he and I have been comparing notes on these for quite some time, In fact he's the one that told me about it.

I don't have it installed on this computer, but basically you zoom in on your WOT portion of the pull, go to file -> export as text -> pick "engine speed" and make sure to only use the "current selection" IIRC. It'll pop it out into a tab delimited .txt file. You just open it up, clip off any extraneous RPM in case you picked too much, ctr-A, open the VDR, pick the first two columns, ctrl V.
BAM, Herpes.

 

I use the Weather Correction Section as well, as temps here jump up and down rather quickly.

 

Oh cool, I guess he never told me he figured out how to do it. He was manually entering in the data for every 100 RPM or so when he first started using it. If it needs to be converted into a text file to open in excel, I won't need to make a dropdown list item for it. I will just have the evoscan and DSMlink items and AEM users will just use the evoscan selection. Herpes, the gift that keeps on giving

Yeah, weather correction will stay intact, just on a separate tab. I just never saw anyone have it enabled when they posted pics really (probably cuz it generally lowers your #'s for most people since baro is higher than 29.235 in most area's). I want to get more data regarding the weather corrections used by the dyno's and make sure we're doing it right.

 

here is what i got. note mellon's dll figures in my sig from the exact pull. car weight i believe is correct. i am '6' 3" 210

 

Yea I'm having some trouble with knock especially at peak torque. Your program has been a big help in showing exactly what effect it has on power output.

Thanks,

Dan (drb)

 

Nice torque. What's the comparison run, previous tune?

 

The left is simulating a Dynojets results, while the comparison pull is his Evo-M Comparator #'s. THe Evo-M Comparator is roughly halfway between a Dynojet and a Mustang dyno and is used so Evo-M users can compare their cars equally.

 

thanks, correct the comparison run is the exact same log but with evom setting as opposed to dynojet setting

 

i also use weather correction throughout the day for temp and barometric pressure... please leave these in.

thanks

 

Well whoflungpoo is the one that showed me how to do it actually... hes pretty smart with a PC im just a tuner But we ran into a problem... My computer works fast and picks up A LOT of data... Before i was manually entering it by .1 seconds of data and it was VERY accurate and didn't require much smoothing. Well when we did it how whoflungpoo stated on my AEM logs it went crazy and i had to use 29 "max" smoothing to make a somewhat smooth graph and it all went funky... I got a reading of 794WHP off a log that i got 766WHP from before when doing it by .1 second increments that i only had to use 12 smoothing to make nice and smooth. So yet another set back for us AEM users. But i can still use it i just have to enter in .1 seconds increments.... just takes A LOT longer haha

 

yeah, it's wierd, because mine seems to work rather well with ~ 12 smoothing just dumping like I always have been, but blevin's map went berserk.

The log output has increments of .02 seconds. I've noticed some weird things about AEM's logging. one is that the more data streams you monitor, the less sampling resolution you seem to get, and two, it's not always consistent, I'll have some instances of nice linear increments of RPM vs time, and randomly it will show the same RPM for a tenth of a second.

I think this is more of an AEM problem than a VDR issue. I don't know how much trouble it would be, but maybe for an AEM input option it may be beneficial to just have VDR sample every .1 second, basically disregarding the other and reducing chances of sampling errors effecting the vdr.

I hope that made sense, I'm on zero sleep and several beers

ps: You got email coming to ya, should be from justinhardyharhar at gmail dot com

 

The smoothing value will change drastically depending on how large your datalog is. With both Evoscan and AEM, you'll log less lines per second as you datalog more items on the list. To make the AEM file smaller, just log more items. The simulator can handle up to 2000 lines so as long as your datalog file is less than that, you're good The more lines per second, the more accurate it is.