Plain ROS Java System Example Project

ROS Java contains a plain java, standalone version of roscore that does not require any ROS instalation to be present. This is an example ROS system running completely on Java with no ROS instalation required. It is an example that demonstrates running a roscore and four rosjava ROS nodes. A Topic Publisher, a ROS Topic Subscriber, a ROS Service Server and a Service Client.

This example project demonstrates how to do the following programmatically through the ROS Java API:

1. Create, start and shutdown the Java roscore
2. Create, start and shutdown ROS nodes
3. Publish and subscribe to a ROS topic
4. Create a ROS Service Server and call it from a ROS Service Client

This repository also provides an example that demonstrates how to run rosjava with an another roscore. E.g. cpp roscore from ROS noetic.
A version of this repository that uses custom ROS messages is available here.

Requirements

In order to compile and run this project only Java needs to be installed. GIT also makes getting the source very easy. Links are provided for convenience.

• GIT , in order to clone the project repository
• JDK, the project has been developed and tested using JDK 21 or later
• Gradle, is used for project compilation. Installing it is not required. The included Gradle wrapper will automatically download the configured Gradle version.

Before running the Gradle commands below, make sure JAVA_HOME points to a JDK 21 or later installation and that java -version reports Java 21 or later.

Quick Instructions for Windows Power Shell

1. Clone the project repository: git clone https://github.com/SpyrosKou/Plain-ROS-Java-System-Example.git

2. Go into the cloned repository directory: cd .\Plain-ROS-Java-System-Example\

3. Compile the project and prepare for running: .\gradlew.bat installDist

4. Run the project using the generated script: .\build\install\Plain-ROS-Java-System-Example\bin\Plain-ROS-Java-System-Example.bat The demo runs for about 30 seconds and prints ROS publisher, subscriber and service activity to the console.

5. Build and run in a single command using the gradle application plugin: .\gradlew.bat run

Quick Instructions for Linux

1. Clone the project repository: git clone https://github.com/SpyrosKou/Plain-ROS-Java-System-Example.git

2. Go into the cloned repository directory: cd Plain-ROS-Java-System-Example/

3. Add execute permission to gradlew script: sudo chmod +x gradlew

4. Compile the project and install it locally: ./gradlew installDist

5. Run the project using the generated script: ./build/install/Plain-ROS-Java-System-Example/bin/Plain-ROS-Java-System-Example The demo runs for about 30 seconds and prints ROS publisher, subscriber and service activity to the console.

6. Build and run in a single command using using the gradle application plugin: ./gradlew run

Using with an existing, external, non-rosjava roscore

It is possible to use rosjava to run rosjava nodes in an environment where a ros system is already running. E.g. a cpp noetic ros instance. An example on how to run rosjava nodes programmatically without starting roscore is provided in MainExternal Note that if a roscore is not running, then this example will not run correctly. In order to use it do the following:

1. Set ROS_MASTER_URI and ROS_IP environment variables. Both these variables are needed. If these environment variables are missing, you will see some errors in step 4 below. The following commands assumes the example and roscore run in 127.0.0.1 aka localhost.
   export ROS_MASTER_URI=http://127.0.0.1:11311
export ROS_IP=127.0.0.1
   On Windows PowerShell the equivalent commands are:
   $env:ROS_MASTER_URI='http://127.0.0.1:11311'
$env:ROS_IP='127.0.0.1'

2. Start roscore Run the following: roscore

3. With the roscore already started externaly run MainExternal

4. You can start directly the MainExternal from the gradle by running: ./gradlew runWithExternalRos On Windows PowerShell use: .\gradlew.bat runWithExternalRos

Project History

A separate high-level project history and change log is available in CHANGELOG.md. It summarizes the major milestones in the repository and also calls out long quiet periods where the main visible changes were Gradle, dependency, or documented Java-version updates.