OpenJAUS is proud to announce the release of OpenJAUS SDK v2023.0! With our 2019-06 release, we started releasing all of our JAUS implementation packages at the same time as a validated distribution and moved to a naming scheme based on the release date (YYYY-MM) of the distribution instead of specific version numbers. With this release, we make two changes to the way that we release the OpenJAUS SDK. First, we have replaced the use of the release month from the SDK version to a release number which starts at zero (0) and increases by one (1) for every release within a year. We found that knowing the release month wasn’t very useful and could lead to issues if there were two (2) releases ever occurred within the same month. This new versioning scheme removes that issue. Second, we now bundle the SDK as a single download. In previous releases, you had to download each JAUS implementation package separately based on the services you needed. As we look at adding new SAE documents and IOP versions, we saw that this could become a huge burden. As such, we will now package the OpenJAUS SDK as a single download which contains all …
OpenJAUS Releases SDK 2020-07
OpenJAUS is proud to announce the release of the 2020-07 distribution of our software development kit (SDK)! Starting with our 2019-06 release, OpenJAUS releases all of our JAUS implementation packages at the same time as a validated distribution and move to a naming scheme based on the release date of the distribution instead of specific version numbers. The term ‘OpenJAUS SDK’ is used as a blanket term to refer to all of our JAUS implementation libraries (SAE JAUS, IOP, AEODRS, etc) and represents our commitment to supporting all programs of record and ensuring that packages continue to work together as our customers expect. This latest release provides access to all the features you need to be SAE JAUS, IOP, and/or AEODRS compliant. There are also several bug fixes and updates to reduce the time developers spend on JAUS specific details and can instead focus on implementing cutting edge capabilities. A few highlights include: SAE JAUS Feature: Restart discovery process if the discovery server it registered with disappears Feature: Added CommandEvent support IOP v3 Bug Fix: Fixed scaled integer bugs in Communicator service Feature: Removed dependency on org.openjaus.ext.cpp library The OpenJAUS SDK continues to be the only commercially available implementation of the …
OpenJAUS Releases SDK 2019-06
OpenJAUS is proud to announce the release of the 2019-06 distribution of our software development kit (SDK)! Starting with this release, OpenJAUS will release all of our JAUS implementation packages at the same time as a validated distribution and move to a naming scheme based on the release date of the distribution instead of specific version numbers. Over the last few years, the number of programs of record utilizing JAUS has grown, prompting OpenJAUS to introduce additional software development packages to meet new demands; such as the RAS-G Interoperability Profiles and AEODRS packages. This has sometimes led to confusion with knowing which packages work together and some packages lagging others in terms of updates. In 2018, we switched to a semantic versioning scheme to alleviate confusion on dependency compatibility. This transition to a date-based naming scheme allows us to version each package independently without confusion with an ‘overall SDK version number’. Also, moving forward the term ‘OpenJAUS SDK’ will be used as a blanket term to refer to all of our JAUS implementation libraries (SAE JAUS, IOP, AEODRS, etc) and represents our commitment to supporting all programs of record and ensuring that packages continue to work together as our customers expect. This latest …
OpenJAUS Releases SDK v5.0.0
OpenJAUS is proud to announce the release of our latest software development kit, OpenJAUS v5.0.0! JAUS has established itself as a key technology in the US Army & US Navy’s Unmanned Ground Vehicle programs of record. In conjunction with the RAS-G Interoperability Profiles standard, JAUS based systems have seen significant opportunity over the past several years. OpenJAUS’ SDK is the only commercially available implementation of the JAUS standard. As such, OpenJAUS is constantly working to improve our products to meet the needs of our customers and their programs as well. Today OpenJAUS is announcing the immediate release of a significant upgrade to our product, OpenJAUS SDK v5.0.0. This latest release gives you all of the features you need to be SAE JAUS and IOPv2 standards compliant. With this release OpenJAUS has made significant changes to its product to address issues identified by its users and improve the quality of life for developers. Highlights of the new features include: Improved Config File format and New Configuration Editing Tool Addition of a default “User Configuration” file for storage and use of custom configuration options Change to versioning numbers to follow Semantic Versioning rules Updated and Improved Buffer API classes Addition of ‘Auto’ Network Interface option Ability to specify TTL value for multicast …
OpenJAUS Configuration Editor Tool
As of version 5.0 of the OpenJAUS SDK, the configuration file has been modified from an INI based file to a JSON based file. In addition, OpenJAUS has developed and made available a GUI tool for editing and maintaining the configuration file. This Configuration Editor is a tool to used to generate a configuration file that will be read by an OpenJAUS specific executable. This file provides configuration data needed by an OpenJAUS application. Download the OpenJAUS Configuration Tool An existing configuration file can be opened by selecting from the menu bar the File->Open option or by pressing the ‘Open JSON Configuration File’ icon. A new configuration file can be created by selecting from the menu bar the File->New option or by pressing the ‘New Configuration’ icon. A legacy configuration file can be imported into the editor by selecting from the menu bar the File->Import option or by pressing the ‘Import Legacy Config File’ icon. Legacy config files have an extension of .conf Once the desired data has been entered the file can be generated and saved. This is done by selecting from the menu bar the File->Save option of by pressing the ‘Save Configuration’ icon. The file will be …
Premake4 not working on Linux
Q: When executing the command premake4 gmake on linux, I get the following error: premake4: No such file or directory
warning: Using ‘gethostbyname’
Q: I get the following warning when I compile my code: “warning: Using ‘gethostbyname’ in statically linked applications requires at runtime the shared libraries from the glibc version used for linking”?
How does the GposClient and Gpos look for each other and not a different class?
Q: How does the GposClient and Gpos look for each other and not a different class? Is it correct to assume it involves the lookupService?
What is the purpose of SIGTERM and SIGINT in the Signal Handler?
Q: What is the purpose of SIGTERM and SIGINT in the Signal Handler? A: The SIGTERM and SIGINT handlers are to catch those standard signals (like Ctrl+C) and allow the application to exit cleaning instead of “crashing”. http://www.gnu.org/software/libc/manual/html_node/Termination-Signals.html
Create a test program
Q: I’m currently trying to make a test program that tries to communicate with a test client (mimicking the Gpos and Gpos client). I’m a little confused as to how the Gpos and Client ëconnectí to each other.
Run files located in the bin folder
Q: I’m trying to run one of the files located in the bin folder but it gives me this message: ./BaseDemo: error while loading shared libraries: libopenjaus-core.so: cannot open shared object file: No such file or directory However, I can clearly see libopenjaus-core.so in the lib folder. Am I missing something? Or am I doing something wrong?