Require help with connecting eCtune to ECU...

Targa4life · Post by **Targa4life** » Mon Aug 31, 2009 9:48 pm

I just got my car finished and ready to start tuning and I am running into a number of problems with eCtune. I have the Dyno in less than 24 hours and need your help urgently with this. Our first main problem is that we can not get the datalogger to connect. I have the Moates Hondalog and I am using the same ECU as I have for years. When we try to connect it gives us a weird error saying \"Object reference not set to an instance of an object\" We looked it up on Google and as far as we can tell its some kind of .NET framework bug or something. We tried to roll back the drivers on the com ports, also tried changing the baud rates, even tried closing all graphs in eCtune but nothing has worked.... We know that eCtune says to set the datalogger port to a 38400 baud rate but still noting... Now the strange thing is that it does says however that its connected to the ECU when we hit the \"Test\" button. However it still gives us the same error when trying the \"connect\" button and we get no info from the ECU. The other big problem that we have is the rate at which the live tuning is updating to the ECU. (since the Ostrich can connect) when we make an adjustments it takes a very long time for it to upload the changes to the ecu. Down bottom it would be counting down numbers and if we made several at once it would take as long as a minute to make the changes. I can not see this being correct... Crome was much much faster than that at updating. When I make a new calibration it updates to the Ostrich very quickly. But if you make adjustments within the tune than it takes forever. Appreciate any help you guys can give. In a bit of jam with this....

Targa4life · Post by **Targa4life** » Tue Sep 01, 2009 2:34 am

I should also note: -P28 ECU -Moates Ostrich 1 -Hondalog Datalogger cable -Old ass IBM laptop (2001 or 2002 year model) with windows XP.

Post by **calvin** » Tue Sep 01, 2009 8:36 am

datalogging problems i would advice follow the debug steps on wiki.ectune.com make sure a rom is uploaded and you have 3 mil flashes after key on... to be sure you are running ectune in the ecu make sure j12 is removed.. Goto device manager comm port advance settings set latency for hulog/ostrich to 2

Targa4life · Post by **Targa4life** » Tue Sep 01, 2009 11:53 am

J12 Is cut, I haven't changed anything since using Crome. Ok I tried changing the Latency to 2 Also, tried to run the Ftclean program but it doesn't work. The only thing I could do was run the automatic Driver updater for the FTDI. I checked and the mil does flash three times with Key on Engine Off. The error I keep receiving is the \"Object reference not set to an instance of an object\". Like I said before, when under the settings I try to test, it says \"Found ECU\" or \"connected to ECU\" or something like that. Under the Device manager on my laptop the Driver details are: Provider: FTDI Date: 2/17/2009 Version: 2.4.16.0 Provider is : Win DDK As for my .NET framework, how do I go about updating this? Or making sure it is up to date?

Targa4life · Post by **Targa4life** » Tue Sep 01, 2009 2:23 pm

Ok, Ive run a number of windows updates on my laptop. Included was a number of .NET framework updates. But I still have the same issue. I am beginning to think this is a problem specific to my laptop. I'm thinking that it has to do with my drivers. As I said before I think I may have botched the FTDI driver clean and install... If anyone has a suggestion as to why when I run the FTDI clean program it tells me why I do not have permission... I am running as the admin and I have even tried using safe mode to do it...??? Its strange that when I test, it says Found ECU but when I press the connect button it gives me that weird error...?

Targa4life · Post by **Targa4life** » Tue Sep 01, 2009 3:14 pm

Ok, I just successfully ran the FT clean program and updated the drivers precisely as indicated. I was hopeful that was the problem but it still says \"found ECU\" but when I go to connect it gives me the error.... I ran the debug test and these were the results: Manual: DTL: baud: 38400 DTL: try to open port: COM6 DTL: port: COM6 open: True DTL: Ecu replied correct handshake byte Auto: DTL: Auto-Scan DTL: Ecu detection started DTL: baud: 38400 DTL: Cached port:6 DTL: Cached port: 6 open DTL: Ecu replied correct handshake byte DTL: ECU-ISR found

Post by **calvin** » Tue Sep 01, 2009 4:46 pm

FTLCLean as per instruction will clean all ftdi drivers... just install the latest... it would be nice to know what version you have before? so i can debug the error you get.

Post by **calvin** » Tue Sep 01, 2009 4:55 pm

happy it's solved

Targa4life · Post by **Targa4life** » Tue Sep 01, 2009 5:04 pm

Pm sent Calvin. Thanks for helping. Hopefully I can get this working tonight.....

Targa4life · Post by **Targa4life** » Wed Sep 02, 2009 10:01 pm

Tried another datalogger and still gives the same error...

Targa4life · Post by **Targa4life** » Sat Sep 05, 2009 11:56 am

Ok, after a hell of a lot of trouble.....

Must have been something wrong/incompatible with my laptop. Calvin would have needed to go in a debug it for but it wouldn't have been done in time... So I took eCtune and installed it on another laptop (a newer one) and imagine that... It works..... So, if anyone else has this trouble and can't get it figured out. Try using another laptop.

joltofwf · Post by **joltofwf** » Sun Sep 06, 2009 12:26 pm

can't wait for targa newfoundland :p

Targa4life · Post by **Targa4life** » Sun Sep 06, 2009 12:39 pm

Me neither... http://www.youtube.com/watch?v=j_X5eSCQtuA

Targa4life · Post by **Targa4life** » Mon Sep 07, 2009 12:26 pm

Dyno today.. Everything worked well. Made more than enough power. 312whp 260ish torque. Lowered the boost to 13psi this year and played more with the mid range than top end. Overall the A/F are rock solid. No complaints here except for the harshness of the rev limiter.... Posted a separate topic about it. go team go.

Post by **calvin** » Wed Sep 09, 2009 2:04 pm

try using Fuelcut only instead of ign cut