Edmund Documentation
/USER MANUAL

Documents & PLC programs

How to add project knowledge in Edmund: upload documents and PLC programs, read the indexing status and type in the list, and know what belongs as a document, a PLC program, a data source or a journal entry.

Expert Last reviewed July 2026

Every project has its own knowledge, and documents are the largest part of it — the manuals, datasheets and drawings Edmund reads to answer questions about that machine. You manage them inside a project under Dokumenty (Documents); controller exports live alongside them under PLC Programy (PLC Programs). Everyone on the project can view what’s there, but uploading and managing files is limited to the Administrator and Expert roles — see Roles & permissions.

Upload a document

  1. Open the project, then go to Dokumenty (Documents).
  2. Choose Nahrát dokumenty (Upload documents) and pick one or more files — typically PDF manuals, datasheets, schematics and spare-parts catalogs.
  3. Wait for the row to finish indexing. Edmund extracts the text and classifies the file by type; a document can’t be used or cited in answers until indexing is done.
Warning

A file that hasn’t finished indexing — or that has no readable text, such as a scanned, image-only PDF — is listed but contributes nothing to answers. If a manual seems to be ignored, check its status here first.

Upload documents — drag files in, or browse, to add them to the project.

The documents list

The Documents list of a real machine — each file's extension, index status, type and source.

The list is a table with columns for Název (Name), Přípona souboru (File extension), Stav (Status), Typ (Type), Zdroj (Source), Nahrál(a) (Uploaded by) and Vytvořeno (Created). Two columns matter most:

  • Stav (Status) is the index state. Indexed means Edmund has read the file and it can appear — with a Source link — in answers. No text means no text could be extracted, so nothing inside it reaches answers.
  • Typ (Type) is filled in automatically when Edmund classifies the file.

Filter by extension, status, type or source to narrow a long list — filtering by No text is a fast way to find files that need a text-based version. For how an indexed document is cited, see Reading answers & citations.

Electrical and pneumatic schematics have their own type, Schématické diagramy (Schematic diagrams) — filter by it to see a machine’s drawings at a glance. Exports from EPLAN land here as searchable PDFs, indexed like any other document:

A real machine's schematics — electrical and pneumatic drawings, including an EPLAN export, indexed and ready to cite.

And this is what an indexed schematic does in chat: ask about a component, and the answer cites the drawing — clicking a Zdroj (Source) link opens the PDF at the exact page, with the cited area highlighted:

A real conversation: the answer cites the EPLAN wiring diagram, and the Source opens the PDF on page 43 with the cited circuit highlighted.

PLC programs

Adding a controller export works almost the same way, with one extra step.

  1. Open the project and go to PLC Programy (PLC Programs), then choose Nahrát PLC Program (Upload PLC program).
  2. Name the program and select the export file.
  3. Wait for indexing to finish. From then on you can ask Edmund about the program in plain language in this project.
A real controller export — a Siemens program, indexed and ready to be referenced in chat.

Once indexed, the program answers at code level: ask about a fault and the reply walks the blocks, timers and I/O involved — and a Zdroj (Source) link opens Náhled kódu (Code preview) with the program tree and the cited block highlighted:

A real conversation: the alarm's PLC logic explained from the Siemens export, with the cited block open in Code preview.

What belongs where

Put each kind of knowledge in the place built for it:

  • Documents — manuals, datasheets, drawings and schematics, including EPLAN exports (files Edmund reads as text).
  • PLC programs — controller exports and control logic.
  • Data sources — live plant data from a connected database. See Data sources.
  • Maintenance journal — repair and fault history. See Maintenance journal.