CF1500 / LCM (Flex) / HDS Parameter Descriptions

 

Default value:  the value the RVM software will assign to this parameter after a parameter table is sent to the RVM but the parameter was not in the table.

Required: 2=fail (required parameter), 1=log warning, 0=don't log warning

Allow edit: allow the value of this parameter to be changed via the RVM keypad.

In alphabetical order (by section):

Common parameters (not all versions support every parameter; not all supported by Flex or HDS):

Parameter Description Default value Re-
quired
Allow
edit?
ACCEPT_DELAY Delay time (x 100 ms) after accepting a container before accepting the next one. Useful in the bottle RVMs to prevent customers from inserting the next bottle too quickly, possibly causing crusher/shredder jams if the crusher/shredder can't keep up with the customer. 0 0 Y
ACCEPT_SIDE

Defines which bin to send accepted container.

0 = Instantly accept container without regard to bin.
1 = Accept to either side.
2 = Accept to left side only.
3 = Accept to right side only.
4 = Use silo table (silo 1 to left, silo 2 to right, bin 3 to far right).

4 0 Y
ALARM Turn on the alarm/page for certain errors (add [n] values in red):
 BIT 0 = [1] store-fixable errors: bin full/overflow, printer/coin errors, bail fails, rescan fail, DROPDETECT fail, Bottle Standing Unit (Norway version)
 BIT 1 = [2] errors requiring Envipco technician: crusher/shredder stall, scanner, diverter, crusher motor overload tripped, out of coupons,
 BIT 2 = [4] errors requiring computer support: parameter/voucher template missing
Parameter added in RVM version 3/22/06.
Not used in XMT versions of software.
1 0 Y
ALARM_ENVIPCO Turns alarm ON for failures requiring ENVIPCO technician: shredder stall, etc.
Parameter removed in RVM version 3/22/06, replaced with ALARM parameter.
0 0 Y
ALARM_STORE Turns alarm ON for store fixable errors: bin full, printer/coin errors, Bail fail.
Parameter removed in RVM version 3/22/06, replaced with ALARM parameter.
1 0 Y
ALARM_SYSTEM Turns alarm ON for errors requiring computer support: Bar code file errors, etc.
Parameter removed in RVM version 3/22/06, replaced with ALARM parameter.
0 0 Y
ALUM_POINTS Defines how many points to pay per alum can.
Note: Japanese versions only use xx.xx format (example: 100 = 1.00 points).
For card reader versions of RVM software only.
0 0 Y
ALUM_SENSOR

This parameter refers to the can coil, which is used to detect aluminum and steel cans. Set ALUM_SENSOR=1 to enable the sensor.
If a can coil is installed in a glass or PET machine, this sensor can be used to reject cans by setting ALUM_SENSOR = the minimum number of can counts to tolerate before rejecting the container.

0 0 Y
ALUM_VALUE if non-zero pay DEPOSITn-1 for aluminum cans, ignoring value in barcode table. Max value=4 = DEPOSIT3
For RVM versions that support charity only. Added 11/6/03.
0 0 Y
ALUM_WARNING Defines when the "alum sensor needs adjustment" warning is sent.
The normal aluminum baseline voltage is 2.50V, by default, if the baseline is above 3.70V or below 1.30V the warning is sent.
Formula for ALUM_WARNING: 128*upper baseline + lower baseline/2. For the example above: 128*370 + 130/2 = 47425 (this is the default value).
For dual or tri RVMs you could probably safely use values of 4.00V and 1.00V, ALUM_WARNING=51250 (128*400 + 100/2).
Previous software versions were hard-coded to send an "alum sensor needs adjustment" warning if the aluminum sensor baseline voltage is above 3.50V or below 1.50V, which corresponds to 1.0V higher or lower than the expected 2.50V baseline. To duplicate this behavior, set ALUM_WARNING=44875 (128*350 + 150/2).
Why use this formula? This method of defining the upper and lower baseline values uses less code space than defining two separate parameters.
Parameter added in RVM version 8/16/13.
47425 0 Y
ALUMTHRESHOLD This many volts (x.01) below baseline (usually 2.5V) = aluminum.  
Normally, the aluminum/steel sensor reads 2.5V when no can is present. When an aluminum can is inserted into the sensor, the sensor voltage decreases by a certain amount. For example, the sensor voltage will read 1.5V when aluminum is inserted. The ALUMTHRESHOLD parameter defines how many volts (x 0.01) the sensor must decrease before the software declares that an aluminum can is present.

So if ALUMTHRESHOLD=60, the sensor must read 1.9V (2.5-0.6) or less before the software will decide that an aluminum can is inserted.

Note: "baseline" means the typical 2.5V when no can is present. The RVM will adjust the baseline reading as the sensor voltage can shift up/down depending on the temperature.

90 0 Y
AUTOPAY_TIME Amount of time (x100 ms) to wait after the customer inserts his last container before autopaying. 
Set to 0 to disable this feature.

Note: only supported in Israeli versions 1/21/02 and later.
0 0 Y
BAIL_ATTEMPTS Max number of times to retry the bail (0 = infinite) 25 0 Y
BAIL_DELAY Time to delay (x 10 ms) after bail reaches limit before returning to center.
If the bail beam is clear after this delay, it is assumed the container dropped out of the bail, so the bail is returned to the center position.  If the bail beam is not clear, a timer as defined by the parameter BAILDROPTIME is started.

Note: if the bail sensor is disabled (BAIL_SENSOR=0)or BAILDROPTIME=0, the bail will return to center immediately after the BAIL_DELAY delay occurs. BAILDROPTIME defaults to 100 (1 sec).
20 0 Y
BAILDROPTIME Time (x10ms) to wait for bail beam to clear after the BAIL_DELAY timer expires. This value should be at least 150 in PET RVMs to prevent 3L PET bottles from being rejected.

If the bail sensor clears before this timer expires, the bail is returned to center and normal operation continues. If the bail beam is still blocked after the BAILDROPTIME timer expires, the container will not be paid for, the bail will remain at the accept limit and the RVM will go temporarily out of service. The display will indicate "temp. out of service" and the machine will vend all money due. Error 401 is sent to the site controller; "BAIL SENSOR FAILED TO CLEAR" will be displayed when the cabinet door is opened. The machine will stay in this state until the bail beam clears, at which point the RVM will perform a reject cycle and return to service.

Note: If the bail beam is not accurately aimed, the beam may remain blocked while the bail is at the left limit, causing the RVM to go out of service for "BAIL SENSOR FAILED TO CLEAR". 
See hardware tech bulletin #23 (Bail Sensor Bracket Installation).  The new Bail Sensor Bracket allows the beam to be more accurately aimed at the Retro Reflector. 

100 0 Y
BAIL_CNTR_TML Additional time (x1ms) to move the bail left after reaching center when starting from the right side.
0=disabled.
Feature added in version 7/15/13 to fix the following problem: if the bail motor becomes worn the bail won't center properly (it stops short) even after adjusting the bail hardware.
0 0 Y
BAIL_CNTR_TMR Additional time (x1ms) to move the bail right after reaching center when starting from the left side.
0=disabled.
Feature added in version 7/15/13 to fix the following problem: if the bail motor becomes worn the bail won't center properly (it stops short) even after adjusting the bail hardware.
0 0 Y
BAIL_FAIL_DLY Time to Delay (x.1 sec.) between bail retry attempts after initial fail.  First four attempts are rapid.   30 0 Y
BAIL_NUDGE_TM Time (x 10 ms) to move bail in opposite direction if it does not move off center.   7 0 Y
BAIL_NUDGEDLY Time (x 1 ms) to delay after a bail nudge before moving bail.   1000 0 Y
BAIL_RETRIES Number of times to retry bail before sending error messages.   9 0 Y
BAIL_SENSOR

Non-zero = Bail sensor installed. 0=other bail parameters are ignored.
Add the following values for the desired features:

1 = bail beam must remain blocked just prior to the bail accepting the container, otherwise the container will be rejected.
2 = bail beam requires only a momentary block before paying (this is the default value)
4 = pay even if bail beam is never blocked. This setting may cause PET bottle jams.
8 = bail beam does not have to clear after accepting.
16 = perform reject cycle after error 401 (Bail sensor failed to clear) instead of leaving bail at left (requires RVM software 9/30/08 or later)
32 = perform bail nudge AFTER returning to center on right side (normally performs nudge from current position) (requires 12/9/08 or later RVM SW)
 64 = perform bail nudge AFTER returning to center on left side, 4 attempts max then switch to reject if unsuccessful (requires 12/9/08 or later RVM SW)

Note: enabling the 64 setting makes cheating much easier if someone reaches up the reject chute and removes the container from the bail.
Note: if the 32 or 64 settings are enabled, the BAIL_NUDGE_TM parameter must be set to no larger than 2 to prevent the nudge from leaving a large enough gap and possibly accepting the container to the left during a reject or rejecting a container to the right while accepting.


You must adjust the bail sensor (aim and gain) at the final installation location. The bail sensor adjustment procedure is in the RVM service and maintenance manual.

2 0 Y
BAILARRIVE_TM Time (x10ms) after container passes entry sensor before it must block the bail sensor, otherwise it will be rejected (130)
Parameter added in RVM version 12/15/09.
130 0 Y
BCSERVERTIME

Specifies the amount of time (x100ms) for WinRVM to respond with barcode when using the "barcode client" architecture.
Note: requires a "barcode client" RVM software version.

30

0

Y

BCTABLESEARCH 0=normal barcode table search order (glass before PET for 3-way RVMs when no PET detected)

1=search PET table before glass table (used in Greece)
When set to 1 this lets Greece place plastic bottles that don't trigger the PET sensor in the PET table as a commodity type of 9 to reject when using an enhanced capacity glass machine that's configured as a glass+PET RVM. See the 6/17/11 software update for more info.
Note: if a glass and PET container have the same barcode in the table, the glass bottle will be rejected as if will match the PET barcode table but no PET was detected on the container.

Note: parameter applies to Greek software version 6/17/11 and later and all software versions 5/14/14 and later.
0 0 Y
BEEPWHENFULL When the machine goes full (by count or sensor) the RVM's internal beeper is turned on for 500ms (1/2 second) every BEEPWHENFULL*100ms. For example, if BEEPWHENFULL=20, the RVM will beep for 1/2 second every 2 seconds. The alarm relay is also turned on with the same timing to allow an external beeper to be attached. The beeper is not turned on for an overflow error when using full-by-count or if FAIL41BINFULL=0 and one bin goes full. Beeping stops when the cabinet or storage door is opened.
The default value of BEEPWHENFULL=0 which is disabled.
Parameter added in RVM version 7/31/09.
Does not apply to XMT versions.
0 0 Y
BIN_TOGGLE

If both bins in the main cabinet are configured to accept identical commodities, the RVM will switch bins every BIN_TOGGLE containers so the bins fill up evenly when using a bin full sensor instead of fill-by-count.
Previous versions of RVM software would fill up the left bin until the bin full sensor was blocked and then go out of service, never putting any bottles into the right bin (only when both bins are configured to accept the same commodity). To get around this problem you had to configure the machine (via the SILOS table) to fill-by-count, then the RVM would fill the left bin then fill the right bin.

Note: sending a silo table to the RVM sets the "current bin" to the left. Updating the RVM software resets the internal glass bin toggle counter to 0.
Parameter added in RVM version 7/29/04.
Note: BIN_TOGGLE only applied to glass in RVM versions prior to 3/11/05

20 0 Y
BINCNTBTNTIME If two cash button presses occur within this time (x 10 ms), show the bin counts.  
If the machine is out of service, the last fail will be displayed.
Parameter removed from RVM versions 7/29/04 and later (value is hard-coded to 19).
19 0 Y
CARD_EXITMSG If non-zero, after a payout (with or without a card scanned, setting of CARD_RECEIPT makes no difference) show lines 593 (top) and 594 (bottom) of messages.tbl on the LCD for this much time (x100 ms), which defaults to:
"VISIT OUR WEB SITE FOR TODAY'S PROMOTIONS"
"shop.envipco.ie"
Valid only in interactive versions of RVM software. Added 10/18/07.
0 0 Y
CARD_NOFULL non-zero=don't go out of service for loyalty card database full.

