need help: new xml files for upcoming ECUFlash release

Reply Subscribe

Thread Tools

Search this Thread

Feb 3, 2009 | 11:26 AM

#211

gsrboi80

Evolved Member

iTrader: (38)

Joined: Aug 2005

Posts: 7,909

Likes: 47

From: On a cliff

Quote:

Originally Posted by mrfred

If you want, yes. The advantage of the separate file is that its easier in the long run... Just move the mods file over each time a new update is released.

Now I get it. Yea that does make sense. Thanks man

Feb 13, 2009 | 10:35 AM

#212

fostytou

EvoM Community Team

iTrader: (15)

Joined: Sep 2006

Posts: 3,143

Likes: 7

From: Aurora, IL

https://www.evolutionm.net/forums/6688770-post841.html

This may be pertinant. Not sure if Mr Freds defs were used in the most recent version of 1.41.

Also, wouldn't it be nice if the mods file could <exclude> a table from the other XML? EG: to get rid of the maps replaced by tephra's altmaps.

EDIT: Fixed, nevermind.

Last edited by fostytou; Feb 13, 2009 at 11:02 AM.

Feb 13, 2009 | 11:03 AM

#213

fostytou

EvoM Community Team

iTrader: (15)

Joined: Sep 2006

Posts: 3,143

Likes: 7

From: Aurora, IL

Does anyone know if there is a flag or an option we can set to make the default status of all of the sections "collapsed" instead of expanded? It seems like every time I open ECUFlash I collapse all of the sections by hand and then expand only the ones I'm working with.

Feb 28, 2009 | 01:24 AM

#214

$al\lupo's Avatar$

al\lupo

Evolving Member

Joined: May 2007

Posts: 178

Likes: 0

From: Italy

There is a mismatch in evo9base: the MAFHz frexpr is wrong, here is the correct one:

Code:

<scaling name="MAFHz" units="Hz" toexpr="6.29*x/64" frexpr="64*x/6.29" format="%.0f" min="0" max="5000" inc="1" storagetype="int16" endian="big"/>

Mar 22, 2009 | 11:44 AM

#215

raasfaas

Evolved Member

iTrader: (30)

Joined: Oct 2006

Posts: 780

Likes: 0

From: Fl/Jam

Bringing back this thread...need a little help here
I just installed ecuflash v1.41 and followed the instructions to do the XXXXXXXX_mods.xml file. Pretty much the only patches I have are Tephra's V5.10, and JDM Map sensor patches...since the 1.41 already comes with the mut tables, lean spool tables and 2 byte stuff I just took them out.
I'm coming from 1.29a so I know I had to change the endian to big in the tephra mods. I'm pretty sure I did everything ok, but when I open my .hex in 1.41 only the tephra stuff from my _mods file show up properly, the map sensor stuff are grayed out. Yes I am in developer mode. Although they're grayed out I can still open the tables and view and change what's in there.
Any idea whats going on here?

Attached Files

88590015_mods.txt (6.0 KB, 0 views)

Mar 22, 2009 | 08:47 PM

#216

mrfred

Thread Starter

EvoM Guru

iTrader: (50)

Joined: Mar 2006

Posts: 9,675

Likes: 132

From: Tri-Cities, WA // Portland, OR

v1.41 pays more attention to the level value in the definitions. Try changing the level="1" to level="2" or just delete the level modifier.

Mar 22, 2009 | 09:40 PM

#217

raasfaas

Evolved Member

iTrader: (30)

Joined: Oct 2006

Posts: 780

Likes: 0

From: Fl/Jam

Thanks mrfred changing it to level 2 worked

One more thing, do you know if the tactrix 1.3 cable is compatible with 1.41? Haven't had a chance to check it yet.

Mar 22, 2009 | 10:31 PM

#218

mrfred

Thread Starter

EvoM Guru

iTrader: (50)

Joined: Mar 2006

Posts: 9,675

Likes: 132

From: Tri-Cities, WA // Portland, OR

Most of the older cables work work with v1.41. There is only a small batch of the older cable that do not work.

Mar 23, 2009 | 01:59 PM

#219

raasfaas

Evolved Member

iTrader: (30)

Joined: Oct 2006

Posts: 780

Likes: 0

From: Fl/Jam

Well just my luck, I happen to fall into that small batch of older cables that don't work. It says that it cannot connect with the interface. Is there some update that I need to do or once it isn't able to connect that's it?

Mar 24, 2009 | 03:32 PM

#220

raasfaas

Evolved Member

iTrader: (30)

Joined: Oct 2006

Posts: 780

Likes: 0

From: Fl/Jam

Is there a software update that is needed for the tactrix 1.3 cable to work with ecuflash 1.41?

Mar 24, 2009 | 03:47 PM

#221

mrfred

Thread Starter

EvoM Guru

iTrader: (50)

Joined: Mar 2006

Posts: 9,675

Likes: 132

From: Tri-Cities, WA // Portland, OR

