Enginuity v0.2.7b (Beta) is now released. (http://www.enginuity.org/viewtopic.php?t=198)

Jared Gould (qoncept) is the programmer/designer behind enginuity. He has worked and researched conscientiously in producing this software.

Please check the enginuity website for required "plug-ins" such as the tactrix SSM cable, latest JVM from Java, and ecuExplorer. All related links are available at the enginuity website.

For those of you who haven't heard of enginuity.

enginuity:

Enginuity is a free, open source application created for viewing, editing and tuning Engine Control Units (ECUs). Enginuity is written in Java and, as of version .20 alpha, uses XML to define ECU versions, meaning it is infinitely extensible and useable on any ECU you can retrieve an image from. Any information stored in your ECU (timing advance, fueling, boost, etc) may be altered, making your stock ECU nearly as powerful as expensive stand-alone units, better than piggy back units, and more functionality than commercial software costing in the thousands of dollars.

Enginuity is intended for use only by experienced tuners who understand the consequences. As with any tuning solution, the potential for engine damage is very high when altering your ECUs hard coded values. The use of appropriate equipment (ie, knock sensor, wideband oxygen sensor) is extremely important.

Donwload Disclaimer:

In order to minimize problems, users are required to register and login before downloading files. I did this to help prevent people who don't know what they're doing damaging their engine/ECU with Enginuity. So.......

Don't flash an Enginuity-altered image to your ECU if you don't understand the values you are editing or are not willing to accept the risks of alpha software. Alpha status means this software is incomplete, untested and NOT in ANY way guaranteed. If you are simply downloading to evaluate and are not using another utility (ie ecuFlash) to flash it to your ECU, you aren't at any risk.


As always, we value your feedback. Please be discrete. We'd like to hear from you.

Good luck tuning!!
enginuity

Enginuity is available under the GNU General Public License (GPL). The short and skinny of it is that it's free and the source is open and available. Any application making use of any or all of the code herein must be made available under the same pretenses.


GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

continued on next post.....

continuation....

4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA


Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

I have use it works great!!!!! :D

Thank you sir! What year is your car and what modifications have you done?

I have use it works great!!!!! :D

I know I am waiting patiently for my warranty to run out, and this project to reach at least Beta stage before I try it out. But I did want to say, thanks for the work and it's great that it is a GPL. :banana:

I am not sure when the Beta stage will be released, but I'm sure Jared is working towards that goal.

Thank you sir! What year is your car and what modifications have you done?

2003 WRX

Turbo xs FMIC
Greddy Big MAF intake
BPM Turbo back exhaust
Hks uppipe
Sti pink injectors
Fuel rails
255 fuel pump
vf22

Nice! :D

I'm missing the FMIC and Big MAF, then we'd have the same setup :lol:


2003 WRX

Turbo xs FMIC
Greddy Big MAF intake
BPM Turbo back exhaust
Hks uppipe
Sti pink injectors
Fuel rails
255 fuel pump
vf22

Nice! :D

I'm missing the FMIC and Big MAF, then we'd have the same setup :lol:

right on!! :D

:devil:

The current plan is to release 1 or 2 more versions to finish including all the basic functions I want and then call it beta. Hopefully then I'll be able to run more comprehensive tests and shortly after release a non-test version -- look for it in about a month.

What modelyears are supported now?

2004 WRX is pretty comprehensively covered, 2002 and 2003 are incomplete but timing, fuel, boost and a few others are supported for a handful of ECU versions. Subaru has about 25 different ECU versions between 2002 and 2005, so getting them all supported is a pain. I've got a laundry list of things to do, but adding support for more ECU versions is one of them.

Subaru has about 25 different ECU versions between 2002 and 2005, so getting them all supported is a pain. I've got a laundry list of things to do, but adding support for more ECU versions is one of them.This is why you see reflashes like the AccessPort using a common ECU revision where possible. For example, all 02-03 cars end up getting reflashed with the same image, all 04 gets the same, all 05 gets the same, all 06 MT gets the same and all 06 AT gets the same.

From a software and map maintenance standpoint the fewer maps you have to keep track of, the better.

This is why you see reflashes like the AccessPort using a common ECU revision where possible. For example, all 02-03 cars end up getting reflashed with the same image, all 04 gets the same, all 05 gets the same, all 06 MT gets the same and all 06 AT gets the same.

From a software and map maintenance standpoint the fewer maps you have to keep track of, the better.


Hasn't that technique bit them in the ass before? I believe that they tried to use the same map on 04/05's for a while? Not that I'm saying it's bad, just that it may be a bit of a technical problem for a volunteer standpoint either way.

Hasn't that technique bit them in the ass before? I believe that they tried to use the same map on 04/05's for a while? Not that I'm saying it's bad, just that it may be a bit of a technical problem for a volunteer standpoint either way.Yes, they did have a problem with the 05s when they were first released and had to use a dedicated 05 maps. I think that especially for a volunteer community it'll be easier to maintain a handful of maps instead of dozens, though if someone is willing to run through the mappings for all revisions of ECU the more power to them.

The next trick is to generate a generic map which when combined with the map offsets gets you your revision specific tuned map. That way you enable map sharing between different revisions of ECU. Maybe this is already possible?

The next trick is to generate a generic map which when combined with the map offsets gets you your revision specific tuned map. That way you enable map sharing between different revisions of ECU. Maybe this is already possible?

Thats what I was thinking, sort of an intelligent diff between ECU's.

The generic map definition already exists, if you look in ecu_defs.xml, WRXBASE has all of the tables and each revision simply adds the storage addresses to that.

The Honda guys on pgmfi.org have been doing this for years, and yeah, they have their revisions narrowed down to the point where they almost all use the same image (easier on old OBD-I and earlier ECUs, though).

What I'd like to do is set up a wiki that has all the latest ECU images for each ECU version so only those would need data offsets, like you said. This could also be used to keep the definition file updated and organized. When I get some time I'll see about setting up the wiki, or maybe Scoobypedia ( www.scoobypedia.co.uk ) would be a better place for it.. Either way, I'm too busy between work, autox and Enginuity to do it right now, but it shouldn't be too long.

Great job man I wish i knew how to do some of this stuff I would help you out, but I have figured out how to use the software though I have been reflashing my car and my friends cars. Great stuff!!!!!!!!!!!!!!!! :D

Great job man I wish i knew how to do some of this stuff I would help you out, but I have figured out how to use the software though I have been reflashing my car and my friends cars. Great stuff!!!!!!!!!!!!!!!! :D
Doing my best.. :) Are you in the AF? I'm at Maxwell/Gunter, have a few friends at Luke.

