Author Topic: 1.1.81 bug  (Read 10075 times)

Offline Jamo

  • Full Member
  • ***
  • Posts: 129
  • BHP: 6
1.1.81 bug
« on: October 06, 2010, 07:26:47 pm »
I've found a problem with 1.1.81 can anybody else confirm this behaviour?

If you have a value in fuel added above egt setting, it's adds fuel no matter what the egt sensor value is.

on mine and another s2 members car it's caused the car lambda target to be mega-rich and car runs really bad.

change the setting to 0 and it runs fine.  my egt limit was 1000c and the sensor was reading 400 on idle but it still was adding fuel!

Offline Alx

  • Jr. Member
  • **
  • Posts: 3
  • BHP: 1
Re: 1.1.81 bug
« Reply #1 on: October 06, 2010, 08:08:10 pm »
No problems like that with mine. Works pretty well, actually, with fuel being added on or within a 15 degree interval around the set EGT limit.

Do you have a config/log file where the problem occurs.

Where did you put your EGT sensor? I placed mine in the opening for the CO measurement tube, i.e. just downstream of the turbo. It is actually in the flange that the turbo is bolted to. This made me wonder how much heat is lost through the turbo? You mention 1000 degrees - which I also consider a reasonable level, but I set the limit at 800, assuming that EGT drops about 200 on the way through the turbo. Do you think that is way off?

\Alex

Offline mattias

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1075
  • BHP: 41
    • Sävar Turbo Site
Re: 1.1.81 bug
« Reply #2 on: October 10, 2010, 11:03:48 pm »
Datalog, or it didnt' happen.

Offline Jamo

  • Full Member
  • ***
  • Posts: 129
  • BHP: 6
Re: 1.1.81 bug
« Reply #3 on: October 11, 2010, 12:48:57 am »
I had to downgrade back to 1.1.74 as the car was unusable.

When I test upgrade next week if it reoccurs I'll datalog log it

My EGT sensor is in the turbo hotside next to the flange hence the higher egt limit

Offline ranz

  • Full Member
  • ***
  • Posts: 137
  • BHP: 6
Re: 1.1.81 bug
« Reply #4 on: October 15, 2010, 08:13:32 am »
Tested it also, no problem with it, below EGT limit I changed it to 0 and back to 30, no change on lambda reading.

Offline Jamo

  • Full Member
  • ***
  • Posts: 129
  • BHP: 6
Re: 1.1.81 bug
« Reply #5 on: October 15, 2010, 02:40:46 pm »
might wait to see what's in 1.1.82 settled on 1.1.74 for the moment as the car is nice on it

Offline Denmark

  • Hero Member
  • *****
  • Posts: 542
  • BHP: 7
Re: 1.1.81 bug
« Reply #6 on: October 30, 2010, 06:13:54 pm »
I also have problems with 1.1.81, when using the subaru trigger.

When cranking the rpm goes to 20-30000 rpm, the same does the rpmcounter in the speedo(not good),
This does not happen with 1.1.76 fw,

But it relates to a problem in the fw, that change with the cranking treeshold set in vemstune, its when crossing that treeshold the rpm goes nuts


Hope it gets corrected some time, as i belive its the same for all other setups, its just more eacy to see with the subaru trigger,

it can be seen if the trigger signals are tested with a stimulatorboard, to feed the different triggersignals.


/Skassa
working on the boxer

Offline billman

  • Full Member
  • ***
  • Posts: 223
  • BHP: 2
Re: 1.1.81 bug
« Reply #7 on: October 30, 2010, 11:29:25 pm »
I also have problems with 1.1.81, when using the subaru trigger.

When cranking the rpm goes to 20-30000 rpm.

Don't know the rpm but the same happens with my rpm gauge also (audi rs2)

Offline Kenny Watson

  • Jr. Member
  • **
  • Posts: 44
  • BHP: 3
Re: 1.1.81 bug
« Reply #8 on: October 31, 2010, 08:21:44 am »
I get rpm blips during cranking as well (60-2 with VR sensor).

Just a bit of trigger noise I think. Doesn't seem to affect starting/running at all so it doesn't bother me, personally.

I like 1.1.81.... :)

Offline AVP

  • Hero Member
  • *****
  • Posts: 743
  • BHP: 11
Re: 1.1.81 bug
« Reply #9 on: October 31, 2010, 08:32:37 am »
i occasionaly get those with 1.1.27. I dont think it has to do with the specific 1.1.81 firmware