Enginuity is MIA so I've created a new repository with the latest source code.

Wiki and downloads: http://www.assembla.com/spaces/enginuity
SVN: https://svn2.assembla.com/svn/enginuity

Also for download are the latest ecu and logger defs and a new test release (rev.785).

Thanks!

Thanks :)

Sweet, thank you

Thanks. I had to format my laptop two weeks ago and couldn't find a recent copy of this anywhere.

Where can I find the differences between this test release and 774?

Also, which do I need to build from to get the new MAF tool?

Anyone got a HOWTO for windows compiling? I'm used to doing it on UNIX/OS X, don't want to miss an important step on Windows.

Where can I find the differences between this test release and 774?

I honestly can't remember what all the changes are. I built rev785 a few months ago now but never released it until now. The main differences are the new MAF rescaling tool and improved AEM UEGO support (still a bit buggy as I don't have a car to test it on). Besides this there are numerous bug fixes and small enhancements to the editor (nothing immediately obvious to the user).

Also, which do I need to build from to get the new MAF tool?
The rev785 test release contains the MAF tool already.
Anyone got a HOWTO for windows compiling? I'm used to doing it on UNIX/OS X, don't want to miss an important step on Windows.
This is java, all you need is the jdk and/or a decent IDE (intellij, eclipse, netbeans).

Unfortunately as I only had a copy of the latest code and not the whole repository, there is no svn history so comparisons between previous versions is not possible.

I honestly can't remember what all the changes are. I built rev785 a few months ago now but never released it until now. The main differences are the new MAF rescaling tool and improved AEM UEGO support (still a bit buggy as I don't have a car to test it on). Besides this there are numerous bug fixes and small enhancements to the editor (nothing immediately obvious to the user).

Great, thank you.

I'm DLing the 785 build now. Are there instructions on how to use the MAF tool?

yes where can i find more info on MAF tool. i am just starting to rescale my MAF for a 70mm intake right now...

I'm DLing the 785 build now. Are there instructions on how to use the MAF tool?

yes where can i find more info on MAF tool. i am just starting to rescale my MAF for a 70mm intake right now...

It goes something like this:

1. Hook up to your car
2. open enginuity
3. load your rom
4. start the logger
5. go to the MAF tab
6. set up the data record trigger conditions (defaults are pretty good)
7. hit 'record data'
8. go for a good drive (you need lot's of data)
9. hit 'record data' again to stop recording
10. use the interpolate button and order number to get a good fitting curve with the data
11. select the mafv range you want to apply the changes to
12. hit apply to have the changes applied to your maf scaling table
13. go to editor and save your rom
14. flash to car
15. repeat steps 7 to 14 until you're happy with the rescaling.

as with everything enginuity related, this is beta software so any changes that are made by the tool to your maf table are ultimately YOUR responsibility to check before flashing to your car.

I honestly can't remember what all the changes are. I built rev785 a few months ago now but never released it until now. The main differences are the new MAF rescaling tool and improved AEM UEGO support (still a bit buggy as I don't have a car to test it on). Besides this there are numerous bug fixes and small enhancements to the editor (nothing immediately obvious to the user).

Awesome! Thanks much kascade!

wow i just installed and checked out the MAF tab (havent plugged into the car yet)... and it looks very promising. thank you very much :).

I honestly can't remember what all the changes are. I built rev785 a few months ago now but never released it until now. The main differences are the new MAF rescaling tool and improved AEM UEGO support (still a bit buggy as I don't have a car to test it on). Besides this there are numerous bug fixes and small enhancements to the editor (nothing immediately obvious to the user).

i have an AEM and will try to give the test release a whirl for you this week.


thanks!
mike

ok i just sat out in the car with it... looks very nice. here's a screenshot for all the lazy people out there:

http://www.bryantroll.com/other/enginuitymafscreenshot.jpg

this was after i recorded my idle for about 10 seconds and interpolated the data.

