Typical Network Connection

Some typical network setup examples. AMAS is network agnostic and relies on Peer-to-Peer connection.

When implementing one of the following network examples, ensure the network performance conforms to the bandwidth and latency requirements specified on the Network Requirements page.

Our peripheral Cortex device is shipped with a static IP in the range of the gateway 192.168.0.1 (normally labelled on the device). We use a custom communication protocol based on TCP/IP and UDP.

We recommend implementing one of the following typical network architectures for establishing the Peer-to-Peer connectivity between the AMAS VR application and Cortex:

Typical connection using an ordinary WIFI setting

Typical connection using 5G connectivity

Remote Connectivity Solution

AMAS VR app could connect to the cortex on a remote network, if the remote network can be accessed via a public static IP (using virtual port forwarding) or a VPN, to establish peer-to-peer connectivity.

Steps for Remote Connectivity using Public Static IP

Pre-requisite: You will need to obtain a Public Static IP Address from your network provider.

We recommend utilising the port forwarding functions of a commercial router to forward a designated static public IP address and ports to local IP addresses and ports.

Note: Port-forwarding to a static public IP address is insecure. When connecting via a Public Network, please consider your cybersecurity policy.

Note: Internal and external ports in the forwarding rules have to match (use the same port)

To set up port forwarding on the Extend Robotics router (ASUS gaming router), the steps could be found at https://www.asus.com/support/faq/1037906/.

Note: The router login credentials would be supplied in the delivery note at the time of delivery.

For any other router, please check the manual from the manufacturer to set up port forwarding.

Example Cortex Configuration:

The network will need to allow these ports to be used over the Internet to access the devices with the following network settings (Note: The port information for each connected robot and sensor can be obtained from the Command Console) :

• Cortex IP : 192.168.0.140

• Robot:

  • ROS Port: 9090

• Sensor 1

  • ROS Port: 9091

  • Data Port:12345

• Sensor 2

  • ROS Port: 9092

  • Data Port:54321

For Sensors, the ROS port and Data Port both need to be exposed (forwarded).

For Robots, only the ROS port needs to be exposed (forwarded).

For this example configuration, 5 port forwarding rules (3 ROS Ports and 2 Data Ports) need to be set up, as shown:

Robot ROS Port Forwarding Setup

Sensor 1 ROS Port Forwarding Setup

Sensor 1 Data Port Forwarding Setup

Sensor 2 ROS Port Forwarding Setup

Sensor 2 Data Port Forwarding Setup