[86GT]

As soon as craig releases the QH

[Craig Moates]

Here is a quick update.

We're still on track with production for shipments/orders by the end of the month. I'll post an update when the first batch of units is ready.

I'm going to hold off on EEC J3 reading capabilities for the current revision, it's a relatively low priority. I may make a standalone device available for this capability with cost around $50.

For multi-bin capabilities, there will be a sweet option for the EEC-IV applications. Rotary switch, easy install, 4 programs. Solders right onto the QH (and F3 adapter for that matter). Probably around $40. Nothing for EEC-V multi-tune capabilities for this release. Later on we can get into that, but have no expectations.

Again, QH price will be $249. If you want one, you can have one in your hands by the end of the month.

Hope this helps,
Craig

[cherrybomber22]

oh i do want one :)

[svojohn]

Again, QH price will be $249. If you want one, you can have one in your hands by the end of the month.

That's good news to hear, I'll start gathering my pennies together.

Has the QH been tested on the EEC-V?

[Cougar5.0]

That's cool.

I do see why Ford has some KAMRF cells using data derived from other driving conditions. Cells in typical "transient" areas are going to cause a LOT of confusion for beginners and experienced tuners alike.

[86GT]

I agree, The screen shot does not show all of the visual. I also have BE changing the color of the cell if the FN1325 has a negative value. Like you said there has to be some way to tell the user that the cell is inderectly addressed.

[SigEpBlue]

We're still on track with production for shipments/orders by the end of the month. I'll post an update when the first batch of units is ready.

Again, QH price will be $249. If you want one, you can have one in your hands by the end of the month.

Also, there goes my tax refund. I will be checking this and your front page daily and often, sir!

For multi-bin capabilities, there will be a sweet option for the EEC-IV applications. Rotary switch, easy install, 4 programs. Solders right onto the QH (and F3 adapter for that matter).

Awesomeness.

Now someone correct me if I'm wrong, but since it will allow you to image the entire ROM and see exactly what's being accessed, one may be able to potentially 'fill in' the gaps of his definition, right? Assuming they're not a braindead moron like me.

[cgrey8]

Do you mean add code to the existing codebase and use the unused portion of the BIN file to do it? Sure. You could do that with the TwEECer. That's exactly what is done when you add FN1360 support to a GUFx def that didn't have that table before.

The limitation of the TwEECer as compared to the QH when it comes to adding code to the tune is that you cannot move or delete things that existed in the EEC's stock tune while using the TwEECer. I wish I fully understood why the TwEECer has such a problem with this, but I don't. I just know it doesn't work and I have my suspicions and theories. But that's all they are. The point is the QH overcomes that limitation by NEVER letting the stock ROM execute. As long as the QH is connected to the J3, the ROM is disabled at least as the QH is currently programmed. This "feature" of the QH allows me to run my GUFB tune on a GUF1 EEC (A9P). That's something I could never do successfully with the TwEECer. See, when Ford made the GUFB strategy, they didn't just simply add more code to the unused places in ROM, they added new code in the middle of the existing codebase which shoved the existing code further forward in ROM.

The only drawback of the QH not allowing the on-board ROM to execute is you cannot "disable" the QH like you can the TwEECer by setting the TwEECer to execute the stock tune. Most people with significantly modified vehicles couldn't run on the stock tune if they wanted to so that's not much of a drawback to them. And for those that do want to have a "stock tune" position, one of the 4 tune positions will have to be used for that purpose.

[SigEpBlue]

Not exactly what I meant, but that's great, since it gave me some other interesting ideas. Lean cruise modes, multiple discharge, alternative shift schedules....lol

Anyhow, I don't consider any of the perceived 'drawbacks' as such with QH, although I do see your point about the setups that are virtually non-driveable without it (then again....oh nevermind ). Rather, they will more than likely make life a little easier for me from the tuning, def-writing, and programming end. I was looking at it as a way to make more sense of what the op-code (everything before the scalars, tables, functions, etc.) is doing, calling, pointing-to, accessing, etc. at any given point in time. I know I'm probably going to end up having to dick with dis8061 and the .dir to further expand my definitions, but I'm holding that off as long as possible.

FWIW, the kinds of things you've talked about for quite some time, regarding the twEECer, are why I will never buy one, especially the proprietary .ccf file format bullshit. I'm really REALLY hoping that definitions and similar for BE/EA stay the same (with Excel-editable defs) regarding the QH and compatibility. From all indications so far, that seems to be the case, so YaY Moates & Clint.

[86GT]

I'm really REALLY hoping that definitions and similar for BE/EA stay the same (with Excel-editable defs) regarding the QH and compatibility. From all indications so far, that seems to be the case, so YaY Moates & Clint.

The logging is going to stay excatly the way it is now. This means no changes for EA what so ever. Now the definition files will change. The structure on the Scalars, Functions and Tables will stay the same. The difference is there is going to be a new tab for the QHorse and its configuration parameters. The remaining tabs also have a few changes. It is going to take some time to clean up and post all the new def files.

