paulr33 Posted October 31, 2016 Author Report Share Posted October 31, 2016 thanks scott, but all good, the vendor has provided the voltage / ohms table as per below.im going to wire this sensor into AN Temp 2 but the plug has two wires??? which wire goes where? does black run to ground and green run to An Temp 2 on the vipec loom? Sensor calculator.pdf Sensor calculator.pdf Quote Link to comment Share on other sites More sharing options...
Scott Posted November 1, 2016 Report Share Posted November 1, 2016 Hi Paul, On the temp sensor one wire will go to Analog Temp 2, the other will go to sensor ground. It doesn't matter which pin goes to where.Scott Quote Link to comment Share on other sites More sharing options...
paulr33 Posted November 1, 2016 Author Report Share Posted November 1, 2016 thanks another crazy tuning question theory sorry, the turbo im about to fit, HKS recommend to not exceeed 900deg EGT. I have an EGT controller to wire into An Volt 1 and ill configure An Volt 1 as EGT 0-5v.i was thinking of using 4d fuel and 4d IGN map to deal with timing and fuel adjustments if EGT is over 900deg but was wondering if theres a way to do fuel cut - like when i get map limit exceeded, but via an EGT value?otherwise, if i go via the 4d map functions - can you see any issues with this approach Quote Link to comment Share on other sites More sharing options...
Scott Posted November 1, 2016 Report Share Posted November 1, 2016 Hi Paul,If you have one available you could consider using one of the GP Limit tables to control max engine speed based upon the EGT, you can set these to cut fuel.Scott Quote Link to comment Share on other sites More sharing options...
paulr33 Posted November 1, 2016 Author Report Share Posted November 1, 2016 thank you kindly good sir, ever so helpful and great software / ECU Quote Link to comment Share on other sites More sharing options...
paulr33 Posted March 11, 2017 Author Report Share Posted March 11, 2017 (edited) hi alli never got around to making my knock box work as the last issue i had was the AUX window wasnt wired into the vipec.recently had some work done and i got my workshop to wire in the AUX window to the vipec from the knock block.i still dont get any knock values whatsoever and the logs show no knock values or counts even when the knockblock is in test mode. the knockblock manual says it should flash when in test mode, but mine doesnt flash, the blue light remains constant. even if i have it in "test mode" - both dials on F and F and turning the unit on and off i never see any status change or values on the vipec logs or display for knock. logging with test mode yields no knock values either. am i doing something wrong or expecting something i shouldnt be? at a dead loss here sorryim certain its configured correctly and wired in properly, normally i have it on 2 and C. keen to hear if anyone has this box working ? attached is current tune, logs and photo of knock block normal settings, but even on F and F "test mode" i dont get any values evo_knock.zip Edited March 11, 2017 by paulr33 Quote Link to comment Share on other sites More sharing options...
Adamw Posted March 11, 2017 Report Share Posted March 11, 2017 The only setting I see wrong in your config is the pull-up is turned on on DI1, this should be off for the Knockblock. If you plug head phones in to the knock block do you hear engine noise? Quote Link to comment Share on other sites More sharing options...
paulr33 Posted March 11, 2017 Author Report Share Posted March 11, 2017 ok thanks heaps, will try that. i dont have the head phones sorry, the knockblock i got was second hand and no headphones Quote Link to comment Share on other sites More sharing options...
paulr33 Posted April 24, 2017 Author Report Share Posted April 24, 2017 hi all, i have the knock block finally working and i have working knock input. i have the knockblock set to gain 2 and filter C on the box and basically any amount of driving, regardless of how hard i drive the car the knock level goes crazy and the ecu basically thinks there is heaps of knock. is the gain too high ? should i try a gain of 1 or 0 ? Quote Link to comment Share on other sites More sharing options...
Adamw Posted April 24, 2017 Report Share Posted April 24, 2017 In PC link, have you set up the individual cylinder knock gains and the target table etc? Quote Link to comment Share on other sites More sharing options...
paulr33 Posted May 22, 2017 Author Report Share Posted May 22, 2017 All sorted, this is how it's intended to work and the I've realised I now need to set the knock target map. So having knock values all over the place isn't an issue, it's only as useful as a correctly configured knock target map Quote Link to comment Share on other sites More sharing options...
paulr33 Posted July 9, 2017 Author Report Share Posted July 9, 2017 hi allif i am driving and put the clutch in at around 20km/h i get this excessive and recursive idle hunt sequence, when the engine tries to idle, and basically hunts its ass off between 2000rpm and 1500rpm in constantly cycle.it looks like this in the logs; i did some more digging in the logs and found im triggering overrun fuel cut, so if i overlap overrun fuel cut on the engine speed plot, we get this view;basically the engine is trying to idle, trips over run fuel cut and then runs in a cyclic idle hunt - drives me nuts when im trying to coast down my street quietly and this 2.3L evo is hunts its ass off between 2000rpm and 1500rpm.so question - is overrun fuel cut the cause of the hunting or is it simply a control mechanism and something else needs to be adjusted? did some reading and understand the intent of overrun fuel cut - maybe i just try disabling it?its based on deactivation RPM and is targetted at 1600rpm at 80deg water temp (the above example) i also have an issue where hot start works first shot, runs for 2 seconds then blips and almost stalls and recovers, incredibly annoying...from the help; Startup Step - Provides increased air bypass for starting. Startup step decays as over a period of three seconds after RPM is detected. In Closed Loop ISC control mode this is a temperature dependant table.my ISC mode is set to closed loop/sol stepperstartup step is on with +20 for 80deg water temp (this log)idle rpm target is 1000rpm at 80deg water tempthe logs show it can hold idle, its only when i tries to lower it, that it just stalls rapidly2.3L with big cams, map sensor etcshould i just increase idle rpm to about 1100rpm and see how that fares? Quote Link to comment Share on other sites More sharing options...
Adamw Posted July 10, 2017 Report Share Posted July 10, 2017 Turn off decel fuel cut for now. For idle speed control you need to fully tune it in open loop mode so that the base position table is close to correct before switching over to closed loop mode.Do this first: Then do this: Quote Link to comment Share on other sites More sharing options...
paulr33 Posted July 23, 2017 Author Report Share Posted July 23, 2017 Overrun fuel cut off and that has fixed the cyclic idle so all good, but I will still do a complete default set of idle control to ensure everything is perfect thanks for your help Quote Link to comment Share on other sites More sharing options...
paulr33 Posted December 28, 2017 Author Report Share Posted December 28, 2017 On 10/07/2017 at 4:47 PM, Adamw said: urn off decel fuel cut for now. For idle speed control you need to fully tune it in open loop mode so that the base position table is close to correct before switching over to closed loop mode. Do this first: FYI just wanted to say thanks for your help with the idle control open loop help, i did this yesterday on my evo with stroker kit, big cams and balance shaft delete so the idle is mega lumpy and following your steps the idle is now a lot better, more stable and predictable and hot start is also prefectly (previously would stall almost every time) Quote Link to comment Share on other sites More sharing options...
paulr33 Posted April 2, 2018 Author Report Share Posted April 2, 2018 i think i have picked up a bad batch of fuel and im now getting some knocking levels previously unseen for my car. i have the ECU setup as follows; what i was hoping for was the vipec to cut ign timing across the whole tune if it picked up knock and not just the individual cell on the tune. i want it to be a bit more failsafe instead of just retarding that cell momentarily (for upto 25sec (Advance delay)) and leave it like that - even when keyd' off. i thought setting "Clear i-trim tables" to OFF would allow me to do this, but the tables are always 0's - both Cyl #1 and #2 - i think its because advance delay is 1s, but the most i can set this to is 25seconds. is there a way to make it cut timing on the whole tune map when it detects KNOCK > KNOCK THRESHOLD (poor mans failsafe)? Quote Link to comment Share on other sites More sharing options...
paulr33 Posted April 9, 2018 Author Report Share Posted April 9, 2018 Anyone else have any ideas what I’m doing wrong? Is there a way to make knock adjustments permanent (with key off) Quote Link to comment Share on other sites More sharing options...
Adamw Posted April 12, 2018 Report Share Posted April 12, 2018 Sorry I missed your earlier post. If you want the whole operating range to be retarded rather than just a specific cell, then you just change the ign trim table axes so that there is only one cell to adjust. Example below. For it to "start up safe", then you turn off "clear I-trim tables". manually put some retard in the I-trim table, then do a store before powering off. The ECU will then always start off with full retard applied and only advance up if it doesnt detect knock for the advance delay time out. Quote Link to comment Share on other sites More sharing options...
paulr33 Posted February 15, 2019 Author Report Share Posted February 15, 2019 noticed a strange issue where in the CAN channel config if i enable knock level global, knock threshold and knock counter cyl #1 all in the same stream the knock level global is no longer required to be multiplied by 5. that is, the number that comes out in the knock level global packet is the actual correct value and doesnt need * 5 to display the correct value, but only after i enabled the other two CAN channel items. Vipec 9 PnP, Firmware 4.10.2 Not urgent just an odd issue i found Quote Link to comment Share on other sites More sharing options...
Adamw Posted February 15, 2019 Report Share Posted February 15, 2019 12 hours ago, paulr33 said: noticed a strange issue where in the CAN channel config if i enable knock level global, knock threshold and knock counter cyl #1 all in the same stream the knock level global is no longer required to be multiplied by 5. that is, the number that comes out in the knock level global packet is the actual correct value and doesnt need * 5 to display the correct value, but only after i enabled the other two CAN channel items. Vipec 9 PnP, Firmware 4.10.2 Not urgent just an odd issue i found As far as I know "knock level global" has never had a multiplier of 5. It is a 16bit value so the full 1000 counts can fit. It is only the individual cylinder knock levels that are shortened to 8bit to save space (only allows 255 counts) so they need a multiplier of 5 to so that they can be displayed as 0-1000. Quote Link to comment Share on other sites More sharing options...
paulr33 Posted February 15, 2019 Author Report Share Posted February 15, 2019 Ok thanks, maybe I read it wrong and saw the other values to be multiplied by 5 in the help. All good thanks Quote Link to comment Share on other sites More sharing options...
paulr33 Posted March 9, 2019 Author Report Share Posted March 9, 2019 Hi all, Can anyone show me what their knock level global values look like? i am curious what other data logs look like for this type of data set as mine doesnt make sense. the values are all over the place. i know my engine is noisey as its a 4g63 stroker with balance shaft delete but the values go from 0 to 800 to 400 to low numbers etc. i checked the values in the log and the values on the chart are all in the "knock window " range. See below graph Left is RPM in blue Right is knock level global in red The concern i have is that the data pattern looks like knock, i.e going from low levels of engine noise to excessively high noise quickly which is what knock patterns look like. so i use the data set to fine tune the knock targets but i just end continually increasing the knock target values each time higher and higher. This is 4g63 stroker kit, balance shaft delete, external "link knockblock" with factory knock sensor and Vipec v44 evo 9 model. i can attach the tune and logs if this helps but more curious on what do other knock level patterns look like. why isnt it linear with engine load / peak torque instead of see saw'ing between values? Quote Link to comment Share on other sites More sharing options...
paulr33 Posted March 9, 2019 Author Report Share Posted March 9, 2019 is it the knock block noise cancelling mode that is causing that see-saw affect of the knock "level"? my box is set to FREQ level C and gain is 2 which im certains is for evo lancer 13khz with noise cancelling Quote Link to comment Share on other sites More sharing options...
Adamw Posted March 11, 2019 Report Share Posted March 11, 2019 Can you attach the actual log file and tune. Quote Link to comment Share on other sites More sharing options...
paulr33 Posted March 11, 2019 Author Report Share Posted March 11, 2019 see attached tune and .log file. see these section times section time 694.9 in the log section time 922.8 in the log tune.zip Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.