[MikeP]

sorry if this a dumb question as this is my first attempt to tune a non flash car, have quarter horse and tunerpro, koeo no communication between laptop and QH, also will not start, pull QH starts right up, pull computer and board to make sure contacts are clean reainstall and again no start, pull QH and it starts right up?? am I missing something? Is there a flow chart or a thread/ video somewhere for beginners? From the videos I've watched it should work? Does the battery in the QH need to be good for it to work? know it wont save without?

[skunk]

Hey Mike....Welcome.

If there is no communication between the QH and your Laptop......I would start by making sure you have the drivers installed and the Moates device is listed in the device manager.

I believe there is a getting started thread on this forum that may answer most of your questions.....but don't let that statement deter you from asking questions.

Good Luck
John

[motorhead1991]

Hey Mike....Welcome.

If there is no communication between the QH and your Laptop......I would start by making sure you have the drivers installed and the Moates device is listed in the device manager.

I believe there is a getting started thread on this forum that may answer most of your questions.....but don't let that statement deter you from asking questions.

Good Luck
John

I believe decipha at efidynotuning also has a similar writeup.

[MikeP]

downloaded the USB Device Driver and installed it said it installed but cant find it in device manage? is in a subfile or all by itself?

Thanks Mike

[skunk]

Mike......I can't remember and I am not close to a computer. I want think it would appear as a com port but only when the QH is plugged in.

John

[cgrey8]

I know BinaryEditor got some changes a while back to allow it to detect and communicate with a QH even when it wasn't discovered as such. However I always had better luck using the original Moates release Quarterhorse 2.6.0.0 driver which explicitly shows up in the Device Manager as the Quarterhorse. But this is also with me using BinaryEditor. I only attempted to communicate with a QH and TunerPro once and that was just a diagnostic effort...not to do actual tuning.

I don't remember what TunerPro wants, but I could see it wanting the QH to be exposed as a COM port. If that is the case, you can identify the Device that the QH is showing up as in the Device Manager, and it seems there's a checkbox in the driver that has to be selected. I think it was labelled VCP (Virtual COM Port). And when selected, the QH will show up with a COM port number in the list of serial COM ports. From there, you can interact with it as a COM port so software that wants to see it as a COM port can find it.

As for the car not starting with the QH plugged in, that's no surprise. It needs a valid tune in it before it'll control the EEC. So before I got any of this installed in the car, I'd go about getting this working with just the QH connected to the computer via USB cable. Once you get your laptop and software capable of communicating with the QH and writing tunes to it just connected (and powered) via USB, then install it on the EEC and go from there.

[MikeP]

so you cant pull the factory tune out of the computer? because there is no chip in the computer to read correct? so I have to download one to the QH correct? Where is the best place to get one? using tunerpro RT

Thanks for the help so far
Mike

[MikeP]

still wont read, pulled QH out of car plugged into lap top in office and still getting "not connected" went to EFIdynotuning and followed his directions multiple times nothing in device managers, double click on xdf file wont pop up in tunerpro RT, am I totally missing something or something wrong with soft/hardware

Downloaded Moates USB Device Driver a coupe times shows to install, but the computer can't find it
I followed these directions, but when you check these items do you uncheck the other items or leave the ones already checked checked?

(After you have downloaded and installed TunerPro RT open tunerpro and do the following:
up top in the tool bars go to tools >> preferences. The "general" table should be opened first
put a check in the box for the following:
Load last XDF at startup
Load last BIN at startup
<---File Associations--->
*.xdf
*.bin
*.adx
*.xdl
<---Table Editor Options--->
Reverse Rows <---
look to the right two tabs for "KEYBOARD"
scroll down to the Delete XDF Parameter command, select it and click the Clear Combination button
Now, look to the far right for the data acq./emulation tab
(on left) data acquisition & logging >> interface type >> select "use plug-in" from drop down menu
click configure plug in >> port type >> shared with emulator)

[skunk]

Sounds like you may have to talk to Moates support. Do you see any unknown or failed devices in your device manager? If you do.....you can try to update the driver from there pointing it to your downloaded driver.

John

[MikeP]

Dave at Moates got me up and running software and hardware were fine did not download enough files, missing bin file and xdf file, didn't think this wold be so complicated Holley and xp tuners is soo much simplier only need one file

Thanks for all the help
Mike

[cgrey8]

Dave at Moates got me up and running software and hardware were fine did not download enough files, missing bin file and xdf file, didn't think this wold be so complicated Holley and xp tuners is soo much simplier only need one file

There's a reason for that.

Holley is a single company producing a coherent product. I'm not greatly familiar with it, but I believe they deliver you both hardware and software as a matched set don't they? Do they reuse the stock EEC at all? I'm asking because I honestly don't know. Regardless, whatever hardware and software they market is a matched set, designed and tested to work together in the applications they support.

In the case of the QH, you got one company, Moates, producing hardware that's intended to reuse the Ford EECs. Then you have either TunerPro or BE handling the software side of things. Then you have the definition developers making the definition files to display and modify the assembly-based tunes, also initially written by Ford. And so it's a lot more moving parts to keep coordinated. And the answers of what you need aren't the same for everybody.

Add to it, in the case of TunerPro and BE, there's only 1 developer on each of those of whom do programing, sales, and support...and doing all that is not their full time job! In the case of Clint, maintaining BE/EA started off as a hobby that turned into a side-job and has not grown nearly large enough to replace their day-job. It's actually pretty amazing we get as solid of an offering as we have given the vast variability and disjointed nature.

I'll be honest, I couldn't deal with the sale and support aspects 1/2 as well as Clint as. I'd be too quick to tell people where they could go when they started complaining. I, generally, try to help people as much as I can and qualified to do. But when people start biting the head off the person trying to help them, I suddenly loose that motivation. That's why I decided YEARS ago that my contributions would always be in an Open Source capacity. That way I would not feel obligated to take abuse from anybody.

[motorhead1991]

Dave at Moates got me up and running software and hardware were fine did not download enough files, missing bin file and xdf file, didn't think this wold be so complicated Holley and xp tuners is soo much simplier only need one file

There's a reason for that.

Holley is a single company producing a coherent product. I'm not greatly familiar with it, but I believe they deliver you both hardware and software as a matched set don't they? Do they reuse the stock EEC at all? I'm asking because I honestly don't know. Regardless, whatever hardware and software they market is a matched set, designed and tested to work together in the applications they support.

In the case of the QH, you got one company, Moates, producing hardware that's intended to reuse the Ford EECs. Then you have either TunerPro or BE handling the software side of things. Then you have the definition developers making the definition files to display and modify the assembly-based tunes, also initially written by Ford. And so it's a lot more moving parts to keep coordinated. And the answers of what you need aren't the same for everybody.

Add to it, in the case of TunerPro and BE, there's only 1 developer on each of those of whom do programing, sales, and support...and doing all that is not their full time job! In the case of Clint, maintaining BE/EA started off as a hobby that turned into a side-job and has not grown nearly large enough to replace their day-job. It's actually pretty amazing we get as solid of an offering as we have given the vast variability and disjointed nature.

I'll be honest, I couldn't deal with the sale and support aspects 1/2 as well as Clint as. I'd be too quick to tell people where they could go when they started complaining. I, generally, try to help people as much as I can and qualified to do. But when people start biting the head off the person trying to help them, I suddenly loose that motivation. That's why I decided YEARS ago that my contributions would always be in an Open Source capacity. That way I would not feel obligated to take abuse from anybody.

The beauty of Open Source is that you can tell people "don't like it? fix it yourself. Otherwise sit back and be quiet"