German Rheinmetall open-sources its Battlesuite connected weapon system protcol
rheinmetall.github.io
rheinmetall.github.io
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”
this deserves an EU grant
Was ist das Betriebssystem des Servers? Windows?!?
This guy military techs :P
It is a DDS API, so if ROS 2 is anything to go by then it probably doesn't work at all at least 40% of the time.
Now they can freely link anyone to the document.
That'll be $1000 consulting fee on ITAR compliance.
Other than that, PX4 uses an in-memory only pub/sub for internal data bus, somewhat inspired by DDS
But yes - there absolutely are solutions already. I guess I was just lamenting that they weren't really functionally accessible for all applications.
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.
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.
Missouri Metalworks :-|
Rheinmetal :-O
>> The most important rivers flowing at least partially through North Rhine-Westphalia include: the Rhine, [...]
I concede that I missed your Riverine connection between Missouri-Rhine but I think the first guy was focusing on the majesty/exotic-ness of "Rheinmetall" while "Missouri Metalworks" just sounds lame, most likely due to the fact that its fake!
In tandem, we're less familiar with them, which gives them that alure. Think of Rheinmetall and you think vaguely of a hulking corporate giant encompassing metalworkers manging molten metal to men in suits pitching fully automatic anti-aircraft turrets to entire nations; think of Missouri Metalworks and you just imagine a dingy suburban factory your mate reckons he worked at once. And no doubt that's how Germans would think of Rheinmetall too.
I think companies like Tesla, IBM, Lockheed, GE, etc. have the potential to sound "cool" like Rheinmetall were they not so ingrained in Anglophone culture. We just know them all too well, so they've become boring.
At least thats how I see it :-}
> Claude, please execute the insurgents. Make no mistakes.
seems like a perfect fit.
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?
It's funny that you can legitimately just add " - OMG!" in the slang acronym meaning after any of its creations' names.
I'm asking as I'm not a fan of DDS, so very curious the direction they are actually heading into, and I haven't found a reference for this yet.
For things like avionics, industrial automation, etc.
I think if the server world ever thought about the advantages of multicast, it might solve some problems there.
There are about 5 viable vendors in this space, and about 6 open source projects out there floating around.
And interoperability between vendors is very good. IMHO.
> 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.
```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?
Your comment is a bit salty, but I learned something from it, so I don’t think you deserve the downvotes
I mean... If your command line utility doesn't print anything til it's done, that is going to be, _at best_, an annoying user experience.
This is not always true in the case the program crashes. I've had case where `std::endl` was necessary.
If you cant follow naming standards which are extremely simple what chance has the rest got.
[1] https://en.wikipedia.org/wiki/Generic_Vehicle_Architecture
Who cares if german company wants to use this mess for their weapons.
Obscurity is part of the allure, not a repulsive factor.
You don't want a hostile nation suddenly and easily understanding your systems.
This is a principle in cryptography, but carries nicely to other things.
Often connectors are even proprietary.
(This is partially to protect systems not from the enemy, but from the troops themselves...)
World of Tanks has repeatedly had military personnel updating the technical specifications with details they have found in the secret manuals.
Those documents are often secret or top secret, or even more compartmentalized.
There are training docs in wide use today that are not publicly findable on the internet, nor are they seemingly in the datasets of LLMs.
I'm sure there are reasons for that, of course.
What you're talking about would have an even higher level of obscurity and secrecy, and probably Compartmented Information access.
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?
There's a very small number of major contractors and if you pick one of their APIs as the new standard, then you disadvantage all the others.
If you pick a greenfield project, then it will take a long time, and once you are done everybody will claim that they can't use it (see e.g. Ada; quick version they started working on a mandate for a programming language in 1975, mandated Ada in 1991 and by 1996 removed the Ada mandate).
The only way to fight those who can just spend more tokens is to have more humans look at it, who also spend tokens.
“Think russian^H^H^H xml”
The situation gets out of hand!