Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by paulr33

  1. ok ive found the issue, its how its calculating per cyclinder and the overall aggregate, see below. it says global level is 0 but it shows numbers per cyclinder still ill do some work on this tonight and see what the issue is, thanks for your help
  2. see attach 40hz log from my car tonight. the log data pattern for knock follows engine load so i think the sensor is working, but again it still shows the data pattern where in one cell its 0 knock level then the next cell its almost at the max range, i.e Section time: 98.225 - knock level global: 0 Section time: 98.25 - knock level global: 620 Thanks for your help Log 22-03-19 9;03;34 pm.zip
  3. thanks , i think i have a better picture of it now, so basically log at the highest possible rate (40hz) then use that to build a knock map of what the engine looks like under good health without detonation
  4. Out of curiosity I tried gain level 2 but with noise cancellation and the level appeared the same so I’ll just disable knock control
  5. from the manual Later model vehicles (2000 onwards) may have difficultly operating with the Internal knock detection circuitry. This is due to the use of "2nd Harmonic" knock sensors that some manufactures are factory fitting. There are two solutions to this problem: 1. Contact your nearest Vi-PEC dealer for the purchase of an after-market knock sensor. I am trying to use the factory 4g63 sensor but happy to replace with an aftermarket unit if someone can tell me what sensor will work with the link knockblock and what sensor settings to select on the box, i.e FREQ setting
  6. 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
  7. before changing anything i would look at the idle control setup and idle functions. the online help covers how to set up "closed loop" idle control, do this first and then when its stable check out open loop idle control. from memory on a turbo engine, map is the recommended axis (again check the help online in VTS or link software)
  8. 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
  9. 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?
  10. Ok thanks, maybe I read it wrong and saw the other values to be multiplied by 5 in the help. All good thanks
  11. 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
  12. took a while sorry, but finally have video
  13. i run innovate LC2 and it works great for wideband input and wideband closed loop on v44
  14. made some good progress tonight. a few values to out how they are displayed, but working with the vipec v44 correctly.
  15. The Vipec v44 and possibly other models require math computation on some of the values so they are displayed properly, so for example temperature is offset by +50 so you need to tell the display this logic otherwise your airtemp will show as 80deg when it’s actually 30. the plex uSDM 102 Pro does this via a feature “math channels” but the function is used for more advanced logic such as showing average of two sensors, using cosine, log etc I.e averages of two EGT probes to be shown as a single value or used for alarms on the display. The software for the plex uSDM 100 and 102 Pro both allow the user to configure an “offset” for every sensor value in the CAN packet so you can say airtemp is airtemp with an offset of -50 thereby solving the wrong values issue. the offset feature is different to the “math channels” so it looks like on the 100 Pro you can run this on a Vipec v44 and use the offsets to do all the calculations and therefore you don’t HAVE to buy the 102 pro version purely for the “math channels” function. in summary you can go for the cheaper option if required. Wish I had of known that when I ordered mine
  16. Hi All, Thread for setup guide of the plex uSDM 102 Pro CAN display on the Vipec v44. My display should arrive this week so I’ll post up info and details on getting this working on a Vipec v44 (my model is Evo 9 topboard PnP).
  17. I’ve purchased a plex usdm 102 pro CAN display so I will post up some info once I have it working etc
  18. sorry its locked, there is no place in 2018 for locked tunes. make sure you tell all your friends the workshop does this. its a beginners trap if you arent advised upfront and find its locked later. can you still read logs off the ECU when its locked? you could reverse look at the logs to see how its tuned etc.....
  19. good choice, ive got an evo 8 FQ with v44 vipec, keen to see your ride
  20. Thanks and all, just couldn’t work out why they opt to use serial instead of native CAN. Maybe they just assume every v44 isn’t compatible based on the 10,000 serial # issue?
  21. hi all considering a commercial off the shelf replacement screen, namely the PLX SDM 102 pro here; https://www.plex-tuning.com/product/plex-%ce%bcsdm-102-pro/ The tech manual states to connect it to the Vipec V44 via Serial TX/RX but the product states it supports CAN but they dont use it on the V44? The I44/i88 refer to connecting it via CAN. Is there a reason for this? I dont want to run it via serial
  22. There are plenty of off-the-shelf CAN displays out there. Have you looked at these? Not cheap but will do what you want. They aren’t cheap because of the design and R&D work they have had to put into each product but will do what u want without hacking tablets etc
  23. Anyone else have any ideas what I’m doing wrong? Is there a way to make knock adjustments permanent (with key off)
  24. 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)?
  • Create New...