QRobot is a knowledge service for developers — start with a free trial of 3 credits, no card needed. Ask for designs, code, BOMs and proposals; answers cite the source documents they draw on and say plainly what is verified, reported, or newly proposed.
The platform the archive describes: a Raspberry Pi 4 application processor linked over UART to an STM32 motion controller, with mobile commands, sensing, user interaction and a power subsystem.

Controller boards, power distribution, UART/BLE links between Raspberry Pi and STM32.
Mechanism concepts and design proposals. Artifact availability is distinct from validated, matched CAD.
Reusable STM32 / embedded excerpts and adaptations to your controller.
Pi-side services, startup sequencing, audio/video handling and troubleshooting.
Each request uses QRobot credits (separate from AI model tokens). New accounts get 3 free credits once; see pricing for costs and plans.
Start free. Paid monthly plans are coming soon.
Requests use QRobot credits — usage credits for this service, separate from AI model tokens. Prices in USD, before applicable taxes. Paid plans are not available yet: no card is collected and nothing is charged today.
One time per new account. No payment card, no automatic subscription. Full available knowledge with the same evidence and source limitations. Enough for 3 general questions or 1 design/code request.
Before applicable taxes · monthly plan
10 QRobot credits / month
For occasional questions and a design or code request now and then.
Before applicable taxes · monthly plan
30 QRobot credits / month
For active development: regular design, code and BOM requests.
Before applicable taxes · monthly plan
80 QRobot credits / month
For heavy individual use across designs, code, BOMs and proposals.
Top-up (coming soon): US$30 for 10 additional credits, one-time — available only with an active paid monthly plan.
You see the cost before sending. Completed answers (including clarifying questions) are charged; failed or empty answers are refunded.
| General question or best practices | 1 credit |
| Electronic or mechanical design, firmware or software code | 3 credits |
| Suggested BOM or technical proposal | 5 credits |
Covered: Raspberry Pi / STM32 architecture, UART and BLE links, startup, audio/video, author-reported power observations, implementation cards and troubleshooting. Not yet established: matched mechanical CAD, current schematics and BOM, or a verified deployed baseline. No evidence for ROS2/MoveIt industrial arm planning, validated collision safety or commercial reliability — general proposals in those areas are offered with explicit limitations. Nothing here is a hardware test result.