First I was excited, then I saw that it's based on DDS.
why the hate on DDS? seems like a perfect fit.
DDS is terrible.
German Rheinmetall open-sources its Battlesuite connected weapon system protcol
41–50 of 114 posts
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#42Earlier quoted context omitted.
I have to assume that so many people require access to the specs that an interested party can surely acquire them. World of Tanks has repeatedly had military personnel updating the technical specifications with details they have found in the secret manuals.
Are you not thinking about the wrong tank game? World of tanks has ancient tanks, not modern (game tank span basically end with the main battle tank making the game tank role division being made irrelevant).
Err yes. War Thunder.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#43Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#44Earlier quoted context omitted.
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?
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.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#45“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…
Excellent cold open for a sci fi
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#46Corba never died!!! OMG!!
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#47Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#48Open the C++ example up and the first thing I see: ```cpp std::cout Generally, I've heard `std::endl` instead of \n has bad performance because it forces the statement to print immediately. And because cout is guaranteed to flush anyways when the program ends, you're adding a delay for no reason. I wonder if there's something I'm not seeing that led to them adopting this rule. e.g. "abnormal program termination" caus…
This seems like an incredibly unimportant quibble... I would imagine they just used std::endl b/c that's what most random tutorials used in the 2000s and that's how the engineer learned. If you are printing a debug string, you probably don't care that much about perf in the first place.
I was wondering if it's a hard real-time constraint or something to ensure consistent timing.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#49Reminds 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…
There's a range of DDS implementations, definitely a number that are compatible with embedded and spaceflight applications that don't require dynamic memory allocations. You're going to take a hit on some DDS features, but then again you aren't going to need to handle a large queue of large dynamically-sized messages on some small embedded platform.
I think it's rarely the right choice - most of the hardware I'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.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#50“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!"