Yvotronics

Hardware, firmware and robotics engineering

We take a product from brief to factory: the board, the firmware and the motion, as one team.

  • Schematics and multilayer layout
  • Embedded firmware and updates
  • Motor control and robotics
  • Production files and test fixtures
Send a project brief

Six copper layers, one boardScroll to walk through the stack-up

YVO-MB-01, six layers, 1.6 mm

Board to
motion

One
team

Close 3D view of the processor and radio on a Yvotronics board
  • Electronics schematic, layout, bring-up
  • Firmware drivers, protocols, updates
  • Motion motors, sensors, control loops
  • Production fixtures, files, first batch

Most products fail between disciplines. The board is finished but the firmware was written for a different revision. The motor runs on the bench and stalls in the enclosure. The factory receives files nobody has built from. Yvotronics is one team for the electronics, the embedded software and the moving parts, so those seams are ours to close: we draw the schematic with the firmware in mind, write the firmware against the real board, and tune the motion on the mechanism it will drive. What you get is a product that can be built, flashed and tested by someone who has never met us.

What wedeliver

Schematic sheet of the YVO-MB-01 power stage: USB-C input, charger and regulators

Every engagement ends in files you own: schematics, layouts, source code, test fixtures and the pack a factory builds from.

All services

Electronics design

Schematics and multilayer layout from requirements to a board that passes its first power-up. We choose parts with healthy supply and second sources where we can.

  • Power and battery
  • RF and wireless
  • Sensors and analogue

Firmware

Embedded C and C++ on bare metal or an RTOS, with the drivers, protocols and update path a product needs for years, not for a demo.

  • ESP32, STM32, nRF
  • BLE, Wi‑Fi, CAN
  • Over-the-air updates

Motion and robotics

Motor control from the gate driver up: brushless and stepper drives, encoders, IMUs and the control loops that make a mechanism move the way it was drawn.

  • Field-oriented control
  • Kinematics and trajectories
  • Limits and safety

Prototype to production

Design for the factory that will build it: manufacturability reviews, test fixtures, flashing and provisioning tools, and the documents a line needs.

  • DFM and DFT
  • Test jigs
  • Production pack

How a project runs

Five stages, each with a written result you can show your team or your investors. Open a stage to see what happens in it and what you get at the end.

System block diagram of the YVO-MB-01: power, motion and connectivity around the processor

Scope

We read your brief, ask the questions that change the architecture, and return a written scope with modules, risks and a price.

  • Scope document
  • Block diagram
  • Cost and schedule
Layout of a six-layer board drawn by Yvotronics: BGA fan-out, a tuned differential pair and an antenna keep-out

Design

Schematic, layout, mechanical fit and firmware architecture happen together, reviewed against the scope before anything is ordered.

  • Reviewed schematics
  • Layout and Gerbers
  • Firmware plan
A firmware build, twelve passing unit tests, flashing, and the board booting on the serial console

Bring-up

First boards on the bench: power rails, clocks, peripherals, then the first firmware image. Every finding goes into a report.

  • Bring-up report
  • Working first prototype
  • Measured results
Firmware release history from v2.0.0 to v2.4.5 with changelogs and the board revision each targets

Iterate

Field the prototype, measure, fix the board and the code, and repeat until the specification is met rather than approached.

  • Revised boards, rev A to rev B
  • Tagged firmware releases
  • Test logs per release
A panel of six YVO-MB-01 boards on a pick-and-place line, drawn by Yvotronics

Production

Hand-off to the factory with the files, fixtures and flashing tools it needs, and support through the first batch.

  • Production pack
  • Test fixture
  • First-batch support
System block diagram of the YVO-MB-01: power, motion and connectivity around the processor
System architectureScope
Product requirements table for the YVO-MB-01 with targets, verification method and status
Requirements you can test againstScope
3D view of the YVO-MB-01 board drawn by Yvotronics: black solder mask, gold pads, the processor, radio and connectors in place
Multilayer boards, ready to buildHardware
C++20 firmware in an editor: the field-oriented current loop of the YVO-MB-01 motor controller
Firmware in modern C++Firmware
Close view of a BGA fan-out with dog-bone vias, from a Yvotronics layout
Fine-pitch BGA fan-outHardware
A collaborative robot arm on a workbench with its teach pendant
Robot arms and grippersRobotics · photo: Wikimedia
Schematic sheet of the YVO-MB-01 power stage: USB-C input, charger and regulators
Power stages and chargingHardware
An open strain-wave gear of the kind used in robot joints
Joint drives and actuatorsRobotics · photo: Wikimedia
A firmware build, twelve passing unit tests, flashing, and the board booting on the serial console
Tested on the real boardFirmware
Firmware release history from v2.0.0 to v2.4.5 with changelogs and the board revision each targets
Versioned releases, v2.4.5 and onFirmware
Layout of a six-layer board drawn by Yvotronics: BGA fan-out, a tuned differential pair and an antenna keep-out
Layout from schematic to GerbersHardware
A panel of six YVO-MB-01 boards on a pick-and-place line, drawn by Yvotronics
Panels and line setup for productionProduction

The five questions a founder asks us first, answered the way we answer them on a call.

Common questions

Can you take only the firmware, or only the board?

Yes. Many projects arrive with one half done. We work from your schematics or your code base, and we say early if something there will limit the result.

What do we need to send to start?

A paragraph is enough. A spec, a sketch, a photo of the prototype or a link to a similar product shortens the first call. We reply within two working days with questions or a scope.

Who owns the design?

You do. Schematics, layouts, source code and production files are delivered to you and licensed to you in full. We keep nothing you would need to go elsewhere.

How do you price work?

Scoped projects get a fixed price per stage. Open-ended work, such as supporting a line or extending a code base, is billed by the day. Both are in writing before we start.

Do you build the hardware yourselves?

Prototypes, yes: we assemble and test the first boards. Volume production goes to a factory, yours or one we recommend, with our fixtures and files.

Have a board in mind?

Send a paragraph about the product, the stage it is at and when it has to ship. We reply within two working days with questions or a scope.

Send a project brief
  • Include what the product does and for whom
  • Include where it stands: idea, prototype, product
  • Include the date it has to ship
  • Attach a sketch, a spec or a photo, if any

Send a project brief

Tap what the product needs, add a few lines in your own words, leave an email. That is the whole form.

What the product needs
Stage of the product

We reply within two working days. Your brief stays between us.