EnglishDeutsch/api/energyGitHub · iceccarelli
Grimaldi EngineeringCluster control · Frankfurt
Integrators

Build the cell. Get the planner.

Two robots to start: Universal Robots with a URScript stub today, one of FANUC / KUKA / ABB next, chosen by the first integrator that brings a cell.

You keep

  • CE marking and the risk assessment
  • Fence, scanners, safety PLC
  • Service contract and spares
  • The customer relationship and the invoice

You get

  • Planner — Mixed-SKU stack from a CSV, stability and density scored, faults named by SKU. Browser planner here, Python engine in the repository.
  • State-machine document — IDLE · RUN · HOLD · FAULT, entry and exit conditions, fault codes, what the PLC sees on OPC UA.
  • Gripper class — One vacuum class with pressure feedback and retry, the interface a mechanical gripper implements the same way.
  • Acceptance test — A written test the cell passes before RUN: sample list, expected layers, stability floor, cycle-time assumption stated.

Robots

RobotStatusNote
Universal RobotsURScript stub shipsUR10e / UR20 class payloads. Export from the planner.
FANUC · KUKA · ABBplannedOne adapter next. The integrator with a cell picks which.

Same controller, next end-effector

PlannerState machineRobot adapterControllerPallet grippernowPaint end-effectorlaterFloor end-effectorlater
Pallet now. Paint or floor end-effector later on the same controller thesis: planner → state machine → robot adapter. No unit for sale beyond the palletizer.

Written and maintained by Vincenzo Ceccarelli Grimaldi, Frankfurt am Main.