For today's spotlight, we invited Aditya Kamath, a robotics systems engineer, to talk to us about his latest project – a robot platform to help the next generation of roboticists learn ROS. As someone who’s spent years tinkering with prototyping tools, computers, and electronics, Aditya had an obvious solution for countering his lockdown boredom – building (multiple!) robots from scratch. We discuss the exciting milestones he’s reached, and his future plans to help aspiring roboticists follow in his footsteps.

Our team first stumbled upon your work when we saw you using Foxglove Studio to visualize your robots. Tell us a little bit about yourself, and how you first became interested in robotics!

I am Aditya Kamath, an Embedded / Robotics Systems Engineer based in Eindhoven, the Netherlands. I currently work as an Embedded Systems Consultant, designing embedded software for complex machines and mechatronic components. I keep my passion for robotics alive by tinkering around with robotic builds, microcontrollers / single-board computers, and rapid prototyping tools like 3D printing.

Aditya Kamath

I earned my Bachelor’s in Electronics and Communication Engineering from MIT Manipal in India (2014). Then, I received a Master of Science (MSc) in Systems and Control and a Professional Doctorate in Engineering (PDEng) in Mechatronic Systems Design from TU Eindhoven (2019). Despite studying many different things, the common denominator in my education and extracurricular experiences has always been the field of autonomous robotics.

What exciting robotics projects are you working on now?

With all my spare time during the COVID-19 lockdown last year, I decided that I wanted to build some robots to experiment with ROS. I also saw this as an opportunity to learn more about 3D SLAM and depth and point cloud processing. The first several months, I focused on building a few Jetson Nano-based ROS robots using some rapid prototyping tools. For one, I used the NVidia JetRacer, an autonomous AI racecar with Ackermann steering, with custom add-ons. For another, I used the NVidia JetBot, an open source robot with differential drive geared towards educational purposes, again with custom add-ons.

Then at the start of this year, I was able to get a LIDAR and an OAK—D camera. With these exciting new supplies, I decided to use everything I had learned the previous months to design and implement my own ROS 1 robot platform from scratch. I named the project AKROS, a working name that combines my initials and ROS – for until I come up with something more original.

robot with LIDAR and camera
The robot with the new LIDAR and OAK—D camera attached.

All the software for AKROS (ROS Noetic) runs on a Raspberry Pi 4. It has a mobile base with omni wheels and four-wheel drive, with each wheel powered by a motor that computes the robot's odometry using encoders. The mounted RPLIDAR A2 provides a 2D laser scan, while the OAK—D camera provides RGB images, stereo depth images, and spatial object detection outputs using the on-board DepthAI module. The Intel Realsense T265 tracking camera provides simultaneous localization and mapping.

What development tools do you use for iterating on AKROS?

I do all my development using JupyterLab – the server runs on the Raspberry Pi, and I open my workspace from any browser on the network. However, this method limits you to the terminal, so for tools like RViz, I have to install and configure ROS on my Windows laptop. After that, I still have to go through three to four additional steps to launch RViz, which unfortunately cannot run directly on Windows. On top of all this, it's easy to forget setting the necessary environment variables to connect to the remote ROS master. The whole process is very annoying and manual.

Once I started playing around with Foxglove Studio, I thought it was a really convenient way to visualize ROS topics and messages from a remote desktop. I love that it works on Windows, because that means I don’t have to go through the process of launching ROS from Windows, setting environment variables, and finally launching RViz. Foxglove takes care of all this for me!

A demo of AKROS's SLAM and object detection capabilities, visualized in Foxglove Studio.

Using Studio on Windows is as easy as using Rviz on a Ubuntu laptop. Now, I can run my ROS launch files from the JupterLab terminal in my browser, then open up Foxglove Studio to start visualizing everything I want – no more complex setup process.

We're so glad to see that Studio has been able to streamline your development process. What do you have planned next on your roadmap?

While this robot fulfills my personal learning goals, I want to take AKROS and develop it into a product that could be used to teach robotics or to perform research in applications like control systems, computer vision, and AI. In fact, I am currently in talks with university students and professors to understand their requirements for a ROS robot platform. Eventually, I want to design a polished product for these end-users, instead of a hacky prototype for just myself.