My first priority is to get the Definition template up to date. I will then work on the defs one by one. The key here is to get those that are in the know to help with the patch codes for the logging. Derek has been awsome at this and is helping more than he knows. I think he may have figured out the 2 bank tune datalogging. I have a CDAN4 sitting on my desk that we were able to get data from, thanks to Derek!!!!

It shouldnt be long. If you want a template of the def file I can send you the GUFB that has already been updated.

[Foxfan88]

since i am not so computer advanced as most of your guys. perhaps someone could put this in a nutshell for me.

will the swap to the QH be as simple as just removing the tweecer, putting in the QH, getting the updated BE and check of that i'm using a QH and then start tuning/log the same that i was before??

maybe someone could make a list of what the swap over from the tweecer to the QH will entail.

clint just mentioned having to update the defintions, if this something that will be updated along with the updated BE?

[cgrey8]

That's pretty much it. Read over the Installation FAQ I wrote up for the physical installation. The installation of the QH in the EEC is the hardest part of the swap over. The rest is just getting the QH installed on COM5 (that's the magic COM port that the QH must be installed on). The updated BE with the latest def files will auto detect the QH. At that point, you select all the payload options you want (no limits with GUFx defs), write your tune to the QH, and off you go.

It wasn't quite that easy for me when I 1st got the QH because there were BE bugs holding things up. But with today's BE, all those issues have been flushed out and should be every bit that easy to make the transition from a TwEECer RT to a QH. There are still some minor bugs in BE that I'm noticing and reporting to Clint as I find them. But all the major stuff has been caught, reported, and taken care of in both BE and the QH firmware. As you would expect, there were issues on both sides that required attention. But that was the whole purpose of a beta period...to work out all those issues so when the QH released, people would have a smoother, more streamlined, user experience. Anybody that started their tuning with the TwEECer and CalEdit/Calcon will not believe how easy it will be with the QH.

There are still things Craig has on the to-do list and the QH will not be full-featured on release. But it'll be well worth getting. The next version of QH, being called the QH2 right now, will have more features like the ability to upload tunes from the EEC as well as a few other minor updates like multi-tune support on EEC-Vs. But for those that already have a tune from their TwEECer/Moates Chip or don't mind starting with standard stock tunes that are readily available, then having the ability to upload the stock tune is not really important.

Also for the time being, there may be some manual intervention with a soldering iron to get a switch on the QH so you can switch the tunes. Although I believe Craig plans to offer a switch option for an additional fee...at least I think that's his intention. For those that have a TwEECer switch, I'm hoping to concoct an RJ11 connection to allow me to reuse that switch with the QH. If I come up with something that works, I'll post up the details of how to do that so others with a TwEECer switch can reuse theirs as well.

[86GT]

The only thing I can add is that COM 5 is not the only com port. If you use BE then any port will do as long as nothing else is using it. If you are going to use the flash and burn then craig recommends using com7.

[Cougar5.0]

There are still things Craig has on the to-do list and the QH will not be full-featured on release. But it'll be well worth getting. The next version of QH, being called the QH2 right now, will have more features like the ability to upload tunes from the EEC as well as a few other minor updates like multi-tune support on EEC-Vs. But for those that already have a tune from their TwEECer/Moates Chip or don't mind starting with standard stock tunes that are readily available, then having the ability to upload the stock tune is not really important.

Hardware or firmware update?

Also for the time being, there may be some manual intervention with a soldering iron to get a switch on the QH so you can switch the tunes. Although I believe Craig plans to offer a switch option for an additional fee...at least I think that's his intention. For those that have a TwEECer switch, I'm hoping to concoct an RJ11 connection to allow me to reuse that switch with the QH. If I come up with something that works, I'll post up the details of how to do that so others with a TwEECer switch can reuse theirs as well.

My switch is in the dash - one way or the other I'm going to want to use an RJ11 connector on the other end.

[cgrey8]

Firmware and Rigidware updates, but not hardware.

Firmware: The code running in the QH's microprocessor. This can be updated using Craig's Flash-n-Burn software by a user.

Rigidware: The hardware design in the QH's CPLD as described by the Hardware Description Language (HDL). This requires a bench update by Craig and thus cannot be done by end users.

The hope is he can get as much support in the rigidware as possible so all the updates will be in the micro...but that's not always possible.

[Craig Moates]

Folks,

I'd like to add a few points for clarity. I know Chris and others get pretty excited on this stuff:

- The Quarterhorse design is set. No need to muddy the waters right now or very soon with a redesign. This thing has been on the back burner for almost 3 years with as many name changes waiting on me to push it out.
- It provides bumpless realtime emulation for all Ford vehicles with J3 port through 2004.
- Datalogging is achieved by a combination of RAM shadowing and ROM code patches.
- If you want to do some multi-tune stuff, you can have up to 4 via external switch taking over the BS0/3 lines. You can do this with the regular F3 adapters as well, so nothing too noteworthy really. No switching for EEC-V. I'll make the switch and interconnect cable/connector available for around $25 or so.
- While hardware provisions are currently in place, they remain untested and there is no current firmware support, field updateable or not, for EEC reading of stock tunes.
- The QH is not intended to compete with any existing products, it's intended to deliver functionality that has never been seen before on the Fords. So any QH -vs- XYZ isn't as relevant as it could be if the QH wasn't bringing new functionality to the table.
- If you want EEC-V bin switching and EEC reading, please don't wait on the QH or get one in hopes that it will be added.

