JAUSInstallation < Main

Tags: view all tags
---+ Introduction to JAUS
---++ Installation
Download the latest source and build it, including ojNodeManager and ojVehicleSim. Install to /usr/local/jaus, or some place that is read-only, unless you plan to modify it intentionally. Make sure to add the dynamic libraries to your /etc/ld.so.conf libraries path or link them properly in make when you run code. 
---++ Basic Use
There are two libraries: libjaus and libopenJaus. libjaus contains most of the infrastructure (messages, state definitions, services, component structures, etc...). libopenJaus is an additional set of tools aimed at actual deployment and has the componentLibrary, nodeManager, utilities, etc... I recommend familiarizing yourself with the contents of the "./include" folders in each library's directory.

After you've read at least the Domain Model of the Jaus Documentation, go to the ojNodeManager directory and make sure you have already built it (there should be a ./bin folder with an ojNodeManager binary). In the ojNodeManager directory, you should see a file called "nodeManager.conf.template". The contents of this file must be tweaked in order to use it, so here is a bare-bones solution that will run out of the package. In order to run the ojNodeManager, you must place the "nodeManager.conf" file in the ./bin directory.

<hr size="2"></hr>
---++++ nodeManager.conf
# This subsection defines the JAUS characteristics of the node<br />[JAUS]<br />#Numeric value from 1-254 inclusive; determines<br />#the unique system ID value of the Node Manager<br />SubsystemId: 7<br />#Numeric value from 1-254 include; every <br />#node must have a unique ID<br />NodeId: 1<br />#These do not have to be unique; they are for human-readable interfaces<br />Subsystem_Identification: RamALbert<br />Node_Identification: primary<br /><br /># This subsection defines the interfaces and their options for component communication<br />[Component_Communications]<br />#interface supports port 24629 and loopback network interface (127.0.0.1)<br />#and expects JAUS traffic only<br />JAUS_OPC_UDP_Interface: true<br />#enables communication between the Node Manager and local components<br />#interface uses port 24627 and the loopback (127.0.0.1) and<br />#expects non-JAUS traffic only<br />OpenJAUS_UDP_Interface: true<br /><br /># This subsection defines the interfaces and their options for node communication<br />[Node_Communications]<br />#determines whether the ojNodeManager's node communications are enabled or not.<br />#enable for inter-node communication; disable for subsystem communication only<br />Enabled: true<br />#JUDP_Interface: true<br />#JUDP_IP_Address: <br />#JAUS_OPC_UDP_Interface: true<br />#JAUS_OPC_UDP_IP_Address: <br /><br /># This subsection defines the interfaces and their options for subsystem communication<br />[Subsystem_Communications]<br />Enabled: true<br />#JUDP_Interface: true<br />#JUDP_IP_Address: <br />#JAUS_OPC_UDP_Interface: true<br />#JAUS_OPC_UDP_IP_Address:<br /> <hr size="2"></hr> Once you have done this, and you have tested that the ojNodeManager runs without problems, you are now equipped to create a test component. Follow the tutorial in the FAQs on the JAUS website.

-- Main.StephenFox - 2010-09-16
Topic revision: r1 - 2010-09-16 - StephenFox