first let me say i never would have known how to properly use the program if you didnt post instructions above. are they posted anywhere else or is that it? seems like there are a lot of great things available but the lack of support holds it back sometimes.

i also had a couple questions now that i've taken a look at it:

what does the "poly. order" number affect?

when you click 'update maf', what happens? does it multiply your actual maf scaling maf by the corresponding values interpolated (positive or negative percentage)? what logic is used here? this will only overwrite the MAFv Range specified?

if the maf scaling map is changed automatically, i assume then you should confirm the changes made and then save the map as a new version, flash, and see how it runs?

thanks for making this, sounds great... just want to make sure myself and everyone else out there understand how to use it properly...

oh and also, is the best way to record data the same as conventional? go sustain a certain mafv for a while, then move to the next, then the next, etc.? does it matter if you drive for 2 mins or 2 hours with this program?

I've tried to use the MAF tab but it does not seem to do anything. What am I doing wrong? I have tried logging too and selecting MAF V and g/s from the logger screen.

When I select record data button it does nothing, then I unselect it and click interpolate, then update MAF and I get an error saying interpolation required.

Any ideas?

Thanks.

did you follow the step by step posted above? thats what i did and it worked fine.

I ran around with the MAF tool active for a while today and I have some questions:

1) Does it in any way filter out data with high IATs? Heat soak at a stoplight can make a ~10% difference in my total AF error until things cool back down again.

2) Does it filter out rapid changes in MAFv/Pedal position? When you punch the throttle (such as a shift in a manual car), it screws up the AF corrections for a bit.

will, glad someone else is checking it out already. can you answer any of the questions i posted above? i havent had a chance to put it into action yet and am just wondering if thats how it works.
also, how much luck did you have using this? let us know what you think...

first let me say i never would have known how to properly use the program if you didnt post instructions above. are they posted anywhere else or is that it?
That's it. I'll post them up on the wiki where it's hosted as well soon.

seems like there are a lot of great things available but the lack of support holds it back sometimes.
That's open source for you I guess. My time is valuable as is yours I'm sure. I write this software so I can use it and if other people find it useful then great.

i also had a couple questions now that i've taken a look at it:

what does the "poly. order" number affect?

Google 'polynomial interpolation'. The polynomial order number basically determines how close the generated rescaling line fits the data. Play with the number to generate a line which you think best fits your data. A higher number isn't always better.

when you click 'update maf', what happens? does it multiply your actual maf scaling maf by the corresponding values interpolated (positive or negative percentage)? what logic is used here?
The values in the maf scaling table of the rom you have open (make sure this is the same rom used to obtain the data!) are adjusted by the amount calculated by the best fit line that was interpolated against the data. so yes, you are basically correct in how it works.

this will only overwrite the MAFv Range specified?
Yes. You should check the range over which you want to apply the changes.

if the maf scaling map is changed automatically, i assume then you should confirm the changes made and then save the map as a new version, flash, and see how it runs?
Yes. It won't be perfect after one run, this is an iterative process, but this tool should reduce the number of iterations required and amount of manual work involved.

thanks for making this, sounds great... just want to make sure myself and everyone else out there understand how to use it properly...
no problem.

oh and also, is the best way to record data the same as conventional? go sustain a certain mafv for a while, then move to the next, then the next, etc.?
The best way is to drive smoothly, avoid quick changes in throttle opening. Cruising at different speeds and at different loads works well. Avoid traffic, stoplights, etc.

does it matter if you drive for 2 mins or 2 hours with this program?
The longer the better to minimise the effects of tip-in, IAT changes, etc.


One thing I want to make clear is that this tool is really only useful for closed loop. Open loop is up to you ;)

Yup I followed the instructions above line by line.

It logs perfectly fine normally but nothing in the MAF tab seems to do anything. Strange. I'll experiment some more during the week. Anything I need to enable before I get into the MAF tab?

