‹ BackHN Continuity

Thread

German Rheinmetall open-sources its Battlesuite connected weapon system protcol

284 points · 109 comments · summarity

  1. alhirzel · · focus · HN ↗
    Reminds me a lot of the Tactical Microgrid Standard (aka TMS aka MIL-STD-3071) [1], probably just because TMS uses DDS as well. I would really like to know if there is a protocol that functions like DDS but caters to real-time guarantees and prioritizes (at a "simple protocol" level) usability on embedded systems with no dynamic memory allocation. It would also need to be just-as-functional with non-real-time systems. One problem with DDS is that it is too heavy-handed to implement well on an embedded system.

    [1] <a href="https:&#x2F;&#x2F;battery.army.mil&#x2F;system-integrator-hub&#x2F;tms&#x2F;" rel="nofollow">https:&#x2F;&#x2F;battery.army.mil&#x2F;system-integrator-hub&#x2F;tms&#x2F;

    1. matthewmacleod · · focus · HN ↗
      Zenoh (<a href="https:&#x2F;&#x2F;zenoh.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;zenoh.io&#x2F;) is a good alternative to DDS in many cases - it scales down to microcontrollers with most features still intact, but scales up to a routed hybrid mesh if needed.

      It does move the schema enforcement out of the middleware layer, so it’s a bit different. But it’s now a first-class alternative middleware implementation for ROS2 as an alternative to DDS.

      1. alhirzel · · focus · HN ↗
        Wow - thanks for pointing this out! I will be looking into it.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.