At this point of time, I am still in the development process. I have two main short-term goals – to set up the ROS navigation stack with the RPLIDAR’s laser scans and Intel Realsense tracking camera’s odometry, and to set up 3D mapping with the OAK-D camera. It's been an iterative process – I recently had to completely redesign my navigation module to accommodate my tracking camera.

unmounted and mounted navigation module
Aditya spent quite some time iterating on his navigation module - adding components, fine-tuning its assembly, redesigning the frame - before mounting it on the rest of his robot.

Do you have any advice for someone who's interested in getting into robotics, either as a hobbyist or startup founder?

The best experience you can get is by building your own robot –  it’s also much more fun than doing an online course or working with a simulation. There are lots of (free and open source) resources out there that will teach you the fundamentals step by step, and cheap robot kits are abundant online. By building your own physical robot, you learn a lot more about robotics than just how to program.

To keep up with Aditya's latest work, check out his project updates on his Twitter, Instagram, and blog.

If you're a university professor or student interested in collaborating with Aditya for his AKROS project, you can get in touch with him directly on Twitter.

This interview has been edited and condensed for clarity.


We sat down with Steve Crowe, the editorial director of The Robot Report, to pick his brain on the state of robotics. As someone who’s covered the industry for about a decade, Steve has seen a lot of ideas (and companies) come and go. We discuss the major industry trends he’s reported on over the last decade, and where he sees the field going in the next ten years.

As the editorial director at The Robot Report, you write about the business and applications of robotics. Can you tell us a little bit about what sparked your initial foray into the world of robotics?

I didn't go to school for robotics or have any interest in the industry before my career path steered me in that direction. I’m a trained journalist, and the publishing company I was working at happened to own a robotics brand, Robotics Business Review. After several years of building out another brand, I was asked to steer that ship to accelerate its online growth. Then in early 2018, my colleague Dan Kara reached out to me as he was growing the robotics editorial team at WTWH Media – that’s how I got started working on The Robot Report.

It’s now been about a decade since I started covering robotics – it’s a ton of fun. I'm located in Boston, which is certainly in the top three robotics clusters in the world, along with California and Austin. It's a great community, a pretty small community of folks.

What does a typical day for you look like?

If I have to summarize what I do, it's educating the robotics community on how to create better, more intelligent systems. Whatever the medium is, whatever the format of the content is, we're trying to build a relationship with stakeholders in the robotics community and gain their trust. We show them that they can come to us to learn about the innovations driving the industry forward. They can come to our events to network with each other, or to learn about the products that will help them create the next generation of commercial robotics systems.

As far as what my typical day looks like, it depends. This week we announced the winners for our annual RBR50 Robotics Innovation Awards. I also moderated a webinar with Rich Mahoney, the former director of SRI International and current VP of Research at Intuitive, the world’s leading robotic assisted surgical company.

This is on top of producing engaging content across our 4 websites – we’ve built a diverse portfolio and grown the group pretty significantly. Our flagship brand The Robot Report covers engineering news, emerging technologies, and investments and acquisitions. Collaborative Robotics Trends teaches companies about the benefits of collaborative robotic arms. Robotics Business Review, the original robotics brand I’d worked on, provides breaking news and informed analysis on the robotics and automation sectors. And finally, Mobile Robot Guide educates companies about the benefits of autonomous mobile robots (AMRs), automated guided vehicles (AGVs), and other mobile robots in logistics and supply chain environments.

How have you seen the industry evolve in the last several years? Are there any particularly interesting industry trends that you’ve seen emerge?

For so long, robotics referred to the industrial robot arms at manufacturing plants – particularly automotive plants. As enabling technologies came down in price and industries were educated about the benefits of adopting these systems, robotics has expanded out of those plants and research labs into a lot of different areas.

One industry that’s attracting more players is food services. Miso Robotics, for example, is automating kitchen operations within fast food restaurants. With COVID and other airborne and foodborne illnesses, you’re seeing more companies trying to make the food preparation process safer.

Miso Robotics' Flippy is an AI-powered kitchen assistant boosting performance and safety in restaurants.

Construction and agriculture are two markets that have often been talked about as being ripe for automation, and now it seems to be happening. Several companies have been developing picking robots to help farms with the harvesting process. They’ve built pretty sophisticated AI that uses vision algorithms to understand when different types of produce are ready to be picked, and what exact mechanism is needed to harvest them.

