paulr33

Can you use an accelerometer instead to detect lateral movement beyond a fixed value when standing still That’s what the Apexi RSM uses , a wired in g-sensor to detect when the car isn’t moving to trigger the “READY” sequence then any lateral movement starts the timer. You could use the same concept using a g-sensor

The factory 26 setup runs twin narrowband and its probably like that for a reason but I’m sure many have done single wideband after the dump pipe. Do you want to be able to independently tune the banks based on their AF/R’s , I.e if you see the last 3 last richer than the first 3 then yes you would need two seperate wideband sensors to give you that level of granularity input. Otherwise an average AF/R is probably ok. I’m sure there are wideband controllers that support dual inputs and provide dual 5v seperate signal outputs which is what you would need if you want to run dual wideband, plus don’t forget you’ll consume an additional analog input on your ECU input so check if you have enough spare inputs as well If in doubt check on skylinesaustralia.com someone would have done on there for sure

There’s no way to add them. The expansion kit supports but the main board doesn’t have the inputs so it doesn’t appear in the menu. V44 limitation. I’ve got the same problem, v44 on an evo 8 and ran out of inputs - even with the expansion loom

Make sure you check what ECU plug type you have in the car as some evo 8’s have 3 pin block and some have 4 pin blocks. For example, my evo 8 runs the evo 9 vipec because of the plug layout. I think it’s 3 pin blocks whereas the one you have is 4 pin blocks so check what your car has if it’s an evo 8

Hi team, I’ve noticed the v44 has its own global variables that are saved when the car is off. I.e engine starts, knock count etc. is there a way to make your own variable? i want to keep track off I/C spray run time, I.e how many seconds the I/C spray has been used for

What I did with my evo vipec v44 was u brought another v44 with a higher than 10,000 serial number and then sold my old unit on eBay. This saves you going without an ECU

I didn’t have any issues with speed and always had fast updates on my display. The problem with my setup was when I needed to change something on the display I had to put it all apart and plug it into the PC seperately to update the 4D systems screen and then the arduino code seperately and also the screen would drop out and flicker because the wiring was always loose from the plugs. The plex usdm is a commercial solution and I can change the scenes and layouts and customise to my hearts content while sitting in the car via USB on the side of the display.

Good work. I ended up going for a plex usdm but making the arduino CAN display did help me learn it all and how it works which was good fun

I still think you’ll find the tablet a half bake setup where to have to press buttons every time or wake it up each time or load software. Hope it all goes well but from making my own CAN display to using an as-built one (the plex uSDM) the commercial product is a million times better. Means I can focus more on tuning the car and not troubleshooting display issues

The problem you’ll find is that it will eventually cost you more in connectors and other bits and you’ll have to solve a heap of problems such as standby, powering on etc and customisation. i made my own CANBUS display thinking it was going to be cheap ended up about $300+ and it still had issues and the plex uSDM 102 is $750 AUD (non pro version) so stuffing around with a tablet or display is pointless. Have you tried reading data from a tablet at an angle in your car while driving? I bet you can’t even read it based on the angle and display type. just trying to save you from re-inventing the wheel

Plex usdm 102 and be done with it, no need for any displays or tricks. Just raw CAN and fully customisable. I did a thread on it the Vipec section

Thank you kindly

Is there a recommended rpm I should be travelling at when I do gear ratio calc in each gear? Evo 8 runs 6 speed close ratio and currently I get quiet a bit of “gear 0” in my logs. I’ll re do all calcs in every gear from scratch, I was thinking 3500rpm in every gear when I do calibrate ? also for the onboard boost control is there a specific solenoid you recommend? I have an eBoost2 and want to use per-gear control so can I re-use that solenoid or should I get a new Vipec compatible one? The wire to the ecu “aux 2” on my v44 evolution 9 is this a Switched ground to the solenoid?

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

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

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

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

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

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

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)

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

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?

Ok thanks, maybe I read it wrong and saw the other values to be multiplied by 5 in the help. All good thanks

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

took a while sorry, but finally have video