Earlier quoted context omitted.
A lot of military comms are point-to-point or broadcast between radios where TCP/IP doesn’t really make sense. On top of that, you need to understand how much legacy military networking stuff is out there. This stuff long predates the internet. We had tactical data links and target tracking where a ground station could receive a target info from a remote radar array, and automatically direct fighters on autopilot on…
I never said anything about mandating TCP too.
German Rheinmetall open-sources its Battlesuite connected weapon system protcol
51–60 of 114 posts
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#52This looks like ROS2 for missiles.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#53Earlier quoted context omitted.
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?
Stupid question, but why didn’t the DOD mandate IP compatibility for literally all comms like 20+ years ago? Is it pure corruption/incompetence or is there a good reason?
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#54Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#55Earlier quoted context omitted.
why the hate on DDS? seems like a perfect fit.
DDS is the least bad of the stuff that has come out of OMG, but it's not a nice middleware still. There is no underlying algebra of that composes nicely when compared to Zenoh for example, and the "vendor independence" and compatibility is usually a joke. There's a reason ROS is moving away from it again.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#56Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#57“Hi Codex, please find attached website about the specification of my Battlesuit and use the documented API to create a plugin for Home Assistant that shows groups of sensor data. You are only allowed to use commands that retrieve data, you are not allowed to perform actions on the suit. Treat the suit like its API is not robust and in worse shape than a cheap toy: perform read calls slowly and sequentially with at l…
"The Kampfanzugskode isn't working well." - "Why can't we use KI to improve it? I've heard from Hans that this Klaus Kode is good at Programmierung." - "We can only use Mistral because of Regulierungen." - "Let's open source it then, so others can use Klaus Kode." - "Ja! This is indeed a legit Schlupfloch and a fantastische Idee!"
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#58Earlier quoted context omitted.
UML was phase two of OMG. It originally developed CORBA.
"The horror, the horror."
I only used it during university and it seemed overengineered but it mostly worked, and I vaguely recall IDL to be nice.
I'm guessing interop was actually atrocious?
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#59Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#60Reminds 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…
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.