“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 least one minute in between.

If possible please group data in meaningful categories, just like the tank and radar dome.

My Home Assistant is the default on the local network, credentials are in credentials.txt.

Please send me a text when you’re done. Kthnxbye”

I wonder if someone just got super annoyed at having to ask legal to share their documentation with a cooperation partner for export control clearance, that they decided getting it open sourced would be less of a hassle.

Now they can freely link anyone to the document.

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] https://battery.army.mil/system-integrator-hub/tms/

Sounds like the Land Data Model (LDM) of the Generic Vehicle Architecture (GVA) [1] that the UK MOD has. GVA is closed source however.

[1] https://en.wikipedia.org/wiki/Generic_Vehicle_Architecture

Oh boy, just what the world needs right now. Open source weapons APIs!

First I was excited, then I saw that it's based on DDS.

Are they trying to recreate DIS (IEEE1278) and HLA (IEEE1516) — like they‘re replicating the FOM architecture from distributed simulations for their weapons to integrate.

Complete horrible wrappers. Its almost like they didnt have any real programmers for those languages.

If you cant follow naming standards which are extremely simple what chance has the rest got.

So like Open Mission Systems (OMS)? https://www.vdl.afrl.af.mil/programs/oam/OMS_Marketing.pdf

Nah, they haven't open sourced anything: https://github.com/rheinmetall. They just published the documentation. Really weird, what's the point?

Open the C++ example up and the first thing I see:

```cpp std::cout << "Received ReportCoordinateFrameSettings" << std::endl; ```

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" caused by the weapon blowing itself up circumventing a buffer flush?

Good. There is no security by obscurity anymore.

The only way to fight those who can just spend more tokens is to have more humans look at it, who also spend tokens.

Rheinmetal is a nice company, hope it just didn't benefit from war/fear of war.

Corba never died!!! OMG!!

Finally, Front Mission in real life.

This looks like ROS2 for missiles.

They could Just have used ROS...

Am 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?)

of course the germans would use a fucking open management group academic mastrubation, bureucratic shitshow like dds.

I cannot find boomstick anywhere in here

[flagged]

[flagged]

[dead]

“Fire your goddamned missiles!.json”

“Think russian^H^H^H xml”

So what do they expect us to do? Write killer-plugins? Or get excited for next upgrade?

The situation gets out of hand!