VS-VY Enhanced Factory Bins
-
3.8TheeWorld
- Posts: 1
- Joined: Thu Sep 11, 2025 8:27 am
- cars: Ls1 Tonner
v6 Eco Tonner
Vr Buick Wagon
Re: VS-VY Enhanced Factory Bins
Hey guys i have been following these forums for a couple years but have never made a post - Recently got my vy v6 One Tonner burnout car out for its debut comp - pretty happy with how it went. It has Vx-Vy enhanced bin flashed onto it and have been making small changes over the past 6 months or so. Has 82 degree thermostat With lower Thermofans , Pacemaker extractors With straight 2.5 inch Side dumps , old injectors were flogged out so went l67 injectors , Maxed out 1-2 n 2-3 low mode and upped pressures slightly . Holds gears good… And will light up straight to the limiter in first + second … But when its eating limiter in second & i try to put the shifter in third … It won’t shift from 2-3 … until i let of the throttle slightly but then it’s hard to stop it from bogging down but once it’s going it goes … Just does my head in i can’t get it to shift on demand Do youse know if there’s anything i could change to make sure shifts are happening almost instantly ? I need a bloody manual can’t believe i have found myself in an auto lol
Jokes aside it’s still good fun , Maybe it needs a shift kit and i’m happy with how it went for a Debut. Any other tips would be great! (I usually have a lot of mechanical sympathy, but this is the car that’s going to cop it all lol i built it from a rolling shell so i’m keen to throw everything i can at it
)
-
Muncie
- Posts: 249
- Joined: Wed Dec 02, 2020 6:15 am
- cars: Vy commodore, Turbo Ecotec v6
- Location: New Zealand Waikato
Re: VS-VY Enhanced Factory Bins
Ive tried to set this up for a guy before same issue you can get 1st and second but 3rd no dice almost think you'd be better with stock shift tune and just let it shift on it own, mine smacks 3rd in burnout box at drag strip and bloody near goes off clock!.
Look up the diode mod if you want to take over shifting yourself RK Garage has a video from wayback I think showing how it's done. Or put a full manual valvebody shift kit in trans.
Look up the diode mod if you want to take over shifting yourself RK Garage has a video from wayback I think showing how it's done. Or put a full manual valvebody shift kit in trans.
-
lakespeed
- Posts: 2
- Joined: Fri Nov 21, 2025 4:34 am
Re: VS-VY Enhanced Factory Bins
I have done some searching on the forums but couldnt really find anything concrete. Has anyone been able to expand the rpm limits or table resolutions to enable tuning beyond the 6375 rpm limit in the VY's? I have seen the limits being that its 8bit rev limit. Is that a hard limit or has someone been able to expand this?
-
Rhysk94
- Posts: 241
- Joined: Sun Mar 15, 2020 9:25 am
- cars: VE SS-V
VY V6 Turbo “Ecojet”
FG XR6 Turbo
VY V6 Stocker Farm Hack
VY V6 Turbo Competition Drift Car
VY V6 L67 Seat Time Drift Car
N80 Toyota Hilux
VZ SS - Location: Perth
Re: VS-VY Enhanced Factory Bins
6350 is the limit
-
Chr0m3
- Posts: 91
- Joined: Tue Aug 08, 2017 6:25 am
- cars: 2004 V6 VY Series 2
Re: VS-VY Enhanced Factory Bins
I've experimented with expanding it, but you lose control of spark at like 6500, I did an in depth video on this actually.lakespeed wrote: Fri Sep 18, 2026 12:18 am I have done some searching on the forums but couldnt really find anything concrete. Has anyone been able to expand the rpm limits or table resolutions to enable tuning beyond the 6375 rpm limit in the VY's? I have seen the limits being that its 8bit rev limit. Is that a hard limit or has someone been able to expand this?
https://youtu.be/mxoHSRijWds?si=SioCCp9ilKp5ril8
I also wrote a thread on here about it too:
viewtopic.php?t=8607&hilit=Dwell+limits
-
lakespeed
- Posts: 2
- Joined: Fri Nov 21, 2025 4:34 am
Re: VS-VY Enhanced Factory Bins
I watched your vid and read through your post in awe haha, incredible work you have done but sadly it’s way out of my skillset to even attempt to replicate. When you say that you lose control, does that mean whatever you set for those upper table regions are not being used properly in the ecu, or the ecu physically cannot manage spark correctly past 6500, even with a removed limiter and no ecu OS changes? I have been weighing up an aggressive cam for my vy rally car but if it’s going to require an aftermarket ecu to tune the upper regions it might become a bit to expensive to botherChr0m3 wrote: Sat Sep 19, 2026 2:35 am
I've experimented with expanding it, but you lose control of spark at like 6500, I did an in depth video on this actually.
https://youtu.be/mxoHSRijWds?si=SioCCp9ilKp5ril8
I also wrote a thread on here about it too:
viewtopic.php?t=8607&hilit=Dwell+limits
-
vlad01
- Posts: 8600
- Joined: Mon Oct 08, 2012 8:41 am
- cars: VP I S
VP I executive
VP II executive
VP II executive #2 - Location: Kyneton, Vic
Re: VS-VY Enhanced Factory Bins
If the thought of aftermarket comes up, I'd personally just covert it over to either 424 if your car retains the auto with the need for PCM control, or if you are manual or manualised auto, the 808 is the better option.
Given it's a rally car, loosing a few dash features wouldn't be a problem I'd imagine and this way it's all thoughtfully documented, heavily supported on here and importantly a very cheap option. There are even ecotec base tuned been available here for this conversion since the dawn of time practically.
The 424 with 11P has 7600rpm support, and the 808 with 12P goes all the way to 9600rpm. The 424 does have a better ignition control system that with some hackery can do a sort of sparkcut maybe a two step and has dwell control iirc. The 808 can not control an auto though, but was matched with the T5 from factory or the dumb non electronic auto. It takes the hall sensor for speed anyway, so something to keep in mind. Running a VDO signal converter lets you run any combo you like anyway.
Given it's a rally car, loosing a few dash features wouldn't be a problem I'd imagine and this way it's all thoughtfully documented, heavily supported on here and importantly a very cheap option. There are even ecotec base tuned been available here for this conversion since the dawn of time practically.
The 424 with 11P has 7600rpm support, and the 808 with 12P goes all the way to 9600rpm. The 424 does have a better ignition control system that with some hackery can do a sort of sparkcut maybe a two step and has dwell control iirc. The 808 can not control an auto though, but was matched with the T5 from factory or the dumb non electronic auto. It takes the hall sensor for speed anyway, so something to keep in mind. Running a VDO signal converter lets you run any combo you like anyway.
-
KingAustraliaggGG
- Posts: 64
- Joined: Fri Nov 15, 2024 2:19 pm
- cars: 323i 1999 e46 sedan m52tub25 ms43 swapped hx35w.
328ci 1999 e46 coupe m52tub28 ms42.
vy 2002 holden wagon executive l67 bottom end/36 top swap, 102mm throttle body, custom intake box. corn fed boost manifold ex44 external gate, turbo hx40 holset super turbo, 3.7 diff.
vs holden sedan turbo gt3582r, 4.11 diff.
Re: VS-VY Enhanced Factory Bins
Vlad, it's fuel cut then cuts spark, progressive spark cut on 11p is what I would call it.
Would anyone recommend going to 11p on 4l60e vs Ecotec if I got a moates ostrich 2.0 in it. Or just run enhanced vs v6 l36 in it, it's a maf l36 engine. Am going to be purchasing one of muncies onerom emulator kits installed in a vy l36 pcm hopefully in the next few days or weeks.
Would anyone recommend going to 11p on 4l60e vs Ecotec if I got a moates ostrich 2.0 in it. Or just run enhanced vs v6 l36 in it, it's a maf l36 engine. Am going to be purchasing one of muncies onerom emulator kits installed in a vy l36 pcm hopefully in the next few days or weeks.
-
vlad01
- Posts: 8600
- Joined: Mon Oct 08, 2012 8:41 am
- cars: VP I S
VP I executive
VP II executive
VP II executive #2 - Location: Kyneton, Vic
Re: VS-VY Enhanced Factory Bins
Pretty sure iirc, 202 hacked 11P to force a kind of spark cut and demonstrated from what I recall a launch control on a VR using the hacked spark cut. That was long ago and my memory of it might be a bit vague now, I'm sure he could confirm or deny if he sees this post. My understanding is none of the delco units do spark cut out of the factory, but VR onward has much better dwell control at the hardware level which can allow spark cut if setup correctly at the software side. That said, I've never used spark cut on any of my cars, the normal fuel cut it just fine. Spark would be useful in boost as they basically need the extra protection.
Anyway, 11P is just the NVRAM deal, same as the 808 but with the bonus of high speed serial as standard, so ALDL cable plugs in and works out of the box. Gareth has one running his ecotec speedway car, and that revs well over 7k and has been a massively successful race car.
The nice thing about the 424 is they are way cheaper and easier to get as very little people outside of this forum know they are fully tunable just like the 808 and they are far less prone to failures too, so there are heap more floating around with little value attached to them. 424 uses the reluctor VSS, so it's compatible with all the newer auto and manual VSS out there, unlike the 808 which needs a digital VSS signal.
Also, iirc, 11P has more compatibility with the dash ALDL stream if put into a late model car, but as far as I know, no one tested that feature. So it's possible that the 424 could run some of the dash where the 808 wouldn't do much for the dash.
Anyway, 11P is just the NVRAM deal, same as the 808 but with the bonus of high speed serial as standard, so ALDL cable plugs in and works out of the box. Gareth has one running his ecotec speedway car, and that revs well over 7k and has been a massively successful race car.
The nice thing about the 424 is they are way cheaper and easier to get as very little people outside of this forum know they are fully tunable just like the 808 and they are far less prone to failures too, so there are heap more floating around with little value attached to them. 424 uses the reluctor VSS, so it's compatible with all the newer auto and manual VSS out there, unlike the 808 which needs a digital VSS signal.
Also, iirc, 11P has more compatibility with the dash ALDL stream if put into a late model car, but as far as I know, no one tested that feature. So it's possible that the 424 could run some of the dash where the 808 wouldn't do much for the dash.
-
KingAustraliaggGG
- Posts: 64
- Joined: Fri Nov 15, 2024 2:19 pm
- cars: 323i 1999 e46 sedan m52tub25 ms43 swapped hx35w.
328ci 1999 e46 coupe m52tub28 ms42.
vy 2002 holden wagon executive l67 bottom end/36 top swap, 102mm throttle body, custom intake box. corn fed boost manifold ex44 external gate, turbo hx40 holset super turbo, 3.7 diff.
vs holden sedan turbo gt3582r, 4.11 diff.
Re: VS-VY Enhanced Factory Bins
VS L36 Ecotec Turbo: Native L67 $51 Enhanced BIN vs L36 Enhanced vs OSE 11P?
I've got a VS Commodore sedan with the factory 3.8L L36 Ecotec and 4L60E automatic. It's my brother's car, and we're setting it up for a turbo with factory L67 injectors.
The spare PCM supplied with the turbo setup is a Delco 16210672, originally running the BSTK1451 ($51C) calibration.
I've got an XGecu programmer, Moates G6 adapter, Ostrich 2.0 for real time tuning, and an eXTuner wideband that uses the Innovate protocol. I also have the matching ADX for logging through TunerPro.
I'm trying to establish which firmware is actually compatible with my existing PCM and which would be the better foundation for a turbocharged L36.
The two Enhanced BINs I'm comparing
VS L36 $51 Enhanced
BIN: VS_V6_$51_Enhanced_v1.4b.bin
Matching XDF: v1.4g
VS L67 $51 Enhanced
BIN: VS_V6_SC_$51_Enhanced_v1.0a.bin
Matching XDF: v1.0d
Both are 128 KB BINs.
My G6 adapter has a four position rotary selector, and I can program compatible 128 KB chips or prepare a 512 KB chip containing four separate 128 KB images. I'd verify the bank layout and readback before testing anything.
I've also got the Ostrich 2.0 for real time calibration changes.
The car isn't currently being driven, as the battery is removed while it's being relocated to the boot. There's no rush to get it running, so I've got time to research the firmware and hardware properly.
My questions
1. Can the native VS L67 Enhanced BIN run on an N/A 16210672 PCM?
I understand the VS L36 and L67 PCMs share some hardware, including the 16210672 service number, but apparently have different PCB component populations.
My L36 PCM has the U7 IC unpopulated, which I've read relates to the traction control input.
Would the missing U7 IC or other component differences prevent the native L67 Enhanced firmware from operating correctly?
I'm particularly interested in whether the engine management, ALDL communications and factory 4L60E transmission control would function correctly.
Are the relevant PCM pinouts and output drivers effectively interchangeable, or are there specific components required for the L67 operating system?
2. Does the L67 Enhanced firmware offer better extended airflow and ignition timing control?
This is one of the main reasons I'm considering the native L67 operating system instead of simply modifying the L36 Enhanced calibration.
From what I've researched, the VS L36 $51 Enhanced firmware already has extended high and low octane spark tables, along with fuel and injector multiplier tables, reaching approximately 977 mg/cylinder.
However, the native VS L67 Enhanced XDF contains separate high and low octane spark tables labelled for the 850 to 1650 mg/cylinder range.
I've been comparing the two firmware versions and their calibration tables, but I'm trying to establish whether the actual L67 operating code can independently select and interpolate those higher load cells.
Can anyone confirm whether the native VS L67 Enhanced firmware genuinely supports spark table selection through to 1650 mg/cylinder?
Does the L67 operating system provide greater usable load range or resolution compared with L36 Enhanced, or are the additional tables simply arranged differently?
I'd also like to know whether the L36 Enhanced firmware has any cylinder airmass limits that would make its extended tables less useful as airflow increases.
I've noticed differences in the ignition tables when comparing the same RPM and load coordinates between the L67 reference and my current L36 turbo calibration.
I understand that the L36 has a higher compression ratio than the L67, so I'm not assuming the factory L67 timing would be suitable for my turbocharged L36.
What interests me is whether the underlying L67 spark strategy offers more calibration control, rather than the factory timing values themselves.
If the L36 Enhanced firmware already provides equivalent control for my intended airflow, I'd rather continue developing that.
3. Are there other worthwhile differences between the L36 and L67 Enhanced operating systems?
Apart from injector characterization and the factory supercharged ignition calibration, does the L67 firmware offer any genuine advantages for a turbocharged L36?
I'm particularly interested in the actual operating code involving cylinder airmass calculations, high load fueling, injector pulse width calculations, MAF limits, adaptive spark control and knock retard.
I've also read about differences involving EGR, two speed fuel pump control, traction control and transmission related functions.
Are these simply features that can be configured or disabled, or are there hardware dependencies that would cause problems on an N/A PCM?
Would it be better to run the native L67 Enhanced firmware, or retain L36 Enhanced and transfer the relevant L67 injector and calibration data?
4. Would OSE 11P be a better alternative?
I'm also considering whether OSE 11P would offer worthwhile advantages for a turbocharged Ecotec while retaining the factory 4L60E automatic.
I understand that 11P requires compatible '424 PCM hardware rather than simply programming an 11P BIN into my existing 16210672.
Would converting to a compatible '424 PCM and making the necessary wiring changes be worthwhile, or is the existing VS $51 Enhanced firmware sufficiently capable?
I'm mainly interested in the available load range, fueling and spark control, logging capabilities and 4L60E support.
Current engine and turbo setup
The engine is a completely stock VS L36 Ecotec internally, not an L67 conversion.
It's currently fitted with a GT3582R style turbo, external wastegate, large intercooler and 3 inch charge piping.
The MAF is positioned after the intercooler, close to the throttle body.
I'm planning to run factory L67 injectors and initially target approximately 5 to 7 psi, depending on what the stock engine and fuel system can safely support.
I've also got ARP bolts available if they're needed, although I'm not planning a complete engine build at this stage.
I understand the MAF calibration, injector data, fuel pressure, ignition timing and commanded fueling all need to be correct for the actual hardware.
Background
The spare PCM and MEMCAL supplied with the turbo setup were advertised as already tuned.
However, after reading the MEMCAL and comparing it in TunerPro against a stock BSTK1451 calibration I already had, I couldn't identify any tuning changes.
The spare PCM plugged into the car and started despite VATS apparently not being disabled. I understand this doesn't necessarily mean VATS was bypassed, as the vehicle's existing security system may simply have accepted the PCM.
The engine ran with the turbo fitted and revved quickly, but it also warmed up rapidly and spluttered when the boost gauge indicated approximately 5 psi during a stationary rev.
I'm aware that's not something to continue doing on what appears to be an untouched factory calibration.
I've also removed the car's original PCM and still need to read its MEMCAL to confirm the original calibration ID and hardware details.
So it appears I was sold a supposedly tuned turbo PCM that was actually running a stock calibration.
Rather than paying for another tune, I've decided to work through the calibration myself and learn the system properly.
What I've done so far
I've already been working on modified VS L36 Enhanced calibrations for both factory L36 injectors and L67 injectors.
These are based on the L36 Enhanced operating system, with changes involving injector characterization, high load spark, fueling, adaptive spark and airflow related calibrations.
They're still being reviewed and haven't been validated on the vehicle.
I'm trying to determine whether continuing to develop the L36 Enhanced firmware is worthwhile, or whether I should start with the native L67 Enhanced firmware instead.
If the L67 operating system genuinely offers a larger usable cylinder airmass range and independently selectable spark tables extending to 1650 mg/cylinder, that seems like a potential advantage for a turbo setup.
On the other hand, if L36 Enhanced can already handle the airflow and provide sufficient spark and fueling control at my intended boost level, I'd rather avoid changing operating systems unnecessarily.
I don't want to spend weeks developing the L36 calibration only to discover the native L67 firmware would have been a better starting point.
What I'm trying to establish
I'm not asking what AFR to target or how to scale the injectors. I understand that calibration needs to be developed and verified using the wideband, logging and actual fuel pressure measurements.
My main questions are whether the native VS L67 $51 Enhanced firmware can operate correctly on my naturally aspirated 16210672 PCM, and whether its extended airflow and spark table capabilities provide a genuine advantage over L36 Enhanced.
Ideally, I'd like to retain my existing PCM rather than buy an L67 PCM unnecessarily.
Has anyone actually run the native VS L67 $51 Enhanced v1.0a BIN on an N/A 16210672 PCM with U7 unpopulated?
If so, did the engine management, ALDL communications and 4L60E operate correctly? Were any hardware or wiring changes required?
And has anyone confirmed through disassembly, logging or actual testing that the native VS L67 Enhanced firmware can access its full 850 to 1650 mg/cylinder spark tables?
I'm mainly looking for firsthand experience or technical evidence of the firmware differences, rather than general injector tuning advice.
I'm happy to work through the calibration myself once I know which operating system is the better foundation.
attached is where i am at right now with trying to work it out, these havent been tested in car or logged im just doing guesstimates.
for the vs ecotec turbo basetune.
My current VS L36 Enhanced turbo calibration revisions
I've also been developing two separate turbo calibration variants based on the clean VS L36 $51 Enhanced v1.4b BIN, using the matching v1.4g XDF.
VS L36 Enhanced turbo v1.4, factory L36 injectors
This is the stock injector version. Compared with the clean L36 Enhanced BIN, the earlier static audit recorded 1,052 changed bytes, all accounted for by the matching XDF.
Changes include revised main and extended high and low octane ignition timing tables, including the 593 to 977 mg/cylinder load range and higher RPM tables.
Selected airflow limits, positive airflow delta allowances and adaptive spark parameters have been revised using the native L67 calibration as a reference.
Power enrichment has been brought in earlier, with approximately 21.09% TPS required through the main 2400 to 4800 RPM region. Warm PE commanded AFR is approximately 11.30:1, with selected high load open loop cells commanding 13.0:1 or richer.
The positive PE spark advance contribution has been neutralised to avoid adding timing on top of the main ignition tables.
Additional high load temperature corrections have been retained, including IAT retard, with the factory knock detection and ESC functions still active.
The original L36 injector flow scalar, battery compensation and MAF frequency to airflow calibration remain unchanged.
Other changes include the 4.11 differential PPK calibration, VATS disabled, and a temporary 4500 RPM fuel cut with 4200 RPM restart for initial testing.
The factory 4L60E shift and line pressure calibration tables have been retained.
VS L36 Enhanced turbo v1.4C, factory L67 injectors
This version builds on the L36 turbo calibration but changes the injector model for the factory Bosch 0280155868 L67 injectors.
The L67 injector flow scalar, battery voltage compensation, short pulse correction and minimum/default injector pulse width calibrations have been incorporated from the native VS L67 reference.
The injector flow scalar is approximately 213.867 ms/g, corresponding to the native L67 calibration.
The injector-related changes also include the purge pulse width threshold and trip computer fuel consumption constant.
The PE TPS transition has been smoothed between 1800 and 2400 RPM to avoid an abrupt change approaching the main 21.09% threshold.
The low octane spark tables have been compared against the native VS L67 tables using matching RPM and cylinder airmass coordinates. Selected cells exceeding the interpolated L67 reference were reduced, and the shared 593 mg/cylinder table boundaries were corrected.
An additional 15 hot, high load coolant temperature spark correction cells were made more conservative.
An earlier mistake involving the cranking calibration was also corrected after tracing the original HC11 code. Two bytes previously treated as a single 16 bit injector-related scalar were found to be independent startup thresholds and restored to their original L36 values.
VS L36 Enhanced turbo v1.5 REVIEW, factory L67 injectors
This is the latest research revision.
Further disassembly identified the actual cranking fuel scalar, F64SCAL, at BIN offset 0x42B3, rather than the previously assumed 0x42A9.
The scalar was changed from raw 8389 to 4965, matching the native L67 injector flow scaling relationship.
Seven additional low octane timing cells were reduced slightly, with no increases to ignition advance.
This revision differs from v1.4C by just 10 bytes, including the checksum update.
Static verification
All three BINs have passed static checksum and spark table consistency checks.
The latest audit examined 1,320 ignition table cells per BIN across the normal and extended high and low octane tables.
No low octane cells exceeded their corresponding high octane cells, and the checked 593 mg/cylinder and 4800 RPM table boundaries were consistent.
The L67 injector v1.4C and v1.5 versions retain the L36 Enhanced operating system, original MAF transfer and factory transmission shift calibration.
These are research calibrations, not finished tunes. None has been tested on this engine, validated on a dyno or proven safe under boost.
I'm interested in whether the native L67 Enhanced operating system offers enough additional high load capability to justify switching firmware instead of continuing to refine these L36 based versions.
I've got a VS Commodore sedan with the factory 3.8L L36 Ecotec and 4L60E automatic. It's my brother's car, and we're setting it up for a turbo with factory L67 injectors.
The spare PCM supplied with the turbo setup is a Delco 16210672, originally running the BSTK1451 ($51C) calibration.
I've got an XGecu programmer, Moates G6 adapter, Ostrich 2.0 for real time tuning, and an eXTuner wideband that uses the Innovate protocol. I also have the matching ADX for logging through TunerPro.
I'm trying to establish which firmware is actually compatible with my existing PCM and which would be the better foundation for a turbocharged L36.
The two Enhanced BINs I'm comparing
VS L36 $51 Enhanced
BIN: VS_V6_$51_Enhanced_v1.4b.bin
Matching XDF: v1.4g
VS L67 $51 Enhanced
BIN: VS_V6_SC_$51_Enhanced_v1.0a.bin
Matching XDF: v1.0d
Both are 128 KB BINs.
My G6 adapter has a four position rotary selector, and I can program compatible 128 KB chips or prepare a 512 KB chip containing four separate 128 KB images. I'd verify the bank layout and readback before testing anything.
I've also got the Ostrich 2.0 for real time calibration changes.
The car isn't currently being driven, as the battery is removed while it's being relocated to the boot. There's no rush to get it running, so I've got time to research the firmware and hardware properly.
My questions
1. Can the native VS L67 Enhanced BIN run on an N/A 16210672 PCM?
I understand the VS L36 and L67 PCMs share some hardware, including the 16210672 service number, but apparently have different PCB component populations.
My L36 PCM has the U7 IC unpopulated, which I've read relates to the traction control input.
Would the missing U7 IC or other component differences prevent the native L67 Enhanced firmware from operating correctly?
I'm particularly interested in whether the engine management, ALDL communications and factory 4L60E transmission control would function correctly.
Are the relevant PCM pinouts and output drivers effectively interchangeable, or are there specific components required for the L67 operating system?
2. Does the L67 Enhanced firmware offer better extended airflow and ignition timing control?
This is one of the main reasons I'm considering the native L67 operating system instead of simply modifying the L36 Enhanced calibration.
From what I've researched, the VS L36 $51 Enhanced firmware already has extended high and low octane spark tables, along with fuel and injector multiplier tables, reaching approximately 977 mg/cylinder.
However, the native VS L67 Enhanced XDF contains separate high and low octane spark tables labelled for the 850 to 1650 mg/cylinder range.
I've been comparing the two firmware versions and their calibration tables, but I'm trying to establish whether the actual L67 operating code can independently select and interpolate those higher load cells.
Can anyone confirm whether the native VS L67 Enhanced firmware genuinely supports spark table selection through to 1650 mg/cylinder?
Does the L67 operating system provide greater usable load range or resolution compared with L36 Enhanced, or are the additional tables simply arranged differently?
I'd also like to know whether the L36 Enhanced firmware has any cylinder airmass limits that would make its extended tables less useful as airflow increases.
I've noticed differences in the ignition tables when comparing the same RPM and load coordinates between the L67 reference and my current L36 turbo calibration.
I understand that the L36 has a higher compression ratio than the L67, so I'm not assuming the factory L67 timing would be suitable for my turbocharged L36.
What interests me is whether the underlying L67 spark strategy offers more calibration control, rather than the factory timing values themselves.
If the L36 Enhanced firmware already provides equivalent control for my intended airflow, I'd rather continue developing that.
3. Are there other worthwhile differences between the L36 and L67 Enhanced operating systems?
Apart from injector characterization and the factory supercharged ignition calibration, does the L67 firmware offer any genuine advantages for a turbocharged L36?
I'm particularly interested in the actual operating code involving cylinder airmass calculations, high load fueling, injector pulse width calculations, MAF limits, adaptive spark control and knock retard.
I've also read about differences involving EGR, two speed fuel pump control, traction control and transmission related functions.
Are these simply features that can be configured or disabled, or are there hardware dependencies that would cause problems on an N/A PCM?
Would it be better to run the native L67 Enhanced firmware, or retain L36 Enhanced and transfer the relevant L67 injector and calibration data?
4. Would OSE 11P be a better alternative?
I'm also considering whether OSE 11P would offer worthwhile advantages for a turbocharged Ecotec while retaining the factory 4L60E automatic.
I understand that 11P requires compatible '424 PCM hardware rather than simply programming an 11P BIN into my existing 16210672.
Would converting to a compatible '424 PCM and making the necessary wiring changes be worthwhile, or is the existing VS $51 Enhanced firmware sufficiently capable?
I'm mainly interested in the available load range, fueling and spark control, logging capabilities and 4L60E support.
Current engine and turbo setup
The engine is a completely stock VS L36 Ecotec internally, not an L67 conversion.
It's currently fitted with a GT3582R style turbo, external wastegate, large intercooler and 3 inch charge piping.
The MAF is positioned after the intercooler, close to the throttle body.
I'm planning to run factory L67 injectors and initially target approximately 5 to 7 psi, depending on what the stock engine and fuel system can safely support.
I've also got ARP bolts available if they're needed, although I'm not planning a complete engine build at this stage.
I understand the MAF calibration, injector data, fuel pressure, ignition timing and commanded fueling all need to be correct for the actual hardware.
Background
The spare PCM and MEMCAL supplied with the turbo setup were advertised as already tuned.
However, after reading the MEMCAL and comparing it in TunerPro against a stock BSTK1451 calibration I already had, I couldn't identify any tuning changes.
The spare PCM plugged into the car and started despite VATS apparently not being disabled. I understand this doesn't necessarily mean VATS was bypassed, as the vehicle's existing security system may simply have accepted the PCM.
The engine ran with the turbo fitted and revved quickly, but it also warmed up rapidly and spluttered when the boost gauge indicated approximately 5 psi during a stationary rev.
I'm aware that's not something to continue doing on what appears to be an untouched factory calibration.
I've also removed the car's original PCM and still need to read its MEMCAL to confirm the original calibration ID and hardware details.
So it appears I was sold a supposedly tuned turbo PCM that was actually running a stock calibration.
Rather than paying for another tune, I've decided to work through the calibration myself and learn the system properly.
What I've done so far
I've already been working on modified VS L36 Enhanced calibrations for both factory L36 injectors and L67 injectors.
These are based on the L36 Enhanced operating system, with changes involving injector characterization, high load spark, fueling, adaptive spark and airflow related calibrations.
They're still being reviewed and haven't been validated on the vehicle.
I'm trying to determine whether continuing to develop the L36 Enhanced firmware is worthwhile, or whether I should start with the native L67 Enhanced firmware instead.
If the L67 operating system genuinely offers a larger usable cylinder airmass range and independently selectable spark tables extending to 1650 mg/cylinder, that seems like a potential advantage for a turbo setup.
On the other hand, if L36 Enhanced can already handle the airflow and provide sufficient spark and fueling control at my intended boost level, I'd rather avoid changing operating systems unnecessarily.
I don't want to spend weeks developing the L36 calibration only to discover the native L67 firmware would have been a better starting point.
What I'm trying to establish
I'm not asking what AFR to target or how to scale the injectors. I understand that calibration needs to be developed and verified using the wideband, logging and actual fuel pressure measurements.
My main questions are whether the native VS L67 $51 Enhanced firmware can operate correctly on my naturally aspirated 16210672 PCM, and whether its extended airflow and spark table capabilities provide a genuine advantage over L36 Enhanced.
Ideally, I'd like to retain my existing PCM rather than buy an L67 PCM unnecessarily.
Has anyone actually run the native VS L67 $51 Enhanced v1.0a BIN on an N/A 16210672 PCM with U7 unpopulated?
If so, did the engine management, ALDL communications and 4L60E operate correctly? Were any hardware or wiring changes required?
And has anyone confirmed through disassembly, logging or actual testing that the native VS L67 Enhanced firmware can access its full 850 to 1650 mg/cylinder spark tables?
I'm mainly looking for firsthand experience or technical evidence of the firmware differences, rather than general injector tuning advice.
I'm happy to work through the calibration myself once I know which operating system is the better foundation.
attached is where i am at right now with trying to work it out, these havent been tested in car or logged im just doing guesstimates.
for the vs ecotec turbo basetune.
My current VS L36 Enhanced turbo calibration revisions
I've also been developing two separate turbo calibration variants based on the clean VS L36 $51 Enhanced v1.4b BIN, using the matching v1.4g XDF.
VS L36 Enhanced turbo v1.4, factory L36 injectors
This is the stock injector version. Compared with the clean L36 Enhanced BIN, the earlier static audit recorded 1,052 changed bytes, all accounted for by the matching XDF.
Changes include revised main and extended high and low octane ignition timing tables, including the 593 to 977 mg/cylinder load range and higher RPM tables.
Selected airflow limits, positive airflow delta allowances and adaptive spark parameters have been revised using the native L67 calibration as a reference.
Power enrichment has been brought in earlier, with approximately 21.09% TPS required through the main 2400 to 4800 RPM region. Warm PE commanded AFR is approximately 11.30:1, with selected high load open loop cells commanding 13.0:1 or richer.
The positive PE spark advance contribution has been neutralised to avoid adding timing on top of the main ignition tables.
Additional high load temperature corrections have been retained, including IAT retard, with the factory knock detection and ESC functions still active.
The original L36 injector flow scalar, battery compensation and MAF frequency to airflow calibration remain unchanged.
Other changes include the 4.11 differential PPK calibration, VATS disabled, and a temporary 4500 RPM fuel cut with 4200 RPM restart for initial testing.
The factory 4L60E shift and line pressure calibration tables have been retained.
VS L36 Enhanced turbo v1.4C, factory L67 injectors
This version builds on the L36 turbo calibration but changes the injector model for the factory Bosch 0280155868 L67 injectors.
The L67 injector flow scalar, battery voltage compensation, short pulse correction and minimum/default injector pulse width calibrations have been incorporated from the native VS L67 reference.
The injector flow scalar is approximately 213.867 ms/g, corresponding to the native L67 calibration.
The injector-related changes also include the purge pulse width threshold and trip computer fuel consumption constant.
The PE TPS transition has been smoothed between 1800 and 2400 RPM to avoid an abrupt change approaching the main 21.09% threshold.
The low octane spark tables have been compared against the native VS L67 tables using matching RPM and cylinder airmass coordinates. Selected cells exceeding the interpolated L67 reference were reduced, and the shared 593 mg/cylinder table boundaries were corrected.
An additional 15 hot, high load coolant temperature spark correction cells were made more conservative.
An earlier mistake involving the cranking calibration was also corrected after tracing the original HC11 code. Two bytes previously treated as a single 16 bit injector-related scalar were found to be independent startup thresholds and restored to their original L36 values.
VS L36 Enhanced turbo v1.5 REVIEW, factory L67 injectors
This is the latest research revision.
Further disassembly identified the actual cranking fuel scalar, F64SCAL, at BIN offset 0x42B3, rather than the previously assumed 0x42A9.
The scalar was changed from raw 8389 to 4965, matching the native L67 injector flow scaling relationship.
Seven additional low octane timing cells were reduced slightly, with no increases to ignition advance.
This revision differs from v1.4C by just 10 bytes, including the checksum update.
Static verification
All three BINs have passed static checksum and spark table consistency checks.
The latest audit examined 1,320 ignition table cells per BIN across the normal and extended high and low octane tables.
No low octane cells exceeded their corresponding high octane cells, and the checked 593 mg/cylinder and 4800 RPM table boundaries were consistent.
The L67 injector v1.4C and v1.5 versions retain the L36 Enhanced operating system, original MAF transfer and factory transmission shift calibration.
These are research calibrations, not finished tunes. None has been tested on this engine, validated on a dyno or proven safe under boost.
I'm interested in whether the native L67 Enhanced operating system offers enough additional high load capability to justify switching firmware instead of continuing to refine these L36 based versions.
You do not have the required permissions to view the files attached to this post.
