TE datalogging issues
 

Everytime I try and log, as soon as I hit the gas I get a subscript out of range error and the plugin freezes.

Using Xeno's USB datalogging cable, latest version of the ECU control plugin for TE and the latest version of TE, and NG60 code.

Any ideas?

Re: TE datalogging issues
 

which plugin? latest version doesnt mean much, theres a shitload of plugins floating around...

Re: TE datalogging issues
 

TE from Xeno, and whichever version is latest on pgmfi.org Opensource ecucontrol thread, I picked it up 2 days ago.

Re: TE datalogging issues
 

have you tried the standalone version of ecucontrol version 5.8.41? make sure that works, then mess with the plugins.... some of them dont work well..especially the opensource ones, because they are works in progress....

Re: TE datalogging issues
 

Yup, the standalone works great, it's the plugins that suck.

I really just want maptrace/wideband reading. I could do it with the standalone, but it's going to require some ------sheeting on my part I guess.

Re: TE datalogging issues
 

my advice is to use the standalone for the logging (csv output) and the plugin for the maptrace (and csv output). a lot of the plugins lock up when you check log file....because they are trying to get other stuff to work and have disabled it or just fucked it up (plus they have removed time as one of the values which is important).

also, i havent seen any plugin that shows the correct wideband reading...just log the wideband voltage and convert it in excel... or depending on what sensor you have, set 2V=20AFR and 0.8v=8AFR and just read the voltage as afr. ie, if you see 1.54v that equates to 15.4AFR...etc

ill look when i get home to see where i got some of the plugins that will log file also...and let you know.

Re: TE datalogging issues
 

I gave up on the plugins too. I just use the standalone ecucontrol, I'm about to move up to Obd1 and an ostrich. FTW

Re: TE datalogging issues
 

Yeah, I think I'm just going to do that. If I log boost, RPM and wideband voltage and then Excel everything, I should be able to go back through my maps and edit everything, it'll just be a little more time consuming.

Re: TE datalogging issues
 

I gave up and I am converting to OBDI as we speak.

Re: TE datalogging issues
 

What the ---- are all your pussies problems...

DONT USE ECUCONTROL....IT HASNT BEEN DEVELOPED IN OVER A YEAR

The version of TurboEdit that I put for download in the first post of the TE sticky thread has the version of TE I know work with the Ostrich FLAWLESSLY and also has DATALOGGING built-in with a working MAP trace and all...

Delete every plug-in or version of ECU control you have, install that version of TurboEdit and have fun...flawless tuning fun :)