Page Type: SYMPTOM
The RADIO MISSING message indicates the Sender searched for its assigned Rangecast scanner ID at all responding COM ports but could not find it. The Sender will be appear on the Configuration screen as Unlinked Sender, without a scanner.
NOTE -- If there are NO COM PORTS then obviously radios cannot be detected even if physically present.
"Radio Missing" means that a scanner expected at a certain PC could not be found by Rangecast Sender software, when searching attached hardware. This may be because (1) the scanner is powered off, (2) the scanner is not connected from PC, (3) the interface hardware (cable or interface box) is defective or not connected securely, (4) a USB problem - some aspect of the USB system may need to be power cycled to recover from an error condition, (5) configuration problem - the Scanner may have been moved elsewhere without updating the current PC's Rangecast's software, so the software is not seeing the expected scanner, or (6) a driver problem - A COM port driver may be wrong, not installed, or corrupted. In any case, Rangecast software on the PC is unable to identify the specific scanner assigned to this ID.
ABOUT CONFIGURATION - When a scanner is used with Rangecast, the Rangecast software on the PC automatically learns the Rangecast ID (e.g. example-10-A) of that scanner, and adds the ID to the list of scanners that are expected to be found when doing a search for attached hardware. The purpose of maintaining such a list, instead of only detecting attached hardware, is so in the event of a hardware problem (such as a disconnected cable) the software can raise an error alarm about the missing radio.
This list of scanners that the PC expects to find can be seen when launching Rangecast, in the panel titled "Group Operation" (listing the senders that will be launched as a group when pressing "Start".) [img-sender_launch]
If a scanner is physically removed without updating this list of expected scanners, the situation looks identical (from a software perspective) to a hardware problem -- an expected radio is missing. The PC will still attempt to find the scanner, and start a Rangecast sender to support the scanner on this PC every time the Rangecast software is relaunched. Therefore, when a scanner is removed or renamed, it is essential to update this list of expected scanners. For more information see
[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.
Sender: Radio Missing error message [img-sender_radio_missing]
Status Page: Sender error code 33 - Radio Missing
(1) RADIO MISSING means there is a mismatch between:
* what hardware the PC expects to find connected (a radio is expected to be there), and
* what hardware the PC actually finds when scanning for connected hardware (the expected radio is not found)
The first step is to determine which side of this mismatch is correct, and which side is in error. In short -- is the scanner identified in the error message *supposed* to be connected to this PC (yes or no)?
If YES: skip to step 2, the problem is that communications with the scanner needs to be restored.
If NO: continue here, the problem is that the PC needs to know that the scanner has been removed from service.
Note: when working remotely without detailed knowledge of the customer site, it may be impossible to find out whether the customer has intentionally removed the hardware. Without this knowledge, it is impossible to distinguish whether hardware has failed or has been intentionally removed -- to Rangecast these look the same. If you don't know what hardware should be there, proceed to step (2) under the hypothesis that there is a technical problem. But if the problem is not easily fixed, consider that the scanner may have been intentionally removed or powered off without updating the software configuration to reflect this change.
If the scanner described in the error message has been physically removed from this PC (or renamed to a new Rangecast ID), and a Radio Missing error is being generated, follow the steps described for removing a scanner. This will remove the Rangecast ID from the list of expected scanners on this PC.
[FAQ-1070] How to remove a scanner from Rangecast service, when it is removed or turned offA scanner can be removed from Rangecast service by disconnecting the scanner from the PC, or powering it off -- and then updating Rangecast Configuration on the PC to indicate that the scanner has been removed. (Without this second step, the PC will report the missing radio as an error condition.)
[FAQ-1073] Notifying Rangecast when a scanner is removed from service, or moved between PCsRangecast Operations tracks the health of the Rangecast system, including detection of scanners that are absent or not operating normally. If a scanner is removed from service, or moved between PCs, or temporarily taken out of service while being relocated, Rangecast Operations should always be notified of this change, otherwise the change may appear to be an incident resulting in a trouble ticket.
[FAQ-1088] How to stop Rangecast software on a feed site PC (temporary stop, not decommission)Rangecast software on a feed site PC includes a "watchdog" process that monitors for software faults, and may automatically relaunch the software if it is not closed correctly. The correct way to stop Rangecast is to click the Rangecast icon, and then press the Stop button.
[FAQ-1085] How to reset the data speed of a model 536 radioFor unknown reasons, the model 536 scanners can switch from the correct baud rate (data speed) 115200 to the factory default value of 4800. If this happens, the data rate can be reset to 115200 using the RC-CONTROL utility software.
[FAQ-1069] How to set the Rangecast ID of scannersEach radio scanner sending content into Rangecast is identified by a unique Rangecast ID, which is set through Rangecast software (configuration interface) on the PC connected to the scanner.
[FAQ-1087] How to permanently disable a failed COM portOn rare occasions, a COM port may experience a failure that cannot be restored to a functional condition. If this happens, the port may be disabled. Afterwards the port will not be available for service, meaning that the PC may not be able to support as many scanners.
[FAQ-1069] How to set the Rangecast ID of scannersEach radio scanner sending content into Rangecast is identified by a unique Rangecast ID, which is set through Rangecast software (configuration interface) on the PC connected to the scanner.
[FAQ-1089] Refresh the Prolific drivers for COM ports (uninstall and automatic reinstall)A problem with a device driver can result in the PC losing data connectivity with a scanner. This can be resolved by uninstalling all COM ports in Windows Device Manager, reinstalling the correct device driver, and then rebooting the PC (which will trigger an automatic reinstallation of these ports.) On occasion, a working system may fail in a way that needs this repair, due to Windows automatically replacing a working device driver with a newer version that is incompatible with our hardware. (The older compatible version is included in the Rangecast installation package, and can be restored when necessary.)
[FAQ-1239] Fixing Windows files for symptom Sender Not RespondingA problem can sometimes occur, apparently within the Windows operating system, that causes Rangecast software to freeze when accessing a Windows DLL necessary for communications over the network. A typical symptom is the senders freezing on launch at the "ping to server" stage. In at least some cases, this can be fixed using a Windows repair utility. (This process is also generally useful for attempting to correct unknown errors in the Windows operating system.)
[FAQ-1249] Remote power cycling of a PC using WebSwitchIf a PC has a WebSwitch rebooter, you can manually request a power cycle and reboot of the PC through an online Rangecast user interface.
[FAQ-1064] How to find the Rangecast ID of a scannerEach physical scanner used for Rangecast has a unique ID. For most scanners (except the model 536), the Rangecast ID of the scanner is briefly shown on the scanner front panel display when the scanner is first turned on. Alternatively, for most scanners (except the model 15), the color of the scanner front panel display is set by Rangecast software to help with identification.
[FAQ-1081] Ensuring scanner power and hardware connectivityFor use with Rangecast, a scanner must be attached to the PC in a way that supports both data and audio connectivity, and the scanner must be powered on.
[FAQ-1083] Power cycling of 536 model scannersBCD536HP model scanners can become unresponsive to computer commands, and cease to communicate with the PC via the data cable / COM port. To restore normal operations, it may be necessary to unplug the power cord from the scanner for about 15 seconds, then try again after the scanner has rebooted.
[FAQ-1084] Power cycle the USB systemOn occasion, some element of the USB system (in either the PC or external hardware) may freeze (probably in firmware), and become unresponsive until it is power cycled. Simply turning a PC off/on may not clear the issue, since many PCs keep minimal power applied to some circuits. To ensure a clean power cycle of the USB hardware, physically disconnect the PC power cable for at least 30 seconds (with Windows safely shut down.)
[FAQ-1160] Installing the device driver for the COM ports (data connection to scanners)The USB data connection between the PC and scanner requires a device driver. The specific device driver to install depends on the type of hardware interface connecting the PC and scanner. The device driver installation software is included in the Rangecast installation software package.
[FAQ-1089] Refresh the Prolific drivers for COM ports (uninstall and automatic reinstall)A problem with a device driver can result in the PC losing data connectivity with a scanner. This can be resolved by uninstalling all COM ports in Windows Device Manager, reinstalling the correct device driver, and then rebooting the PC (which will trigger an automatic reinstallation of these ports.) On occasion, a working system may fail in a way that needs this repair, due to Windows automatically replacing a working device driver with a newer version that is incompatible with our hardware. (The older compatible version is included in the Rangecast installation package, and can be restored when necessary.)
[FAQ-1065] Connecting a limited number of scanners to a partially failed interface boxFor PCs using the old 'black box' hardware interface to scanners, when (1) there is a partial hardware failure resulting in the loss of data and/or audio connections, and (2) it is not necessary to utilize the interface's maximum capacity of 4 scanners (e.g. the PC can be limited to 3 or fewer scanners) -- then this process may be used to establish full connectivity to as many scanners as possible, given the partially failed hardware.
SYMPTOM