DrAmaT - AI agent - Check prompts

« AI Agent examples (editor) | Contents | AI Agent window of the Robot Cell Simulator »

One sentence is enough: write what you want to check, and the AI agent chooses the commands of DReS itself, runs them and answers with the findings. This page is a catalog of example prompts for the AI Agent window of the editor and the AI Agent window of the Robot Cell Simulator. Change the names, folders and limits to your own – the agent answers in the language of the prompt.

The agent only reads. A fix is a proposal (place and new text); programs are changed only when you agree.
Every number in the answer comes from a command of DReS – the agent does not estimate results.
What could not be checked is listed as Not checked with the reason – never reported as OK.

How to ask What the answer looks like Status of the prompts A. Syntax and structure B. Points and reachability C. Tools, bases, loads D. Path and time E. Signals, interlocks, VW standard F. Collisions and zones (simulator)G. Comparisons and archives H. Reports and documentation Combined check of a station Licenses Limits

How to ask

Scope – say what to check: the open robot projects / all robots of the station, robot R05, the open programs, this program, the archives in D:\Archives\ST010, the loaded station (simulator). Archives of a folder are opened as robot projects in the project tree when a check needs them.
Limits – give your values: max. 2 mm, above 90 %, closer than 30 mm, longer than 1500 mm.
Result – say the form: as a table, as a PDF report, as an Excel file with one sheet per robot.
Language – any; the agent answers in the language of the prompt.

Long checks (hundreds of programs) take minutes; the agent says the plan and the expected time before it starts. Checks of the syntax of many files open and close each file in the editor without saving.

What the answer looks like

Every check of the editor and of the simulator answers in the same format:

Summary – what was checked and the result in numbers, e.g. 5 robots, 214 programs: 3 errors, 11 warnings.
Problems – one table, errors first: priority, robot, program / file, point / line, problem, suggestion.
What the programmer should do – a few points in the order of importance.
How it was checked – commands and numbers of files.
Not checked – everything that could not run, with the reason (missing file, unsupported controller or mounting, missing license, no station loaded, function not available yet).

Priority	Robot	Program	Point / line	Problem	Suggestion
ERROR	R2	Folge12	line 48	UP77 is called, the program does not exist	add UP77 or remove the call
WARNING	R4	UP42	P49	A4 uses 96.1 % of its range (2.1° left)	check S / T of the point
INFO	R1	UP105	–	UP is never called	may be started by the SPS – check

ERROR = the robot does not work correctly or it is dangerous, fix before the start-up; WARNING = probably wrong or left over, the programmer checks it; INFO = cleaning up and documentation.

Status of the prompts

available the agent does it with the commands of today available – partly works with more steps, or the agent computes the verdict from the data coming soon the command is in preparation – until then the agent says what it cannot check and names the manual way (menu or plugin).

Window: Editor = AI Agent window of the editor, RCS = AI Agent window of the Robot Cell Simulator (a station must be loaded). The commands behind each prompt are described on the pages VeRa – Editor API and RCS command API.

A. Syntax and structure

ID	Prompt	What the agent checks	Window	Status
A1	Check the syntax of all programs of the open robot projects and list the errors.	syntax check of every program, errors per robot / file / line, warnings grouped (API check_syntax with projects, without windows)	Editor	available
A2	Check the syntax of every robot archive in D:\Archives\ST010.	find_projects lists the archives of the folder, check_syntax with folders reads them without opening; archives not recognised listed separately	Editor	available
A3	Which Folgen call UPs that do not exist, and which UPs are never called?	UP calls against the existing UP programs	Editor	available
A4	List the used and unused Makros of every robot and the called Makros that are missing.	Makro calls against the existing Makros	Editor	available
A5	Which programs have a different TPVW version than the rest of the robot?	TPVW version of every program, deviations from the majority	Editor	available
A6	Find Folgen with an empty comment and .src files without .dat.	header comments, pairs .src / .dat	Editor	available
A7	Do all robots of the station use the same VW user and KSS / system version?	robot info of every project as one table	Editor	available
A8	Compare the Makros of all robots with the master Makros in D:\Standard\Makro.	first different line per Makro (changes may be intended)	Editor	available – partly

B. Points and reachability

