STM32F746 Cortex-M7 control board with DYNAMIXEL TTL/RS-485, CAN, UART, USB OTG, mixed-signal I/O and onboard inertial sensing
Compute & Control · Open-source robot control board
OpenCR1.0
The exact TurtleBot3 Burger controller-board identity. Public hardware specifications expose controller, I/O and power boundaries, while the installed firmware and the MPU9250-to-ICM-20648 hardware transition require unit-level evidence.
ROBOTIS OpenCR 1.0 · Also: OpenCR1.0, OpenCR 1.0
What this record can support today.
Coverage is computed from published, non-unknown fields. It measures the record—not product quality—and makes missing procurement evidence explicit.
Engineering field coverage40%
4 of 10 selected fields published
- Official product sourcepublished
- Lifecycle statepublished
- Mechanical dimensions / mass / mountingmissing
- Environmental operating limitsmissing
- Compute performance boundarymissing
- Memory and storagemissing
- Power mode / inputpublished
- I/O and expansionpublished
- Software / OS supportmissing
- Thermal design boundarymissing
Procurement field coverage15%
2 of 13 selected fields published
- Official product / sales routepublished
- Lifecycle statepublished
- Exact orderable SKU / part numbermissing
- Price with region, currency and quantitymissing
- Lead time with check datemissing
- Commercial availability / stock statemissing
- Minimum order quantitymissing
- Authorized distributor / sales channelmissing
- CAD / STEP / interface drawingmissing
- Certification with identifiermissing
- MTBF / failure / reliability datamissing
- Warranty termsmissing
- PCN / EOL / replacement noticemissing
Coverage measures whether a selected public field is present with non-U evidence. It is not a product score, compatibility result, certification, availability confirmation or procurement recommendation. Download the complete readiness coverage JSON →
Exact-model responsibility-party BOM crosswalk.
This edge requires a pinned robot BOM identity and an exact RCI component record. It remains separate from as-built inspection, compatibility and performance evidence.
Robot BOM → exact component
TurtleBot3 Burger
The pinned TurtleBot3 Burger responsibility-party parts list publishes “OpenCR1.0” in the Burger column with quantity 1. The RCI component catalog independently represents that exact OpenCR1.0 board identity from the official ROBOTIS e-Manual.
Published quantity: 1. One board is published for the selected Burger configuration. RCI did not inspect a serialised board, populated IMU revision, bootloader or flashed firmware image.
Boundary: This relation establishes an exact public-BOM board identity only. It does not prove the MPU9250 or ICM-20648 hardware era, firmware state, electrical compatibility, bus timing, current supply, endorsement or physical validation.
Robot BOM → exact component
TurtleBot3 Waffle Pi
The pinned TurtleBot3 Waffle Pi responsibility-party parts list publishes “OpenCR1.0” in the Waffle Pi column with quantity 1. The RCI component catalog independently represents that exact board identity from the official ROBOTIS e-Manual.
Published quantity: 1. One board is published for the selected Waffle Pi configuration. RCI did not inspect a serialised board, populated IMU revision, bootloader, flashed firmware or electrical state.
Boundary: This relation establishes an exact public-BOM board identity only. It does not prove firmware state, electrical compatibility, bus timing, current capacity, installed serial, endorsement or physical validation.
1 bounded physical-evidence record.
Publisher independence, identity precision and measurement scope vary by row. Results remain bounded by the disclosed specimen, setup, workload and metric; an inconclusive mapping is evidence associated with the catalog model, not verification of a manufacturer claim.
| Measured result | Conditions | Claim mapping | Source |
|---|---|---|---|
| Independent OpenCR-based real-robot experimentindependent_real_robot_experiment | OpenCR controlled the physical TurtleBot3 platform in real teleoperation trialsReal TurtleBot3 Burger, obstacle course and VR-assisted teleoperation; board-level timing and power were not isolated. | supportedThe physical TurtleBot3 experiments independently establish operation of OpenCR 1.0 as the real robot controller, without isolating board timing or electrical limits. | Virtual Reality-Based Interface for Advanced Assisted Mobile Robot Teleoperation ↗Section 3 physical platform and real experiments Checked 2026-08-26 |
Reported values, conditions attached.
Evidence state describes the claim—not the prestige of the company or document.
| Claim | Reported value | Condition / boundary | State | Source |
|---|---|---|---|---|
| Microcontrollermcu | STM32F746ZGT6; 32-bit ARM Cortex-M7 with FPU; 216 MHz; 462 DMIPS | Manufacturer specification. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Onboard inertial sensoronboard_sensors | ICM-20648: 3-axis gyroscope, 3-axis accelerometer and digital motion processor | New hardware; the manual states that the discontinued MPU9250 was replaced in 2020. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Digital I/Odigital_io | 32 Arduino-connectivity pins; 4 × 5-pin OLLO; 18 GPIO; 6 PWM; 1 I2C; 1 SPI | Published connector/function counts. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Analog inputsanalog_input | 6 ADC channels, maximum 12-bit | Manufacturer specification. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| USB interfaceusb | 1 × Micro-B USB 2.0 with host, peripheral and OTG support | The e-Manual also lists USB DFU programming support. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| DYNAMIXEL portsdynamixel_ports | 3 × TTL; 3 × RS-485 | Published physical-port counts; actuator protocol and firmware compatibility remain separate. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| UART portsuart | 2 ports | Manufacturer specification. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| CAN portscan | 1 port | Manufacturer specification; no end-to-end bus timing or application-protocol validation is implied. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Input power sourcesinput_power | 5 V USB VBUS or 5–24 V battery/SMPS | Default references are 11.1 V 1,800 mAh Li-Po and 12 V 4.5 A SMPS. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Output-power railsoutput_power | 12 V up to 4.5 A; 5 V up to 4 A; 3.3 V up to 800 mA | The manual limits combined 12 V and 5 V port consumption to 55 W. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Board dimensions and massphysical | 105 × 75 mm; 60 g | Board-only published dimensions and weight. | M · Manufacturer claimed | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Installed TurtleBot3 firmware identityinstalled_firmware_identity | Not published in cited public evidence | RCI checked the cited official product documentation on the verification date.The cited TurtleBot3 BOM fixes the board identity but does not publish a serialised board dump or one exact flashed-firmware digest for every unit. | U · Unknown | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
| Independent exact-board validationindependent_board_validation | Not published in cited public evidence | RCI checked the cited official product documentation on the verification date.No RCI physical OpenCR board, firmware image, electrical measurement or complete robot run has been recorded. | U · Unknown | ROBOTIS OpenCR 1.0 e-Manual ↗Introduction, board specifications, power boundaries and hardware-revision sensor note · Live e-Manual observed 2026-08-13 Checked 2026-08-13 |
Known limits
What this record does not prove.
- OpenCR1.0 hardware spans at least the MPU9250 and ICM-20648 sensor eras; a board name alone does not identify the populated IMU.
- Port availability does not prove firmware support, bus timing, electrical compatibility or a successful robot integration.
- The TurtleBot3 crosswalk is a pinned public-BOM relation, not an as-built, serial, endorsement or physical-test claim.