Mellon Racing

iTrader: (38)

Brad it's working very good, nice work my friend.

tcomp that was the only oddity I saw in that particular log.

brad that issue is going to come up with 2byte and maybe 1byte rpm logging, would it make sense to filter out odd spikes that can't be real?

bbarnhill

iTrader: (1)

I dont have a way to logically determine if a spike is abnormal or not. Any ideas? 1.0.7 knocks at some of the humps ...

Boosted Tuning

iTrader: (12)

2byte rpm can have spikes just like 2byte load, but 1byte load and rpm rarely have spikes.

bbarnhill

iTrader: (1)

Im at a loss for how to trim spikes out. I dont know how to tell if they are real power gains or false. I know we can tell by looking at them but how can I convert that into logical statements? Hum ... the delimia

Boosted Tuning

iTrader: (12)

I always use regular 1byte RPM (you only need 2byte if you rev over 796X) and I never every have any rpm spikes.

So I wouldnt be that worried. V7 beta 4 is working great IMHO.

Mellon Racing

iTrader: (38)

I rev to 9-9500 and a few of my customers do as well with larger turbo and built motors, but I agree this minor issue isn't a show stopper. Just something I noticed

bbarnhill

iTrader: (1)

I dont know what to do about the two byte rpm problem. Any ideas? Anyone thinj we should get with hamish and see what we can do? Or
is this something that is an ecu issue? Where is the proper place to fix it as i dont mind working with whoever as long as we dont patch this up. Lets hit it at the source.

l2r99gst

iTrader: (2)

It's a logging speed issue. There's not much that you can do about it while logging MUT. 2 byte RPM will have spikes anytime the first byte and second byte aren't in the same 'step' so to speak.

Logically, you may be able to write code to look at RPM dips or raises in the range of the step value (which will be 1000RPM) and it will always happen on multiples of 1000RPM.

Boosted Tuning

iTrader: (12)

Eric, do you think theres any way to change 2byte RPM into a "1byte RPM" like we did with load?

l2r99gst

iTrader: (2)

That has to be coded into the ROM. Tephra did that for 1 byte load.

Boosted Tuning

iTrader: (12)

Yeah, I know it has to be modded into the ROM. But it could be done right?

l2r99gst

iTrader: (2)

Sure.

Mellon Racing

iTrader: (38)

version 1.7 is up! as always, uninstall the old before installing the new
http://www.mellontuning.com/index.ph...dex&cPath=1_28

1.0.7 (October 26, 2010)
- Fixed a bug that would cause some resizing issues and save the wrong size and locations
- Fixed a bug that would not properly read CSV files with commas in the data or data was enclosed in quotes
- Fixed flickering on smoothing level selection
- Added RomRaider AEM UEGO support
- Added 2000-2009 Honda S2000 (6 speed) support
- Added Engine Load as a boost column for AEM logs
- Added print dialog to select printer to print to when the print button is clicked
- Added Hydra EMS log support
- Added GReddy EManage log support
- Added HHH log support
- Corrected Evo X incorrect weights corrected
- Corrected 07 STI Rear drive from 3.545 -> 3.900
- Corrected 02-05 WRX Wagon drag coefficient 0.35 -> 0.33
- Moved profiles to menu dropdown selection
- Increased graphable runs to 6
- Active profile is displayed on the bottom status bar
- If more runs are listed than can be displayed the side bar is now scrollable
- Profiles moved to the menu at the top of program
- TPS trimming is done automatically and no longer requires a setting
- Seperate HP/kW and lbft/Nm settings so any combination can be used
- Double buffering enabled to cut down on flicker when drawing graphs
- Show run level messages out beside the run control
- Enhanced error messages (E101-E102) to show file names causing errors
- Mustang Dyno correction factor changed to 0.95 to better match average MD
- Software version number printed on graph
- Using InstallShield now to install
- Code cleanup and unused code removed
- Performance analysis done to find bottlenecks

leecavturbo

do you have to trim out the non 100% tps data?
anyone got an example datalog i can look at?

bbarnhill

iTrader: (1)

no you dont have to trim out the less than 100% TPS. TPS trimming is automatic now. Just please spare me the hassle of trying to graph a part throttle run. I assume you are smart enough to use a WOT run I cant handle that part in the code, atleast not with this algorithm.