question on custom os 0202005

[AllOutPerformance]

i converted a 2000 pickup to a 2156 os and it runs fine.I load the 0202005 for nitrous control and the truck starts and dies and wont run.
Ive done many custom os with great results.What am i missing.I full flashed the 2156 os then full flash the custom os then cal flash the 2156 in and the pull back out save as and re cal flash and it wont run.

[joecar]

Did it run properly on 12212156...?

When you cal only flashed from 12212156 was it the right 12212156 file...?

Did you disable A0003...?

Did you fix the out of range cells...?

Will it start but not run...?

Post file.

[AllOutPerformance]

Hey can you call me bud.559 999 2265

[AllOutPerformance]

Ok.
truck is a 2000
so i converted it to a 2156 os.Full flash fires rigt up.
next i full flash a 0202005 custom os
cal flash my stock 2156 file
read file
save as and reflas as a cal only.
truck starts and dies
yes i disabled 03

[joecar]

Nate, calling you in 3 minutes...

Edit: your voice mailbox is full, can't take messages...

[joecar]

Nate,

Look at B3647, it needs to be filled with good values.

Edit: he called me back, this is what we concluded.

[AllOutPerformance]

Ok new problem
When converting from the 2000 O.S system 09354896 to 2156 01 and up O.S and ten adding the 02020005 custom os i have no timing retard when grounding red pin 56.Is it the early ecu that doesnt have the capacity to do this.Ive gone threw all tables with Joecar and we are at a loss.My next question is i have a 411 ecu i can toss in right now but do i have to eat a lic fee as i ave already lic the ecu that was in the truck.Thanks guys.

[joecar]

Nate, I pm'd Tech Support.


Make sure that you have it wired to pin 56 of connector J2 (it may not necessarily be red);

what year/model/vehicle is the original PCM...?

[Taz]

LS1-B PCM service numbers 09354896 and 12200411 are generally interchangeable - at least with OEM tunes. I believe that connector C2 (red) or C2 (green) pin 56 was never used in Gen III OEM tunes. Not sure about COS requirements - but if OS 12212156 was functional in that PCM - then logically the COS based on that OS should also function.

Don't want to see you use up a tuning licence unnecessarily. Sorry - I don't have an exact answer on this one.


Regards,
Taz

[AllOutPerformance]

2000 Chevy pickup.and yes its red pin 56 triple checked it and even cut wire and put manually to the battery still no retard function

[AllOutPerformance]

See I was under the same impression as you.the OS dictates what the pins do.but maybe the 2000 ecu non411 doesn't have the capability to do this.

[Taz]

Did you add that wire ? C2 pin 56 should not have a pin / wire - just a cavity plug.


Regards,
Taz

[AllOutPerformance]

Yes i added a pin and a wire to red pin 56.

[Taz]

OK ... was just checking. Is there continuity in that circuit - when measured with a volt meter - from the "pin" (PCM side) to the "cut" end of the wire you are trying to ground ?


Regards,
Taz

[AllOutPerformance]

The circuit checks out good.

[Tordne]

As far as I am aware the 1999 through 2004 LS1 PCM (512KB) is the same which is why people are able to pretty much swap in any OS that was intended for the PCM type.

[AllOutPerformance]

Well so far the custom OS on this one isn't working

[joecar]

Can you somehow backprobe that pin, make sure it goes to zero volts when the switch is tripped.

[joecar]

Sanity check:
- A0011 set to N2O Monitor,
- A0016 contains non-zero values.

[AllOutPerformance]

yes joe we went over those already remember lol.

[AllOutPerformance]

A0016 is set at 6 degrees
and monitor is on.
Yes i have back probed the pin and completley checked the circuit.
Went away from the switc even and went straight to battery ground after verifing the circuit was correct.

[AllOutPerformance]

10780

[AllOutPerformance]

Here is the tune.
Ive chhecked it 2 dozen times but maybe im missing something.

[AllOutPerformance]

Theres a few things i still need to change in just the base part of the tune.As i avent even made any pulls yet cause i havent gotten the nitrous control to work.
Gotta make some changes in the pe settings still and a few other tables.

[joecar]

It may not be working because the tunetool claims these are out of range:


Out of Range calibration summary: 10:28:27 pm, Tuesday May 10, 2011

