Robot cells: registry, commissioning survey and Robotics Studio

Production → Robot cells → Registry & survey. This is where you record what exactly is in the cell and how well it is known.

Evidence level

Every fact has a level: unknown < estimated < simulated < measured < validated.

• A model name read in the robot's web interface is estimated.

• The same name on a nameplate photo is measured.

• "Measured" and "validated" cannot be saved without a source or a photo.

A conclusion is never stronger than the weakest data it rests on. So until the robot model is confirmed, Oprela will not say "feasible" any stronger than "estimated".

Commissioning survey

Sections: robot arm, controller, software & SDK, laser source, laser head, chiller, positioner, safety, network, process & parts. Each answer has a value, a level, a source and photos (e.g. of the nameplate). A new answer does not erase the old one: the history stays. The survey is read-only: take photos, read versions, write down what is missing. Robot motion and the laser are not switched on for it.

Robot, model, tool

• Robot in the cell: code, vendor, model as shown by the device, serial numbers, firmware, the SDK on the gateway, WebAPP / WebRecovery addresses. Passwords and tokens never go here: the system refuses them, they stay on the cell gateway.

• Robot model (kinematics): the official URDF of the confirmed model. The server parses the file and checks the axes and limits. An approved model is frozen; a change is a new revision.

• Tool: e.g. the laser head: an envelope for collision checks, the nominal TCP, the working distance and its tolerance.

Robotics Studio

Open Robotics Studio opens the 3D scene of the cell:

• the robot from its kinematics, with axis sliders inside the limits;

• the workpiece: a weld node with its 3D model and seams (green — confirmed, yellow — suggested);

• tables, fixtures, fences, doors, keep-out zones; move and rotate with the mouse or by numbers.

The layout is saved as a revision. An approved revision is frozen and is part of the robot program fingerprint: changing the layout, the tool or the robot model makes an approved program non-current. The scene is a preview only. It does not prove that the robot reaches the seam or that nothing collides. Reach and collision checks come in the next stages.