TephraMod V7

Reply Subscribe

Thread Tools

Search this Thread

Oct 12, 2009, 06:53 PM

#211

Jack_of_Trades

Evolved Member

iTrader: (17)

Join Date: Jun 2007

Location: Opelika,AL

Posts: 3,523

Likes: 0

Received 2 Likes on 1 Post

Quote:

Originally Posted by phenem

My post mentions it, I put that up the first day. Doesn't matter just wanted to point out that people don't really read everything even though you make it bold and red in color!

Think of the color blind people!

haha

Reply Like

Oct 12, 2009, 07:07 PM

#212

Jack_of_Trades

Evolved Member

iTrader: (17)

Join Date: Jun 2007

Location: Opelika,AL

Posts: 3,523

Likes: 0

Received 2 Likes on 1 Post

After reading, the MAP sensor tables I re-labeled earlier are only called up for the MAP sensor VE tables for SD and do nothing for PSI based boost control. So we will need to convert the scaling tables for BoostErrorPSI,Psia16 and Psia8 to be able to have the BDEL,TBEC and BCLO tables be accurate with each type of map sensor. It is currently set up ONLY for the JDM/Evo X Map sensor by default in the XML.

Reply Like

Oct 12, 2009, 07:14 PM

#213

recompile

Evolved Member

iTrader: (38)

Join Date: Nov 2006

Location: New Hampshire, USA

Posts: 1,745

Likes: 0

Received 6 Likes on 4 Posts

Woo hoo!

Last edited by recompile; Oct 12, 2009 at 08:33 PM.

Reply Like

Oct 12, 2009, 07:30 PM

#214

phenem

Evolved Member

iTrader: (39)

Join Date: Jul 2005

Location: Central PA

Posts: 811

Likes: 0

Received 4 Likes on 2 Posts

If you have a good idea on how to organize the information please suggest by sending me an email to phenem at gmail dot com and we can work offline and figure this out and post up what we work out. I will gladly let you construct the post and edit it in a more organized fashion.

Last edited by phenem; Oct 12, 2009 at 08:36 PM.

Reply Like

Oct 12, 2009, 07:51 PM

#215

recompile

Evolved Member

iTrader: (38)

Join Date: Nov 2006

Location: New Hampshire, USA

Posts: 1,745

Likes: 0

Received 6 Likes on 4 Posts

Woo hoo!

Last edited by recompile; Oct 12, 2009 at 08:33 PM.

Reply Like

Oct 12, 2009, 08:01 PM

#216

mt057

Evolved Member

iTrader: (6)

Join Date: Apr 2007

Location: DFW

Posts: 1,529

Likes: 11

Received 12 Likes on 11 Posts

Thank You to everyone's hard work to make this happen. It makes me love owning an evo even more. I wish I knew how to code to help out.

Last edited by mt057; Oct 12, 2009 at 08:54 PM.

Reply Like

Oct 12, 2009, 08:16 PM

#217

phenem

Evolved Member

iTrader: (39)

Join Date: Jul 2005

Location: Central PA

Posts: 811

Likes: 0

Received 4 Likes on 2 Posts

Perfect! Appreciate the help, can you edit that and delete it so people don't get confused now? I will update my first post with your modified version.

Honestly I like your version better, I just didn't have time to lay it out so I typed it up as I thought about it.

Reply Like

Oct 12, 2009, 08:35 PM

#218

recompile

Evolved Member

iTrader: (38)

Join Date: Nov 2006

Location: New Hampshire, USA

Posts: 1,745

Likes: 0

Received 6 Likes on 4 Posts

Quote:

Originally Posted by phenem

Done, and edited away my harsh criticism earlier in the thread as well. Sorry for coming off that way, I do appreciate your time and effort.

Reply Like

Oct 12, 2009, 08:39 PM

#219

phenem

Evolved Member

iTrader: (39)

Join Date: Jul 2005

Location: Central PA

Posts: 811

Likes: 0

Received 4 Likes on 2 Posts

Quote:

Originally Posted by recompile

Done, and edited away my harsh criticism earlier in the thread as well. Sorry for coming off that way, I do appreciate your time and effort.

Thanks man, I did the same. It honestly does look better now. I added some addition things just in case and it will definitely be better for everyone reading it now.

Reply Like

Oct 12, 2009, 08:40 PM

#220

phenem

Evolved Member

iTrader: (39)

Join Date: Jul 2005

Location: Central PA

Posts: 811

Likes: 0

Received 4 Likes on 2 Posts

Quick question for you guys, how would you do the number sequence for the EVO 9 guys?

We have consolidated ROM versions such that all Evo VIII ROM IDs share version 96530706 (MAF) and 96531706 (Speed Density) and all USDM Evo IX ROM IDs share version 88590715 (MAF) and 88591715 (Speed Density)

Blue color is tephra version number
Red color is 0 for MAF and 1 for Speed Density

Is this acceptable for everyone or is there a better idea?

Last edited by phenem; Oct 13, 2009 at 06:05 AM.

Reply Like

Oct 12, 2009, 09:15 PM

#221

jrohner

Evolving Member

Join Date: Oct 2008

Location: Willmar MN

Posts: 160

Likes: 0

Received 0 Likes on 0 Posts

Why not put the 0 or 1 in the same position for both -- so 96531706 and 88591715?

Reply Like

Oct 12, 2009, 09:22 PM

#222

tephra

EvoM Guru

Thread Starter

iTrader: (6)

Join Date: Feb 2007

Location: Melbourne, Australia

Posts: 9,486

Likes: 1

Received 66 Likes on 42 Posts

Speed Density users *should* be more up-to-speed with XML changes etc.

I wouldn't worry about having a new ROMID for them...

Reply Like

Oct 12, 2009, 10:14 PM

#223

Monochrome

Evolving Member

iTrader: (9)

Join Date: Apr 2005

Location: Avondale, PA

Posts: 145

Likes: 0

Received 0 Likes on 0 Posts

Quote:

Originally Posted by phenem

Quick question for you guys, how would you do the number sequence for the EVO 9 guys?

We have consolidated ROM versions such that all Evo VIII ROM IDs share version 96530706 (MAF) and 96530716 (Speed Density) and all USDM Evo IX ROM IDs share version 88590715 (MAF) and 88591715 (Speed Density)

Blue color is tephra version number
Red color is 0 for MAF and 1 for Speed Density

Is this acceptable for everyone or is there a better idea?

I thought that was a brilliant idea for keeping them all straight.