When do the points appear on the MAF graph? Real time or after clicking "record data" to stop the recording again? Do I need to enable logging of short/long term/mafv/gs etc before entering MAF tab?

It's a AF423 16bit ECU

Cheers

1) Does it in any way filter out data with high IATs? Heat soak at a stoplight can make a ~10% difference in my total AF error until things cool back down again.
No not in the current version. Maybe in the future. Better just to avoid traffic lights, pause recording of data, or wait until you've hit more open areas before recording data.

2) Does it filter out rapid changes in MAFv/Pedal position? When you punch the throttle (such as a shift in a manual car), it screws up the AF corrections for a bit.
No, same as above. Drive as smooth as possible.

Yup I followed the instructions above line by line.

It logs perfectly fine normally but nothing in the MAF tab seems to do anything. Strange. I'll experiment some more during the week. Anything I need to enable before I get into the MAF tab?

It's a AF423 16bit ECU

you should have some *.log files in your enginuity directory. post them up for me to look at. You sure the filter conditions have been met? coolant temp high enough? afr in range, etc?

Yeah I even made them even looser, dropping coolant to 50 etc and widening AFR range but no luck. I'll scan through the .log file to see whats up. It's kinda messy in there as I was trying to get the wideband running too (on the wrong port) so there is a whole bunch of port errors. I'll clear it out and start fresh.

Since we're talking about the MAF tool... is the stock O2 sensor in an RS accurate at stoich even at WOT or high RPM/partial throttle?

For those that want a visual todo. Here is the new GUI that was in progress. This is based on the "Tuning Entity" idea where Enginuity might support a medley tuning devices (Utec, AEM, Hydra, etc)

-= ROM EDITING TUNING ENTITY Needs to be implemented against the tuning entity interface =- The Gui framework is pretty damned complete, so getting started while cross referencing the current ROM editing code should make for a pretty straight forward task, though time consuming.

-Utec tuning entity edits maps, with partial lightly tested code to pull maps directly from the Utec and almost complete code to push maps back on the Utec. This might be of interest to people as well. Also, the TXS Tuner Pro is supported as a logging device, but I think it might need to be kicked off from the main gui, Kascade, is this true?


package enginuity.NewGUI.interfaces;

import javax.swing.JMenu;
import javax.swing.JToolBar;
import java.awt.event.ActionListener;
import java.util.Vector;


public interface TuningEntity extends ActionListener{

// Return name of tuning entity
public String getName();

// Return all the menu items relevant to tuning entity
public Vector<JMenu> getMenuItems();

// Return the toolbar
public JToolBar getToolBar();

// Return object data based on passed table name
public Object[][] getTableData(String tableName);

// Remove tuning group
public void removeTuningGroup(String tuningGroup);

// Push back modified data to the tuning entity
public void setTableData(String tableIdentifier, Object[][] data);

// Control methods
public void init(TuningEntityListener listener);

// Notify of system exit. Tuning entity must reply to parent GUI that they are in fac
// ready for shutdown
public void notifySystemExit();
}

package enginuity.NewGUI.interfaces;



import enginuity.NewGUI.tree.ETreeNode;



import javax.swing.JMenu;

import javax.swing.JToolBar;

import java.util.Vector;



public interface TuningEntityListener {



/**

* Change the tree structure base on the passed root node

*

* @param rootNodeOfNewTree

*/

public void addNewTuningGroup(ETreeNode rootNodeOfNewTree);



/**

* Removes a tuning group from the tree

*

* @param tableGroup

*/

public void removeTuningGroup(String tableGroup);



/**

* Prepends list of menu items to the menu bae

*

* @param items

*/

public void rebuildJMenuBar(Vector<JMenu> items);



/**

* If a tuning entity has a custom tool bar to add, call this method.

*

* @param theToolBar

*/

public void setNewToolBar(JToolBar theToolBar);



/**

* Return the number of maps that have changed belonging to the targeted tuning entity of the defined tableGroup

*

* @param tuningEntity

* @param tableGroup

* @return

*/

public int getMapChangeCount(TuningEntity tuningEntity, String tableGroup);



/**

* Has the main GUI kick off the process of saving table data.

*

*/

public void saveMaps();



/**

* Tuning entity calls back to main gui when its prepared for exit.

*/

public void readyForExit();

}



