Typical Network Connection
This section shows some typical network setup, although the AMAS system agnostic to the type of network with a Peer-to-Peer connection.
When implementing one of the following network examples, ensure the network performance conforms to bandwidth and latency requirements specified on the Network Requirements page.
Our peripheral devices are shipped with static IP with the gateway range 192.168.0.xxx. This is normally labelled on the device. We use a custom communication protocol based on TCP/IP, UDP.
We recommend implementing one of the following typical network architectures:
Connectivity via Public Network
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.
Pre-requisite: you will need to obtain a Public Static IP Address from your network provider.
Note: Port-forwarding to a public IP address is insecure. When connecting via a Public Network, please consider your cybersecurity policy.
For now, internal and external port forwarding rules have to match (use the same port)
As an example:
The network will need to allow these ports to be used over the Internet to access the devices with below network settings:
RoboKit:
Local IP: 192.168.0.140,
ROS Port: 9090
SenseKit 1
Local IP: 192.168.0.141
ROS Port: 9091
Data Port:12345
SenseKit 2
Local IP: 192.168.0.142
ROS Port: 9092
Data Port:54321
You can use port forwarding on an ASUS Wi-Fi router. The port forwarding can be configured following: https://www.asus.com/support/faq/1037906/. In total, 5 port forwarding rules need to be setup as below:
Last updated
