Live data from Hacker News

Robotics and ROS 2 Essentials

henkirobotics.com

101–107 of 107 posts

Re: Robotics and ROS 2 Essentials

#101
post #92

Earlier quoted context omitted.

Groupthink is what happens when people don't share their dissenting views, so the group as a whole makes poor decisions. This is why it is a bad idea to silence dissent. This defines the ROS community, as you have exemplified. So it is good that you come and read the comments here. Welcome!

Many people in that thread you linked to have criticized ROS and explained the issues they have with the build system, some even proposed improvements, but somehow you're the only one that had to have their permissions restricted because of your behavior. And that's after repeatedly breaking the code of conduct for years. I've yet to see any technical contribution from you in ROS or any other project. You don't know…

Sorry, I do not contribute to projects governed by a tribal oligarchy. However, the ROS project gives me many anti-patterns for software engineering research. Social and psychological aspects that lead to such a collective frenzy are also interesting. But you definitely deserve a special chapter on software engineering failures, where the intersection of technical debt, second-system effects, hubris, and bad governance.

Re: Robotics and ROS 2 Essentials

#102
post #46

Earlier quoted context omitted.

We replaced ROS with GRPC, foxglove and our own code. Works reliably, much better to handle. Would recommend everyone else to try it

Isn't Foxglove built for ROS?

Foxglove works well with ROS, but it also works well without ROS. It's not a requirement

Re: Robotics and ROS 2 Essentials

#103
post #100

While it's used in industry sometimes, ROS is really one of those by-and-for-academia tools. There's a reason it's near-universally reviled, and why "migrate off of ROS" is a standing goal at a lot of robotics companies. There's also a reason why it's a standing goal, rather than a completed goal. It does little or nothing really well, but it does everything kind of okay. There's a lot of "alternatives", most of whic…

Which would you choose to do real-time robotics with C++ on Linux/PREEMPT_RT with CUDA support?

Well, the features you're talking about are operating system features, which despite its name, ROS is not. That request is independent of middleware.

As far as I'm aware very few real time operating systems support CUDA, and none that are free. You could look at Concurrent's RedHawk Linux.

Re: Robotics and ROS 2 Essentials

#104
post #31

I'm new to embedded systems programming and looked into ROS recently, without using it, while figuring out a minimal software stack for a UAV project (px4 over ArduPilot for the flight controller, but what to run on a "companion" computer is open ended). [my XP is in cloud infra, RESTful microservices, web apps, videogames] Researchers, hobbyists, and some industry professionals (for prototyping?) seem to love ROS fo…

Correction - Basis will be Rust compatible in the future. :)

Re: Robotics and ROS 2 Essentials

#105
post #72

Earlier quoted context omitted.

About the theory, you can learn yourself (I think) about practice, well, you may learn 1 or 2 platforms, but not all. If you get a job, you will for sure have to learn a lot from the platform they use, but much more of the application they do. Also the platforms get obsolete fast… What about buy 2nd hand/use/resell some hardware? I do not know how much cost a Ms in CMU, but sure does bot even compare to 20k. Sorry ma…

That’s $20k for one robot. If you want exposure to the breadth of hardware a ME at CMU would bring, you’d need access to the facilities as well. Robotics takes space most people don’t have.

But Ms at CMU, aren’t you looking at about 400k?!

Re: Robotics and ROS 2 Essentials

#106
post #46

Earlier quoted context omitted.

We replaced ROS with GRPC, foxglove and our own code. Works reliably, much better to handle. Would recommend everyone else to try it

Isn't Foxglove built for ROS?

Foxglove founder here. Foxglove is framework agnostic - we have first class ROS support but you can just as easily bring in custom data via Websocket or MCAP files.

https://docs.foxglove.dev/docs/connecting-to-data/frameworks...

Re: Robotics and ROS 2 Essentials

#107
post #86

We have a handful of devices built on STM32, RP2040, RP2350, RP Pico and RP Pico-W running bare metal firmware and green threads for task management. These were generally designed to communicate over UART (to a physically-connected host) or a LAN (wired or wireless) using MQTT topics and plain text message formats. We have a primary, core machine built around Linux SOMs like NVidia's Orin or the RPI5, which could run…

The one over-arching issue I'd point to is that network pub-sub is the way to connect different parts of your system in ROS, and that's a bad default, and an even worse single option. For most data-flow, you probably don't want to be hitting a serialisation step at all, but if you do, you probably want to be thinking carefully at the system level about how to move it around (how much data, what latency, from what kin…

This is super helpful.

We're digging into Zenoh as a potential "library" level integration.

Do you have any experience/thoughts on their tools?

Post reply on HN