Jump to content

Fraser

Members
  • Content Count

    12
  • Joined

  • Last visited

About Fraser

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    United Kingdom

Recent Profile Visitors

169 profile views
  1. Fraser

    Renault trigger signal/polarity issue (now resolved)

    I now have this running beautifully smooth. No more hunting, spitting and stumbling. Thanks for the help. Fraser
  2. Fraser

    Renault trigger signal/polarity issue (now resolved)

    Fair point. I will try the map changes soon and let you know. Just my luck that it actually ran decent....with wrong polarity, and trigger pattern! or i'd have changed it earlier. Next time the engine is out i'll swap the flywheels back and try. why is the amplitude so much greater with the reversed polarity?
  3. Fraser

    Renault trigger signal/polarity issue (now resolved)

    Adam, I followed the help note in the Link manual which advised i had to machine off the double high tooth to a conventional 60-2 arrangement. See me do this here.. I really wanted to keep the trigger un touched so i could use the OE ECU. that's pretty annoying if i didnt have to do that as i cant swap back now without swapping the flywheel... That aside, if the trig pattern is changed to multi/missing 60-2 i should be ok? Will try today (UK) and report back Cheers, Fraser
  4. Fraser

    Renault trigger signal/polarity issue (now resolved)

    As requested. File names are self explanatory. cheers, Fraser really good kangoo.pclr trigger play inverted wiring..pclr
  5. Fraser

    Renault trigger signal/polarity issue (now resolved)

    Simon. No cam trig used. Engine ran great for months apart from a wandering idle which i was puting down to the inverted crank signal causing the ecu not trigger on the right edge. Since ive tried to get it to run 'right' ive ran into these problems. If i swap it back, it runs fine. Cheers Fraser
  6. Fraser

    Renault trigger signal/polarity issue (now resolved)

    Gents, thanks for the feedback. sorry for the delayed reply. Flat battery, frosty weather, kids...etc... just having a go just now. swapped the wires on the pickup and no RPM sig and no noticeable trigger on the pclink scope. dropped the arming threshold as low as i could and got it to register on the scope - showing a now correct polarity (attached). but i still see no RPM sig. this is a fully charged battery running at normal crank speed. for some reason there is a marked loss of power generated from the pickup when the wires are inverted. what to do now? cheers, Fraser
  7. Can someone confirm that the attached trigger trace is the WRONG polarity? It goes negative as the tooth approaches which would tell me it's wrong, but if i swap the 2 cores over, it wont start at all. Is there a way in software to invert it or can anyone explain why it wont fire when its physically swapped? Sensor is an OE Renault crank sensor and plug. Fraser
  8. Fraser

    Thunder e-throttle closed-loop idle (now resolved)

    Made the changes as suggested and idle control burst into life. Thanks for the help. I doubt i would have found that one myself!
  9. Fraser

    Thunder e-throttle closed-loop idle (now resolved)

    Thanks for the reply. I thought it was something stupid i had missed. I will give it a try in a couple of days and let you know. Fraser
  10. Fraser

    Thunder e-throttle closed-loop idle (now resolved)

    Adam, See a selection of logs and map attached cheers, Fraser Log 2018-03-25 7;21;47 pm.llg idle log.llg Log 2018-03-25 7;21;16 pm.llg
  11. Fraser

    Thunder e-throttle closed-loop idle (now resolved)

    Thanks for the reply. Ive not selected a drive speed lockout so i assumed the road speed was not required. Surely i dont need to install road speed feedback to get it to idle?
  12. Hi folks. First time Link user here and ive had no issues tuning with it so far. Trying to polish up the details now but i'm really struggling to get the closed loop idle control working after so many attempts. 'Idle status' always shows 'speed NOT selected' The ethrottle target is always 'table 1' surely this should change to ethrottle target at some point? The ethrottle target table 1 is set to '0' at closed throttle and base idle position is '2.5' to give an idle speed of 1k rpm. No amount of increasing or reducing the error by altering the idle setpoint will make it respond or 'control' All it will do is perform a % increase when the coolat fan comes on, and it jumps to this setting with no issues. How does it know whether or not to look at table 1 in an idle condition? Would uploading a short log file help work out whats going on or are there specific settings i should check? The help file doesnt have a lot of detail on this topic. Cheers!
×