[Toy94GT]

Running BE 5.212 running on windows 7.
I can data log fine when the hardware is not enabled. But with it enabled it will not log and does not give any error. Looks like it tries to start but just stops.
I can use Windaq and see the data from my wide and O2/dataq.

[cgrey8]

When working with auxiliary devices such as datalogging the DataQ or Innovate hardware, it's best to disable everything else and focus on getting JUST that device working. Once you have it working, you can go back and active your primary device (e.g. Quarterhorse or TwEECer).

As for why its not datalogging, click on the recent log history list at the bottom of the BE screen. You see it updating when you do things like start/stop a datalog. If you click it, it should expand and show you the most recent 10 entries. See if there's any errors that are showing up in there that may give a hint as to what's happening.

The most common things to check are that BE is configured for the correct COM port.
Next check that BE has the DataQ inputs checkboxed/selected.
Then confirm you have a valid transfer defined that will convert the DataQ's voltage values to datalogged/display values. I believe that transfer is a bit finicky in that you have to make sure the numbers go in a specific order. It seems like the first column has to be larger numbers on top. But I can't remember right off. If in doubt, try just a 2-row transfer with the values in the 1st column being 0 and 10, then 10 and 0. The values in the 2nd column are not as important for just diagnostics, but they do need to be set to something that's different so you can see if the datalogging is working so set the values in the 2nd column to the same value as its counterpart in the 1st column.

Once you get the datalogging to work, then you can go back and put whatever the real numbers need to be...and add more rows if that's necessary. Although most WBs are linear devices, so MOST of the time, you don't need more than 2 lines for them. There are reasons why you might add a 3rd, but don't worry about them right now. Just get the datalogging working for now.

[Toy94GT]

Cgrey8

It was working last time I was tuning with the original 2012 version. I built a stroker over the winter and am back to tuning. I am using the same laptop.

If I am following disable tweeter and try to get just Data Q logging. I did not realize I could just log AFR from my wide-band via Data Q.

I cannot find where to set the com port parameters in the current version. In the original 2012 it was in the hardware dialog.

Yes, I have the Data Q enabled on the hardware screen and have the transfer defined.

The event log says tweeter not connected. But I can read write and log if DataQ is not enabled.

Thanks for your help.
Bruce

[Toy94GT]

Tried with just Data Q enabled and the log said device not responding.

[cgrey8]

If you are confident the COM port BE is using is the same as your DataQ, then this sounds like something Clint may need to remote into your system and look into. I can't think of anything else to try that I haven't already mentioned.

The good news is it's getting a LOT easier to support people like you now, even us guys here on the forum with tools like Zoom, which will let us communicate and share screens. It'll even let the other person take control of your system and poke-around to figure problems out as if they were using your keyboard. That's powerful stuff.

[Toy94GT]

Can you tell me where I can verify the com setting in BE?
It use to be on the HW screen but it is no longer there.

[04Lightning]

You likely have this sorted by now, I have had similar issues with my 04 Lightning (PCM Catch Code URB1) TDT0 strategy.

Win 7 laptop with QH and BE on a dongle, dataq 4 channel logger (unplugged now) LC2 WB and controller. I Had the dataq first with not much luck in BE. Driver issues somehow not working in BE (current ver 5.203)

My issue is similar yours, save for the fact that when I hit data log sometimes it stalls my motor. And occasionally breaks communication with my instrument cluster, causing a no start. Dashes in the odometer. A quick re-flash of the tune corrects this.

3-ish Things I have had to do to data log.

1- I Removed all Dataq drivers from my laptop.
Installed Innovate LC2 and software to set WB parameters. Bought the innovate license from Clint, and configured the parameters in BE to match the WB. This is working good now.

2- Save the payload logging list in BE I want to log along with the calibration (tune) I am going to burn to the QH.

3- Erase the previous tune in the bank I want to burn the new one to.

I don't start or stop logging while driving because it has shut me off on the road....Having to coast over to the side of the road, and do the re-flash and get home.

Neither Dave B. at Moates nor Clint G. could figure this out. I even bought Moates $40 OptoIsolator. No change.

It's taken me a bit long to tune, but it does work now enough to get it done.

I think my 4 bank tunes are large enough that might cause load up issues in the QH??

[Toy94GT]

04Lighting

Actually just getting back to this.
So if I am following.
You removed the Dataq drivers.
You still connect the Datq to a serial port.
Then using the Innovate LC2 software set it up.
Then license the use of Innovate LC2 from Clint

Does that sound correct?

Thanks Bruce