Modeloop
A modern model-based design tool
Last verified:
What is Modeloop?
Modeloop is a browser-based model-based design tool that allows users to create dynamic systems visually using block diagrams. Users connect blocks into diagrams, simulate the dynamics instantly in the browser, and generate production-ready C code from their models. The tool runs entirely in the browser with no installation required, making it instantly accessible for experimentation and design work.
The platform features a ROS 2 toolbox that runs in a desktop app, enabling integration with robotics workflows. The ROS toolbox imports .msg and .srv files directly from existing ROS workspaces, provides native Publisher/Subscriber blocks for drag-and-drop topic wiring, supports ROS 2 Humble/Iron/Jazzy with QoS settings, and generates standalone C++ (rclcpp) or Python (rclpy) nodes. It also supports Hardware-in-the-Loop (HIL) testing where users can run models locally while connected to a live ROS network or Gazebo.
Modeloop is designed for robotics engineers, control system designers, embedded systems developers, and anyone working on model-based design who wants a Simulink-style experience without the installation overhead. The model format uses plain, git-friendly text, making it version-control friendly. The tool emphasizes Separation of Concerns architecture, allowing users to model Finite State Machines and observer subsystems separately from core control logic.
The tool is still in early development with an active roadmap, and users need to sign up for a waitlist to access the full ROS workflow desktop app. The browser-based modeling and simulation can be tried instantly without signing up.
Modeloop pricing
Pricing model: Freemium
Free tier available - the browser-based modeling and simulation experience runs entirely in the browser and can be tried instantly at no cost with no installation. The ROS 2 toolbox desktop app requires signing up for a waitlist to access. No specific paid plan pricing information is publicly available as the tool is still in early development.
Modeloop pros
- Runs entirely in browser - no installation required
- Instantly accessible for modeling and simulation
- Generates production-ready C code from block diagrams
- Plain, git-friendly text model format
- ROS 2 toolbox with native Publisher/Subscriber blocks
- Supports ROS 2 Humble, Iron, and Jazzy versions
- Import .msg and .srv files directly from ROS workspace
- QoS settings configuration for ROS 2
- Generates C++ (rclcpp) and Python (rclpy) nodes
- Hardware-in-the-Loop with live ROS network connection
- Debug against real sensor data without compile step
- Drag-and-drop topic wiring for ROS blocks
- Finite State Machine modeling capability
- Separation of Concerns architecture philosophy
- Simulink-style modeling experience in browser
Modeloop cons
- ROS 2 toolbox requires separate desktop app installation
- Browser sandbox cannot speak DDS or connect to live ROS graph
- Still in early development stage
- Full ROS workflow requires waitlist sign-up
- No built-in magic blocks for physical anomaly handling
- Users must build custom state-estimators for hardware issues
- Limited to C code generation primarily
- Active roadmap means features may change frequently
Frequently asked questions about Modeloop
What is Modeloop?
Modeloop is a browser-based environment for model-based design where you connect blocks into a diagram, simulate the dynamics, and generate code. It provides a Simulink-style modeling experience but runs entirely in the browser with models stored as plain, git-friendly text.
Do I need to install anything to use Modeloop?
For the core modeling and simulation experience, no installation is required - it runs entirely in your browser and you can start using it instantly. However, the ROS 2 toolbox runs in a desktop app because a browser sandbox cannot speak DDS or connect to a live ROS graph.
What code does Modeloop generate?
Modeloop generates production-ready C code from block diagrams. For ROS 2 workflows, it generates standalone C++ (rclcpp) or Python (rclpy) nodes with QoS profiles and lifecycle support.
What ROS 2 versions does Modeloop support?
The ROS 2 toolbox supports ROS 2 Humble, Iron, and Jazzy versions, with full QoS settings configuration available.
How does Hardware-in-the-Loop work in Modeloop?
Hardware-in-the-Loop allows you to run the model locally while connected to a live ROS network or Gazebo. You can debug against real sensor data with no compile step during design, which is a significant workflow accelerator.
Can I import my existing ROS workspace files?
Yes, the ROS toolbox imports .msg and .srv files directly from your existing ROS workspace, allowing seamless integration with your current robotics projects.
How do I handle physical anomalies like wheel slip or localization jumps?
Modeloop follows a Separation of Concerns philosophy. Instead of magic blocks, you should create a dedicated State Estimation/Observer subsystem separate from the control logic. You can model a Finite State Machine that monitors signal integrity and transitions from 'valid' to 'faulty' when anomalies are detected, then filter or reconstruct data accordingly.
How do I access the ROS 2 toolbox?
The ROS 2 toolbox desktop app requires signing up for a waitlist. The creator is sharing desktop builds for testing and gathering feedback from people doing real robotics/control work.
What is the model format in Modeloop?
Models are stored as plain, git-friendly text, making them version-control friendly and easy to diff, review, and collaborate on using standard git workflows.
Is Modeloop suitable for production robotics projects?
Modeloop is still in early development and the creator is actively shaping the roadmap. While it generates production-ready C code and has real ROS 2 node generation capabilities, you may want to evaluate what's missing for your specific real project needs before committing to production use.