Page Type: SYMPTOM
This message means that Multisync is not operating correctly.
Multisync is software that coordinates the scanning pattern of multiple scanners sharing the same programming, so that each transmission is received by only one scanner in the cluster, while other scanners are free to detect simultaneous transmissions on other channels. For low latency (realtime control of scanners), Multisync operates locally (over a LAN, not instead of over the internet) on a 'master' PC arbitrarily chosen from among the PCs participating in the cluster. If the Multisync software freezes, or is somehow blocked from operation, the senders will report that Multisync is unresponsive. This can also happen if attempting to connect PCs into a single cluster that are on different LANs, since the PCs cannot communicate with each other over a shared local network.
A "cluster" is a group of senders operating with the same hub name and feed site number.
[FAQ-1129] What is a Cluster?A group of radio scanners operates as a "cluster" when all of the scanners are programmed to receive the same channels, and the scanners operate collaboratively via Multisync to efficiently receive transmissions on these channels. Each cluster is associated with a "cluster number", channels are assigned for reception to a particular cluster (by number), and scanners within a cluster (with the hub and number as part of its Rangecast ID) are programmed to match the programming assigned to the cluster.
SYMPTOM on Sender - NO MULTISYNC error message - Image below
CORRECTING A MULTISYNC FAILURE -- First simply wait about 20 minutes, and the Sender may automatically fix the problem. If that does not happen, then follow procedure below to check, confirm and repair possible misconfiguration.
1) WAIT FOR 20 MINUTES BEFORE INTERVENING -- The problem may be automatically repaired.
[FAQ-1077] Rangecast will clear some problems automatically - It may be best to wait 20 minutes.The Rangecast system is designed to be self-healing from many common problems. Although errors are generally reported quickly so you can be aware of performance and current operations, for many errors, it is often advisable to wait for 20 minutes and see if the problem corrects itself without intervention. If the cause of the problem is that some computer is temporarily offline (e.g while rebooting, undergoing maintenance, or subject to a temporary network outage), this allows time for the computer to recover and resume normal operations. Similarly, some aspects of the Rangecast system are designed to wait for a few minutes before attempting to automatically reconfigure or correct problems.
[FAQ-1074] How to remove a scanner from Rangecast serviceWhen a Rangecast scanner is removed from Rangecast service (while the PC remains operational), then either the scanner's Rangecast ID must be changed to a special value (if the scanner remains connected) indicating that the scanner should not be used, or (if the scanner is disconnected) the Rangecast Configuration on the PC must be informed that the removed scanner is no longer expected on the PC.
[FAQ-1075] How to move a Rangecast scanner from one PC to anotherWhen a scanner is moved from one PC to another, in addition to moving the scanner itself (and possibly associated hardware), changes in Rangecast Configuration are needed on the PC where the scanner was removed to notify that PC that the scanner is no longer expected there. In addition, if the scanner is a model 536, Rangecast Configuration changes are needed on the PC receiving the scanner, to set the scanner's Rangecast ID.
[FAQ-1078] How to check that Rangecast has correct network permissionsRangecast feed site software only uses outbound connections to the internet (similar to a web browser), with no inbound connections from the internet, so in general there is no need for special network permissions. However, two components of Rangecast software (multisync.exe and rc-awsd.exe) must have permission in Windows to communicate within the LAN; for example, multisync serves as a communication service between PCs on the same LAN to coordinate scanner tuning for maximum efficiency. The Rangecast software, when installed, should have the correct permissions in Windows. However, if these permissions are changed for any reason, it may be necessary to restore the correct Windows settings to allow Rangecast operation.
[FAQ-1078] How to check that Rangecast has correct network permissionsRangecast feed site software only uses outbound connections to the internet (similar to a web browser), with no inbound connections from the internet, so in general there is no need for special network permissions. However, two components of Rangecast software (multisync.exe and rc-awsd.exe) must have permission in Windows to communicate within the LAN; for example, multisync serves as a communication service between PCs on the same LAN to coordinate scanner tuning for maximum efficiency. The Rangecast software, when installed, should have the correct permissions in Windows. However, if these permissions are changed for any reason, it may be necessary to restore the correct Windows settings to allow Rangecast operation.
It is possible to custom-configure a sender to use Multisync in a mode where the LAN address of the master is a fixed value, not dynamically assigned. In this case, the sender will show some value other than [M] or [S] on the Multisync line. This is a very rare circumstance preserved for backwards compatibility, and is not a recommended configuration.
[FAQ-1094] How to remove the INI file for one sender on a feed site PCEarly versions of the Rangecast software had each sender on a PC operate entirely independently of the others (no configuration page to view settings for all senders in one place) with settings for each sender stored in a separate INI file generated by that sender's "Setup" page. This feature is still used in the rare case of VOX senders, but in all other cases is deprecated. Automatic settings have been developed that eliminate the need for customization in most situations, and when necessary any customization should be done in the "Special Settings" box of the configuration screen, where the settings are more visible (and it's possible to ensure all senders are set as desired.) This process describes how to remove the INI file, and transfer any manual settings that you want to preserve to the "Special Settings" parameter.
Rangecast dynamically assigns a Master PC for each cluster (group of senders with the same hub and feed site number, e.g. example-10). Which PC operates as the master may change on occasion, usually in the event that a former master experiences an internet outage lasting more than 10 minutes. Therefore, whether a particular PC is operating as a master or slave is a temporary designation, not a permanent condition.
INDEX