Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by richardpalinkas

  1. I have already tested the spring pressure as this is the only way for me to road tune without wheel spin in 2nd gear, then put back in my higher boost and check on 3rd gear on the highway. Lambda is the same boost varying. Will check the cam overlap and see how that affects it
  2. So more data logging/ adjusting and what I have done seems to have solved the issue. I found dead times for my injectors, so to start with I started from scratch. Put in the newly acquired dead times which were quite a bit bigger than id1000 or the data that was in the vehicle, which resulted in a steeper low slope, high slope was similar to what I had with the old injectors. But random lean under low rpm and off throttle is now next to gone. however... with both sets of injector data I also have an issue which I can’t seem to resolve. At wot, as the boost curve comes up to max boost, approx 3500rpm, my fuel is always richer than my commanded lambda table. After this period, maybe to about 4000-4500rpm, fuel is back to commanded lambda and holds steady until redline. But rich wise, if I’m commanding 0.75 lambda, it goes to about 0.72 lambda, then comes to my desired fuel map. ideas? thanks
  3. I’ll try to increase the min pulse width and see how it goes. How large a value can you go before going too far? I’ve seen most inj min pulsewidths 0.272 but factory injectors run at 0.9, just so I know if it’s getting too much. il check what the o2 sensor is doing. Wideband is mounted in the rear o2 sensor port just after the cat. I haven’t been logging ltft yet as I’ve been mainly looking at the wideband and disabling ltft. Also can you log ltft with pcmtec ? I’ve been having to log with for scan the ltft car drives fine, I just hate looking at the wideband when it’s anything above 1. Gets me worried, even though I know on decel it’s probably not hurting anything
  4. Have a question regarding scaling injectors, just fitted a walbro 525 and fuel pressure reg to my car, set base pressure at 4 bar as required, injectors are a bit of an unknown so I’m working off what the data was previously in the car, but what I am experiencing is good cruising afr on wideband, almost spot on under wot to redline, but I get a lean spike under decel, which I have decel fuel cut disabled. It’s not all the time, but if I’m coasting along, lambda is 1, but if I apply throttle, say 25% and come off throttle, I get 1.15lambda that slowly creeps back down to 1. Under all cruising I’m sitting close to commanded, maybe slightly rich. That being said, it did the same before upgrading fuel pump from 460 to the 525, dead times are the same, injectors I believe are sonic performance 1000cc. The sonic performance offset table is a lot different to the offset that was originally in my car. Can offset cause the random lean out under some decel applications?
  5. If the switch is disabled then the vehicle runs when its disconnected. I learnt that when I disconnected it due to causing throttle opening on cruising speeds, so I had to disable it so I could still drive the car. Was very annoying driving as if your stalling up everywhere you stopped
  6. That is a possibility. Will obviously need wiring extended to relocate also.
  7. Yea I’m pretty confident in that the boost sensor is faulty as I am getting a boost pressure sensor correlation fault code since replacing the sensor with a pat version. reason I am wondering about the need for the sensor is that if it’s only useful for closed loop boost control, which mine is already tuned for, I would like to eliminate the sensor so that I can eliminate the throttle body elbow and blow off valve port and just have a silicone 90 deg bend from throttle body to intercooler pipe instead of the factory plastic pipe.
  8. Ok. My car is tuned in open loop anyways so it should be all ok to disable then without causing other issues with drivability?
  9. what is the purpose of the boost pressure sensor in the intercooler pipe? pre throttle body (fg falcon on the 90 deg bend just at the throttle body) im getting intermittent boost surge under load (not reaching boost target) as well as intermittent boost spiking (overshooting to 25psi, commanding 18psi) since fitting an aftermarket boost pressure sensor when the original one failed. there is a scaler to disable the boost pressure sensor if need be, but just wanted to check how important this sensor is as the manifold already has a map sensor
  10. in regards to this, if we change the values to say 1 in all instances, would that mean that the cylinder cut would be quite short?
  11. Just to update, if you modify the idle spark tables (normally have values of 60deg) it will change the idle spark value. Say if you set it to 10 deg, it will command 10 deg and adjust throttle to keep it at 10 deg idle spark
  12. on the topic of timing maps, what is better. i already have my high load borderline knock timing pretty good, but regarding blk lambda correction, would it be better to leave it 0 or reapply the lambda correction table, and adjust the borderline knock table (as in minus at given load and commanded lambda the relevant spark adder) to suit, so that the spark will be optimised for the lamda correction values? or is it a 6 to one half dozen to the other situation?
  13. that is true. would love a dyno and endless hours, id be on it everyday to steady state tune if i could. but surely someone has done it or at least done a haltech and transferred over the data from that as you could steady state tune quite quickly
  14. mainly this part of the map that i am trying to fine tune. as you can see if i were to work with the factory map for my vehicle, thats quite aggressive compared to the other 2, by far. the other 2 maps are a lot less aggressive but also have larger turbos, which i would have thought less heat, less chance of detonation, and more chance of advancing timing closer to mbt
  15. I'm just trying to fine tune the transition parts of the map. Wot load and timing seems pretty happy with no if not much knock retard (less than 1deg)
  16. Cheers for that. My current setup is a pte6235, so slightly bigger then the f6 and sprint file. Currently is around the 400rwkw mark. Peak load around 2.2, but steady around 2.1 load Also having said that, all spark adders and modifiers between all 3 maps are the same. Hence my confusion why such a drastic difference between all 3 BLK maps.
  17. ive been looking at the stock spark maps for an fg xr6 turbo, f6 and sprint. ive reinterpolated all axis for the spark tables so that i can compare them, but im a bit confused as to the reasoning behind why ford have done what they have done... as you can see, the xr6t has a far more aggressive spark map, compared to the f6, and the sprint is even more sedate in terms of spark calibration. now when trying to build from a map and modify, which spark map is a better platform to work with? does the lower spark in some lower load cells help turbo spool as seen in the f6 and sprint? xr6t f6 sprint
  18. In regards to the sprint MBT tables, reason for asking whether being able to use them or stick with the stock ones is that the sprint uses the same engine as the xr6t, but with the f6 turbo, so essentially if running a turbo similar size to that of a gt3582 with the same compression ratio of the engine, would it be more accurate?
  19. Cheers. I've had a read through those threads. They are a good read.
  20. How does ford calculate MBT timing from factory? Is it based off race fuel at a certain temperature? With ethanol unlikely to reach knock in lower loads (0-1.5 loads etc) should we be aiming to achieve MBT in our borderline knock table, obviously logging knock retard to make sure it's all ok? Also with running a bigger turbo than standard (FG xr) is it better to use MBT calibrations from the vehicle it is designed for or to use one say from an f6 or sprint that have the higher loads already and reinterpolated to suit any load scale adjustments?
  21. When are you expecting histograms to be available? Very keen to look at if there's beta versions
  22. Trying to find a catch code for a fgx g6e turbo, but the tear tag is not working EAJA ER2G-14C20A-AJA SOFTWARE code. 2015 fgx 6cyl turbo
  23. have removed the rear o2 sensor to put in place a wideband. what scalers need to be adjusted to stop the engine light coming on?
  24. That's a fair reply. It's working great nevertheless. Keep it up 👌
  • Create New...