TROUBLESHOOTING |
|
The most common problems users encounter with CAPTURE involve the program failing to start up properly, the failure to detect connected RAD7s, and errors in downloaded RAD7 data. Solutions to these issues are described below. |
|
CAPTURE Fails to Launch | If CAPTURE fails to launch on Windows XP and displays a dialog box similar to the one shown below, it may be because the version of CAPTURE that has been installed is too new to run on an older operating system. The solution is to install a legacy version of CAPTURE. See the the Legacy Versions of CAPTURE page on the Durridge website for details. If CAPTURE launches but fails to display the splash screen and the Main Window, it may be the result of a problematic preferences file. The solution is to restore the default preferences file. This is achieved by holding the Shift and Control keys as CAPTURE starts up. A dialog box will appear prompting for a confirmation to proceed with the operation. If this dialog box is not immediately visible, check to make sure that it is not hidden behind a folder or other window. Once the preferences have been reset, CAPTURE will start up normally. Be warned that all custom-configured RAD7 profiles and other settings will be lost. |
CAPTURE Launches Slowly | When CAPTURE starts up, it examines each serial port on the computer, including Bluetooth-enabled serial ports, to determine which ones can be used to communicate with RAD7s and other devices. Usually this process takes a fraction of a second for each port, but under certain conditions it can take substantially longer. If CAPTURE is taking a long time to launch, it may be because it is evaluating one or more problematic serial ports. To avoid this, unpair and delete any unneeded Bluetooth devices, such as mobile phones, Bluetooth audio speakers, and improperly configured Bluetooth to serial adapters. The process for removing such devices differs depending on the operating system version. |
Device Detection Failure |
If CAPTURE is unable to detect a connected RAD7 or DRYSTIK, the following steps may be helpful. General Solutions:
RAD7 Detection Solutions:
DRYSTIK Detection Solutions:
After performing the above checks, if the device is still not recognized, try restarting the device and your computer. If another computer is available, try to connect on the other one. It is important to determine whether the problem lies with the instrument or with the computer. This requires connecting a different serial device that is known to work, such as a modem or other instrument. Use a terminal emulation program such as Durridge Terminal or TerraTerm, and attempt to communicate with the device. If communication is successful, then it is possible that there is a problem with the instrument or CAPTURE. If communication is unsuccessful, then it is more likely that the computer is not properly configured with the serial to USB adapter driver. |
RAD7 Data Errors |
When RAD7 Data is opened in CAPTURE the program evaluates the data, and if one or more problems are detected a notification will appear at the top right corner of the graph display, along with a button labeled "Details..." Clicking this button displays the Data Errors Window, which lists the problems in the data set. The Data Errors Window can also be opened by choosing the Show Data Errors... command in the File Menu. Data records that are too damaged to be parsed will not be displayed as points on the graph, and CAPTURE will identify such records in the Data Errors Window using octagonal stop sign icons. Records that are problematic but salvageable will appear on the graph, and they will be identified in the Data Errors Window using alert icons. Records that are only slightly problematic will be identified in the Data Errors Window using information icons. |
Zero Live Time Notifications It is not uncommon for a message such as the following to appear in the Data Errors Window: This message indicates that the Live Time values for some of the RAD7 data cycles was zero, which means that the operation of the RAD7 was interrupted at or near the beginning of the cycle, and the instrument did not actively record data for that particular cycle. This can occur if the RAD7 keypad is used to choose 'Test Save' before a radon measurement has started, causing the current cycle to be stored with a recorded duration of zero. It can also be caused if 'Test Save' is used to advance to the next cycle within the first 6 seconds of a cycle's progress. Radon concentrations are calculated by dividing the count rate by the Live Time, so when the Live Time is zero the reported radon concentration may be reported as a nonsensical number, rendering the cycle invalid. This problem does not compromise the integrity of the other cycles in the data set, so the remaining data points will still appear on the CAPTURE graph. |
CAPTURE's Print command may fail on certain Windows 7 configurations. If this happens it is recommended to use the File menu's Save Graph Picture command instead of the Print command, and then open the resulting PNG image in a different program for the purpose of printing. Another solution is to install the legacy version of CAPTURE for Windows. See the the Legacy Versions of CAPTURE page on the Durridge website for details. |
On Windows 10 systems, the labels on graphs and status bars may appear misaligned if the display is set to an irregular scale setting. To correct this, go to the Start Menu and choose Settings, then open the Display panel. In the Scale and Layout section, set the size of the on-screen elements to a whole value such as 100% or 200%, as shown in the screenshot below. |
If you think you have found a bug in CAPTURE, please let us know. DURRIDGE's software development staff can be contacted at software@durridge.com. |