Advanced node config for permanent installation
How to set up nodes for permanent installations
This page describes some usefull configuration options for permanent installation of Augmenta Nodes. All those instructions can and should be performed before deploying the system at the final location. Doing everything described here will save you time and prevent discovering issues on site.
Hardware
The hardware should have been tested by the system integrator that did set up the nodes.
Make sure that unused ports have covers on them.
1. Initial setup
Prepare your network : before starting your nodes you should have a working network with DHCP (automatic IP configuration).
Wire up your nodes : connect the sensor to it, connect the network cable in the LAN1 interface.
Connect the power supply to your nodes.
Open Augmenta Fusion, the nodes should appear after some time.
Go into the web interface of each node and check that you can correctly see the stream of the depth camera.
The steps above describe how to get started with an Augmenta System. The instructions below explain how to perform specific actions for permanent installations.
2. Node updates
You should make sure that you have the latest software version for the node. You might overwright some configurations files while updating, that's why it is advised to perform this step first.
Go into each Node's web interface. In the settings tab, you can enable auto-updates. When the auto-update is enabled, you can select the channel you want to track.
The stable channel hosts a legacy version of the software. With the current version of Augmenta Fusion you will not be able to detect them or get data from them. The candidate channel hosts the most stable version of the current Node software. {.is-warning}
As described above, we recommend to track the candidate channel, which is the most stable version of the current Node software. It is also the default channel set at the factory.
When you are on the right channel, you can click on the Update button in the web interface. It might take some time for the Node to download the software and to install it.
After the update, check that you are on the right channel and that the available version field displays None.
Now your nodes should be up to date.
Offline updates
If you know that you will not have access to the internet or have a low network speed, there is a way to manually update node with a version that you did download on a computer or from another node.
3. Name and tags
Once your node is up to date you can start configuring your node.
It is advised to give a name to each node. This can be done in Augmenta Fusion. In the source pannel, you can double click on a node's name and you will be able to edit it.
You can also set a common tag name for a set of nodes. This will allow you to add them in batch to Fusion. This can be usefull when you have multiple installations that use Augmenta Nodes.
To do this, go into each Node's web interface. In the advanced tab, there is a tag section. You can enter a tag name and click on add. Now you should be able to add your tagged Nodes in batch in Fusion. When adding nodes, there is an option add all sources from tag... that does this.
4. Write down informations about each nodes
You should write down the following informations for each node:
MAC address : the unique identifier for the main network card, this will never change
Node name : the node name you did set in the section above
IP address : the IP address of the node, see below how to set a static IP on a node
S/I number : under the node, there is a sticker with a number starting with "AR", write it down in case of a hardware failure
5. Networking
The nodes have a specific network configuration that is by default developper oriented. You might want to change some settings when installing it a permanent setup. You can read more about the network configuration here.
The instructions below detail which settings could be interesting to tweak.
Fallback to link-local
If a node does not get an IP from a DHCP server for a certain amount of time, it will fallback to an IP in the link-local range. This allows a node to be directly connected to a computer, because Windows will also fallback to a link-local IP by default.
But in the case of a permanent installation we do not want our node to fallback to such an IP because it will then be unjoinable and we will have to reboot it manually or by cutting power to it.
If you want to deactivated the fallback to link-local, follow the instructions below:
connect to the node through SSH (username augmenta, password augmenta78)
Disable or delete the link-local fallback
nmcli connection modify enp1s0-ll connection.autoconnect = falseor you can also delete it
nmcli connection delete enp1s0-llNow your node will never fallback to the link-local range. It will always ask for an IP to the DHCP server. You can also set a static IP for your node if you want, as described below.
Static IP
When permanently installing Augmenta Nodes it can be usefull to give a static IP address for each one. This can be done on each Node.
Alternatively, you could set a static DHCP lease for each node in your router. The inconvenient is that if you have to change your router you will have to configure it again.
When setting static IPs on the nodes, the only case where you'd have to do this configuration is if a node dies and you have to replace it. The router swap might happen more often. That's why we recommend to set static IP addresses in the nodes.
Set a static IP through SSH
The procedure is described on this page.
You might want to set up the static IP but not set it by default for now. It might be better to leave the nodes to default on DHCP. This way if when arriving on site the network is not the same, or you have to put a node on a DHCP network, you will be able to connect to it. If you are deploying your own network, it might not be usefull. Just remember that if you set it to a static IP it will be harder to access the Node if you do not have the correct network in place. {.is-warning}
Last updated