Tunerpro glitch, lucas 14cux?

[RR90]

Hi all, I am trying to resolve an issue that has popped up whilst trying to arrange my fuel map.(4.6 rv8).
I attempted to use fuel map 2 (green), but the values appear to be nonsense. Map 1 looks normal. (I cant load an image at the moment. )
Starting enrichment looks like rubbish too, the top row seems to have 2 or 3 values repeated instead of a linear progression of temp values.
I am using tunerpro 5 v8853(?).
Am I going mad? Regards Steve

[blitzracing]

Possibly, the normal issue is you cant see any map data, not, white being there, but green not. Use the option to display the 3d map and see what they look like graphically.

[blitzracing]

Just a thought- have you used the utility to copy the map into the second half of the chip? You may be be seeing random data if the second 128k of chip space is empty, and thats where you are looking.

[RR90]

The graphic view is just as bad as the actual values. Also the green fuel map will display in hex only. I have gone back to the red tune. I dont know if the problem will manifest in other ways, but I did try the operation pride tune and it displayed as map 5 in rovergauge.
I'm not sure what the problem is. Any advice appreciated.
Thanks, Steve

[RR90]

No I haven't used the utility. I wouldn't know how. I have just modified bins that I have downloaded.

[blitzracing]

The early chips where 128k, and the later ones are 256k so the upper part of the chip is blank. I dont fully understand how the duplication of the two halves is laid out, but the utility copies into the second 128k. It also corrects the checksum error when you alter the maps.

Download here- 14cux toolkit

http://www.remap-14cux.uk/gadgets.html

Edited by blitzracing on Thursday 1st November 13:35

[RR90]

Thanks for that . I'll look into it tomorrow. Thanks Steve

[stevesprint]

RR90 said:

Hi all, I am trying to resolve an issue that has popped up whilst trying to arrange my fuel map.(4.6 rv8).
I attempted to use fuel map 2 (green), but the values appear to be nonsense. Map 1 looks normal. (I cant load an image at the moment. )
Starting enrichment looks like rubbish too, the top row seems to have 2 or 3 values repeated instead of a linear progression of temp values.
I am using tunerpro 5 v8853(?).
Am I going mad? Regards Steve

If map 2 look nonsense in 'MAP 2 FUEL TABLE - Green' try 'MAP 2 R2422 & OLDER FUEL TABLE - Green' as it could be a very early 14CUX prom.

What is the CHIP ID and TUNE ID in TunerPro.

Do you have a prom emulator or are you opening the bin file from your hard drive?

If you saved to file via RoverGauge Mark is right, you'll need to run the 14CUX Tool kit to double up the prom file.

Does fuel map 2 look ok in RoverGauge?

Steve

[spitfire4v8]

As Steve says, it might be an early version of chip (but it's a 4.6 ? so shouldn't be)

If you're only looking at the rovergauge downloaded file then that will be 16k, there's a utility that allows you to double up that 16k and fix any checksum errors , really nifty bit of kit, it's called 14cux toolkit and it's available from Steve's go-to lucas remap website

I don't have any experience of the later tunerpro software though, I have an earlier version customised with just the important stuff I need for remapping, it just works so I'm loathed to update anything for just the reasons you're encountering .. it might not work after updating

[RR90]

The bin I am using is a 2967 tune. It may be an evolution of my original tune. (Was 3.9 low comp.) I have also tried the later 3652 op pride tune. The values are still wacky on map 2.
I won't pursue it any further because map 1 is working for me.
I wouldn't mind some clarification of terms, as there seems to be some interchangeable or similar sounding terms.
Main scalar= multiplier?
Row scalar= adjusts range or sensitivity of afm?
Afm offset= moves centre point of map up or down.? Am I on the right track with these?
I had fooled myself into thinking I had done a good job using af ratio meter and seat of pants until I realised I was hitting bottom row on half throttle.🤨 Thanks again for your input. Steve

[blitzracing]

