this post was submitted on 30 Jun 2023
3 points (100.0% liked)
ROS
169 readers
1 users here now
Welcome to our ROS community!
This is a place where you can post links and news about the Robot Operating System and share with the rest of the Fediverse.
For content general to Robotics and unrelated to ROS, checkout: !robotics
Community References:
Project Resources:
Q&A Exchanges:
Event Calendars:
Helpful Links:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes, I believe it has plenty advantages in using the steam deck vs android tablets. Instead of installing Ubuntu on my Steam Deck, I utilize Podman and Podman Compose to launch the necessary ROS nodes.
My Steam Deck records compressed RGB+D and LiDAR data into rosbags, while running a LOAM-based algorithm and visualizing the map in real-time. During this process, the CPU usage remains around 70%. The primary consumer of system resources was Chrome, (running Foxglove), which accounted for approximately 17% of CPU usage. This leaves room to experiment with more resource-intensive algorithms (which I will be doing in the future). I think I could not have managed this in a tablet for the price of the Steam Deck.
The presence of joysticks on the Steam Deck proves useful for utilizing it as a controller, another benefit versus using an Android tablet. Although I have not yet messed with the joysticks, only with the back buttons to add a few keybindings.
What display server does steam use on Arch/SteamOS? Wayland, X11? I imagine you're using Foxglove with native browser install to work around the hassle of having to do display forwarding and GPU passthrough from the container to use rViz instead?
It uses X11. I am using Foxglove on a container and exposing a port. I didn't tried Rviz, but it probably is not straightforward to make it work. So I went directly to a web-based viewer.