feature article
Subscribe Now

Let’s Get (a) Physical

RoweBots’ MedicalOS Does Just What is Says on the Box

“UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity.” — Dennis Ritchie

You can turn a sailboat around faster than a battleship, and a minnow changes course quicker than a whale. Small-fry RTOS company RoweBots has made a sharp pivot and set its compass toward bright horizons in the medical-devices field.

If you’ve heard of RoweBots at all, it’s likely because of Amelia’s interview a few months ago, or by way of Unison OS, an early POSIX-compliant RTOS intended for small embedded systems. The little Canadian/German company has been around for 30-odd years, never growing beyond a few dozen employees. It’s definitely a small fish in a big pond, but a happy fish nonetheless. Its customers are happy, too, which is more important.

But like any lifeform, success comes from specialization, and RoweBots has decided that a generic, Linux-like RTOS for “whatever” wasn’t going to get the company to its next stage of evolution. It was time to narrow the corporate focus and concentrate on a few specific product areas. Thus did Unison split into WearableOS, ConsumerOS, VehicleOS, and MedicalOS. No prizes for guessing which product niches the company decided to inhabit.

You could argue that some of the value in any operating system, large or small, is the time it saves you in developing applications to sit atop said OS. It’s not just a technology solution that makes the clocks tick and the interrupts interrupt; it’s a time-saver. The more familiar the OS, the better. And the more prepackaged it is, the better. Do-it-all OSen that come with myriad optional components are nice in concept, but a big waste of time when you’re focused on a single chore. Why spend time discarding the vehicle-related software components – interesting as they are – when you’re developing a medical device? Sure hope I didn’t pay extra for all that superfluous code.

That’s why Kim Rowe, CEO of RoweBots (get it?) thinks MedicalOS will be a great time-saver for those developing small, embeddable (in the medical sense) devices. It’s not the right OS for CAT scanners, but a good choice for concussion-logging crash helmets. In fact, one RoweBots customer has developed just that: a football helmet that senses and logs blows to the head using accelerometers, microcontrollers, and nonvolatile storage.

What makes an RTOS medical-specific, apart from leaving out the automotive, satellite, rack server, and industrial robotics features? Small size, low power consumption, and preconfigured device drivers, says Rowe. Wearable devices are physically small, and always battery-powered, so a full-fledged OS wastes storage space, CPU cycles, and energy. Better to use an RTOS that was designed from the outset for limited resources, and specifically for the resources one might find in a wearable medical device. No more, no less.

MedicalOS also comes with a ready-made batch of device drivers for relevant peripherals, like the aforementioned accelerometers as well as sensors you’re likely to see in medical (but not industrial or automotive) applications. Naturally, developers can add their own devices drivers, too, just as with any OS. But if a half-dozen of your favorites are already preconfigured, why not save the time?

RoweBots hasn’t strayed far from its Unison roots with MedicalOS. It’s still a Unix-like RTOS with most of the functions and APIs that a programmer would expect. “Think of it as Embedded Linux… for MCUs.” Says Rowe. It’s not an all-singing, all-dancing embedded Linux, but it’s close enough that Linux programmers will feel immediately at home.

The “…for MCUs” part is important, because MedicalOS (and its other market-specific brethren) runs on some really small MCUs, not just the higher-end devices. Chips like the Renesas M16C family, Microchip’s PIC24, Xilinx MicroBlaze, and NXP’s Cortex-M3 parts are all supported right out of the box.

For all its small size, MedicalOS doesn’t skimp on modern networking features (if you want them). Exciting buzzwords like SNMP, MQTT, IPv6, 6loWPAN, RESTful, and others all make the features list. ARM’s recently announced Platform Security Architecture also made the cut. Finally, cloud services like AWS, Azure, and Watson are available, too.

What’s the price for all this? It depends. Rowe describes his company’s pricing as “flexible.” There could be an upfront licensing fee; there might be royalties; there might be both. Since many of RoweBots’ customers are small firms without eight-figure R&D budgets, the company offers a number of payment schemes. Bigger users tend to prefer a one-time license fee and never worry about unit volumes after that. Startups want to conserve precious capital, so they opt for the back-loaded royalty-bearing model. Just about any payment structure is fine, and RoweBots understands that some customers will never generate any significant revenue at all. In fact, they plan for it. Your first 99 units are free, no matter what.  Now that’s a medical plan everyone can agree on.  

One thought on “Let’s Get (a) Physical”

Leave a Reply

featured blogs
Oct 21, 2020
You've traveled back in time 65 million years with no way to return. What evidence can you leave to ensure future humans will know of your existence?...
Oct 21, 2020
We'€™re concluding the Online Training Deep Dive blog series, which has been taking the top 15 Online Training courses among students and professors and breaking them down into their different... [[ Click on the title to access the full blog on the Cadence Community site. ...
Oct 20, 2020
In 2020, mobile traffic has skyrocketed everywhere as our planet battles a pandemic. Samtec.com saw nearly double the mobile traffic in the first two quarters than it normally sees. While these levels have dropped off from their peaks in the spring, they have not returned to ...
Oct 16, 2020
[From the last episode: We put together many of the ideas we'€™ve been describing to show the basics of how in-memory compute works.] I'€™m going to take a sec for some commentary before we continue with the last few steps of in-memory compute. The whole point of this web...

featured video

Demo: Low-Power Machine Learning Inference with DesignWare ARC EM9D Processor IP

Sponsored by Synopsys

Applications that require sensing on a continuous basis are always on and often battery operated. In this video, the low-power ARC EM9D Processors run a handwriting character recognition neural network graph to infer the letter that is written.

Click here for more information about DesignWare ARC EM9D / EM11D Processors

Featured Paper

The Cryptography Handbook

Sponsored by Maxim Integrated

The Cryptography Handbook is designed to be a quick study guide for a product development engineer, taking an engineering rather than theoretical approach. In this series, we start with a general overview and then define the characteristics of a secure cryptographic system. We then describe various cryptographic concepts and provide an implementation-centric explanation of physically unclonable function (PUF) technology. We hope that this approach will give the busy engineer a quick understanding of the basic concepts of cryptography and provide a relatively fast way to integrate security in his/her design.

Click here to download the whitepaper

featured chalk talk

PolarFire SoC FPGA Family

Sponsored by Mouser Electronics and Microchip

FPGA SoCs can solve numerous problems for IoT designers. Now, with the growing momentum behind RISC-V, there are FPGA SoCs that feature RISC-V cores as well as low-power, high-security, and high-reliability. In this episode of Chalk Talk, Amelia Dalton chats with KK from Microchip Technology about the new PolarFire SoC family that is ideal for demanding IoT endpoint applications.

Click here for more information about Microchip Technology PolarFire® SoC FPGA Icicle Kit