Here is the core summary of the ​**​"If Alarm" and "But Not"​**​ parameters in the Artisan alarm system, covering their definitions, workings, application scenarios, combined logic, and key considerations

[Terracotta-6]

​I. Core Definitions & Purpose​

​Parameter​	​Essential Function​	​Value Rules​	​Logical Relationship​
​If Alarm​	Sets a ​prerequisite dependent alarm​	0: No dependency, triggers independently n(another alarm ID): Depends on alarm ID n	The current alarm ​only becomes active​ after the dependent alarm triggers
​But Not​	Sets an ​exclusion alarm​	0: No exclusion m(another alarm ID): Disables current alarm if mtriggers	If the exclusion alarm triggers, the current alarm is ​permanently disabled​

---

​II. Detailed Working Mechanism​

1. ​If Alarm (Dependency Logic)​​

   • ​Activation Condition: The system only starts checking the current alarm's conditions (time/temperature) _after_the specified prerequisite alarm (e.g., n) has triggered.

   • ​Trigger Order: The dependent alarm's (n) trigger is a ​necessary but not sufficient condition​ (e.g., if Bdepends on A, and Anever triggers, then Bnever activates).

   • ​Typical Scenarios:

     • Preventing false triggers in initial cooling phase (depends on a "Cooling Temp > 40°C" marker alarm).

     • Delaying an action (e.g., "adjust damper 30 seconds after First Crack", depends on a First Crack marker alarm).

2. ​But Not (Exclusion Logic)​​

   • ​Disable Condition: If the specified exclusion alarm (e.g., m) triggers, the current alarm is ​skipped entirely and permanently, regardless of whether its conditions are met.

   • ​Irreversibility: Once the exclusion alarm triggers, the current alarm is ​permanently disabled​ for the roast (even if conditions later match).

   • ​Typical Scenarios:

     • Disabling automatic power adjustments after Second Crack (exclude a Second Crack marker alarm).

     • Disabling automatic operations after manual intervention (e.g., exclude a "Manual Damper Adjust" marker alarm).

---

​III. Typical Application Scenarios​

​Scenario 1: Basic Alarm Chain (Prevent False Trigger)​​

​Alarm​	​Condition​	​If Alarm​	​But Not​	​Action​	​Purpose​
Alarm 1	ET > 40°C	0	0	None (Marker)	Confirm cooler is active
Alarm 2	ET < 35°C	1	0	Start COOL	​Only active after Alarm 1 triggers, prevents room temp false triggers

​Scenario 2: Delayed Action Post-Event​

​Alarm​	​Condition​	​If Alarm​	​From​	​Action​	​Purpose​
Alarm 1	BT > 155°C (FC)	0	Dry End	None (Marks time T0)	Mark start of First Crack
Alarm 2	Time = 0:30	1	If Alarm	Fan to 40%	​Executes 30 seconds after T0​

​Scenario 3: Conflict Avoidance (Disable adjustment after SC)​​

​Alarm​	​Condition​	​If Alarm​	​But Not​	​Action​	​Purpose​
Alarm 3	BT > 175°C (SC)	0	0	None (Marker)	Mark start of Second Crack
Alarm 4	BT > 180°C	0	3	Power to 50%	​Never activates if Alarm 3 has triggered​

---

​IV. Combined Logic: Dependency + Exclusion​

​Case: Adjust fan 1 minute after First Crack, but prohibit adjustment if Second Crack occurs.

