User's Manual

NETNode
Phase 1 and 2 Units
NETNode
User Manual
NETNode-V2.3
2-54
DS000034 Unclassified
4.6. Configuration Tab – Mesh Pane
4.6.1. Mesh ID
The Mesh ID tells the unit which group it belongs to. All NETNodes on Mesh ID 122 for
example will communicate with each other.
This means you could set up another mesh with Mesh ID 125 for example on the same
frequency which would run independently of Mesh 122 (though you would have to be
careful about interference and run the units in separate areas).
You can choose any numbers from 001 to 255 for your Mesh ID. Different Mesh systems
should not be allowed to co-exist on the same frequency.
4.6.2. Node ID
The Node ID gives the unit a unique ID within the mesh. You can have up to twelve
NETNodes in a mesh and they each must carry a unique Node ID.
You can choose any numbers from 0 to 11 for your Node ID.
A node may choose to automatically reassign its‟ node ID on power if it conflicts with an
existing node on the network.
4.6.3. IP Forward
If this NETNode is connected to an IP source then checking the IP Forward check box will
ensure this data is passed around the mesh for access on other units. A node will forward IP
data when it finds that the data cannot get from the source node to the destination node in
a single hop. Leave this box checked for normal operation.
4.7. Configuration Tab – Streamer Pane
When you have got the asset to the NETNode, you may want to stream that information
down a fixed IP link. The streamer pane enables you to configure this facility easily for
Multicast IP streaming.
Streaming is the transmission of digital audio or video or the listening and viewing of such
data without first storing it.
In Cobham systems we have the ability to carry streams using Multicast, Unicast and RTSP
protocols. The protocol selection is performed within the Global settings tab (see Section
4.4.6 Streaming Protocol).The Streamer pane within the configuration tab is purely
associated with Multicast streams. These streams can come from external or internal
sources. This is controlled by the Source Mask.
To ensure we don‟t overload the bandwidth we want to be able to choose which nodes get
to receive the stream. This is controlled by the Destination Mask.