This shows how little I know, how did you guys view the bin file I uploaded? I have TunerPro installed on another laptop and want to view it inside my house but if I try and open it is says 'detecting hardware' and does nothing. Sorry its been years since I looked at all this.Charlescrown wrote: ↑Wed Jan 22, 2025 8:07 am 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.
265 Hemi to efi
Re: 265 Hemi to efi
Re: 265 Hemi to efi
Top left of screen, select open bin then click on the bin that you have saved.
Next one along should XDF and same again.
Next one along should XDF and same again.
Re: 265 Hemi to efi
Thanks Brindo, my problem is that Tunerpro is stuck 'Detecting Hardware' as I am trying to using this on a laptop not connected to the car but it doesn't proceed go any further.
Re: 265 Hemi to efi
I'm in there now, installed latest version of RT and all good.
I just used the XDF file I downloaded called 'OSEPV112-Categorised - 1,2 and 3 bar', is that ok? I can read the bin file so can't be too far off.
Now that I have this bin saved with the boost AE and spark maps and other changes made by the dyno tuner, if required this could be uploaded back into the NVRAM by opening bin in Tunerpro and then click 'Upload current bin to Emulator'? Would I have to change any other software or settings? And this is how I would import a fresh stock OSE_12P V112 bin to the NVRAM.
To be honest, if I unhook the boost and swap the injectors back to standard the engine is virtually stock and back 10 odd years ago the upboosted engine ran ok on the standard 12P file.
I just used the XDF file I downloaded called 'OSEPV112-Categorised - 1,2 and 3 bar', is that ok? I can read the bin file so can't be too far off.
Now that I have this bin saved with the boost AE and spark maps and other changes made by the dyno tuner, if required this could be uploaded back into the NVRAM by opening bin in Tunerpro and then click 'Upload current bin to Emulator'? Would I have to change any other software or settings? And this is how I would import a fresh stock OSE_12P V112 bin to the NVRAM.
To be honest, if I unhook the boost and swap the injectors back to standard the engine is virtually stock and back 10 odd years ago the upboosted engine ran ok on the standard 12P file.
Re: 265 Hemi to efi
Thanks, I can't imagine its running on MAP B as the dyno guy would have said something but I will check that pin B9 is not wired.Holden202T wrote: ↑Fri Jan 24, 2025 11:25 am i just had a look through your tune and theres a few things that look odd .... im assuming your running on MAP A settings, but if for some reason its on MAP B then theres some fucked up settings:
for starters the map sensor is not even configured right for it - both section A & B are ticked which is not a valid setting.
map b also has closed throttle VE set although the settings do look reasonable so it probably would work (if the map sensor setting was correct)
for reference, pin B9 is the map switch function and grounding it should activate map b ..... this can be easily seen when data logging it shows it.
i stand by my statement to try a fresh tune with just the absolute bar minimum to make it run changed.
I Assume this what you mean, that MAP B MAP sensor has both ticked.
I just need to go back and recheck the base timing settings first but I understand that a fresh tune will clear up a lot on unknowns.
I will also save a log file on start up and hopefully I can get it to idle for a short time.
-
- Posts: 1956
- Joined: Sat Aug 06, 2011 7:58 am
- cars: V8 VR Commodore BT1
LB Lancer 2L turbo & Delco
Starion TBI with Delco
Mitsubishi Lancer EVO4 track car
NA MX5
3 vintage motor bikes - Location: Padstow NSW
Re: 265 Hemi to efi
Before you check the base timing check that the harmonic balancer hasn't slipped. If that's slipped trying to use the mark on the outer ring is a waste of time. Just find TDC No1 and see if the timing mark lines up with zero degrees. You can just pull the plug out and use a screwdriver turn the engine over by hand till it shows maximum travel.
Re: 265 Hemi to efi
Yes thanks I will check again with a helper & thanks for the advice about using the compare tool. I am preparing a spreadsheet of all parameters etc that have been changed in the current tune compared to the stock 12p bin.Charlescrown wrote: ↑Sat Jan 25, 2025 7:28 am Before you check the base timing check that the harmonic balancer hasn't slipped. If that's slipped trying to use the mark on the outer ring is a waste of time. Just find TDC No1 and see if the timing mark lines up with zero degrees. You can just pull the plug out and use a screwdriver turn the engine over by hand till it shows maximum travel.
- delcowizzid
- Posts: 5630
- Joined: Sat Feb 28, 2009 8:38 pm
- Location: Wellington NZ
- Contact:
Re: 265 Hemi to efi
Map a looks to be set for 3 bar map sensor map b is incorrect
If Its Got Gas Or Ass Count Me In.if it cant be fixed with a hammer you have an electrical problem
- Holden202T
- Posts: 10394
- Joined: Sat Feb 28, 2009 9:05 pm
- Location: Tenambit, NSW
- Contact:
Re: 265 Hemi to efi
i would recommend using the OSE flashtool to upload/download just to be safe.heff0018 wrote: ↑Sat Jan 25, 2025 6:45 am I'm in there now, installed latest version of RT and all good.
I just used the XDF file I downloaded called 'OSEPV112-Categorised - 1,2 and 3 bar', is that ok? I can read the bin file so can't be too far off.
Now that I have this bin saved with the boost AE and spark maps and other changes made by the dyno tuner, if required this could be uploaded back into the NVRAM by opening bin in Tunerpro and then click 'Upload current bin to Emulator'? Would I have to change any other software or settings? And this is how I would import a fresh stock OSE_12P V112 bin to the NVRAM.
To be honest, if I unhook the boost and swap the injectors back to standard the engine is virtually stock and back 10 odd years ago the upboosted engine ran ok on the standard 12P file.
the other thing too ... if you data log with the laptop, at key on the map sensor should be 100kpa, if its not that might indicate the map sensor settings arnt right.
im not sure if you've said if its a 2 or 3 bar map .... set accordingly.
No matter what the question is, the answer is always more horsepower! 
Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread

Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread
- antus
- Site Admin
- Posts: 9009
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: 265 Hemi to efi
the ADX contains the scaling for the MAP when you are logging, so it is possible to have the wrong thing set in the tune and see the right thing when logging or vice versa. You def need the right settings in the calibration and the right ADX loaded for the MAP sensor you have.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396