Frosty, I missed the information you are talking about. Thanks for the clarification. If the spreadsheet is correct then to enable the bit it is a "0", which I have in the ROM as default.

 

I was just wondering that today ...

 

That would be nice! I beleive this is a mrfred mod and has not been ported over to the 96530006 ROM.

 

Seems like it might be useful to have this (https://www.evolutionm.net/forums/ec...trol-mods.html), already be patched in to the load based version.

 

They will be eventually. Those same tables can be used for EITHER load or PSI boost control, you just need to edit a few tables which takes all of 1 minute once I finish my layout.

 

You can use the method I used.

Do a 96530006_base.xml that has most everything in it and calls the evo7base.xml

96530006.xml only has the small fuel and timing maps and the stock boost control tables. On the fuel and timing maps, leave the element size out of the evo7base.xml and put the element size in the 96530006 definition.

96530706.xml has the tephra options, the BIG fuel an timing maps (with larger element size), and the relevent boost control tables.

96531706.xml has the tephra options, Big Maps, MRfred direct boost stuff + relevent stock boost tables, and JCSBanks SD patch stuff.

Each 9653XXXX.xml file calls the 96530006_base.xml.

It doesn't gray them out, they just don't show up at all since they never show up in the xml if the table isn't used.

 

Well I was trying to find a way to do it that worked with the 'default' XML files that comes with ECUFlash, that way we don't have to have users replace a ton of XML files, just plug n' play. If they could JUST load the v7 XML and have things already grayed out, that would be ideal....if possible. I don't like messing with the base files because a bunch of rom's inherit those tables so you then need to modify a bunch of files to make it all work. I could go through my own files and get everything I wanted it quite easily, just trying to find a way simple enough for a noob to accomplish without bothering us haha.

 

Yeah, that's why I picked up the thing gearhead did on his...

evo7base_20091012.xml

Then it doesn't mess with any of the other ROMs.

 

Trying to remain patient...

But, do you happen to have a ballpark ETA for 88590715?

 

It may be easiest to have a separate base XML for the patch to keep it neat and tidy. I wouldn't mind since we just need to rename the current base xml and edit it solely to work with the v7 XML file.

evo7base_v7.xml


or.........don't have it inherit the base xml file all together and have everything in the v7 xml file.

 

OK, I have tested DMA/LiveMap successfully for v7-bigmap today. Instead of posting the instructions here, I think I will email phenem a patched ROM so that maybe he can add it and the XML definitions to his posts.

Also I modified my version of the LiveMap app quickly to allow the bigmaps to fit nicer (scroll bars, etc) and have the XMLs setup based on my header scaling. I will send that to him as well. I think ziad has a better version of the LiveMap app that he is working on, but I haven't had a chance to play around with it yet.


Eric

 

The more I think about it, the more I like the idea of ONE xml file for these and not have them rely on the original ROM ID and base xml files. That way we can keep it neat and have all of the most current tables embedded into it already and we can rename them without throwing off other ROM xml's. We should be able to insert just about EVERY new patch into it too. Sure the file will be big.....maybe a whopping 100KB lol.

So maybe I missed it somewhere in this 'soon to be' novel of a thread, are there no LOW octane maps for the ALT maps anymore? Does it just reference the standard low octane maps?

 

yes i have a better version... its soo good that i have to close it down to restart logging.... but its about 50% faster with no slowing down when updating a lot of stuff

 

I know they don't represent actual AFR but if the scaling is close the AFRs will be close...

 

Alright, I went looking back through the rom again and I'm pretty sure I understand the MAP VE calibration part. Next step is to find out what percentage of an increase is the Omni 4 bar over the standard 3 bar and make the changes...man I should have bought a stock sensor, this would be so much easier lol.