Alarm A (Mark FC): BT > 155°C, From=Dry End, If Alarm=0
Alarm B (Mark SC): BT > 175°C, If Alarm=0
Alarm C (Target Action):
  - Time=1:00 (1 min after FC)
  - From=If Alarm (Base time is A's trigger time)
  - If Alarm=A (Depends on FC mark)
  - But Not=B (Disabled if SC occurs)
  - Action: Fan to 60%

​Logic Chain:

A triggers → Allows C to check conditions → If B not triggered → C triggers 1 min after A

If B triggers → C is permanently disabled

---

​V. Key Considerations (Pitfalls to Avoid)​​

1. ​ID Accuracy:

   • Must reference ​existing alarm IDs​ (check first column of alarm table), names are invalid.

   • Incorrect IDs cause dependency/exclusion to fail (system defaults to no dependency/exclusion).

2. ​Trigger Order is Critical:

   • If Bdepends on A(If Alarm=A), A​must trigger before B's conditions are met, otherwise Bnever activates.

   • If Cexcludes D(But Not=D), Cis ​immediately and permanently disabled​ after Dtriggers.

3. ​Synergy with FromParameter:

   • If Alarmcontrols ​​"when the alarm activates"​, Fromcontrols ​​"during which roast phase it is active"​​ or its time reference.

   • If Bdepends on A(If Alarm=A), and A's From=CHARGE, then B's Fromcan often be set to If Alarm(it doesn't need the phase restriction again).

4. ​Avoid Circular Dependencies:

   • Avoid dead loops like A depends on B, B depends on A(neither can trigger).

5. ​Leveraging Manual Intervention:

   • Use the ​​"Event to Alarm"​​ function (e.g., button click) to generate an exclusion marker, enabling semi-automatic control (e.g., disable automatic logic after manual adjustment).

---

​VI. Core Value Summary​

​Parameter​	​Problem Solved​	​Contribution to Automation​
​If Alarm​	​​"When is this alarm allowed to become active?"​​	Builds alarm chains, ensures sequential operation (e.g., staged cooling, post-event actions).
​But Not​	​​"When must this alarm be prohibited from activating?"​​	Avoids logical conflicts, enhances stability (e.g., disabling non-essential actions in critical phases).

​Combined Use: Elevates Artisan alarms from ​simple conditional triggers​ to an ​intelligent, multi-condition rule system, enabling:

✅ ​False trigger prevention​ (e.g., initial cooling phase)

✅ ​Phased operations​ (e.g., adjust damper after First Crack)

✅ ​Conflict avoidance​ (e.g., no power adjustments after Second Crack)

✅ ​Human-machine collaboration​ (pausing automation after manual intervention)

​Configuration Advice: Diagram the dependency/exclusion relationships between alarms (e.g., A → allows B; C → prohibits B) before setting parameters to significantly reduce logic errors.

[Terracotta-6]

Artisan 警报系统中 ​​"If Alarm" 和 "But Not" 参数的核心内容总结，涵盖其定义、工作机制、应用场景、组合逻辑及关键注意事项：

---

​一、核心定义与作用​

​参数​	​本质作用​	​取值规则​	​逻辑关系​
​If Alarm​	设置前置依赖警报​	0：无依赖，独立触发 n（其他警报编号）：依赖编号 n的警报触发	当前警报仅在依赖警报触发后才可能生效​
​But Not​	设置排除警报​	0：无排除 m（其他警报编号）：若 m触发则禁用当前警报	若排除警报已触发，​当前警报永久失效​

---

​二、工作机制详解​

1. ​If Alarm（依赖逻辑）​​

   • ​激活条件​：仅当指定编号的警报（如 n）已触发时，系统才开始检测当前警报的条件（时间/温度）。

   • ​触发顺序​：依赖警报（n）的触发是必要非充分条件​（如 B依赖 A，A未触发则 B永不生效）。

   • ​典型场景​：

     • 防止冷却初始阶段误触发（依赖“冷却温>40℃”标记警报）。

     • 延后操作（如“一爆后30秒调风门”，依赖一爆标记警报）。

2. ​But Not（排除逻辑）​​

   • ​禁用条件​：若指定编号的警报（如 m）已触发，无论当前警报条件是否满足，​均直接跳过检测。

   • ​不可逆性​：排除警报触发后，当前警报永久失效​（即使后续条件满足）。

   • ​典型场景​：

     • 二爆后禁止自动调功率（排除二爆标记警报）。

     • 手动干预后禁用自动操作（如排除“手动调风门”标记警报）。

---

​三、典型应用场景​

​场景 1：基础警报链（防误触发）​​

​警报​	​条件​	​If Alarm​	​But Not​	​动作​	​作用​
警报 1	冷却温 > 40℃	0	0	空（标记）	确认冷却器已进入工作状态
警报 2	冷却温 < 35℃	1	0	启动 COOL	​仅在警报1触发后生效，避免室温误触发

​场景 2：事件延后操作​

​警报​	​条件​	​If Alarm​	​From​	​动作​	​作用​
警报 1	BT > 155℃ (一爆)	0	Dry End	空（标记时间T0）	标记一爆开始时间
警报 2	Time = 0:30	1	If Alarm	风扇调至 40%	​在T0+30秒后执行​

​场景 3：冲突规避（二爆后禁用调整）​​

​警报​	​条件​	​If Alarm​	​But Not​	​动作​	​作用​
警报 3	BT > 175℃ (二爆)	0	0	空（标记）	标记二爆开始
警报 4	BT > 180℃	0	3	功率调至 50%	​若二爆已触发，则永不生效​

---

​四、组合逻辑：依赖 + 排除​

​案例​：一爆后1分钟调风扇，但二爆后禁止调整，且仅在脱水后生效。

警报 A（标记一爆）: BT > 155℃, From=Dry End, If Alarm=0  
警报 B（标记二爆）: BT > 175℃, If Alarm=0  
警报 C（目标动作）:  
  - Time=1:00（一爆后1分钟）  
  - From=If Alarm（基准为A的触发时间）  
  - If Alarm=A（依赖一爆标记）  
  - But Not=B（二爆后禁用）  
  - 动作：风扇调至60%

​逻辑链​：

A触发 → 允许C检测条件 → 若B未触发 → C在A触发后1分钟生效

若B触发 → C永久失效

---

​五、关键注意事项（避坑指南）​​

1. ​编号准确性​：

   • 必须引用已存在的警报编号​（在警报表格第一列查看），名称无效。

   • 错误编号会导致依赖/排除失效（系统默认为无依赖/无排除）。

2. ​触发顺序不可逆​：

   • 若 B依赖 A（If Alarm=A），则 A​必须在B条件满足前触发，否则 B永不生效。

   • 若 C排除 D（But Not=D），D触发后 C​立即永久失效。

3. ​与 From参数的协同​：

   • If Alarm控制 ​​“何时激活警报”​，From控制 ​​“在哪个烘焙阶段生效”​。

   • 若 B依赖 A（If Alarm=A），且 A的 From=CHARGE，则 B的 From可设为 Start（无需重复限制阶段）。

4. ​禁止循环依赖​：

   • 避免 A 依赖 B，B 依赖 A的死循环（两者均无法触发）。

5. ​手动干预的转化​：

   • 通过 ​​“事件转警报”​​ 功能（如点击按钮）生成排除标记，实现半自动化控制（如手动调风门后禁用自动逻辑）。

---

​六、核心价值总结​

​参数​	​解决的问题​	​对自动化流程的贡献​
​If Alarm​	​​“何时允许警报生效”​​	构建警报链，确保操作按顺序执行（如冷却分阶段、事件延后）。
​But Not​	​​“何时禁止警报生效”​​	规避逻辑冲突，提升稳定性（如关键阶段禁用非必要操作）。

​二者结合​：使 Artisan 警报从 ​单一条件触发​ 升级为 ​多条件联动的智能规则系统，实现：

✅ ​防误触发​（如冷却初始阶段）

✅ ​阶段化操作​（如一爆后调风门）

✅ ​冲突规避​（如二爆后禁调功率）

✅ ​人机协同​（手动干预后暂停自动化）

​配置建议​：用流程图梳理警报间的依赖/排除关系（如 A→允许B；C→禁止B），再对应设置参数，可大幅降低逻辑错误率。