*Im lazy and didn't crop out my 2nd screen, so feh, enjoy the Simpsons*

What you see here is the new GUI with the partial support for the UTEC, which was left at about 75%. Gui changes are needed. BTW, that "S" button is the smooth button. Also, for those devs new to Eclipse, be sure to set your library path ala: "-Djava.library.path=/home/botman/workspace/enginuity/lib/logger/rxtx/linux/i686"

Get to it:
http://i189.photobucket.com/albums/z250/tgui_photos/Screenshot.png


Also, for those that bitch about the 3D... first off. Bite me ;) 2nd off, its based off alpha quality code that binds Java to OpenGL, hence the speed issues and possible memory leaks. Someone should check on the status of that project, it might be better now. 3rd, its not just a rendering/visualization tool, its a real time map editor that reflects changes back in Enginuity.

Short list of commands:
*mouse click cell selection
*shift key for multiple cell selection
*shift hold down plus arrow keys select boxes
*"ctrl-a" select all cells
*"/" full 2d smooth of selected area
*">" vertical smooth
*"<" horizontal smooth
*"F1 or F2" Select render mode
* Mouse wheel zoom in and out
* Mouse click drag to rotate

... Yes, looking under the graph looks strange. This is because I needed to cut down on the polygons to speed rendering. Someone can change this if desired.
Select cells, yes, background image sucks...
http://i189.photobucket.com/albums/z250/tgui_photos/Screenshot-4.png



Smooth data:
http://i189.photobucket.com/albums/z250/tgui_photos/Screenshot-5.png



Change render mode, yes needs work, maybe just wire frame, but the code is there.
http://i189.photobucket.com/albums/z250/tgui_photos/Screenshot-6.png


In any case, I'm busy, but will answer questions if there is an interest to pick things up. Grad classes start again soon so time will be limited for me.

There are other features lurking in the source code, like the RamTune features etc. I hope the devs working on that will speak up and explain those features and their current states.

-Eric-

OK, I gotta ask, what's the difference in the gui in the picture? It looks just like what I'm using now...

OK, I gotta ask, what's the difference in the gui in the picture? It looks just like what I'm using now...

Totally different code base thats NOT coupled to ROM editing. Its has table and tuning functionality put into a set of interfaces to make it easy to support a wide range of tools.

Also, the JInternalFrames are not custom components but derived fully from existing swing components.

The hope is that it would look similar ;)

Sounds like its definitely the way to go for hack / ram tuning image.

I'd also like to know some more about the ramtune function in its current form and future plans.

Totally different code base thats NOT coupled to ROM editing. Its has table and tuning functionality put into a set of interfaces to make it easy to support a wide range of tools.

Also, the JInternalFrames are not custom components but derived fully from existing swing components.

The hope is that it would look similar ;)

Ah, cool. I was thinking it was a front-end thing and I was Missing Something (TM). If it's all backend stuff, then I'm not totally oblivious.

1) So this map smoothing thing.... is it available in the 785 release or has it not made it that far yet?

2) What about map scaling?

here's the log file, I deleted the LC1 errors for clarity



