We currently offer support for ROS 2 and are actively working on adding support for other frameworks such as ROS 1, ARK, and Drake. Please ping us in the contact form if there is a particular framework you need supported.
This was one of the problems that motivated us to build this tool. We offer various checks in place to work around a limited connection. Small snippets of data will be uploaded for you to get an understanding of what you collected, and you can decide if you want to upload it straight from the robot or bring the disk to your computer to upload.
We provide several mechanisms to monitor specific topics within your ROS 2 architecture. For example, if you want to record whenever model performance drops below a threshold (i.e. 70% confidence), you can register this information in our interface and it will produce a recording every moment this occurs.
Yes, we provide the functionality to maintain a rolling buffer that will automatically be prepended to any recording triggered by an event.
Yes. Once the robot re-establishes a connection to the internet, the metadata around each recording will be uploaded for you to view in our interface.
Yes. All you have to do is register the message's schema.
Any way you like: our web interface, our API, or your S3 bucket. We leave the choice up to you.