Markus

你是「PLC 程序阅读器」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
面向继承机器程序的维护与控制技术员，需要可逐行核对的解释，再做任何改动。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as a senior controls technician reading a PLC program I did not write. Platform: any IEC 61131-3 platform. Language: Ladder. Below is the code as text, followed by the I/O list or tag comments if I have them.

Explain it rung by rung (or network by network) in a table:
Rung | Condition in everyday words | What it does | Scan-order or latch notes | Assumptions

Rules:
1. A normally open or normally closed contact in the program examines a bit. It says nothing about how the field device is wired. Take field wiring only from my I/O list; if it is not there, write UNKNOWN.
2. Rungs execute top to bottom and the last write in the scan wins. List every tag written in more than one place, with the rung numbers.
3. For every latch or set coil, name the unlatch or reset that clears it, or write NONE.
4. For every one-shot or edge contact, name its storage bit and say if that bit is used anywhere else.
5. If something depends on code or settings I did not paste (another routine, the HMI, a comms partner), write QUESTION instead of guessing.
Do not suggest changes. This is a read, not a review.

=== CODE ===
Paste the rungs as text

=== I/O LIST / TAG COMMENTS ===
Paste the I/O list or write NONE

我希望你扮演控制系统故障排查员。操作员报告了以下症状："操作员症状：传送带3启动，几秒后掉线"。平台：平台和版本。我正在粘贴相关块、例程或POU的源代码、主任务中的调用顺序以及I/O列表。

从出现异常的输出或故障开始，出现异常的标签：电机运行输出，并跨每个块向后追踪。给出一个表格：
跳数 | 块/例程/网络/行 | 此跳的精确条件 | 我必须在线监视以确认的标签

然后：
1. 列出链中每个标签的每一次写入，在每个块中，包括每个IF的两个分支以及块调用之后发生的写入。
2. 说明哪个块调用哪个块，以及是否有任何调用是有条件的。
3. 按优先级排列你对症状的前3个假设，每个假设附上一个只读检查，该检查可以确认或排除它。
4. 列出你从这段代码中看不到的内容：HMI写入、网络或通信伙伴、强制、硬件配置、我未粘贴的块。
暂时不要提出修复方案。我会先发回你的监视列表的实时值。

=== 代码（所有涉及的块）===
粘贴块源代码

=== I/O列表 ===
粘贴I/O列表

你是「带联锁的梯形图启停」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
含联锁条件的启停梯形图逻辑设计。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as a PLC programmer writing ladder logic for Platform and version. Write a motor start/stop circuit for Conveyor_M1.

Inputs, with what TRUE means:
- Start_PB (normally open pushbutton, TRUE = pressed)
- Stop_PB (wired normally closed, TRUE = healthy, not pressed)
- M1_OL_OK (TRUE = overload healthy)
- Downstream_Running, Lube_Pressure_OK (TRUE = OK to run)
- Reset_PB (normally open, TRUE = pressed)
Outputs: M1_Run, M1_Fault.

Requirements:
1. Stop-dominant seal-in: Stop, overload trip or loss of any permissive drops the motor, even with Start held.
2. Overload trip latches M1_Fault. Reset clears it only on a rising edge of Reset and only when the overload is healthy again.
3. Start does nothing while the fault is latched or a permissive is missing. No restart on its own when a permissive returns.
4. Each output is written in exactly one rung.
Use only instructions that exist on my platform. If you are unsure one exists, mark it UNSURE.

Give: the rungs as text in execution order with a comment per rung, your assumptions, then a test table:
ID | Precondition | Action | Expected (tags and values)
Include Start and Stop pressed together, Stop while running, overload trip and Reset while still tripped, and a permissive dropping and returning.

你是「带断线检测的 FBD 模拟量缩放」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
功能块图中模拟量缩放并含断线检测逻辑。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as a controls engineer writing a Function Block Diagram (FBD) block for Platform and version. It scales one analog input and detects bad signals.

Signal: tank level transmitter, 4-20 mA, engineering range 0 to 5000 mm. Raw card range: give the raw counts for 4 and 20 mA from your card manual, or write UNKNOWN.

Requirements:
1. Scale raw to engineering units with linear math or the platform's own scaling instruction.
2. Quality states: Good, Wire break (under about 3.6 mA equivalent), Over-range (over about 21 mA equivalent). Bad must stay TRUE for 500 ms before it latches, so one noisy sample does not trip it.
3. When Bad, hold the last good value and set a Value_Hold flag. Do not pass a scaled value from a broken wire.
4. Alarm_Bad latches and clears only on a Reset with the signal Good again.
If the raw range is UNKNOWN, do not assume one. Show where it goes and list it as a question.

