eCtune

So I had a problem yesterday trying to connect to a car previously tuned... Ostrich connected fine the first few times and uploaded fine and then just stopped working. No amount of setting COMs, using Auto or manaully setting worked. It just wont connect anymore... I thought this was a fluke with my equipment, but then John Vega called me tonight and he had the same exact problem in the middle of tune on the dyno. Whats up with that?

i'm not aware of problems what happens. between r4 and r5 there no emulator changes. most of u had r4 already

Well its happened to two people in one day...can you please look into it? Any suggestions on what to do? Thank god I dont have any cars to tune...

my get rom/verify option never worked. not a big deal for me tho.

well... I can loook but if i don't know what excatly happen it's hard. Verify rom doesn't work because of timing/speed of pc. But that will be solved shortly. I'll use a new serial port libary

I had some what a similar problem. My Ectune showed my Ostrich was connected but it would not update the ECU. I had opened Ectune, plugged in the ostrich and datalogging cables (datalogging wouldn't connect either) clicked connect on the program and it said emulator connected, opened the .cal and clicked upload turned the key and solid CEL. With the key on clicked upload, cycled the key still solid CEL. After alot of closing out the program, reloading the .cal, unplugging and plugging back in the ostrich and restarting the computer it just decided to start working and I got the car started. Datalogging wouldn't connect at all with the auto-scan checked. I had to set the port myself to get it to start working, not all that big a deal but just thought I would add. I never did get any kind of error pop-up or anything otherwise I would have taken a screenshot and posted it up for you to look at but, that was just what happend to me today, thought I would post up my experience to see maybe if it can help.

auto-scan datalogging bug has been fixed

calvin wrote:well... I can loook but if i don't know what excatly happen it's hard. Verify rom doesn't work because of timing/speed of pc. But that will be solved shortly. I'll use a new serial port libary

I've never tried to verify ROM...just normal operations. I'll try a force update again and hopefully it fixes the issues. By the way, my issues were with an Ostrich 1

I will try out a verify tonight; I rarely use it personally. Normally the only time on CROME I would use verify was if I got a cel that would pop up after a few seconds/min of the put. And then it would just turn out to be something like o2 heater or somethin.

this is fixed and will be on forceupdate shortly

Calvin, It is 1:29PM EST I tried force update and it listed r5 still, it also gave me the same issues as before. I am manually re-installing r6t1 again. Update: I had to downgrade to r1, then copy the r6t1 update ontop of r1 to get the ostrich to connect.

force update is the r6t1 you tested. which was good. I just didn't change the r6. I don't believe there are problems anymore. Please don't switch version back and forth. r6t1 is on forceupdate what problems are you having? timeout? Why i never run into problems? So i can debug myself f** tired of this i'll verify everything again later. Step by step. But the to connect functions are the same. U just get a time out? Why not try to use ostrichECT. Post back. I'll be online in an hour again

Update 4:14PM EST... Installed r5 fresh again, forced update to r6, selected com port manually & tried baud rate of 115200 & ostrich connects.... Autodetect does not work for me.

What firmware are the other people that are having issues running ?