ID	Prompt	What the agent checks	Window	Status
B1	Check whether points 1, 2 and the last point of every Folge are the same, and whether every UP starts at the point where it is called (max. 2 mm).	distances in mm, different bases compared in world coordinates	Editor	available
B2	Show me all points where an axis uses more than 90 % of its software range.	usage of every axis in %, side, margin in degrees – Axis limit usage	Editor	available
B3	Same for the robot archives in D:\Archives (axis range report as PDF).	as B2, archives read from the folder (nothing opened), report file PDF / HTML / Excel / CSV	Editor	available
B4	Are all points reachable? List the points the inverse kinematics cannot solve.	points without a kinematic solution; unsupported mountings reported as not checked – Axis limit usage	Editor	available
B5	Are all E1 values (travel track, 7th axis) inside the axis limits?	E1 of every point against the software limits	Editor	available – partly
B6	Find points with the same coordinates but different names, and points used twice.	points of a program in the same place (path_check duplicates in mm); across programs: point tables compared	Editor	available – partly
B7	Which points are close to a wrist singularity (A5 near 0°)?	A5 of the points of LIN / CIRC motions (also the auxiliary points of the arcs; PTP on request) – Axis limit usage	Editor	available
B8	Is the first and the last point of every Folge the HOME position of the robot?	distance of the points from HOME in mm	Editor	available – partly
B9	Export the point tables of all UPs of robot R05 to one Excel file.	one sheet per UP	Editor	available

C. Tools, bases, loads

ID	Prompt	What the agent checks	Window	Status
C1	Which tools and bases are used in the programs, and are they all defined?	used numbers against the robot data: used but undefined, defined but unused	Editor	available
C2	Check the payload data of every used tool (not set, above the rated payload, centre of mass 0).	payload of the used tools against the robot model	Editor	available
C3	Does every used tool have a tool calibration in the .cal file?	calibration data of the used tools (KUKA VKRC)	Editor	available
C4	Compare the bases of the robot archives with the bases of the study.	position and rotation differences, common bases of the station	RCS	available
C5	Do tools with the same number have the same data on all robots of the station?	differences in mm / degrees per tool (may be intended)	Editor	available
C6	Give me the tool / base usage of all robots as an Excel table.	usage table and the most important remarks	Editor	available – partly

D. Path and time

ID	Prompt	What the agent checks	Window	Status
D1	Path length and motion time of every Folge of all robots in one table.	TCP path length and planned time per program	Editor	available – partly
D2	Find motions longer than 1500 mm in the UPs of R03.	segments with length, motion type and speed (path_check longSegments)	Editor	available
D3	Check the approximation: are there approximation distances that cannot be reached?	approximation in mm against half of the shorter neighbouring motion (path_check approximation)	Editor	available
D4	Are all switch points (trigger, distance / delay) inside their motion?	distance and delay of the switch points against the motion (path_check switchPoints)	Editor	available
D5	Glue length of every glue UP (gun on / off).	path length while the process is on, lines used as on / off	Editor	available
D6	Compare the planned motion time of Folge 81 with the cycle time from the simulation.	difference = waits for interlocks and wait times	Editor + RCS	available
D7	Find LIN / CIRC motions with very low or unusual speeds and PTP above 100 %.	speed of every motion	Editor	available
D8	Which arcs (CIRC) are longer than 180° or badly defined?	arc geometry: collinear points, more than 180°, radius, auxiliary point near the end (path_check arcs)	Editor	available

E. Signals, interlocks, VW standard

ID	Prompt	What the agent checks	Window	Status
E0	Check the collision zones / collisions of the robots in D:\Archives\ST030.	without a study with the robot positions and without a defined WORLD position (robot_world: $ROBROOT ≠ 0) the agent says that a geometric collision check is not possible – it does not guess positions or place the robots at zero; it offers the check of the programmed interlocks (VKRC, Fanuc: collision_map, RCS check_interlocks)	Editor	available
E1	Generate the collision map for all robot archives in D:\TEST and check the logic.	interlock map robot – robot from the program code (KUKA VKRC, Fanuc), findings; signal analysis, not geometric	Editor	available
E2	Which zones are requested but never released, or requested without Makro20?	findings of the interlock map	Editor	available
E3	Do the comments over the interlock points name the right partner robot?	partner named in the comment against the interlock logic	Editor / RCS	available
E4	Check the interlocks of the station with the simulator rules (wait chains, races, zones held too long).	rules of the simulator with the cost in seconds of the cycle	RCS	available
E5	Which used inputs / outputs have no long text?	used signals against the long texts	Editor	available – partly
E6	Find outputs that are set and never reset and waits without timeout.	set / reset and wait commands per program	Editor	available – partly
E7	Show all SERVOZANGE welds with Offset > 0 in the UPs, values 0 in red.	parameters of the SERVOZANGE commands as a table	Editor	available
E8	Are weld point numbers used on two robots?	weld point numbers of all robots	Editor	available
E9	Review the Folgen of R02 against the VW good-program checklist.	points of the checklist OK / not OK	Editor	available

F. Collisions and zones (simulator)

