*
> RVM Communications Problems... <
 
 

RVM not communicating or RVM status is "not selected".

"No RVM response to RSTART" is displayed

"No RS-485 card detected" error displayed when using RS-232 to RS-485 converter box

"No RS-485 card detected" error displayed when using Quatech DS-200/300 card

An "SC02:No RVM Response to CRC Query" error is sometimes logged.

The RVM’s RS-485 port address occasionally gets reset to "?".

The site controller won’t load an RVM with software.

The site controller won't load barcodes to an RVM.

The CF1500 site controller does not detect one or more RVMs.

When RVM is powered down, it always loses it’s port address.

A "W150: Command to RVM Invalid" is logged for each RVM when the Site Controller program is started.

Unknown RVM messages such as "steel ratio=0, al=0, steel=0", etc. are logged.

A "no response to REBOOT" error is displayed on the PC after new RVM software is loaded to the RVM.

MU2000 RVM on Port 5 doesn’t communicate



RVM not communicating or RVM status is "not selected".
[updated 12/7/12]: 

  • Turn all the RVMs off and turn the PC off (don't just reboot them, turn them OFF). Turn the RVMs back on first, then turn the PC back on.

  • Turn the RVM off then back on then immediately attempt communications.

  • Check for the correct communications mode (RS-232/RS-485) on all RVMs: hold down the "#" key while powering on the RVM to change. Make sure jumper W5 is set to RS-232 or RS-485, as appropriate.

  • Check for the correct baud rate on all RVMs (older installs use 19,200, newer installations use 38,400): hold down the "#" key while powering on the RVM to change. The baud rate must match the baud rate configured in WinRVM or the Site Controller.

  • [RS-232 only] Check for the correct parity on the RVM (should be "OD"). On power up the display should indicate "MON 1500 [date] (RS232:38.4 OD)". To change: hold down the "#" key while powering on the RVM to change. hold down the "#" key while powering on the RVM. Press "0" for the Comm Options, press "7" for "OD" then "#" to go back.

  • Make sure battery jumper (W3) is on snugly.

  • Make sure the communications cable on the motherboard is plugged into the site Controller plug (J19).

  • Check/swap all communications cables (including the cable from the RVM board to the back of the machine).

  • If this is an interactive RVM, make sure the on-screen keyboard program is not running prior to running WinRVM as this program takes over the the COM port. Use WinRVM 3.3.4 or later to avoid this issue.

  • [RS-485 only] Make sure each RVM’s port address it set correctly and that no other RVMs have the same port address (RVM ports must be sequentially numbered, starting at 00).

  •  If chips at U46 and U47 (RS-485 drivers) on the RVM controller are hot to the touch they are probably blown up from a power surge. Replace RVM controller board to fix.

  • [RS-485 only] Plug the RS485 connector directly to one of the RJ45 connectors at the top-left of the RVM controller board. Disconnect the other RJ45 connector. Try again. If this works, your RVM controller is good but the cabling going to the back of the RVM or the RJ45 connector on the back of the RVM is bad.
    If this is a thru-the-wall installation, you can temporarily pull the AC box out slightly to allow enough room to route the cable into the RVM.

  • [RS-485 only] Use a LAN cable tester to verify all communications cables, including the junction blocks at the back of each RVM. A bad junction block on RVM 2 may cause an RVM downstream (such as the last RVM) to not communicate.

  • [RS-485 only] If using barcode-client software such as interactive or NexCycle version, use MON ROM 2-8-12 or later to avoid communications problems.

  • If using a USB to RS-232 adapter:
    - We recommend using the SABRENT Model SBT-FTDI 6 ft. USB 2.0 to Serial (9-pin) DB-9 RS-232 Adapter Cable 6ft Cable (FTDI Chipset) or FTDI US232R-100-BULK. We no longer recommend the IOGear GUC232A if used under Windows 7 or later.
    - Make sure WinRVM is set to the same COM port as the adapter (sometimes Windows changes the COM port number when the adapter is plugged into a different USB port). Use the Window's device manager to determine the COM port.
    - Disable power management on the USB to serial adapter:
    1. Click "Start" then type in "Device Manager" in the search box then click "Device Manager" in the list
    2. Double-click Ports to expand it, right-click "ATEN USB to serial bridge", and then click Properties.
    3. Click the Power Management tab.
    4. Uncheck "Allow the computer to turn off this device to save power" then click OK.

  • Swap the RVM's VFD / LCD (a bad LCD can cause RVM communications problems)

  • If all else fails, swap the PC (perhaps there's a loose serial cable inside the PC case or motherboard problem), then the RVM controller board.

  • Also see Troubleshooting RVM communications problems in the pocket PC FAQ.

  • For DOS-based Site Controller Sites:
    - Make sure the latest software is running in the Site Controller, RVM, and RVM Monitor ROM.
    - When the site controller is running, press F3 to view the site configuration, make sure X in "all X RVMs will be polled ..." matches the number of RVM connected. If not, run SCSETUP and enter the RVM serial number, RVM type, etc. for all the RVMs. 
    - If the PC is Pentium-based and the "speed calibration" that is displayed on startup is sometimes 850, when it is normally much higher, such as 19000, this is a known bug with SC version 1.33 and earlier: Temporary solution: set the PC’s clock speed to non-turbo via the turbo button, or set the clock speed to "low" via the CMOS setup. Solution: run the latest SC version!
    - If the "speed calibration" seems low, click here for details.

If this is a new DOS-based PC:

  • For DOS Site Controller Sites:
    - Run SCSETUP and make sure all the RVM's serial numbers and machine configurations are correct.
    - Check the CommDelay parameter in SC_CTRL.PRM, generally, it should have a ";" in front of it so that the SC will auto-calibrate this parameter. 
    The CMOS setup may need to be changed to prevent an IRQ 7 conflict between the parallel port and the Quatech RS-485 card:

  • Run the CMOS setup program. 

  • Select "Integrated peripherals" with the arrow keys and press Enter. Set OnBoard Parallel Port to disabled. 

    For DOS-based "El diablo" Site Controllers requiring a printer:

  • Select OnBoard Serial Port #2 and set it to DISABLE.

  • Select OnBoard Parallel Port and change it to 278/IRQ5.

  • Select OnBoard Parallel Port Mode and set it to SPP.

  • The modem must be configured for COM2, not COM3/IRQ5 (consult modem documentation). 

  • If a remote display is to be used, connect it to COM1.

  • Press Esc to exit. The Automated Power Management should also be disabled. Choose SAVE and EXIT. 

  • Note: if a PCI "win modem" is installed, remove it! It may cause the RVMs to not communicate because of IRQ conflicts.

    For DOS-based Proteva (and some other) PCs, make the above "El diablo" changes, plus:

  • In the BIOS FEATURES SETUP menu, set Anti-Virus Protection to Disabled, Boot Up System Speed to Low

  • In the POWER MANAGEMENT menu, verify that it is disabled and the option MODEM use IRQ is set to 3

  • In the PNP/PCI CONFIGURATION menu, set PNP OS Installed to NO, set Resources Controlled By to Manual, change the IRQ and DMA addresses for all interrupts IRQ7, IRQ14 and IRQ15 to to Legacy ISA, all others should be set to PCI/ISA PNP.

  • Set OnBoard MODEM to Disabled.

  • Set OnBoard SOUND to Disabled.

  • Set OnBoard USB Function to Disabled.

If no RVMs are communicating [RS-485 only]:

  • Connect just one RVM to the PC/pocket PC (disconnect all other RVMs from this RVM). Try every RVM, one-at-a-time, with all other RVMs disconnected. Turn off the RVM and the PC between tests. A single bad RVM controller or cable can cause all RVMs to stop communicating. Sometimes the RJ-45 connector at the back of the RVM gets damaged.

  • Use an 8-pin mod tap connector on the back of the RS-485 card (not a 6-pin connector).

  • For DOS Site Controller Sites: move the Quatech communications card in PC to a different slot.

  • For DOS Site Controller Sites: Check the dip switches on the Quatech communications card, they can easily be inadvertently changed if you had the PC’s case removed.

  • Reseat all cards in the PC and check all cable connections in the PC.

DOS Site Controller Sites: Run CONSOLE/CONS485 and press Enter, the RVM should respond with "ALERT_:150". If it still doesn’t communicate, as a last resort before swapping the RVM controller, pry up RAM chip U26 with a screwdriver and re-install to clear the RVM memory (note: all accounting data will be lost! RVM software must then be reloaded).

If all of these fail, swap the Site Controller PC.

MU2000:
While the site controller program is running, press shift-F1 to display the communications status screen. If a port’s interrupt count is increasing rapidly, this indicates a problem. Turn off the RVM that is connected to this port. If the status interrupt count is still increasing, then the PC’s comm port is bad. Swap cables on the back of the PC to an RVM that is communicating properly. If the status interrupt count is still increasing rapidly, then the PC’s comm port is bad, otherwise, the cable or RVM is bad - swap just the cables with known good cables to figure out which is bad.

WinRVM logs “Error is StripPacketOnInput(): 8020: Error reading comm device”
For Windows 7 embedded PCs, roll back the COM port drivers in device manager:

1. Click Start then enter “dev” into the search window then click the “Device Manager” icon.
2. Expand the “Ports” section then double-click “Nuvoton Communications Port (COM1)”
3. Click the Driver tab then click “Roll Back Driver” which should revert to the Microsoft 6/21/06 driver.
4. When finished, restart the PC.

"No RVM response to RSTART" is displayed
[added 8/9/04]: The RVM program is probably corrupted. You can attempt to force-load the software to the RVM. 
If the RVM is unable to communicate:
Pull memory chip U26 on the lower-left of the RVM controller board for a few seconds (note: this will erase all the RVM accounting data).
Attempt to force-load the RVM software again. If the same RSTART error is given after the RVM software (cf1500.img) is loaded, this may indicate the cf1500.img on the hard disk is corrupted. Overwrite c:\cf1500\cf1500.img with a good copy and try the force load again.

"No RS-485 card detected" error displayed when using RS-232 to RS-485 converter box
[added 10/1/01] Make sure you're using SC version 1.48 or later. Edit SC_CTRL.PRM to make sure RS485PORT parameter is set to the COM port where the converter box is connected to (6 for COM1 or 7 for COM2). If the error still occurs this indicates the COM port selected is bad/not found.

"No RS-485 card detected" error displayed when using Quatech DS-200/300 card
[added 11/8/01] Make sure the left-most jumper (SP) of J9 is ON to enable the scratchpad register. See sc_pc.txt for details.

An "SC02:No RVM Response to CRC Query" error is sometimes logged.
[added 3/13/00] There is a known bug with RVM versions prior to 3/13/2000 that will cause this error message under the following condition: If the cabinet door is shut and the RVM's reject chute sensor is blocked. This bug only appears to affect glass/PET RVMs.

A "W150: Command to RVM Invalid" is logged for each RVM when the Site Controller program is started.
[added 10/8/99] This usually indicates that an old version of RVM software is being used with a new version of Site Controller software or vice versa.
However, if using a version of RVM software after 7/22/99 and Site Controller software (1.38 or earlier), this is a known problem, this message can be ignored; there are no ill effects. Use a newer version of Site Controller software to eliminate this warning message. This message occurs because the SC sends a "VIEWAD:OFF" message to the RVM; "VIEWAD" support was removed from the RVM software on 7/23/99.

Unknown RVM messages such as "steel ratio=0, al=0, steel=0", etc. are logged.
[updated 10/8/99]  The RVM was left in the "VIEWAD:ON" debugging mode. Just reboot the site controller to turn this mode off if using SC1500 ver 1.38 or earlier, otherwise, you'll have to manually send the "VIEWAD:OFF" command to the RVM via the console/cons485 program.

The RVM’s RS-485 port address occasionally gets reset to "?".
This problem occurs when two RS-485 devices are trying to drive the line at once (can happen when two RVMs are programmed with the same port address) or when one or more RVMs are daisy-chained together but set to RS-232 mode instead of RS-485.

This can also be caused by a bad RVM controller board or a bad cable (not necessarily the RVM that is having the problem!). Check to see if chips at U46 and U47 (RS-485 drivers) are hot to the touch in every RVM, is so, they are probably blown up from a power surge (replace RVM board).
Note: Monitor ROM ver 4/15/98 and later prevent this from occurring.

The site controller won’t load an RVM with software.
Run console/cons485 to see if the RVM will communicate (press Enter, the RVM should respond with "ALERT_:150"). If it does, check the CRCs via F7 (REQUST:CRC). The RVM will report "RVMCRC:xxxx;yyyy"; if xxxx=0000 then a known bug in the site controller is not allowing the RVM software to load.

Note that the following procedure will lose all accumulated accounting data contained in the RVM! Fix by pulling the RAM chip or running console and changing memory location 20:0 to 01 (DEBUGR, M 20:0).

The site controller won't load barcodes to an RVM.
[added 8/6/01]: Make sure the RVM serial number matches the entry in SCSETUP.

When RVM is powered down, it always loses it’s port address.
Check the RVM battery voltage. Make sure the battery jumper is installed correctly. Reload the software. Move the RS-485 card in the PC to a different slot.

A "no response to REBOOT" error is displayed on the PC after new RVM software is loaded to the RVM.
[added 2-3-2000] Check the date/timestamp and size of the RVM program on the PC (cf1500.img or mu2000.img). If the size or date of the file is different than what the official software release document indicates, then the RVM program has been corrupted and is unusable. Get a good copy of the RVM program and reload the software. 
CAUTION! Never edit the RVM program with an editor. Simply opening the program in an editor and resaving the file will alter the RVM program, as the RVM program is a binary file and most editors will misinterpret/add line-feeds, carriage-returns, etc. when the file is saved.
If you want to force the RVM program to reload:
1. If using a Site Controller, press alt-L and follow the on-screen instructions.
2. If using PCRVM, simply select "update RVM program" from the menu.

MU2000 RVM on Port 5 doesn’t communicate.
If the PC is Pentium-based, the CMOS setup must be set up properly to allow interrupt 15 to be used by the SC software:

  • Disable the on-chip secondary PCI IDE from the integrated peripherals menu. 

  • Assign IRQ-15 to legacy ISA from the PNP/PCI configuration menu.

 
 

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