‹ 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. cpgxiii · · focus · HN ↗
      There&#x27;s a range of DDS implementations, definitely a number that are compatible with embedded and spaceflight applications that don&#x27;t require dynamic memory allocations. You&#x27;re going to take a hit on some DDS features, but then again you aren&#x27;t going to need to handle a large queue of large dynamically-sized messages on some small embedded platform.

      I think it&#x27;s rarely the right choice - most of the hardware I&#x27;ve seen that uses embedded DDS probably should have used plain old UDP instead and then whatever client was running on beefier hardware then handled the translation into DDS - but there are shipping products that use embedded DDS.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.