[86GT]

I just noticed that last Thursday, FTDI came out with new drivers. I compiled it and posted the new drivers at:
http://www.eecanalyzer.net/downloads/Driver.zip

There was a whole list of things they fixed but we will have to see. I did notice that my read and writes are faster.

[88351stang]

I am having this issue as well. Finally got my car back to where I was ready to crank it. I upgraded to the QH 1.6 and BE 2010 while I have been doing other work on the car. Well now, when I installed everything and downloaded my tune, the fuel pump runs constantly, along with some clicking (which I assume is the injectors) I am in mode 2 and have tried downloading to all tune positions. If I go to mode 0(stock tune), everything works fine (car will run also).

I can't get it to clear tune 8 either. When I clear tune 8, tune 5 clears instead. I have BE build 17 with GUF1 strategy Rev 80. Do I need to rewrite my tune from scratch with BE2010?

I am missing something else. Any suggestions would be appreciated.

[86GT]

I will look into the clearing of tune 8.

As for the car running on the mode 0 that proves the EEC and car are ok. If you setup a secure.logmein.com account i can log in and take a look. Make sure it is a secure.logmein free account.

[88351stang]

Just sent - Thanks Clint.

[cgrey8]

I have no clue what kind of PS a Dell P90 supply is. But I know what you mean about inverter's spitting out an odd form of power. Instead of a smooth sine, you usually get a boxy square-wave...much the same as what you get with really cheap UPS units for home use.

[jphil81]

I have been experiencing the crash when exiting Datalogging. My tune is in tune1 and that is active and I have done the check that you have given earlier for this. Latest version of BE build 17 and QH is 1.6. I'm using the laptop on battery only.

It seems to be variable and does not happen every time.

Are you any closer to a fix? Its not a ball breaker though, just one of those things to work around. I'm enjoying BE so thanks for all your hard work.

[86GT]

I have been experiencing the crash when exiting Datalogging. My tune is in tune1 and that is active and I have done the check that you have given earlier for this. Latest version of BE build 17 and QH is 1.6. I'm using the laptop on battery only.

It seems to be variable and does not happen every time.

Are you any closer to a fix? Its not a ball breaker though, just one of those things to work around. I'm enjoying BE so thanks for all your hard work.

Send me an email and i will help try to debug it.

[decipha]

if i may add my .02

i don't have any issues just using 1 tune position, for those with issues, perhaps this can be a viable solution?

others that use only 1 position don't have any issues either

[Chucko]

Why would you buy a device that supports multiple tunes if you're not going to use them?

BTW decipha, I love your new sig.

[decipha]

for the same reason the ecu only uses 1 tune at a time

because that's all i need

just giving you a hard time chucko

oh and my sig.. so true

[Craig Moates]

Gents,

Just a heads-up, I will be digging deep into the BE/QH interface protocols here shortly to help with validation of Clint's implementation at the COM level, particularly regarding the different positions/modes/etc. It seems that something gets lost in the shuffle at times in terms of active position and that sort of thing.

A solution, if applicable, will likely be a few brute force maneuvers software-side instead of any firmware or hardware changes.

To be clear, the QH was never conceived or intended with the purpose of having multiple positions or modes. It's targeted to datalogging and emulation. The multi-tune thing was a bit of an afterthought, sort of a "Hey we've got all this space, why not?".

-Craig

[cgrey8]

I agree, some aspects of this issue will likely be easier to take care of on the software side.

However what won't be is the issue relating to Mode 5 where 1 position is software selectable, and the others are hardware selectable. If the software selects the software selectable tune to be Tune 7, for instance, once you flip away from the software-selectable position, you can never get Tune 7 back without reconneting the PC. It may be just easier to remove the Mode 5 option from BE so this issue isn't apparent. TBO, I wouldn't be heavily offended by loosing Mode 5. I can do 99.9% of everything I need to do with Mode 1 and 2.

[XR7Dave]

Hey guys, most of you don't know me, but some do. Anyway I do a ton of tuning with BE and QH's, mostly SC stuff but a significant amount of Fox body too. I don't have any solutions to present but I do have some experience to relate and a comment or two.

1) I use Mode 1 Tune 1 almost exclusively and I rarely have any problems at all. Keep in mind that I connect literally with 100's of cars. To me the most important thing is that I can rely on the tune I'm using being the tune I think I'm using. To me having multiple tunes on one device is foolish and extremely dangerous. I would NEVER run multiple tunes on one device. I tune cars that have 200hp nitrous systems - if the owner EVER made the mistake of mixing up tunes, or had his QH access the wrong tune - it could cost $20,000 instantly. It is absolutely absurd in my opinion to try to run multiple tunes on one device. If I were in charge I would instantly terminate all multi tune support both in the hardware and in the software. It's that serious, IMO. There is no tangible benefit to running multiple tunes.

2) I find that T1M1 works perfectly on most all SC's, but some 94-5's seem to prefer M2T8. For some reason I find that certain cars just won't even run on M1T1, in which case I defer to M2T8 and everything seems fine. I have found that Fox body cars don't like M1T1 but seem to work ok on M2T8. No idea why, but once I figure out what one particular car likes, I stick to it and generally don't have any more issues. Again, only one tune being used! I find that if I switch Modes, often times complete jibberish shows up in unused spots. This is disconcerting to me but I just clear those tune positions and carry on. So far so good.

