[econobarn]

This A9L has me scratching my head...

Was able to force open loop once.

Now, regardless of what OLSW or FN320A is set to, it will not go into OL at all. I even unplugged the HEGOs, still wont go into open loop.

Anything else that may be causing it to stick in CL?

Similar issue as the gentleman in this thread: viewtopic.php?p=73359

[EDS50]

This A9L has me scratching my head...

Was able to force open loop once.

Now, regardless of what OLSW or FN320A is set to, it will not go into OL at all. I even unplugged the HEGOs, still wont go into open loop.

Anything else that may be causing it to stick in CL?

Similar issue as the gentleman in this thread: viewtopic.php?p=73359

Make sure the o/l c/l indicator is configured correctly and Clear the kamrfs just for the heck of it.

[cgrey8]

Agreed. The OL status flag is 1 when in OL and 0 when in CL. Just verify you are interpreting the "flag" correctly.

If you feel you are, what's the tuning device? If it's a Quarterhorse, datalog the tune position and make sure the tune that's actually being executed by the EEC is the tune you are writing to in the QH.

[econobarn]

This A9L has me scratching my head...

Was able to force open loop once.

Now, regardless of what OLSW or FN320A is set to, it will not go into OL at all. I even unplugged the HEGOs, still wont go into open loop.

Anything else that may be causing it to stick in CL?

Similar issue as the gentleman in this thread: viewtopic.php?p=73359

Make sure the o/l c/l indicator is configured correctly and Clear the kamrfs just for the heck of it.

FLAG1 B2 for the OL/CL light.

Cleared KAMRFs again, no change.

I think it's mocking me...lol

TUNEPOS is 1

[econobarn]

Got my gears turning so I wrote a change...set idle for 3000RPM and wrote the bin to the QH, and wouldn't ya know...nothing changed.

So that's probably the issue, changes being written to the QH are not being applied or something...now to figure out why that's happening.

[EDS50]

Got my gears turning so I wrote a change...set idle for 3000RPM and wrote the bin to the QH, and wouldn't ya know...nothing changed.

So that's probably the issue, changes being written to the QH are not being applied or something...now to figure out why that's happening.

If its a fox body try detting the hadware to mode 2 tune 2. Also make sure the j3 port has been scraped clean of the protective silicone.

[econobarn]

Got my gears turning so I wrote a change...set idle for 3000RPM and wrote the bin to the QH, and wouldn't ya know...nothing changed.

So that's probably the issue, changes being written to the QH are not being applied or something...now to figure out why that's happening.

If its a fox body try detting the hadware to mode 2 tune 2. Also make sure the j3 port has been scraped clean of the protective silicone.

Already took the box apart and made sure that wasn't the issue.

Just cleared the QH, rewriting now. Been in Mode2, I'll try Tune2 instead of Tune1...

I'll let you know how that goes. Thanks for the input guys! :)

[econobarn]

Gave it another go.

I have it in Mode2 with Tune2 selected TUNEPOS states 8. If I write changes while the thing is idling AFR does dip for a moment when it writes to Tune2 though...

Same issue. What a wonderful Thursday! lol!

Anything else I could try?

[EDS50]

Gave it another go.

I have it in Mode2 with Tune2 selected TUNEPOS states 8. If I write changes while the thing is idling AFR does dip for a moment when it writes to Tune2 though...

Same issue. What a wonderful Thursday! lol!

Anything else I could try?

Clear all the tunes out from all the banks and then write your current tune to all 8 positions and see what happens.

[cgrey8]

Yeah, as I suspected, you are commanding one tune but not getting that tune actually served up. It's quite common for Tune 8 to be the one that gets served up when the QH goes stupid like this. This is why you monitor the position so you can confirm that what you are commanding is what you are getting.

Imagine fighting with that problem before you realized that was even possible. That's what I fought with for a few days before it occured to me that this was happening. Then I had the dilemma of trying to prove it. That's when I modified the datalogging execution code to create the TUNEPOS datalogging option. Once I got enough info to prove my suspicions, Clint gladly added support to BE to automatically fill the Z_TUNEPOS scalar for the QH. We took all that info to Craig Moates. But he never figured out how or why the Verilog HDL code was doing this. So it remains a bug.

[econobarn]

Gave it another go.

I have it in Mode2 with Tune2 selected TUNEPOS states 8. If I write changes while the thing is idling AFR does dip for a moment when it writes to Tune2 though...

Same issue. What a wonderful Thursday! lol!

Anything else I could try?

Clear all the tunes out from all the banks and then write your current tune to all 8 positions and see what happens.

That got it to go into OL is enabled but now RPM and MPH are not being datalogged.

Could the QH be bad/defective?

[cgrey8]