E-commerce is another area where robotic systems are currently gaining a lot of traction. Mobile robots that transport items throughout a facility are one of the hottest markets right now. It was already growing at a pretty good rate before 2020, but the pandemic introduced more people to online shopping. The only way for many e-commerce players to keep pace with the demand was to automate parts of their operation. Amazon’s own AMRs, for example, have been vital in helping them keep up with the demand.

What do you see as the industry’s biggest technical challenge?

I'm pretty excited to see how the legged robotics market develops – Boston Dynamics and ANYbotics are interesting ones to watch. There's been a lot of skepticism about the benefits of legged robots – they’ve been under research and development for decades, but nobody ever really thought that they were commercially viable or that there was a compelling use case for them. But within the last year, several quadruped robots have been commercialized, the most well known one being Boston Dynamic’s Spot. Humans have teleoperated this system to inspect sites around the Chernobyl nuclear power plant disaster for radiation. It can even be set up to perform autonomous missions to keep humans out of harm's way – a great use case for robotics.

Boston Dynamics' Spot allows users to automate routine inspection tasks and capture data safely and accurately.

As for bipedal robots, Agility Robotics has a fascinating one named Digit. They've studied animals – in particular, ostriches – to inform their locomotion design and planning algorithms. With Digit, they're targeting not last mile delivery, but something like last hundred feet delivery. They've done some crazy tests with partners like Ford where these robots get out of the car, deliver a package to a door, and then reload themselves into the car.

Agility Robotics has partnered with Ford to test doorstep deliveries with its bipedal robot Digit.

These robots have very sophisticated locomotion capabilities – they can climb stairs and navigate over all sorts of terrain – giving them a major advantage over wheeled robots. The construction, oil and gas, mining industries are all trying to figure out how to put these platforms to use. We’ll have to wait and see whether they prove themselves useful outside the lab.

What are the major business hurdles that robotics startups face today?

A lot of this stuff is hardware-centric – it just takes so much capital to develop these systems that don't have a tremendous amount of customers. For example, Locus Robotics is an AMR company that’s been around for about 7 years and recently raised $150 million in Series E funding. They’ve said that their next step is to IPO, but here’s the thing – they have roughly 40 actual customers. It takes an incredible amount of time and money to develop these things, to hire the incredibly smart and hardworking people to iterate on these systems. Building robots and gaining any traction is incredibly challenging.

Locus Robotics offer automated warehouse robots that increase productivity and order accuracy.

Interoperability is another hurdle that's talked about a lot now. Mobile robots developed by different companies often operate in roughly the same way, but they all have their own proprietary communication systems and operating systems. So there's an emerging problem with adopting heterogeneous fleets of robots from different manufacturers, since these robots must operate together in the same environment, but can’t communicate with each other on their own. If you have robots from 4 different vendors that you want to reprogram in any way, there’s a good chance you have to learn 4 different operating systems. It makes the whole operation much more challenging for the end user.

Thankfully, there's a lot of work being done around setting a standardized communication protocol. For example, READY Robotics is creating a universal operating system so that users only have to learn one approach, regardless of how many different robotics vendors they choose. Open Robotics, the group behind the Robot Operating System, has been collaborating with a hospital network in Singapore to develop a fleet management system that allows their healthcare robots communicate with each other. These robots were eventually able to recognize each other’s movements as they navigated hallway traffic and called elevators to travel between floors.

Open Robotics has been collaborating with Singapore’s Centre for Healthcare Assistive and Robotics Technology (CHART) to develop an open source infrastructure framework that simplifies cross-fleet collaboration.

Have there been any sectors of the industry that haven’t been able to live up to the hype?

There hasn’t been much progress in the consumer market. iRobot was very successful with its robot vacuums, but there really hasn't been much progress with other robots for your home. iRobot had been talking about a robot lawnmower for over a decade, and they finally teased it last year. But they eventually shelved it, citing fallout from the COVID-19 pandemic. Social robots have often been hyped as the next in-home consumer robot, but it's been a disaster of an industry with a few high-profile failures.

One consumer robot company that does seem to be having some success is Embodied. Their Moxie robot helps young kids build social-emotional skills, by recognizing what a particular child is struggling with and then serving up content that might be beneficial to that child. I think they’ve been successful, because they weren't trying to be an all consumer companion robot – they honed in on one specific application.

