Ship your product with a simulation model your customers can use.
Give customers a model of your product to evaluate in their own simulator. We build it from your CAD and specifications, with integration examples and documentation. Hardware validation is available separately.
A model, integration example and documentation.
The model uses your CAD mass properties and specified joint limits. Meshes are simplified for simulation; missing properties and any estimates are identified in the delivery.
The ros2_control configuration exposes matching interfaces in simulation. A compatible hardware driver is needed to use the same controllers on the real unit.
- URDF and xacro description with source meshes and stated mass-property assumptions
ros2_controlconfiguration matching the interfaces on the real unit- Gazebo integration
- Isaac Sim integration, geometry in OpenUSD
- Launch files and a worked example
- Documentation site covering joints, interfaces, parameters and units
- CI that builds the package and runs its tests
The proposed package includes these items; see how we scope the work.
What we need before the model can be built.
The call confirms what you have and what needs to be prepared.
CAD of the machine
Assembly-level STEP or native CAD. We use its mass properties when available; otherwise the quote states which properties will be estimated from geometry and stated mass.
The interface specification
Joint limits, gear ratios, ranges, units and sign conventions — whatever your technical team uses. A register map or an SDK header is a better source than a datasheet.
What your customers ask for
Which simulator they run, which distro they are on, and what they are trying to evaluate. This decides what the model has to do well.
Someone to answer questions
A technical contact who knows the machine and can answer questions about its specification.
Agree the model and interfaces first.
Start with one machine in one variant, using your CAD and an agreed interface specification. Additional variants, sensor and tool interfaces, and CAD rebuilding are scoped explicitly.
- ROS 2 hardware driver — so the same interfaces drive the real unit
- Hardware-validated twin — the model’s accuracy as a measured figure
Before we discuss your project.
Which simulators does it cover?
We build and test in Gazebo and Isaac Sim. Geometry is delivered in OpenUSD and URDF, with parameters provided separately. Other simulators may require adaptation, which is agreed in the quote.
Is this a validated twin?
No. It includes geometry, motion constraints and simulation integration. Comparing its dynamics with a physical unit is a separate validation service.
Our CAD is a mess. Is that a problem?
We review the CAD first. The quote identifies simplification, missing properties and any estimates or additional measurements needed.
Can we keep it private?
Yes. You choose whether to publish the project-specific work, share it with customers or keep it internal, subject to the component licences identified in the quote. Nothing about your product is published here without written permission.
Who maintains it after handover?
Your team receives the source, documentation and automated tests. Maintenance across future releases can be quoted separately.
Tell us about the product.
Start with a free twenty-minute scoping call. We’ll review the task and available information, then propose a scope and price. If a paid assessment is needed first, we’ll agree that with you before proceeding.
Or email hello@drimkoe.com
For procurement: the capability statement — competencies, past performance, scope and engagement terms in a printable document.