0 INFO [AWT-EventQueue-0] - Plugin loaded: AEM UEGO v0.01
0 INFO [AWT-EventQueue-0] - Plugin loaded: Innovate LC-1 v0.02
16 INFO [AWT-EventQueue-0] - Plugin loaded: UTEC v0.01
858 INFO [Thread-3] - Error sending ecu init: Parameter portName must not be null or empty
1872 INFO [Thread-3] - Error sending ecu init: Parameter portName must not be null or empty
2886 INFO [Thread-3] - Error sending ecu init: Parameter portName must not be null or empty
3900 INFO [Thread-3] - Error sending ecu init: Parameter portName must not be null or empty
4914 INFO [Thread-3] - Error sending ecu init: Parameter portName must not be null or empty
6069 INFO [Thread-3] - Connected to: COM4
6303 INFO [Thread-3] - ECU ID = 1B14400505
6303 INFO [AWT-EventQueue-0] - CAL ID = A4SGC00C
6303 INFO [AWT-EventQueue-0] - Loading logger config for new ECU (ecuid: 1B14400505)...
6459 INFO [Thread-3] - Connection closed.
6600 INFO [Thread-3] - Connected to: COM4
6600 INFO [Thread-3] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]
22352 INFO [Thread-3] - Connection closed.
22352 INFO [Thread-3] - Disconnected.
23164 INFO [Thread-270] - Connected to: COM4
23366 INFO [Thread-270] - ECU ID = 1B14400505
23554 INFO [Thread-270] - Connection closed.
23679 INFO [Thread-270] - Connected to: COM4
23679 INFO [Thread-270] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]
83221 INFO [AWT-EventQueue-0] - Innovate LC-1: connecting
83371 INFO [AWT-EventQueue-0] - Connected to: COM6


625613 INFO [Thread-19813] - Connected to: COM4
625845 INFO [Thread-19813] - ECU ID = 1B14400505
625993 INFO [Thread-19813] - Connection closed.
626117 INFO [Thread-19813] - Connected to: COM4
626118 INFO [Thread-19813] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]



854711 INFO [Thread-25474] - Connected to: COM4
854939 INFO [Thread-25474] - ECU ID = 1B14400505
855069 INFO [Thread-25474] - Connection closed.
855196 INFO [Thread-25474] - Connected to: COM4
855197 INFO [Thread-25474] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]

905875 INFO [Thread-27043] - Connected to: COM4
906094 INFO [Thread-27043] - ECU ID = 1B14400505
906221 INFO [Thread-27043] - Connection closed.
906348 INFO [Thread-27043] - Connected to: COM4
906348 INFO [Thread-27043] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]
9
958427 INFO [Thread-27728] - Connected to: COM4
958660 INFO [Thread-27728] - ECU ID = 1B14400505
958791 INFO [Thread-27728] - Connection closed.
958912 INFO [Thread-27728] - Connected to: COM4
958912 INFO [Thread-27728] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]



