paulr33

i think i recall reading somwhere that you cant use the CANBUS and CANBUSF cable at the same time? on my vipec i have the CANUSB permentantly connected for when i want to use and use the laptop so when i use my display unit will i have to reach into the VIPEC and swap the connectors each time? or is this where the CANEXSTENION comes into play so that the connector can sit in the glovebox for example? i dont mind if I can only use one, just want the connector in the glovebox as the evo ECU is behind the dash

thanks, but they dont list the CANF part on their site, can i special order it somehow?

i found two of the parts at carmodsaustralia.com.au; CAN to Jst Connector (200mm CAN cable for plug in ECU's) Expansion Loom (G4 Plug-In XS Loom for auxiliary sensors/inputs) but I cant find the CANPCB module??? actually sorry, the CANPCB is the first item, its called a CAN to JST connector.... actually thats all i need, ill order these from carmodsaustralia.com - can you just confirm that expansion loom will plug onto the VIPEC board?

hi scott can i order these online from linkecu.com or via sales email ? id also like the expansion connector too please

If I mange to find a v44 plugin with a serial Ove 10,000 is it ready to go with CANBUS other than needing the right CANBUS plugs?

the screen is about credit card sized so ideal for the dashboard

this is what my friend is going to build for me obviously made up using dummy #'s and bullshit data so far

until im able to wire in the aux input can i wire up a dummy knock led instead? at least that way i have working knock indication even if the ECU doesnt have it

Thanks and I see the error in what I have done. I don't do any wiring works on my ECU as its too fiddle so it won't be wired in until September when it goes in for next service. is the link box expecting to see ground signal on that wire? Can I just hardwire it to ground (the orange "window in" wire so that the knock box will still work? Obviously during the entire RPM range

see below latest tune with DI5 off and also the PC logs and screenshots, not sure if its any different. I did a store, then started the engine so DI5 should definetly be set to OFF now http://www.paulr33.com/evo/knock2.zip Thanks

Thanks, will try this tonight

Thanks scott, is this not something I can apply myself, i.e a simple firmware .bin reflash??? Saves me sending the ECU to NZ and back, don't want the ECU to be lost in the post

Hi Simon, Thanks for your detailed help and I did this on the weekend and it looks like ive got the knock box setup properly. I set the gain to 0 then revved to 3500rpm and kept increasing gain until i saw around 1.5vs on the analogue output wire, from memory the gain is set to 2. then i set the filter frequency to C which is 13khz and that all appeared OK. I then set the knock system active and all the attributes / trim settings as per the two above screen shots. these saved and commited Ok and no issues. With the engine running on the vipec "run time values" and on the "DI input tab" I can see "D1 - Digital KNOCK feedback Active" flashing in green but on the far right panel "KNOCK" under "Knock Sys Status" it says ERR - DI KNK .... I can get a screen shot of the error. Is there a way to debug the input from the knock box, I.e can i add a manual voltage watch on DI1 to see if its actually sending some sort of voltage? Below is current tune and logs if this helps http://www.paulr33.com/evo/knock.zip

hi, any update RE: costs to "CAN BUS Upgrade" a V44 ECU?

Hi David, Is there anywhere in Melbourne that can perform this or do I have to post the ECU to cairns?? Also can you supply the other CAN BUS parts that I need when performing the CANBUS modification on my Vipec V44 to suit Evo 9? 1 x CAN-PCB connector (from us) 1 x CAN-F connector (from us) Can you please PM me total price for this including return postage to Melbourne

I have a friend at work helping me, who has done heaps of electrical engineering and has done adruino's before etc so he is well equipped I think first we will do the setup in the first post using the ardruino and the LCD display and then once it all works, we will tackle if we can make a CANBUS pass through box to feed the KMS display manipulated CANBUS packets from the VIPEC so the KMS display shows them correctly. This saves me selling my ecu and buying a Link G4

thanks and good insight, i hadn't considered using the aurdrino as in inbetween CANBUS gate to the KMS display, i only thought of it as a do it yourself display. ill chat to my friend tomorrow to see if he can get the audrino as a CANBUS gate to the KMS display

100% keen to try this instead

hi, this looks great and a bridge gap between a full CANBUS setup like the KMS display or display dashes etc would this work with the V44 topboard I have (evo 9 PNP unit), but it still requires the CANBUS upgrade (serial below 10,000) if i wanted the KMS display unit i had to upgrade to Link G4 and then but the KMS display, but this looks like it might work with native V44 CANBUS - as the audrino can do arithmetic on the CANBUS values

Hi all, Turned the boost up recently to 24psi, all OK but up a hill in 3rd gear, full load and bang some sort of misfire / detonation so i backed off instantly. thought i had blown the motor but everything was OK and car drove fine after it etc. it looks like ive hit some sort of fuel cut but my data logs (10hz samples), the values for MAP are close the limit, but dont hit the limit. the vipec software, as i was actively logging when it happened displayed "map limit activated" after the event, so it sounds like map limit. the map limit table is 300kpa all the way through (28.8 psi) and in my logs i can see a few logs of 288 kpa (27psi) at the most, so just shy of the map limit is it simply approaching the map limit, and there' some sort of pre-emptive cut or its simply my logging samples arent quick enough to catch it i would have expected to find some sort of "map limit reached" flag in the logs, but cant see any?

Thanks, very helpful

hi sorry for 8000 questions. looking at logs, trying to view some data where the vipec is using and actively doing closed loop, in the logs i can see three meaningful columns; Lambda Fuel Corr. Lambda Status 1 An V4 - WideBand i can see fuel corr. looks like a % number or some sort of floating # and it appears to be how much fuel the vipec is trimming, which is great to see. but what is the significance of lambda status, in the logs i can see it being numbers of 5, 6,7 14. for numbers around 7 and 14 thats when it looks like its running in closed loop. what do the status numbers mean? i tried to find it in the documentation but couldnt see anything sorry.

I adjusted the map lockout value 120 and set the trim max to 15%. I can see the vipec trying to bend the AFRs at idle but only gets to around low13s which is good enough. I even checked the target table and it should aim for 14.7. All good either way. Thanks for your help

Have working closed loop feedback (stoich) mode and it's working really well. My sensor wasn't calibrated properly before so that's why I had screwy voltages for the AFRs. All working well now and it's very responsive. One thing I can't work out is why I have 12.1 AFR idle. It seems the wideband closed loop won't bend it back to 14.7. The Ftrim limit is on 8%. Looking at the Maps and ghost trace I can't see any reason why it's so rich at idle. Should I adjust the Ftrim? Manual says 15% as a suggestion but mine is set to 8% (was default)

ok thanks, didnt really check how detailed the initial configuration requirements were. will plan to do in the next few days