Yeah ... its getting better Im adding some new features as we speak. I also am talking to my software engineering buddy and coming up with some new ideas. The beta has some bugs or Id release a beta for ya. Ill have a functional beta in a day or two. Patience child ... patience.

 

So far here are the changes in 1.0.5:
- Settings are now not saved on graph settings window close via the X
- Fixed a bug when renaming logs that caused a fatal error
- Fixed a bug that caused the FindRPMRange to return no range due to blank RPM columns
- Fixed a bug that would cause the TPS to be found and not trim blank columns
- Added adjustable Auto Trim TPS value to the settings screen
- Added cancel zoom button to the quick action bar
- Load runs even if file is already open in another program (non-exclusive file access)
- Increased the sensitivity of smoothing
- Boost graphing on Y2 axis of bottom graph
- FindColumnName function added to remove redundant code
- Finding of column names moved outside each row so its only performed once per table hence improving graphing time
- Added Evo 5 GSR (5 Speed)
- Graphing can be done in metric or imperial units now (HP/ft-lbs or kW/N m)
- Splash screen background set to transparent
- Dynamically scaling of AFR and Boost graphs

Figured Id keep you aware of the changes made so far. Betas have their copies and as soon as I hear from them ... you know what time it is ... RELEASE TIME!!!

 

Brad,

Looks good. I am looking forward to the release.

We going to easily be able to add cars to the list and save changed to them? I been tuning Supra's fairly often and use the program for that a lot.

I know I can edit cars.xml which I have done but just checking.

 

I took a quick look at the 1.5 beta that you have on your site today (not sure if that's the latest version) and the only comment I have is to add a little buffer to the upper end of the boost scaling.

I loaded a run into it and the graph exactly scales to my highest boost spike, and zedgraph doesn't list the value on the scale axis. Maybe add 1-2 psi over the highest boost reading for the highest scale marker so that the highest boost is readable by giving zedgraph a chance to get in another value on the axis?

 

It should buffer the boost graph but ill check that.

 

Im going to work on saved car profiles this week on vacation. No updates this week but maybe that will let me hammer this feature out. Let me know if you have any issues.

 

Also, one last thing...again not sure if this is fixed in a more recent beta:

I didn't have TPS in my log and it kept saying that all data was trimmed and to set the trimming in the settings. Even if I unchecked TPS trimming, it still errored out and never graphed my log. Only after adding a TPS column to the log, did it work without the error.

 

Yeah I noticed that too ... going to fix that.

 

one thing, can you make the make max hp & tq in larger print? Thanks

 

I think Im going to create a Legend control that I can customize how I see fit. The legend right now is included in the graphing library. It will be after I get the profiles added as I feel that is a bigger priority, but its definately already on my 'to do' list.

I am getting this done as quickly as possible but it just takes time to get things written and then to the beta and tested. Rest assured that with me writing and Mellon, Jay, and others testing ... itll get done.

 

Am I doing something wrong or does this program just run incredibly slow? It's running 24% on a quad core but it is SLOW.

Also, I am getting a very rough chart even with the smoothing turned all the way up.

HP numbers are pretty close to VDR but the rough torque gives a lot of spikes that are about 10% higher then what the torque probably really is.

 

The higher you turn smoothing up the longer it will take to graph. Also the bigger the file the longer (which is understandable). How many rows are in your data file. Ive graphed a 5min log (which is looooong) that was 4500 lines long and it took 5-6 seconds to graph on my quad core. Now you know its not written to take advantage of multicore processors, right? (another thought ive had).

Let me know how many records are in your file for my knowledge.

 

I'm not sure if this has been suggested or not, or if it is changed...

What would be nice is most dynos read solid lines for a pull, dotted for the comparison. On this platform, its solid for HP and dashed for TQ. It gets confusing for those of us use to looking at dyno sheets, especially since there are 4 different colors for 2 comparisons.

 

nice program! i cant wait to be able to try this when i get back home.

 

You must be using an ooooold copy if its got 4 colors for two runs.

What should the 3rd and 4th look like? I wanted them to look uniform when comparing multiple runs. Get the new version and let me know if its any better and we will go from there ok? Do let me know though!!