Moxie uses play-based activites created by child development experts to promote children's mental well-being.

What are some of your favorite robotics projects out there in the wild today?

I love self-driving cars. I love following Cruise, Waymo, and the other leading autonomous vehicle developers. It's just a fascinating concept and a super challenging problem from an engineering standpoint. There are so many people who are killed in careless car accidents, so if these systems could be scaled and deployed commercially all over the world, that would be tremendously valuable to society.

There are also so many applications for an autonomous vehicle outside of a robo taxi. I've seen use cases where autonomous luggage cart vehicles operate on fixed repeatable routes – at a certain terminal, multiple times a day. There’s opportunity there.

British Airways started trials of driverless luggage carts at Heathrow Airport in 2019 to speed up loading carts.

And I’ve said it before, but the realm of legged robotics is super exciting as well. I'm sure you’ve seen the viral videos of Boston Dynamics’ two-legged robot doing gymnastics routines and going for a jog. But we have to see how that progresses. That's what gets me fired up – seeing these challenges that are still left for us to solve.

What advice do you have for someone who's interested in entering the robotics field, whether as an entrepreneur, engineer, or investor?

If you’re starting a robotics startup – don't create a solution that's looking for a problem. Don't just go build a supply chain robot because you know that’s a really hot market right now. Find a problem that has yet to be solved or automated, and figure out how to do that. So many companies we've reported on have gone out of business, because there was never a great use case for what they built. They took a variety of enabling technologies that had improved and come down in price over the years, and fused them together. But the problem it was solving was never really there. They were so concerned about building the coolest product with the coolest tech that they forgot about their end user.

The startups that are still around and getting customers and funding have that one thing in common – they really understand the problem that their user is trying to solve. An example is 6 River Systems, which was acquired by Shopify for almost half a billion dollars. Its executives may have had some robotics knowledge, but their expertise really lay in the logistics business. They had great firsthand knowledge of the challenges that supply chain operators face on an everyday basis. They could think clearly about the tools and system that they could develop to help these operators overcome those challenges.

6 River System's Chuck uses machine learning and artificial intelligence to fulfill orders more efficiently.

Also, talk to as many people as you can. Find people who have the domain knowledge you want to learn, and pick their brains – that's really the key. It’s a pretty small community, and most people that I've met in my 10 years in the industry are super passionate about what they do. They’d love to talk to you about what they're working on, or about the business and technological challenges they face on a regular basis. They want nothing but to move this industry forward – to get more robots out in the world helping people overcome daily challenges.

A lot of the general public is afraid of these systems, as they start to appear out there in the real world. Sci-fi over the years has probably done a major disservice to the industry. But so many folks in the industry want to reverse that misconception and educate people about how these systems actually work and how they can help us tackle daily challenges.

To keep up with Steve’s latest work, you can follow him on Twitter or read his pieces on The Robot Report.

This interview has been edited and condensed for clarity.


Earlier this year, we announced support for playing back ROS 2 bags in Foxglove Studio. We were thrilled to see the community's enthusiasm for broader ROS compatibility, so in the weeks since that release, we've been working hard to expand Studio's ROS 2 support.

Today, we're excited to announce that v0.18 of Studio allows you to connect to a live ROS 2 stack with two new data source options – ROS 2 (beta) and ROS 2 Rosbridge. Whether you're running ROS on your local machine or a physical robot, you can now connect directly to your ROS 2 nodes to visualize their data in real-time.

Share your feedback

While we're approaching feature parity with ROS 1, our long-term vision for ROS 2 compatibility is still evolving. Beyond the preliminary support in this release, we're still working with the larger ROS community to bridge the gap between what we can achieve now and the upstream work that remains (like message definitions at runtime and in bag files).

With that said, we're excited for you to test this feature out in the field, and to give us feedback on how we can improve and expand on it. Feel free to share your thoughts in Slack, file bug reports and feature requests on GitHub, or message us directly on Twitter.

If you experience any issues with native ROS 2 connections, you can always fall back to our more battle-tested ROS 2 Rosbridge connection option. Check out our docs for more details on how to connect to all our supported data sources.


Announcing Live ROS 2 Support

Read more:

Ready to try Foxglove?