*
> Q file problems... <
 
 

The "HT" lines in a 3-way (tri) RVM are all glass such as "HT HGF"

The barcode counts are mostly zero even though the machine took many containers.

The meter reading goes down over time in an RVM attached to a SC.

The barcode counts have been reset to zero

The barcode counts get reset to zero after the site controller has a lingering communications problem with the RVMs.

A Q file is not created after selecting "retrieve barcode data from RVM" from PCRVM.

The first "MP" line (meter reading) in the Q file contains bogus data such as "MP :54".

The first "MP" line (meter reading) in the Q file is appended to the last "HI" line.

The "HI" lines in the download data (Q file) retrieved from an RVM are all on the same line.

The download data (Q file) retrieved from an RVM is in an incorrect format (some lines longer than others).


The "HT" lines in a 3-way (tri) RVM are all glass such as "HT HGF"
[added 3/16/12] Make sure “Support 3-way enhanced capacity glass” is unchecked in WinRVM’s Barcode Options (iPAQ) / General Options (PC). When this is enabled it treats a tri RVM as a 3-way glass RVM, which when downloading, causes all the machine type header lines in Q file to show up as glass.
This setting is currently only used in certain RVMs in Iowa and Hawaii.

The barcode counts are mostly zero even though the machine took many containers.
[added 11/10/10] If this is for an interactive RVM or other barcode client RVM, this is related to a bug in WinRVM versions prior to 3.0.8 and pocket WinRVM  versions prior to 1.6.3. See WinRVM 3.0.8 for more info and a workaround.

The meter reading goes down over time in an RVM attached to a SC.
[added 12/15/03] If an RVM controller board is replaced, the last known meter reading count (from the previous successful scheduled call) will be reloaded into the RVM controller. For example, if an RVM controller dies and is replaced at 6pm, the counts from the previous night's scheduled call will be reloaded into the RVM. Note that only the meter reading and other misc counts (the "MP" lines in a Q file) are restored. The barcode counts are zeroed. The end result is that the meter reading will appear to go down. 

This same scenario will occur if an RVM "code space CRC error" occurs; the meter readings will be restored, but the barcode counts will be zeroed. The "code space CRC error" is automatically detected and fixed by the site controller - no controller board replacement is necessary. 
If a "table space CRC error" occurs, the meter reading, all counts and all barcode counts are zeroed. A "table space CRC error" will occur if the memory containing the RVM tables get corrupted somehow (see The barcode counts have been reset to zero below).
If any CRC error happens more than once in a single RVM controller, the RVM controller should be replaced as the memory may be defective (or perhaps the battery is simply low).

The barcode counts have been reset to zero
[updated 7/29/03] For site controller installations: this happens when a "table space CRC error" occurs, which means the RVM's "table space" memory has changed somehow (not by the site controller program). This can occur for several reasons:

  1. A table (barcode, parameter, whatever) was sent to the RVM by a program OTHER than the site controller. For example, PCRVM or WinRVM was used to send a voucher template to the RVM.
  2. The RVM's memory was corrupted due to hardware failure/glitch such as an electrical spike caused by lighting or hardware component failure on the RVM controller board.
  3. The file c:\cf1500\rvmload.db on the SC got corrupted such as by hard disk failure. This file stores the current CRC of the RVM's memory and is updated each time the SC sends a table to the RVM.
  4. The RVM controller board was replaced.

