Whether you're tracking multiple robots, dealing with local-to-production issues, or waiting on C++ builds, this month we streamlined the workflows that matter most.
Multi-machine fleet dashboards
Monitor your entire fleet from a single dashboard. Set up widgets to pull data from multiple machines, visualize trends across your fleet, and filter for specific machines or time ranges. Expanding on teleop's single-machine view, dashboards let you monitor every robot simultaneously—including spotting outliers, tracking fleet health, and identifying trends without switching between machines.
Temperature monitoring dashboard widget showing two sensor readings over time.
Dashboard GPS widget showing machine locations on a map view.
Simplified resource names in motion APIs
Motion APIs now accept simple names instead of complex identifiers. Where you previously had to specify "rdk:component:arm/foo" to control a robot arm, you can now just use "fooArm". The system automatically handles name conflicts and lets you add prefixes like "robot2.fooArm" when controlling multiple robots. Note: Update both SDK and viam-server, then switch your code to the new naming format.
10x faster C++ builds with Conan server
C++ build times just dropped from an hour to under 10 minutes. We set up a Conan server that caches prebuilt SDK dependencies so you don’t have to rebuild the same libraries every time. Add the remote with conan remote add viamconan and your builds automatically use the cached dependencies. Especially useful if long C++ build times have been blocking your module development.
November brought more platform improvements designed to streamline your robotics development. Questions or feedback? Drop by our Discord to let us know what friction points we should tackle next.
Find us at our next event
Error! No upcoming events found. Please check back later!
