Rangecast FAQ
[FAQ-1065] Connecting a limited number of scanners to a partially failed interface box


Page Type: SOLUTION


OVERVIEW

For 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.


BACKGROUND

Each scanner has two connections to the PC -- a data cable, and an audio cable.


METHOD

Note: This process should only be tried after working through repair options that address failures in the USB system or device drivers. These failures are more common, and can be repaired more easily than the test process described below.

(1) Identify the Rangecast ID of each physical scanner connected to the PC


[FAQ-1064] How to find the Rangecast ID of a scanner

Each 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.


. Method 1 is preferred, since the current problem may interfere with the Rangecast software's ability to set the front panel display color on the scanners.

(2) Ensure that each scanner is powered on, connected to the black box with two wires (data and audio), and that these connections are secure. Also check that the black box is connected to the PC with two USB cables, and that these connections are secure.

(3) Launch Rangecast and press 'Configuration'. Wait until the software has completed polling the hardware.

(4) List the Rangecast ID of scanners reported on lines that begin COM. These scanners have working data connections to the PC.

(5) List the physical scanners enumerated in step 1 that are NOT on the list of scanners with working data connections created in step 4. These scanners do NOT have working data connections to the PC.

(6) For the scanners enumerated in step 5 (no working data connection), unplug the data cables and set them aside. Then try connecting other unused data cables (from the black box) to these scanners in their place. With these changes made, repeat from step 3.

If there are scanners without working data connections, and no further unused data cables (excluding those which have been set aside due to failed tests), then remove these scanners (disconnect from the black box, and set aside). No working data connection is available, and these scanners cannot be brought online with this method.

(7) At this point, all remaining scanners should have good data connections, and we will proceed to work on audio connectivity. Launch Rangecast and press 'Configuration'. Wait until the software has completed polling the hardware.

(8) List the Rangecast ID of scanners with a A# value shown in the audio column (e.g. A1, A2, A3, etc). These scanners have working data and audio connections to the PC, and should be operational.

(9) List the Rangecast ID of scanners on lines starting COM where the audio column does NOT show a specific value (e.g. '?'). These scanners may not have working audio connections to the PC (but the test here is not definitive, these may be working.)

(10) If there are NO scanners in the list from step 9 (e.g. all scanners on lines starting COM have shown a A# value in the audio column), then STOP -- these scanners have working data and audio connections, and you may resume normal operations.

(11) If there are any scanners in the list from step 9 (audio connection suspected of not working), close and relaunch Rangecast software, and repeat the 'Configuration' (waiting until the software has completed polling the hardware).

(12) ONLY considering the scanners in the list from step 9 -- see if a A# value is shown in the audio column. If so, the scanner has working data and audio connections (despite the prior uncertain test result), and can be removed from the list generated in step 9 of scanners that may not have working audio connections.

(13) If there are any scanners remaining on the list from step 9, unplug the audio cables from these scanners and set the cables aside. Then try connecting other unused audio cables (from the black box) to these scanners in their place. With these changes made, repeat from step 11.

If there are scanners without working audio connections, and no further unused audio cables (excluding those which have been set aside due to failed tests), then remove these scanners (disconnect from the black box, and set aside). No working audio connection is available, and these scanners cannot be brought online with this method.

Note: if this process does not result in a sufficient number of scanners being brought online, then the hardware may need repair or replacement.


CITATIONS

SYMPTOM


Rangecast FAQ - ID 1065 - last updated 02 August 2017     Images shown - [block]