I guess it is only a matter of time before we have real-time tuning as well. When that ability is finally cracked its going to be awesome.

Doing my best.. :) Are you in the AF? I'm at Maxwell/Gunter, have a few friends at Luke.

Yes I am and Luke is where I be! :D

Very nice, I am working on some developement for '05 WRX Maps.

The generic map definition already exists, if you look in ecu_defs.xml, WRXBASE has all of the tables and each revision simply adds the storage addresses to that.I suspected it might already be possible, I just haven't looked into the software mapping details that far, yet. Good work, I'll try to get some time getting my 03 mapped out. I wonder what the ECU will think it is after having been flashed by AccessPort, though.

I wonder what the ECU will think it is after having been flashed by AccessPort, though.Why not dump its ROM and find out? My guess is a 2002 WRX.

Once my cable arrives I'm going to dump some roms from an 02-03 AP'd WRX and get someone to help me do some dumping on an AP'd 04-05wrx.

I suspected it might already be possible, I just haven't looked into the software mapping details that far, yet. Good work, I'll try to get some time getting my 03 mapped out. I wonder what the ECU will think it is after having been flashed by AccessPort, though.
It'll be the same revision as every other 02/03 WRX. We've been talking on openecu about what Cobb does when it unmarries -- none of us have an AP to test if it replaces the original image that was on your car, or just whatever revision they happen to already have on the AP.

In any case, if you have an AP or ecutek, make sure you keep a backup of your ROM. That way, if you ever want to use the AP or ecutek again, you can be 100% sure you'll have all the licensing in the ROM.

I'll do some comparisons on that as soon as my cable arrives next week.

I've got a few bug fixes and a ton of ECU revisions to add, hopefully that'll be done some time this week.

Just curious wha bugs you are refering too? Error handeling?

http://www.enginuity.org/viewforum.php?f=5

..and here's the list of things I'm going to add. I probably won't get to all of them for 0.2.5 but I hope to get most of them knocked out.

http://www.enginuity.org/viewtopic.php?t=48

Version 0.2.5 beta is now available. Must log in to download, yada yada..

http://www.enginuity.org/viewtopic.php?t=137

great news! Hats off to you for all the hard work.

I understand this has the capability to work on an 02 WRX ecu. What are the chances of it being functional on an v7 STi ecu, using the same plugs, connectors, ect as a wrx ecu, the only real difference being AVCS?
this could make my pump gas tuning much easier
thanks!
Hunter

Basically, to support an ECU version, all you need is a way to get the image off the ECU and the data locations. You'll need ecuExplorer ( http://www.tari.co.za/cgi-bin/yabb2/YaBB.pl?num=1138965460 ) and an openport 1.2 cable ( www.tactrix.com ) to get the image. ecuExplorer supports ROM dumping / flashing from USDM WRX 2002-2005, non-USDM WRX 2001-2005 and non-USDM STi 2001-2005.

