| name | tc-beckhoff-docs |
| description | Use when researching a Beckhoff TwinCAT library, function block, or function via Beckhoff infosys, OR when looking up a Beckhoff hardware product by order number. Triggers on requests like "what does FB_EcCoESdoRead do", "which TF library has SDO read", "what are the inputs of FB_X", "what are the technical specs of EL3004", "look up EPP6228", "how many channels does the EK1100 have", or as a precondition before writing code that uses an unfamiliar Beckhoff FB. Uses TcKit's FindFb, SearchDocs, FindHardware, and GetDocPage MCP tools. Do NOT use for inspecting the user's local project (that is tc-read-project). |
| allowed-tools | mcp__tckit__FindFb, mcp__tckit__SearchDocs, mcp__tckit__FindHardware, mcp__tckit__GetDocPage |
Researching Beckhoff infosys
Beckhoff FB conventions, timing notes, and hardware specs are not reliable in training data, especially for newer TF libraries and hardware. Always ground claims in infosys.
Procedure
- Known FB name →
FindFb. If the user (or your prior reasoning) has a specific FB name, call FindFb(fbName) first. The result includes inputs, outputs, timing notes, and a description.
- Fuzzy query →
SearchDocs. When you don't know the exact name, call SearchDocs(query, section=""). Use section to scope to a known infosys area when you know one.
- Hardware order number →
FindHardware. For a Beckhoff hardware product (e.g. EL3004, EK1100, EPP6228-0022, EJ1100, CU1128), call FindHardware(orderNumber). It returns the product description, the infosys URL, and the parsed "Technical data" table. The order number may carry a variant suffix (); it is normalised to the bare order. Covers EtherCAT Terminals (EL/EM/ELM/ED), couplers (EK), EtherCAT Box (EP/ER/EQ), EtherCAT P Box (EPP), plug-in modules (EJ), IO-Link boxes (EPI/ERI), and infrastructure/switches (CU).
