[firemanwill28]

I've been having trouble the past couple days with my QH losing connection while daatlogging. Anyone else have this issue and know a fix? I cant ever remember having this issue with the Tweecer. I seems to do it at randome times and I cant seem to nail it down.

[firemanwill28]

I used the search funtion and found a thread from a couple years back where a few people were having this same issue. So I went to Radio Shack and purchased the lare ferite bead and will test it tomorrow.

[firemanwill28]

I'm still losing connection while datalogging. This is happening at radom times and it just dies off. To fix it, I have to shut the car off, unplug the QH and LC-1, and restart BE. It happened four times today in all four datalogs I ran.

Any ideas? :dunno:

[85GT]

Is it something like I'm experiencing?

viewtopic.php?f=10&t=17816

[firemanwill28]

Is it something like I'm experiencing?

viewtopic.php?f=10&t=17816

Yeah, that looks like the same problem. Just stops datalogging at radom times.

[85GT]

I emailed Clint about it last week. He said possibly bad connection on the J3 connector. To try reseating/cleaning. I haven't tried yet. Hopefully this weekend. Other option he offered was that crossloop thing. I'll look into that afterwards.

It's a shame as it worked so well before it developed the problem.

[firemanwill28]

We'll I made a few changes with the latency and such and was able to datalog for about 15 minutes without it stopping on me; I actually stopped in manually. Now the problem is the datalog file doesn't seem to be saved anywhere, I also did a search for the file and nothing was found. Is there a setting I might have changed that would have not allowed the datalog to be saved?

[Jamlx1]

make sure you have the checkbox on the bottom right of your dashboard 1 or 2 where the start stop button is checked. it will then save your datalogs under the datalogs file folder.

[firemanwill28]

make sure you have the checkbox on the bottom right of your dashboard 1 or 2 where the start stop button is checked. it will then save your datalogs under the datalogs file folder.

I check this tomorrow when I get home from work.

Thanks, Will

[firemanwill28]

I seem to be running datalog without losing connection these days. I did change my latency settings as indicated by the Moates tech support.

[85GT]

Where are those latency settings?
Seems my problem is doing better by having reduced the payload. I'm able to now log again. Liljoe had same problem and it worked for him too.
But, would like to see these setting too.
Where on the Moates site is that info?
Thanks

[firemanwill28]

Where are those latency settings?
Seems my problem is doing better by having reduced the payload. I'm able to now log again. Liljoe had same problem and it worked for him too.
But, would like to see these setting too.
Where on the Moates site is that info?
Thanks

I sent an email to their general tech support address. The latency can be brought up in BE by pressing Control L. I'd send an email over to Moates, they're pretty responsive.

[85GT]

Ahh... see it. Mine is set to the max of 16. What was yours before and after if you don't mind?

[firemanwill28]

Ahh... see it. Mine is set to the max of 16. What was yours before and after if you don't mind?

I was set at 16 and now have it at 2. There's another setting in the device manager, I'll see if I can forward the link from Moates that walks you thru the process.

[EDS50]

Just to give everyone an update, Clint, Craig Moates and I have been testing a fix for this issue and I am confident we have come across the fix since I was having the same issue with BE and TunerPro but am still testing the final settings. Like most of you this issue happened out of the clear blue sky and I believe it has something to do with windows update but I cant confirm it. The fix seems to be a combination of having the correct ftdi driver installed which is v.2.8.12 which can be downloaded from the moates.net website and the more important setting (in my oppinion) that has fixed my issues are the latency settings in BE that Clint and I have been working on. When BE is open hit ctrl-L and the latency screen will come up. The first two settings up to are latency timer and pipe count. Set Latency to 2ms and the pipe count to 26. Leave the timeouts at 0 and transmit bytes to 4096. Having a ferrite bead attached to the usb cable at the bulk head connector and at the pc end of the usb cable seemed to help me as well. I aslo have an advanced version of BE that is not available yet but this fix should work the same for BE2010 and under. Hope this helps.

[firemanwill28]

Here is some more information from Moates support that helped me as well.


We're waiting to hear back results from some other people who are having similar issues. I'll keep you posted as we have more information. WinXP is known to be really shitty with USB drivers.
Try these drivers to be certain, and make sure you have followed the USB troubleshooting guide.
http://support.moates.net/2009/02/10/us ... oting-101/
http://www.moates.net/cd/USB%20Device%2 ... taller.exe

Thanks,
-Dave Blundell
Moates.net Support

[EDS50]

