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.
German Rheinmetall open-sources its Battlesuite connected weapon system protcol
11–20 of 113 posts
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#12Am I just too ignorant of Miltech, or is this that in large parts recreating Standard messaging primitives that other protocols and systems have been providing for decades already (so invented elsewhere?)
DDS sort of took over from CORBA in the military domain, and the statically-typed IDL was still quite similar to CORBA last time I looked at it, so that takes you back to around 1998 when CORBA was being used a lot in the military in my experience.
What other protocols and systems were you thinking of that can provide (depending on broker) hard-realtime delivery that can be used in safety-critical systems?
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#13Earlier quoted context omitted.
Every mil company designs unique bespoke things often with some exceptions, and even the "open systems" mostly aren't open by any stretch of the definition. Obscurity is part of the allure, not a repulsive factor. You don't want a hostile nation suddenly and easily understanding your systems.
Also you do not want them to benefit from your smart design choices. You want them to suffer from their bad choices and not learn from your success. (Yes, of course you could have bad design choices that you don’t realize someone else has solved more intelligently.)
Bad design choice is probably why they open sourced it.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#14Am I just too ignorant of Miltech, or is this that in large parts recreating Standard messaging primitives that other protocols and systems have been providing for decades already (so invented elsewhere?)
Every mil company designs unique bespoke things often with some exceptions, and even the "open systems" mostly aren't open by any stretch of the definition. Obscurity is part of the allure, not a repulsive factor. You don't want a hostile nation suddenly and easily understanding your systems.
Hat sounds like a particularly weak form of security by obscurity
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#15This looks like ROS2 for missiles.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#16Nah, they haven't open sourced anything: https://github.com/rheinmetall. They just published the documentation. Really weird, what's the point?
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#17Am I just too ignorant of Miltech, or is this that in large parts recreating Standard messaging primitives that other protocols and systems have been providing for decades already (so invented elsewhere?)
Every mil company designs unique bespoke things often with some exceptions, and even the "open systems" mostly aren't open by any stretch of the definition. Obscurity is part of the allure, not a repulsive factor. You don't want a hostile nation suddenly and easily understanding your systems.
Asterix is an actual standard for radar data, coming from civilian radar systems. I wish it was updated somehow for 3d beam-steered (and moving) sensors, but still it covers most of the industry's needs... I keep hearing so many grumblings of replacing it (it is binary, unforgiving, quirky, very 80s...) and of course fragmentation is back in.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#18[dead]
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#19Nah, they haven't open sourced anything: https://github.com/rheinmetall . They just published the documentation. Really weird, what's the point?
They've got the IDL files as well for the APIs, but you can't use them without their libs:
> The data model is defined using a custom format .rmodel based on the ddkit > framework (rmodel-api).
> Please note that the .rmodel data model is for documentation purposes only and > does not reflect the actual interface used on the communication layer. Network > communication is only possible through the provided libraries.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#20Earlier quoted context omitted.
Every mil company designs unique bespoke things often with some exceptions, and even the "open systems" mostly aren't open by any stretch of the definition. Obscurity is part of the allure, not a repulsive factor. You don't want a hostile nation suddenly and easily understanding your systems.
On the other hand, its good to design systems where it wouldn't even matter if the hostile nation state knows exactly how it works. This is a principle in cryptography, but carries nicely to other things.
I feel like this is always the best design whenever possible.