Moderators: cgrey8, EDS50, Jon 94GT, 2Shaker
Re: Delayed data logging
Is the latency setting global or application specific? I have a serial/USB adapter to connect to my Innovate WB.
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
Re: Delayed data logging
I just know that if it's not set to 2 on my computer I'm unable to datalog. Win7 32-bit.2Shaker wrote:Is the latency setting global or application specific? I have a serial/USB adapter to connect to my Innovate WB.
'89 Fox: 8.6:1 306, GT-40 lower, Blowzilla 2.2, ProM 92mm MAF, 90mm TB, LU80s, TwEECed A9L w/EDIS8
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
Re: Delayed data logging
Changing latency seemed to make no difference. It was set to 2 as Clint explained above, I tried 10 and 16 with no improvement. I still have to hit the "Start" button more than one time, sometimes as many as 4 or 5 times.
As for the logging, if I start the live data and check the log box after the dash is working I get a log.
Clint, any progress on these issues?
As for the logging, if I start the live data and check the log box after the dash is working I get a log.
Clint, any progress on these issues?
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
It seems to be specific to your PC or your type of PC. I have three PCs here and none of them are doing it with the same version of BE that you have.
To answer the question about latency, it is global. All devices will be affected when changed.
I am still looking but without a PC that is doing it in my possession it is going to be hard to fix.
To answer the question about latency, it is global. All devices will be affected when changed.
I am still looking but without a PC that is doing it in my possession it is going to be hard to fix.
Re: Delayed data logging
The workaround has been working reliably for me.86GT wrote:It seems to be specific to your PC or your type of PC. I have three PCs here and none of them are doing it with the same version of BE that you have.
To answer the question about latency, it is global. All devices will be affected when changed.
I am still looking but without a PC that is doing it in my possession it is going to be hard to fix.
'89 Fox: 8.6:1 306, GT-40 lower, Blowzilla 2.2, ProM 92mm MAF, 90mm TB, LU80s, TwEECed A9L w/EDIS8
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
Re: Delayed data logging
86GT wrote:It seems to be specific to your PC or your type of PC. I have three PCs here and none of them are doing it with the same version of BE that you have.
To answer the question about latency, it is global. All devices will be affected when changed.
I am still looking but without a PC that is doing it in my possession it is going to be hard to fix.
I'm going to remove and reinstall both BE and EA. I'm going to reinstall the older version of BE as I feel I need to get back to square one. This all started because the compare function wouldn't clear after 4 tunes had been loaded and I went to the latest BE.
FWIW, my PC is a standard off the shelf 3 year old HP with Win 7.0
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
If you would like i can log in and try to take a look.
Re: Delayed data logging
Thank you Clint. I will reinstall BE with the latest from your site, then I'll drop you an e-mail when I'm ready to have you connect to my PC. Probably won't be able to do this until next week.
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
Re: Delayed data logging
Sounds like maybe it's an HP thing!
I was sort of thinking of possibly changing my tuning laptop to a Lenovo X131e... not sure though.
I was sort of thinking of possibly changing my tuning laptop to a Lenovo X131e... not sure though.
'89 Fox: 8.6:1 306, GT-40 lower, Blowzilla 2.2, ProM 92mm MAF, 90mm TB, LU80s, TwEECed A9L w/EDIS8
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
My wife has an HP that i could test with. It is an older pavilion DV7
maybe?
maybe?
Re: Delayed data logging
Might be worth a shot. Nothing more annoying than having to field a bunch of software support calls for a specific platform. A DV7 is a reasonably expensive machine so I would be skeptical of duplicating the issue on it, but maybe there really is an issue with the cheaper HP machines. Some sort of component spec for their smaller form factor mobos might be causing an issue, perhaps...
'89 Fox: 8.6:1 306, GT-40 lower, Blowzilla 2.2, ProM 92mm MAF, 90mm TB, LU80s, TwEECed A9L w/EDIS8
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
'79 Bronco: 8.5:1 408C-2V, Lightning lower, Cobra upper, LMAF, 65mm TB, 24# injectors, EDIS8, Moates F3, single O2
'66 Mustang: 10.5:1 289, Victor Jr. EFI intake, 90mm TB, LMAF, 30# injectors, CDAN4 TwEECed
'00 Mountaineer: 9.2:1 302, ported Perf. RPM2, LMAF, 65mm TB, LU24As, READ0, QH currently
'08 & '09 Buell XB12Ss, 1125CR: DDFI3 tuned via TunerPro RT
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
I have seen this on two machines and both were smaller atom processor type PCs. Not sure if yours is an atom processor or not. The other weird thing is i noticed on one of them they had a single click action set in the control panel. Not sure if that has any barring on it or not.
Re: Delayed data logging
I did some testing today. I started by completely removing both EA and BE then loaded the current versions from the web site. I then tried changing the dashboard / logging refresh rates to 130 and 80 respectively. This seems to fix the inability to get the dashboard to work without repeated "Start"s. I can capture a log if I cycle the check box. BE still locks up if I shut off the car without stopping the log fist.
I also still cannot get EA to apply a lean/rich % across the MAF curve. Maybe I'm doing something wrong.
My PC is a Pavillion dv7, WIN 7.
I also still cannot get EA to apply a lean/rich % across the MAF curve. Maybe I'm doing something wrong.
My PC is a Pavillion dv7, WIN 7.
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
so anything faster than 130 ms is causing you to have to hit the start button twice?
the toggling of the enable really strange.
It just dawned on me. Check the permissions on the BE folder and make sure "EVERYONE" has full access to the directory and its contents. I am thinking BE does not have access to write to the config files which tell BE what to do and what to remember.
the toggling of the enable really strange.
It just dawned on me. Check the permissions on the BE folder and make sure "EVERYONE" has full access to the directory and its contents. I am thinking BE does not have access to write to the config files which tell BE what to do and what to remember.
Re: Delayed data logging
Permissions were not enabled. I set permissions in the BE directory and all sub-directories to everyone, full permission. I'll be able to try it later today. As for the 130/80 ms refresh rates, I just guessed at something greater than 100 and less than 200. I don't like the slower rate at 200.
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
Re: Delayed data logging
Permissions fixed the check box toggling issue, and the strategy compares.
I got 3 logs today and only the first required me to press start twice.
BE still locks up if you shut the car off without stopping the log first. And I changed the folder permissions in EA too but it did not fix the Lean/Rich button for the MAF curve.
How did the permissions get set this way to begin with? Did they come set that way with the downloads?
I got 3 logs today and only the first required me to press start twice.
BE still locks up if you shut the car off without stopping the log first. And I changed the folder permissions in EA too but it did not fix the Lean/Rich button for the MAF curve.
How did the permissions get set this way to begin with? Did they come set that way with the downloads?
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
no the permissions is set on the OS level. I will look at my installer but it does not set permissions.
The lean rich in ea is working if you put values in the lean rich column. what about it is not working? Is it that no calculation is done or what.
The lean rich in ea is working if you put values in the lean rich column. what about it is not working? Is it that no calculation is done or what.
Re: Delayed data logging
Sorry Clint, brain fart on my part. It works. I think this brings an end to this thread, thanks for all your patience and help (and Shaker666 as well!) I'll leave it that the BE lockup when shutting off the car while logging is something you'll tackle later on.
94 GT, CBAZA/J4J1, 347 (on a R302 block), F303 cam, Performer II Intake, 1.7 Crane RR's, 1 5/8 Shorties, 70MM BBK TB, C&L 85mm Tuner MAF, Pro-Charger D1SC, 60#'s, TKO 600. Runs 11:80's
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
I did some research on the permissions. It looks like Microsoft has now forced the Program file folder to be read only/execute for all non administrators. They expect all programs to move their data to the Program Data folder. It appears that in windows 8.1 and later we will not be able to even change the permissions in the program Files folder.
I really do not want to break BE out into different directories darn Microsoft.
I really do not want to break BE out into different directories darn Microsoft.
Re: Delayed data logging
Why not install off the root?
85GT, 302 w/Dart Windsor Jr heads, Crane 2030 equiv. Performer 5.0, 75mm TB, 88mm slot MAF, 34lbs injectors, BBK shorties, 5spd converted to 4R70W with Baumann controller, 9" rear w/3.25s
A9L running A9P bin via Quarterhorse w/LC-1 WB
A9L running A9P bin via Quarterhorse w/LC-1 WB
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
i can do that too. I might do that to get around the Microsoft requirement.
Just not sure if windows 8.1 is doing that on all but the program data folder. I need to do some more research
Just not sure if windows 8.1 is doing that on all but the program data folder. I need to do some more research
Re: Delayed data logging
Just upgraded to dongle and BE2012 from BE2010. My normal tuning computer is still running BE2010 and works great with Tweecer and LM2. But I'm having issues with BE2012 upgrade, Tweecer and logging. Both laptops are running Vista, one that works with BE2010 and LM2 and the one that is struggling with BE2012.
I'm having same issues notes in this post, sometimes it will start logging, but most times it won't. I'll try changing latency with ctl+l to 200.
BUT has there been any updates to BE2012 to address this?
Greg
I'm having same issues notes in this post, sometimes it will start logging, but most times it won't. I'll try changing latency with ctl+l to 200.
BUT has there been any updates to BE2012 to address this?
Greg
72 Ford Bronco, 4 speed Toploader O/D Tranny, 94 Roller 408W, A9L, 85mm Pro-M Delphi, 36lb/hr inj, Torker II, 1000 cfm TB, Custom cam (@.050 I218 E224 Lift I.571 E.574 w1.6rocker), AFR 185 comp, Short tube ceramics, 3" exhaust, 4.5"suspension, 1" body, 33x10.5, D20 transfer case, D44 front, Ford 9" rear, 4.11 gears, Tweecer R/T + Innovate LM-2 WB + BE 5.365
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
When t stops logging what is the error message in the status bar. If you would like i can log in and take a look.
Re: Delayed data logging
Thanks for the quick response Clint. Let me play around tonight. I'll apply permissions and change latency and see if I can get any behavior change. I'll try and get a bit more information and exact behavior.
Greg
Greg
72 Ford Bronco, 4 speed Toploader O/D Tranny, 94 Roller 408W, A9L, 85mm Pro-M Delphi, 36lb/hr inj, Torker II, 1000 cfm TB, Custom cam (@.050 I218 E224 Lift I.571 E.574 w1.6rocker), AFR 185 comp, Short tube ceramics, 3" exhaust, 4.5"suspension, 1" body, 33x10.5, D20 transfer case, D44 front, Ford 9" rear, 4.11 gears, Tweecer R/T + Innovate LM-2 WB + BE 5.365
Re: Delayed data logging
Well, tried setting latency. Didn't help. Also tried giving users full permission to BE folder and subfolders (through inheritance) but no luck. No error messages. But the status at bottom says Tweecer: Started and then Tweecer:Polling Stopped. I used FTClean to clear all drivers then reloaded both bus and serial using those in the BE2012 drivers folder. Dates on Drivers for USB and Port are 1/18/2013. My only guess is that I have the driver messed up somehow. I've had the problem before. Be great if you can take a look. Once I figure this laptop out I need to update my good one.
Greg
Greg
72 Ford Bronco, 4 speed Toploader O/D Tranny, 94 Roller 408W, A9L, 85mm Pro-M Delphi, 36lb/hr inj, Torker II, 1000 cfm TB, Custom cam (@.050 I218 E224 Lift I.571 E.574 w1.6rocker), AFR 185 comp, Short tube ceramics, 3" exhaust, 4.5"suspension, 1" body, 33x10.5, D20 transfer case, D44 front, Ford 9" rear, 4.11 gears, Tweecer R/T + Innovate LM-2 WB + BE 5.365
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
setup teamviewer.com and send me the id and password.
Re: Delayed data logging
sent via pm
72 Ford Bronco, 4 speed Toploader O/D Tranny, 94 Roller 408W, A9L, 85mm Pro-M Delphi, 36lb/hr inj, Torker II, 1000 cfm TB, Custom cam (@.050 I218 E224 Lift I.571 E.574 w1.6rocker), AFR 185 comp, Short tube ceramics, 3" exhaust, 4.5"suspension, 1" body, 33x10.5, D20 transfer case, D44 front, Ford 9" rear, 4.11 gears, Tweecer R/T + Innovate LM-2 WB + BE 5.365
Re: Delayed data logging
Just wanted to follow-up on my issue. Clint jumped on teamviewer last night and did some troubleshooting. There was an error in the GUFB - Revision 98 strategy file for DSDRPM on the Payload worksheet. Not exactly sure of the error in the file but Clint will contact Chris. Now works as expected.
Greg
Greg
72 Ford Bronco, 4 speed Toploader O/D Tranny, 94 Roller 408W, A9L, 85mm Pro-M Delphi, 36lb/hr inj, Torker II, 1000 cfm TB, Custom cam (@.050 I218 E224 Lift I.571 E.574 w1.6rocker), AFR 185 comp, Short tube ceramics, 3" exhaust, 4.5"suspension, 1" body, 33x10.5, D20 transfer case, D44 front, Ford 9" rear, 4.11 gears, Tweecer R/T + Innovate LM-2 WB + BE 5.365
- 86GT
- BE/EA Developer
- Posts: 5142
- Joined: Sat Feb 22, 2003 11:19 pm
- Location: Dixon, California
- Contact:
Re: Delayed data logging
There is a space in one of the columns that BE did not like. I am changing BE to handle this better and not complain.
Who is online
Users browsing this forum: No registered users and 17 guests