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 …
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 …
Q: When executing the command premake4 gmake on linux, I get the following error: premake4: No such file or directory
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”?
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?
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
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.
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?