It sounds like it is all kinds of screwed up and BE isn't inserting the datalogging patch code. RPM, MPH, ECT, ACT, and a few others are "special" in that they require patch code assistance to get datalogged. If they aren't being copied out correctly by the patch code, then BE won't datalog them correctly. BTW, I edited my post above.

[econobarn]

So at this time there is no solution being it's a bug?

[EDS50]

Make sure the proper payload is defined and being served to the tune. Also make sure the other gauges on the dashboard are configured correctly.

[cgrey8]

So at this time there is no solution being it's a bug?

Solution as in fix? No.
Workaround. Yes.

To read more, check out this thread:
Tune Selection Bug in Quarterhorse (QH) firmware

[econobarn]

Dashboard was working fine and dandy.

Payload hasn't changed.

Took a glance at that thread, cgrey8. That's kind of disheartening.

[cgrey8]

I've been a little disappointed that this hasn't gotten fixed.

But being there is a workaround way to get the QH straightened back out and in def files that allow you to monitor the tune position, it is detectable when it is happening, it doesn't concern me nearly as much.

[liljoe07]

Dashboard was working fine and dandy.

Payload hasn't changed.

Took a glance at that thread, cgrey8. That's kind of disheartening.

In the email I sent you the other day, you'll see I mentioned writing to all 8 positions. And I briefly described the bug you are seeing.

There has to be a solution. The weird part is, not all have the bug. I have never had to write to all 8 positions. I've used one position since I've owned a QH. You would think you could just compare the firmwares of the ones that do have the bug to the ones that don't???

[cgrey8]

They all have the bug. It's something about writing to all 8 tune positions back-to-back (and probably other things not yet known) that triggers this. Ever since this has been discovered, I found if I write to a tune position, then datalog. Then write to a different tune position, I never get this problem. I only seem to get this problem when I write to multiple tune positions back-to-back and don't datalog.

[econobarn]

In the email I sent you the other day, you'll see I mentioned writing to all 8 positions. And I briefly described the bug you are seeing.

There has to be a solution. The weird part is, not all have the bug. I have never had to write to all 8 positions. I've used one position since I've owned a QH. You would think you could just compare the firmwares of the ones that do have the bug to the ones that don't???

It's a small world, hey guy!

I do really appreciate you poking at that bin, gave me a piece of mind that I wasn't going crazy.

Yeah, it's puzzling why QH does what it does...hopefully it gets sorted out eventually because it makes the real time tuning worthless which was one of the main reason I purchased it.

[EDS50]

In the email I sent you the other day, you'll see I mentioned writing to all 8 positions. And I briefly described the bug you are seeing.

There has to be a solution. The weird part is, not all have the bug. I have never had to write to all 8 positions. I've used one position since I've owned a QH. You would think you could just compare the firmwares of the ones that do have the bug to the ones that don't???

It's a small world, hey guy!

I do really appreciate you poking at that bin, gave me a piece of mind that I wasn't going crazy.

Yeah, it's puzzling why QH does what it does...hopefully it gets sorted out eventually because it makes the real time tuning worthless which was one of the main reason I purchased it.

Im confused. I have zero issue with the qh, be or tuner pro. What firmware do you guys have? What version of be do you guys run?

[liljoe07]

In the email I sent you the other day, you'll see I mentioned writing to all 8 positions. And I briefly described the bug you are seeing.

There has to be a solution. The weird part is, not all have the bug. I have never had to write to all 8 positions. I've used one position since I've owned a QH. You would think you could just compare the firmwares of the ones that do have the bug to the ones that don't???

It's a small world, hey guy!

I do really appreciate you poking at that bin, gave me a piece of mind that I wasn't going crazy.

Yeah, it's puzzling why QH does what it does...hopefully it gets sorted out eventually because it makes the real time tuning worthless which was one of the main reason I purchased it.

Im confused. I have zero issue with the qh, be or tuner pro. What firmware do you guys have? What version of be do you guys run?

Edward, I don't have that issue. I've written to 1 tune position the entire time I've owned the QH. Not once has it written to the wrong tune. And I've never had to write to all 8.

QH v1.4 BE2010

Dave, it shouldn't effect the real time tuning.

[EDS50]

In the email I sent you the other day, you'll see I mentioned writing to all 8 positions. And I briefly described the bug you are seeing.

There has to be a solution. The weird part is, not all have the bug. I have never had to write to all 8 positions. I've used one position since I've owned a QH. You would think you could just compare the firmwares of the ones that do have the bug to the ones that don't???

It's a small world, hey guy!

I do really appreciate you poking at that bin, gave me a piece of mind that I wasn't going crazy.

Yeah, it's puzzling why QH does what it does...hopefully it gets sorted out eventually because it makes the real time tuning worthless which was one of the main reason I purchased it.

Im confused. I have zero issue with the qh, be or tuner pro. What firmware do you guys have? What version of be do you guys run?

Edward, I don't have that issue. I've written to 1 tune position the entire time I've owned the QH. Not once has it written to the wrong tune. And I've never had to write to all 8.

