eCtune

hackish wrote:1)Reset check engine does not appear to work. A car that I tuned threw a vtec spool and the only way to reset it was keyoff and keyon. Then a different car threw an IAC code, again, right clicking on the error code dialog and selecting clear codes did not accomplish anything. 2)Datalogger "test" button under settings will mis-report an ECU connection if J12 is still present. It will also randomly fail. I think the protocol should detect if it's getting an echo of what it sends and inform the user rather than claiming a successful ECU connection. 3)Whenever the computer goes to sleep or hibernates datalogging will not reconnect until you unplug and replug the USB cable. 4)If you enter a decimal (yes I was trying to break it) in the RPM cell it pops up with "invalid table entry" and when you click the "ok" button it pops up with the same dialog and the only way to get out is force kill ectune. In my test I entered 1500.6 RPM. 5)When I try to edit the RPM it is in the native format but the MAP values are in their RAW format so if you want a column for 5 psi you have to try a bunch of raw values until you can find the raw that corresponds to 5 psi. 6)If I hit the "g" button it correctly selects the proper cell but using arrow keys to go to the adjacent cell goes somewhere else. I suspect you're not updating all the variables and it remembers the last selected position. 7)If you change the baudrate in settings and then click test it does not appear to change the baudrate until you hit save to close the dialog and go back in. I still have to test this in a terminal program though. 8)On earlier map file revisions the hot RPM gear based rev limiter shows random values and does not do anything. Maybe it should be disabled... or maybe older non-supporting map files will never end up being used... 9)Boost cut seems to cause odd behaviour when hit... The engine will die for a few seconds rather than coming back to life as soon as the MAP value drops below the limit. This is using the limit at 1200 rpm feature. As I posted somewhere else the current RPM limit does not make sense. If I'm overboosting I want to cut no matter what RPM I'm at! 10)Boost cut allows us to select the boost pressure in PSI but not edit it. I think if you can use the same sort of solution here as the map column editor you can allow edits in the native units. Kill 2 birds with 1 stone. 11)In the injector calibration tab of parameters there is a typo in the Note: section... "Overall fuel trim can be used to add/subtract fuel op top of injector trim" That's all I found so far. -Michael

hackish wrote:#5 when I click on let's say the 7 psi column it only allows me to edit the number as 1550 or something like that. I want to enter 8.5psi but I can't. Instead I have to spend 5 minutes guessing... is it 1630? 1615 etc. -Michael

hackish wrote:For #9 I think that's wrong. When I did the OBD0 stuff I just set the rev limiter to 1200 RPM. When this was moved to OBD1 they just copied my methodology. The computer is quick enough to catch an overboost so it should just stop injecting/firing until the MAP value drops. There is no reason to wait until 1200 rpm. I ran into this issue with a customer. He was merging on the highway and hit the boost cut. Normally we would have been safe with him backing off a bit on the throttle but the engine just cut out and wouldn't run with a semi bearing down on us. I guess now it must have been waiting for 1200 rpm or something... Fortunately I reached over and flipped the key off and on quick enough that we got out of the way. -Michael

Synoptic wrote:

hackish wrote:#5 when I click on let's say the 7 psi column it only allows me to edit the number as 1550 or something like that. I want to enter 8.5psi but I can't. Instead I have to spend 5 minutes guessing... is it 1630? 1615 etc. -Michael

because it uses mbar...

Bugermass wrote:Yeah I have the same problem trying to set boost cut, I have to keep entering in mbar values until I get the PSI I'm shooting for.. The reset DTC in the drop down menu under.. I think tools? worked last time I used it, I can't remeber if that was on r1 or r2...