3) There are some issues with datalogging and I'm pretty sure most of it is due to electrical interference in certain vehicles. I have one SC that runs fine most of the time, but at about 4000rpm under full load the MAF signal suddenly goes apeshit and the car can't calculate load or PW. Of course everything goes to hell at that point. Occasionally the car will make a clean pull, but don't count on it. Disconnect the laptop and the car runs perfect. This is as repeatable as you want, all day long. This car had similar issues when I tried tuning it 4 years ago using a Sneec type interface. Customer has been battling these issues ever since. We just figured out this fall that disconnecting all diagnostic equipment from the car results in perfect performance. I don't know what a datalogger could be doing to the MAF signal but I've seen it and documented it many times (on this car only). I've also seen GUFx cars that won't datalog with QH installed. They start datalogging at idle ok, but as soon as you take rpms up any they puke out the datalog. In those cases (I'm using BE), if I switch to my Tweecer, no problem! I just came to the roundabout conclusion that some vehicles must have ground path issues which show up when attempting to intercept data either before the EEC or inside it. I've even changed EEC's in some cases, no difference.

Well, those are my comments. I love the QH and I like BE, and I sell both to all my customers but there are some serious bugs that should be worked out. Other than that, you guys (Craig and Clint) have the best thing ever going here and I love it so take what I say as constructive criticism.

PS. I'm using BE 2009 build 39 Beta. I have 2010 but have had issues with it so while I have it installed on my laptop, I don't use it for hardware connections, I use 2009 for all my actual tuning.

[decipha]

holy shmoley its the owner of SuperCoupes Unlimited, Mr. Dave Dalke, welcome to the forums Dave, I'm ecstatic that you've joined!!!

the new release of BE is really stable and reliable, im using the newest full release with the current published update, I have almost zero problems with it.

[cgrey8]

Craig/Clint,
Any update on this?

[fasterpatrick]

I've read through this thread a couple of times now and something clicked. I think the issues I was having were related, I was using mode 2 tune 1 and not loading it to any other spot with my mark VIII EEC as decipha suggested. What would happen if there is no tune in any other locations when the tune switched would it revert to stock or worse. My car will not run correctly with the stock tune, heck I didn't think it would start due to the transmission switch not being there to send feedback to the EEC. When the snow melts I will load the tune to all 8 positions, but first I think I will run through all the modes and run a clear data on all positions.
Patrick

[cgrey8]

See if you can get your def file updated to allow you to datalog your tune position. Then there's no question as to which tune the EEC is running from.

[cgrey8]

Clint/Craig,

Any update on this? For the 1st time in a few months this happened to me again. I tried to download all 8 positions and the QH was still jacked up on a few tunes. Tune 1 never would run right. It kept coming up as Tune 3 when flipped to it via the switch. Tune 2, 3, and 4 all worked fine. Tune 1 was also commandable in Mode 2 (software selectable), just not Mode 1 (hardware selectable).

[86GT]

Clint/Craig,

Any update on this? For the 1st time in a few months this happened to me again. I tried to download all 8 positions and the QH was still jacked up on a few tunes. Tune 1 never would run right. It kept coming up as Tune 3 when flipped to it via the switch. Tune 2, 3, and 4 all worked fine. Tune 1 was also commandable in Mode 2 (software selectable), just not Mode 1 (hardware selectable).

Chris have you found a pattern to duplicate this. I would like to get further into it but i can not seem to duplicate it on a regular basis.

[cgrey8]

I went months without seeing this issue, and I was downloading to various tune positions. However what seemed to cause it this time was downloading to a tune position that was not selected via the hardware switch. I have no clue why that caused it. But that's the only thing I can think that I did different. The odd thing is all tune positions were commandable in Mode 2. But Mode 1 got jacked up. All tune positions were stuck serving up tune 3. After switching to Mode 2, downloading to all positions, then going back to Mode 1, I could get all tune positions EXCEPT Tune 1. Tune 1 consistently came up as Tune 3. Although I could command Tune 1 in Mode 2, so I know it wasn't just tune tune position value that got downloaded wrong. After a bit more finagling (no clue exactly what I did), I got Tune 1 to work again. Like I said, I don't know exactly what I did to get it to work. But for something to try to experiment with, try downloading to a tune position OTHER than the one selected via the hardware switch while in Mode 1. It doesn't happen everytime. But it does seem to happen.

All I can say is thank goodness I got the tune selection datalogging feature so I can see when this happens and see what tune is actually being made active when this happens. With a hodge-podge of gasoline and ethanol tunes of various concentrations, having the QH jump to a wrong tune could be annoying if I didn't have my laptop with me to monitor it.

The good news is this only seems to be agitated by downloading/writing tunes. As long as tunes are not being written or are always written to the same position, the behavior of the QH seems stable.

[86GT]

Have you notified craig of this yet. If not i can contact him and have him read this thread.

[cgrey8]

No I haven't contacted him. But because he has responded to this thread in the past, he should be getting notifications when people update it.

[Craig Moates]

I share the frustration of being unable to reproduce any such behavior with regularity. We're committed to getting to the bottom of this if there is a bug, but so far I've not been able to make it happen at all and certainly not repeatably. If you have any ideas or want to come visit for the weekend, maybe we could try something heroic to illustrate this offline.

[decipha]

heroic

[Disney Lincoln]

I was just checking in on this to see if there was a for sure "fix" to it. Maybe the method, or maybe the sequence that i'm writing tunes? I haven't figured it out just yet.

[86GT]

We need to find a repeatable way to duplicate this.

[Disney Lincoln]

Amen. It doesn't always do it to me, but when it does it's extremely frustrating. I messed around with it for about a week back in Dec and eventually just quit on it. Reading Chris' post sheds a little more light on it, but I think I went through this back then too, I was trying everything it seemed. Anymore, I'm just ready to get away from multiple tunes anyways.

[blwn95gt]

Any update to this?

[Mike2042]

has this been resolved??

[EDS50]

has this been resolved??

I would hope so? Its been 7 years.