Pop me a copy of your bin, ill try it out. [e-mail]

[stevesprint]

RR90 said:

The bin I am using is a 2967 tune. It may be an evolution of my original tune. (Was 3.9 low comp.) I have also tried the later 3652 op pride tune. The values are still wacky on map 2.
I won't pursue it any further because map 1 is working for me.
I wouldn't mind some clarification of terms, as there seems to be some interchangeable or similar sounding terms.
Main scalar= multiplier?
Row scalar= adjusts range or sensitivity of afm?
Afm offset= moves centre point of map up or down.? Am I on the right track with these?
I had fooled myself into thinking I had done a good job using af ratio meter and seat of pants until I realised I was hitting bottom row on half throttle.?? Thanks again for your input. Steve

Does map 2 look wacky in RoverGauge?

Yes, you're on the right track with those terms above.

Sounds like you need to reduce your row scalar, try 90 to 9F for your 4.6L and leave the AFM offset at 1E. In RoverGauge logs I aim for a maximum currentFuelMapRow of 6.8 to 6.9 then you know you're not over shooting, I'm sure you realise the top row is 0.
Enjoy, Steve

[RR90]

Thanks to SteveSprint Those numbers you quoted work pretty well. I am herding the chickens in the right direction.
There are a few items in your xdf file that I haven't seen before, can you tell me the difference between fam offset global and mad scalar offset. They seem to be interlinked.
Also cranking idle adjustment. Is this some sort of stepper override?.
Thanks again Steve.( yeah another one. !)
Ps thanks also to Markblitz.

[stevesprint]

RR90 said:

Thanks to SteveSprint Those numbers you quoted work pretty well. I am herding the chickens in the right direction.
There are a few items in your xdf file that I haven't seen before, can you tell me the difference between fam offset global and mad scalar offset. They seem to be interlinked.
Also cranking idle adjustment. Is this some sort of stepper override?.
Thanks again Steve.( yeah another one. !)
Ps thanks also to Markblitz.

It’s a pleasure, I never thought Mark Blitz and I would be helping people from all around the world.

Once you’ve got your AFM row scaled correctly the next step is to adjust the main fuel multiplier until you have the correct AFR on full load with near max FF hex values on the bottom row where the active cell passed through during the full load run, then finally you can start mapping the rest of the individual cells in the fuel table. That way you’ll maximise the range and values of the fuel table.

In TunerPro “AFM Table Offset (Global) (at 0x41C8)” & “TABLE 1-5 MAF Scalar Offset” (at 0x41C7)” are the same but one is 1 byte long and the other 2 bytes long. Sorry for the confusion, I’ll remove the single byte parameter as the AFM row offset is 2 bytes long in the data at offset 41C7 & 41C8, however in reality you’ll only ever need to change 41C8.

There is only one AFM offset per chip and increasing it pulls the active cell up uniformly across the whole table, effectively moving the centre point of the table. Whereas there are 5 AFM row scalar, 1 per map and expands and shrinks the usable range of the fuel table. To make mapping idle easier and more stable you could go one step further and massage your AFM scalar and offset together so your idle is on row 1.0 & full load on row 6.8 in the RoverGauge logs, that's the second and last row on RoverGauge's main screen.

Cranking Idle Adjustment (at prom offset 415D) sets the stepper position while cranking as per the following list and can be seen in RoverGauge before cranking while the coolant temperature is above 87 deg °c, but may via with different tunes files.
10=31%
14=33%
1A=36% (TVR&LR)
20=40% (Cold weather)
2C=46%
32=50%

Whereas the Idle Temperature Table (Open-Loop) (9x3) starting @ 4184 set the idle for the first 4 seconds after cranking and is base on coolant temperature and doesn’t effect the AFR. This Idle Temperature Table can remain active longer if you drive off within 4 second of starting not giving the ECU long enough to activate closed loop idle control (target idle in RoverGauge) and then you could end up with the wrong idle speed while coasting.

Keep up the good progress and let us know how it goes.