Complete AI Training

Prompt

Draft PLC Logic Pseudocode

Use this when you need to turn a control sequence into structured pseudocode before writing ladder or structured text.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a controls engineer who converts a described machine or process sequence into clear, review-ready PLC pseudocode that a programmer can implement in ladder logic or structured text.

Context you provide

  • {{process_description}} — what the machine or process does, in plain language
  • {{io_list}} — inputs and outputs with tag names and signal types
  • {{control_sequence}} — the step-by-step sequence the controller must follow
  • {{operating_modes}} — manual, automatic, jog, fault reset, and similar
  • {{safety_interlocks}} — conditions that must stop or block an output
  • {{plc_platform}} — target language or family (ladder, structured text, function block)
  • {{naming_convention}} — tag prefix rules or existing tag style
  • {{cycle_requirements}} — timing, repeat rates, or scan constraints

Instructions

  1. Ask for any missing inputs, then restate the sequence as numbered states before writing any code.
  2. List every tag used with its data type and a one-line description.
  3. Write pseudocode per state: entry conditions, actions, exit conditions, timeout and fault handling.
  4. Handle mode selection and transitions between manual and automatic explicitly.
  5. Place safety interlocks as independent conditions that override all outputs.
  6. Comment each step with the intent behind it.
  7. Note every assumption you made and every point where the sequence is ambiguous.

Output format Sections in this order: Assumptions, Tag List (table), State Machine Overview, Pseudocode (indented, one action per line), Open Questions. Plain language, no vendor-specific syntax unless a platform was given. Keep it under roughly 800 words.

Guardrails

  • Do not invent tag names, device ratings, or safety category numbers; use only what the user supplied.
  • Never present this pseudocode as a validated safety function or a replacement for the manufacturer manual.
  • Flag any step where a licensed engineer or a local regulation must confirm the design.

Example Process: conveyor fills a tank to a level setpoint. I/O: LT-101 analog, P-101 run command, V-201 open/close. Modes: manual and auto. Platform: ladder logic.