I will certainly keep working on the firmware development and addition of features, but from my experience, this thing is already about as complex as it can be without becoming a source of confusion. If I'm able to squeeze additional features into the firmware (either field update or send-it-back update), I'll make it available to QH owners at no extra charge.

Hope this helps,
Craig

[DrDirt]

This is all sounding so cool! Available by the end of the month, huh? How convenient....my birthday is in 2 days. When can the ordering begin? IThe Old Horse needs a Quarter Horse.

[tealstang67]

i definitly agree can't wait to tune and drive. I have been waiting about 3 months new motor only has 33 miles on it.

[lito]

Do you see it can be used to do various cars as a tuner tool? Have the tune ready, burn a chip, next?

[cgrey8]

The Quarterhorse cannot write to the EEC. It substitutes the EEC's onboard ROM. Thus when you remove the QH, the tune goes with the QH.

However, you can easily use the QH to tune a vehicle. Once tuned, burn that tune to a Moates Chip (or similar), install the Moates chip on the tuned car, and use the QH on another vehicle at that point.

[86GT]

No more waiting they are in. Craig will have the updates to his web site by tomorrow and will be accepting orders.

[svojohn]

Cha Ching!!!

[Craig Moates]

Craig will have the updates to his web site by tomorrow and will be accepting orders.

Done.

[lito]

droooooooooooollllllllll.

Nice!

One addtnl question prior to setting up an order on the moates site the upcoming days, I use the SCT software but tuning EEC-IV totally blind is very hard. (I can't find my old EEC tuner) I was very close to getting into the competing hardware until I've read about this a few weeks back so I put everything on hold until this was released.

I plan to use for custom tuning customer's cars, what else should I need to get up and running (I mean, which burner that would work with BE, or my SCT burner will do the job, and will the SCT chips work along with the moates ones? I've plan to get moates chips anyway but have a few SCT's in stock now)

I've already bought EA a few months ago (but no BE), does the HQ come with BE already?

thanks,

Manuel.

[wa_4x4builder]

Craig will have the updates to his web site by tomorrow and will be accepting orders.

Done.

-1. One less for the rest of you

Now, I get to talk to Clint about his wares...

[cgrey8]

...One addtnl question prior to setting up an order on the moates site the upcoming days, I use the SCT software but tuning EEC-IV totally blind is very hard. (I can't find my old EEC tuner) I was very close to getting into the competing hardware until I've read about this a few weeks back so I put everything on hold until this was released.

I plan to use for custom tuning customer's cars, what else should I need to get up and running (I mean, which burner that would work with BE, or my SCT burner will do the job, and will the SCT chips work along with the moates ones? I've plan to get moates chips anyway but have a few SCT's in stock now)

I've already bought EA a few months ago (but no BE), does the HQ come with BE already?...

You will want to get BE as well. EEC Editor I believe also will support the QH. But 99% of the people on this site use BE mainly because Clint supports it so well and he's an active member of this site. So I'd highly recommend you also license BE.

As for burning hardware, the QH won't require its own burner. But chips obviously will. You can use Moates burners and chips to burn with. And I believe the Moates burner will burn SCT chips. So if you have a collection of SCT chips, you can use them up with BE and the Moates burner.

[lito]

...One addtnl question prior to setting up an order on the moates site the upcoming days, I use the SCT software but tuning EEC-IV totally blind is very hard. (I can't find my old EEC tuner) I was very close to getting into the competing hardware until I've read about this a few weeks back so I put everything on hold until this was released.

I plan to use for custom tuning customer's cars, what else should I need to get up and running (I mean, which burner that would work with BE, or my SCT burner will do the job, and will the SCT chips work along with the moates ones? I've plan to get moates chips anyway but have a few SCT's in stock now)

I've already bought EA a few months ago (but no BE), does the HQ come with BE already?...

You will want to get BE as well. EEC Editor I believe also will support the QH. But 99% of the people on this site use BE mainly because Clint supports it so well and he's an active member of this site. So I'd highly recommend you also license BE.

As for burning hardware, the QH won't require its own burner. But chips obviously will. You can use Moates burners and chips to burn with. And I believe the Moates burner will burn SCT chips. So if you have a collection of SCT chips, you can use them up with BE and the Moates burner.

Yes I have SCT's, red diablo's, black diablo's, I can make a big chip omelette!

So, QH+burn2+F2A adapter+chips+BE and I would be more than ready to run, right?

thanks.

[cgrey8]

I think so...

[SigEpBlue]

One more ordered!

BTW, thanks for the help over email, Clint. I'll definitely be ordering EA soon. Probably another copy of BE too, since I think I killed my old laptop it was locked to.

[lito]

Chalk another one!