Jump to content
SAU Community

Recommended Posts

I thought I'd start a new thread for this seen as I was stealing the other one a bit. And I think this might be an issue if it turns out to be a problem with the new gen Power FC's

If you havent read the other thread I'll do a summary here.

Basically the Power FC is retarding around 10 Degrees when going from closed throttle to any throttle input. It will stay at 10 degrees retarded for about 1-2 seconds then go back to normal map at which point the car surges forward with a power boost. It appears like its going to the idle map then taking a second to realise its off closed throttle before reacting

This is a graph on the HC of timing, showing what is happening:

White and Red are gear changes where it is retarding the timing

Blue is a normal gear change with normal timing

TimingEdit.jpg

So far I have tried:

Adjust TPS - No change, except when adjusting it to far so it didn't go into the idle map at all

Data Init - Changed injector and AFM settings only and went for a light drive, no change

Changed TPS vs IGN - In FC Edit, every value to 0, no results

Played with the IGN map - no results

Disconnected and turned off the boost control Kit - no result

Below 60 Degrees, everything works fine, so it must be fine in the cold start map, but as soon as it goes to std map, something goes wrong

I'm hoping its not faulty Power FC but I guess if thats the case I can get a replacement. Have emailed Apexi USA about it so hopefully they have answers

Any help is much appreciated, its frustrating me quite alot at the moment, considering my ancient Power FC (V2.20E) doesnt have this problem and then new one does.

Have now tried unplugging VCT and going for a drive with no change (VCT plug is leaking oil, but its still clicking so sounds like its working)

unplugged the wtr temp sensors, gauge one made no difference (didnt expect it to) and ECU one just made it stick in Cold start

Does anyone know how to extract the information from the Power FC so you can view the coding, I've seen lines of code from power fc data before, but cant work out how to extract it at the moment, going to compare old with new to see if theres any answers in there.

I just had a thought and it may be a long shot but .

In one of the threads I think I mentioned that I set the 50c warm up setting to zero where the default is different .

Mine is not a fresh PFC but I can't remember what version it is .

It sounds like the thing is not coming out of "invisible learned idle mode" straight away and is retarding the ignition to pull what it thinks is a high idle back .

The only other thing I can think of is the scaling with Z32 AFMs may not be spot on at just off idle speeds .

A .

The Wtr Temp (Cool) settings are the same as the old unit. Set at 0 retard at 60+ degrees

I suppose I could try putting 1 degree retard in there to see if it just always runs 1 degree less then normal, and I can just bump all the cells up 1 degree. Its worth a try I guess

Comparing the two (old vs new) Power FC settings in FC-Edit there is no difference at all in the Air flow curves for the VG30 AFM. The only difference is the IGN vs TPS settings which apparently arent used in the older versions of FC edit. Besides all this, as far as I know its the TPS that tells the ECU to return to the Idle map when at closed throttle (and perhaps this is compared with engine RPM also)

Might try the Wtr temp cool vs IGN, retard it 1 degree at +60 and see what happens, but don't think its going to be the answer

Thanks for the idea though, I'm open to any suggestions at this point. Its a bit frustrating, Thinking I might have to send it to Apexi

No go on that, doesnt make a difference. It seems to work ok for the first minute or so, all gear changes seem ok, but then it starts after that. i've graphed it in FC Edit (chart) and the timing goes crazy when it does this. Have done some dodgy paint marking to show whats happening. Its got me a bit stuffed as to why the timing is jumping around like it is and then so smooth when the gear change is quick:

TimingJPEG.jpg

