Bob or anyone else...

I'm getting RX timeout errors when trying to upload my bins to my ECM via What'sUp. I've been able to upload successfully, but its maybe 1 out of 20 times I try to upload that it works. I get RX timeout 1, 2 and 3 intermittently.

I looked at the old release notes and for 2.2e Bob increased a timeout value from .5 sec to 2 seconds due to lag introduced in serial to USB cables. I do have a serial to USB, which I bought at the local PC warehouse. Could this be my problem? Any way I can hack the timeout value to be higher? Or any sort of logs I could parse through? I'm at code 2.2f.

The right COM port is selected, and the key is in the ignition position. If I go out of the BIN load screen to the WUD screen and press the gas, I see TPS go up and down.

Thanks
Chuck

 

Go to this link and follow the directions to lower the latency setting:

http://www.dynamicefi.com/USB2SerialSetup.php

If there is a latency setting as shown in the last picture then lower it. That will take care of the issue.

If instead there are FIFO sliders I know of no fix with the exception of a different USB/Serial adapter cable.

The USB/Serial adapters that use the latest FTDI chip set are recommended.

RBob.

 

Of course I have the non FTDI chipset with the sliders. Mine is made by Prolific, and Windows7 out of the box installs driver v3.3.11.152 (7/15/2010). I tried to change every setting in the driver setting I could and had no luck.

I downgraded to driver 3.3.5.122 (7/17/2009) and that appears to have fixed the issue... I was able to upload twice without issue, then I called it quits for the night. I'll update this next time I can and let everyone know if its permanent.

Drivers for my specific cable are here, but the included driver is generic for Prolific.
http://downloads.trendnet.com/TU-S9/Driver/

Thanks
Chuck

 

The older driver fixed it for the Prolific chip sets. I have not had an issue uploading the last five bins.

To be honst, just buy the cable from Bob. It saved me $5 to buy it locally, but cost me 3 hours of troubleshooting instead of tuning.

Thanks
Chuck

 

That is good news that the older driver worked out. I'm saving the link to the drivers for others when they have a problem. The Prolific cables are, well, prolific out there (ouch).

RBob.