Ftdi Drivers Moates

This is important because of the possibility of a driver conflict between drivers for your Moates. The troubleshooting. Installing the latest drivers from FTDI. Oct 19, 2017 theres an new updated FTDI driver dated september 2014, its a worthy download, go ahead and get your QH driver up to date I just seen it.

We're about to start tuning my son's engine and I am having problems datalogging. The engine is a forged Darton 85mm sleeved B18C1 with a P&Pd B16A head on it, stroked with an LS crank to 2.0L. We had it running well NA with a stock P72 ECU so we could get a BAR sticker for it.

We've just upgraded to an LHT intercooled JRSC blower, with Precision 680 low impedance injectors, and have two chipped OBD1 P30 ECUs, one JDM and one USDM. We will be tuning with CROME Pro on a Win7 PC (assuming we can get it working) as we did a few years ago with the same ECUs for our old B16A race motor. The old setup that worked with these ECUs was an older version of CROME PRO with an old XP PC with a serial port. I have CROME Pro 1.6.2 and 1.5.0 on my PC with USB, hence the use of the Hulog. (I have had the Hulog for some time as well, just haven't used it.) Both P30s have been properly chipped, and used in his other CRX when it had the race motor in it. J4 has been cut in the JDM P30 and J12 has been cut in the USDM P30. Mother 3 English Translation Download there. We have a new Ostrich 2.0 and a Burn 2 with some Atmel chips.

We have put a base tune for our setup in both the Ostrich and a chip, and do not get a CEL with either. We have run them both in both P30s. The error message we get when we try to datalog is that it can't connect to the ECU, and it times out. We have installed the latest FTDI drivers from their web site. We have set it to COM1: in device manager at 38400 baud, with the proper 8,N,1 settings.

CROME Pro has the same settings. We also tried COM11: (next available), but that caused CROME Pro to freeze when trying ot detect the com settings. So I put Hyperterminal on my PC, and pointed it at COM1.

I put a 4-pin header in the Hulog CN1 connector and jumpered TxD and RxD together to do a loopback test. I tried all different comm settings and flow control options on Hyperterminal and could not get anything to echo. I tested the 4 wires on the Hulog cable and all 4 have continuity. I tried two USB cables between the PC and the Hulog, one of which is a know good one fomr my printer. I am beginning to think I have a bad Hulog unit. Any other ideas? I would say so.bad hulog.

I imagine you realize how to check the comm ports, to make sure crome (or the datalogger you are using). So as you stated, make sure the hulog and crome use the same comm port. You can actually just make your own hulog, you don't need a bypasser (hulog).

Search how to make ur own.try that before assuming its bad. Maybe contact moates at moates.com. I mean hulog and datalogging are pretty straight forward. Solder 4 pin male header and connect cable to ecu, connect usb 2.0 to pc. That's all there is to it.

Tian90crx wrote:i would say so.bad hulog. I imagine you realize how to check the comm ports, to make sure crome (or the datalogger you are using). So as you stated, make sure the hulog and crome use the same comm port.

You can actually just make your own hulog, you don't need a bypasser (hulog). Search how to make ur own.try that before assuming its bad. Maybe contact moates at moates.com. I mean hulog and datalogging are pretty straight forward. Solder 4 pin male header and connect cable to ecu, connect usb 2.0 to pc. That's all there is to it. Yes, I did check to make sure both CROME Pro and Hyperterminal were using the correct comm port.

And tried two different available ones. I know it should be simple. It worked before, although with a serial port, rather than USB/Hulog. I will contact Moates tomorrow, and will search for how to make my own today. Thanks for the input.

I use crome pro and neptune with windows 7 to tune my cars. I had the same problem at the beginning with the Hulog, brand new one as well. I got a different one, just because they are cheap. My problem was the actual software, I downloaded the latest version of crome pro (Version 1.6.2) and tried it again and it worked. From the editor's settings, go on the tuner comm tab, select Crome QD2 (before it used to be PGMFI OBD1), choose your comp port, the Baud should be 38400, databits at 8, none for parity, 1 for Stop Bits. Under the Connection Setting, 250 milliseconds for timeouts and 3 Max tries.