Jump to content
SAU Community

Recommended Posts

describe what happens please

does the inj/ign etc all show zero's ?

when you do DATA INIT, choose Yes (non default item) then press NEXT and then reboot the car

does it retain the previous settings?

i could post up default BNR32 maps, but it would by far easier to fix the root cause

if it wont DATA INIT, then its likely it wont save other changes too

so let's clarify and fix that up first - so as above, try DATA INIT the way listed above

  paulr33 said:
describe what happens please

does the inj/ign etc all show zero's ?

when you do DATA INIT, choose Yes (non default item) then press NEXT and then reboot the car

does it retain the previous settings?

i could post up default BNR32 maps, but it would by far easier to fix the root cause

if it wont DATA INIT, then its likely it wont save other changes too

so let's clarify and fix that up first - so as above, try DATA INIT the way listed above

The unit is used. the inj/ing settings do not show zeros. It retains what it was even when shut down and the battery is pulled and residual electricity is drained from the system. Changes I have made prior to the DATA INIT are retained.

when i DATA INIT and reboot the car, the settings are retained. Although after I did the 30 min idle it seems to idle better.

Thank for your help or at least trying.

this is a known issue, its covered in the PFC FAQ

view it from my signature and then look for "ECCS"

there is a known relay issue, and when the issue occurs, changes in the PFC tune are not saved at power off

which also explains why the DATA INIT doesn't clear, read it, and it tells you the correct fix

when you key off, the PFC needs an additional 1-2 seconds to write any run-time changes to NVRAM

if the install is shagged or the car isnt wired correctly, the PFC isnt given the extra 1-2 seconds required at key off

the end result is, at key off, the PFC doesnt get time to commit changes to NVRAM, so it results in a Read-only PFC or a "unsavable PFC" like what you are seeing

  paulr33 said:
this is a known issue, its covered in the PFC FAQ

view it from my signature and then look for "ECCS"

there is a known relay issue, and when the issue occurs, changes in the PFC tune are not saved at power off

which also explains why the DATA INIT doesn't clear, read it, and it tells you the correct fix

when you key off, the PFC needs an additional 1-2 seconds to write any run-time changes to NVRAM

if the install is shagged or the car isnt wired correctly, the PFC isnt given the extra 1-2 seconds required at key off

the end result is, at key off, the PFC doesnt get time to commit changes to NVRAM, so it results in a Read-only PFC or a "unsavable PFC" like what you are seeing

Thanks Paul. I had read your FAQ but didn't realize that the ignition needed to be cycled after the DATA INIT. I'll give it a try and keep the ignition off for at least a few seconds.

  • 2 months later...
  paulr33 said:
describe what happens please

does the inj/ign etc all show zero's ?

when you do DATA INIT, choose Yes (non default item) then press NEXT and then reboot the car

does it retain the previous settings?

i could post up default BNR32 maps, but it would by far easier to fix the root cause

if it wont DATA INIT, then its likely it wont save other changes too

so let's clarify and fix that up first - so as above, try DATA INIT the way listed above

Sorry to bring this back from death, but a friend's evo VII is having this issue. Both Ign/Inj maps are filled up with zero's and any change i make gets errased as soon as i press the PREV button.

I only have the commander to tune.

How can i fix this???

THanks a lot in advance guys.

  chip said:
Sorry to bring this back from death, but a friend's evo VII is having this issue. Both Ign/Inj maps are filled up with zero's and any change i make gets errased as soon as i press the PREV button.

I only have the commander to tune.

How can i fix this???

THanks a lot in advance guys.

locked for sure.

yep as the others have said 0's on the hand controller for the maps is a locked powerfc tune.

find a local tuner who has apexi fc commander pro or datalogit and unlock it (simple tick box) and away you go.

  paulr33 said:
yep as the others have said 0's on the hand controller for the maps is a locked powerfc tune.

find a local tuner who has apexi fc commander pro or datalogit and unlock it (simple tick box) and away you go.

i'll probably get from a friend a dattalogit box to use it with a laptop. But, how the heck do i unlock it? Is it a simple feature?

thanks a lot guys for your answeres.

yep

it's just a tickbox, no magic, no password

but sure to note, there are some things that are not restored when a tune is unlocked

be careful if this car has injectors that are non-std, and other key non std items such as AFM or map sensor

datalogit has some bugs where it mangles up the values sometimes when a tune is unlocked

i dont know why it does it, it just does its a bug with datalogit.

  paulr33 said:
yep

it's just a tickbox, no magic, no password

but sure to note, there are some things that are not restored when a tune is unlocked

be careful if this car has injectors that are non-std, and other key non std items such as AFM or map sensor

datalogit has some bugs where it mangles up the values sometimes when a tune is unlocked

i dont know why it does it, it just does its a bug with datalogit.

Thanks a lot paul. I'll post up as soo as i try this out.