If you get an image off your ECU, let me know (on enginuity.org, it's the only place I check frequently anymore) and I can get the ECU definition file set up for you.

If the ECU is not DBW (which it shouldn't be for the ver 7) then you should be able to dump it with either ecuFlash or ecuExplorer.

Jared, All,

I'm more than happy you guys use my Scoobypedia Wiki (http://www.scoobypedia.co.uk) to either store and/or index all the ECU images by linking back to the relevant Enginuity forum post. Either way, let me know if you want any help doing so. Alternatively Feel free to throw anything my way and I'll publish it for you guys. It's the least I can do to say thanks for your contributions to date.
-Steve.

...What I'd like to do is set up a wiki that has all the latest ECU images for each ECU version ... or maybe Scoobypedia ( www.scoobypedia.co.uk ) would be a better place for it..

It'll be the same revision as every other 02/03 WRX. We've been talking on openecu about what Cobb does when it unmarries -- none of us have an AP to test if it replaces the original image that was on your car, or just whatever revision they happen to already have on the AP.

In any case, if you have an AP or ecutek, make sure you keep a backup of your ROM. That way, if you ever want to use the AP or ecutek again, you can be 100% sure you'll have all the licensing in the ROM.The AP definitely replaces the map with an "Off the shelf stock" map, not the original one from your car.

hey guys...very intrigued by this, and VERY impressed

do you guys think this is worth ditching my UTEC for? To me, it actually seems like it would be preferable...

Will Version 0.2.5 support my UKDM 2004 WRX??

How can I verify this??

do you guys think this is worth ditching my UTEC for? To me, it actually seems like it would be preferable...
That's the idea.. There are definately some features of the UTEC that we can't copy yet (like launch control), but not having to use a piggyback makes it worth it in my opinion.

Will Version 0.2.5 support my UKDM 2004 WRX??

How can I verify this??
Not at the moment, but it would be easy enough to add support. What you'd need to do is get an openport cable (www.tactrix.com) and ecuExplorer (www.tari.co.za). Get a copy of your ROM uploaded so I'll know what version it is and it'll take me 10 minutes to create a definition for it.

Enginuity 0.2.6 Beta is now available.

http://www.enginuity.org/viewtopic.php?t=163

Enginuity 0.2.7.2 Beta is now available.

http://www.enginuity.org/viewtopic.php?t=200

Enginuity 0.2.7.4b is now available.

http://www.enginuity.org/viewtopic.php?t=287

Yay!!!!

good stuff

What will it take to get FXT support added in? My '04 is needing a new tune. :)

The architecture of all the DBW ECUs is totally different than non-DBW cars. Just this week someone finally figured it out so it shouldn't be too long now.

Can I disable TGV CELs/codes? Especially the ones that cause limp mode?

Can I disable TGV CELs/codes? Especially the ones that cause limp mode?

Thats a good question. That one has crossed my mind before.

All CELs can be disabled by modifying the ROM.

All CELs can be disabled by modifying the ROM.

my consern is when they hook it up to the odbII scanner at state inspection in nj if it will show that something isn't right or if it will just pass?

It will be completely transparent to OBD-II sniffers. They'll have no idea.

It will be completely transparent to OBD-II sniffers. They'll have no idea.

thats what i like to hear :D

All CELs can be disabled by modifying the ROM.
I believe you, but I would like to get more clarification.

It has taken EcuTek and others quite some time to defeat the TGVs.

I don't mean "intercept the problem and just don't light up the CEL on the dash". That's relatively easy as I understand it.

I mean "fully subvert" TGV logic so that a car with no TGVs and no TGV sensors plugged in has zero problems.

Defating the CELS is generally not that hard. Most of the locations are known. Most CELS are deleted (well not actaully deleted) but the values that trigger them are moved to a point where they no longer trigger the cel hence "deleting" the cel. I hope that made sense?

PM crazymike.
He has been comparing the USDM and JDM ECUs. I think he said that the memory space used for the TGV code in the US ECU is used for the AVCS in the JDM ECU. You might be able to flash the JDM ROM into the US ECU. That way the US ECU won't even check for the TGVs.
I am not sure so you would need to talk to him.

TMS

I believe you, but I would like to get more clarification.

It has taken EcuTek and others quite some time to defeat the TGVs.

I don't mean "intercept the problem and just don't light up the CEL on the dash". That's relatively easy as I understand it.

I mean "fully subvert" TGV logic so that a car with no TGVs and no TGV sensors plugged in has zero problems.

Jeff, you can disable all CEL codes. My car has a stock ECU right now tuned via Colby's ECUflash, Calvin's ECUexplorer, and qoncept's Enginuity.

Say your DTC is P0420.

Load the ROM A4SGD10C in a hex editor. Search for either the hex sequence

03 04 20

or

04 04 20

The 03/04 depends on whether the DTC is an OBD or OEM specific code, I think. You can see that the DTC part of the bytes is just encoded as BCD, and looks like decimal. In this case, I find 03 04 20 in one place in the file, at address 0x2DB0D. To eliminate this DTC mapping, replace the 03 04 20 value with 05 00 00, which appears to be Subaru's way of mapping this event to a non-existent DTC, which produces no CEL.

That's it! Just be sure you don't accidentally edit some other part of the ROM that just happens to have a byte sequence that matches the DTC you are looking for!

Colby

Version 0.3.0 is now available for download. This version adds 32-bit ECU support (STi, Legacy, Forrester etc) (!), new checkboxes for disabling CELs, and some other minor changes. Now get it and tune your STi!

http://www.enginuity.org/viewtopic.php?t=397

w00t! :)

Gotta get my cable now :D

should'a done that three months ago :p :D


w00t! :)

Gotta get my cable now :D

should'a done that three months ago :p :D


I only got my FXT 3 months ago :p

Until as of last week it's been relatively stock. :devil: :banana: