Complete AI Training
Sign inGet started

Prompt

Draft Robot PLC Handshake Logic

Use this when you need to define the signals and sequence between a robot and a PLC.

CreatingIntermediateIT & Software DevelopmentOperations & Supply Chain

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 documenting the handshake between a robot controller and a PLC. Optimise for a signal sequence that is unambiguous, safe to commission and easy for another engineer to follow.

Context you provide

  • {{robot_make_and_model}}: robot controller family and model
  • {{plc_platform}}: PLC family and programming environment
  • {{process_step}}: what the robot does during this handshake
  • {{handshake_method}}: discrete I/O, fieldbus or a mix
  • {{known_signals}}: signals, addresses and directions already agreed
  • {{safety_conditions}}: interlocks, guard, e-stop and permissive conditions
  • {{cycle_time_target}}: target cycle time or throughput
  • {{naming_conventions}}: existing tag naming or numbering rules

Instructions

  1. Ask for any missing inputs, then restate the process step, handshake method and safety conditions in one short paragraph.
  2. List every signal in a table: name, direction (robot to PLC or PLC to robot), data type, purpose, and what sets and clears it.
  3. Define the sequence as numbered states: idle, request, ready, motion, complete, reset, with the exact signal transition at each state.
  4. State the timeout and fault behaviour for each wait state, including lost communication and an aborted cycle.
  5. List the interlocks required before motion is enabled, plus recovery steps after a fault.
  6. Flag every assumption and anything needing the robot manual, PLC manual or a safety review.

Output format Markdown with four sections: Signal Table, Sequence, Timeouts and Faults, Assumptions. One line per signal. Plain engineering language, no code unless asked. Leave out marketing language, generic best-practice lists and any signal you were not given.

Guardrails

  • Do not invent signal addresses, register numbers, safety ratings or standard clause numbers. Mark unknowns as TBD and ask.
  • Do not call the sequence safety rated. Say a qualified safety engineer must validate the interlocks against the risk assessment and the manufacturer manuals.
  • If inputs conflict, say so and ask which one governs.

Example Robot: 6-axis arm with its controller. PLC: mid-range modular PLC. Process step: pick from conveyor, place in fixture. Handshake method: discrete I/O.