If CARD_NOFULL=1 and the loyalty card database goes full, a new warning 482: "Loyalty card database full, ignoring" is sent instead of the error 481 "Loyalty card database full" and the RVM will purge it's loyalty card database and continue running. Note: this feature should only be enabled for demo situations where you don't care if loyalty card data doesn't get saved to the interactive PC.
If CARD_NOFULL=0 and the RVM goes out of service for "loyalty card database full", setting CARD_NOFULL=1 from RVM keypad command #9,20 will clear the failure and put the RVM back into service. This lets you bring the RVM back into service if the interactive PC is unable to communicate with the RVM for some reason.
Valid only in interactive versions of RVM software.
Valid only in interactive versions of RVM software. Added 1/8/09.
1 0 Y
CARD_READER non-zero=card reader installed
Valid only in interactive versions of RVM software. Added 10/18/07.
0 0 Y
CARD_RECEIPT 1=print receipt for loyalty card users, 0=no receipt for loyalty card users
Valid only in interactive versions of RVM software. Added 10/17/07.
1 0 Y
CARD_REQUIRED

This parameter only applies to card-reader versions. Values:
1=customer MUST insert card first to accept containers (LCD indicates "insert card")
0=accept containers without customer inserting a card first (customer will not be paid) (LCD indicates "insert card or container")
Added 10/26/04.

0 0 Y
CHAR_TO_CASH if non-zero pay cash when charity button pushed
Valid only in charity versions of RVM software such as in Greece. Added 10/26/04.
0 0 Y
CHARITY_INPUT  defines where the charity switch is mounted:
0=switch mounted in RVM controller (new method)
1=switch in door (old method)
0 0 Y
CHEAT_DELAY Time (x 100 ms) to delay, after a multi-scan or COIL4CHEATDET cheat is detected, before accepting the next container to annoy the cheater. 0 0 Y
CLR_BIN_ANYTM Determines which bin counts are cleared when the clear button is pressed (by cabinet):
0=any bin that is full will be cleared
1=clears all bin counts no matter what.
2=all bins must be full before the counts are cleared
0 0 Y
COIL4CHEATDET

This parameter applies to the can RVM only.
Non-zero enables cheat detection using the can coil. When the bail returns to center after accepting a can into the crusher, if the can coil detects metal, the previous can will NOT be paid for.

If the machine is idle and no cans are being feed into it, but the can coil detects a can, the bail will perform a reject cycle and the machine will delay CHEAT_DELAY seconds before accepting any more cans to annoy the cheater.

This parameter is normally set to 0 as long cans may not be paid for.
Parameter removed in RVM version 11/11/03 because it didn't work for long cans.

0 0 Y
COIN_AUTOPAY non-zero = autopay a coin when amount due reaches value of the largest coin, otherwise use MAXPAY
This fixes a problem when configured for operation in Mexico when the RVM is configured for 20 cent and 1 dollar hoppers. In Mexico the deposit values are 4, 5, 10, 20 cents. If the customer is due 16 cents (less than the smallest coin hopper) and the customer inserts five 20-cent cans, he will be paid 1 dollar (largest coin value) but the 16 cent remainder is cleared. 
Set COIN_AUTOPAY=0 to force the software to not pay any coins until the customer presses the payment button. Only then will any amount due less than the largest coin be cleared.
Parameter added in RVM version 8/23/02.
1 0 N
COIN_HOP_TYPE

Defines the type of coin hoppers installed:
0 = no coin hoppers installed
1 = Standard Change hoppers installed (not typically installed in CF1500s)
2 = Asahi-Seiko hoppers installed

0 0 N
COINRELAYTEST 0 = don’t test for stuck relays on power up
1 = test for stuck power and control relays on power up (requires appropriate coin board)
0 0 Y
CR_REV_TRIES Number of side cabinet crusher stall recovery attempts to make in reverse. 10 0 Y
CR_STALL_ATTS Number of side cabinet crusher stall recovery attempts to make going forward 2 0 Y
CR_STALL_DLY Time (x 10 ms) to delay to prevent "plug reversing" the Shredder/Crusher motor during stall recovery. "Plug reversing" refers to running the motor in one direction and then immediately changing the motor direction without letting the motor slow to a stop first.
Applies to the first SH_STALL_QWIK recoveries only, see SH_STALL_XDLY.
250 0 Y
CR_STALL_REV Time (x 10 ms) to run side cabinet crusher in reverse during stall recovery. 100 0 Y
CR_STALL_TIME Max time (x 1ms) to allow between side cabinet crusher transitions before declaring a stall (0=disable) 400 0 Y
CR_START_TIME Time (x1ms) to allow compactor to get up to speed before taking 1st baseline when using CRUSHTIME_MIN to prevent non-payment of the first can.
Does not apply to XMT software versions.
2000 0 Y
CRUSHDETECTIM Time (x100ms) to wait for can crush after bail accepts when using CRUSHTIME_MIN feature.
Does not apply to XMT software versions.
25 0 Y
CRUSHER_TYPE 1 = Crusher/Compactor
2 = Shredder
0 = Not installed
2 0 Y
CRUSH_POS_DLY

Used to force the cans to consistently fall into the open area of the crusher. CRUSH_POS_DLY defines the delay (x 1ms) once crusher position sensor leaves the end sensor before the bail dumps can into crusher. 

Set to 575 if using 60Hz, 700 if using 50Hz.
Does not apply to XMT software versions.

575 0 Y

CRUSHFAILCNT

Defines how many containers in a row to accept with no can crush detected (CRUSHTIME_MIN feature) before not paying for cans.
The default value of CRUSHFAILCNT is 3 which means the RVM will pay for 3 cans in a row even if no crush is detected.
To make make the software behave the old way (not pay for any can unless a can crush is detected), set CRUSHFAILCNT=0.

Parameter added 11/9/09.
Does not apply to XMT software versions.

3 0 Y
CRUSHTIME_MIN

This parameter is used to prevent cheating in a standalone can crushing machine. The software detects if a can is actually crushed by monitoring the crusher’s RPM sensor during the crush cycle. The software looks for a "long" crush cycle to detect the can crush.

See software updates Vol. 7 No. 5 and Vol. 8 No. 1 for more info.
Details:

When the RVM is ready to accept a container, a timer (CRUSHDETECTIM x100ms) is started as the bail begins to move to the left. A can crush must be detected before this timer expires, otherwise the customer will not be paid. During a can crush cycle, the software records the time between each gear tooth transition (period) of the crusher, as measured by the crusher’s RPM sensor.

The RVM sums the first 12 crusher RPM periods after the crusher leaves the position sensor and compares that to the previous non-can-crush sum (the baseline). If the difference is greater than or equal to the number defined by the CRUSHTIME_MIN parameter, the can will be paid for.

Legitimate can crushes showed a crush time difference of at least 5 ms. 
Set CRUSHTIME_MIN=0 to disable this feature.

Some can crushers move slower in one direction than the other; the software thinks a can is always being crushed in one direction and never being crushed in the other direction.
To fix this problem, the RVM keeps track of individual baseline times for the left-to-right and right-to-left movements of the crusher. 

  • the upper byte is the threshold for the left-to-right crusher movement
  • the lower byte is the threshold for the right-to-left crusher movement

The formula for setting CRUSHTIME_MIN is: 256 * left-to-right threshold + right-to-left threshold.
For example: for a left-to-right threshold of 6 and a right-to-left threshold of 5, set CRUSHTIME_MIN=1541 (256*6 + 5).
Other values:
1285 = 5 on both sides
1028 = 4 on both sides

  771 = 3 on both sides
  514 = 2 on both sides (recommended value)
  257 = 1 on both sides
      0 = disabled

Do not enable this feature unless your RVM version is 4/19/02 or later, as there are bugs in this feature that may prevent paying for containers under certain conditions.

Does not apply to XMT software versions.

0 0 Y
CUSTDOORDELAY Time (x 10 ms) to wait after customer door opens, before locking. 25 0 Y
DEBUG

Non-zero enables anti-cheat debug messages, “cheat codes”:

1 = Coil detected before Can accepted
2 = Coil detected after Can accepted
3 = BAILBLOCKETIME fail
4 = BAILCLEARTIME fail
5 = Multi-scan: Not enough time between scans
6 = Multi-scan: Two different bar codes detected
7 = Multi-scan: Not enough scans
8 = Bail beam not blocked just before accept cycle
9 = Staging PET/sensor blocked after ENTRY_DEBTIME expired
10 = Bail beam blocked after bail returned to center
11 = Bail beam blocked while machine idle
12 = Can not crushed in CRUSHDETECTIM seconds
13 = Multi-scan: last 2 barcode scan times inconsistent (MS_MIN_DIFF fail)

For HDS RVMs:
32 (rear exit sensor blocked before first exit sensor)
33 (exit sensors not blocked simultaneously long enough)
34 (exit sensors blocked simultaneously for too long)
35 (rear exit sensor went clear before front exit sensor)
36 (rear exit sensor blocked unexpectedly after container in bail)

If the can crusher timing anti-cheat feature is enabled (CRUSHTIME_MIN set), then debug can be set to these values (see See software updates Vol. 7 No. 5):

DEBUG=2, a minimal set of can crusher timing data will be displayed in CONSOLE.
DEBUG=3, a complete set of can crusher timing data will be displayed in CONSOLE,
                 and the DROPDETECT counter will be displayed instead of the clock.

In RVM versions 8/3/04 and later, setting DEBUG non-zero now shows the barcode in service mode.

0 0 Y
DEPOSIT0

XX.XX cents to pay for each container value of 0.

The DEPOSIT0-DEPOSIT3 parameters define the number of cents to pay for each container of value N, where N is the value of container (0 to 3) as defined by 'v' in the barcode table: barcode,v,c,t,o.
For example, for the barcode table entry: 1234567890,1,0,0,0
The value of the container is 1, which corresponds the the DEPOSIT1 parameter. You must then look at the setting of DEPOSIT1 to determine the actual amount of money to pay.
For different currencies, the concept is the same. A maximum of 99.99 cents (or units of another currency) can be paid.

0 2 N
DEPOSIT1 XX.XX cents to pay for each container value of 1.   0 2 N
DEPOSIT2 XX.XX cents to pay for each container value of 2.   0 2 N
DEPOSIT3 XX.XX cents to pay for each container value of 3.   0 2 N
DISCARD_START Number of sensor samples to discard at beginning of data stream.   20 0 Y
DISCARD_STRT% Non-zero = interpret DISCARD_START as a percent, otherwise an absolute number.   0 0 Y
DISCARD_END Number of sensor samples to discard at end of data stream.   20 0 Y
DISCARD_END% Non-zero = interpret DISCARD_END as a percent, otherwise an absolute number.   0 0 Y
DISPLAY_COUNT 0 = display amount due.  
1 = display number of containers accepted.   
2 = display nothing. *
0 0 Y
DISPLAY_TIME Defines how long to display certain customer LCD messages on the screen such as "Unable to read barcode" before returning to the "Insert container" message.
Parameter removed from versions 11/19/18 and later (now hard-coded to 60).
60 0 Y
DIV_ATTEMPTS Number of times to retry diverter before sending an error message. 3 0 Y
DIV_DELAY Do not move diverter again for this much time (x 100 ms.).
This allows time for shredded PET to fall into the bin before moving the diverter to avoid contamination.
40 0 Y
DIV_TIMEOUT Diverter time-out (x 10 ms.)
Parameter removed from versions 11/19/18 and later (now hard-coded to 200).
200 0 Y
DROPDETECT If non-zero and bin full sensors not briefly blocked after this many containers in a row (the RVM will not actually go out of service until one additional container is inserted), go temporarily out of service for a length of time specified by DROPDETECTDLY.
Parameter added in RVM version 8/5/05 (click for more info).

Parameter removed from HDS versions 5/23/12 and later.
0 0 Y
DROPDETECTDLY Go temporarily out of service for this long (x100ms) for a DROPDETECT or CRUSHFAILCNT fail.
0=stay out of service indefinitely. (3000 = 5 minutes)
Parameter added in RVM version 8/5/05 (click for more info).
0 0 Y
DROPDETECTBIN  Defines which bins to use for the DROPDETECT feature: 1=main cabinet, 2=side cabinet, 3=both (3)
Parameter added in RVM version 10/13/05.
2 0 Y
DROPDETECTOPT Defines various DROPDETECT options, based on the bit values (add [n] numbers is red):
  BIT 0: 0=key press clears failure, 1=door close clears failure   [1]
  BIT1: 0=don't print barcode on cheater's receipt (
only works with Cybertech text and graphics printers), instead print line of text defined by line 580 of messages.tbl
          1=always print barcode (voucher template defines barcode as before).   [2]

To determine the value of DROPDETECTOPT, add the [n] values above in red. Here are the 4 possible values of DROPDETECTOPT:
0  key press required, don't print barcode on cheater's receipt
1  key press not required, don't print barcode on cheater's receipt
2  key press required, print barcode on cheater's receipt (every receipt)
3  key press not required, print barcode on cheater's receipt (every receipt)

Parameter added in RVM version 3/22/06.

0 0 Y
EAN13TRUNCATE

This parameter applies to non-EAN versions of software only. This allows 13 digit EAN barcodes to be accepted into regular RVM software that only holds 10 digit UPC barcodes.

