265 Hemi to efi

[Charlescrown]

Spark reference angle is 10 for a 4 cyl, 70 for a 6 and 60 for an 8 cyl engine. This is a program setting and has no reference to base timing that should be set at 10 degrees for accurate display of the actual timing. OMG I hope you have a copy of your tune. I keep a copy of every change I have ever made so if I stuff it up "which has happened" I can just go back to the previous tune and have another go.

[heff0018]

bin saved jan 2025.bin

(32 KiB) Downloaded 78 times

Hi all, I have attached the bin I downloaded from TunerPro.

Spark reference angle shows 9.84

Is it possible to tell if this bin file is corrupt. Thanks in advance.

[brindo]

I’m potentially the last one who should offer advice on this. But maybe start with viewing that bin in Tunepro and use the Difference Tool to compare to a stock 12p bin? If theres a heap of changes that you didn’t make, or the fuel and timing maps have any crazy changes, or theres any Undefined Changes, then start again. You should have enough info from that bin to make a new 12p bin and that way you will know exactly what changes have been made.

[Charlescrown]

9.84 is the spark reference angle for a 4 cylinder engine. Maybe someone else might be a bit smarter than me but that's possibly a big problem. I'll have a look at the bin file later today. Gotta find the right XDF first.
Just had a quick look and your right it has a spark reference angle of 9.84 degrees. I had a look at a std VR V6 which is what 12P is based on and they use 69.96 which is what you end up with if you type in 70.
I'm not sure if a Hall effect trigger uses a different value to an inductive. That's something I haven't come across and I have no idea how the wrong figure would effect the running on the engine. Specialist brain needed here.
I don't think your program is corrupted. I don't like the tune but it shouldn't stop it starting and running. I'll spend some nore time later today.

[Holden202T]

9.84 is the right setting for the camira ignition module!

[Charlescrown]

Thanks for that info. So the number of cylinders makes no difference. I did see in some notes I have that the Hall Effect switching may play a part. I'd better put a note with this one.

[Mechcano]

I too do not believe that your bin file is corrupt, i compared it against one of mine and all the parameters were present, though the values varied.

One thing i though may be on the low side was "SCALAR: Map A: Run A/F Param - Displacement/inj flow rate (Litres/Grams per sec) 0.05 Grams/Sec"

For a quick test possibly change it to "0.10 Grams/Sec" to increase the fuel flow, this being a "global" value.

[Charlescrown]

I had a look at one of my tunes 4 cyl using L67 injectors and mine is set at 0.06 so that may correct if he has big injectors. Definately not corrupted. As I said I don't like the tune it looks like it's pouring buckets of fuel in under boost but the tuner would have been using a wideband. Thanks to 202 yes I did find in my notes when using a Camira module set the spark reference angle to 10 deg for all but thanks for the refresher. Old minds don't think as clear as they used to. The tune should start and run as it did before. I'm wondering if the nvram and it's communication channel. Never used one so can't comment on what they do in funny situations. Perhaps burn the tune into a VR V6 memcal and see how it responds. Looks like all the other possibilities have been exhausted without going outside the square to other issues but it must be fuel because it runs on aerostart. Silly thought maybe the intake manifold gasket has slipped blocking the injector spray pattern? When an engine backfires it's either lean or timing but mostly lean.

[brindo]

I am by no means a gun on any of this, but a quick look shows a few spikes in the ignition maps.
This is the boost ignition map, and there's also one crazy value in the 20 -100 kPa map at 85 kPa 5200 rpm. They could just be typos, and if they are, wouldn't cause the issues you are having.

Boost Igntion Map.PNG (65.33 KiB) Viewed 1157 times

I'm not sure what bin you started with, but there does seem to be a lot of Undefined items using the Difference Tool compared to BLCD.
I could be wrong, happy to be corrected, but if you start again with a new bin from scratch, and just carry over everything that is known, it will only cost you time not parts.

[heff0018]

I’m potentially the last one who should offer advice on this. But maybe start with viewing that bin in Tunepro and use the Difference Tool to compare to a stock 12p bin? If theres a heap of changes that you didn’t make, or the fuel and timing maps have any crazy changes, or theres any Undefined Changes, then start again. You should have enough info from that bin to make a new 12p bin and that way you will know exactly what changes have been made.

Thanks Brindo, didn’t know there was a difference tool and that will certainly be helpful