EFIDynoTuning Forum

I just installed the Moates QH and my vehicle won't start. Is this ever a problem for anyone else?
I'm going to take it out and test the battery first. Also, the FTDI driver may not be on this laptop. Which is best for this
Windows 10/11 laptop? Pic below with choices.

Sounds like your quarterhorse is still blank and you didnt write a tune to it?

if so the fuel pump should run non stop which means the ecu is corrupted i.e. no tune being served

really shouldnt try to start it like that as you can flood the engine

TunerPro RT wouldn't let me "initialize emulation hardware" and I wasn't getting a device connected indication.
I tested the 3-volt battery, and it was at 3.15 volts.
I just downloaded the FTDI driver and installed on the small laptop. It was on my old laptop before. Now TunerPro RT let me load the tune to the QH.
It looks like it is going to work. Thanks.

make sure you set it up per the getting started write up on the homepage

I still have to get all of this back in the vehicle now. I have a question about this statement:
"NEVER CONNECT OR DISCONNECT ANYTHING FROM THE J3 PORT WHILE THE ECU IS POWERED UP AS IT WILL FRY BOTH COMPONENTS."
Does this mean make sure that the ignition switch is off or that the car battery is disconnected while attaching all the pieces together?,
pcm with Moates QH ready, cable from Moates to laptop, then hook up car battery?
Late yesterday when it wouldn't work, with the key off, I unplugged the cable from the laptop. I hope I haven't hurt the QH.
I installed the QH in the pcm. Then I installed the 3-volt battery, but next time 3-volt first, then install in pcm. Installed the pcm. Then connected vehicle battery. Then before I started it, plugged cable into laptop.
Last question. I purchased an AEM Wideband UEGO Air Fuel Ratio Gauge (30-4110). When picking from the chart of possible wide band sensor/gauge kits, which one should I click to match up with the 30-4110? Or is it set to that one AEMUEGO?

Loose from the pcm, I uploaded the bin file to the QUARTERHORSE. The truck will start and run. I assume that it is accessing the file in the QH.
If that it so, I assume that the J3 port is cleaned thoroughly and wouldn't be the problem that I'm having.
I have everything configured correctly in TunerPro RT. I have gone over the directions several times so I know that it is correct. Last night I downloaded and installed FTDI. I can search for it in device manager, but I can't find it or something that looks like what I think I'm looking for.
The laptop with TunerPro RT is open and ready but the QH and the laptop aren't communicating.

do you have the bin adx and xdf loaded in tunerpro?

in device manager under usb you should see the com port pop up and become available with the qh plugged in

This may be the problem. I previously had this set correctly, but the TP RT update may have caused it to change.
"click configure plug in >> port type >> shared with emulator"
I'll have device Manager open when I get up from the table and go back to the vehicle. Checking all TP RT settings again too.
??? Does it sound like the QH and PCM are cooperating at the J3 port?

In the device manager, I could see an indication as I plugged the QH into the laptop. I'm not sure what is up. I'll go through everything again this evening. I have some physical mechanical work that I need to do while our temperature is at more of a humane level. Could the J3 port be just partially working or more likely that I just don't have one little thing configured properly? I'm able to follow your set-up directions.
I found one thing that I wondered about. In picture below.
Thanks again for your time and input.

Im into the USB serial port/FTDI part of this. I see that I may have one last thing to do to have this configured properly.
Document says "https://ftdichip.com/drivers/d2xx-drivers/ After you've downloaded the driver, you will need to go to device manager and find the ftdi device which is the qh. Plug the Qh in to make it appear. Click on properties and update the driver manually to the search path you downloaded the driver files to." The picture is of the point that I got to but I'm not getting the last step.