If non-zero, the first two digits and the very last digit of any EAN-13 barcode received are discarded so that a barcode table match is possible.

For example, to place the EAN 1234567890123 into the barcode table, discard the first two digits "12" and last digit "3" and simply place 3456789012 into the barcode table.

Note: RVM software prior to 10/4/01 had a different algorithm: the first three digits of any EAN-13 barcode received were discarded.

0 0 Y
ENTRY_DEBTIME

Time (x 1ms) to debounce the container past the customer door/staging sensor (can)/intensity sensor (COLOR_SENSOR). When this debounce timer expires, the machine stops taking sensor data to identify the container, the customer doors are locked and the feed wheels stop turning (if not a can staging machine). This parameter is needed for cases where bottles are inserted neck-first and tilted.

Normal values: can: 20, glass: 100, PET: 450

100 1 Y
ERRLOGPRNLIMT Limits the RVM error log printout (keypad command #4,05) to this many errors (shows the last ERRLOGPRNLIMT errors).

Valid in Greek versions of software only. Added 3/6/07.

10 0 Y
FAIL41BINFULL 0 = the machine will not go out of service until ALL bins are full.
non-zero = the machine will go out of service as soon as one bin goes full.
Note: for an with a side cabinet, if the glass bin full sensor is blocked the machine will continue to accept can/PET and when a glass bottle is inserted, the LCD will indicate “sorry, glass bin is full”.
However, if you open and close the cabinet door and the side cabinet bin full sensor is blocked, the machine will remain out of service for “side cabinet full”. You could shake the glass bin to clear the sensor to get the RVM back into service (or empty the glass bin!).
0 0 Y
FEED_SWITCH

Parameter used by glass & PET machines only.
1= feed switch installed (obsolete hardware configuration)
2=customer door installed
0=neither installed (for testing purposes only)

This parameter should always be set to 2.

2 0 Y
FEED_TIME Turn feed wheels OFF if no container is inserted after this much time (x 100 ms) 20 0 Y
GLASS_POINTS Defines how many points to pay glass bottle.
Note: Japanese versions only use xx.xx format (example: 100 = 1.00 points).
For card reader versions of RVM software only.
0 0 Y
LEFT_HOPPER Left coin hopper value cents. Will auto-pay when largest coin value reached. Also see RIGHT_HOPPER. 0 0 N
LIFECYCLEMAX

Defines how many cycles perform in the life cycle test, diagnostic 90. The default value is 0 (infinite).
You can change LIFECYCLEMAX from the keypad via #9,20, assuming SC_ATTACHED is not set to 1.
When the max count is reached, the display will indicate the number of cycles completed.
If diagnostic 90 is repeated it will run LIFECYCLEMAX cycles again. 
Parameter added in RVM version 6/23/06.

0 0 Y

MANYSCAN_MAX

 If non-zero go out of service if the same barcode is scanned this many times in a row (default value: 0). It doesn't matter if the customer presses the payment button between running the same container.
When the cabinet door is opened or the cash button is double-clicked, "PLEASE CONTACT STORE MANAGER" is displayed. The message is intentionally vague so as to not alert a cheater to the actual reason the machine is out of service.
 Note: this message can be changed via the following lines of messages.tbl:
;MANYSCAN failure message when MANYSCAN_FAIL=1
634: PLEASE CONTACT STORE MANAGER, PRESS KEY
;MANYSCAN failure message when MANYSCAN_FAIL=2
635: PLEASE CONTACT STORE MANAGER
Parameter added in standard US RVM version 1/6/15.

0 0 Y

MANYSCAN_FAIL

if out of service for a MANYSCAN_MAX failure, define how the RVM is allowed to return to service:
1=require key press to clear fail, 2=cabinet door open & close clears fail
Parameter added in standard US RVM version 1/6/15.

0 0 Y
MAX_CANCOUNTS

Defines the maximum allowable number of can counts detected by the aluminum/steel sensor. This parameter can be used to detect two cans run end-to-end with no gap between them. The following tables lists the average aluminum counts per can:

Size (oz)

Aluminum counts

8

91

12

113

16

156

25

191

Two 8

193

two 12

244

Setting MAX_CANCOUNTS to 210 should be a good compromise between rejecting two 12oz cans and accepting a single 25oz can.

Note: sticky cans, roller, or glide plate under the feed wheels will slow the can down as it passes the aluminum sensor, causing higher than normal aluminum counts.

500 0 Y
MAXCLIENTUPCS

Specifies the number of barcodes for the RVM to cache when using the "barcode client" architecture.
This should be used for testing purposes only.
Valid values: 1-500 (100 is recommended). If you attempt to set it higher than 500 the RVM will force it to 500.

Note: requires a "barcode client" RVM software version.

500

0

Y

MAX_INVALID

This parameter is used to detect two cans run end-to-end by detecting the gap between the cans. Note that due to the way the aluminum sensor works, the software can’t detect a gap smaller than approximately two inches. This parameter defines the maximum allowable amount of time (in ms) between two cans before rejecting. Testing indicates a value of 10 works well. Note: if this parameter is set too small, such as 1, legitimate single cans may be rejected due to the way the aluminum sensor works.

This parameter is enabled by default (set to 10). Set MAX_INVALID=0 to disable.

10 0 Y
MAX_REBOOTS

Defines how many reboot attempts to make (default value is 5) when the RVM reboots itself for certain errors flagged as "R" in column 9 of the ERRLIST file.

Set  MAX_REBOOTS=0 to disable the reboot feature.
The reboot counter is not per unique error, but a global counter. For example, if MAX_REBOOTS=5 and the printer doesn't respond twice in a row (rebooting after each error), then the printer responds but then the print head is determined to be lifted 3 times in a row (rebooting after each error), the RVM will give up rebooting because 5 total reboots occurred.
The reboot counter is reset when the cabinet door is opened and after accepting a container.
Another example: if the printer doesn't respond after every other customer, the RVM will reboot itself once after each error, but continue working indefinitely because after the RVM accepts a container it clears the reboot counter.

Note: requires Greek RVM software version 10/5/07 or later.

5 0 Y
MAX_SCAN_TIME Max time (x10ms) to scan for barcodes.   120 0 Y
MAXPAY

Maximum amount of money to accumulate before auto paying the customer. 
Format: $XX.XX, example: 0500 = $5.00
0 = No auto-pay (value of 0 not recommended because RVM will rollover from $99.99 to $10.00, use 9900 max for $99.00)

700 1 Y
MESSAGE_PORT

Feature used only in certain interactive or "VFW" versions of RVM software.
0 = don't send any "interactive mode" com
mands out the RVM's AUX or LAN port.
1 = send various barcode/voucher/LCD commands out the RVM's LAN port. This is required when using WinRVM in "interactive mode".
The WinRVM and the RVM should be configured for 38.4K baud to minimize transmission delays.
2 = send various barcode and voucher commands out the RVM's AUX port (for VFW compatibility).

2 0 Y
MIN_CANCOUNTS Defines the minimum number of aluminumcan counts required for acceptance.
A typical 12oz can will have around 110 counts.
This settings is used to prevent containers cut in half from being accepted.
Note: in software versions prior to 4/18/11 this parameter also applied to steel counts.
40 0 Y
MIN_STEELCNTS Defines the minimum number of steel can counts required for acceptance.
A typical 12oz can will have around 110 counts.
This settings is used to prevent containers cut in half from being accepted.
Parameter added in RVM version 4/18/11.
40 0 Y
MS_MIN_DIFF 

If non-zero, reject the container if the scan times of the last two barcodes are different by this much time (x10ms).  In other words, the last two barcode scan times must be consistent. MULTI_SCAN must be set to 4 to enable the MS_MIN_DIFF feature because the time difference between the first two scans is inconsistent due to the unknown starting position of the barcode.
For example, if MS_MIN_DIFF=6, the time it takes to scan the 3rd barcode must be within 60ms of the time it takes to read the 4th barcode, or the container will be rejected.
If DEBUG>0 and the RVM is in service mode and the  MS_MIN_DIFF feature detects a cheater, a new cheat code 13 will be displayed (see DEBUGin parameter table for list of all the cheat codes).
If DEBUG=2, the scan times of the last two barcodes are transmitted out the serial port in "MS:x,y" format (use CONSOLE program or WinRVM's console mode to view this data). This feature is for debugging purposes only and should not be left enabled in the field.
Parameter removed in RVM version 5/15/14.

6 0 Y
MS_MIN_SCANS Minimum number of times the barcode must be read as part of a multi-scan.
Parameter removed in RVM version 10/1/03.
2 0 Y
MS_MIN_TIME Minimum time (x 10 ms) allowed between consecutive barcode scans for multi-scan.  
RVM versions 10/1/03 and later: no longer time between the first two barcode scans in case the container is inserted such that the barcode is scanned just as the barcode is leaving the scanner's field of view, thus shortening the scan-to-scan time of the first two barcode reads.
Parameter removed in RVM version 5/15/14.
47 0 Y
MS_SCAN_DLY Time (x 1 ms) to delay, after a multi-scan barcode is detected, before scanning for the next bar code. 
Set to 200 so that 3L PET bottles will not be rejected.
Parameter removed in RVM version 5/15/14.
150 0 Y
MULTI_SCAN

"Multi-scan" is an anti-fraud feature. The MULTI_SCAN parameter must be set to non-zero to enable this feature.: this parameter also defines minimum number of times the barcode must be read. 

When multi-scan is enabled, the MAX_SCAN_TIME parameter now defines the maximum amount of time to read the barcode MULTI_SCAN (typically 4)  times.
For can RVMs, set MAX_SCAN_TIME=340 (3.4 sec) to allow 25oz Fosters type cans.  Set MS_MIN_TIME=47.
For PET RVMs (or combi RVMs that accept PET), set MAX_SCAN_TIME=450 (4.5 sec) to allow 3L bottles. Set MS_MIN_TIME=55.
For glass RVMs, set MAX_SCAN_TIME=340 (3.4 sec) to allow large bottles. Set MS_MIN_TIME=52.
This means that a different option file must be used to enable each RVM type.

If the barcode is read less than the number of times defined by MULTI_SCAN, the container will be rejected. Once the scanner has read the barcode MULTI_SCAN times, the multi-scan feature is immediately terminated. 
In previous software versions the multi-scan feature scanned for a fixed amount of time and required the barcode to be read MS_MIN_SCANSnumber of times.

The following checks are then made:

  1. The time between reading the barcode on successive scans must not be too quick. The parameter MS_MIN_TIME defines the minimum allowable time x10ms (typically 470ms). The MS_SCAN_DLY parameter defines how long (x 1ms, typically 150ms) to wait after scanning a barcode before scanning again).
  2. Only one unique barcode must be read. This prevents cheaters from inserting a bottle and then using a barcode on a stick (assuming the barcode on the stick is different).
  3. If any of the above checks fail, the software will delay to annoy the cheater before displaying "non-participating". The delay time is defined by the CHEAT_DLY parameter (x100ms, set to 0 to disable this feature). 

Note: the multi-scan feature should be enabled only in locations where cheating is suspected. There are several disadvantages to using multi-scan:

  1. Bottles that do not spin well for whatever reason (deformed PET bottles, gooey spinner, ribs on rollers) will not be accepted (checks #1 or #2 from above will fail).
  2. Sometimes the laser scanner decodes a barcode incorrectly, this will cause check #3 from above to fail.
  3. The multi-scan routine always takes a fixed amount of time to complete (typically 1.1 seconds; depends on MAX_SCAN_TIME parameter), which is slower than when running in the normal mode which accepts the bottle as soon as the barcode is detected.
  4. Multi-scan many not work well if the scanner has a wobbler installed.

Note: due to the slow rotational speed of large PET bottles, the parameters may need to be tweaked for PET RVMs. For example, the MS_MIN_SCANS may need to be reduced, or MAX_SCAN_TIME may need to be increased, MS_MIN_SCANS and MS_SCAN_DLY may need to be tweaked as well.  The laser scanner's beeper should be disabled for even more effective cheat prevention.

Note: temporarily enable the DEBUG parameter to force the RVM to display a "cheat code" when a container is rejected. See question 49 for a description of the cheat codes.
Do not enable multi-scan and supplemental barcode detection at the same time in versions of RVM software prior to 9/24/03! Otherwise the RVM will basically ignore the supplemental barcode requirement and accept cans without the proper supplemental barcode. Additionally, another bug exists that results in corrupted RVM memory identical to the
WILDCARDSTART bug.
Do not enable multi-scan in versions of RVM software prior to 1/19/04 as a bug exists (see software update Vol. 12 No. 1).

See the RESCAN_TIME parameter for another method to deter cheating, which can be used with multi-scan if desired.
Parameter removed in RVM version 5/15/14.

0 0 Y
NO_SCAN_TYPES

Do not scan for a barcode for these container types (use material sensors only)
add the following container values (0 = Normal mode, scan all container types for bar code):

1 (alum)
2 (steel)
4 (green PET)
8 (clear PET)
16 (clear glass)
32 (green glass)
64 (amber glass)
128 (vinyl)

common values:
2 = accept everything except steel cans
124 = accept alum&steel cans only
126 = accept alum cans only
15 = accept glass only
114 = accept PET & alum only
115 = accept PET only
255 = accept NOTHING

0 0 Y
OVERFLOWSENSR

The OVERFLOWSENSR parameter defines the number of containers to keep accepting once the main-cabinet bin full sensor indicates a full condition. If the bin full sensor clears before a OVERFLOWSENSR number of additional containers is accepted the count is reset. An additional OVERFLOWSENSR number of containers will be accepted.

If using "full-by-count" ('full volume' in silos table is non-zero) and the main cabinet’s bin full sensor is blocked for OVERFLOWSENSR number of containers prior to going full-by-count, a "overflow sensor blocked" failure will occur. If OVERFLOWSENSR =0, the RVM will ignore the full sensor and simply go out of service after accepting a specific number of containers as defined in the silos table.

If not using "full-by-count", a "bin full" error will occur after accepting OVERFLOWSENSR number of containers in a row while the main cabinet full sensor is blocked. OVERFLOWSENSR must be non-zero if not using "full-by-count", otherwise the RVM will never detect a full condition.

Typically we configure the RVM to use "full-by-count". Normally, the hardware bin full sensor will not be blocked. However, if a problem occurs (like the user forgets to empty the bin after the RVM goes full), the hardware bin full sensor is a safety measure to prevent jamming.

6 0 Y
PARALLEL_PORT 0=send printer data out regular RS-232 printer port
non-zero=send printer data out parallel port this many bytes at a time (requires graphics printer, see PRINTER_TYPE)
Note: RVM versions 10/15/01 and later support this parameter for use with the cash voucher.
0 0 Y
PET_POINTS Defines how many points to pay per PET bottle.
Note: Japanese versions only use xx.xx format (example: 100 = 1.00 points).
For card reader versions of RVM software only.
0 0 Y
PET_VALUE if non-zero pay DEPOSITn-1 for PET bottles, ignoring value in barcode table. Max value=4 = DEPOSIT3
For RVM versions that support charity only. Added 10/7/10.
0 0 Y
PIN_STALL_CLR 1=Envipco PIN required to clear crusher stalls
0=cabinet door closing clears crushers stalls
Added in RVM version 5/17/13.
1 0 Y
POS_SYSTEM ;non-zero=enable Point Of Sale system support. The default value is 1 (enabled) in POS software versions.
If set to 0, this software will function like regular RVM software (without coin hopper support).
This parameter is not present in regular RVM software. See the POS release note for details.
Note: requires special RVM software version that supports POS.
1 0 Y
PRINT_HEADER 0 = don't print headers/footers (counters ticket) for cash/charity vouchers

Add the following values to enable multiple features:
1 = print header for cash voucher
2 = print footer for cash voucher,
4 = print header for charity voucher
8 = print footer for charity voucher

This feature lets you create longer cash/charity vouchers than normal by first printing the contents of the counters ticket before and/or after the cash/charity voucher.
Note: only applies to Greek Cybertech printer versions 5/14/10.

0 0 Y
PRINTER_TYPE 0 = No printer installed
2 = Cybertech text printer
3 = Cybertech 9250 graphic printer
4 = Hecon C56 printer (requires special printer-only RVM software version released 09/09/05 or later)
5 = Swecoin TTP 2010 printer (requires special printer-only RVM software version released 03/21/07 or later)
6 = Hecon X56 printer with cutter (requires special printer-only RVM software version released 04/25/08 or later)
Note: you must ensure the format of the printer vouchers/coupons loaded into the RVM match the printer type.
2 0 Y
PRINTTIMEOUT Time (x100ms) to wait for response from printer.
Parameter added in RVM version 11/16/11. Previous software versions used a hard-coded value of 150=15 seconds.
200 0 Y
PRIZE_AT_END 0=immediately print prize coupon (see PRIZE_ODDS) when due
1=wait for pay button press before vending prize coupon then showing the coupon selection screen.
0 is the default.
See here for more info on coupons.

Added in 6/12/13 RVM versions that support coupons.

0 0 Y
PRIZE_ODDS Set the "special coupon number" in the coupon list file to 9999 to indicate the "prize" coupon. This coupon will only be vended when the total number of containers entered is divisible by PRIZE_ODDS (for example, 5000). You can limit the total number of prize coupons by setting the max count field in the coupon list file. Added a new entry in the counters table to indicate the current prize counter so that it is not reset when the RVM software is updated.
Prize coupons will not be printed from diagnostics. Note: diagnostic 45 (coupon print) will print nothing when the
next coupon is a prize voucher, enter 45 again to print the next coupon.
Once the maximum number of prize vouchers has vended, you can enable prize vouchers once again by resending a CLS file to the RVM or by using RVM keypad command #9,12 and pressing 0.
See here for more info on coupons.
Note: requires Greek RVM softw
are versions 3/15/07 or later or an interactive barcode client version.
0 0 Y
REJECT_TYPES

Indicates which types to reject. Note that the silos table defines what containers to accept. Each container type is assigned a value, add the following values:

1 = aluminum
2 = steel
4 = green PET
8 = clear PET
16 = clear glass
32 = green glass
64 = amber glass
128 = vinyl  

examples:2 = accept everything except steel cans.
124 = accept aluminum and steel cans only.
126 = accept aluminum cans only.
15 = accept glass only.
114 = accept PET and aluminum  only.
115 = accept PET only.
255 = accept NOTHING.

Note: eliminated in RVM versions 4/19/20 and later as this parameter was redundant; the bin configuration file determines what commodities to accept.

0 1 Y
REJ_SENSOR If non-zero, a reject sensor is installed and defines how long (x10 ms) sensor must be clear before rejecting. 0 0 Y
RESCAN_COMP 0 = don't pay if any barcode is rescanned
1 = pay if the rescanned barcode is different than the original barcode (this is the default value and is how all previous software versions functioned)
This parameter was added in RVM version 9/10/03.
1 0 Y
RESCAN_FAIL If non-zero, the RVM will go out of service for error 458 "laser rescan found barcode" if the rescan feature detects a cheater. Detecting a cheater means scanning the same barcode after the bail has returned to center after accepting a container.
Note: this only applies when the rescan feature (RESCAN_TIME parameter) is enabled.
Values:
1=require keypress to clear fail
2=door close clears fail
Parameter added in RVM version 11/22/01.
0 0 Y
RESCAN_TIME

The RESCAN_TIME parameter is used to prevent cheating. If RESCAN_TIME>0 (typically set to 60 = 0.6 sec), the scanner will perform a second scan after the accept cycle to make sure a barcode is not detected in the bail area, otherwise the previous container will not be paid for. The RESCAN_TIME value defines the time (x 10ms) to rescan for the barcode. If the rescanned barcode is different than the barcode on the accepted container the RVM will pay for the container because it is assumed the scanner read a "phantom" barcode.
If the rescan feature is enabled, the ACCEPT_DELAY parameter may not need to be enabled because RESCAN_TIME will provide a delay.
Also see the RESCAN_FAIL parameter.

Notes:
It is possible for the scanner to read a barcode at the very end of the time allowed by RESCAN_TIME and yet the RVM will stay pay for the container. This is normal, as it takes a while for the barcode to be transmitted to the RVM at 1200 baud.

Software versions prior to 9/29/00 did not rotate the rollers during the rescan process, which may not detect a barcode taped to the rollers.

Versions between 4/29/99 - 9/29/00 should not be used with rescan if configured as a can crushing machine and the can-crush anti-cheat feature is enabled.

Versions prior to 10/10/00 did NOT rotate the rollers during the rescan process; a barcode taped to the rollers may not be detected.

Versions prior to 11/19/01 contain a rescan bug if the EAN13TRUNCATE parameter is enabled to accept EAN13 barcodes. 

Versions from 1/99/99-4/14/03 contain a rescan bug if the BAIL_SENSOR parameter is set to 2.

See the MULTI_SCAN parameter for another method to deter cheating, which can be used with rescan if desired.

0 0 Y
REV_ENTRYBEAM This parameter defines the sense of the hardware entry beam.
Always set REV_ENTRYBEAM=1 for can RVMs.
Always set REV_ENTRYBEAM=0 for glass and PET RVMs.
0 0 Y
RIGHT_HOPPER Right coin hopper value in cents.  Will auto-pay when largest coin value reached. Also see LEFT_HOPPER. 0 0 N
RUN_TIME Time to keep the Shredder/Crusher on after the last container (x .1 sec.).
For XMT RVMs, make sure RUN_TIME >= CONVEYREVTM2 +30, otherwise the RVM will not detect "conveyor beam blocked" failures.
600 0 Y
ROLLER_DELAY Delay (x10ms) before turning on rollers to allow time for a barcode on a rectangular bottle to be scanned. 
0 = no delay (default; software behaves as before, which causes the bottle to rotate 90 degrees once, prior to the barcode being scanned, assuming the barcode is inserted facing upwards). 
The ROLLER_DELAY timer starts when the scanner is turned on. This lets the customer hold the customer doors open for a bit before inserting their rectangular bottle. A value of 15 is recommended if rectangular bottles are to be scanned.
Parameter added in RVM version 10/15/01.
0 0 Y
ROLLER_DIR

Added ROLLER_DIR parameter to specify the direction in which to turn the rollers while scanning for a barcode, accepting container, rejecting container.
You can also define if the rollers should not be turned on during any of these three events.
Previously the rollers always ran CW while scanning, CCW while accepting, CW while rejecting.

ROLLER_DIR    Direction to turns rollers during scan/accept/reject:
[1] = on during scan (0=off)
[2] = CCW during scan (0=CW)

[4] = on during accept (0=off)
[8] = CCW during accept (0=CW)

[16]= on during reject (0=off)
[32]= CCW during reject (0=CW)

Add values in brackets [] for desired configuration.
The default value is 29 to duplicate previous machine behavior = CW during scan [1] + CCW during accept [4+8] + [16] CW during reject

Alternate geeky description in terms of bits:
bit 0 = on/off during scan (0=off, 1=on), bit 1 =direction during scan (0=CW, 1=CCW)
bit 2 = on/off during accept (0=off, 1=on), bit 3 =direction during accept (0=CW, 1=CCW)
bit 4 = on/off during reject (0=off, 1=on), bit 5 =direction during reject (0=CW, 1=CCW)

Parameter added in RVM version 8/10/10.

29 0 Y
SCANNER_TYPE Specifies the type of scanner installed:
    2 = Envipco U2 / Metrologic MS720 scanner (this is the default value)
    3 = Metrologic IS220 scanner (requires RVM software 10/23/08 or later) or
ZEBEX A-50M scanner (Zebex support added on 6/12/13 to HDS and Flex versions)

Note: don't set SCANNER_TYPE =0 to disable the scanner, set USE_LASER=0 instead.

The IS220 scanner requires MAX_SCAN_TIME to be increased to something like 300 = 3 sec. If MAX_SCAN_TIME is kept at the default value of 120, the IS220 will only scan for 1.2sec even if USE_LASER is > 1.
You can send option file IS220.opt to the RVM to enable the IS220 which sets:
    SCANNER_TYPE=3 ;scanner type: 2 = Envipco U2 / Metrologic MS720, 3 = Metrologic IS220
    MAX_SCAN_TIME=330 ;Max time (x10ms) to scan for a barcode

Note: when exiting diagnostic 12 or 13, the IS220 laser will be left on for 1 minute.
When scanning a supplemental barcode is diagnostic 13 the 2-digit supplemental is indicated after the regular barcode, with a space between them such as "496340 01".

Parameter added in RVM version 10/17/08.

2 0 Y
SC_ATTACHED 0=Site Controller not connected which allows: serial number can be set from keypad, allows edit in #9,20 and 21.
1=SC connected, which sends certain communications commands to SC such as PIN entry/exit, customer start/stop, door open, initializing, etc. The RVM parameters can not be changed from the RVM keypad via #9,20 as this changes the RVM's memory which the SC will detect as a "CRC error" and reload the RVM with tables.
2=WinRVM computer connected. This is the same as being set to 1 except RVM parameters can be changed from the RVM keypad via #9,20 as WinRVM software doesn't keep track of RVM CRC errors.
Parameter value 2 was added in RVM version 9/9/05.
0 0 Y
SC_GLS_CRUSH non-zero=side cabinet glass crusher installed 0 0 Y
SCROLL_TIME Time (x 10 ms) between scrolling characters.(0 = disable scrolling)
Scrolling messages are only displayed on line 2 of the LCD. The contents of the message is saved in table 16 (scroll.tbl).
The text will be scrolled whenever there is no money owed, the door is closed, the machine is in service (but not in service mode), and the clock display feature is not enabled. The scrolling message is limited to 500 characters. It is advisable to put approximately 45 spaces at the end of the message to give a pause. Note: a VFD (not an LCD) must be installed to support scrolling.
0 0 Y
SETTLE_TIME Time delay (x 10 ms) for container to settle in bail prior to rejecting.  Helps prevent bail jams.   50 0 Y
SHOW_BARCODE Set SHOW_BARCODE>0 to briefly display the customer's barcode on line two of the LCD.
This feature was added for demonstration/debugging purposes.
Parameter removed from RVM versions 7/29/04 and later (setting DEBUG non-zero now shows the barcode in service mode).
0 0 Y
SHOW_CLOCK 0=no clock display.  
1=12-hr format:
AM is indicated by a leading “0” as in 08:00.”  “8:00” indicates PM.
2=24-hr military format (new option 10/15/01)
1 0 Y
SH_REV_TRIES Number of Shredder stall recovery attempts to make in reverse.
Does not apply to XMT software versions.
10 0 Y
SH_STALL_ATTS Number of Shredder stall recovery attempts to make going forward. 2 0 Y
SH_STALL_DLY Time (x 10 ms) to delay to prevent plug reversing the Shredder/Crusher motor during stall recovery.  Applies to the first SH_STALL_QWIK recoveries only, see SH_STALL_XDLY. 150 0 Y
SH_STALL_QWIK Number of Shredder stall recovery attempts to use the SH_STALL_DLY parameter subsequent attempts use the SH_STALL_XDLY parameter.
Parameter removed in RVM versions 12/21/05 and later.
5 0 Y
SH_STALL_REV Time (x 10 ms) to run Shredder in reverse during stall recovery. 50 0 Y
SH_STALL_TIME

Defines the maximum amount of time (x 1ms) that may pass without seeing either:

  • glass/pet: a crusher/shredder motor gear tooth transition

  • can: either crusher position sensor from seeing a transition

When the motor is first started, a small delay (1 second) is given for the motor to get up to speed.

If SH_STALL_TIME=0, stalls will not be detected.

If a stall is detected, the motor is turned off and after a small delay (SH_STALL_DLY parameter ), the motor will be run in the reverse direction for a short time (SH_STALL_REV parameter). If the motor fails to move in the reverse direction, the software will attempt to move the motor in reverse again (up to SH_REV_TRIES times). If the motor doesn't stall in reverse, the motor will be run in the forward direction. If the motor doesn't stall going forward, then the machine will continue to operate normally. If the motor stalls going forward, the next stall recovery attempt will be in reverse.

The following applies to glass crushers only: when the maximum number of stall recoveries in the forward direction has been exhausted (SH_STALL_ATTS parameter), instead of going out of service, the crusher is reversed for an extended period (SH_STALL_XREV parameter) to drop the object into the bin. The crusher will then make one last attempt at moving forward.

The crusher attempts several "quick" stall recoveries (as defined by the SH_STALL_QWIK parameter). If the crusher is still unable to move, subsequent delays between stall recovery attempts will be longer (as defined by the SH_STALL_XDLY parameter). Note: these parameters removed in RVM versions 12/21/05 and later.

The total number of stall recovery attempts to make in the forward direction is defined by the SH_STALL_ATTS parameter, the total number of stall recovery attempts to make in the reverse direction is defined by the SH_REV_TRIES parameter.

The customer is instantly paid when a stall is detected so he/she doesn’t have to wait for the stall recovery to finish (which may now take a while, depending on how the parameters are set up).

If the shredder/crusher fails to start, the customer’s container is immediately returned back to the customer.

"Temp. Out of service" is displayed during the stall recovery.

The customer door is locked during a stall recovery to prevent stuffing.

300 0 Y
SH_STALL_TOGL

This parameter will hopefully prevent cans with frozen liquid from permanently stalling the can crusher.
  1 = toggle crusher motor direction after each stall recovery attempt
  0 = run crusher in reverse only until not stalled (how previous software versions worked)

This feature applies applies to can, glass, and PET RVMs. The default value for this parameter is 1.
Parameter added in RVM version 12/21/05.

1 0 Y
SH_STALL_XDLY Use this value instead of SH_STALL_DLY after SH_STALL_QWIK recovery attempts.
Parameter removed in RVM versions 12/21/05 and later.
6000 0 Y
SH_STALL_XREV Extended time (x 10 ms) to run Crusher in reverse after stall recovery or to dump bottle (used by glass machine only). 100 0 Y
SIDE_ACPT_DLY Specifies the time (x 100ms) after accepting a container to the side cabinet before accepting the next one. This is used to slow the acceptance rate to prevent bottle jams. 0 0 Y
SIDE_CABINET

This parameter determines whether a side-cabinet is installed. A side cabinet can be used as a storage bin for rejected containers, or it can be used as a glass "soft drop" (no crush) bin, or a glass crusher and diverter can be installed in the side cabinet to crush glass and perform a 2-way separation.

Valid values:

0 = side cabinet not installed
1=side cabinet installed, use the reject chute sensor as the bin full sensor (must disable REJ_SENSOR)
2=use the BSU (Norwegian Bottle Standing Unit) error signal instead of the reject chute sensor as the side cabinet full indication.
3=BSU installed, use the BSU error signal instead of the reject chute sensor as the side cabinet full indication.
4=only accept softdrop glass to side cabinet, use BSU error = full sensor
value 4 added in RVM version 11/11/03, then removed from version 07/29/04

0 0 Y
SIDE_OVERFLOW

The SIDE_OVERFLOW parameter defines the number of containers to keep accepting once the side-cabinet bin full sensor indicates a full condition. If the bin full sensor clears before a SIDE_OVERFLOW number of additional containers is accepted the count is reset. An additional SIDE_OVERFLOW number of containers will be accepted.

If using "full-by-count" ('full volume' in silos table is non-zero) and the side cabinet’s bin full sensor is blocked for SIDE_OVERFLOW number of containers prior to going full-by-count, a "side cabinet overflow sensor blocked" failure will occur. If SIDE_OVERFLOW=0, the RVM will ignore the full sensor and simply go out of service after accepting a specific number of containers as defined in the silos table.

If not using "full-by-count", a "side cabinet full" error will occur after accepting SIDE_OVERFLOW number of containers in a row while the side cabinet full sensor is blocked. SIDE_OVERFLOW must be non-zero if not using "full-by-count", otherwise the RVM will never detect a side cabinet full condition.

This error can only be cleared by unblocking the sensor and then opening and closing the main cabinet door. This clearing method was chosen for safety, as the software has no way of knowing if the side cabinet’s door is open or closed.

Typically we configure the RVM to use "full-by-count". Normally, the hardware bin full sensor will not be blocked. However, if a problem occurs (like the user forgets to empty the bin after the RVM goes full), the hardware bin full sensor is a safety measure to prevent jamming.

2 0 Y
SOFTDROP_MAIN

Allows you to configure a standalone glass RVM to accept or reject softdrop bottles depending on the value of SOFTDROP_MAIN :

0 = RVM accepts softdrop bottles only
1 = RVM accepts non-softdrop bottles only
2 = RVM accepts both softdrop and non-softdrop bottles (this is the default value)

Softdrop and non-softdrop RVMs can now be loaded with the same barcode table. Each barcode's option byte determines if the bottle is softdrop or not (set bit 3 of the option byte for softdrop bottles, which corresponds to a value of 8).

Note: for glass RVMs with a softdrop side cabinet, the SIDE_CABINET parameter must be set to 4 as before as described at http://www.envipcotech.com/software/documentation/software_updates/Vol_11_No_05__CF1500_RVM_11-19-03.htm
When SIDE_CABINET=4, the SOFTDROP_MAIN parameter is ignored (softdrop bottles will be placed into the side cabinet, non-softdrop into the main cabinet).

Parameter added in RVM version 7/22/04.

2 0 Y
STAGE/PETSNSR

The meaning of the parameter depends on the RVM type:

  • Can: Staging sensor installed? (non-zero =YES). If set to 0, cans will be feed in one at a time.
  • PET: defines the minimum number of PET sensor counts required before accepting. Normally set to 20.
  • Glass: defines number of PET sensor counts it will tolerate before rejecting. This is for the case of a glass machine that has a PET sensor installed so that it can reject PET bottles.

    Note: set STAGE/PETSNSR=0 if using the color sensor's PET sensor.

There is always a staging/PET sensor installed in a can or PET machine. If the sensor fails, it can be temporarily disabled until it is replaced.

20 1 Y
STALL_DELAY Time (x 10 ms) to delay after a stall recovery to ensure Shredder/ Crusher is up to speed.
Set to 300 for side-cabinet PET shredder installations.
50 0 Y
STEEL_POINTS Defines how many points to pay per steel can.
Note: Japanese versions only use xx.xx format (example: 100 = 1.00 points).
For card reader versions of RVM software only.
0 0 Y
STEEL_RATIO

Normally, STEEL_RATIO=90, which means at least 90% of the container sensor samples must be steel, otherwise the container will be rejected.

This parameter can be changed if the RVM won’t take steel cans with an aluminum lid.
Some cans such as 1 Liter Danish cans can be as low as 82% steel, 18% aluminum. To fix this problem STEEL_RATIO must be lowered to a number less than 82. 

90 0 Y
STEEL_VALUE if non-zero pay DEPOSITn-1 for steel cans, ignoring value in barcode table. Max value=4 = DEPOSIT3
For RVM versions that support charity only. Added 11/6/03.
0 0 Y
STEELTHRESHLD This many volts (x.01) above baseline (usually 2.5V) = steel.
The STEELTHRESHLD parameter is similar to ALUMTHRESHOLD except it defines how much the sensor much increase before the software declares that a steel can is inserted.
90 0 Y
SUPPLECPNBYTE 0 = Legacy supplemental method. This is the default value; when updating the RVM software to this version, the supplemental search routine will work the same way it currently works in the field:
The barcode table is first searched for the base barcode. If the barcode's option byte indicates a supplemental barcode is required, a second scan for a 2-digit supplemental barcode will occur (except IS220 scanners which read the base barcode and supplemental simultaneously). The barcode table is then searched for the 2-digit supplemental (such as 01FFFFFFFF) to determine if the container should be accepted.

1= Each barcode's coupon byte specifies the supplemental barcode expected for that container.
The barcode table is first searched for the base barcode. If the barcode's option byte indicates a supplemental barcode is required, a second scan for a 2-digit supplemental barcode will occur (except IS220 scanners which read the base barcode and supplemental simultaneously). The 2-digit supplemental read must match the barcode's coupon byte for the container to be accepted. 
Since the coupon byte is limited to a hex nibble (0-F), this scheme limits the RVM to supplemental codes 01-15.
2-digit supplemental codes in the barcode table are ignored.

Barcode table examples: (the coupon byte is shown in red).
Coke Classic uses an 01 supplemental:
496340FFFF,0,1,0,2

Heineken in NY will use an 02 supplemental:
7289000016,0,2,0,2

Heineken in other deposit states uses an 01 supplemental:
7289000016,0,1,0,2

For Corona 10 supplemental, use A in the coupon byte, as hex A=10:
806614FFFF,0,A,4,2

The software allows you to define a specific 2-digit supplemental barcode to accept, by barcode. This change is required to accept the new Heineken 02 supplemental codes in NY. Heineken will be using an 02 supplemental on their NY deposit containers, and an 01 supplemental on their deposit containers in other states. In NY, the RVM must accept Heineken 02 supplementals and reject Heineken 01 supplementals, yet still accept 01 supplementals on Coke products.

Added in version 1/17/13.

0 0 Y
SUPPLEMENTAL

Non-zero enables supplemental barcode detection. A supplemental barcode is an additional 2-digit barcode placed on certain containers (such as Coke cans in NY with a 01 code).

The parameter value also defines the length of time (x10 ms) to scan for the 2-digit supplemental barcode.
Do not enable multi-scan and supplemental bar code detection at the same time in versions of RVM software prior to 9/24/03! Otherwise the RVM will basically ignore the supplemental barcode requirement and accept cans without the proper supplemental barcode. Additionally, another bug exists that results in corrupted RVM memory identical to the WILDCARDSTART bug.

The scanner will scan several times (as defined by the USE_LASER parameter) for the supplemental barcode. The duration of each scan is defined by the SUPPLEMENTAL parameter. Since USE_LASER is normally set to 3, the laser will scan up to 3 times for a supplemental barcode when the main barcode indicates a supplemental barcode (usually 01) is also required (as defined by barcode option bit 1 in the barcode table).

Note: in software versions prior to 5/15/06 the laser scanned for the supplemental barcode just once, for the length of time specified by the SUPPLEMENTAL parameter (max 1.1 sec).

Also see SUPPLEMNTMODE parameter.

0 0 Y
SUPPLEMNTMODE

Defines the 2-digit supplemental barcode search mode. There are two settings/modes:

0 = The container is searched for a regular UPC/EAN barcode. The table is searched for this barcode, if the barcode's option byte indicates a supplemental barcode is required, an additional scan for a 2-digit supplemental barcode will occur (if the SUPPLEMENTAL parameter is set). The barcode table is then searched for the 2-digit supplemental to determine if the container should be accepted.

1 = The container is searched for a 2-digit supplemental barcode only. If a supplemental barcode is found, the barcode table is searched for a match (SUPPLEMENTAL parameter are ignored). This mode is typically only used in Japan.
Note: when SUPPLEMNTMODE=1, the scanner diagnostics will only scan for 2-digit supplemental barcodes.

The barcode table must contain the appropriate 2-digit supplemental barcode(s) to accept and each must be right-padded with "F"s such as "01FFFFFFFFFFF" for a supplemental code of 01.

Note: to accept a container that only has a 2-digit supplemental barcode requires a Metrologic scanner, because the Envipco scanner can only scan supplemental barcodes in one direction, and only scan supplemental barcodes that are placed directly after the regular barcode.

RVM versions 02/08/12 and later don't support this parameter (except Japanese versions), they behave as if SUPPLEMNTMODE =1.

0 0 Y

TAKE_UNREAD

If non-zero, this assumes a scanner is installed, but enables the machine to accept containers that don't have a barcode (or the barcode was unreadable).

Note: in versions 6/17/11 and later the value defines the commodities of containers to accept with no barcode. To determine a value for this parameter, add the following commodity values:
1 (alum), 2 (steel), 4 (green PET), 8 (clear PET), 16 (clear glass), 32 (green glass), 64 (amber glass), 128 (vinyl), 255 (all)
Previously, any non-zero value let the RVM accept containers without barcodes. To mimic previous software behavior, set TAKE_UNREAD=255 to enable or 0 to disable.
Note: ultimately, the bin configuration file defines the commodities the machine accepts.

The UNREAD_VALUE parameter determines how much to pay for unreadable containers.

0 0 Y

TAKETICKET_B4

0=don't check Hecon printer's "ticket present" sensor before printing
1=check Hecon printer's "ticket present" sensor before printing cash or charity voucher
2=check Hecon printer's "ticket present" sensor before printing coupon
3=check Hecon printer's "ticket present" sensor before printing voucher and coupons

For example, if TAKETICKET_B4=1 and the customer presses the cash payment button, if the printer's "ticket present" sensor is blocked the RVM will beep and display "PLEASE TAKE YOUR TICKET BELOW" (line 59 of messages.tbl), waiting for the customer to remove the ticket, observing the TAKETICKET_TM settings.
After printing a cash or charity voucher the RVM will again display "PLEASE TAKE YOUR TICKET BELOW", observing the TAKETICKET_TM settings as before.
As before, after printing a coupon the software does not immediately make you remove the ticket.

Note: if the printer's front sensor remains blocked:
• The printer itself won’t allow a new roll of paper to be fed after running out of paper.
• If a paper jam occurs the printer will not report a paper jam.

Added in RVM versions 6/9/09.

0

0

Y

TAKETICKET_TM 0 = cash/charity ticket must be taken before allowing next customer to insert containers.

non-zero=defines how long to wait (x100ms) for customer to take ticket before allowing next customer to insert containers. For example, if TAKETICKET_TM=90 and the customer presses a payment button but doesn't take his ticket, the RVM will display "PLEASE TAKE YOUR TICKET BELOW" and beep every four seconds until 9 seconds has elapsed, at which time the RVM's display will return to "INSERT CONTAINER" and the RVM will stop beeping.

Added in RVM versions 7/10/07.
0 0 Y
UNREAD_BIN

Specifies which bin to place unreadable containers when TAKE_UNREAD=1. Valid values:

  • 0 (use material sensors to determine which bin to place container, based on the silos table)
  • 1 (left bin)
  • 2 (middle/right bin)
  • 3 (right-most bin/side cabinet)

This is useful to allow unreadable PET bottles to be placed into the green PET bin of an RVM with a clear PET and green PET bin. Previously, all unreadable PET would be placed into the clear PET bin. FYI, all unreadable glass defaults to clear glass.

Note: if UNREAD_BIN is set to non-zero, the BIN_TOGGLE feature will not work for unreadable containers.

0 0 Y
UNREAD_VALUE

Specifies the amount to pay for containers accepted with unreadable barcodes when the TAKE_UNREAD parameter is set. Valid values of UNREAD_VALUE are 0-3, corresponding to the actual deposit values defined by the DEPOSIT0-DEPOSIT3 parameters.

This parameter allows unreadable containers to be accepted but not paid for (set UNREAD_VALUE=3 and DEPOSIT3=0).

0 0 Y
USE_DIVERTER

0=no diverters installed.

Add the following values to enable:
1=upper diverter
2=lower diverter
4=side cabinet diverter

for example, 3=upper & lower diverters installed, 7=all 3 diverters installed

0 0 Y
USE_EEPROM

0 = EEPROM not installed.

1 = EEPROM installed.  

The EEPROM is a data backup device that can be used in non-Site Controller configurations.

If enabled, various counters (the first 25 counters of the counters table, except counters 7-9) are saved to the EEPROM for safe-keeping after a successful payout. The counters are not saved after every container because EEPROMs have a limited number of write cycles. A warning 178 (EEPROM error) will be given if the EEPROM fails to accept the data.

Keypad command #3, 01 (save data to EEPROM) should now be used prior to performing an RVM controller board swap.

Keypad command #3, 03 (restore data from EEPROM) should now be used after performing an RVM controller board swap.

0 0 Y
USE_LASER

Non-zero = the scanner is enabled and the number entered determines the number of scan attempts.  

0 = the scanner is not used. Acceptance of containers is based solely on the ability of the container sensors to identify a container.
Note: to disable, you must also set SCANNER_TYPE=2.

3 1 Y
USE_STAGING

Applies to can machine only.

0 = cans will be fed into the bail area one at a time. The feed wheels will not come on to feed in the next can until the previous can has been tossed into the crusher. This mode is generally not used.

non-zero = cans will be staged at the staging sensor prior to being fed into the bail area. This allows the customer to insert cans faster.
Does not apply to XMT software versions.

1 0 Y
WARN_TIME When enabled (set to a non-zero value), the RVM will log and transmit a warning if it is has been in a certain condition for the amount of time specified by WARN_TIME  (x100 ms). The default value of WARN_TIME  is 6000 = 10 minutes.
New warnings:

210 - Too long in "Remove container" mode    [such as if customer holds the customer door opens a long time]
211 - Too long in "Cabinet door open" mode  
[cabinet door left open a long time]
212 - Too long in "Take your ticket" mode   
[waiting for customer to take ticket - only enabled when TAKETICKET_TM=0]
213 - Too long in Service mode               [technician entered PIN but hasn't quit service mode]
214 - Too long in "Remove reject" mode      
[reject chute sensor blocked]

Warning 214 added in RVM version 5/6/13.
Note: requires Greek RVM software version 10/5/07 or later. Added in all other RVM versions on 5/2/13.
6000 0 Y
WEIGHT_ACCEPT

non-zero = use weight sensor for acceptance (ignore material sensors) and defines bin # to accept (1=left, 2=right), default value=0.
Meant for use with TAKE_UNREAD=1.
This allows:
- a PET RVM to accept blue PET bottles that are not detected as PET but are light weight.
- a glass RVM to accept heavy glass bottles with a PET wrapper (the PET sensor could also be disabled)
 Note: if this feature is enabled, the RVM will also accept undesirable containers such as paper cups, etc, as long as it's the correct weight.
Note: requires Greek RVM software version 9/30/08 or later.

0 0 Y
WEIGHT_SENSOR

Set to non-zero to enable the weight sensor and define which commodities use the weight sensor for acceptance:
1=can (container must be light)
2=PET (container must be light)
4=glass (container must be heavy)
Add values for multiple commodities, for example, 7=enable for all commodities

Note: requires Greek RVM software version 9/30/08 or later.

0 0 Y
WEIGHT_TICKET

2=print the error log (same as keypad command #4,05) if the bin clear button is held less than 3 seconds (bin counts are not cleared unless held more than 3 seconds).
Note: requires Greek RVM software version 7/10/07 or later.

1 = Print weight ticket when the weight ticket button is held less than 3 seconds. The bin counts are cleared when the button is held for more than 3 seconds.

0 = No weight tickets printed, clear bin counts when weight ticket button is held for any length of time.  

0 0 Y
WEIGHT_TIMER      

Defines the weight sensor debounce time (x10ms).

When rejecting a container due to the weight sensor,  a different message is displayed for each commodity, as defined by the message table line number:
602: CANS MUST BE EMPTY
603: GLASS BOTTLE IS TOO LIGHT
604: PLASTIC BOTTLES MUST BE EMPTY
 

Note: requires Greek RVM software version 9/30/08 or later.

30 0 Y
WILDCARDSTART

This parameter enables partial-wildcard barcode support. This allows all containers from a single manufacturer to be grouped into the same count. For example, the barcode 12345AAAAA will cause all barcodes starting with 12345 to be counted together. Note that the barcode table is first searched for an exact barcode match, if the barcode is not found, then partial-wildcard barcodes are searched for. The number of digits searched for is defined by the parameter WILDCARDSTART. 
In Japan, they are using 5-digit manufacturer codes, so WILDCARDSTART should be set to 5 to speed up the partial-wildcard barcode search.
Valid values are 1-9 (12 for EAN versions).

example: if WILDCARDSTART is set to 9, and the barcode 1234567890 is scanned, the RVM will first search the barcode table(s) for the barcode 1234567890. If not found, 123456789A will be searched for, then 12345678AA, then 1234567AAA, then 123456AAAA, ... 1AAAAAAAAA.

For the same barcode, if WILDCARDSTART is set to 5 and barcode 1234567890 is not in the table(s), 12345AAAAA is searched for, then 1234AAAAAA, then 123AAAAAAA, then 12AAAAAAAA, then 1AAAAAAAAA. This greatly speeds up the table search time, especially if a large barcode table is loaded.

Note: there is no way to search for barcodes such as AAAA123456. The special wildcard barcode AAAAAAAAAA will match all barcodes however.A major bug exists in all versions prior to 9/24/03. Do not set WILDCARDSTART to a number greater than 9 (11 for EAN versions of software)! If set to a large number such as 65000, the RVM's memory will become corrupted after the first non-participating barcode is inserted, causing numerous problems such as (but not limited to):

  • the RVM will lock up with the container spinning on the rollers
  • any subsequently printed vouchers will have many "A"s in place of the site name and number
  • the RVM's meter reading and all internal counters will be set to 1094795585, corrupting all "MP" counters in the Q file retrieved from the RVM (the barcode counts are unaffected however).
  • the RVM's crusher may unexpectedly turn on
  • the RVM's display may blink erratically
  • the RVM may log numerous bogus "E104: Battery voltage lower than 2.2V" messages

Furthermore, once this occurred, PCRVM/SC/WinRVM would be unable to perform a software update due to a communications failure. As a workaround, start the software installation procedure immediately after rebooting the RVM.

Parameter added in RVM version 7/23/97.

0 0 Y

The following parameters apply only to the "distributor report" versions of RVM software:

CANS_PER_CASE defines number of cans per case for the individual distributor counts ticket. 0=use bin count from silo table as the number of cans in a bag. Note: the silos table still defines how many containers to accept before going full.
Parameter added 3/12/03
0 0 Y
GLS_PER_CASE    defines number of glass bottles per case for the individual distributor counts ticket. 0=use bin count from silo table as the number of bottles in a bag. Note: the silos table still defines how many containers to accept before going full.
Parameter added 3/12/03
0 0 Y
PET_PER_CASE  defines number of PET bottles per case for the individual distributor counts ticket. 0=use bin count from silo table as the number of bottles in a bag. Note: the silos table still defines how many containers to accept before going full.
Parameter added 3/12/03
0 0 Y

 

HANDLINGFEE_C handling fee (xx.xx cents) per can used by the individual distributor report ticket. 
Note: The handling fee parameters define how much to pay per container including the deposit amount. If the handling fee is the same for all commodities then set all 3 parameters to the same value such as 0600 for 6 cents. Fractional cents are supported, so you could configure the RVM to pay 4.5 cents per can by setting HANDLINGFEE_C=0450.
Parameter added 10/16/02.
0 0 Y
HANDLINGFEE_G handling fee (xx.xx cents) per glass bottle used by the individual distributor report ticket.
Parameter added 10/16/02.
0 0 Y
HANDLINGFEE_P handling fee (xx.xx cents) per PET bottle used by the individual distributor report ticket.
Parameter added 10/16/02.
0 0 Y

 

The following parameters apply only to XMT versions of RVM software:

See XMT 9-5-02 software update for more information on the XMT.

BLOW_DELAY If BLOW_DELAY=0 then no blower is installed and the software will operate as before, otherwise it defines the delay (x10ms) after turning on the blower (connected to the glass side cabinet crusher fwd output) before turning on the flattener. The blower is turned off after the flattener run-time timeout. The blower is kept on during a flattener stall. Like the MU2000, if the RVM goes out of service, the blower will remain on until the flattener run timeout expires.
Added new dedicated blower on/off/jog diagnostic 39 that is enabled whenever the BLOW_DELAY parameter is set.
Parameter added in RVM version 5/15/02.
0 0 Y
BLOW_OFFDELAY  

Parameter added in RVM version 8/12/09.

60 0 Y
CONVEYBLOCKTM If conveyor beam blocked longer than this (x10 ms), run conveyor backwards to dump can into trash can 100  0 Y
CONVEYFWDTIME Max time (x100 ms) to run conveyor forwards to let blower remove the can 30 0 Y
CONVEYLEAVEON if non-zero, turn conveyor on forwards after beam is unblocked to handle two cans run at once. Turn conveyor off when shredder times out. 1 0 Y
CONVEYMAXREV if non-zero, go out of service after conveyor is reversed this many times in a row 5 0 Y
CONVEYREVTIME Time (x100 ms) to run conveyor backwards to dump can if barcode's option bit 3 set 22 0 Y
CONVEYREVTM2 defines how long to reverse the conveyor (x 100ms) when attempting to clear the can intake with the blower turned off. During this time, "ONE MOMENT PLEASE..." will be displayed and the "push button below for payment" is removed from line two of the display.
Previously, the CONVEYREVTIME parameter was also used for this delay. CONVEYREVTM2 should be set to a long time such as 300 (30 sec) to give more time for the blower to release the can. When reversing the conveyor to clear the intake, if the can intake beam clears prior to the CONVEYREVTM2 timer expiring, the conveyor will run in reverse for the short amount of time defined by the CONVEYREVTIME parameter instead of waiting for the longer CONVEYREVTM2 timer to expire. 
Note: after the CONVEYREVTIME or CONVEYREVTM2  timers expire, a "can intake blocked" failure will occur unless the intake beam is clear.
If the CONVEYREVTM2 parameter is set to 0, this feature is disabled, and the blower will not turn off during can conveyor reverses. The software will behave the way it did prior to adding the CONVEYREVTM2 parameter.
Make sure RUN_TIME >= CONVEYREVTM2 +30, otherwise the RVM will not detect "conveyor beam blocked" failures.

Parameter added in RVM version 10/14/04.
300  0 Y
CONVEYSTOPDLY Delay (x 10 ms) after conveyor beam blocked before stopping conveyor 5 0 Y
CONVEYSTRTDLY Delay (x10 ms) after bail starts to accept can before starting conveyor motor, 0=no delay 0 0 Y
FAILRUNTIME The minimum time (x100 ms) to keep conveyor/shredder on after accepting a container before shutting them off when a failure is detected. The default value is 40 = 4 seconds. Previously, if a PET bottle was accepted that filled the PET bin, the RVM would shut off the conveyor and shredder while the bottle was still on the conveyor before being fed into the shredder. After a container is accepted a timer starts, and if the machine goes out of service before this timer expires, the conveyor/shredder will be left on until the timer expires.
Parameter added in XMT version 5/19/09.
40 0 Y

The following parameters apply only to coupon versions of RVM software:

See here and Vol_07_No_01__CF1500_RVM_(coupon)_5-27-99 for more information on coupons.

1ST_COUPON Vend first coupon after customer inserts this number of containers.
Note: 0 is the same as 1.

For RVM versions 1/21/09 and later:
if 1ST_COUPON=0 and COUPON_FREQ>0, a coupon is vended every COUPON_FREQ containers, regardless of how many customers/vouchers printed. If 1ST_COUPON>0 then the customer's coupon count is reset whenever the customer presses a payment button.

5 0 Y
ALT_VOUCHER 0=print regular cash voucher

non-zero=use cash voucher loaded into this particular coupon slot. This allows different cash vouchers to be loaded into the RVMs memory. The current cash voucher in use can be specified by simply changing this parameter.

For example, if the following coupon list file RC.CLS is loaded into the RVM with PCRVM to define the coupons and vouchers:

rcgu1.cpn
rcgu2.cpn
rcgu3.cpn
CSHRCGU1.VOU
CSHRCGU2.VOU

If ALT_VOUCHER is set to 4, the cash voucher will be changed to CSHRCGU1.VOU.

0 0 Y
COUPON_FREQ number of containers between coupons (0=never vend coupons, minimum=4)
(if non-zero, coupons will be vended by default)
0 0 y
COUPON_MASK 0=all containers will counts towards a coupon

non-zero=only count containers whose barcodes’ coupon byte match this bit pattern (bits are ORed)

For example, if COUPON_MASK=2, then any barcode whose coupon byte’s bit 1 is set will count towards a coupon. In the RC Cola program, RC products will have bit 1 set.

For Greek RVM software versions 10/23/06 and later, COUPON_MASK is used differently. If COUPON_MASK=0 then "normal" coupons are vended only. If COUPON_MASK=1 then "special" coupons are also enabled.
See the 10/23/06 RVM software release note for more info.

0 0 Y
COUPON_MODE 0=vend coupons as soon as they are due (default value)
1=vend coupons after customer presses for payment (coupons will be printed prior to the cash voucher)
2=the RVM will not print a cash voucher, but it will send a message to WinRVM so that a coupon selection screen can be shown on the interactive PC monitor. Must also set COUPON_FREQ=0.
Requires 4/3/09 or later RVM interactive barcode client software. Line 608 of the message table ("SELECT COUPON FROM MONITOR") will be briefly shown on the RVM's LCD when the cash button is pushed.
3=vend coupons after customer presses for pay and don't print cash voucher if a coupon was vended (6/17/10 or later interactive versions only)
4=print cash voucher and show coupon selection screen when customer presses payment button. (10/12/10 or later interactive versions only)
0 0 Y
COUPONOUTFAIL non-zero = fail when run out of coupons 0 0 Y
COUPONTOPRINT non-zero=only print this particular coupon (as defined by the order in which coupons were loaded to the RVM), ignoring all other coupons that are loaded into the RVM’s memory

0=allow all coupons in memory to be vended (default value)

0 0 Y
CPNSELECTTIME

After pressing the cash button the RVM's LCD displays "SELECT COUPON FROM MONITOR" and the RVM will not accept containers until a coupon selection is made on the interactive PC.
CPNSELECTTIME specifies how long (x100ms) to wait for the customer to select a coupon from the interactive PC. If this time expires, the RVM will return to "insert container" mode.The default value is 600=60 seconds. This time value must be set to the same time (or slightly longer) as the "coupon selection screen timeout" in WinRVM's Interactive Mode Options.
Note: WinRVM ver 2.0.1 or later automatically sets the RVM's CPNSELECTTIME parameter value when starting Interactive Mode if "Show coupon selection screen" is enabled in the Interactive Mode Options.
The maximum value of this timer is 16380 = 27 minutes.

parameter added in interactive RVM version 8/18/09.

600 0 Y
CUT_COUPON non-zero=cut paper after coupon print 0 0 Y
PARM_SCHEDULE Automatically change RVM parameters based on the date. Multiple dates and parameter changes can be defined.

0 = disable this feature.
1 = enable. table (18, PARMSKED.TBL), defines the start dates and the parameters to be changed 
Site controller installs must have a new TEMPLATE.LST file to force table 18 to be loaded to the RVMs.

0 0 Y
VENDEACPNONCE 0=unlimited number of coupons per customer, 1=only vend 1 of each coupon per customer 1 0 Y
 

The following parameters apply only to color-sensor enabled versions only:

AMBERTHRESHLD Color = amber if this many volts (x .01) above baseline.   100 0 Y
COLOR_SENSOR Non zero = Enable color sensor 0 0 Y
GLASS_RATIO Minimum allowable % of glass counts compared to other counts before rejecting. 40 0 Y
GREENTHRESHLD Color = green if this many volts (x .01) above baseline.   50 0 Y
INTENS_CLEAR If color glass, but intensity is < baseline-INTENS_CLEAR, then save as amber glass.   50 0 Y
INTENS_CP When intensity sensor drops below baseline by this much (x .01v) a container is present.   10 0 Y
INTENS_INVALD Color data is invalid if intensity is this much (x .01V) less than baseline intensity.   175 0 Y
PET_SENSOR Non zero = Enable color sensor unit’s PET sensor.  For glass defines the number of PET sensor counts +1 before discarding.   0 0 Y
PETTHRESHOLD PET = PET if this many volts (x .01) above baseline.   20 0 Y
 

Flex/LCM-specific parameters:

CABINET_DOOR override the cabinet door switch for testing purposes, 0=use hardware switch, 1=closed, 2=open 0 0 Y
EXITSNSR_TIME time (x10ms) for container to unblock exit sensor while reversing feed 45 0 Y
FEED_ATTEMPTS number of times to toggle direction of feed when looking for barcode/commodity when the commodity type couldn't initially
be determined by the sensors. Set to an odd number like 5 so when rejecting, the container will be left at the customer door
Note: set USE_LASER=FEED_ATTEMPTS-2 to avoid leaving a rejected container at the back of the feed.
3 0 Y
FEED_REV_TIME time (x100ms) to run feed in either direction while looking for barcode/commodity. Also time to reverse feed when rejecting container to customer. 10 0 Y
FDUNBLOCK_DLY time (x10ms) to wait for container to unblock the exit sensor after FEEDUNBLOCKTM expires 40 0 Y
FDUNBLOCK_ATT number of times to toggle direction of feed when trying to clear a blocked exit sensor 5 0 Y
FEEDUNBLOCKTM time (x100ms) to run feed in reverse when accepting container, diverter is up but exit sensor remains blocked 5 0 Y
REJECTMSGTIME time (x100ms) to show the reject message screen before returning to the welcome screen loop. 0=show screen until customer door opened.
Note: the actual delay may be 1 second longer than specified due to the way the  LCD program works.
40 0 Y
REMOVE_MSG 1=leave "remove container" message on screen until customer door opened when rejecting container, 0=return to "insert container"
Parameter added 7/23/12. Previous versions of software behaved as though REMOVE_MSG=0.
1 0 Y

Flex/LCM and HDS specific parameters:

BAIL_FEED_ATT max # of times to retry accepting container into crusher when bail beam blocked after returning to center (0=disabled).
If BAIL_SENSOR bit 3 is set then the check is not made.
1 0 Y
LCD_TYPE Type of customer LCD: 1=Amulet LCD (older style), 2=Reachtech LCD (newer).
Parameter added in RVM version 10/3/12
2 0 Y
LCD_PACK_DLY Delay this much time (x10ms) after sending a command to the LCD before sending another command to avoid overrunning the LCD
Parameter added in RVM version 10/3/12
6 0 Y
LCD_PAGE_DLY Delay this much time (x10ms) after sending a command to switch background images to the LCD before sending another command to avoid overrunning the LCD (use 25 for Reachtech, 120 for Amulet)
Parameter added in RVM version 10/3/12
25 0 Y
POWERONDELAY Added parameter: POWERONDELAY = delay (x1000 ms) after showing RVM version after powerup before continuing, allows time for Amulet LCD to power up. If the delay is too short the display text may be garbled until the customer door is opened. 5000 0 Y
TWO_LINE_LCD 0=don't show customer messages on 2-line LCD, 1=show messages (for the interactive version) 0 0 Y

HDS-specific parameters:

BAIL_ATTS_MAX Number of times to run entire indexing sorter recovery routine sequence before giving up and going out of service for a bail failure. 2 0 Y
BAIL_DELAY_C Time to delay (x 10 ms) after bail reaches the left or right limit before returning to center when accepting a can. 60 0 Y
BAIL_DELAY_G Time to delay (x 10 ms) after bail reaches the left or right limit before returning to center when accepting a glass bottle. 60 0 Y
BAIL_DELAY_P Time to delay (x 10 ms) after bail reaches the left or right limit before returning to center when accepting a PET bottle. 60 0 Y
BELTCLEANFWD Time (x100ms) to run belt forwards during cleaning routine, 0 to disable
Parameter added in RVM version 1/23/13
50 0 Y
BELTCLEANTIME Perform belt cleaning routine every X minutes (run belt fwd for BELTCLEANFWD), 0=disable belt cleaning routine
Parameter added in RVM version 1/23/13
60 0 Y
DONTTHROWMSG Display customer message to not throw containers in if the following sensors aren't blocked before rejecting (add values): 1=PET sensor, 2=entry 2 sensor, 4=exit sensor 1, 8=exit sensor 2
0 = disable.
This is for the case where the container is thrown into the bail area but exit sensor 2 is never blocked.
Notes: in all cases, these features are only enabled when DONTTHROWMSG>0. Set DONTTHROWMSG=0 to make software behave like previous versions. If you want to enable features 1 and 2 above without enabling feature 3, set DONTTHROWMSG=16.
Line 226 of the message table defines the "PLEASE DON'T THROW CONTAINERS IN!" message.
14 0 Y
ENTRY2DELAY When rejecting a container, once the entry 2 sensor is blocked, delay this amount of time (x 10ms) before reversing the feed to block the entry sensor. 20 0 Y
ENTRY2MODE

To prevent feeding two containers into bail at once and paying for one, added parameter to define how quickly customer can insert their next container:
0=ignore entry 2 sensor while feeding previous container.
Non-zero=show "Please insert ONE container at a time" and reject both containers if entry 2 sensor blocked while feeding previous container while:
3=waiting for front exit sensor to unblock, 4=waiting for rear exit sensor to unblock, 5=waiting for gate to close

4 0 Y
ENTRYBEAM_DEB time (x10ms) to debounce entry beam when returning a container to the customer 25 0 Y
ENTRYBEAMONLY 1=entry beam defines when to start feed (other feed sensor blockage starts a reject cycle like previous versions of software)
0=also use mid and exit sensor 1 to start feed (allows customer to throw container into feed area without first blocking the entry sensor)
0 0 Y
ENTRYBEAMMODE Specifies how machine should behave if customer inserts a second container while the previous container is being scanned. "Insert one container at at time" will be displayed in all cases. Possible values:

0 = Both containers are rejected (after customer removes second container the feed is reversed and customer must remove the original container). This prevents customer from inserting a second container too quickly which could result in both containers being accepted into the bail but only paying for one. However, this setting will annoy the customer if they insert their second container too quickly because they must remove their first container.

non-zero = if entry beam is blocked less than this amount of time (x10ms), reject both containers. This handles the case where customer quickly inserts a second container while the feed is NOT on while the previous container is being scanned (both containers are rejected instead of accepting both and paying for one).
If the entry beam is blocked longer than this time, the machine waits for the second container to be removed, then scanning of the previous container will resume. The default value is 15.
Note: this scheme can handle the case where a customer quickly inserts a second container too quickly, but it can't prevent customer from slowly inserting a second container just beyond the entry beam. In this case, the RVM has a blind spot where it has no idea that a can has been inserted, and there is still a possibility of accepting two containers and paying for one. This issue can only be resolved by adding a another sensor about 3" beyond the entry beam to eliminate the blind spot (or setting ENTRYBEAMMODE=0).
15 0 Y
EXITBEAM2_DEB Time (x10ms) to debounce rear exit sensor to prevent prematurely closing gate when accepting 8oz cans. 10 0 Y
EXITBEAMS_MIN minimum amount of time (in program loops) that both exits sensors must remain simultaneously blocked, otherwise container will be rejected. 0=disable 3 0 Y
EXITBEAMS_MAX maximum amount of time (in program loops) that both exits sensors may remain simultaneously blocked, otherwise container will be rejected. 0=disable 90 0 Y
EXITBEAMSMODE Add the following values to enable specific fraud detection methods: (0=disable)
1=rear exit sensor blocked before front exit sensor
2=rear exit sensor clear before front exit sensor
4=rear exit sensor blocked unexpectedly after container in bail
1 0 Y
FEED_REV_ATTS Number of times to retry reversing feed to return container to customer if entry sensor never blocked to free a possibly bridged container. Previously when rejecting a container the software didn't care if the entry beam never blocked when returning a container to the customer. Now, when rejecting a container if the entry beam is never blocked the software will jog the rollers then reverse the feed to return container to customer. If the entry beam is still not blocked the software will keep retrying until the number of the times specified by the parameter. 2 0 Y
FEED2_DELAY time (x10ms) to keep rear feed on once rear exit sensor goes unblocked prior to moving bail when accepting a container 10
(55 for indexing sorter)
0 Y
FEED2_TIME max time (x100ms) to run rear feed waiting for rear exit sensor to block when accepting a container. Container will not be paid for if not blocked in time. 20 0 Y
FEEDPASTENTRY additional time (x10ms) to run feed in reverse once entry sensor is blocked when returning container to customer
Note: removed in 7/22/11 and later versions.
5 0 Y
FEEDSTOPSNSR When feeding in container past the mid sensor for the time defined by FEED_TIME, this defines if the feed should be stopped if the exit 1 sensor is blocked prior to the FEED_TIME expiring: 0=no (for new sensor position), 1=yes (for old sensor position next to the gate)
Parameter added in RVM version 9/20/11
0 0 Y
GATE_ATTEMPTS # of times to retry gate before sending error message (255 max) 3 0 Y
GATE_TIMEOUT gate movement timeout (x 100ms) 18 0 Y
GATECLOSEOPT 1=don't close gate if exit sensor 1 blocked, 2=don't close gate if exit sensor 2 blocked (default), 3=don't close gate if either exit sensor blocked, 0=ignore both sensors when closing gate
Parameter added in RVM version 9/20/11
2 0 Y
GATEFEEDDLY 0=wait for gate to open before feeding container into bail (old behavior). If non-zero, start opening gate then delay this amount x10ms then start feeding container into bail prior to the gate fully opening.
Note: If the FEED_TIME delay is too long (current default value is 4) the container may be fed onto the rollers such that it’s almost touching the gate. This may cause a problem if we then feed into the bail too quickly as the container may slam into the gate.
20 0 Y
INDEX_SORTER

1=indexing sorter installed, 0=CF1500-style sorter/bail installed
Parameter added in RVM version 5/23/11

0 0 Y
LEAVEFEEDON 0=leave feed off while customer idle (how previous RVM versions behaved). Feed turns on when customer inserts a container.
1 = leave feed on while customer idle (shuts off when pay button pressed, crusher timeout out, failure). This gives the customer a visual clue as to when it's OK to insert the next container - they don't need to look at the LCD. This should help speed up the real-world throughput: whenever the feed is on they can insert a container. After a container is rejected (such as can't read barcode), once customer removes the container, the fed will turn on automatically.
Parameter added in RVM version 9/16/11.
1 0 Y
MIDSENSORREJ 0=mid sensor doesn't have to be blocked to accept container as long as barcode read, 1=reject container if mid sensor never blocks (display "Don't throw containers in" if another sensor is blocked).
Parameter added in RVM version 6/4/12
1 0 Y
MIDSENSORTIME time (x10ms) to debounce mid sensor. Once container passes mid sensor, allow next container to be inserted. 4 0 Y
MINFEEDREVTM if total time spent (x100ms) reversing feed when rejecting two containers is less than this, keep feeding in reverse until this amount of time is reached. This fixes the following problem:
if inserted 2nd container too quickly then used your hand to quickly remove the 2nd container, if your hand blocked and unblocked the entry beam twice and the first container could not be seen by any sensors such as just past the exit 2 sensor, the 2nd container would be left in the feed tube. The next container inserted would be accepted normally and the customer's first container wouldn't be paid for.
5 0 Y
READYLIGHTOK Defines the RGB colors of the ready light to indicate when next container may be inserted (add following values: 1=red, 2=green, 16=blue)
Parameter added in RVM version 9/20/11
2 0 Y
READYLIGHTNO Defines the RGB colors of the ready light to indicate machine is busy (add following values: 1=red, 2=green, 16=blue)
Parameter added in RVM version 9/20/11
1 0 Y
REFEED_ATTS Number of attempts to feed container into bail area when exit sensors aren't blocked (helps feed in wet cans). The rollers are toggled direction between attempts. 0=disable feature. Previously, this feature was hard-coded to a value of 1 and the rollers didn't toggle direction. 2 0 Y
REFEED_TIME Additional time (x10ms) to feed in a long container if the entry 2 sensor is still blocked after feeding container past the mid sensor and stopping after the FEED_TIME delay.
Previously, FEED_TIME was also used for this delay.
10 0 Y
REJECT_MODE   If customer blocks the entry beam without inserting a container the machine can be configured to not perform a scan cycle followed by a reject cycle.
0=don't reject or turn on rollers if mid or exit sensors never blocked within ROLLER_START timeframe (default value). Note: may need to increase ROLLER_START from default value of 4.
1=assume container inside and attempt to scan for barcode (this is how previous software versions behaved).
  0 Y
REJECT_TRIES max number of times to attempt to reject a stuck container back to the entry sensor. 10 0 Y
ROLLER_SAFETY  0=allow customer to stage next container blocking entry beam while rollers are on
1=turn off rollers if entry beam blocked
2=turn off rollers if both entry beams blocked
1 0 Y
ROLLER_START While feeding in container if mid sensor never blocked, start scanning after this much time since feed started (x100ms), 0=disable. 4 0 Y
ROLLER_STOP  roller stop mode:
1=wait for blocked, unblocked, then blocked again before stopping (US infeed with 3 roller lobes),
2=wait for unblocked then blocked before stopping (German infeed with one roller lobe)
3=as soon as roller index sensor is initially blocked stop rollers (not recommended, may not stop roller consistently)
Parameter added in RVM version 5/5/11.
1 0 Y
ROLLERDLY_CCW When stopping the rollers while turning counter-clockwise, delay this much time (x1ms) after target is initially blocked before stopping the rollers. 0 0 Y
ROLLERDLY_CW When stopping the rollers while turning clockwise, delay this much time (x1ms) after target is initially blocked before stopping the rollers. 0 0 Y
ROLLERJOGTIME

When rejecting a stuck container, run rollers in reverse (defined by ROLLER_DIR) for this amount of time (x10ms), then re-index them in the normal direction while returning container to customer.
Previously, the rollers always ran in one direction while scanning.
Parameter added in RVM version 5/13/11.

30 0 Y
ROLLERSTALLTM while scanning for a barcode if no roller movement is detected within this timeframe (x10ms) (bottle caps can cause the rollers to stall), reverse the direction of the rollers. Default value is 60. Previously, the rollers always ran in one direction while scanning and the software didn't monitor for roller stalls.
Parameter added in RVM version 5/13/11.
60 0 Y
ROLLERTIMEOUT max time (x10ms) to wait for roller index position sensor (US infeed with 3 roller lobes: use 50, German infeed with one roller lobe: use 100).
Parameter added in RVM version 5/5/11.
50 0 Y
STAGE_TIME After reading can or glass barcode and turning on feed, if entry beam 2 is blocked within this much time (x10ms) reject container, 0=disable. Note: do not set this to a value larger than 30 as this will cause containers to be rejected even after the "ready light" is turned on.
Parameter added in RVM version 9/26/11.
10 0 Y
THROWDETECT time (x100ms) after barcode scanning starts to reject if any exit sensors were previously blocked but no infeed sensors are currently blocked, 0=disable feature.
Parameter added in RVM version 6/7/12.
6 0 Y
USE_GATE 2=only close gate when customer presses for payment, not after every container. This feature was added to increase the throughput speed. However, this will defeat the safety feature of the gate. I don't recommend this setting as someone could insert their hand into a crusher w/o blocking any sensors if they hold their arm at the top of the feed chute.
as before:
1=open/close gate after every container
0=gate disabled (not recommended for the same safety reasons as 2)
1 0 Y

MI optical camera-specific parameters:

CAM_START_DLY Delay (x1 ms) after bail beam initially blocked during container acceptance before sending command to camera to start looking for a mark, 0=don't send command (default is 0).
Set to 0 for the Axis camera system, 20 for the German camera (may need tweaking).
0 0 Y
CAM_TIMEOUT Max time (x10ms) to wait for camera to send an indication if a mark was found on the container. This timer starts when FEED_TIME expires. The default value is 70 (0=disable camera) 70 0 Y
CAM_TRIGGER 1=bail sensor triggers camera
2=staging sensor triggers camera (for Envipco camera)
Previously, in the Axis camera setup, the staging sensor was unplugged from the RVM and routed directly to the camera. When using the Envipco camera the staging sensor is plugged into the RVM.
CF1500-only parameter.
2 0 Y