Your inputs
Platform and firmware versions, SDK/API access, task description, sample data, equipment and site rules.
Integration / complete stack
Connecting robots, software and perception
MALONI provides programming and integration of robots, cameras, sensors and software for a specific task. We connect ROS 2 with object recognition and control interfaces; scope, responsibilities and evaluation are agreed for the platform and operating environment.
50°05' N / 14°25' EHUMAN · SYSTEM · ENVIRONMENT01 / MALONI ROBOTICSSCROLL TO EXPLORE ↓
Technical team and actual examples
Meet our team and explore documented internal development work. The MuJoCo examples are simulations, not customer installations.
Timotej Rybár — Robotics Software Lead →Humanoid development examples →
01 / Integration
What to prepare and what we hand over
We agree development scope and handover materials before starting. Each deliverable is tied to the specific configuration and acceptance scenarios.
Agreed deliverables
Configuration and interfaces, a runnable example, reproduction steps and documentation. The agreement specifies source-code handover and licensing.
Testing and acceptance
Predefined scenarios, conditions and success measures; a record of results, limitations and open issues. Simulation and physical-robot tests are evaluated separately.
02 / Integration
Robot programming, perception and control
MALONI provides C++ and ROS 2 programming for humanoids and robot arms. Our offer covers Gazebo, RViz, cameras, sensors, navigation algorithms, MoveIt 2 and ROS 2 integration with object recognition. Compatibility and development scope are confirmed for the platform, available interfaces and specific project.
03 / Integration
The layers to coordinate
Robot platform and mobility
Physical capability, charging, movement and site constraints.
Manipulation and hands
Grasping, reach, payload and task tooling.
Vision and perception
Sensing, localization and scene understanding.
Voice and human interaction
Accessible interaction with appropriate human escalation.
AI and embodied software
Planning, control and learning within a defined operating envelope.
APIs and connectivity
Connections to enterprise systems and data flows.
Teleoperation and orchestration
Remote intervention and repeatable workflow control.
Safety, monitoring and support
Assessment, observation, incident response and documented procedures.
04 / Integration
A coordinated delivery model
MALONI aligns manufacturer guidance, customer requirements and specialist engineering. The exact workshare, acceptance criteria and support responsibilities are defined per project; every discipline is not claimed as an existing in-house service.
05 / Integration
Assign an owner to every handover
A proposed responsibility check for a future project. Record the named person, document and approval for each line before the robot operates.
Manufacturer
Provide approved operating limits, technical documentation, software rules, diagnostic route and repair or warranty decisions.
Customer and site operator
Own the task, site access, people nearby, data permissions, operator training and safe-stop procedure.
MALONI and specialists
Agree any coordination, interfaces, local triage and handover work in writing; do not assume authorization or on-site coverage.
ImportantExact duties depend on the platform, risk assessment and signed agreements.
06 / Integration
Hand over a supportable system
An agreed handover should identify the deployed configuration and software versions, permitted log access, data owner, safe-stop and recovery steps, change approval and named customer and manufacturer escalation contacts. Record task acceptance criteria and unresolved issues. The exact first-line role and on-site coverage must be agreed before operation.