Using RFL100 Maintenance Tool to correct sample ID corruption - RFL100

Update advisory for RFL100 Wireless Data Logger with firmware version 1.0.0, 1.1.0, or 1.2.0 Technical Note

Document code
M212775EN
Revision
A
Language
English
Product
RFL100
Document type
Technical note

Required:

  • Computer with a free USB port and running a Windows® operating system. The computer that is running the viewLinc Enterprise Server is recommended for convenience.
  • USB connection cable (USB 2.0 type A - micro-B, Vaisala cable 244961). You can also use a generic cable that has all pins connected (not just power).

  • RFL100 Maintenance Tool from Vaisala. You can download it from this link. The package includes RFL100 firmware version 1.5.0.

RFL100 Maintenance Tool is designed to detect and update problematic RFL100 data logger firmware versions, and to verify and correct the sample ID corruption issue if it has occurred. The tool must be run on the system that is running the viewLinc Enterprise Server software so that it can read the sample ID counters in the viewLinc database.

If the server is not suitable for connecting the RFL100 devices (for example, in the case of virtual servers), you must then transfer the tool and the viewlinc_devices.dat file it creates to another computer that has a free USB port and a Windows® operating system.

  1. Run the tool on the viewLinc server and create the viewlinc_devices.dat file:
    1. Log in to the desktop of the server that is running the viewLinc Enterprise Server software.
    2. Transfer the RFL100 Maintenance Tool package to the system and unzip it to a temporary directory.
    3. Start the RFL100Maintenance.exe application.
      You will see a notification that the tool is unable to find the viewLinc devices file.
    4. Select File > Read viewLinc database....
      A file browser opens, and the viewLinc database file viewlinc.sqlite is already selected.
    5. Select Open to confirm this is the database file to use, and wait for the file to be processed.
  2. If you cannot connect USB devices to the viewLinc server, you must now export the viewlinc_devices.dat file and set up the tool on a separate computer:
    1. Select File > Export viewLinc devices file... and export the viewlinc_devices.dat file.
    2. Copy the RFL100 Maintenance Tool and the viewlinc_devices.dat file to the computer you will be using to connect the data loggers.
    3. Start the RFL100Maintenance.exe application and select File > Import viewLinc devices file... to import the devices file.
  3. Connect an RFL100 data logger. Open the plug that covers the service port and connect the USB cable between your computer and the service port of the RFL100.
    Note that you can connect more than one data logger at the same time. You can change the currently selected data logger from the Connected devices selection in the tool.
  4. Wait for the data logger to be detected and diagnosed. The discovered issues are indicated in the Comments panel.
  5. If the firmware version of the data logger is older than 1.3.0, the Firmware version field is highlighted in red. This means the data logger is currently vulnerable to the sample ID corruption issue. Select Update to update the firmware, and wait for the data logger to be re-detected. Note that the firmware update clears all recorded measurement data from the data logger.
    If the firmware version is 1.3.0 or higher but not 1.5.0, the field is highlighted in yellow. Update is recommended but optional.
  6. If the Sample ID field is highlighted in red, the tool has detected sample ID corruption that must be corrected to allow the data logger to function normally. Select Update to correct the sample ID. Note that updating the sample ID is not available for data loggers with firmware version lower than 1.5.0.
    If you updated the firmware in the previous step, the sample ID may not be shown since all recorded samples have been cleared by the update. If this happens, wait for a couple of minutes with the data logger turned on for samples to be recorded, and reconnect the data logger.
  7. Verify that issues indicated by the tool are now resolved.