Before I blow up my engine tomorrow, I am just curious if anyone else here has ever manually increased the 12x12 Megatune2 Spark and VE tables themself. I just finished increasing to 16x16 tables, but it required an extra "page" in the megasquirt-II.ini file in order to do it. Also, the offset positions don't really matter as long as they don't overlap other bits, don't exceed the max 1024 bits/page, and aren't nested in an "if-else" statement, right? I ask, because I had to do a little moving around to get the 900 or so extra bits to fit on the 3 pages. Physically, the program DOES recognize the 16x16 tables and will take inputs to the fields. I just wanted to see if anyone here has any idea if the processor operates too slow to handle this properly or if even decreasing the "blockReadTimeout" from 200ms to 133ms would alleviate any possible problems. Any help would be appreciated. Here are two pics to show I guess...Ignore the actual values as I was testing to see that they indeed work.
VE table
and Spark table
And this is the "blockReadTimeout" constant I was referring to...
What engine is this for??????
Why do you have your idle adv. set so high? And why does your VE table cut at 80kpa? Idk where your at but if your N/A id think you would be tuning to atleast 100kpa..
Either way, good to see another Megasquirt User!
now The L61 Powered Fiero
PURE DICE, PURE Design.Innovation.Creation.Excellence.
I try and pick up on most of the MS threads here, and Ive yet to see anyone try this. is it really worth it? will the car run any smoother?
"
boobs now with Riboflabin"
The purpose is to have a more fine tune. An engine management system (at least MS and MS-II) will take the values in the bins and make linear approximations to determine what the VE and Spark advance should be at any given MAP and RPM. The problem is, VE has a non-linear shape per MAP value and per RPM, so the more bins you have, the closer the linear approximation gets to fitting the curve. 12x12 is certainly plenty for my current NA engine, but it will receive a turbocharger in the hopefully near future and it's a 10.7:1 SCR engine . So, I could really use the extra fine tuning a 16x16 table gives when that happens. I still have yet to test this, so I'm not sure if the processor is fast enough to keep up. I believe that MS2EXTRA has 16x16 table capabilities, so I'm really not too worried.
MS2Extra has some other features that may be nice too. But I think you have to set it up differently. I tried flashing it onto mine, and then the car wouldn't start.
The 16x16 tables look nice though, I'd do it to mine if I knew what I was doing.
Yeah MS2Extra has table switching as well, to name just one of the many other features it has. That would be a benefit over the single 16X16 tables, but I am just trying something simple for right now, considering I have everything already setup in Megatune2.
I still have my reservations on trying this, still. I guess I can wait a few weeks until I go back home and can test it on the simulator first. I'll let you guys know how it goes when I do.
Yeah...Bad Idea.
Gauge was showing something like 550+ degrees of advance at idle. I don't know if that was just a problem with the values the gauge takes or if the math to actually do the calculations requires the original placement in RAM to perform them correctly and those would have to be changed as well. Either way, I may still mess around with this code, but until I am certain where the math looks for values to calculate, I'm just going to stick with the stock Megatune code or MS2Extra for now.
I like the 16 x 16 tables, that gives you a lot of room to play.
I would say you'll need to figure out your timing issue with code, but thoes tables look sweet.
Now if i could only figure out how to expand the tables in the odb1 pcm????
