It will work with AEM files, just need to convert the TIME data from milliseconds to seconds before loading it into VDR. I am working on adding a "File Type" Dropdown list for Evoscan,AEM EMS and DSMlink. For now, you'll just copy/paste your RPM and TIME columns in VDR and it does the conversion but I'm desperately trying to find a way to just select the file name and it extracts the data automatically so no one will need to do the CUT/PASTE step anymore. Workin' on that part though

 

jamie.... u will need to put say a button and write some vba code to do the loading of the file. btw i am happy to test if u need more ppl to test

 

Good deal, i was aware that it will currently work, just takes some finnageling(sp?)

I spent about 2 hours last night bored at work reading through this entire thread

 

Yeah, I wish I actually took a class on excel or something lol. Was quickly browsing the help section and it said something about pivot tables that might be what will work but i gotta do some googling now that I am home. Asl long as any excel version from 2000+ can use the features, I'm cool with doing whatever I can. Even if 2003+ is all I can manage.

 

myforumname .at. gmail ,dot, c!o!m ;P

 

*looks for his trusty decoder ring*

 

^^ he is making it harder isint he

jack depends on how much work u want to do. i think easiest would be to leave it like that. cuz otherwise u gota think about what if there are two or more full throttle areas in the file. if the file has different names for rpm and times... i am sure users can change the colum name and position in evoscan etc.

pivot tables i dont think will do.... but i never really used pivot tables. i thought hey are used to display extra info (like 3rd diamention) from say a row and column.

 

Yeah, for now I think its easiest to set it up for the user to paste their data in it. It makes it a bit more universal that way.

Question for you and Brad, how are you guys setting up your smoothing? Averaging a few lines before/after each data point? I havent been happy with my crude smoothing and would love to see how you guys are approaching it.

 

as i said before i dont understand the whole theory.. .so i am using ur smoothing aproach... mrfred had a different way to do it though... i suppose my idea was to get it (hp/tq) similar to ur output (hp/tq)

so i get the base smooth rpm/torque or hp then loop x ammount of times to smooth it further, it sometimes causes some artifacts.

 

Yeah, the immense amount of averaging at the end of the pull causes anomalies that I am currently trying to fix so I can get rid of the 'RPM TRIM' feature entirely. I am googling about a =smooth() feature that I might be able to use. Here is the link. Try the QUICK START portion at the bottom.


Also look into LOESS Smoothing HERE. This might be better.










.

 

jamie make sure you workout what the installation is, for new installs. as i know that Office2007 doesnt like macros and even vba code due to security and will complain until user explicitly puts an exception... or the file is digitally signed.

 

jamie... now i know why u went to the 2nd link

 

lol, all of these smoothing methods aren't making me happy right now. The issue is with the variation in the length of data. That's why its so hard to get the smoothing to come out right at the end of the pull because some logs rev higher than others. I need to standardize the size of the averaging area so its always averaging JUST the amount of rows i need for that particular datalog. I think i can find a way for it to count the rows with data in them and only allow it to average up to the highest row#. Hmm, maybe using the AVERAGEIF function?

 

how is brad doing his smoothing.... for me i feel that havign more data elements makes it more smoother... except i get a lot of large hp points when startign the log then the drop off to "normal" hp/tq points and then maybe at the top end i might get artifacts.... but this is before having rpm up/down things.

 

I do my smoothing with a little butter knife. Having more data does help with smoothing. BUT the user doesnt have to worry about trimming in my program due to automatically using TPS to trim out the cruise and decel portions of the recorded run. The smoothing is just simple averaging.

Good lord tephra ... Ill see if I can send you an email if I can decrypt your coded transmission earlier ... may have to get the russians involved though.