ID	Prompt	What the agent checks	Window	Status
F1	Load the open robot projects into the simulator and run Folge 81 on all robots.	station built from the robot projects (today: from a study or a simulation file)	RCS	coming soon
F2	Open the study D:\Study\cell.psz with the archives in D:\Archives and check the bases.	loading report and base check	RCS	available
F3	Find all possible collisions of the open station and give me the report.	standard collision study: zones, interlocks, robustness test, Live 3D, report	RCS	available
F4	Which robot pairs come closer than 30 mm? Save the closest approaches as PDF with R1..Rn.	closest approach per pair (parts, distance, time, points), report with anonymous robot names – Closest approaches	RCS	available
F5	Which shared work zones have no interlock?	shared volume of the pairs against the interlocks; proposal only	RCS	available
F6	Is there a request race that changes the cycle time? Test both orders.	simulation of both orders, difference of the cycle	RCS	available
F7	Run the robustness test (missing signals) and list the collision risks.	risks per test step, robot and point	RCS	available
F8	Compare the cycle time of the changed programs with the original.	difference of the cycle per robot and its reason	RCS	available
F9	Check the stations of all simulation files in D:\Sim overnight and give me one table.	station × cycle × collisions × risks (files named by you or recent files)	RCS	available – partly

G. Comparisons and archives

ID	Prompt	What the agent checks	Window	Status
G1	Compare the archive of R05 before and after the start-up: what changed?	programs only in one archive and changed programs with the changed lines (archive_diff); moved points with points per program	Editor	available
G2	Which points moved by more than 2 mm between these two versions of UP42?	points matched by name, differences in mm / degrees	Editor	available – partly
G3	Compare the interlocks of the old and the new archive of the station.	zones new / removed, changed partner	Editor	available – partly
G4	Which Makros differ between the robots of the station?	Makro, robots, first difference	Editor	available – partly
G5	Is the archive in D:\Backup\R03 the same as the open project R03?	yes / no and the list of differences (archive_diff with the archive folder of the project)	Editor	available

H. Reports and documentation

ID	Prompt	What the agent checks	Window	Status
H1	Robot check of all robots of the station before the start-up, as a PDF report.	programs, Makros, tools, loads, bases, calibration, axis limits per robot (KUKA VKRC, Fanuc VW)	Editor	available
H2	Check collisions in the open robot projects for VKRC and Fanuc, check the reachability of the points and generate a report.	interlock map, axis usage and reachability, geometry in the simulator when a station is loaded	Editor (+ RCS)	available – partly
H3	The same for the folder D:\Archives\ST020.	as H2 for the archives of the folder	Editor (+ RCS)	available – partly
H4	Full check of the station (syntax, points, axes, tools, interlocks, path) as one PDF and one Excel file.	combined check, errors / warnings per robot and per check	Editor	available – partly
H5	Generate the program documentation of R01 (all Folgen and UPs).	program documentation (today: DocGenerator plugin)	Editor	coming soon
H6	Write the findings of the last check into an Excel file with one sheet per robot.	Excel file of the findings	Editor	available
H7	Save the procedure of this check as my own knowledge file "station_check".	own knowledge file, used in the next chats	Editor	available

Combined check of a station

Prompt:

Check the open robot projects (structure, tools, loads, axis range, points, interlocks) and give me a PDF report.

The agent works step by step and tells you the plan and the time first:

robots and controllers of the scope;
structure: UP and Makro calls, versions, comments;
tools, bases, loads and calibration;
axis range, reachability and wrist singularity of the points (Axis limit usage);
same points and start points of the UPs;
interlock map robot – robot (KUKA VKRC, Fanuc);
syntax of all programs – on request or for small stations;
one report (HTML and PDF, Excel on request): summary table robot × check, one section per check, Not checked at the end.

Collisions in 3D, work zones and closest approaches are checked in the Robot Cell Simulator – the agent offers it as the next step. In reports for other people the robot names can be written as R1..Rn.

Licenses

AI agent knowledge (247) – the knowledge of DrAmaT for the AI agent windows (recipes of these checks).
API / CLI (248) – commands that change something (writing report files, opening projects); reading commands need no extra license.
Robot Cell Simulator: Simulation (141) for runs, Work Zones (143) for zones of more than 2 robots and the interlock checks, Robustness test (144), Collision 3D (145) for Live 3D and closest approaches – see RCS licenses.
Controller licenses of the editor apply as for the menus (e.g. KUKA KRC functions).

A missing license is reported by the agent under Not checked; it does not try other ways.

Limits

Signals are not geometry. The interlock map and the interlock checks analyse the program code; collisions and distances come only from the Robot Cell Simulator (zones, Live 3D, robustness test). Without Collision 3D the agent never reports no collisions.
Kinematics. Only proven robot configurations and mountings are computed. A point that cannot be computed (unsupported mounting angle, robot base not supported, robot on a base axis) is reported as an error or not checked – never as reachable.
Coming soon. For these prompts the agent says what it cannot check yet and names the menu or plugin to do it by hand.
The agent never saves robot programs without your consent; files of your archives are only read.

« AI Agent examples (editor) | Contents | AI Agent window of the Robot Cell Simulator »