Whenever the site controller detects a "table space CRC error", it assumes the RVM's table memory is corrupted. The following sequence is performed:

  • The counters table (table 2) and the barcode tables are retrieved from the RVM and saved in the c:\cf1500\upload directory with a file name ending in ".xxx" such as 11111102.xxx which represents table 02 for RVM serial # 111111. A Q file is *not* made. These files are transmitted to the host system the next time a scheduled call occurs.
  • All RVM tables are sent to the RVM except the RVM program.
    Note: the counters table (table 02 which corresponds to all the MP lines in a Q file) that is sent to the RVM is the counters table from the last time the RVM's barcodes were retrieved from the RVM for a scheduled call (specifically, the c:\cf1500\upload\ssssss02.uld, where ssssss=6-digit RVM serial #). This means the RVM's meter reading and various counts will be reset to the last time a Q file was made, most likely the previous night.
    Note: if the RVM controller board is replaced, make sure the RVM's serial number is set correctly! If the serial number is set to another RVM's serial number at this site, the wrong counters will be loaded to the RVM!
  • The SC logs "Volume Counts Reset to Zero" which means all the RVM's barcode counts have been zeroed.
  • Here is a sample sc_event.log snippet for this sequence:
    <051111> 07/25/03 11:41:59 -- W751: RVM Table Space CRC Error
    <051111> 07/25/03 11:42:10 -- T001: Upload Table 02
    <051111> 07/25/03 11:42:19 -- T001: Upload Table 07
    <051111> 07/25/03 11:42:24 -- T002: Download of MESSAGES.TBL
    <051111> 07/25/03 11:42:27 -- T002: Download of UPLOAD\05111102.ULD
    <051111> 07/25/03 11:42:29 -- T002: Download of PA051111.TBL
    <051111> 07/25/03 11:42:32 -- T002: Download of PINS.TBL
    <051111> 07/25/03 11:42:34 -- T002: Download of CASH.VOU
    <051111> 07/25/03 11:42:35 -- T002: Download of COUNTERS.VOU
    <051111> 07/25/03 11:42:37 -- T002: Download of IND_WT.VOU
    <051111> 07/25/03 11:42:38 -- T002: Download of SCROLL.TBL
    <051111> 07/25/03 11:42:39 -- T002: Download of SI051111.TBL
    <051111> 07/25/03 11:42:52 -- T002: Download of PBARCODE.TBL
    <051111> 07/25/03 11:43:03 -- E757: Volume Counts Reset to Zero

    The barcode counts get reset to zero after the site controller has a lingering communications problem with the RVMs.
    [added 6/26/02] If PCRVM on a laptop or HUSKYRVM on a Husky handheld are used to send barcodes (or any table  such as a PIN table, voucher template, etc.) to an RVM, this changes the RVM's memory. The next time the site controller is able to communicate with the RVMs the site controller will detect that the RVM's memory has changed unexpectedly and log a "W751: RVM table space CRC error" and proceed to reload ALL tables to the RVM(s), which zeros out the barcode counts.
    For site controller installations, DO NOT use PCRVM/HUSKYRVM to change data in the RVM! However, it is OK to retrieve barcode counts from an RVM using PCRVM/HUSKYRVM since this doesn't change the RVM's memory.

    A Q file is not created after selecting "retrieve barcode data from RVM" from PCRVM.
    [added 3/24/00] This can occur if the RVM's machine type is not set. Select "Set/Modify RVM Identification" from the main menu and make sure all fields are accurate. 
    PCRVM versions 3/29/00 and later will display the error message "RVM type not set!".

    The first "MP" line (meter reading) in the Q file contains bogus data such as "MP :54".
    [added 3/24/00] This can occur if the RVM's counters table (table 2) timestamp is somehow set to a very long string. Upgrading PCRVM/Site Controller to the latest version (PCRVM 3-23-00/SC 1.40 or later) may fix the Q file problem. The RVM software may need to be reloaded to fix this error.

    The first "MP" line (meter reading) in the Q file is appended to the last "HI" line.
    Site Controller versions 1.35 and 1.37 have a bug that omits a line-feed character after the last "HI" line containing the RVM's software version (the line prior to the first "MP" line).
    This only occurs when using RVM software versions after 12/4/97.

    For example, here is a normal Q file:

    HI RVM 1500 Jun04'98 09:22 (AP,C,650000)
    MP 00000123
    MP 00000000
    ...

    Here is a Q file produced by versions 1.35/1.37:

    HI RVM 1500 Jun04'98 09:22 (AP,C,650000)MP 00000123
    MP 00000000
    ...

    The "HI" lines in the download data (Q file) retrieved from an RVM are all on the same line.
    This occurs when an RVM that has never had barcodes loaded to it is downloaded. Look at the "MU" lines, if there are no barcodes, than this is the case. Send barcodes to the RVM before downloading it. Note: SC1500 ver 1.36 and later and PCRVM versions after 5/18/98 correct this problem.

    The download data (Q file) retrieved from an RVM is in an incorrect format (some lines longer than others).
    [updated: 11/18/04]: If the Q file contains strange characters in it, upgrade to the latest version of PCRVM/HUSKYRVM, as versions from 11/99-5/15/02 have a bug related to the binary barcode feature. If that doesn't fix the problem, try setting FORCEASCIIBARCODES=1 in SC_CTRL.PRM (for SC installations) or PCRVM.INI/HUSKYRVM.INI (for PCRVM). 

    For Site Controllers running on old PCs, make sure the PC has the turbo button depressed (turbo on).
    Note: if the turbo switch is set for ‘non turbo’, don’t just press the turbo button and walk away, because the Site Controller requires the speed to be recalibrated. The proper way to enable turbo mode is to press F10 and wait for the SC program to exit, then press the turbo button before the SC program begins again. It is a good idea to disconnect the turbo switch from the motherboard to prevent it from accidentally being pressed. If the turbo switch is on and the speed calibration is still low, check the CMOS setup to make sure the internal and external CPU caches are enabled.
    Note: if just one of the RVM's Q files are corrupted in this manner:

    • Make sure the latest SC, RVM, and MON ROM software are running the latest versions, as old versions may have communications bugs.

    • If this still doesn't fix the problem, then the problem is either related to that particular RVM or COM port/cable. Swap COM ports with another RVM and see if the problem follows the COM port or the RVM. If it follows the COM port, then replace the Quatech card (or use the built-in COM1 or COM2). If the problem follows the RVM, swap the RVM board.

    • Upgrade to a faster PC.

     
     

             word = Microsoft Word document (download free viewer from Microsoft)
              floppy = downloadable software
              Need translation? Try FreeTranslation.com, Babelfish, Google translate
              page last updated: 11/27/13 10:37 AM