A HelixNet system/Link Group will support up to 64 endpoints.

Endpoint Resource Limit describes how many audio and endpoint connections the system can be aware of during its operation. HelixNet does also have a network bandwidth limit, which is described in the Network Guide, but this is higher than the Endpoint limit in most normal LAN environments.

Endpoints consume system resources depending on the number of audio paths the endpoint
contains and may include: user stations, assigned HLI and LQ interface ports, program audio inputs, LQ IVC ports, LQ Agent-IC and LQ SIP accounts.

The HelixNet System Resource Limit is not enforced by the system with hard limits. This is intentional to allow advanced users to come up with creative ways to assemble larger systems. To this end HelixNet has been augmented with methods that allow the user to adapt resource usage of the system.
In larger systems it is recommended to balance the loading of endpoints and accounts on the HMS-4X Main Stations in the Link Group. Balancing the resource loading is especially important when the resource limit of the system is exceeded.

Exceeding the system endpoint limits can cause a sluggish system response which is first noticed in lagging response when navigating the front panel menus of the HMS-4X.

Keep in mind when managing system resources

HelixNet endpoints load the resources of the HMS-4X they are connected to (via Powerline or 2W/4W Module installed in the device) or paired to (Ethernet).

LQ Interface ports and active LQ Agent-IC, IVC and SIP accounts load the resources of the system's Link Master. If the port is not needed, un-assigning the port from a channel will conserve resources.

HLI Audio Modules load the resources of the Link Master when their ports are assigned to Channels. If one of the port is not needed, un-assigning the port will conserve resources.

HRM-4X Remote Stations include two audio interfaces which can be assigned to the system's channels. The HRM-4X Remote Station allows you to disable the unit's Program Audio input as well as to configure the Stage Announce output for local use only. This way you can conserve the use of system resources in larger systems from version 4.1 and onward.

HelixNet’s binaural HXII-BP-X5 Beltpack uses twice the amount of system resource than the standard HXII-BP-X4 due to each headphone amplifier being a separate audio destination.

CCM System resource meter

There is a resource meter on the main station device icon showing live resource use of the currently active system setup. The resource meter is found in the Overview page of the CCM on the icon of the individual HMS-4X. Hover your mouse over this icon to see exactly how many system resource units are in use in its current configuration.

Estimating Resource Use

Following chart allows estimation of resource requirements of individual HelixNet devices.

Are there other Limits on HelixNet Systems?

Yes, network bandwidth is a limitation to HelixNet systems and is described in the system’s Network Guide. HelixNet’s internal network is hard limited to 100Mb to conserve electrical power and thermal dissipation.

Endpoint requirements:
Each audio source requires ~300Kb from the input to the HMS when talking.
Each audio destination requires up to ~1,2Mb from the HMS when fully loaded with talkers.

Distribution between Link Group Members (i.e. “Trunking”):
Each audio sources requires ~300Kb from the HMS it is connected to (Powerline or Paired to via Ethernet) to other HMS or LQ who needs its audio.

In normal system sizes/layouts the bandwidth limit of HelixNet is not expected to be exceeded.