Page 1 of 1

DIY tuning with eCtune

Posted: Sat Nov 17, 2007 8:51 pm
by borat
I've spent about a week now playing with ectune, and here are my impressions. Keep in mind that I am not a professional tuner, and only have experience tuning my own vehicle with Uberdata and crome over the past 2 years. Also, ectune has very little documentation at this point, so all my tuning was done while figuring out what various things did. Here we go: :arrow: Basemap creation is very intuitive. Boost table creation and injector adjustments are made when opening a basemap. I have a prelude, so the fuel maps were way off, but that is to be expected. :arrow: The fuel/ign tables are smaller in size (pixels, not actual rows/columns) than other software, which lets you have more room for datalogging graphs and sensor info. :arrow: Datalogging is amazing with ecune. Sensor info is configurable, so you can tailor the display to your liking while logging. I'm also getting almost twice the samples per second that I was getting with other software. :arrow: The datalog graphs are simple to use, customizable, and work exactly as I expected them to. Very useful! :arrow: The number of options for configuring your tune are staggering. I spent probably a good 30 minutes clicking through all the options just to figure out which ones I could and couldn't use. :arrow: The ECU code itself seems much more solid than other software. I used to have horribly rich startups that I spent hours trying to iron out with crome, and nothing I tried worked. The AFR would start at 9 or 10, and slowwwwwly work its way up to the 14's. Now, the car fires up with to within 1 AFR of what I want every time. :arrow: Using the auto-adjust worked pretty well to get my AFRs close to what I wanted when I started tuning. :arrow: Closeloop mode with wideband input works alright, though it doesn't seem any better than openloop to me. Need to test this one more. Overall, tuning with ectune has been great. I didn't run into any show-stopping bugs at all. It did crash once or twice, but I was unable to reproduce the cause, and it never crashed during datalogging. Here are my suggestions: :idea: DOCUMENTATION! There is a severe lack of documentation with current DIY tuning programs. This could really put eCtune above and beyond even more than it already is. :idea: Status indicator when creating basemap: When you click 'Finish' to make a basemap, it just sits there like nothing is happening for 10 seconds or so. The first time I did it, I thought something was wrong. :idea: Shortcut key to apply the suggested fuel correction when you highlight just one cell. Currently it only works for 2 or more. Also, where is the auto-tune? Would have saved me a lot of time to let ectune auto-correct as I drove in the map regions I specified, instead of having to pull over and apply the auto-corrections manually. If it exists, I couldn't find it! My setup: -1999 Prelude base, 5MT -JRSC kit, 6-8psi during boost on the datalogs -p28, cellphone-usb datalog cable (prolific chip) -Ostrich v1 -Innovate LC-1

Posted: Sun Nov 18, 2007 12:31 am
by calvin
when using h22 maps you should have a multiplier of 1. so you change old and new injector size to 290/33. Good report though.. thanks.. Documentation will come. twice the amount of sample and how about 3 or 4 times the amount of data for datalogging. No auto-tune will come. Maybe much later but not now

Posted: Wed Nov 21, 2007 7:47 am
by calvin
twice the amount of samples and the data that i get from the ecu is 3-4 times as much. Btw i fixed ectune with old injector size. When creating a h22 map. Old size is now 330, new size 330. and fuel maps are much closer fixed in r5