Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by fiestacosworth

  1. The ecu has been fitted to the car for a wile and had another engine previous. This statistics are old. It hasn’t made that rpm or air temp or map with us running it. No trigger errors at all. Very confusing.
  2. Map limit is set to 320kpa. Map sensor is built in on board 4 bar that comes on the link xtream ecu. Not tried a manual controller no as we have control. Just can’t go over 1.1 bar of boost or it’s like there is a cut. But there are no limits set that low.
  3. Ok. So had some time on this evo today. And done a few changes. Changed the dwell of the coils to 2.5ms. Set the gearchange duty cycle table to 0. Checked the fuel pressure and fitted new plugs gapped to 0.5mm. All ok and running well.... however. Now if we try and adjust the boost up the car has the same problem that it had before of that bogging down and cutting. We cannot get it to run anymore than 1.1 bar or boost. It made good power at this. However cannot work out why we cannot run anymore boost. Fuel and ignition are good. Why can we not run anymore boost ? I have attached a photo of t
  4. The guy bought the car with the ecu fitted. And a blown engine. He supplied a new engine turbo etc and we installed in. It is annoying that lambda isn’t on there or fuel pressure. However when on the dyno we are running a wideband so can see what it’s doing and it’s ok. I do agree I need to perform a fuel pressure test to be sure it’s ok. When it happens the lambda reading goes rich - lean - rich - lean and then carry’s on smooth. Also we have 0 trigger errors so I ruled that out.
  5. I understand that. However this makes sense as to why we have no boost control. Any ideas yourself of what it could be causing the issue ?
  6. Ahh ok! So it’s applying 100% wastegate duty cycle all the time. Regardless of wastgate table! This could well be the issue! Why the hell would it be set to that as standard. We don’t have the gears wired in. So I can set this to 0 and just use the wastgate table.
  7. Ok so fuel starvation. I will hook up a fuel pressure gauge and check it. Customer told me it has a walbro unrated pump in there. But needs checking. I also read somewhere last night that the evos have a restrictor on the return line in the tank and it messes up the fuel pressure. So will have to check that also.
  8. Hi thanks for your reply. So you was receiving low fuel pressure at this point due to the pump ? I have not removed the pump to check it what was the issue with your pump ?
  9. Hi Adam. Sorry forgot to mention that. The engine fitted is an evo 8 “block and head” have tried the trigger settings on both 1-6 and 7-9 and it’s exactly the same.
  10. Hi guys we have a evo 4 at work that has a weird issue that i just cant seem to find. the car has a link g4 plugin ecu. its a built motor etc gt45 turbo. loaded up base map and just checking basics ie injectors and coils boost solenoid valve etc all working ok. car starts and runs ok good idle. run it on the dyno to set up the fueling all fine. until it hits 4000rpm. and then the car just splutters like its hitting a limit of some sort. if i attempt a power run it starts fine then as soon as it hits 4000 the power just drops off does the splutter business and then builds up again. its not miss
  11. The vehicle has an apexi soloniod. Looks identical to a Mac valve. Can check what is connected to NC AND NO tomorrow tho.
  12. Hi guys got a customers car at work that we have just built the engine for. It’s a evo 4. Running a link g4 plugin ecu. Turbo is a gtx35. With tial external waste gate and 3 port boost controller. Engine is fully built etc. The car starts and runs fine. Some fine tuning needed but no real problems. The problems come when boosting! So I had it on the dyno setting the fuelling sites and then as it got onto boost it’s like it his it’s map limit and just stuttered. Until I let off. So I tested the boost solenoid and it is clicking fine. So checked the boost control table again and had it set ok.
  13. hi guys i have a log attached of my car idleing. want some advice please. the car idles rough and jumps all over the place. mechanicalt it is fine i just cant seem to figure out why it wont idle smooth! the engine is a built cosworth yb engine. siemens dekka 875cc injectors. coil on plug conversion. bd14 inlet and exhaust cams 8.1 compression ratio. link monsoon ecu. just want it to idle smooth but its all over the place! help please! rough idle.zip
  14. For anyone who has this same issue. i cut the live wire feed for thr can lambda and run a new wire direct from the battery and it works perfectly thanks adam.
  15. hi. so my can lambda running on my monsoon ecu was working fine. was running a log and it just stopped reading! so run a log to record it and i am getting error 16 heated too long. also error 33 open circuit APE-IPE and 34 open circuit RE-IPE and its cycling between these 3 faults. can anbody shed any light on what is going on here!! i have checked the sensor and the wiring visually and everything looks good. no loose wires pins etc any help would be much appreciated! thanks. luke. Log 2018-10-21 12;22;31 pm.llg
  16. Hi just wanted someone to advise me if they think my car is safe to drive to the dyno. thats about 20 miles on the motorway so no real load. I have mad a very rough map. it does run quite well etc but want some opinions. the engine is a 4 cylinder cosworth engine running on pump fuel "supreme" 80lb injectors. t35 turbo link monsoon ecu. I also don't have any knock detection equipment. or I would tune it myself on the road. cosworth map.pclr 30 may log 1.llg
  17. Yes let me emphasis that is tried to calibrate the sensor as I didn’t know if it had just fallen out of sync. I wired the car and had zero issues. I just wanted my suspicion confirmed that the sensor has failed! So that obviously won’t help with the running
  18. Hi I actually did as you suggest. And the settings are 0v low error and 5v high error. I had the computer connected with the ignition on and unplugged the TPS and it dropped to 0.02v. That’s what lead me to believe it’s either “stuck” on full throttle inside the sensor. Or it’s shorting straight to earth inside the sensor ? Only confusing thing is that on the throttle graph it shows 0.0% throttle all the time. As you can see on the log. If it was stuck at 5v surely it would be stuck at 100% throttle ?
  19. I did have a little look today and didn’t see anything obvious with the wiring. But I will have a better look when I have more time. I will also get the map up aswell
  20. Hi. Looking for some info. All was ok Cosworth YB engine TPS was fine. Not been near the car for a month or so. Now have a fault with the tp main reading 4.99v constantly ? And it doesn’t register anything when I press the accelerator I have tried calibration but makes no difference. I’m guess that the TPS is faulty ? Next the car is running extremely lumpy. I have uploaded a log. Can anyone see anything obvious? Thanks. 30 may log.llg
  21. It’s strange because the time I run it before I logged it the trigger count stayed at zero and didn’t go up. Then the time I logged it it turned over a bit error count went up then it started.
  22. Map sensor is built into the ecu. Monsoon ecu. And it’s plumbed from the plenum straight to the ecu. I set up log and seletced select all.. I thought that would have put everything in. Will have to do another one tomorrow now.
  23. Ok so removed a tooth from a spare dizzy I had and fitted it to try the way you guys are saying. I also sorted the charging issue. Although I forgot to hook it up for the log!! DOHH!! However still reading 12.5v etc. So logged it and it runs very lumpy and then for no reason on its own just went really lean and cut out please see the attached log and advise. Thanks! new log fiesta cosworth.llg
  24. Thanks for the replies. I will remove one of the teeth on the phase. I will turn the engine over by hand until the gap on the crank pulley is lined up with the sensor and then remove the phase tooth that is furthest away from the phase sensor ? Or just remove either one ? Is that correct ? And will also sort the changing issue out too and then perform another log and see how it goes.
  25. So that would explain the misfire/spit I get every 3 - 5 seconds on idle ? Ok so either put the standard pulley back on the crank. Or chop a tooth off the phase? Anything else you can see in my log and map that might be messing things up simon ? And any idea why my lambda is cutting out like that ?
  • Create New...