Clear-Com Solutions  
Solution 1822 : Wireless: Can I select certain Wi-Fi channels for Tempest 2400 to hop on?
 
Question:  Can the Tempest 2400 systems RF signal be set to hop only in specific parts or channels in the 2400MHz Wi-Fi band channels 1 to 14? 

Answer:  Tempest offers seven operational bands inside the 2.4GHz ISM band so that the user can select the frequency band that is appropriate for the regulations and operational considerations of the location. It is the user’s responsibility to select a frequency band that is legal for the country of operation. Legal 2.4GHz operation may vary from country to country. Many countries allow full use of the 2400 – 2480MHz spectrum, but many do not. Please check with your local RF specialist to ensure that you pick an operational frequency band that is legal for your country.

Even in locations that allow full band operation you may wish to choose one of the limited operational frequency bands. This may be the case if you would like to keep Tempest from operating in a given portion of the spectrum to avoid a specific Wi-Fi device or some other interference source. Having said that, Tempest works well even when collocated with Wi-Fi or other 2.4GHz devices, so using as much of the band as your country of operation allows is usually the best idea.
The seven operational frequency bands available for Tempest are: 
















To access this menu go to the Tempest base station "Tech Menu" and select "Radio Configuration" menu / "Set Band" to select the most appropriate Band #.

Choosing the lowest number band that is legal in the country for which you are operating, will usually produce the best results. The lower the band’s number the more channels and spectrum available for Tempest to use. This helps ensure that Tempest will have plenty of room to hop and avoid interference sources that may be present in your area.

Note: if you change the RF band, you will need to re-register your beltpacks


Related Attachments
 None Found



  



Most popular solution: Hotfix for EHX failing to launch after .Net update.