[2Shaker]

If you don't use the auto trigger functionality for data logging is there a delay before it will start logging when you press the "Start" button? I don't use the auto start functionality and I find myself having to press the "Start" button several times after the car starts before it will start logging.

[cgrey8]

If I'm just datalogging the QH, there is almost no delay. Logging begins within 0.25-0.5 seconds of hitting the button.

However when also datalogging my LC1, there is a definite delay between hitting the start button and when values actually populate. In fact, it appears all of BE is locked up during this delay period until logging begins. So don't get impatient and keep hitting the button or you might queue up hits on the button that stop/start/stop/start BE multiple times.

I've never used the auto-logging feature to know what it even is. I just always hit the space bar or click the green START button to start datalogging.

One of the things I find frustrating is when something happens that causes BE to stop datalogging. Sometimes its Windows (or the FTDI driver) that gets screwed up requiring I disconnect and reconnect the USB devices. However most often just restarting the datalog is all that's required. What I'd like is a way for BE to just always be datalogging from the moment supported (and licensed) hardware is inserted and only stop when I disconnect the hardware or it has to (i.e. downloading a new tune). If an error occurred that would normally stop logging today, I would want BE to retry as long as it saw the hardware still connected. With all that working and in place, I would probably want a "trigger" to tell BE to only save what it datalogs to file when there's specific activity like RPMs > 0 or MPH > 0, but otherwise just datalog for display.

[2Shaker]

Thanks Chris. I must be one of the few who has not gone over to QH - I'm still running the TwEECer. FWIW I'm on BE 5.27.25.

[cgrey8]

It's been so long since I used the TwEECer that I can't tell you what modern BE does with it. However it wouldn't surprise me if there is a delay datalogging it.

With the QH, BE rewrites the patch code to the tune when you start datalogging. Since it is only writing small amount of data, it doesn't take long to perform. However with the TwEECer, you can't do this. If you write to a portion of the tune, you have to write the entire tune. BE used to not rewrite the patch code on datalog back when I used it on the TwEECer. It simply assumed that the payload selected is still whatever it was last time you wrote the tune to the TwEECer...and thus immediately started datalogging. But I wouldn't be surprised if every time you datalog today with BE, it's rewriting the tune. If that's the case, there would be a noticeable few seconds of download time waiting for the tune-write to complete every time you started datalogging.

[Shaker666]

A few weeks ago I sent my QH back to Moates for RMA because it wasn't logging at all for some reason. We debugged things for quite a while, but eventually all fingers pointed at the QH itself. I swapped a TwEECer RT in its place and there is much more happening, but it's definitely got some issues too. Regardless, I can at least view realtime data with the TwEECer whereas the QH was only able to flash new tunes.

I'm using an HP Mini 210 laptop as tuning device. Has 2GB of RAM, Windows 7, 180GB SSD. The issues:

1. Generally speaking, I have to press the Start button for datalogging twice to get it to start logging.
2. No matter where I specify the log locations to be, no datalogs are to be found anywhere.
3. I've tried making BE "Run as Administrator" and that seemed to have literally have worked once, but never again.
4. If the car is turned off while BE is displaying realtime data (datalogging doesn't work), BE will lock up. Have to use ProcessExplorer and kill it then restart it.

Finally, just a few minutes ago I encountered an issue I've not seen before and could not resolve it. I'd start realtime logging with BE and the timer was running, but the data had stopped updating. Restarting the computer didn't help. I packed it in for the day! Hoping to get some of Clint's time to help me figure these issues out next week. Anyone else seen this before?

[2Shaker]

....The issues:

1. Generally speaking, I have to press the Start button for datalogging twice to get it to start logging.
2. No matter where I specify the log locations to be, no datalogs are to be found anywhere.
3. I've tried making BE "Run as Administrator" and that seemed to have literally have worked once, but never again.
4. If the car is turned off while BE is displaying realtime data (datalogging doesn't work), BE will lock up. Have to use ProcessExplorer and kill it then restart it.

Finally, just a few minutes ago I encountered an issue I've not seen before and could not resolve it. I'd start realtime logging with BE and the timer was running, but the data had stopped updating. Restarting the computer didn't help. I packed it in for the day! Hoping to get some of Clint's time to help me figure these issues out next week. Anyone else seen this before?

I'm having the same troubles with your numbers 1,2 and 4.
1. When I press "Start" it acts like it's going to log as it turns on "Stop" but then after a few seconds "Start" is displayed again. I have to press "Start" several times before it finally starts to log.
2. When I do get it to log I only find one or two logs in the Datalog directory, so it's intermittent.
4. If I'm watching the dash display live data and I turn the car off without stopping the logging and the dashboard display then BE locks up and I have to use Control/Alt/Del to close it.

I this all may be related to the data log auto start functionality. I noticed this on page 39 of the "Help" file and I have never seen that before, but I don't know when Clint implemented this functionality. I excerpted that section below:

"Data logs can also be auto started based off of a user defined TAG and its corresponding
value. If the Auto Start is enabled, Binary Editor will keep a 200 row buffer in memory until
the TAG value has been exceeded. When the TAG value has been exceeded the buffer
will be flushed to the data log and normal data logging will start. The buffer is used so the
data log will show what happened just prior to the Auto Start being triggered."

I do not use the Auto Start functionality.

[Shaker666]

I don't use the auto start logging feature, either. I expect it to log when I press Start and stop when I press Stop or turn the engine off. That's how BE '10 used to work, at least.

I do know that not all USB cables are made the same. I have a USB cable in use that has a cylindrical filter on one end and thick, shielded insulation. When I started having my most recent issue where it would start logging and then stop a few seconds later, I realized that I had plugged in a USB extension to reach my laptop and that may have actually been the source of the problem. I'll verify this soon and post up.

Not sure if you're aware of this keyboard shortcut, but Ctrl-L brings up a dialog which allows you to change some values such as Latency Timer, Reset Pipe Retry Count, Minimum Read Timeout, Minimum Write Timeout, and USB Transfer Sizes. I've had some luck with changing my Latency Timer and USB Transfer size values. Might be worth a shot.

[2Shaker]

I have a USB cable in use that has a cylindrical filter on one end and thick, shielded insulation. When I started having my most recent issue where it would start logging and then stop a few seconds later, I realized that I had plugged in a USB extension to reach my laptop and that may have actually been the source of the problem. I'll verify this soon and post up.

I think I have the same cable so I'd be interested in your findings.

[Shaker666]

Ok, so using JUST the USB cable directly from my TwEECer RT results in a successful realtime display... still not able to datalog for some reason, however. The cable I have is 6 ft long and has a filter on it. If I attach an extension to the cable, things don't work very well anymore.

[2Shaker]

Ok, so using JUST the USB cable directly from my TwEECer RT results in a successful realtime display... still not able to datalog for some reason, however. The cable I have is 6 ft long and has a filter on it. If I attach an extension to the cable, things don't work very well anymore.

I never had any of these problems with previous versions of BE and I've had the same cable for years. Something is wrong with the SW. And yesterday I got the dashboard to work on several different runs by pressing the "Start" button several times, but like you I find no logs even though the log check box is marked.

[Shaker666]

Ok, so using JUST the USB cable directly from my TwEECer RT results in a successful realtime display... still not able to datalog for some reason, however. The cable I have is 6 ft long and has a filter on it. If I attach an extension to the cable, things don't work very well anymore.

I never had any of these problems with previous versions of BE and I've had the same cable for years. Something is wrong with the SW. And yesterday I got the dashboard to work on several different runs by pressing the "Start" button several times, but like you I find no logs even though the log check box is marked.

I thought I was the only one with datalogging issues! My situation began after I completed an EEC-V conversion on my classic Mustang and forget datalogging, realtime display didn't even work. Turns out that I had to send my Quarterhorse back to Moates for RMA, Derek needed to update the strategy file, and Clint had to upgrade me to BE '12. Finally, I got realtime display to work, but I've still never seen any datalogs. I'm currently connected to a TwEECer RT as well. As far as logging goes, I did get a single log once... but I've never been able to get it to do that again. I'm trying to get some of Clint's time to help me resolve the issue; I'll keep you posted.

[2Shaker]

As far as logging goes, I did get a single log once... but I've never been able to get it to do that again. I'm trying to get some of Clint's time to help me resolve the issue; I'll keep you posted.

I hope he can resolve this soon. I too got just one log - thought I had gotten more.

[Shaker666]

As far as logging goes, I did get a single log once... but I've never been able to get it to do that again. I'm trying to get some of Clint's time to help me resolve the issue; I'll keep you posted.

I hope he can resolve this soon. I too got just one log - thought I had gotten more.

He mentioned being able to look at it this evening, possibly. I'll keep you posted.

[decipha]

what is your latency set to?

[Shaker666]

what is your latency set to?

I've tried 2 and 16 and everything in between. I can get BE to display the data in realtime, but it doesn't want to log to disk. Any disk for that matter, not the main HDD (SSD) or an SD card.

[86GT]

Does the directory have permissions set to everyone. If not it should. If you still have issues send me the teamviewer id and password via email and i will log in and try to help

[2Shaker]

Does the directory have permissions set to everyone. If not it should. If you still have issues send me the teamviewer id and password via email and i will log in and try to help

Will this fix the problem that the real time data doesn't start until I press the "start" button multiple times?

[86GT]

I doubt that. Have you tried the later build of BE 5.27 that is on the web. I am currently working on that build so i can make changes if needed.

[Shaker666]

Does the directory have permissions set to everyone. If not it should. If you still have issues send me the teamviewer id and password via email and i will log in and try to help

I did try this and it's still not logging... very curious indeed.

[86GT]

Is there anyway i can log in using teamviewer?

[Shaker666]

Is there anyway i can log in using teamviewer?

Of course, I'll be home around 8:30pm tonight. If that works for you, let me know. Everything else appears to be working, it just won't record to file. The QH is being shipped back from Moates, but won't be here in Tucson until Saturday according to USPS so still stuck with the TwEECer RT for now.

[86GT]

ok so tweecer is not logging either?

[2Shaker]

ok so tweecer is not logging either?

Correct, I'm seeing the same things Shaker666 is seeing. Dashboard does not start and if it does the log is nowhere to be found. Well I did get 1 log and I think it might be the one from the first time I tried to open the dashboard and see live data. Also, the way the logging is behaving is that you hit the green start key and it changes to red ("stop") immediately but no data is displayed. After a few seconds it switches back to green "start". I will go through this cycle several times before it starts to display. The "log" check box is marked.

[86GT]

Ok when you are ready i am. Just send me the id and password via email and have the car ready with the laptop connected.

[Shaker666]

Alright, thanks Clint, for logging in and checking things out.

I'm not convinced this is an Intel Atom specific issue... it might be a gutless processor issue, but not sure if it's isolated to Atoms (possibly, they are the most gutless, after all).

Here's a few workarounds, for sure... hopefully get you by until an update is released that resolves things permanently.
1. Ctrl-L and try setting the latency timer to 2.
2. Once you've successfully started realtime logging to the display, uncheck the Enable checkbox and then check it again. That should create a datalog wherever you've set the location. Basically, cycle the Enable checkbox after you've started datalogging.
3. Dashboard refresh and Data Logging rates less than 200 ms do not work on my computer. I have to set them both to 200 ms and I'm able to datalog.

Hope that helps.

[86GT]

You are correct. The procedure you mentioned is the workaround. I just tested this all last night on my PC. The logging starts and stops with one click. I dont have to cycle the enable checkbox. While logged in i noticed something different within windows and not BE. You do not have to confirm any deletes and most everything i did only required a single click and not the typical double click. Do you have the settings changed for the mouse or anything that you can remember?

[Shaker666]

You are correct. The procedure you mentioned is the workaround. I just tested this all last night on my PC. The logging starts and stops with one click. I dont have to cycle the enable checkbox. While logged in i noticed something different within windows and not BE. You do not have to confirm any deletes and most everything i did only required a single click and not the typical double click. Do you have the settings changed for the mouse or anything that you can remember?

Aside from unchecking the delete confirmation from the Recycle Bin and turning off Windows Aero, the computer is pretty standard. Win7 32-bit, 2GB RAM, 180GB SSD. Double-click is generally required for most operations, maybe that was an artifact of using TeamViewer or something. I have definitely noticed that adjusting the refresh rates for datalogging and display affects whether a datalog will start or not. Values less than 200 ms on this machine and it's probably not going to work.

[86GT]

ah ok, if the refresh is affecting it then i will test that tonight. I never thought about the refresh rate i have mine set at the defaults. I will crank it down to 5 ms and see if it logs.

[2Shaker]

I assume the latency timer is a Win 7 or BE function. What does it do? Is it an option in BE that I have to worry about with TwEECer?

[86GT]

The latency is a value that tells windows how long to wait for the next communication request. All windows xp machines have this set to 16 and any newer os uses a value of 2.

Yes the tweecer is affected by this too. The lower the number the faster the device will communicate but the higher the chance of errors.

To set the value press curl L when be is open and has focus.