QH v1.4 BE2010

Dave, it shouldn't effect the real time tuning.

Well that kind of confirms that its really not attributable to firmware or software build. I would try messing with the latency settings and maybe a new usb cable. Usb driversfor the qh and maybe even the .net framework all can have something to do with it as well. Just throwing things out there. I did have an issue with electromagnetic interference causing craziness which was remdied with installing a superlogger whicb is still prototype. If you continue to experience difficulties contact craig and have him perform a remote session with you and tuner pro. He can get things straightened out with tunerpro which will also helps with BE.

[econobarn]

Dave, it shouldn't effect the real time tuning.

It does, the only way I can get the QH to actually take the tune is to manually clear each tune then re-write to all eight. If I don't do that, the changes don't take.

I have BE2012 and QH 1.6.

My payload and everything else appears to be correct, none of that has changed. I've tried on 2 cars so far, both wont display ECT or ACT. One A9L was displaying those fields just fine before clearing all 8 tunes and rewriting. The other one may be a harness issue so I can't confirm that issue is with BE/QH.

I have 3 more A9L rides that are still need to be buttoned up before I can see if the data is displayed correctly on them.

Everything was working great until this bug occurred. The first day I was able to use the thing trouble free, second day the problem started to occur.

[EDS50]

Dave, it shouldn't effect the real time tuning.

It does, the only way I can get the QH to actually take the tune is to manually clear each tune then re-write to all eight. If I don't do that, the changes don't take.

I have BE2012 and QH 1.6.

My payload and everything else appears to be correct, none of that has changed. I've tried on 2 cars so far, both wont display ECT or ACT. One A9L was displaying those fields just fine before clearing all 8 tunes and rewriting. The other one may be a harness issue so I can't confirm that issue is with BE/QH.

I have 3 more A9L rides that are still need to be buttoned up before I can see if the data is displayed correctly on them.

Everything was working great until this bug occurred. The first day I was able to use the thing trouble free, second day the problem started to occur.

Something definitly went haywire. This bug shouldnt just all of a sudden appear in my experience. I would love to be able to remote in and see whats going on with the laptop and while its connected to the car.

[econobarn]

Dave, it shouldn't effect the real time tuning.

It does, the only way I can get the QH to actually take the tune is to manually clear each tune then re-write to all eight. If I don't do that, the changes don't take.

I have BE2012 and QH 1.6.

My payload and everything else appears to be correct, none of that has changed. I've tried on 2 cars so far, both wont display ECT or ACT. One A9L was displaying those fields just fine before clearing all 8 tunes and rewriting. The other one may be a harness issue so I can't confirm that issue is with BE/QH.

I have 3 more A9L rides that are still need to be buttoned up before I can see if the data is displayed correctly on them.

Everything was working great until this bug occurred. The first day I was able to use the thing trouble free, second day the problem started to occur.

Something definitly went haywire. This bug shouldnt just all of a sudden appear in my experience. I would love to be able to remote in and see whats going on with the laptop and while its connected to the car.

I may take you up on that offer once we get caught up. Have to get the shop cleaned up for dyno day tomorrow, I'd much rather be tinkering with BE, lol!

[EDS50]

Dave, it shouldn't effect the real time tuning.

It does, the only way I can get the QH to actually take the tune is to manually clear each tune then re-write to all eight. If I don't do that, the changes don't take.

I have BE2012 and QH 1.6.

My payload and everything else appears to be correct, none of that has changed. I've tried on 2 cars so far, both wont display ECT or ACT. One A9L was displaying those fields just fine before clearing all 8 tunes and rewriting. The other one may be a harness issue so I can't confirm that issue is with BE/QH.

I have 3 more A9L rides that are still need to be buttoned up before I can see if the data is displayed correctly on them.

Everything was working great until this bug occurred. The first day I was able to use the thing trouble free, second day the problem started to occur.

Something definitly went haywire. This bug shouldnt just all of a sudden appear in my experience. I would love to be able to remote in and see whats going on with the laptop and while its connected to the car.

I may take you up on that offer once we get caught up. Have to get the shop cleaned up for dyno day tomorrow, I'd much rather be tinkering with BE, lol!

PM me if you cant figure it out and when your ready.

[econobarn]

Bumping this...

So here's what I've found...

QH works fantastic...has a few quirks though...

Here's how I ended up getting around the quirks that were irking me...

Before I write a new tune I clear the ram, then I write all...once write all is complete I select a different bank in BE...then all my data comes to life...if I don't I can't log ECT, ACT, RPM and TP.

Is this more time consuming than I'd like? Yes, but at least it works.

Also noticed that when I clear individual banks the bank I'm erasing is always different than what it says it's erasing...example: Bank 2 is sometimes 0 or 5 or 7 or 3 or any number between 0 and 7...