On-demand robotics simulation engineering
Send the robot, the environment, and the engineering question. MRPX can take it as a Simulation Sprint or as a work package for an existing engineering team.
MRPX turns robot models, CAD, layouts, and operating scenarios into simulation environments. Typical engineering questions include:
You do not need a complete simulation specification to start. Send the robot, environment, and the decision you need to make.
Start with a defined package of work. Hosting comes later, if you want the scenario to stay up.
Starting at $2,000
One robot. One scenario. One engineering question. One documented result.
Scoped by project, milestone, or work package
External simulation engineering for a team with a larger backlog. MRPX delivers the work package.
Need to keep the validated scenario accessible after delivery? These are continuations, not the entry offer.
Starting at $200/month
Starting at $1,000 add-on
Starting at $6,000
Need a dashboard add-on, extended engineering, or a private deployment? Those remain available as separately scoped work. See pricing or contact MRPX.
You do not need complete files to start a discussion. Depending on the project, useful inputs include:
Potential or scope-dependent outputs — not every project includes every item:
After a project is confirmed, use your account to upload categorized files and track build status.
| Category | What to put here |
|---|---|
| Visual meshes | Appearance geometry (.stl .obj .dae) for rendering |
| Collision meshes | Simplified or dedicated collision bodies |
| URDF / XACRO | Robot structure (.urdf .xacro) |
| CAD | STEP/STP when meshes are not yet split |
| Config files | .yaml .yml .json |
| Dynamics data | Mass, COM, inertia tables or notes |
| Control mappings | Input-to-motion mapping notes and requirements |
| Interface / API docs | SDKs, protocols, message contracts |
| Calibration references | Transforms, reports, calibration data |
| Videos / images | .mp4; .png / .jpg |
| General documentation | README, acceptance criteria, specifications |
Allowed extensions: .urdf .xacro .stl .obj .dae .step .stp .zip .yaml .yml .json .pdf PNG/JPEG images .mp4. Other formats available on request.
Mobile robots, manipulators, inspection/field platforms, warehouse/AMR systems, research robots, and other custom platforms. Scope depends on available models, interfaces, and the defined scenario — not every robot is a standard sprint.
You do not need complete files to start. Ideally URDF/XACRO with mesh files, but we can also work with CAD, photos, videos, dimensions, ROS packages, or a clear scenario description.
Standard fixed-scope Simulation Sprints target 7–10 business days after scope and required inputs are accepted. Larger or more complex simulation projects are estimated separately and may take multiple weeks.
No. Review the simulation from the browser when that helps your team or customer. A sprint can also deliver recordings, results, and other agreed technical outputs.
Yes. A Hosted Validation Twin keeps the environment available for reviews, demos, reruns, and later updates. That is a simulation twin today. A connected operational twin with live telemetry is scoped separately if the business case requires it.
No. MRPX can simulate planned robot or automation behavior so your team finds integration problems earlier. It does not replace full PLC commissioning, safety certification, or professional engineering review.
Connected operational twins are scoped carefully. MRPX does not claim safety-critical autonomous control. Real-robot pathways require customer-side validation, hardware safety systems, and agreed operating procedures.
Hosted access to your validated simulation via browser (when that is the delivery model), maintenance, uptime monitoring, and limited monthly usage. Usage limits depend on compute requirements and simulation complexity.
Send the robot, the scenario, and the engineering question. Files do not need to be complete to begin.
Questions? manuel.retana@mrpxtech.com · Home