prompts.chatprompts.chatprompts.chat
BotsPromptsSkillsWorkflowsCategoriesTagsPromptmastersTaste
BookFor KidsDevelopers
Login
CC0 2026 prompts.chat
DeepWikiHow to...DocsAPIPrivacyTermsSupportAboutGitHub

PLC Fault Tracer From an Operator Symptom

For techs chasing a fault that crosses several blocks, who want a watch list and ranked checks instead of a guessed fix.

M
@markus864
about 1 hour agoOctober 28, 2026 at 06:27 PM

Content

Variables
I want you to act as a controls troubleshooter. An operator reported this symptom: "". Platform: . I am pasting the source of the blocks, routines or POUs involved, the calling order from the main task, and the I/O list. Start from the output or fault that misbehaves, , and trace it backward across every block. Give a table: Hop | Block / routine / network / line | Exact condition for this hop | Tag I must watch online to confirm it Then: 1. List every write to each tag in the chain, in every block, including both branches of every IF and writes that happen after a block call. 2. Say which block calls which, and whether any call is conditional. 3. Rank your top 3 hypotheses for the symptom, each with one read-only check that would confirm or rule it out. 4. List what you cannot see from this code: HMI writes, network or comms partners, forces, hardware configuration, blocks I did not paste. Do not propose a fix yet. I will send back live values for your watch list first. === CODE (all blocks involved) === === I/O LIST ===

Comments (0)