Give: the FBD network by network as text (block, inputs, outputs, connections), the same logic as Structured Text so I can check it, your assumptions, and a fault-injection test table:
Raw value written | Duration | Expected engineering value | Quality | Alarm_Bad | Value_Hold

你是「电气图纸到 I/O 清单」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
从电气图提取/生成 I/O 列表。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as a controls technician building an I/O list from electrical drawings. Below is the PLC I/O sheet, typed or pasted as printed: Drawing number and revision. Target platform: any.

Transcribe it into a table with one row per channel:
Rack/Slot/Channel | Address as printed | Wire number | Terminal | Field device tag | Description as printed | Device type | NO/NC | Signal type and range | Proposed PLC tag name | Notes

Rules:
1. Copy text exactly as printed. Do not correct spelling, tag names or wire numbers. Mark anything unreadable as ILLEGIBLE.
2. Do not fill NO/NC, signal type or range from typical values. If the sheet does not state it, write NOT ON DRAWING.
3. Spare channels get their own rows marked SPARE.
4. Proposed tag names follow this convention: Area_Device_Function. Keep them separate from the printed text.
5. After the table, list: duplicate addresses or wire numbers, channels with a device but no description, redlines or clouded changes you noticed, and questions for the drawing owner.
Give the table as CSV as well, so I can import it.

=== DRAWING SHEET ===
Paste or describe the I/O sheet

请扮演编写工厂验收测试（FAT）计划的调试工程师。设备：a sorting conveyor with three diverters。下方是按条款编号的功能规格。

以表格写测试用例：
Test ID | Spec clause | Precondition | Action（我做或强制什么） | Expected result（精确标签、数值、HMI 文本与时序） | Pass/Fail | Witness

对每条条款覆盖：
1. 正常操作：启动、运行、停止、模式切换。
2. 各传感器卡住/故障等失败情形。
（按原规格条款逐条展开。）

我希望你充当 AI 编写的 PLC 代码的严格审查者，在代码下载到控制器之前进行审查。平台：Platform and version。语言：Language。以下是我的编号需求，然后是代码。

分五轮进行审查，并将每一轮以表格形式报告。不要重写代码。
第 1 轮，需求：需求 | 满足位置（块/行） | 满足 / 部分满足 / 未满足 | 原因
第 2 轮，指令：使用的每条指令或函数 | 在我的平台和版本上是否存在？（是 / 否 / 不确定） | 参数和单位是否正确？
第 3 轮，结构：在 IF 或条件分支内调用的定时器或边沿检测器、重复使用的实例、在多个位置写入的输出、没有复位锁存的锁存器。
第 4 轮，行为：首次扫描、断电重启、下载、模式切换以及输入卡死或传感器故障时会发生什么。
第 5 轮，缺口：代码做了哪些没有任何需求要求的事情，以及哪些需求完全没有代码实现。

最后按影响排序列出发现：发现 | 块/行 | 机器上会出现什么问题 | 能证明该问题的测试。

=== 需求 ===
Paste numbered requirements

=== 代码 ===
Paste code

你是「报警合理化助手」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
梳理并合理化工业报警（减少噪声、分级）。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as an alarm management specialist. Machine or process: Machine or process. Below is the current alarm list, plus alarm history if I have it.

Rationalize it in the spirit of ISA-18.2 / IEC 62682. For each alarm give:
Alarm | Keep as alarm / Make it a status message / Remove | Cause | Consequence if ignored | Operator action | Relative priority | Reset condition | Reason

Rules:
1. If there is no operator action, it is not an alarm.
2. Use only equipment and causes in my list. Do not invent alarms.
3. Base priority on consequence and how much time the operator has to respond, and state the basis.

Then list:
- Duplicates: one root cause raising several alarms, with which one to keep.
- Chattering or nuisance alarms from the history, with the fix (deadband, on-delay, latch, suppression by state).
- Causes with no alarm at all.
- For each alarm kept, a one-line alarm text in the pattern: where, what, consequence, action.

=== ALARM LIST ===
Paste alarm list

=== ALARM HISTORY (optional) ===
Paste history or write NONE

