eCtune will not open out of the blue/Emulator problem(Fixed)

mtber · Post by **mtber** » Mon Dec 03, 2007 4:41 am

Just to double check I did another complete factory system restore. Ran windows update, installed frameworks 2.0 Tried r5 orig & the test release you just sent me. Burn1 works fine, Ostrich won't connect with auto detect or with manual port selection. Crome connects just fine & lets me upload etc.. _________________________________________________________ comErr.txt 12/3/2007 12:29:00 AM,Emulator Notification - Can't dectect \"Ostrich_1_2\" on port: COM5 12/3/2007 12:29:16 AM,Emulator Notification - Can't dectect \"Ostrich_1_2\" on port: COM5 _________________________________________________________ Comm_Trace.txt Emulator Auto-Scan: 12/3/2007 12:33:55 AM Port scan thread Try Cached port Cached port failed with Object reference not set to an instance of an object. Port open and check emulator=False Port open and check emulator=False Port Scan Failed at port 30 _________________________________________________________ Everything was working fine when I was using v0.0.2.0 (first release) Is there any way I can get the original v 0.0.2.0 to test with ? The only issue I had with v 0.0.2.0 (first release) was a random code 10 on two cars. I have yet to try using the disable stock ve and closed loop code feature for those cars. Thank You, John Vega

mtber · Post by **mtber** » Mon Dec 03, 2007 6:04 am

For the record I tried another ostrich 1 brand new in the box that I have as a backup. It showed the same exact issue. It will connect to everything but eCtune.

Post by **calvin** » Mon Dec 03, 2007 9:28 am

cached port error is normal. But it walks through all the ports and try to find the ostrich. What you can do. Remove all ftdi driver. there is a tool fdi clean. reinstall them and try again.

Post by **calvin** » Mon Dec 03, 2007 9:39 am

i just arrived home from a very long flight. I test with ostrich 1 and ostrich 2 no problems connecting. I did like 10 uploads and 5000 byte changes. I'll add more debug info for testing like i did with the datalogging debug window.

mtber · Post by **mtber** » Mon Dec 03, 2007 12:39 pm

calvin wrote:cached port error is normal. But it walks through all the ports and try to find the ostrich. What you can do. Remove all ftdi driver. there is a tool fdi clean. reinstall them and try again.

I will try the ftdi clean, however the install is only a few hours old. Moates's ftdi usb drivers on his website are from 2004....

mtber · Post by **mtber** » Mon Dec 03, 2007 12:40 pm

Like I said before, if I could get you to send me a version of the original v 0.0.2.0 to try that would be great, or even v 0.0.1.9 r3

Post by **calvin** » Mon Dec 03, 2007 12:50 pm

please use the driver from FTDI or from my forum. Those are old... I doubt that it's the problem. Well i have to go search in backups... I don't know the 00020r0 i should have it but no backups here... I'll find what it is. But the emulator thing is real easy and shouldn't give problems... How about the baud?

mtber · Post by **mtber** » Mon Dec 03, 2007 12:53 pm

calvin wrote:please use the driver from FTDI or from my forum. Those are old... I doubt that it's the problem. Well i have to go search in backups... I don't know the 00020r0 i should have it but no backups here... I'll find what it is. But the emulator thing is real easy and shouldn't give problems... How about the baud?

I switched the baud around, no luck.

mtber · Post by **mtber** » Mon Dec 03, 2007 1:08 pm

Tried the updated ectune ftdi drivers. No changes, crome connects to and uploads just fine. eCtune produces the same error \"Can't detect Ostrich_1_2\" on port: COM5 I switched the ports around to make sure it was not the USB port, I tried 2 ostrich v1 units, one which is brand new. Both work in hondata & crome. Thanks, John Vega

Post by **calvin** » Mon Dec 03, 2007 1:22 pm

which ftdi driver version you have? I suspect something with the .net framework to be honest. I use .net framework for serial port. I found out it's really messed up. After debugging something with moates. I have a new serial port dll i can buy. but involes a lot of coding. How come i don't have that problem here neither to others. Chirs, You, 1 more guy had some problems. It gets me f*** mad

Bindegal · Post by **Bindegal** » Mon Dec 03, 2007 1:59 pm

This is weird. I did some wiring and initial tests on a customer car yesterday. I used R5 to fire it up, and I didnÂ´t notice anything out of the ordinary. Ostrich1, logging and Burn1 all worked well. /Allan

mtber · Post by **mtber** » Mon Dec 03, 2007 5:47 pm

calvin wrote:which ftdi driver version you have? I suspect something with the .net framework to be honest. I use .net framework for serial port. I found out it's really messed up. After debugging something with moates. I have a new serial port dll i can buy. but involes a lot of coding. How come i don't have that problem here neither to others. Chirs, You, 1 more guy had some problems. It gets me f*** mad

I don't understand why this is an issue. As I just told you it worked FINE on the older versions of eCtune, this is the first time Chris or I have had issues... I tried the moates version of ftdi driver which was working fine from 2004.... I also have tried the version http://www.ftdichip.com/Drivers/CDM/CDM ... tified.zip Like I said, I have tried a FRESH install of windows & frameworks.

Post by **calvin** » Mon Dec 03, 2007 5:50 pm

i mailed the first 0020r1 version. Test please. I also have r6 with plenty debug so we can see what's going on.

mtber · Post by **mtber** » Mon Dec 03, 2007 6:19 pm

calvin wrote:i mailed the first 0020r1 version. Test please. I also have r6 with plenty debug so we can see what's going on.

Testing now.... I will report back in 10 minutes.

mtber · Post by **mtber** » Mon Dec 03, 2007 6:24 pm

Glad to report that 0020r1 WORKED FINE! Connected without an issue, uploaded without an issue! The next issue is trying to figure out why r5 flipped out and decided to stop opening & stop working with the ostrich out of the blue.