paulr33
-
Posts
262 -
Joined
-
Last visited
-
Days Won
15
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by paulr33
-
-
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 ?
-
Haven't forgotten, I think I'm about half way through, just juggling work and uni priorities
-
ok thanks heaps, will try that. i dont have the head phones sorry, the knockblock i got was second hand and no headphones
-
hi all
i 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 sorry
im 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
-
- JMP, davidbek95, armin and 1 other
- 4
-
-
double checked a few things today and all the new sensors are working (oil temp, oil pressure and EGT) so that confirms my wiring map outs / pin outs are correct. engine light still stuck on, pressing E during car ON but engine not running reports nothing, if i do clear ecu fault codes the engine light flashes off and back on qiuckly, nothing in event viewer other than it saying ive cleared the errors. "run time stats" all looks good and no issues or anything that would make the engine light come on.
ill take it for a drive in an hour or so and do a PC log and see what i can find
-
The engine check light comes back, even after clearing the errors via "Clear ECU fault codes".
ill have to start it and see what it says
-
Thanks and yeah the engine light was originally on because the air temp sensor was unplugged but I fixed that , confirmed the sensor is working and also did clear error codes but it keeps coming back.
the only thing I haven't tried it starting the car and doing a full clear again.
-
thanks for your help, i will check it soon. the thing that doesnt make sense (if the above is root cause) is that its been like that for about 3 years now
no settings in the tune have changed. ive simply had the workshop run new wires to new unconfigured sensors
This is what they have done;
· Connect orange wire from Knock controller in globebox to pin 63 (AUX 3) on Vipec ECU loom
· Connect green wire from oil temp sensor to pin 96 (An Temp2) on Vipec ECU loom
· Connect ANALOG OUT wire from EGT controller sensor to pin 92 (An Volt1) on Vipec loom
· Connect blue wire from oil pressure sensor to white wire (An Volt 6) on expansion loom in glovebox
i have not yet configured any of those sensors and i also found the air temp (An temp 3) was unpluged, so ive fixed that (air temp working) but the engine light is still stuck on
is it because it can see voltage at one of the above sensors and because i havent configured anything its throwing on the engine light?
note this is for vipec v44 topboard for evo 9
-
hi all, hope you are all well. i am in the finishing stages of my can bus display and ive had my local workshop do some work for me (new senors added on). for some reason, my wideband is dead so ill need to spend some time working out why, but i cannot for the life of my make the engine check light go away. ive disabled wideband and also turned off stoich but its still stuck on. any help would be great?
logs and tune
http://www.paulr33.com/evo/help.zip
the only thing i can see in the logs is;AF6 - CE light
2 -
Hi All, I have my car back at home now, out of storage so I'll try and finish this project and document the whole build
- davidbek95 and JMP
- 2
-
thank you kindly good sir, ever so helpful and great software / ECU
-
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
-
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?
-
manated to find some info,
redarc oil temp sensor
http://www.tayao.com.tw/auto01.html
redarc oil pressure sensor
http://www.pressuresensorsuppliers.com/up/doc/58117025aff70.pdf
the oil pressure one was easy, but the temperature one is a tayao sensor, the markings on the sensor are TAYAO609 and it says -20 to 170deg but i cant find any voltage ramps etc
do i just assume -20 is 0v and 170deg is 5v ????
-
I've purchased redarc.com.au sensors for oil temp and oil pressure and ive been told these are direct plug and play into the vipec. I was expecting to see pin outs with the sensors and also voltage scales for the sensors, but the sensors didnt come with either. ive sent the supplier a note asking about this info but wondering if anyone else has used their sensors for inputs into the vipec? I am after the voltage scales for each sensor (oil temp and oil pressure) and also the pin outs so i know which is the signal wire etc.
Thanks and if I hear back from the vendor I will post the data up here
-
fyi another product that looks alright, looks like the KMS display
-
-
Yeah happy to release the code and write it up, just need to finish building. Car in storage for two months as we rebuild our garage then I can finish it
-
Ordered new oil temp, oil pressure and EGT sensors and will get these soon. Then I can wire into vipec and finish the display.
still on the todo list is to write up documentation and software code for this project
-
Hi jigga
with VTS you can open two copies simultaneously of VTS and have your old tune on the left and the new tune on the right. Double check each setting page to ensure they are the same.
-
Yeah I wanted to know that knock system is active (green box indicator) and also want to see how many times the vipec detects knock over the target value and cuts timing. Then I can sit at home analyse the logs and adjust the tune properly or diagnose cause of knock.
I'm used to the PFC style knock alert which flashes the engine light so I'll probably do this as well but it's nice to see how many times the target has been reached
-
this is where im upto with the current display. some minor changes, now includes oil temp, oil pressure and exhaust temp.
also included knock display status from the vipec and global knock triggered times # which reflects # of times vipec has trigger excessive knock and cut timing.i cant find a good symbol for pressure so i used *
I know this post is old. Any one here interested in showing their code? I just want to look at the interfaces and a overall board design so I can get a little feel for this. I am doing some basic with this but still have some stuff to do and other things.
hi,
The board design is a simple arduino Uno with two shields (CANBUS shield & 4d displays systems shield). No other changes are required to the board and these are off the shelf items.
the rest of the solution is simple arduino code to drive the CANBUS adapter and then display values on the 4d display.
happy to post my code when it's finished
EVO 8 V44 plugin - no knock or speed input?
in ViPEC V Series
Posted
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