I hope this is just an isolated incident and not affecting all of the new Power FC's. Its bad news for me if so but good news for everyone else. Don't suppose anyone has a new one that can tell me if theirs does anything like this. Frustrating that everything is so good, and the car is running better then ever apart from this issue. It might not seem to bad, but you imagine making a snap decision at a roundabout to go through and then the car just goes nowhere for a moment, its not good :(

EDIT:

A thought has occured to me, am I running to much timing in the top row(s) (More then 40 degrees) and its cutting it back as a precautionary measure? I didn't think it did this but just a thought: UPDATE - No improvements as expected

Edited by 89CAL

What was wrong with your old Powerfc Cal?

Nothing at all really, its just (Im told) a really old version and is slow to write and read data, which I have noticed compared to the new one. The new one for whatever reason shows the car having less knock, I always knew I was getting false readings on the old one so thats a really good thing for me. It was basically just available at a good price and I thought I would update before mine decided to die. But in saying that its never showed signs of dying before.

I was trying to sell it but I may hang onto it for the moment till i can work out whats wrong with the new one

done about 3 or 4 with no issues, sounds odd but it may be a dud ecu rare but possible.

Where these all complete new tunes from scratch or was data bought across from older Power FC's? I think they will have been complete new tunes but just something else for me to think about. Might try and bring the old tune over to the new power FC with FC Pro. Don't expect to see any change but

Have you got a valid Vehicle speed signal on both PFC's.

Generally when you have delta idle ignition maps, you need to lockout their effect via either vehicle speed or rpm or both.

The logging I did with FC Pro shows both RPM and Speed about where they should be. Revs slowly rising and speed rising very slowly till the Timing returns to normal at which point it increases faster

O.K i have made some sort of progress on this. It's not giving me the answer but I have found some proof that of where the problem lies, here is the explaination I've just been writing:

So when lifting off the ECU should realise TPS is back to idle and initiate fuel cut to the determined point (As tuned, the F/C AC on and off) right. So I have a permanent wideband setup and driving around now I’m just noticing that its taking a little longer for it to realise the throttle is closed, it drops down in the 10’s:1 AFR momentarily before going right to max lean. Now on the old Power FC when lifting off it went quickly to full rich then quickly to full lean, which is to be expected. So the new Power FC isn’t making this transition as quickly for some reason. I think this is the root cause of the problem.

Also if I stay off the throttle (In this case lets assume im in second) until the F/C window is reached and it goes back to having a readable AFR (Not just off the scale lean) and I then put my foot down, no such problems, it takes off fine.

I'm wondering if its just the TPS or is it something in the ECU. It just seems strange that it works faultlessly on the old Power FC

BTW, since the last post I have:

Used FC Pro to pull the tune from my old Power FC, done a data init on the new one and put the new tune on it. Have completed the self learn idle again. No results

Pulled the bridged neutral switch in case it thought the car was always in neutral, no results

Awaiting a reply from Apexi america, hopefully they reply soon

I loaded the tune with FC-Pro but previously have done the data init and used the HC to just change the injector and AFM settings to go for a drive and see if it made a difference but it still had the problem then

The logs I have from FC-Pro show everything normal except for the timing, where it appears pretty much the same as the chart from FC edit above. FC-Pro is good for logging as it logs everything and you can select any point along the log and it tells you all values at that point

But it just isnt helping me at the moment :(

Logged a run with the old power FC and the only difference is there are voltages at the AN1 and AN3 points, but these have nothing to do with the Power FC when the FC-Hako is disconnected so I think thats a dead end

I pulled my TPS off and checked to make sure everything was working. And it looks like its 100% O.K

emailed APEXi Pacific before so hopefully get a response from them. At this point I just want to send it back for repairs/replacement

If it's commanding the low ignition values then it's software based; hence a software issue.

Hopefully it's an easy fix. Maybe it's something to do with how quick they allow the ignition to transition between commanded values....

A few of the high end ecu's like autronic can change how quickly ignition timing can be ramped in and out, wouldn't surprise me if PFC had similar background variables. This is usually only required on high compression engines where transient knock can be an issue.

If it's commanding the low ignition values then it's software based; hence a software issue.

Hopefully it's an easy fix. Maybe it's something to do with how quick they allow the ignition to transition between commanded values....

A few of the high end ecu's like autronic can change how quickly ignition timing can be ramped in and out, wouldn't surprise me if PFC had similar background variables. This is usually only required on high compression engines where transient knock can be an issue.

Best answer so far, Thank you :)

Makes sense

Just not sure why its occuring at the moment. Wonder if I will have to send it back or if they will give me the stuff to re-write software on it. I highly doubt that but

Appears to be all the time. I have loaded 2 different maps in there (albeit both maps from my car) and driven with data init performed and just the injector and AFM settings changed via hand controller just to get it moving. Havent got a reply from apexi yet. So think I try and contact Apexi america again and maybe get in touch with apexi japan

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

    • Any update on this one? did you manage to get it fixed?    i'm having the same issue with my r34 and i believe its to do with the smart entry (keyless) control module but cant be sure without forking out to get a replacement  
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
×
×
  • Create New...