0.97 Released

[Kaas]

Phil. This is much better, very fast up start!

I have not tried the bluetooth yet, but here is a video with serial connection!
http://uk.youtube.com/watch?v=DrogbMtaDik

[shauer]

Phil,

I really like what you did for the accel wizard, are you working on anything similar for EAE? Having to edit at least 4 different curves in different dialogs is getting kind of old. Any chance an EAE wizard is in the works???

[LT401Vette]

I really like what you did for the accel wizard, are you working on anything similar for EAE? Having to edit at least 4 different curves in different dialogs is getting kind of old. Any chance an EAE wizard is in the works???

That can be done easy enough. the catch is that I would really prefer to just build it in the ini file for future flexibility. But that would mean I probably wouldn't be looking to go back and edit all the ini files back in time, just the more current and going forward.

[LT401Vette]

Phil,

I really like what you did for the accel wizard, are you working on anything similar for EAE? Having to edit at least 4 different curves in different dialogs is getting kind of old. Any chance an EAE wizard is in the works???

So tell me what you have in mind. What would be the most value add to you? Just to have the real-time graph with the Curve, or a consolidation of several curves with the graphs? It isn't much work to do... What firmware version do you need to supported?

[Gokart]

Phil,
where are all those ini files stored? I'd like to add some ini files for easy reference of TS.

[LT401Vette]

[install dir]/config/ecuDef

I believe it adds them when ever you browes to to select one somewhere else on your disk. I don't remember for sure though

[shauer]

So tell me what you have in mind. What would be the most value add to you? Just to have the real-time graph with the Curve, or a consolidation of several curves with the graphs? It isn't much work to do... What firmware version do you need to supported?

I just read your reply. I just got done getting another engine up and going with EAE today so I might have some ideas on this. Even having just the Added to walls and sucked from walls graphs and RPM correction (4 graphs total) all shown and editable at once would be a big improvement.

It would also be nice to be able to view a log file with all 4 graphs displaying the active areas on each graph as the log file cursor is moved, similar to the VE, ignition, and AFR tables in Megalogviewer. I personally don't use the coolant correction curves much so those 2 would be the lowest priority to display with the others.

A real-time display with the same 4 graphs (added to walls, sucked from walls, added RPM correction, sucked rpm correction) in the tuning area would be nice but the number of traces needed to view in real time would be high (RPM, TPS, MAP, AFR, EAE%) I use all 5 of those as a minimum in Megalogviewer to dial in EAE. I'm not sure about screen space for 4 editable graphs and a real time view of at least 5 signals.

As more myself, I'm running 2.00 or 2.01 firmware. Would it be unreasonable to require MS2-extra version 2.00 or higher for the wizard to work?

These ideas are just off the top of my head, let me think about this some more and maybe some discussion and input from others who are tuning EAE will help as well.

[LT401Vette]

That does sound like it would work pretty nice, the one problem is what you pointed out, it would be big!
You can make the Curve graphs pretty small on the AE wizard with them only being 4x4 arrays, but these 4 are 12x12's.

Now I see a couple ways to address this, You couple break that into 2 screens considering if you have the screen space, TunerStudio lets you open multiple windows at the same time anyway. So say you put both RPM's in one dialog and both kpa in the other, or sucked in one, adhere in the other....

Another possibility, but this would be a more work, is if I made the curve graph support multiple lines on a single graph. Then we could put both RPM curves on one, and both Walls curves on the other, that would bring it down to 2 graphs and all 4 curves showing.

I need to make that current value do a bit better job placing itself too, it currently covers some values sometimes.

5 signals on the graph widget isn't a problem, it will grow taller with each new line to fit the values, but they could get hard to track all on the same widget, it might be easier with 2 graphs. With the width of this I can easily put 2 side by side.

So all of it is just ini work and improving some ini interpretation except the 2 curves on 1 graph, that will take some widget modification.

I'm sure James and Ken would most likely be fine with rolling the ini changes into their builds going forward as long as it doesn't hurt MegaTune compatibility, and it won't. MegaTune will just display it as it does now.

[shauer]

That does sound like it would work pretty nice, the one problem is what you pointed out, it would be big!
You can make the Curve graphs pretty small on the AE wizard with them only being 4x4 arrays, but these 4 are 12x12's.

I thought each EAE table was a 12x2 table. 12 MAP or RPM settings with the MAP/RPM value and the EAE value that goes with it (24 values total). I think you would need to do at least 4 12x2 tables. Still a challenge but better than 4 12x12 tables!

Now I see a couple ways to address this, You couple break that into 2 screens considering if you have the screen space, TunerStudio lets you open multiple windows at the same time anyway. So say you put both RPM's in one dialog and both kpa in the other, or sucked in one, adhere in the other....

Another possibility, but this would be a more work, is if I made the curve graph support multiple lines on a single graph. Then we could put both RPM curves on one, and both Walls curves on the other, that would bring it down to 2 graphs and all 4 curves showing.

