obdo shit
 

Ok I have a chipped pr4 I am using turbo edit. Turbo edit works ok but I need to data log I am trying to use free log beta. I have the code set to ng60 obdo I have the rpm and map scale to match turbo edit. I have the wide band set to match my lc-1. I have my com port set rite. I hit connect it hooks up for about a min I get clear rpm reading but my map always floats around -17 then it says unstable would you like to stop dataloging.


What do I do? Should I try different programs?

Re: obdo shit
 

I also have a pr4 and I always had problem with dataloging. If it work, it work for 2 minutes and crash. I tried with TE, BRE, freelog and nothing to do...

I don't know if it's the cable I use or the ECU but it's not fun :3

BRE has cool features though...

Re: obdo shit
 

I cant ever get bre to work. What features are you talking about? I also have a pm6 I could chip has any one had luck with a pm6? Maybe its just a pr4 thing or a obdo thing.

In the 2 mins do you get a clear map signal?

Re: obdo shit
 

try downloading the later version of turbo edit http://www.-------------/te.php?page=te_cover ,

a tip from getting the logging error is to go into tools/options, then under the tps log data set it to like 5% for the min and 100 to max, that will keep from logging all your idle ----, and only logging when you crack the throttle. you only have a limited amount of space to store all the logs and one its full you will get an error that locks up the app.

Re: obdo shit
 

use the ecuControl plugin for turboEdit. You can get it here:
http://forum.pgmfi.org/viewtopic.php?f=60&t=14776

Make sure you get the latest version...just scroll to the bottom of the thread. It works really well and has a lot of nice features. O0

Re: obdo shit
 

cant get the plugging to work how did you do it? I thought ecu control was another rom editor?

Re: obdo shit
 

don't use that ----, that version of te has the ------- datalogger built into it, rightclick file, go to datalogger and it will open, then go to tools options and set up all your com ports and your tps ----, it should remind you to do that before it starts logging as well. ecu control doesn't allow you to maptrace

Re: obdo shit
 

Ok thanks got it to work on my home computer but my laptop is different it will not recognize .dll files. I’m running xp at home and 98 on the laptop. Any help?

Re: obdo shit
 

98? damn man lol. Well whats the error your getting and where did you install the program?

Its not an issue with windows 98 not recognizing .dll files because even 3.0 used them, problem is the guy that wrote both the original and newest open source version of TE used xp and i believe the directory structure is different, so basically its probably calling a file that is not where it should be. So you need to figure out whats calling that dll, find the dll and put it into the folder it needs to be in, make sense?


or you could just install xp on your laptop like everyone else in america, lol. :1

Re: obdo shit
 

Ya I got a cheap laptop ,I got the dll to work thanks. lol It will not run xp it doesn’t have the memory.

Re: obdo shit
 

you talking about 3.1.7? I downloaded it, but havent tried to run it. The last time i used turboEdit,i was helping to test 3.1.4 (?) so, maybe things have changed where the ecuControl plug-in is now built in. There was a button to launch the ecuControl lugin-in, as well as RTP, but it was still a plugin you had to install.

Re: obdo shit
 

Ok gave ecu control a shot not go with the log works and ecu plugins I also tried the stand alone ecu control. I tried freelog again with no luck.

I think it may have something to do with this.
Attachment 15500
I am using ng60 but you go to the address and
Attachment 15501
Thy are all for a pm6 the ng60,ng55 and ng61 I can not change it to a pr4 in less I use the stock bin from xenocron. But then I get no features.

Could this be why I am having such a problem dataloging? I do Have a pm6 I can chip should I try that?

Re: obdo shit
 

ok where did you get that version of turbo edit? I have never seen it before and if i remember correctly 3.0 is obd1 compatible but i didn't think anyone was really using it and your going to have alot more problems because theres probably alot of untested ---- in there.

i already told you where to get the last stable version from Xenocron and i just did a fresh install on my machine and verified that everything still works correctly, william told me that the guy that wrote ECU control used slightly different math and that ---- would be a little off and since he already wrote his own datalogger he didn;t bother correcting any of that ----. you would benefit from reading the recent posts on pgmfi.org because most all the issues have been fixed, bad thing is the "datalogger issues" thread is now at 22 pages.

Edit:

Ok i just downloaded TE3.1.7 and found what your looking at, well I got an error saying you have to install "Map selection" and stock 1.8 bar settingss will be used until then, guess this is anouther plug in, I'll dick with this tommorrow, have you read through the latest pgmfi stuff? you should IM the guy developing this plug in.

Re: obdo shit
 

Ya I have dug threw pgmfi and found several post but everyone is using a pm6. So not a lot of it applies to me. So you say the old version 2.5.5 of turbo edit with the built in dataloger has no problems? I forgot to try it. I will give it another shot.

If all else fails I think I will go with this and go external dataloging. http://www.innovatemotorsports.com/products/ssi_4.php should work well with my lc-1.

Re: obdo shit
 

you were trying to use the newer ecucontrol plugin with an older version of TE. ecucontrol now looks to TE to see which map sensor your bin uses so that the correct formulas are used. if it cant find the variable for the map sensor (ie using an older version of TE), then the stock 1.8 bar formulas will be used...the program will still work though.

using pm6 code in a pr4 will still work. i use a pr4 and have no problems. make sure you are using the ng code, not a stock rom, because the stock rom has no datalogging code in it. start with an ng60 or ng61 rom (the bnt file included are the most up to date), copy your maps/settings over and use that bin. make sure your com ports are setup correctly.

if you can get the old standalone version of ecucontrol to work (even if the data is incorrect) then every datalogging app should work...ecucontrol, ecucontrol plugin, bre, freelog, etc...

i use a pr4 with the pm6 based ng development rom in my car and i can log with any number of datalogging apps...ive tried it on 3 different laptops and never had an issue. i also use the old gotspeed 232 board with a serial to usb convertor...with no problems.

Re: obdo shit
 

I am using hulog. I have tested it in an obd1 car with no problems. I am using ng60 not a stock bin. I can get rtp to work, everything works on turbo edit for me just not dataloging. I can not get the old standalone ecu control to work. I have the com ports seat right. I will try the old te and switching to ng61 and ng55 and see what happens.

Did I forget to cut some thing is their a j12 for obdo???????????????????????????????

Thanks for all your help everyone. + I got the porn form now ++++++++++++++++++++++++++++++++++++ 50 post.




UPDATE
Ok I may have not had a ng60 bin I do not know what I had I coped a close bin to my engine of exnocron it looked a bit odd but worked fine.

Re: obdo shit
 

Makes sense, i am using stock map sensor settings.