Here is some more information from Moates support that helped me as well.


We're waiting to hear back results from some other people who are having similar issues. I'll keep you posted as we have more information. WinXP is known to be really shitty with USB drivers.
Try these drivers to be certain, and make sure you have followed the USB troubleshooting guide.
http://support.moates.net/2009/02/10/us ... oting-101/
http://www.moates.net/cd/USB%20Device%2 ... taller.exe

Thanks,
-Dave Blundell
Moates.net Support

I am the one they are waiting on...lol.. I sent Craig an email tonight since Dave really is out of the loop on it. Craig, Clint and I have spent countless hours on this running live with me in the car. As far as xp, pay no mind to Dave's comments as he is sadly mistaken. XP proved to be the stable os vs. Vista. Whats odd id that Vista has been equally stable up to this point but has proven to be stable again with the latency changes. Dont waste your time with the moates trouble shooting links you have provided with the exception of maybe the comport settings but those settings have made no difference on my machines. That seems to be a generic response from Moates tech support. You will have to trust me on this.

[liljoe07]

When BE is open hit ctrl-L and the latency screen will come up. The first two settings up to are latency timer and pipe count. Set Latency to 2ms and the pipe count to 26. Leave the timeouts at 0 and transmit bytes to 4096.

I have BE 2010 and only settings that come up are the Latency settings. The rest of the settings you listed must just be for the Advanced Edition you have, and us mere Mortals cant get yet. :coffeespray:

[EDS50]

When BE is open hit ctrl-L and the latency screen will come up. The first two settings up to are latency timer and pipe count. Set Latency to 2ms and the pipe count to 26. Leave the timeouts at 0 and transmit bytes to 4096.

I have BE 2010 and only settings that come up are the Latency settings. The rest of the settings you listed must just be for the Advanced Edition you have, and us mere Mortals cant get yet. :coffeespray:

LOL, those setting I posted should all be in the latency window when you open it. If not the 2 important ones are the latency and pipe count. The other area Clint and I are currently discussing revolve around properly configuring the comport settings which up until now have not been neccessary. It appears that the tutorial in the link firemanwill provided explains the comport settings in detail.

[liljoe07]

When I hit control+L, only thing it allows me to change is the Latency. Nothing about pipe count at all.

[EDS50]

When I hit control+L, only thing it allows me to change is the Latency. Nothing about pipe count at all.

Hmmm, its probably just the difference between the build you and I have of BE. Set the latency to 2 and see how that works and we'll go from there.

[firemanwill28]

When I hit control+L, only thing it allows me to change is the Latency. Nothing about pipe count at all.

Thats the same for most if not all of us; Ed is just special and gets more settings.

[cgrey8]

There's a Beta 2011 version that has more than just latency. Clint's furiously working to solve some really stubborn problem before releasing.

[EDS50]

When I hit control+L, only thing it allows me to change is the Latency. Nothing about pipe count at all.

Thats the same for most if not all of us; Ed is just special and gets more settings.

:coffeespray:
I'm not special, I'm just helping out with testing the beta before Clint Releases it.

[85GT]

Appreciate you guys working on it, but,this is starting to get old.

What looked like a workaround solution a few days ago of making the payload smaller is no longer working either.

I got a whole minute and a half of logging on the first attempt. It then crashed. Spent a half an hour restarting, making smaller, changing latency... nothing.

Maybe those tweecer's are more valuable then we think...

[cgrey8]

Weird. The only problem I've had with my QH is the tune selection. Otherwise, I'm quite content with it and value it WAY more than I do my TwEECer. The whole thought of reverting back to the TwEECer makes me cringe so badly I get cheek-muscle cramps.

[85GT]

Not that weird if they are working on the problem.

Well maybe not tweecer, but maybe a different software...

[EDS50]

Well for some reason my logger failed twice today out of the clear blue sky again. I guess its back to the drawing board with this problem..lol..

[liljoe07]

Well for some reason my logger failed twice today out of the clear blue sky again. I guess its back to the drawing board with this problem..lol..

Thats just great Ed! Way to pump us full of hope, then pull the rug out from under us. :coffeespray:

What computer platform are you using?

[EDS50]

Well for some reason my logger failed twice today out of the clear blue sky again. I guess its back to the drawing board with this problem..lol..

Thats just great Ed! Way to pump us full of hope, then pull the rug out from under us. :coffeespray:

What computer platform are you using?

Sorry, I didnt want to skew the results by not being honest. HP pavillion laptop with vista.