All Trinity-300 nodes (300/316/318/323/216 etc.) come with the exact same firmware. All Trinity-800 nodes (800/816/823 etc.) comes with the same firmware.

This means that the same manual applies to all Trinity-300 nodes and the same manual applies to all Trinity-800 nodes.

Note: The only thing to keep in mind here is that Trinity 300 and Trinity 800 nodes have different firmware and manuals and that they are not compatible with each other.

You find the manuals under “Documents” under the respective product category (Trinity-300 or Trinity-800) here: http://www.repeatit.se/product-support/trinity/

1546 Bytes

How to set up and configure a Trinity node is described in the radio node manual (and the Quick start guide) that  you can find here:


Click on “Documents” under the product type (Trinity 200/300 or Trinity 800) that you want to configure.

Possible reason Suggested action
Tidal waves (link mounted over water and antennae are not moving) –         Use narrow-beam antennae (less multipath fading, better link budget)

–         Use narrower channels (20MHz rather than 40-80MHz)

–         Monitor link trend in Repeatit’s cloud service

Tidal waves (link mounted over water and antennae are moving since they are mounted on a boat etc.) –         User wider beam antennae (23dBi etc.)

–         Consider configuring a multipoint system (requires an extra non-Repeatit box behind the client links to steer traffic right)

Link signal quality (RSSI) drops –         Is the link configured over water? If yes, see above.

–         Check the cloud management system to figure out when the RSSI dropped. Can it be related to some specific event (e.g. someone climbed the mast the same day)?

–         Did it drop on both sides of the link or just one? Did it drop for both antenna chains or just one? Collect information and contact your support if nothing of the above helps.

Link performance goes down –         Check the signal strength (RSSI bars) on both sides of the link. If they are all over 23-25dB it is normally ok.

–         Check the PHY Errors rate and Checksum Errors rate on both sides. If it has gone up on one of the sides, it could indicate interference from some other system. Perform a spectrum scan and look for another channel.

Yes, this is common if one of the following conditions hold:

  1. The Fresnel zone is not clear (see figure below where the waves are close to the Fresnel zoner boundary). Even if the zone is not exactly on the boundary you could experience problems. The issues get worse the more opening angle and stronger side lobes you have on your antenna. The reason is that you get multipath copies that bounce off the water and arrive at the receiver with misaligned phase. This results in lower received signal strength or it might just corrupt the packets. You will see this as low RSSI (compared to what is expected) and/or high levels of retransmissions, PHY errors and checksum errors.


Remedy: Use radio nodes with external antenna ports and connect high gain parabola antennas on each side. This gives you higher RSSI margin and reduces the main/side lobes which gives less multipath propagation.

  1. One (or both) of the antennae is moving due to that it is placed on a boat or something similar. In these cases, it could be wise to set up two or more clients on different heights and configure the system in a multipoint fashion to increase the stability.

Tip 1: Tidal waves don’t just follow a 24-hour cycle. They also vary in height based on the position of the moon and sun so the actual height of a high wave is different each day during a month. By using Repeatits free cloud service, you can easily monitor the trends for your links and correlate the link performance and RSSI figures with the tidal wave information.

Tip 2: Unless you really need bandwidth, use a Trinity 323 configured at a 20MHz spectrum bandwidth (rather than 40MHz) and enable the Packet Heal functionality but setting the “Always buffer” parameter to Yes and change the “Reordering level” parameter to High in the Trinity radio’s web GUI configuration tab. This will improve TCP level stability if you have packet errors as additional error correction is added on top of the normal radio layer error correction.

The power consumption depends on the Trinity model. Please refer to the data sheet of each product where these values can be found. You find the data sheets here: http://www.repeatit.se/products/trinity/

802.1Q and 802.1p are both supported (we prioritize on 802.1p or on DSCP and 802.1p is overriding any IPTOS settings)

VLAN ID is supported

802.1D is not supported (Spanning Tree is not implemented)

Trinity links support QinQ transparently, but do not tag/untag double tagging. This means packets are sent through but the Trinity nodes do not do any VLAN handling or QoS priority handling of the secondary tag in the client as of today.

Trinity clients support trunk (up to 10 trunk VLANs allowed in/out). One VLAN can be configured as “access VLAN”. It is also possible to configure a mix of trunked and a mixed VLAN. So yes, all of these are supported.

Regardless if you have lost connectivity by simply forgetting the IP address of a node or accidently set the wrong management VLAN, the Repeatit Restore To Default (RTD) utility can be used. The tool can be downloaded on this link (where you also find instructions on how to use it): http://www.repeatit.se/product-support/utilities/


Please refer to the link budgetizer tool here: http://www.repeatit.se/tools/link-budgetizer

No, this is currently not possible.

Node upgrade is explained in the manual. You find the manuals by clicking on the right product here and then select “documentation”: http://www.repeatit.se/product-support/


The latest firmware for Trinity nodes can be downloaded here (find the “latest firmware” section on the right hand side): http://www.repeatit.se/product-support/trinity/

On the client side you normally go for the SU units that are more cost effective. In Repeatit’s case this means that you get an integrated 30 degree antenna. The clients use this antenna to get a good mix of:

  • Radio performance (good signal strength over long range).
  • Low injected interference and noise in concurrent systems in the vicinity that might operate on the same channel.
  • Ease of installation.
  • Client unit size.

If you would like a wider/narrower opening angle to improve the range or ease of installation, it is possible to use one of the base station units (there is one with N-connectors if none of the integrated antenna versions fit) and configure it as a client as this normally is supported in software (always check with Repeatit before going ahead with any such plans so that we can verify that the software is supported). Also, we recommend that you do the planning of your network in our Link Budgetizer tool (that can be found here: http://www.repeatit.se/tools/link-budgetizer) in order to verify that your antenna configuration delivers the expected performance.

Yes, our Trinity-300 system support very precise synchronization for both links and sites.

Link synchronization:

As Trinity-300 nodes use a Time Division Duplex (TDD) based access protocol, it means that you are in full control of the exact bandwidth that can be configured uplink and downlink per user (with overbooking options)

Site synchronization:

As TDD protocols have well defined Transmission (Tx) and Receive (Rx) windows, meaning you know exactly when you transmit and receive, several radios on the same site can share the exact same frequency if two conditions are met:

  • Same Tx/Rx window size, typically 50/50.
  • Enough antenna isolation. This is normally very easy to obtain, especially for Point to Point links facing different directions.

We have installations where many base stations are sharing the same channel of operation. To synchronize several nodes at the same site, the nodes are inter-connected via our SyncMaster network switch that provides precise timing via a GPS-controlled clock.

The number of supported clients is 31 on both the Trinity-300 and Trinity-800 platform. As both latency and throughput are functions of the number of connected users, it often makes sense to connect fewer users than the maximum. We normally recommend that you start off building a traffic model that can be used when designing the network. Reach out to us if you have questions on how to do this.

Point to Few comes from the fact that our Trinity-300 series supports Time Division Multiple Access (TDMA). The radio connectivity makes use of time slots where a base station and its connected clients share 31 slots for uplink and downlink traffic on the same frequency band. This also means that we limit the number of connected clients to maximum 31 per base station. In many cases, customers choose to connect even fewer clients per base station as this means lower latency and higher throughput per client. If you have questions about the number of connected clients in your network, please reach out to us and we will help you looking at the traffic model and recommend a proper configuration.

Tag: Trinity

Yes, this is what our products initially were developed for. We have Point to Multipoint systems deployed in over 50 countries today.

Load More

Contact us today for pricing, technical support & more info