digger

i have an issue where if the engine is cold and start the engine straightaway it acts as if the ICV is not working the only way ive overcome this is i put the ignition on for a few seconds to "prime" the system (i.e allow the the valve to move to correct position i assume it doesn happen instantly )then turn key to the cranking/starter position and it starts beautifully and functions as per expected. i dont actually know if it is an ICV issue but its a theory of mine. i could just check the valve position but ive never gotten around to it

bmw e30 with m20 engine

I thought I should reply to this given I’ve sorted my issues. When you disconnect the sensor and multimeter across the 5V sensor supply pin and ground there needs to be 5V. There is also 5V across signal wire and ground as well. This measn two compibantions of pins should give 5V when the circuit is unloaded (i.e. no sensor plugged in) When you plug the sensor in the 5v and ground should remain at 5V but the load of the sensor will pull the voltage between signal and ground down to typically 0.5V at 0 tps and 4.5V at WOT (depending on sensor etc). My issue was that I didn’t have the 5V supply only the 5V signal when the sensor was unplugged, being unware that I should get 5V across two pins (the internet failed to provide answers) I was confusing the two. It still functions with the 5V supply but poorly. The root cause was that WOLF routed the 5V supply to a different pin when they made the plug and play harness. I believe this to be an error.

hi, i am trying to verify the wiring of my TPS. If i disconnect the TPS harness from the TPS itself and use a multimeter to probe across the signal pin and ground pin on harness side should i get 5V with ignition on? Note that I’m talking with the sensor unplugged, when it’s plugged in i get 0.9V closed throttle and 2.15V WOT across the signal and ground. This is a very small range between 0 and 100% throttle which is what im troubleshooting. Can anyone confirm that what I am seeing is correct with the wolf v500? i think this is correct but want to check with other users Thanks

i have a naturally aspirated engine running ALpha N setup but currently not using the internal map sensor to compensate for ambient pressure due to altitude change etc how do you do this?

I currently have a couple of those cheap ceramic ones which i have had for quite a few years and have been looking to upgrade to some MetalCat ones. Are 100 cell cats likely to out perform 200 cell cats given the METALCAT 2.25" 100cell flow 640CFM and the 2.25" 200cell flows 540CFM which is almost 20% more, but in flow only. Is this likely to make any performance gain on moderately tuned NA engine (stroked, bored, high compression, cammed, ported, V500 ecu etc, etc cheers

i sent my ECU down to wolf to get the WB firmware (or whatever was required) and i still can't get my Wolf to read the AFR and i am using everything from Wolf e.g techedge stuff latest software and had it installed as per wolf recommendations.

Speaking about logging data has anyone been able import the log file into excel to very that what is being logged is correct? For example when i log a start the delivered fuel and timing does not match what it should as set out in the map unless i misunderstand how starting fuel is calculated. Same as at idle when i look at rpm, temp and other corrections to try and predict what the delivered fuel and timing should be it doesn't add up! Plus mine doesn't even registed enrichment but clearly enrichment is delivered based on varying response of the engine when enrichment is altered.

If Braap or anyone wants V75, or V77 Pm me your email. I got my ECU back after upgrading the firmware to support WB but logging still doesn't work properly. I am using V77 , when i look at the datalog tab on the v500 software the oxy1-V seems to vary erratically but the AFR1 is a constant at 16 so its not using the calibration function at all. Then when i open the file in Excel and it reads a constant 0 AFR1 and the OXYV1 are different from whats displayed within the wolf software and off what i think it should be for the AFR i am getting. I have a digital gauge that came with the techedge that i know reads reasonable just it doesn't log anything, so i will know when the wolf is reading properly. I haven't tried V75, V74 or V73 yet with my new firmware so thats the next step

Got my ECU back with original trigger setup and its back to normal. I do get an occasional noise event when the engine cranks but its a single event only and doesn't happen every time i start and is not detectable other than looking at the laptop.

I am confused are you still getting problems? Wolf suggested in my case putting a 1k resistor across two of the pins A27 and A28 iirc otherwise they said sent it back and they put the trigger board back to what it was.

I am using a plugnplay system for a BMW M20 I6 with a 60-2 wheel, reluctor type sensor and a single channel igniter. Does anyone know where i can find a good explanation of how the triggering system works specifically what REF and SYNC are?

i am using a plug and play setup so it uses the original harness and sensors all i did was plug it back in. Even when i slowly rev it happens and its all the time and it doesn't want to pass through it at all. What do you mean by power off reset? I Was using H/W RevA F/W 5.02 now i'm using H/W Rev A 22nf F/W 5.04

I just got my V500 back from melbourne after sending it to be upgraded to be able to use Wideband. So i started it up and seemed to idle as usual but when i try and go past 2000rpm there is a misfire and the V500 starts counting noise events and syncx events. Before i sent it down there were no issues, all i wanted was to be able to use the WB facility now it won't run properly:mad: Its the wrong time here to contact Wolf over the phone it'll have to wait a while so does anybody know what could cause this? Does it definitely seem like a ECU problem given its counting noise,syncx? Cheers

I got my techedge WB wired in and setup exactly as the guys at WOLF said but i don't get any AFR on my laptop and consequently can't log anything......i spoke to the WOLF support guys and now i am waiting for them to confirm that my firmware Rev5.02 doesn't have WB capabilities so i can send it in to be upgraded. I have also noticed that my ENRICH always reads 0 on the laptop even though its enabled. The engine responds to changes when i alter the transients though. Anyone else had this problem?

I spoke to Steve from Wolf and he said i don't need to upgrade the firmware unless i want to run two WB units or use a new function that can lock the Map so it can't be edited without entering a code. He said i should be able to log AFR with what i have and the latest verison of the software. He did email me the latest PC software V5.00.75 which has the modified WB setup features but is not on the website yet. If anyone wants 5.00.75 that hasn't got it they can PM me their email.

So does that mean the V2 has different software that is not yet on the website? Are there any other differences beside the WB issue?

Thanks Bo I only bought the techedge unit 2 weeks ago and they never mentioned a thing about upgrading. It looks like Ron and yourself are saying that they supply a techedge unit for free? Hopefully its not the same controller i just paid for!! It looks like i'll have to give them a call and see what they say and if i need to send it to them its not too inconvenient for me i am only interstate. Regarding sensor calibration curve did you just use one of the Aux inputs and associated input calibration table? There is a Lambda 1/2 in the sensor setup but the calibration is merely a single integer. So i am not sure where to put the voltage vs AFR calibration table/curve.

Does anyone know when V2 was made available? I bought mine from WOLF in Early Nov07 so does that mean i am V2 or V1? Does anyone use the techedge 2J1 WB unit with LSU4 sensor with the V500? Cheers