eCtune

First, let me say after tuning my first car on eCtune, this software absolutely blows CROME out of the water. I am very impressed on eCtune's functionality for being a ROM editing platform. There are very few features a full standalone can offer that eCtune does not. Now that I've got that off my chest, I need some help diagnosing a problem. I seem to be experiencing the same problems as these two: eCtune Freeze eCtune Freeze 2 Hardware summary: JDM OBD1 PR3 B16 ECU Ostrich 2 Hulog2 Xtreme POS Dell laptop Windows 7 2gb RAM / 1.8 Ghz AMD 64bit Fresh FTDI install (and clean) as of 9/6/2009 I never get any connection errors with the emulator or datalogger The freeze happens usually during datalogging, but has happened in just general live-sensor view a couple times. The entire computer completely freezes and forces a hard reboot. The good thing is that the datalogs up until the freeze are still stored in memory upon restart, so I am not wasting a bunch of time (just the ~4 minutes or so between restarts). Since there are two instances above where others have experienced the same problem (and possibly more...), I was hoping to find a solution from someone. I have a feeling it has something to do with Windows 7. I did a fresh FTDI installation and clean as per Calvin’s recommendation in one of the linked threads above, but that did not solve the problem. Thanks.

what is your driver version? What is the latency of the FTDI drivers?

calvin wrote:what is your driver version? What is the latency of the FTDI drivers?

Ostrich2 (COM 4) 2.2.4.1 FTDI Latency 10 msec HuLOG Xtreme (COM 5) 2.2.4.1 FTDI Latency 2 msec

I'm having the same problem. I think I have the same driver (can't check right now) and have the same latency setings. those were the recommended settings i found somewhere, although I noticed the xenocron support section suggests setting latency to \"1\" for both devices. i'll install the latest FTDI drivers (2.4.16) tomorrow. *edit Checked out FTDI's changelog and found some bugfixes wich might be related: 2.04.06:

• Fixed deadlock issues for multi-processor systems. Fixed lock-up problem in Vista and XP.

Thats odd that after I performed the FTDI clean and installed a fresh download of VCP drivers, the laptop still shows 2.2.14 as the current version. I will try again tonight to FTDI Clean and download the driver pack again. I will be touching up my map next week, so I can hopefully get this issue resolved!

I can confirm that the 2.2.4 drivers are bad. I've upgraded to 2.4.16 and the hard lockups are gone. I've done 2 20-30min datalogs now withouth any problems. For anyone with lockup problems, download these latest drivers: http://www.ftdichip.com/Drivers/CDM/CDM ... tified.zip Do a manual driver update (from within 'device manager')'. No need to do a driver cleanup. Just choose update driver, and choose to manually select the driver (don't let windows search). Then select ftdiport.inf for the virtual comport driver. I set buadrates back to default, and latency to 1. No problems so far.

good