/
Wireless: Tempest 2400 beltpacks having problems switching between base stations
Wireless: Tempest 2400 beltpacks having problems switching between base stations
Question: I have two Tempest 2400 systems version 3.00 that I have co-located in a RF overlap zone. The base stations are approximately 500 feet apart from each other. I have the beltpacks registered to both base stations and am using the I-Select roaming feature to switch the beltpacks from one base to the other. When I attempt the switch over the beltpacks from one base to the other base they will not switch until I power cycle the beltpack. The network and lockout numbers on both bases are set to 00 and 255 respectively. Why am I having problems?
Answer: With each base stations network and lockout set to the same numbers the beltpacks are going to have problems switching manually from one base to the other because the RF hopping patterns are the same and causing each base stations RF carrier to interfere with the other. To rectify the situation change the network number on one base station from 00 to 01 or 02 (The network number for a version 3.0 system group can be 00 to 10). Also change the lockout code to a different number (254 or lower).
Once this is done repair the beltpacks to the base station so that they can "register" the new network/lockout numbers. The beltpacks will now be able to manually select via I-Select roaming the base station of choice, and you should notice that the RF range will be improved since each base station is no longer interfering with the other base station.
Answer: With each base stations network and lockout set to the same numbers the beltpacks are going to have problems switching manually from one base to the other because the RF hopping patterns are the same and causing each base stations RF carrier to interfere with the other. To rectify the situation change the network number on one base station from 00 to 01 or 02 (The network number for a version 3.0 system group can be 00 to 10). Also change the lockout code to a different number (254 or lower).
Once this is done repair the beltpacks to the base station so that they can "register" the new network/lockout numbers. The beltpacks will now be able to manually select via I-Select roaming the base station of choice, and you should notice that the RF range will be improved since each base station is no longer interfering with the other base station.
, multiple selections available,
Related content
Wireless: Tempest Beltpacks won't register consistantly with paired Base Station
Wireless: Tempest Beltpacks won't register consistantly with paired Base Station
More like this
Wireless: Having issues with Tempest beltpack operation after upgrade to version 3.00
Wireless: Having issues with Tempest beltpack operation after upgrade to version 3.00
More like this
Wireless: Tempest Beltpacks show "Slot Occupied" Message when paired to Base Station
Wireless: Tempest Beltpacks show "Slot Occupied" Message when paired to Base Station
More like this
Wireless: Tempest Beltpacks go into searching mode while roaming
Wireless: Tempest Beltpacks go into searching mode while roaming
More like this
Wireless: Will having 2 Tempest 2400 version 2.10.01 basestations next to each cause interference
Wireless: Will having 2 Tempest 2400 version 2.10.01 basestations next to each cause interference
More like this
Wireless: Tempest Network / Lockout default codes as shipped from factory
Wireless: Tempest Network / Lockout default codes as shipped from factory
More like this
CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT
This solution was provided by Clear-Com via a question submitted to us by customers like you. If you wish to share with us a new solution or update an old one, please follow this link..
The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.