1198918 INFO [Thread-34398] - Connected to: COM4
1199136 INFO [Thread-34398] - ECU ID = 1B14400505
1199151 INFO [AWT-EventQueue-0] - CAL ID = A4SGC00C
1199151 INFO [AWT-EventQueue-0] - Loading logger config for new ECU (ecuid: 1B14400505)...
1199323 INFO [Thread-34398] - Connection closed.
1199449 INFO [Thread-34398] - Connected to: COM4
1199449 INFO [Thread-34398] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]
1296245 INFO [Thread-34398] - Connection closed.
1296245 INFO [Thread-34398] - Disconnected.
1296963 INFO [Thread-38355] - Connected to: COM4
1297181 INFO [Thread-38355] - ECU ID = 1B14400505
1297337 INFO [Thread-38355] - Connection closed.
1297462 INFO [Thread-38355] - Connected to: COM4
1297462 INFO [Thread-38355] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]
1318653 INFO [Thread-38355] - Connection closed.
1318653 INFO [Thread-38355] - Disconnected.
1319590 INFO [Thread-38844] - Connected to: COM4
1319806 INFO [Thread-38844] - ECU ID = 1B14400505
1319962 INFO [Thread-38844] - Connection closed.
1320087 INFO [Thread-38844] - Connected to: COM4
1320087 INFO [Thread-38844] - Connected to: COM4; using protocol: SSM; conn props: ConnectionPropertiesImpl[baudRate=4800, dataBits=8, stopBits=1, dataBits=8, parity=0, connectTimeout=2000, sendTimeout=55]
1539770 INFO [Thread-38844] - Connection closed.
1539770 ERROR [Thread-38844] - Error occurred
enginuity.logger.ecu.exception.SerialCommunication Exception: enginuity.logger.ecu.exception.InvalidResponseExce ption: Invalid header. Expected: 80. Actual: 00.
at enginuity.logger.ecu.comms.io.connection.SSMLogger Connection.sendAddressReads(SSMLoggerConnection.ja va:81)
at enginuity.logger.ecu.comms.manager.TransmissionMan agerImpl.sendQueries(TransmissionManagerImpl.java: 61)
at enginuity.logger.ecu.comms.manager.QueryManagerImp l.sendEcuQueries(QueryManagerImpl.java:209)
at enginuity.logger.ecu.comms.manager.QueryManagerImp l.runLogger(QueryManagerImpl.java:189)
at enginuity.logger.ecu.comms.manager.QueryManagerImp l.run(QueryManagerImpl.java:128)
at java.lang.Thread.run(Unknown Source)
Caused by: enginuity.logger.ecu.exception.InvalidResponseExce ption: Invalid header. Expected: 80. Actual: 00.
at enginuity.io.protocol.SSMResponseProcessor.assertE quals(SSMResponseProcessor.java:88)
at enginuity.io.protocol.SSMResponseProcessor.validat eResponse(SSMResponseProcessor.java:61)
at enginuity.io.protocol.SSMResponseProcessor.extract ResponseData(SSMResponseProcessor.java:72)
at enginuity.logger.ecu.comms.io.protocol.SSMLoggerPr otocol.processReadAddressResponses(SSMLoggerProtoc ol.java:69)
at enginuity.logger.ecu.comms.io.connection.SSMLogger Connection.sendAddressReads(SSMLoggerConnection.ja va:78)
... 5 more
1539770 INFO [Thread-38844] - Connection closed.
1539770 INFO [Thread-38844] - Disconnected.
1539896 INFO [Thread-38844] - Connected to: COM4
1540156 INFO [Thread-38844] - Connection closed.
1540156 INFO [Thread-38844] - Error sending ecu init: Parameter processedResponse must not be null or empty
1541170 INFO [Thread-38844] - Error sending ecu init: Unable to resolve port: COM4
1542184 INFO [Thread-38844] - Error sending ecu init: Unable to resolve port: COM4
1543324 INFO [Thread-38844] - Connected to: COM4
1543552 INFO [Thread-38844] - Connection closed.
1543552 INFO [Thread-38844] - Error sending ecu init: Parameter response must not be null or empty
1544692 INFO [Thread-38844] - Connected to: COM4
1544921 INFO [Thread-38844] - Connection closed.
1544921 INFO [Thread-38844] - Error sending ecu init: Parameter response must not be null or empty
1545935 INFO [Thread-38844] - Error sending ecu init: Unable to resolve port: COM4
1546949 INFO [Thread-38844] - Error sending ecu init: Unable to resolve port: COM4
1548089 INFO [Thread-38844] - Connected to: COM4
1548512 INFO [Thread-38844] - Connection closed.
1548512 INFO [Thread-38844] - Error sending ecu init: Parameter response must not be null or empty
1549791 INFO [Thread-38844] - Connected to: COM4
1550054 INFO [Thread-38844] - Connection closed.
1550054 INFO [Thread-38844] - Error sending ecu init: Parameter response must not be null or empty
1696742 INFO [Thread-38844] - Connected to: COM4
1698988 INFO [Thread-38844] - Connection closed.
1699877 INFO [Thread-38844] - Connection closed.
1699878 INFO [Thread-38844] - Error sending ecu init: java.io.IOException: Input/output error in writeArray


Do I need anything selected in the logger? I've tried selecting everything related to MAF scaling and no joy.

