Returning after a year, I still am philosophically revolted by the way #ros2 and #microros shove all their demos and dependencies into a project's src folder, and then you're supposed to start building inside one of the demos (apparently).

Middleware should install itself somewhere discreet and make *just enough* of itself available as a dependency.

Maybe I just don't *get* colcon and cmake

#microros remains so obnoxious to set up that I'd almost rather take my chances with homebrewed uart or restful webservice

I. Want. My. Logic. Strictly. Isolated. From. The. Platform. Build. System.

Как студенты МИФИ призывали Шиву на Eurobot 2024, часть 2

Вторая часть повествования опыта участия студенческой команды НИЯУ МИФИ в соревнованиях по робототехнике Eurobot 2024. В статье представлены решения программного управления периферией на роботе и алгоритмы движений, а также описана стратегия поведения на игровом поле.

https://habr.com/ru/articles/839368/

#eurobot #microROS #raspberry_pi_pico #raspberry_pi_4 #github #opencv #vs_code #diy

Как студенты МИФИ призывали Шиву на Eurobot 2024, часть 2

В первой части статьи , мы описывали конструкторские детали и используемую электронику в нашем SheevaBot, робота, собранного для участия в соревнованиях Евробот 2024. Перейдём к рассмотрению...

Хабр
micro-ROS: bringing ROS 2 to MCUs

#microros is doing something to my custom messages such that they can be passed around just fine by #ros2 itself, but the pointers given to my callback are mangled

Today I found out that #microros switches off some of the rosout logging capabilites, but doesn't tutorialize what to do instead. Or give a clear account of which #ros2 apis are no-op.

Sure, I can use custom trace publisher, but I wish I could read about *WHY*

Trying to set up a minimal #microros devcontainer for #vscode, really struggling to get performant intellisense.

I think the bits where even token recognition locks up are probably the worst.

Trying to use most lightweight possible #ros2+#microros on #raspberrypi #pico container is agonizing. I think a big part is because *some* components seem to think that the best-documented onboarding path needs to involve fetching and building a huge stack of demos.

If I could reach a minimal dev container image, maybe I'd know for sure.

Omniwheels finally arrived from @[email protected], had to print spacers so that they don't hit the servo motor, but everything's now assembled and good to go! Time for some software!

#microros #ros #robotics

Loving all the pictures of robots everyone built in 2022! For me, 2022 was the year of exploring #microROS with different microcontrollers, upgrading the AKROS robot with a #Teensy and a new RPi case, and of course #ROSCon in Kyoto! Looking forward to an exciting 2023!