EFILive Custom Calibrations
{A0001} Forced Octane Scaler Percentage, was out of range when loaded.
{A0002} Octane Scaler Limiter, was out of range when loaded.
{A0004} MAP Disable TPS VE Table, was out of range when loaded.
{A0005} RPM Disable TPS VE Table, was out of range when loaded.
{A0006} TPS Disable TPS VE Table, was out of range when loaded.
{A0011} PCM Input #1 Function, was out of range when loaded.
{A0017} N20 Monitor VE Multiplier Table RPM Enable, was out of range when loaded.
{A0018} N20 Monitor VE Multiplier Table MAP Enable, was out of range when loaded.
{A0007} TPS VE Table, contained one or more out of range values when loaded.
{A0009} Boost VE Table, contained one or more out of range values when loaded.
{A0015} N20 Monitor VE Multiplier, contained one or more out of range values when loaded.
{A0010} Boost Timing Table, contained one or more out of range values when loaded.
( and A0012/A0013 are OOR )

Give me a minute, I'll set those to in range values...

[Tordne]

I saw the same and was just setting up a test VM to load the latest GA software (I'm running pre-release and saw the same thing). Are you running the 7.5.6 Build 157 version Joe?

[AllOutPerformance]

Ok that doesn't show up when I bring up the tune.im version 157

[AllOutPerformance]

And how is it all out of range I didn't change any of that from the custom settings it comes with.

[Tordne]

You absolutely MUST manually change those setting as required. The COS doesn't come with any default settings. In fact the areas in memory that those custom tables occupy will contain whatever data was in the memory area of the cal-flash calibration that you flashed.

This is very significant and I think we may have found the issue :). As the COS have been out for about 5 years now and no other reported issues I'm pretty confidant that this might just be the root cause right here.

[joecar]

