I've got various ng55 and ng60 basemaps, but they are all kicking a code13 when loaded. I've used xenocrons pm7 base and it works, but it's not boost capable.

It's been years since I've messed with Turboedit, but this customer won't go any other route. I'm trying to get back up to date with TE, but the car is here, and I just need a basecode to tune on or a solution to the issue.

Worst case I'll have to chip a PR4 I have here I suppose, but I'd like to avoid that.

Thanks.

 

i posted a response to your thread on pgmfi...

when it comes to obd0, HT is just as slow as pgmfi... plus i visited there before i looked here.

 

lol...yeah, I figured I'd give it a shot though.

I have a stack of ecu's, so the easier solution will be just to chip a PR4 I have. I don't really have time to attempt to create a plugin or work with code to attempt to remove the baro sensor.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by RC000E &raquo;</TD></TR><TR><TD CLASS="quote">lol...yeah, I figured I'd give it a shot though.

I have a stack of ecu's, so the easier solution will be just to chip a PR4 I have. I don't really have time to attempt to create a plugin or work with code to attempt to remove the baro sensor. </TD></TR></TABLE>

its just a table in TE that enables or disables the CEL for any sensor. the coding is already done in the ROM and in TE....

not sure if it will work or not (thats a feature that needs testing), but trying it is easier than chipping another ecu.

otherwise, the PR4 would probably be the best bet...

 

Yeah, I couldn't find that feature. I searched in properties and options...didn't see it. I downloaded the latest version via the link on xenocrons site.

 

Just did some searching...I didn't see all the development you did in the other forum. I downloaded the recent version you have and am trying **** now. I'll hit you with a donation if I can get this car outa here....lol

Don't wanna speak too soon, but it appears to have worked. This car is a wiring nightmare though, so I'm working on some FAILED dpfi to mpfi injector wiring. Appears the 13 is gone though. Lemme get this **** finished...I'll paypal you some dinner.


Modified by RC000E at 4:31 PM 10/18/2008

 

Well, the dpfi to mpfi wiring had the resistor box grounded, so I supplied 12v, pinned everything out...it's fine. I disabled the code 13, and the light went away, but on startup I was getting code 16. I investigated fuel issues and there are none. I installed a PR4 and the car runs fine, codeless.

So, I'm at a stop again. Is something buggy happening in TE making it kick a false code, or is my chip burning happening wrong. I'm burning SST chips with an 8000 hex offset like I do for OBD1...is that an issue?

Any help?

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by RC000E &raquo;</TD></TR><TR><TD CLASS="quote">Well, the dpfi to mpfi wiring had the resistor box grounded, so I supplied 12v, pinned everything out...it's fine. I disabled the code 13, and the light went away, but on startup I was getting code 16. I investigated fuel issues and there are none. I installed a PR4 and the car runs fine, codeless.

So, I'm at a stop again. Is something buggy happening in TE making it kick a false code, or is my chip burning happening wrong. I'm burning SST chips with an 8000 hex offset like I do for OBD1...is that an issue?

Any help?</TD></TR></TABLE>

im assuming you are using ng55, 60 or 61 code as a base because they all should have the coding for the cel disable...

so with the PM7:
when you disabled the code 13 (baro) in TE, it went away...but now you get a code 16 (FI). im not sure why that would come up....im assuming that it is a false code because usually code 16 = runs horrible. plus if it runs fine with the PR4 then i guess that answers that question.

i would say to disable the code 16 also and see if you get another false code or not. but im sure you dont want to disable a bunch of codes on a customers car....

as far as the offset, yes 8000h is correct for obd0 also. i used to use the sst512 chips and that always worked for me.

if you want to post your bin with the code 13 disabled, i can look to make sure that its not doing something else weird. (PM me if you want to email it to me)

sorry your not having luck...

 

ok i did some quick searching...

the ng code is looking for the baro and the inj test circuit...which the pm7 wont have. so you have to disable these codes.

http://forum.pgmfi.org/viewtop...42602
http://forum.pgmfi.org/viewtop...+code

here is a bin with the baro, inj and ELD disabled... from what i've read, the ELD may or may not have to be disabled. so you can turn it back on if you want. fuel and ignition maps are mine, so they will be bogus for you. and check the rom options because teh boost cut is still turned on.

http://www.geocities.com/joeyp...1.bin

hopefully that helps

 

Damn it, I forgot all about that injector test circuit. I'm so used to shuffling through the options on Crome I don't think about them much. Yeah, that's sounds like the issue though.

During this time though, the turbo showed itself to be a p.o.s., so the cust is buying another. It gave me a break to deal with a couple others and get them done. So, probably mid week I'll have to finish sorting this one out.

I'll use the info and stuff you provided....lemme see how this goes here.

 

We are still waiting for our refunds, Damian.

http://www.sr20-forum.com/turb....html

 

I'm working on the three refunds, this isn't the place for this.

 

I'm done being patient...... I think we have all given you way more patience than anyone else would...

 

that's certainly disputable

 

any updates...on the TE stuff?