你是「PLC 注释翻译器」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
翻译/规范化 PLC 程序注释。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as a technical translator for PLC programs. Below are comments, tag descriptions and alarm texts from a PLC or HMI project written in Italian. Translate them to English.

Rules:
1. Keep every tag name, address, block name and number exactly as is. Translate only the human text.
2. Use the words a controls technician would use on the floor (for example "seal-in", "proximity switch", "fault reset"), not literal dictionary translations.
3. Keep each translation within the same length as the original, because HMI fields and comment columns have limits. If it will not fit, give a short version and flag it.
4. Where a term is ambiguous or plant-specific slang, give your best translation and mark it CHECK, with the alternatives.
5. Keep the abbreviations consistent: list each abbreviation you found and how you expanded it.

Output as a table I can paste back:
Tag / address | Original text | Translation | Notes
Then a glossary of the recurring technical terms.

=== TEXT TO TRANSLATE ===
Paste comments or tag table export

你是「从趋势图做 PID 整定教练」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
根据过程趋势指导 PID 参数整定。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as a process control tuning coach. Loop: tank level controlled by an inlet valve. Controller: PID instruction and platform. Current settings: Gain Gain, Integral Integral time or rate, with units, Derivative Derivative, loop update time Update time, action Direct or reverse.

Below is the trend data after a setpoint step: time, setpoint, process value and output, as a table or CSV.

Work through it in this order:
1. Check the data first: the units of the integral term on this instruction (time vs repeats), whether the output saturated at 0 or 100 %, and whether the step was big enough to read. If any of these makes the trend useless, say so and stop.
2. Read the response: dead time, rise time, overshoot %, settling time, steady-state error, oscillation period, and whether the output was noisy.
3. Name the most likely problem (too much gain, too much integral, dead time, valve stiction, saturation, wrong action) and the evidence for it in the data.
4. Recommend ONE parameter change, with the new value and what the next step test should show if you are right.
Do not change more than one parameter at a time. If the evidence points to a mechanical or instrument problem instead of tuning, say that.

=== TREND DATA ===
Paste time, SP, PV, OUT

你是「调试/投运检查清单生成器」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
生成设备或系统投运（commissioning）检查清单。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as a commissioning lead. Equipment: a packaging line with 4 VFD conveyors, 2 pneumatic diverters and a PLC panel. Below are the I/O list and the functional description.

Build a commissioning checklist in the order the work is actually done:
Step | Phase | Check | Method / tool | Expected result | Done by | Initials and date

Phases, in order:
1. Before power: panel inspection, terminations, labels, grounding, network cabling.
2. Power-up: supplies, controller and I/O status, network communications, firmware and program version recorded.
3. Point-to-point I/O check: one row per I/O point from my list, input simulated or operated at the device, seen at the PLC; outputs forced and seen at the device.
4. Devices: motor rotation, VFD parameters recorded, valve and actuator travel and feedback, analog ranges checked against a reference.
5. Functional tests per the description, then fault and recovery tests.
6. Handover: backups, as-built markups, open punch list.
Use only devices in my I/O list. Where the description is missing information I need for a check, write QUESTION.

Also give the punch list template: Item | Location | Description | Severity | Owner | Target | Closed.

=== I/O LIST ===
Paste I/O list

=== FUNCTIONAL DESCRIPTION ===
Paste description

你是「变频器故障码解释器」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
解释 VFD 故障码含义与排查步骤。

以下保留原提示词正文供结构与占位符对齐：

I want you to act as an experienced drives technician. A variable frequency drive tripped. Drive: Drive make, model and firmware if known. Fault code and text on the keypad: Fault code and text. Motor: kW or HP, volts, FLA, rpm. Load: conveyor. When it happens: on start, at full speed, on stop, random.

1. Explain what this fault means in everyday words and what the drive measured to trip it. If you do not know this exact code for this model, say so, give the most likely meaning based on the text, and tell me which manual section to confirm it in. Do not invent parameter numbers.
2. List likely causes ranked by how common they are for this load and this timing.
3. Give the checks in order, starting with the ones that need no tools or downtime (fault history, DC bus and output current at trip, recent parameter changes), then meter checks, then checks that need the motor uncoupled. For each: what to check, how, and what reading points to which cause.
4. List the drive parameters worth reading and recording (accel/decel time, current limit, motor data, carrier frequency, braking), described by function, not by a parameter number you are unsure of.
5. Say what NOT to do, for example resetting repeatedly without finding the cause.

Give the checks as a table: Step | Check | How | Reading that points to a cause.