Jump to content


Photo

Racelogic Traction Control


  • Please log in to reply
203 replies to this topic

#201 techieboy

techieboy

    Supercharger of Doom

  • 22,914 posts
  • Gender:Male
  • Location:Bedford

Posted 25 February 2014 - 09:50 PM

Luckily I have the dutch software so can disable if needed, but that's blind luck Surely if triggering a misfire EML was a material issue, it would be well known by now..?   There are enough people using it..?

I'm only aware of one Z22SE (standard NA) car that has it fitted and he certainly suffers with an EML whenever it cuts in. Presumably less of an issue on the pig iron cars or their ECU is more forgiving of misfires.  

My info came from CS just not compatible with Klassen VX220 2.2 soft ware at present no crank senor delete :blush:

Huh? Why would you have a crank sensor delete? That's fairly fundamental to the functioning of the engine. :o

#202 cs_

cs_

    Member

  • Pip
  • 213 posts
  • Gender:Male
  • Location:Berlin (Germany)
  • Interests:fast lightweight cars
    computers
    music
    home & family

Posted 26 February 2014 - 06:59 AM

That's true, operating the TC on a Z22SE will trigger EML if the TC cuts in several times, even if there is some time between the events. It seems that the Z22SE ECU remembers previous ignition fails at least for some time, accumulates them and at a certain summed up limit triggers the limp home mode with EML activated. Can be bad if you drive slalom.

 

As for the Z20LET ECU things are a lot better, it triggers EML only at very hard misuses of the throttle with TC cutting in very hard. And it does not remember earlier ignition fails. So if you want to trigger the EML you can do it by trying to do donuts with the TC on. And you can avoid it by lifting the throttle a bit if you feel/hear the TC starts working. This is the normal driving style you should use if you have the TC to help you in unwanted situations, react to it.

You can reduce the propability of EML by altering the cut sequences in the TC setup in a way, that every cylinder will have at least one proper ignition cycle on a regular base. The standard Racelogic TC setup is far but optimal for that. Did that modification of the programming for myself and that helped reducing the limp homes to a minimum. If you use my setup file for the Speedster/VX220 you will also have these altered cut sequences.

Furthermore a diff lock helps a lot. For all the time since I dropped in the Quaife I had not one EML / limp home anymore! You just cannot spin the wheels hard enough anymore that the TC has to cut almost any ignition cycle as it can happen with standard diff.

 

In general the TC is no good for posing, so doing burnouts and producing lots of burned rubber and ignition cut sounds is probably a good way to pick some chicks, but also to get the EML coming up fast. If you take the TC for a more offensive driving style on track or to enhance the safety while passing other cars you will not encounter EML. So keep that in mind please.

 

 



#203 siztenboots

siztenboots

    RaceMode

  • 26,614 posts
  • Gender:Not Telling
  • Location:Surrey
  • Interests:french maids

Posted 26 February 2014 - 02:02 PM

Motronic misfire Statistics, Fault processing: Within an interval of 1,000 crankshaft revolutions, the detected number of misfiring events is totalled for each cylinder. If the sum of cylinder fault counters exceeds a predetermined value, a fault code for emission relevant misfiring is preliminary stored after completion of the first interval after engine has been started or the forth interval during a driving cycle where misfire has been detected. In the case of misfire detection for one cylinder, the fault is determined by a cylinder selective fault code otherwise the fault code for multiple misfire will be stored additionally. Within an interval of 200 crankshaft revolutions, the detected numbers of misfire events is weighted and totalled for each cylinder. The weighting factor is determined by a load/speed dependent map. If the sum of cylinder fault counters exceeds a predetermined value, the fault code for indicating catalyst damage relevant misfiring is stored and the MIL is illuminated with "on/off"-sequence once per second (blinking). In case of misfire detection for one cylinder the fault is determined by a cylinder selective fault code otherwise the fault code for multiple misfiring will be stored additionally. If catalyst damaging misfire does not occur any longer during the first driving cycle, the MIL will return to the previous status of activation (e.g. MIL off) and will remain illuminated continuously during all subsequent driving cycles if catalyst related misfire is detected again. However all misfire events where the catalyst can be damaged are indicated by a blinking MIL. If catalyst damage is not detected under similar conditions in the subsequent driving cycle the temporary fault code will be deleted. In the case of catalyst related misfire, the Lambda closed loop system is switched to open-loop condition according to the basic air/fuel ratio calculation (Lambda=1). All misfire counters are reset after each interval.

#204 Kieran McC

Kieran McC

    Scary Internerd

  • PipPipPipPipPipPip
  • 3,416 posts
  • Gender:Male
  • Location:Norwich
  • Interests:Fast cars,Track Days.

Posted 26 February 2014 - 02:25 PM

 

Luckily I have the dutch software so can disable if needed, but that's blind luck Surely if triggering a misfire EML was a material issue, it would be well known by now..?   There are enough people using it..?

I'm only aware of one Z22SE (standard NA) car that has it fitted and he certainly suffers with an EML whenever it cuts in. Presumably less of an issue on the pig iron cars or their ECU is more forgiving of misfires.  

My info came from CS just not compatible with Klassen VX220 2.2 soft ware at present no crank senor delete :blush:

Huh? Why would you have a crank sensor delete? That's fairly fundamental to the functioning of the engine.

 

Saab LSJ 2.0 L running VX220 2.2 CS soft ware has caused a EML problems its down to the fake crank censor readings






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users