crimson red

Hi, Everyone!! I'm crimson red.

This is my first post. I'm glad to join your community!!

Quick introduction: 2007 EvoX GSR 5MT(JSDM), INNOVATE LC-1 with an Analog Gauge, tactrix OpenPort2.0, and a WinXPSP3 in my Macbook(Boot Camp 2.1) for logging. Almost stock blue car.(in spite of my name.）

BTW, I have 2 questions.

First, I'm testing EvoScan 2.6 Alarms function.

1. I wrote 'knock alarm' formula(stock ECU knock count was up to 3):
([KnockSum] > 3)
It's simple and works well.

2. Then I wanted to detect A/F problems (for protect 4B11t), so I wrote as below:
([WideBandAF] > 0) and ([WideBandAF] > 15.0) and ([RPM] > 700) and ([APP] < 20.09)
[findings]
a. during fuel-cutting, WideBandAF returns 0.
b. no step on　accel pedal, APP returns 20.083.....

It isn't work well. the formula often returns True and Alarms!
Because WideBandAF often returns values over 15, 16, 20, and even 60 momently.

Anyone has idea??

Second, I want to know Alarm formula's grammar.
How many operators can be used? What priority do they have?
Are variable's types(i.e. real, integer, etc) different or every values have just double type?
When a Alarm became True value, can I direct some actions(e,g, insert a formatted message)?

Thanks!!

crimson red

After that I thought, during short time before and behind fuel cut, does a sensor return high A/F value ( ex. 16 / 17 / 18 etc) ?

Is my guess right?