I need to make that current value do a bit better job placing itself too, it currently covers some values sometimes.

5 signals on the graph widget isn't a problem, it will grow taller with each new line to fit the values, but they could get hard to track all on the same widget, it might be easier with 2 graphs. With the width of this I can easily put 2 side by side.

So all of it is just ini work and improving some ini interpretation except the 2 curves on 1 graph, that will take some widget modification.

I'm sure James and Ken would most likely be fine with rolling the ini changes into their builds going forward as long as it doesn't hurt MegaTune compatibility, and it won't. MegaTune will just display it as it does now.

All good ideas. I think it might be doable on a more conventional set of widgets if I am right and each EAE curve is 12x2.

I was thinking of ideas around allowing an EAE wizard to show you the eccel enrich behavior that a given set of tables would give you for a given input as defined by a log file but I think that might be a little over the top. EAE is continuously calculated and there is a fair amount of work in the calculations from what I have seen in the code.

Being able to "just" view/edit the 4 most important tables on one screen and see what portions of each curve are being used while viewing a log file would be great for an EAE wizard.

[LT401Vette]

Yeah, technically you are right as an array, they are 12x2, if the were 12x12 it wouldn't be a curve, it would be a table.
All curves are X x 2, I'm just looking at is as 12 high by 12 wide.

Don't worry about conventional widgets, there are none in the app. They are all ground up, so changes to them are never a constraint . Except the 2D table, that is based on a JTable. The curves, graphs gauges, 3D tables.... All were written ground up for TunerStudio.

[shauer]

Ok, I understand where you are coming from. You need a 12x12 space to be able to display the curve correctly due to there being 12 points defined in the array.

There is a problem with the scale of the values for these tables when it comes to displaying multiple curves in the same graph space. The sucked from walls constants are about 1/10 the values of the adhere to walls constants. The RPM corrections are both in percent so those might be able to share a graph. If you were to display the adhere to walls and sucked from walls curves in the same graph I think the scaling would be an issue. (sucked from walls would be compressed into the bottom 1/10 of the graph)

I'm about out of ideas for now. My original proposal is about the best I can think of right now. Be able to view/edit the adhere to walls, sucked from walls, and the related RPM corrections on one screen with a trace view of RPM, TPS, MAP, AFR, and EAE%. The EAE curves would show the active area of each curve in either real time with the trace view or as a log viewer when analyzing a previously stored log file.

Now I just need a 24" wide screen monitor to be able to see all this at once.

[LT401Vette]

There is a problem with the scale of the values for these tables when it comes to displaying multiple curves in the same graph space. The sucked from walls constants are about 1/10 the values of the adhere to walls constants. The RPM corrections are both in percent so those might be able to share a graph. If you were to display the adhere to walls and sucked from walls curves in the same graph I think the scaling would be an issue. (sucked from walls would be compressed into the bottom 1/10 of the graph)

Yeah that's what I was thinking, their scales are close enough to overlap. Alternatively I could make the curve support multiple scales.

Heck it would probably be pretty helpful in the short run to even have a graph on each of the curve's instead of the single gauge, even without consolidating, because you can open the multiple dialogs at the same time and it does remember where they last were. It would be nice to combine them. I'll churn on it some more.

Thanks for all the input. I think AE is a great place to improve things, it is often one of the more challenging tuning aspects.

[dave]

calibrating the TPS ADC's doesn't seem to make the TPS gauge read right for me, when the foot is off the pedal it still reads 40% throttle.

I love the histogram you added, works pretty nice. I see the coolant reading dip/blip ocassionally, not sure if this is real noise on my setup or not yet. will start taking some logs in this software and megatune and compare.

[ausloki]

I haven't had any further problems, latest version detects my correct code version without problems.
The update process is still a little hit and miss but otherwise i'm loving it.

Now on to those nice autotune wizards

[Kaas]

Dave!
Copy the TPS inc file from megatune to your project, it worked for me!

[LT401Vette]

Dave,
Sorry I've been out of town a couple days, I'll give that a check. It should be working, but I haven't tested that on an MS1 in a while, perhaps i broke it?

[LT401Vette]

Dave,
Are you saying that after calibrating the Throttle from the Tools menu, it still didn't take effect?

Kaas, you see the same before you copied over the throttlefactor.inc from MegaTune?

It seems to be working for me

[Kaas]

Yes it works just as well as in megatune!

I tried first calibratiing the TPS in TS, but no inc file was made. So I just copied the throttle inc from megatune to my project along with the temp inc files!

[dave]

Dave,
Sorry I've been out of town a couple days, I'll give that a check. It should be working, but I haven't tested that on an MS1 in a while, perhaps i broke it?

Dave,
Are you saying that after calibrating the Throttle from the Tools menu, it still didn't take effect?

That's correct.
I'll try copying the file from the MS dir, but I couldn't get it right through the menus.

I'm running MS1-extra

[LT401Vette]

Which firmware?