I fixed the OOR values (there's a trick to doing this, see the History tab)...

try the attached file (when you open it, there should be no OOR values).

[AllOutPerformance]

Ok call me stupid but it looks just like what i already had.
And ive used this os already in camaros with zero issues.WORKED PERFECTLY thats why i like to use it.Hmm

[ScarabEpic22]

Its out of range because EFILive doesnt populate those areas of memory. If GM didnt (no need in factory OSs) and EFILive doesnt do it for you, you MUST do it manually. LB7/LLY DSPx are the same way, have to script sane values into all the new tables because they can have random or no values.

Ive gone through and added sane values to all the COS tables. It is not using the TPS or Boost VE tables, just the N2O Monitor. N2O VE multiplier has been set to 1 so no VE corrections will be made.

Its not the COS, it could be the Camaros dont have anything in those memory areas so you're ok not adjusting the values. This truck OS might and is causing your problems. ALWAYS fill in COS tables with sane values otherwise the motor could go boom down the road if one of the tables becomes activated.

Dang, Joe and Andrew beat me to it. Again. :D

[AllOutPerformance]

Ok thats fine and dandy but all the values look exactally the same when i open up the custom portion of the tune.And THANKS for all the help thus far guys.
Im just not seeing (when i open the file) the changes.I see stuff in the history but in the file it self it looks exactally the same as before.Now i just feel like a moron

[AllOutPerformance]

Scarab thanks for the changes,i actually was going to do the 50% on the hi low blending.I just hadnt had that chance cause i was trying to just make it work first lol.Tanks though.I still dont understand how all the A0000 threw A0018 were out of range when its the exact same things that were already there.Not to mention i had changed some of the items that were out of range to what there set to now.

[TFZ_Z06]

Here is a photo in case anyone finds it useful:
High Resolution Photo Red Pin 56: (http://home.comcast.net/%7Ebooth.p/redpin56.jpg)

[joecar]

I saw the same and was just setting up a test VM to load the latest GA software (I'm running pre-release and saw the same thing). Are you running the 7.5.6 Build 157 version Joe?Yes, I'm 157.

[AllOutPerformance]

Ok looking at all the parameter files to me those didnt change.But do you have to set them to something different first then fill them back in.If so i understand that.
I do see that the tpsve and boostve stuff changed and a few other things.

[joecar]

And how is it all out of range I didn't change any of that from the custom settings it comes with.The COS defines some areas of flash memory that were previously not used and contain junk values (whatever GM left there in the PCM).

Just like Andrew and Erik said above.

[AllOutPerformance]

I understand that Joe but where do i view this to make the changes.

as you said in your email you changed a0001 from 1600 to 99
In mine it was set to 100.And all i saw was 100.Im sorry im just not understanding.Where am i not looking to see what everyone else is seeing.

[joecar]

Ok thats fine and dandy but all the values look exactally the same when i open up the custom portion of the tune.And THANKS for all the help thus far guys.
Im just not seeing (when i open the file) the changes.I see stuff in the history but in the file it self it looks exactally the same as before.Now i just feel like a moronLook at these threads:


Fixing Out Of Range Cells:
showpost.php?p=87052 (http://forum.efilive.com/showpost.php?p=87052&postcount=14) post #14
showthread.php?14119-3000-RPM-max-and-setting-codes-03-Z06-with-Magnuson-at-150kPa (http://forum.efilive.com/showthread.php?14119-3000-RPM-max-and-setting-codes-03-Z06-with-Magnuson-at-150kPa) posts #14, #17
showthread.php?14654-I-need-help-getting-the-most-out-of-my-car (http://forum.efilive.com/showthread.php?14654-I-need-help-getting-the-most-out-of-my-car) post#2

[joecar]

I understand that Joe but where do i view this to make the changes.

as you said in your email you changed a0001 from 1600 to 99
In mine it was set to 100.And all i saw was 100.Im sorry im just not understanding.Where am i not looking to see what everyone else is seeing.Yes, I saw it being 100 (what the tunetool displayed, the real value was 1600); so I changed it to 99 (less than max display value); I changed all of the OOR's; saved file; exited tunetool;

then, if you really wanted 100, reopen file, change 99 to 100 (now, 100 is really 100 and not 1600); change all the ones you changed; save file.

Tricky. :doh2:

[AllOutPerformance]

Ok i awnsered my own question lol in a eralier post.So you have to change it regaurdless if the values are the correct values that your going to use.Thanks for the help.Atleast i dont feel like a complete idiot now lol.

[AllOutPerformance]

Silly.but now i know.Thanks again for the input.Now i can get it finished up.

[joecar]

Ok i awnsered my own question lol in a eralier post.So you have to change it regaurdless if the values are the correct values that your going to use.Thanks for the help.Atleast i dont feel like a complete idiot now lol.Yes, if it has blue dogear corners, it is OOR, you have to change it, save file, exit tunetool.

[joecar]

Let us know if it pulls timing on switch trigger.

[AllOutPerformance]

Ill let ya know tomorrow Joe.Thanks again for all the help sorry for the noob questions.

[joecar]

No worries... OOR's are tricky.

[joecar]

Here is a photo in case anyone finds it useful:
High Resolution Photo Red Pin 56: (http://home.comcast.net/%7Ebooth.p/redpin56.jpg)Hi TFZ,

Thanks for the pic :cheers:

Note that the file in your sig has some OOR's:


EFILive Custom Calibrations
{A0000} Forced Octane Scaler, was out of range when loaded.
{A0001} Forced Octane Scaler Percentage, was out of range when loaded.
{A0002} Octane Scaler Limiter, was out of range when loaded.
{A0017} N20 Monitor VE Multiplier Table RPM Enable, was out of range when loaded.
{A0018} N20 Monitor VE Multiplier Table MAP Enable, was out of range when loaded.
and also A0012, A0013 (set these last two to 511 since 512 appears to be OOR).

[joecar]

...

Dang, Joe and Andrew beat me to it. Again. :DYeah, we have armies of robot slaves who transcribe dictation into thread/post replies... :cucumber:

[joecar]

I wish... :doh2:

[joecar]

red = values left there by GM in PCM (undefined areas)
blue = intermediate values (not max or min)
green = final values (if you want max or min value)



May 10, 2011 22:34:36
EFILive Custom Calibrations
{A0001} Forced Octane Scaler Percentage, changed from "1600" to "99".
{A0002} Octane Scaler Limiter, changed from "1600" to "99".
{A0004} MAP Disable TPS VE Table, changed from "1280" to "104".
{A0005} RPM Disable TPS VE Table, changed from "12800" to "7999".
{A0006} TPS Disable TPS VE Table, changed from "1280.0" to "100.0".
{A0007} TPS VE Table, modified. {A0009} Boost VE Table, modified.
{A0010} Boost Timing Table, modified.
{A0011} PCM Input #1 Function, changed from "255" to "Not Used".
{A0012} Valet Mode Speed Limit with ETC, changed from "512" to "511".
{A0013} Valet Mode Speed Limit non ETC, changed from "512" to "511".
{A0015} N20 Monitor VE Multiplier, modified.
{A0017} N20 Monitor VE Multiplier Table RPM Enable, changed from "12800" to "7999".
{A0018} N20 Monitor VE Multiplier Table MAP Enable, changed from "1280" to "104".

__________________________________________________ ______________________________

May 10, 2011 22:37:51
EFILive Custom Calibrations
{A0001} Forced Octane Scaler Percentage, changed from "99" to "100".
{A0002} Octane Scaler Limiter, changed from "99" to "100".
{A0004} MAP Disable TPS VE Table, changed from "104" to "105".
{A0005} RPM Disable TPS VE Table, changed from "7999" to "8000".
{A0006} TPS Disable TPS VE Table, changed from "100.0" to "101.0".
{A0007} TPS VE Table, modified. {A0009} Boost VE Table, modified.
{A0010} Boost Timing Table, modified.
{A0011} PCM Input #1 Function, changed from "Not Used" to "N2O Monitor".
{A0015} N20 Monitor VE Multiplier, modified.
{A0017} N20 Monitor VE Multiplier Table RPM Enable, changed from "7999" to "8000".
{A0018} N20 Monitor VE Multiplier Table MAP Enable, changed from "104" to "105".


The red values are pretty wild, but the tunetool displays them using the max display value (with blue dogear corners on the cells).

You have to set intermediate values, save file and exit tunetool (important).

Then if you want to set final values, open tunetool/file, set values, save file.

[TFZ_Z06]

Hi TFZ,

Thanks for the pic :cheers:

Note that the file in your sig has some OOR's:
and also A0012, A0013 (set these last two to 511 since 512 appears to be OOR).

Roger that!! I'm tuning TOMMORROW on COS5. Check out the file when you get a chance and see if it makes sense.

[GMPX]

There's a bit of a trick with the NOS timing retard, it will only function when table B5956 has a multiplier value of 1.00, typically at idle / part throttle this can be calibrated to 0.0 from factory. I had completely forgotten about that, it was 6 years ago we did that OS :shock:

[ScarabEpic22]

So then it might be a good idea to set B5956 to 1.00 in all of the normal operating temp cells? Like the 176-194F rows, set all those cells to 1.00 so when the car is warm and you hit the switch it will properly pull timing regardless of what the RPM is?

Am I understanding this correctly?

[joecar]

This is B5956 from a stock 2001/2002 F-car file (...I haven't looked at 1998, 1999/2000...):

[AllOutPerformance]

Works perfect Joe.thanks.now I know what to look for in the future.

[joecar]

Ok, cool :cheers:

this OOR business has jogged my memory, I updated the COS5.txt notes in the COS5 thread.

And thanks for posting back :cheers:

[GAMEOVER]

There's a bit of a trick with the NOS timing retard, it will only function when table B5956 has a multiplier value of 1.00, typically at idle / part throttle this can be calibrated to 0.0 from factory. I had completely forgotten about that, it was 6 years ago we did that OS :shock:

So do we set all the normal operating temp cells to 1.00 like Eric asked....

Post #54 above...

[joecar]

So do we set all the normal operating temp cells to 1.00 like Eric asked....

Post #54 above...Yes.

[GAMEOVER]

Thanks Joe....I got another question(nothing to do with nitrous) if I want COS5 to pull timing or act like a stock High Octane & Low Octane tables(in case of bad petro) do I set A0001 to 50% and A0002 to 50%? Or?

[GMPX]

On the stock F-body spark multiplier map you can see it will work fine above 1,600 RPM, there is no need to set the entire map to 1.0, you only need to do this in an area you want the timing pulled and if the cell is currently 0.
I suppose most people will just test it at idle, which of course won't work on that map.

[joecar]

Thanks Joe....I got another question(nothing to do with nitrous) if I want COS5 to pull timing or act like a stock High Octane & Low Octane tables(in case of bad petro) do I set A0001 to 50% and A0002 to 50%? Or?The COS slides between HO and LO tables just like a stock OS (even when MAF is failed)... set A0000 to Disable and A0002 to 100%.

[AllOutPerformance]

I thought you had to set it at 50% so it will blend between hi and low.
Joe quik question.I'm doing a c6z06 ls7 in a gto and has long tubes.having a hard time getting o2s hot at idle.I changed the switch rate.can I tell the heaters to be on all the time.I think I read somewhere someone did this and it worked good.I've turned on the heaters all the time and it really helped the o2 from making such big swings while switching.

[5.7ute]

I thought you had to set it at 50% so it will blend between hi and low.
Joe quik question.I'm doing a c6z06 ls7 in a gto and has long tubes.having a hard time getting o2s hot at idle.I changed the switch rate.can I tell the heaters to be on all the time.I think I read somewhere someone did this and it worked good.I've turned on the heaters all the time and it really helped the o2 from making such big swings while switching.

A0002 set to 100% will force the pcm to use the high octane table as the default until knock is detected. If knock is present it will still learn down (watch the ASPARK pid).
Setting to 50% will have a blended value between the HIGH/LOW table as the default. Not sure if it will learn up as I always set to 100%

[GAMEOVER]

Thanks Joecar, Ross & 5.7ute...I just realized that I've been doing the COS5 wrong for the past 6 months or so... I'm glad I followed this thread...:D