I really like the power FC but i also really hate it to have this kind of problems.

I'm experiencing a problem now with a MY00 WRX that doesn't save when the key is off using the commander. It's not an engine swap, everything is stock (electrical) but i'm having this issue.

Once again, thanks a lot for the support mate.

Cheers.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • I'd be installing 2x widebands and using the NB simulation outputs to the ECU.
    • Nah, it's different across different engines and as the years went on. R32 era RB20, and hence also RB26, the TPS SWITCH is the idle command. The variable resistor is only for the TCU, as you say. On R33 era RB25 and onwards (but probably not RB26, as they still used the same basic ECU from the R32 era), the idle command is a voltage output of close to 0.45V from the variable resistor.
    • It's actually one of the worst bits of Nissan nomenclature (also compounded by wiring diagrams when the TCU is incorporated in ECU, or, ECU has a passthru to a standalone TCU).... the gripe ~ they call it the TPS, but with an A/T it's actually a combined unit ...TPS (throttle position switch) + TPS (throttle position sensor).... ..by the looks of it (and considering car is A/T) you have this unit... https://www.amayama.com/en/part/nissan/2262002u11 The connector on the flying lead coming out of the unit, is the TPS (throttle position sensor) ...only the TCU reads this. The connector on the unit body, is the TPS (throttle position switch) ...ECU reads this. It has 3 possible values -- throttle closed (idle control contact), open (both contacts open, ECU controls engine...'run' mode), and WOT (full throttle contact closed, ECU changes mapping). When the throttle is closed (idle control contact), this activates what the patent describes as the 'anti stall system' ~ this has the ECU keep the engine at idling speed, regardless of additional load/variances (alternator load mostly, along with engine temp), and drives the IACV solenoid with PWM signal to adjust the idle air admittance to do this. This is actually a specific ECCS software mode, that only gets utilized when the idle control contact is closed. When you rotate the TPS unit as shown, you're opening the idle control contact, which puts ECCS into 'run' mode (no idle control), which obviously is a non-sequitur without the engine started/running ; if the buzzing is coming from the IACV solenoid, then likely ECCS is freaking out, and trying to raise engine rpm 'any way it can'...so it's likely pulling the valve wide open....this is prolly what's going on there. The signal from the connector on the flying lead coming out of the unit (for the TCU), should be around 0.4volts with the throttle closed (idle position) ~ although this does effect low throttle shift points if set wrong, the primary purpose here is to tell TCU engine is at idle (no throttle demand), and in response lower the A/T line pressure ... this is often described as how much 'creep' you get with shifter in D at idle. The way the TPS unit is setup (physically), ensures the idle control contact closes with a high margin on the TPSensor signal wire, so you can rotate the unit on the adjustment slots, to achieve 0.4v whilst knowing the idle control contact is definitely closed. The IACV solenoid is powered by battery voltage via a fuse, and ground switched (PWM) by the ECU. When I check them, I typically remove the harness plug, feed the solenoid battery voltage and switch it to ground via a 5watt bulb test probe ; thing should click wide open, and idle rpm should increase... ...that said though, if it starts & idles with the TPS unit disconnected, and it still stalls when it gets up to operating temperature, it won't be the IACV because it's unused, which would infer something else is winking out...  
    • In the context of cam 'upgrader' I mean generally people who upgrade headers/cams - not my specific change. I mean it makes sense that if I had a bigger cam, I may get more false lean readings. So if I went smaller, I'd get less false lean readings. To a point where perhaps stock.. I'd have no false lean readings, according to the ECU. But I'm way richer than stock. My bigger than normal cam in the past also was giving false rich leanings. It's rather odd and doesn't add up or pass the pub test. Realistically what I want is the narrowbands to effectively work as closed loop fuel control and keep my AFR around 14.7 on light sections of the map. Which is of course the purpose of narrowband CL fuel control. So if I can change the switch points so the NB's target 14.7 (as read by my WB) then this should be fine. Haven't actually tested to see what the changed switchpoints actually result in - car needs to be in a position it can idle for awhile to do that. I suspect it will be a troublesome 15 min drive home with lots of stalling and way too rich/lean transient nightmare bucking away for that first drive at 2am or whevener it ends up being. Hopefully it's all tune-able. Realistically it should be. This is a very mild cam.
    • Messing with narrowband switchovers is a terrible bandaid. I don't want to think about it. You are a cam "upgrader" only in concept. As you said, your new cam is actually smaller, so it's technically a downgrade. OK, likely a very small downgrade, but nevertheless. But the big thing that will be the most likely suspect is the change of the advance angle. That change could be equivalent to a substantial decrease in cam lobe duration. I haven't gone to the effort of trying to think about what your change would actually cause. But until someone (you, me (unlikely), Matt, someone else) does so and comes to a conclusion about the effect, it remains a possibility that that is the change that is causing what you're seeing.
×
×
  • Create New...