Ah, cool. I was thinking it was a front-end thing and I was Missing Something (TM). If it's all backend stuff, then I'm not totally oblivious.

1) So this map smoothing thing.... is it available in the 785 release or has it not made it that far yet?

2) What about map scaling?

Not available yet as someone needs to implement the functionality to actually edit ROM images. As of now its hidden and only works on Utec maps.

It goes something like this:

1. Hook up to your car
2. open enginuity
3. load your rom
4. start the logger
5. go to the MAF tab
6. set up the data record trigger conditions (defaults are pretty good)
7. hit 'record data'
8. go for a good drive (you need lot's of data)
9. hit 'record data' again to stop recording
10. use the interpolate button and order number to get a good fitting curve with the data
11. select the mafv range you want to apply the changes to
12. hit apply to have the changes applied to your maf scaling table
13. go to editor and save your rom
14. flash to car
15. repeat steps 7 to 14 until you're happy with the rescaling.

Man this is so cool Kascade. Does it work on the 32 bit ECU as well? I haven't messed with the new test release yet. :D

It takes me forever to rescale the MAF by hand. ;)

Gabe

pardon my ignorance....but what am I supposed to download from that link in the first post? once I get it, what am I supposed to do with it?

I was hoping for a "click to install" button.

Click here to download the ZIP file

http://www.assembla.com/spaces/enginuity/documents/dgq_GmWnKr3isFabIlDkbG/download

Save that and extract the files from the zip into a folder. Go into folder and click on run.bat which is a batch file that runs the Java

OK, I have a follow up to the stuff about the MAF tool in 785. Check out http://forums.nasioc.com/forums/showpost.php?p=20726553&postcount=20 and tell me what you think of the discrepancies I'm seeing.

pardon my ignorance....but what am I supposed to download from that link in the first post? once I get it, what am I supposed to do with it?

I was hoping for a "click to install" button.
The link is to the subversion repository. What you need to do is install rapid svn (free) and then point it to the url in the link. Once done, click "update" and it will download everything for you.

kascade, how is the polyfit achieved? Is it best fit for the total data set? Best fit of the averages per MAFv? Best fit of the modes per MAFv?

Tried the MAF scaling tool yesterday for the first time - works like a dream and ironed out some minor discrepancies in closed loop fueling for me. Great tool and saves no end of leg work.

kascade, how is the polyfit achieved? Is it best fit for the total data set? Best fit of the averages per MAFv? Best fit of the modes per MAFv?

it is achieved via a numerical analysis of the total dataset. no fancy stuff.

I tried this out this morning, but I forgot to change the user level so when I hit save it didn't save the changed scaling. I was already halway through finishing scaling my MAF and it was almost done. The small changes it made seemed perfectly correct (My AFL ranges are already +/- 5%). Argh! I'll have to redo it now. I should have been logging at the time too. Great tool! I am rescaling for the APS 65 MM CAI.

I have gone through 2 iterations so far (about to flash the second one and the line is getting flatter). Of course I almost had it all dialed in by hand already, but this tool really helps to speed things up. ;)

how are you making this work...I keep getting interpolation errors? and no data shows up....except for one little dot.

I launch it, hit the start recording button, hit the log button, hit stop (both logging and recording button) when i get to work and then click interpolate. I have my current map open in enginuity before I start, and I click apply changes before shutting the logger off, then I save the rom.

Gabe

Subscribed!

Awesome. I'ma go home tomorrow and give it a whirl...
My friggin MAFv prolly looks like this right now /\/\/\/\/\/\/\/\/\ :lol:

subcribed kascade your awesome. thanks

kascade, I presume that since you're calculating the polyfit after logging is over that somewhere there's an array of all the sample points. How hard (programatically) would it be for the tool to calculate the modal correction at each voltage and represent it on screen as a colored dot? The user could then pick the poly order which sent the fit closest to the modal points.

