More info, see TAQ's posts: showthread.php?t=7653
Printable View
More info, see TAQ's posts: showthread.php?t=7653
Related material: showthread.php?t=2270
Check to see if you have these files:
02020005:
C:\Program Files\EFILive\V7.5\Calibrations\LS1B\Custom\020200 05.cal
My Documents\EFILive\V7.5\Bins\Custom OS\02020005.tun
01290005:
C:\Program Files\EFILive\V7.5\Calibrations\LS1B\Custom\012900 05.cal
My Documents\EFILive\V7.5\Bins\Custom OS\01290005.tun
If you have a later build of EFILive software, you should already have those files;
If you don't have them, then get them from here: showpost.php?p=50208&postcount=218
Note that the two .tun files above are "empty" (they contain no calibration data);
you have to full flash the COS5 .tun file, and then cal only flash from your running
12212156 (for 02020005) or 12225074 (for 01290005) file;
then read back the tune, fix the out-of-range cells, and save as a new file...
this is now your first working file (i.e. from now on, edit and flash from this or its children).
If you're starting from OS's other than 12212156 or 12225074, then follow these steps first:
If your 1999 F-body .tun file is stock, www.holdencrazy.com has a 1999 F-body->12212156 migration tune file;
If your 2001 F-body .tun file is stock, then no need to copy tables, just go straight to 12212156 (see full flash below);
Otherwise, you must copy each table from old file to new file (use copy-with-labels and paste-with-labels);
Then full flash in the new 12212156/12225074 file, make sure the vehicle runs correctly before flashing in COS5.
COS5 summary notes are attached.
You will have to read the rather long COS5 thread if you want to get the full benefits of COS5.
Thanks.
:cheers:
The latest July 11 download www.efilive.com/downloads includes the COS5 files.
The necessary files are already included in the later builds of the software...
There is no need to copy them from any links in this thread.
Hey guys I have a car with a 12593358. Can I use the OS5 with this or am I screwed.
I want to mainly use it for the Nitrous Part.
Thanks for all help.
Evil, welcome...:cheers:
You will have to copy all your tables from 12593358 to 12212156:
- read post #243 above...
- open 2 instances of tunetool: one on 12593358, other on 12212156;
- for each table do copy-with-labels from 12593358 and paste-with-labels to 12212156;
- do full-flash of this copied 12212156;
- make sure your Z28 runs at least as good as it did before;
- do full-flash of 02020005 (COS5);
- do cal-only-flash of your copied/running 12212156;
- read the flash and save to new tune file;
- in the new tune file, fix all out-of-range cells;
- do cal-only-flash of the the edited new tune file;
- read and apply the attached doc in post #243.
Evil,
Oh... from your sig I assumed you had a Z28 (cable linkage throttle)...
I don't know how drive by wire works with COS5...
We need someone else's input on this...
Sorry...:)
Just upgraded to COS#5 and used TPS VE Table,What a difference in throttle response:grin: Didn't go for a test ride yet...............Paul
so...goin to change to either cos3 or cos5...earlier in this thread sounded like Fbody cable driven tbody were the only cars that could accept cos5....now 1 of the 2 OS that accept it is the 12212156 OS....which came stock in a 02 vette manual and auto...i have a 02Z06 with the xxx588 OS....wont have any problems copying tables from my Z OS to this 2156OS then to a COS5 flash in my cars computer via OS flash then a cal flash only with my data in the 2156 OS?
I believe the 2002 M6 Corvette 12212156 file is ETC, you should be ok.
Be sure to read post #243 above: showpost.php?p=67875&postcount=243
One of the issues we are faced with is we had planned on rewriting (and maybe simplifying) the custom OS's for the GenIII PCM's from 98 - 08.
There is a number of technical issues with the later PCM's, the first and major problem is there is no room left in the calibrations area of the PCM, so we would need to move any additional tables we add out to another section of the PCM's flash memory, this unfortunately means a full reflash anytime you wanted to make a change.
That means a much higher risk of a doorstop PCM and a reflash time of about 3mins, not 30 seconds per change.
I think I have come up with a system that can work, but we don't want to try to implement it in the Version 7 software as it will require a lot of changes to the core of the program, something we don't want to do when it is going to be phased out this year.
Cheers,
Ross
Bill,
The current V7.5.x software works with V1 (which already does BBL from the V7.5.x software);
The current V8.x software is for doing BBL with V2 (currently beta testing)...
In the future the V8.x software will eventually include everything (scantool, tunetool, BBL, BBF) and will replace V7.x software for V2.
V7.x software will continue to support V1.
i.e. you can run the latest V7.5 software on your V1... you don't really need V2 unless you're flashing an ECM that is not supported by V1...
when the eventual all-inclusive V8 software comes along, you will be able to run that on your V1.
Correction: see post #265 below (V7 will always be available).
Too bad about your job, hope you can find work somewhere.
Cheers
Joe
:^)
Does that mean the 98 OS 19980200 will work with that? Is that a miss print. I hope not. Anyway, is that the case that V8 will replace 7.XXX and work with the V1. I do not have the V2. I really like the computer and am looking at the newest small windows based PC's with 9 and 10 inch screens (they are down to around $300.00) to build into my dash were the stereo is and be able to use EFILive and the iPod setup too with a pad and keyboard were the compartment in between the seats are. With V1 this winter along with the 98 to 02 PCM conversion. Nothing fancy though as it seems really straight forward but very time consuming.
Please let me know as winter grows near as does the snow (a little over 2 1/2 months).
98 tigershark
Are you asking if the V8 software will work with a V1? It will completely replace the V7.5 Tuning and Scan programs. For your future carputer and iPod integration setup, honestly you will not need a V2 as your V1 can BBL a little and the rest can be done in passthru mode straight into the V8 scan program.
Ive heard the 98-02 PCM swap takes a weekend to do especially copying all the tables over in EFILive but is so worth it.
TS,
Correction:
V1 will not be supported by software V8.
V1 will continue to be supported by V7 software (see post #265 below).
19980200 will continue to be supported by both V1 and V2.
You will still be able to use your V1 to flash your 1998, and to convert it to a 2002 or COS as you said...
V2 is required only if you have a vehicle with a newer PCM (e.g. E38, E40, E67).
Thanks Guys,
That answered my question very well. I am looking into the small computer setup so that is great news and I hope that i will be able to do that money wise. I think that would be cool to have EFILive right there all the time in your dash board so thanks as we get allot of snow where I live and winters are long so I will soon have allot of time to plan it out. Did I ever tell you guys we used to walk 6 miles to school up hill both ways with only tennis shoes and no socks (we did have clothes of course) in 6 feet of snow? My youngest kids are all back in school now, today was the youngest ones first day as a senior in high school. I have been a member of this forum since 2006 and LS1 edit since 2004. Where does the time go?
98 tigershark
FlashScan V1 will continue to be supported by software V7 (which will continue to be available indefinitely).Quote:
Originally Posted by Blacky via PM
FlashScan V2 will in future be supported by software V8.
So if you have FlashScan V1, you will still be able to do BBL and to flash in a different OS or COS.
:)
V1 cartainly can do BBL (i.e. it can log without a laptop connected)... :)
Follow these steps:
- using PC/laptop program the pids you want to log,
- remove V1 from PC/laptop and take V1 to car,
- log from car (while PC/laptop stays home),
- remove V1 from car and take it to your PC/laptop,
- upload the saved log(s) and view in scantool.
From the V7 scantool see these menu commands:
FlashScan->Program Selected PIDs Into FlashScan
FlashScan->Read Logged Data From FlashScan
In those 2 commands, "FlashScan" refers to FlashScan V1.
V1 BBL:
- single pid list (you program this in while connected to laptop).
- 23 minutes worth of log (in Fast 10 mode).
V2 BBL:
- multiple pid lists (you select which pid list you want to log).
- number/length of logs limited only by SD card size.
- able to read OBD-II diagnostics information (DTCs, modes 2,3,4,5,6,7,9).
Still no NOS stuff for the 1mb PCM guys? eg 04140005
Jez
Old thread I know but...
You can build a small device with a relay that goes in line with your IAT sensor. It's NC contacts pass the normal IAT signal through to the PCM but when on, it replaces the IAT with a fixed value resistor (or resistors). You can use this to force the IAT sensor to some fixed value that is very low when nitrous is active. In turn, goto the IAT-VE spark modifier table and subtract timing in the corresponding temp and WOT area. There is an IAT PE modifier that works in that OS as well, so you have some rudimentary WOT fuel control with this as well. It's not as powerful or flexible, but it works. I have a few cars that spray between 250 and 325 (DP) that use these.
Or wire a simple relay/switch to the IAT sensor, leave it on when not using N2O and when you ground the relay have it ground the IAT sensor so the PCM/ECM sees the default value for the IAT tables. Pull spark based on the IAT table.
It would be nice to have the correct tables, but at least you dont have to buy an external box or anything to reduce timing!
In that case you don't even need to ground the input, just use the NC contacts to open the IAT circuit when active and it will default to min value. The reason I use a resistor rather than this method is that the car goes into OL if the value falls that far and some folks want it active with the system just armed. If the car been sitting in the lanes and the IAT is heatsoaked, your part throttle could be lean without closed loop for the duration of burnout and just after.
Just some thoughts...
Very good point, Ive never actually done it before just relaying information others have posted up online saying it works.
Interesting, it could drop into OL? In theory that makes sense, if IATs are that low it means ambient temps are really low and the PCM should dump fuel.
Ah, IAT heatsoak. Tell me about it, its bad on my 02 I6 but the SS is miserable. Watch IATs spike 20F+ sitting at a light, not good for launching.
Off topic [heat soak] I know...
I have a supercharged car right now with his IAT after twin meth nozzles but it's right behind his second hi-speed fan. It's so ridiculous there that I logged 150deg IATs at restart after a 5 minute sit time and have seen IATs of 165 at restart on 90deg days. Slow traffic in 80 deg weather = 120 + degF in no time. It may not be the best approach, but the car now has 2 IATs... One in the nose seeing outside air and the second one is still after the meth nozzles near the throttle body. At 1psi his hobbs switch that turns on the second Walbro now also turns on a relay that switches the IAT in the nose over to the IAT in the intake tract after the methanol nozzles. Hot start and cruise fueling is very stable. In most all cases, some afterstart enrichment work with IAT/ECT adders can cover up the lean spot the false IAT creates until closed loop. I don't yet know what these tables are called in EFILive.
Interesting method Frost.:cheers:
When logging, how long does it take for the logged IAT to change with this method? (It may give us an idea on the iat filtering)
Using the two & switching while logging dynamic air temp. Since this is what the pcm uses for airmass estimation.