Instructions to change fuel maps on 14CUX Griffith, Chimaera
Discussion
Steve/Dan
I’m looking to switch between map 1, 2 and 3 for testing various Map setups, SCALAR and MAF Changes on my Pre CAT :-) . Am I right in assuming the contents of ‘fuelMap2’ in the data*.asm can be pasted and replace all of the ‘fuelMap1’ and ‘fuelMap3’ references without issue? If so, I’m planning to build a tune resistor switch box :-) and reduce the times I crack open my CPU and re-flash the EEPROM.
Cheers
MPO
I’m looking to switch between map 1, 2 and 3 for testing various Map setups, SCALAR and MAF Changes on my Pre CAT :-) . Am I right in assuming the contents of ‘fuelMap2’ in the data*.asm can be pasted and replace all of the ‘fuelMap1’ and ‘fuelMap3’ references without issue? If so, I’m planning to build a tune resistor switch box :-) and reduce the times I crack open my CPU and re-flash the EEPROM.
Cheers
MPO
Hi! I have almost zero time for my Rangie and reading forum past months, but I was thinking on a maybe silly idea. You guys lenghten the RPM range, but what if I want to shorten it?
Based on my logs, the max RPM was about 3200, even when I accelerate hardly. I drive it mainly in the range of 1200-2200 RPM, both on- and off-road. So would it be good to restructure the fuel table, to be more detailed below 2500 RPM, or its totally useless?
Based on my logs, the max RPM was about 3200, even when I accelerate hardly. I drive it mainly in the range of 1200-2200 RPM, both on- and off-road. So would it be good to restructure the fuel table, to be more detailed below 2500 RPM, or its totally useless?
MPO said:
Steve/Dan
I’m looking to switch between map 1, 2 and 3 for testing various Map setups, SCALAR and MAF Changes on my Pre CAT :-) . Am I right in assuming the contents of ‘fuelMap2’ in the data*.asm can be pasted and replace all of the ‘fuelMap1’ and ‘fuelMap3’ references without issue? If so, I’m planning to build a tune resistor switch box :-) and reduce the times I crack open my CPU and re-flash the EEPROM.
Cheers
MPO
Yes, you can cut and paste the maps- ideal if you want to set up a cat map in the non cat position for 14.7:1 without the lambda feedback- you can switch tune resistor with a switch box, but you will have to stick with white and blue for cat use or green and yellow for non cat use- so a single switch where you simply sort out a resistor is all you need- so for say cat use you would have a 1.8 k and 2.2 k in series with a switch across the 2.2 k. short out the 2.2.k and you get the blue map, or open circuit you will get the white map. You need to do an ECU rest between switching maps to prevent it throwing a fault code.I’m looking to switch between map 1, 2 and 3 for testing various Map setups, SCALAR and MAF Changes on my Pre CAT :-) . Am I right in assuming the contents of ‘fuelMap2’ in the data*.asm can be pasted and replace all of the ‘fuelMap1’ and ‘fuelMap3’ references without issue? If so, I’m planning to build a tune resistor switch box :-) and reduce the times I crack open my CPU and re-flash the EEPROM.
Cheers
MPO
blitzracing said:
Yes, you can cut and paste the maps- ideal if you want to set up a cat map in the non cat position for 14.7:1 without the lambda feedback- you can switch tune resistor with a switch box, but you will have to stick with white and blue for cat use or green and yellow for non cat use- so a single switch where you simply sort out a resistor is all you need- so for say cat use you would have a 1.8 k and 2.2 k in series with a switch across the 2.2 k. short out the 2.2.k and you get the blue map, or open circuit you will get the white map. You need to do an ECU rest between switching maps to prevent it throwing a fault code.
Hi MarkThanks for your reply and clarification, I like your tips on the resistor switching :-) .
Cheers
MPO
sszab77 said:
Hi! I have almost zero time for my Rangie and reading forum past months, but I was thinking on a maybe silly idea. You guys lenghten the RPM range, but what if I want to shorten it?
Based on my logs, the max RPM was about 3200, even when I accelerate hardly. I drive it mainly in the range of 1200-2200 RPM, both on- and off-road. So would it be good to restructure the fuel table, to be more detailed below 2500 RPM, or its totally useless?
I don't think there is much to be gained by doing this.Based on my logs, the max RPM was about 3200, even when I accelerate hardly. I drive it mainly in the range of 1200-2200 RPM, both on- and off-road. So would it be good to restructure the fuel table, to be more detailed below 2500 RPM, or its totally useless?
stevesprint said:
danbourassa said:
stevesprint said:
Dan, Dave or Colin
I've been asked if a 512K EPROM with 4 prom images would work in the 14CUX or would it be safe to try?
Cheers
Steve
When the 32K PROM (27C256) was introduced and quickly replaced the 16K (27C128) it was compatible by design because the /PGM input was re-assigned to the additional address line (A14) which was needed. This program pin was already hardwired high in the circuit board because /PGM is active-low. This is why only the upper half of the 32K PROM is accesible in the 14CUX.I've been asked if a 512K EPROM with 4 prom images would work in the 14CUX or would it be safe to try?
Cheers
Steve
This compatibility approach was continued with the 64K PROM (27C512). In this case, the Vpp input which is normally held at +5 volts was reassigned to the additional address line (A15). This would mean that only the top 16K of the 64K PROM would be used but it should work.
The reason one would want to do this is the same as using the 32K PROM in place of the 16K. The earlier chips are actually harder to find and can be more expensive than the later, larger devices.
Thanks, Steve
When 256s are cheap as chips here:
http://www.ebay.it/itm/like/221723906362?clk_rvr_i...
Edited by davep on Friday 11th September 12:17
These work well and less than 2 weeks delivery.
http://www.ebay.co.uk/itm/141665307479?_trksid=p20...
http://www.ebay.co.uk/itm/141665307479?_trksid=p20...
jjohnson23 said:
I have just bought a 14cux and taken a reading via Rovergauge.
It is image R2161 which if I remember from previous posts is a very old revision.
If I remove the prom from the board and fit a socket is it going to be a problem making up a suitable eprom image?
By the way it only cost a few quid so I am willing to give it a go.
Paul,It is image R2161 which if I remember from previous posts is a very old revision.
If I remove the prom from the board and fit a socket is it going to be a problem making up a suitable eprom image?
By the way it only cost a few quid so I am willing to give it a go.
Should be ok as you’re not run lambda probes. It’s only an issue with lambda probes on the very early 14CUXs with the MVA5033 chip instead of the later MVA5033KA chip.
jjohnson23 said:
These work well and less than 2 weeks delivery.
http://www.ebay.co.uk/itm/141665307479?_trksid=p20...
99p each with free postage, that's especially good for the electrically erasable proms and therefore worth the wait.http://www.ebay.co.uk/itm/141665307479?_trksid=p20...
MPO said:
Thanks Dan and Steve :-)
I’m hoping this is not off topic… I have a manual fan override switch that I’m sure most of us have by now. When I use the manual override my RPM’s increase by about 50 RPM… Not ideal when you want to keep the engine speed down in traffic jams and almost defeats the object really IMHO. Is there setting option to adjust this in the 14CUX code?
I’ve finally had a chance to test the heated screen +12v input on pin 8 and can now confirm applying +12v to the heated screen input on pin 8 actually LOWERs the idle speed by the data value at prom offset $41E9 (idleAdjForHeatedScreen).I’m hoping this is not off topic… I have a manual fan override switch that I’m sure most of us have by now. When I use the manual override my RPM’s increase by about 50 RPM… Not ideal when you want to keep the engine speed down in traffic jams and almost defeats the object really IMHO. Is there setting option to adjust this in the 14CUX code?
My precat's idleAdjForHeatedScreen has always been 00 plus my cooling fans +12 volts supply has always been connected to pin 8. Intrestingly when my fans first kick in the idle initially rises about 50 rpm for 1 to 2 seconds and then settles back down to the original idle speed. (base + neutral/manual select). With this set up the engine copes really well with the initial extra load of the fan and therefore I recommend it if you are are experiencing issues when your fans come on.
Hi Colin
When you are working on RoverGauge next please can you add the RPM limiter and AFM row scalar to the line above the fuel table next to the current map and multiplier. The RPM limiter is a common question and AFM row scalar will be useful when comparing main multipliers.
I've noticed if you start log with all sensors selected and then de-select some the de-selected sensors are then constantly logged with their last known values and not set to zero which is misleading. I don't mind if the de-selected sensors are completely stripped out or just set to zero.
Also, I've recently noticed if you connect before turning on the ignition the Tune, Ident and Checksum fixer are not loaded when you eventually power on the ignition. I guess I'm noticing this now I'm using the new auto connect option and have RoverGauge in my startup menu. It is also an issue without the auto connect option.
When you are working on RoverGauge next please can you add the RPM limiter and AFM row scalar to the line above the fuel table next to the current map and multiplier. The RPM limiter is a common question and AFM row scalar will be useful when comparing main multipliers.
I've noticed if you start log with all sensors selected and then de-select some the de-selected sensors are then constantly logged with their last known values and not set to zero which is misleading. I don't mind if the de-selected sensors are completely stripped out or just set to zero.
Also, I've recently noticed if you connect before turning on the ignition the Tune, Ident and Checksum fixer are not loaded when you eventually power on the ignition. I guess I'm noticing this now I'm using the new auto connect option and have RoverGauge in my startup menu. It is also an issue without the auto connect option.
stevesprint said:
I’ve finally had a chance to test the heated screen +12v input on pin 8 and can now confirm applying +12v to the heated screen input on pin 8 actually LOWERs the idle speed by the data value at prom offset $41E9 (idleAdjForHeatedScreen).
My precat's idleAdjForHeatedScreen has always been 00 plus my cooling fans +12 volts supply has always been connected to pin 8. Intrestingly when my fans first kick in the idle initially rises about 50 rpm for 1 to 2 seconds and then settles back down to the original idle speed. (base + neutral/manual select). With this set up the engine copes really well with the initial extra load of the fan and therefore I recommend it if you are are experiencing issues when your fans come on.
Steve, my good man, I respectfully disagree with your conclusion.My precat's idleAdjForHeatedScreen has always been 00 plus my cooling fans +12 volts supply has always been connected to pin 8. Intrestingly when my fans first kick in the idle initially rises about 50 rpm for 1 to 2 seconds and then settles back down to the original idle speed. (base + neutral/manual select). With this set up the engine copes really well with the initial extra load of the fan and therefore I recommend it if you are are experiencing issues when your fans come on.
The 14CUX code shows that the value in $C1E9 (or $41E9) is additive, not subtractive. The code also shows that +12V at pin 8 means that the screen heater is OFF (zero volts is ON). You may have never noticed the backwards wiring since the adjustment value was always zero.
As far as the temporary rise in RPM, I suspect that it's just a momentary over-correction by the stepper motor.
danbourassa said:
stevesprint said:
I’ve finally had a chance to test the heated screen +12v input on pin 8 and can now confirm applying +12v to the heated screen input on pin 8 actually LOWERs the idle speed by the data value at prom offset $41E9 (idleAdjForHeatedScreen).
My precat's idleAdjForHeatedScreen has always been 00 plus my cooling fans +12 volts supply has always been connected to pin 8. Intrestingly when my fans first kick in the idle initially rises about 50 rpm for 1 to 2 seconds and then settles back down to the original idle speed. (base + neutral/manual select). With this set up the engine copes really well with the initial extra load of the fan and therefore I recommend it if you are are experiencing issues when your fans come on.
Steve, my good man, I respectfully disagree with your conclusion.My precat's idleAdjForHeatedScreen has always been 00 plus my cooling fans +12 volts supply has always been connected to pin 8. Intrestingly when my fans first kick in the idle initially rises about 50 rpm for 1 to 2 seconds and then settles back down to the original idle speed. (base + neutral/manual select). With this set up the engine copes really well with the initial extra load of the fan and therefore I recommend it if you are are experiencing issues when your fans come on.
The 14CUX code shows that the value in $C1E9 (or $41E9) is additive, not subtractive. The code also shows that +12V at pin 8 means that the screen heater is OFF (zero volts is ON). You may have never noticed the backwards wiring since the adjustment value was always zero.
As far as the temporary rise in RPM, I suspect that it's just a momentary over-correction by the stepper motor.
davep said:
As always I'm confused. If pin 8 is +12V for heated front screen OFF the Land Rover 14CUX diagnostics test procedure (31) is wrong! Could there be an internal inversion between pin 8 and the ADC routine?
Dave, this was probably the case originally. Both the troubleshooting guide and the schematic (dated 1990) in the shop manual indicate that +12V is ON. However, I just went out to measure pin 8 in my 1993 RR and +12V is OFF in that vehicle. I think it's clear that the intent in the 14CUX code was to raise the RPM when the alternator came under heavy load. Maybe, as the alternator became higher amperage over the years, they realized that they could get away with zero RPM adjustment. Anyway, I'm quite sure that the 14CUX code expects +12V_OFF/0V_ON at Pin 8.stevesprint said:
Hi Colin
When you are working on RoverGauge next please can you add the RPM limiter and AFM row scalar to the line above the fuel table next to the current map and multiplier. The RPM limiter is a common question and AFM row scalar will be useful when comparing main multipliers.
I've noticed if you start log with all sensors selected and then de-select some the de-selected sensors are then constantly logged with their last known values and not set to zero which is misleading. I don't mind if the de-selected sensors are completely stripped out or just set to zero.
Also, I've recently noticed if you connect before turning on the ignition the Tune, Ident and Checksum fixer are not loaded when you eventually power on the ignition. I guess I'm noticing this now I'm using the new auto connect option and have RoverGauge in my startup menu. It is also an issue without the auto connect option.
Hi Steve/ColinWhen you are working on RoverGauge next please can you add the RPM limiter and AFM row scalar to the line above the fuel table next to the current map and multiplier. The RPM limiter is a common question and AFM row scalar will be useful when comparing main multipliers.
I've noticed if you start log with all sensors selected and then de-select some the de-selected sensors are then constantly logged with their last known values and not set to zero which is misleading. I don't mind if the de-selected sensors are completely stripped out or just set to zero.
Also, I've recently noticed if you connect before turning on the ignition the Tune, Ident and Checksum fixer are not loaded when you eventually power on the ignition. I guess I'm noticing this now I'm using the new auto connect option and have RoverGauge in my startup menu. It is also an issue without the auto connect option.
As the AFR/RG database references all fields by default, removing them will have an impact on the default database table structure. To cope with various user requirements, It would be best to leave them all in but enter a null or zero values in the log. It does this at the moment and proves to work well. :-)
Cheers
MPO
stevesprint said:
Hi Colin
When you are working on RoverGauge next please can you add the RPM limiter and AFM row scalar to the line above the fuel table next to the current map and multiplier. The RPM limiter is a common question and AFM row scalar will be useful when comparing main multipliers.
I've noticed if you start log with all sensors selected and then de-select some the de-selected sensors are then constantly logged with their last known values and not set to zero which is misleading. I don't mind if the de-selected sensors are completely stripped out or just set to zero.
Also, I've recently noticed if you connect before turning on the ignition the Tune, Ident and Checksum fixer are not loaded when you eventually power on the ignition. I guess I'm noticing this now I'm using the new auto connect option and have RoverGauge in my startup menu. It is also an issue without the auto connect option.
Hi Steve,When you are working on RoverGauge next please can you add the RPM limiter and AFM row scalar to the line above the fuel table next to the current map and multiplier. The RPM limiter is a common question and AFM row scalar will be useful when comparing main multipliers.
I've noticed if you start log with all sensors selected and then de-select some the de-selected sensors are then constantly logged with their last known values and not set to zero which is misleading. I don't mind if the de-selected sensors are completely stripped out or just set to zero.
Also, I've recently noticed if you connect before turning on the ignition the Tune, Ident and Checksum fixer are not loaded when you eventually power on the ignition. I guess I'm noticing this now I'm using the new auto connect option and have RoverGauge in my startup menu. It is also an issue without the auto connect option.
Apologies for the delay in getting back to you. I've been quite busy lately.
I can definitely take care of all of this in an upcoming release. The change to zero-out the sensors readings in the log when they are disabled is already done, and I just fixed the tune/ident/checksum read issue in the code as well. Adding the RPM limit and row scaler should be fairly straightforward so I'll make that change soon and do a build.
--Colin
I just released RoverGauge 0.8.2. This fixes a couple minor bugs, such as the failure to read the tune ID if RG is connected before the ECU is turned on. It also introduces logging of static data (e.g. fuel map contents, map multiplier, row scaler).
https://github.com/colinbourassa/rovergauge/releas...
--Colin
https://github.com/colinbourassa/rovergauge/releas...
--Colin
cmb said:
I just released RoverGauge 0.8.2. This fixes a couple minor bugs, such as the failure to read the tune ID if RG is connected before the ECU is turned on. It also introduces logging of static data (e.g. fuel map contents, map multiplier, row scaler).
https://github.com/colinbourassa/rovergauge/releas...
--Colin
Thanks again Colin.https://github.com/colinbourassa/rovergauge/releas...
--Colin
cmb said:
I just released RoverGauge 0.8.2. This fixes a couple minor bugs, such as the failure to read the tune ID if RG is connected before the ECU is turned on. It also introduces logging of static data (e.g. fuel map contents, map multiplier, row scaler).
https://github.com/colinbourassa/rovergauge/releas...
--Colin
Nice one Colin, I'll be putting this through its paces over the weekend.https://github.com/colinbourassa/rovergauge/releas...
--Colin
I'll let you know how it goes :-)
MPO
cmb said:
I just released RoverGauge 0.8.2. This fixes a couple minor bugs, such as the failure to read the tune ID if RG is connected before the ECU is turned on. It also introduces logging of static data (e.g. fuel map contents, map multiplier, row scaler).
https://github.com/colinbourassa/rovergauge/releas...
--Colin
Colinhttps://github.com/colinbourassa/rovergauge/releas...
--Colin
Brilliant, thanks.
The Row scalar always displays correctly and the RPM limit also displays correctly if you start the engine before connecting. However, I’ve noticed if you connect before firing up the RPM limit defaults to InitialRpmLimit of 5403rpm in data.asm.
There's no rush as winter has finally arrived.
Thanks again
Steve
Gassing Station | Griffith | Top of Page | What's New | My Stuff