kascade, I presume that since you're calculating the polyfit after logging is over that somewhere there's an array of all the sample points. How hard (programatically) would it be for the tool to calculate the modal correction at each voltage and represent it on screen as a colored dot? The user could then pick the poly order which sent the fit closest to the modal points.

I don't believe it would be too difficult. Same goes for adding the extra filter options you suggested such as max IAT and rate of change which are great ideas. My biggest problem is time.. work.. kids.. wife... other projects... you know how it goes.

nevertheless i'll see what i can do.

I don't believe it would be too difficult. Same goes for adding the extra filter options you suggested such as max IAT and rate of change which are great ideas. My biggest problem is time.. work.. kids.. wife... other projects... you know how it goes.

nevertheless i'll see what i can do.

I asked about the modal points being highlighted because I thought that was the least work for you to implement that would give the biggest benefit to the user. Probably next after that would be doing a polyfit of the modal points. THEN filtering the data as that can be somewhat done "by hand" as the logging is done.

But yeah, I know all about real life and pet projects.

It goes something like this:

1. Hook up to your car
2. open enginuity
3. load your rom
4. start the logger
5. go to the MAF tab
6. set up the data record trigger conditions (defaults are pretty good)
7. hit 'record data'
8. go for a good drive (you need lot's of data)
9. hit 'record data' again to stop recording
10. use the interpolate button and order number to get a good fitting curve with the data
11. select the mafv range you want to apply the changes to
12. hit apply to have the changes applied to your maf scaling table
13. go to editor and save your rom
14. flash to car
15. repeat steps 7 to 14 until you're happy with the rescaling.

Yeah, so I followed the steps, verbatim, and never saw anything but one orange or pink point on the black graph, after 20 minutes of cruising 60mph. This was with all defaults..
WTF am I doing wrong?

Also, i tried it in the driveway, for about 10 minutes, and got absolutely nothing. I know it's something I'm doing wrong...

Yeah, so I followed the steps, verbatim, and never saw anything but one orange or pink point on the black graph, after 20 minutes of cruising 60mph. This was with all defaults..
WTF am I doing wrong?

Also, i tried it in the driveway, for about 10 minutes, and got absolutely nothing. I know it's something I'm doing wrong...
In Dashboard view, bring up all of the data the MAFTool will exclude based upon. Make sure the ECU thinks all the requirements are being met.

Also, are you running the most current logger defs with the 785 build?

In Dashboard view, bring up all of the data the MAFTool will exclude based upon. Make sure the ECU thinks all the requirements are being met.

Also, are you running the most current logger defs with the 785 build?

I d/l 785 and the defs at the same time, so yeah..

I'm not really sure what you mean, by your statement about the dashboard view, above.. Exclude based upon? Ive got no idea..:(

silly m istake - all good now :P

Update:

This is how easy it was to scale my MAF (for an APS 65 mm CAI).

The scaling was off so much, and I like scaling my MAF by changing G/S, not voltage. This is what I did:

Reset the ECU after installing APS CAI. Waited until all 4 fueling ranges were filled. They were like this:

A: +15
B: +12
C: +17
D: +1

After rough scaling with those ranges, it took 3 iterations of using the MAF tool to get it like this:

A: -4 (you want A to be negative)
B: +2
C: +3
D: -0.7

Of course they vary some, but this is to be expected.

Nice tool.

Gabe

:D

<---- jealous of ^^ ability to get the tool to work ;)

It hits nicely now when stomping the gas with little to no knock. :D

With much positive AFL, the ramp time is about two seconds, so it would go wayyy rich before hitting the correct target AFR. Much better now. :D

FYI guys I noticed there is a site up to replace enginuity

www.romraider.com

You have to register on the forums to download

FYI guys I noticed there is a site up to replace enginuity

www.romraider.com

You have to register on the forums to download

Lol :lol:

useful faq

http://www.scoobypedia.co.uk/index.php/Knowledge/RomRaiderAndReflashingFAQ