why am i having so much trouble with ectune??

non-vtec · Post by **non-vtec** » Tue Jan 01, 2008 7:58 pm

hi guys i spent the whole afternoon trying to get my car running on ectune and all I'm left with is a car that wont start now. i can't even load my old tuned uberdata bin since my ostrich is locked with a different firmware. i keep getting a incorrect ostrich version when i try. and to top it all off moates removed all the old firmware from the website so i can't even put it back to how it was originally

i do not understand what I'm doing wrong when it comes to creating a proper base map. i followed the steps. entered the correct map sensor and correct fuel injector size and saved the calibration. technically it should start and run off that base map. right....hmm....wrong....

I'm not a \"professional tuner\" but i have been tuning my own setup with uberdata for well over 4 years with no real major issues. i know i can figure ectune out.

here is what i did: i connect to the emulator in ectune. it says connected at the bottom of the screen. i select upload calibration. it loads up and everything appears to load correctly. but with key on engine off the MIL light stays on solid. i can crank the engine but it will not fire. i tried it multiple times with the same results. i tried to jump the 2 pin connector to get the CEL to blink but it just stays on solid. it does NOT flash. and will not go out. hardware: USDM P28 ECU (i set it up as a CDM ECU could this be a problem?) Ostrich V1 flashed with firmware 18 engine setup: B20/VTEC/Turbo AEM 3.5bar map sensor rc750cc injectors all other original sensors/connectors plugged in and working. (engine was running fine before the ectune installation attempt) the only think i can possibly think may cause this problem is port settings perhaps for the ostrich? i searched but could not find any port settings on moates website or on here. or is there any port/sensor settings i overlooked inside ectune? i attached my calibration file if someone wants to have a quick look at it. i don't think there are any errors what would cause a solid CEL and no start condition. i am currently waiting for Calvin to re-register my ostrich again as reset it so i can load my old tuned bin back on..but that wont work so my car is stuck in the driveway cuz it wont run. i gotta pick up my chip burner from my friend and load the old tune onto a chip tomorrow just so i can move the car. so what am i doing wrong? do i have to have the key on engine off when loading a cal file? does it matter? any help input will be GREATLY appreciated.

Post by **Bugermass** » Tue Jan 01, 2008 8:35 pm

if your cel stays on then either your ostrich isn't getting the data from eCtune or the ECU isn't reading the ostrich.. Have you checked to see if the ROM will verify after you upload it to the ostrich? If it does verify then try reseating your ostrich in the ECU.. Are you using ostrich 1 or 2?

non-vtec · Post by **non-vtec** » Tue Jan 01, 2008 8:43 pm

thanks burgarmas. ectune \"says\" its connected and it \"shows\" that the calibration gets loaded and all looks normal. if i try to verify rom it says ecu not connected even though ectune says connected? ostrich 1

Almighty-Si · Post by **Almighty-Si** » Tue Jan 01, 2008 9:22 pm

From what I see you had forgot to check off a few things in the parameters like disable O2 heater and closedloop only checkboxes. Here is your cal back with the boxes checked...open your injector calibration just before you start your car also cause it will probably run lean when it starts.

Post by **calvin** » Tue Jan 01, 2008 9:45 pm

it shouldn't solid cell.. My guess your ecu is not reading from the ostrich. Or ectune doesn't upload. Verify should work with your 10.18 firmware

non-vtec · Post by **non-vtec** » Tue Jan 01, 2008 9:54 pm

Almighty-Si wrote:From what I see you had forgot to check off a few things in the parameters like disable O2 heater and closedloop only checkboxes. Here is your cal back with the boxes checked...open your injector calibration just before you start your car also cause it will probably run lean when it starts.

thanks i'll give that a try but i dont think having closed loop dissable and o2 heater dissable will do anything.........all those things are/were hooked up and working properly before. for some reason i think calvin is right.....the ecu is not communicating to the ostrich but it makes no sense why as it was working perfectly before.... any suggestions on what the port settings should be for the ostrich?

Post by **calvin** » Tue Jan 01, 2008 10:01 pm

what port settings? Baud should be 921600 put a hardcoded comm [port(disable auto0scan) That is all i can say. After u connect the ostrich in ectune please send me a screenshot. Is the ostrich \"paired/licensed\"? Is the color green where there is \"emulator: connected\"

non-vtec · Post by **non-vtec** » Tue Jan 01, 2008 11:07 pm

calvin wrote:what port settings? Baud should be 921600 put a hardcoded comm [port(disable auto0scan) That is all i can say. After u connect the ostrich in ectune please send me a screenshot. Is the ostrich "paired/licensed"? Is the color green where there is "emulator: connected"

ok I'll set the baud settings manually and try again. I'll take screen shots of the ostrich after it's connected. I'm pretty sure it says connected and it looks like it successfully uploads the calibration but something else it wrong. Calvin i need you to re-send the ostrich license. i emailed u the request.

Almighty-Si · Post by **Almighty-Si** » Tue Jan 01, 2008 11:31 pm

Really? I always get a solid CEL if I don't have them either checked. When I had my narrowband installed and disconnected the line to install my wideband I got a CEL. Unchecked both and CEL gone. Guess I should run through my own setup huh? LoL

z31 · Post by **z31** » Wed Jan 02, 2008 12:01 am

I believe he just never got the ostrich paired correctly, that's all. On a side note though, I've also gotten the solid cel before but with no actual codes. It's happened on other tuning programs also. If it happens try to take the key out and try to start again. If that doesn't help it then take make a new rom and import your .cal to it. This has always fixed it for me. I can't really explain it since it only happened once, but I'm pretty sure it had something to do with the ostrich and not the program since the program gets me to work every single day.

non-vtec · Post by **non-vtec** » Wed Jan 02, 2008 12:22 am

calvin wrote: Is the ostrich "paired/licensed"? Is the color green where there is "emulator: connected"

i think this is the problem.? it said emulator connected but it's in all red letters.......i used the license.xml file you sent me so i assumed everything was correct. it even said ostrich licensed true in the ostrich info window?? i ended up resetting the ostrich so now i need a new OST license registration file to try it over again....

Post by **calvin** » Wed Jan 02, 2008 1:05 am

i'll resend the license now

Bindegal · Post by **Bindegal** » Wed Jan 02, 2008 2:35 am

Another thing. When you get the OstrÃch running properly, you may find that it still wonÂ´t start because the spark pliugs are (or were) wet. I find that NGKÂ´s are often killed off permanently by drowning in fuel. I would replace those pliugs with a set of used known-good or new ones before trying to start it up again. /Allan

non-vtec · Post by **non-vtec** » Wed Jan 02, 2008 9:13 pm

ok calvin sent me a new license file and all appears to be working correctly. ostrich is paired. uploads and verify's calibration. all seems to be working good. i wont be able to test or tune the car until the weekend. it's supposed to be -20 overnight tonight and -15 tommorow for the high so i dont feel like freezing my ass off messing around with the tune. i'll get to it this weekend.

Post by **calvin** » Wed Jan 02, 2008 9:22 pm

good stuff.. happy it's ok now