Quote:

Originally Posted by raasfaas

Is there a software update that is needed for the tactrix 1.3 cable to work with ecuflash 1.41?

If you bought the cable from Tactrix and still have the receipt, give them a *call*. If you bought the cable from Limitless (EvoScan), contact them. They can help you get your cable working with the latest versions of ECUFlash.

Mar 25, 2009 | 09:12 AM

#222

fostytou

EvoM Community Team

iTrader: (15)

Joined: Sep 2006

Posts: 3,143

Likes: 7

From: Aurora, IL

Quote:

Originally Posted by al\lupo

There is a mismatch in evo9base: the MAFHz frexpr is wrong, here is the correct one:

Code:

<scaling name="MAFHz" units="Hz" toexpr="6.29*x/64" frexpr="64*x/6.29" format="%.0f" min="0" max="5000" inc="1" storagetype="int16" endian="big"/>

It shouldn't matter thanks to order of operations, but you may want to keep the parens just for accuracy (and yes, it was incorrect in my 1.41 also):

Code:

<scaling name="MAFHz" units="Hz" toexpr="6.29*x/64" frexpr="(64*x)/6.29" format="%.0f" min="0" max="5000" inc="1" storagetype="int16" endian="big"/>

This increment update also helps a ton with being able to incriment the injector latency:

Code:

<scaling name="InjectorLatency" units="ms" toexpr="x*0.024" frexpr="x/0.024" format="%.3f" min="0" max="4" inc="0.024" storagetype="uint8" endian="big"/>

Last edited by fostytou; Mar 25, 2009 at 09:17 AM.

Mar 26, 2009 | 07:40 AM

#223

japanevo

Evolving Member

iTrader: (2)

Joined: Jan 2007

Posts: 124

Likes: 0

From: Las Vegas

if it isn't to late to make a contribution i have a 9055 rom i can send you.... however. i tried it with the evo7base in the zip file on this thread and cant view half of my tables. so if you can give me a couple of days to get everything working again that would be great.

Mar 26, 2009 | 10:06 PM

#224

japanevo

Evolving Member

iTrader: (2)

Joined: Jan 2007

Posts: 124

Likes: 0

From: Las Vegas

looked at both evo7bases and all of your definitions are almost the same as mine just minor changes i made to mine to get them working. also i have a lot of tables in my 7base that you didnt have. i made a txt with the changes for you to look at i also included the tables that i use along with my 9055 xml. carfull i have just about all of the mods i can think of in my 9055, tephra and SD.

Attached Files

9055 and 7base changes.zip (6.3 KB, 0 views)

Mar 27, 2009 | 07:42 AM

#225

logic

Evolved Member

iTrader: (2)

Joined: Apr 2003

Posts: 1,022

Likes: 7

From: Berkeley, CA

mrfred, do you think it would be possible to get the MUT table definition in evo7base_*.xml changed to this one (with the "RamAddress" scaling)? The default version is almost unusable for some of us using small form-factor systems for flashing (tablets, netbooks, etc; the maximum resolution on my tablet is 800x600).

Code:

	<scaling name="RamAddress" units="hex" toexpr="x-4294901760" frexpr="x+4294901760" format="%04X" min="0" max="65535" inc="1" storagetype="uint32" endian="big"/>
	<table name="MUT Table" category="Misc" type="3D" level="1" scaling="RamAddress">
		<table name="X" type="Static X Axis" elements="16">
			<data>0</data>
			<data>1</data>
			<data>2</data>
			<data>3</data>
			<data>4</data>
			<data>5</data>
			<data>6</data>
			<data>7</data>
			<data>8</data>
			<data>9</data>
			<data>A</data>
			<data>B</data>
			<data>C</data>
			<data>D</data>
			<data>E</data>
			<data>F</data>
		</table>
		<table name="Y" type="Static Y Axis" elements="16">
			<data>MUT0X</data>
			<data>MUT1X</data>
			<data>MUT2X</data>
			<data>MUT3X</data>
			<data>MUT4X</data>
			<data>MUT5X</data>
			<data>MUT6X</data>
			<data>MUT7X</data>
			<data>MUT8X</data>
			<data>MUT9X</data>
			<data>MUTAX</data>
			<data>MUTBX</data>
			<data>MUTCX</data>
			<data>MUTDX</data>
			<data>MUTEX</data>
			<data>MUTFX</data>
			<data>MUT10X</data>
			<data>MUT11X</data>
			<data>MUT12X</data>
			<data>MUT13X</data>
			<data>MUT14X</data>
			<data>MUT15X</data>
			<data>MUT16X</data>
			<data>MUT17X</data>
			<data>MUT18X</data>
			<data>MUT19X</data>
			<data>MUT1AX</data>
			<data>MUT1BX</data>
			<data>MUT1CX</data>
			<data>MUT1DX</data>
		</table>
	</table>

Reply Share

First
Prev
15 / 16
Next
Last