3M™ Parking Troubleshooting Manual Version 1 Safety Notice CAUTION! To reduce the risk of severe personal injury or damage to equipment that may not be covered by warranty, turn off the power to the equipment before performing any maintenance or repairs. − Failure to heed this warning could result in injury or even death of those who come in contact with the product − Failure to turn off the power before performing any maintenance or repairs may result in damage to the equipment that is not covered by the warranty. People’s lives and property depend on your safe installation of equipment. Listed below are some important safety instructions and precautions which you should follow when working on any 3M Company equipment. Failure to follow all safety precautions and instructions can result in serious injury or property damage. Refer to the specific operational manual for a particular piece of equipment before beginning any service work. Frequently inspect the equipment to ensure that it is operating properly. Ensure that maintenance is performed by the factory or an authorized distributor at least twice a year. Safety Hints Use vibrant colors on parking equipment at entrance lanes and exit lanes. Always provide proper signage, both on the roadway and on other equipment. Maintain the manufacturer’s warning stickers on gate arms and on other equipment. Encourage the use of safety devices such as buzzers or flashing lights. Always recommend that sidewalks be parallel to entrance lanes and exit lanes. Safety Notice Any activity in relation to entrance lanes and exit lanes should be monitored to ensure against accidental lowering or raising of barrier gates or manipulation of equipment so as to prevent injury of pedestrians, maintenance personnel, persons on bicycles or motorcycles. Take special care when commanding any equipment action from a centralized computer system, especially when the control equipment is not in your line of vision. Use Pictograms 3M strongly recommends that you use universally identifiable icons, or pictograms, in all entrance lanes and exit lanes, roadways, posts and walls. It is also recommended that a “No Pedestrian” pictogram be painted on the roadway immediately adjacent to a parking barrier gate. Pictograms depicting “No Motorcycles,” “No Wheelchairs,” “No Bicycles,” and “No Trucks” are also recommended. Safety Is Good Business As an institution, municipality, or private operator, it is important to be aware of the potential liabilities which may arise in normal parking operations. Adopting a “Safety First” attitude will provide your business and your patrons with a safer environment. After all, safety is good business! COPYRIGHT Troubleshooting Manual 78-0060-4094-9, Ver. 1 ©2013 3M Company. All rights reserved. All materials in this document are protected by copyright law and international treaties. Materials contained in this document are confidential and/or trade secrets of 3M Company. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, without the written permission of 3M Company. Manual Version 1 3M v1 Date February, 2004 August, 2013 Contents ACT..................................................................................................................................... 1 Automatic Cashiering Terminal Paper Roll Relief Notch for Seiko/Citizen Printers .... 1 ACT Receipt Door Modified .......................................................................................... 1 Expansion Board for Serial Ports 5 through 8 ................................................................ 1 Serial Port Config Options for Automatic Cashier Terminal ......................................... 2 Axiohm Printer and Controller Board Obsolete ............................................................. 3 Editing Configuration Chips ........................................................................................... 3 Axiohm DIP Switch Settings and Wire Connections for ACT....................................... 7 ACT or CCXV Fee Display Common Troubleshooting................................................. 7 Device Addresses Stuck on Zero .................................................................................... 8 PowerPad Power Supply Revision E2 and Older Not Suitable for Upgrading to ACT or MG-1500 Spitter or Exit Verifier ................................................................................... 8 Upgrade Instructions for multiple characters on ACT, APS, MG-1500 Spitter and Exit Verifier, SST Ticket Spitter and Exit Verifier, Display 82-20059 ................................. 8 Version C3.6.1.3 ........................................................................................................... 14 Version C3.6.0.11 ......................................................................................................... 15 APS ................................................................................................................................... 17 Updating the Mars Bank Note Acceptor to Accept New Bills ..................................... 17 Sodeco Support Tool Installation, Programming and Utility Instructions ................... 17 PowerPad and APS Keys Making Noise, but not Performing Function....................... 49 Device Address Stuck on Zero ..................................................................................... 50 CashCode Instead of Mars ............................................................................................ 50 APS Not Spitting Notes ................................................................................................ 51 Editing Configuration Chips for Auditor PowerPad, Automatic Pay Station, Credit Card Exit Verifier, Automatic Cashier Terminal, and MG-1500/ML-3500 Spitter ..... 51 Automatic Pay Station: Switch Replaced ..................................................................... 51 Pre-Pay Option for the APS .......................................................................................... 52 General Information ...................................................................................................... 52 Common Troubleshooting ............................................................................................ 53 Not Asking Cash Amount When Reinserting Note Dispenser ..................................... 54 Stopped Taking Bank Notes ......................................................................................... 54 Program to Pull Reports ................................................................................................ 55 Language Changed to Italian ........................................................................................ 55 Axiohm Receipt Printer DIP Switch Settings and Wire Connections .......................... 55 Sodeco Support Tool/HyperTerminal ........................................................................... 55 Note Validator Variant First Thing Loaded After Cold Start ....................................... 56 BNA 51 and 52 Series Note Acceptors Discontinued .................................................. 57 Output 5/Voice Annunciation ....................................................................................... 57 Version C4.0.1.5 ........................................................................................................... 57 Version C3.6.1.3 ........................................................................................................... 57 Version C3.6.0.11 ......................................................................................................... 57 Version B3.3.2.0 - New Config Chip Required when Upgrading ................................ 58 Platforms B and C prior to C.3.3.0.2/Facility Codes above 512 .................................. 58 Troubleshooting Manual 78-0060-4094-9, Ver. 1 • i Version C3.2.0.2 ........................................................................................................... 58 Version 3.2.0 ................................................................................................................. 58 Version A1.8.0 .............................................................................................................. 59 CF-803i ............................................................................................................................. 61 CF-803i: English 7.1.34UN and Spanish 7.1.34EN ..................................................... 61 CCEV (Credit Card Exit Verifier) .................................................................................... 63 Version C2.8.1.4 ........................................................................................................... 63 CCEV Serial Expansion Board ..................................................................................... 63 Crossover Exit Verifier DIP Switch Settings................................................................ 63 Programming Crossover Exit Verifiers ........................................................................ 63 Gate ................................................................................................................................... 65 Gates Tips & Tricks ...................................................................................................... 65 Type of Motor Oil for Gate Reducer ............................................................................ 65 G-90 LCD Config Module, “No Config” Message ...................................................... 66 New Flash Omega Controller ....................................................................................... 66 Troubleshooting Loop Detection for a G-90 CD Gate ................................................. 66 I am getting erroneous transient backward and illegal forward messages from gates installed in a parking deck structure. What could be causing this? .............................. 67 Why does my Reversing lane constantly show “illegal reverse” or “illegal forward” and generate inaccurate lot counts? .............................................................................. 67 The Gate Arm is Stuck in the Up Position. What should I do? .................................... 67 Motor Troubleshooting ................................................................................................. 68 Loops vs. Frequency ..................................................................................................... 69 G89 Gate-I am using an MP-6000 (black box). When a car vends the gate while on loop B, the arm goes up about 6 inches, and comes right back down. If the patron holds the card in the reader, it will eventually vend. Is there something I can check? .......... 69 Lane Troubleshooting ....................................................................................................... 71 Troubleshooting Loop Detection for a G-90 LCD or CD Gate. ................................... 71 TD-249 to CD gate........................................................................................................ 71 LCD or CD gate/Passport Plus Card reader/No arming. .............................................. 73 LCD or CD Gate ............................................................................................................... 77 Basic Inputs and Outputs .............................................................................................. 77 Not Reading Config Module ......................................................................................... 77 Cold-starting the Omega Controller in the G-90 CD Gate ........................................... 78 Using EDC-1000 to Stop Free Gate from Vending When Desired Count is Reached . 78 Multiple Readers Operating from One Built-in Power Supply on the G-90 CD Gate . 78 Warning Labels ............................................................................................................. 79 Circuit Board Redesigned ............................................................................................. 79 Losing Programming Powering the LCD/CD Gate ...................................................... 79 Master/Slave CD Gate .................................................................................................. 79 Omega Displays only Black Bars ................................................................................. 80 LCD Gate: Loop Detector not Resetting after Tailgate ................................................ 80 CD Gate Introduction.................................................................................................... 80 Rebound Circuit ............................................................................................................ 81 LCD/CD B Platform Omega Communication Wave Forms ........................................ 82 LCD/CD C Platform Omega Communication Wave Forms ........................................ 83 ii • 78-0060-4094-9, Ver. 1 Troubleshooting Manual Omega Version C3.0.5 and B2.4.8/No Config Mode Problems ................................... 83 Version B2.4.7 and C3.0.4 ............................................................................................ 84 Version C3.0.1 .............................................................................................................. 84 Version B2.6.0 .............................................................................................................. 84 Version B2.1.2 .............................................................................................................. 84 Version B2.1.1 .............................................................................................................. 84 Version B2.1.0 .............................................................................................................. 85 Base Mode 5 Sub Mode 1 Does Not Work................................................................... 85 Mode DIP Switch Settings ............................................................................................ 86 Omega Controller Counts Option ................................................................................. 87 Lane Troubleshooting TD-249 Barcode Ticket Spitter and G-90 CD Gate ................. 88 Lane Troubleshooting Passport Plus Card Reader and G-90 CD Gate ........................ 90 LD-23 ................................................................................................................................ 93 I have an LD-23 loop detector, and it is not working correctly. Is there some troubleshooting I can do in the field? ........................................................................... 93 LPI..................................................................................................................................... 95 New LPI Hand Held Computer With 10K Capacity .................................................... 95 Here are some notes to keep in mind when using the new LPI HHC. .......................... 95 Scan NT Update: License Plate Inventory .................................................................... 96 Receiving an “LPI PORT OPEN” Message ................................................................. 96 When I try to print a report showing the LPI inventory, I get an Error 1000: field (inv.plate) cannot be a 0 length string. .......................................................................... 96 Netport ............................................................................................................................ 103 Introducing the NetPort............................................................................................... 103 NetPort Features.......................................................................................................... 103 NetPort Passback Control Feature .............................................................................. 103 Primary Area Control/with 100K readers ................................................................... 104 Editing Port Controller Info ........................................................................................ 104 Netport Changes.......................................................................................................... 104 NetPort Programming Instructions ............................................................................. 105 Setting NetPort Addresses .......................................................................................... 106 Version A2.2.4 ............................................................................................................ 106 Version A2.2.3 ............................................................................................................ 106 Passport 360 .................................................................................................................... 107 Version 1.1.2.4 ............................................................................................................ 107 PDA Software 1.3 ....................................................................................................... 107 Dyna III A2.3.1 ........................................................................................................... 107 PDA to Passport 360 Serial Connection ..................................................................... 107 Replacing Passport Plus .............................................................................................. 109 How can I program the Passport 360 reader? ............................................................. 109 Introducing the Passport 360 Card Reader System..................................................... 109 General Information .................................................................................................... 110 Version 1.1.1.3 ............................................................................................................ 110 PDA Software 1.2 ....................................................................................................... 110 PDA Software 1.1 ....................................................................................................... 111 Passport Plus ................................................................................................................... 113 Troubleshooting Manual 78-0060-4094-9, Ver. 1 • iii 27128A EEPROM Obsolete ....................................................................................... 113 Downloading Firmware/Which Systems Matches the Firmware ............................... 113 Programming Universal Track 2 Reader .................................................................... 113 Universal Track 2 reader not reading or showing Alien Card .................................... 114 Programming for TagMaster AVI Read Head ............................................................ 114 AWID Prox reader MR-1824 Inconsistency In Read Range ...................................... 114 Wiring for HID Read Head ......................................................................................... 114 Wiring for Amtech Read Head ................................................................................... 115 Wiring for Motorola Card Read Head ........................................................................ 115 Programming CASI-RUSCO Cards ........................................................................... 115 Card Data Configuration for Weigand Read Heads ................................................... 116 Card Data Configuration for Bar Code Read Heads ................................................... 117 Getting Errors Programming Series Readers .............................................................. 117 Passport Plus D-Type Firmware Shows as Door Reader............................................ 117 Passport Plus Product Line Discontinued ................................................................... 118 Passport Plus Expansion Boards ................................................................................. 118 Upgrade Dyna II to a Dyna III .................................................................................... 119 Passport Plus Losing Memory .................................................................................... 119 Series-16 with Prox Readers ....................................................................................... 120 PC Control over Host-Based Cards ............................................................................ 120 Resync Explanation .................................................................................................... 122 Card Readers Showing Up as Door Readers .............................................................. 122 ScanNet Not Locking Out Standard Credentials with Group Control ........................ 122 Nesting Area Reader Type .......................................................................................... 123 Keypad Programming ................................................................................................. 123 Weather Striping ......................................................................................................... 125 Passport Plus reader setup as displayed in Sybase Central ......................................... 125 Universal Track 2 and Standard Logic A3.3.0 ........................................................... 125 Posting Reader A1.8.6 ................................................................................................ 125 Host-Based Logic A1.2.5 & A3.4.5/Series 16K A3.4.5 ............................................. 126 Host-Based Logic A3.4.5............................................................................................ 126 Host-Based Logic 3.4.2............................................................................................... 126 Host-Based Logic A1.2.1/Series 8K & 16K Host-Based Logic A3.4.1 ..................... 126 Series 100K Logic A1.9.2 ........................................................................................... 127 Series 16K Logic A1.9.1 ............................................................................................. 127 Series 100K Logic A1.8.1 ........................................................................................... 127 Standard Logic D3.3.1 not vending the output (remotely or by card) ........................ 127 Standard Logic A3.3.1 ................................................................................................ 127 Standard Logic A1.9.0/Series 100K Logic A1.9.1 ..................................................... 127 Standard Logic May 1999........................................................................................... 128 Dyna 3 Read Head A2.2.0 .......................................................................................... 128 Lane Troubleshooting Passport Plus Card Reader and G-90 CD Gate ...................... 128 Codes for D Type Firmware ....................................................................................... 130 Host-Based Logic D3.4.5/Host-Based Series 16K D3.4.5 ......................................... 130 Series 16K D1.9.2 and Series 24K D1.9.3 .................................................................. 130 Standard Logic D3.3.2 ................................................................................................ 131 iv • 78-0060-4094-9, Ver. 1 Troubleshooting Manual Standard Logic D3.3.1 ................................................................................................ 131 Port Controller ................................................................................................................ 133 B1.8.7 Hides "Enter Retry Mode" Message ............................................................... 133 27128A EEPROM Obsolete ....................................................................................... 133 Getting Non-existent Devices after Replacing the Port Controller ............................ 133 Port Controller 2MHz Processor................................................................................. 133 Editing Port Controller Information............................................................................ 134 Pin-out Between Port Controller and Computer ......................................................... 134 Port Controller Upgrade .............................................................................................. 134 Version B1.8.6 ............................................................................................................ 134 Version B1.8.5 ............................................................................................................ 135 Version B1.8.3 ............................................................................................................ 135 Version B1.7.5 & 100k Version B1.8.1 ...................................................................... 135 PosiDRIVE ..................................................................................................................... 137 Three Position Door Safety Switch............................................................................. 137 Balancing the Gate Arm.............................................................................................. 137 Version 1.2.1/Backout Timer ...................................................................................... 138 Warning Labels ........................................................................................................... 138 Improved Gate Arm Design ........................................................................................ 138 PosiDRIVE Gate Heaters Discontinued ..................................................................... 139 New Mainspring.......................................................................................................... 139 Gear Box Lubricant..................................................................................................... 139 Arm of PosiDRIVE Gate Does Not Raise When Power is Lost................................. 139 Wiring Red/Green Light ............................................................................................. 140 Version 1.1.1 ............................................................................................................... 140 PowerPad ........................................................................................................................ 141 “Ticket Jam” Message When Ticket is Inserted Into Validator ................................. 141 Merchant (Hole-Punch) Validator Setup .................................................................... 141 Merchant (Hole-Punch) Validator Which ID Should a Particular Store Get.............. 141 Merchant (Hole-Punch) Validator Cashier Accidentally Validates Ticket in Zone that was Already Used ....................................................................................................... 142 Merchant (Hole-Punch) Validator Ticket Inserted Wrong Way................................. 142 Merchant (Hole-Punch) Validator Location of Holes on Ticket Matching Account Number ....................................................................................................................... 142 Editing Configuration Chips ....................................................................................... 144 Credit Card Clearing Houses for Datacap DataTran POS System ............................. 147 CPU Error Messages ................................................................................................... 148 PowerPad Fee Computer Tips and Tricks .................................................................. 149 Updating C-3 fee Display from Auditor II to PowerPad ............................................ 150 "Lost not Active" Message When Entering Date and Time for Lost Tickets ............. 150 Clearing Memory on New PowerPads ........................................................................ 150 CCXV Fee Display or ACT Fee Display Common Troubleshooting ........................ 150 Reduced Exit Time Account Validation ..................................................................... 151 Auto Rate Feature ....................................................................................................... 151 PowerPad: MC3486 Receive IC ................................................................................. 151 PowerPad Display Shows Correct Characters but Wrong Spacing ............................ 152 Troubleshooting Manual 78-0060-4094-9, Ver. 1 • v SST PowerPad Ticket Validator Power Supply.......................................................... 152 Desktop Fee Display Communication ........................................................................ 152 PowerPad Currency Exchange Feature ....................................................................... 152 C Platform PowerPad Memory I/O Expansion Board ................................................ 153 PowerPad Expansion Board Problem ......................................................................... 153 Differences Between Paid and Unpaid Grace Time ................................................... 154 Validated Tickets to Vault .......................................................................................... 154 Printer Continuously prints “******257*****date/time.”......................................... 154 Maximum Number of Cashiers Logged On at One Time........................................... 155 Customize Financial Reports ...................................................................................... 155 “Ticket Being Printed” Message Shows When No Ticket is Present ......................... 156 Clearing Cash Reports ................................................................................................ 157 Alternative Use of Repay Feature ............................................................................... 157 Credit Card Point-of-Sales Equipment Collects Parking Fees ................................... 158 Clearing the YTD Lane Report ................................................................................... 159 PowerPad Internal DIP Switches ................................................................................ 160 PowerPad Not Vending Gate ...................................................................................... 160 PowerPad Not Vending Drawer.................................................................................. 161 Deciphering the Journal Tape ..................................................................................... 163 Keys Making Noise but Not Performing Function ..................................................... 163 Device Address Stuck on Zero ................................................................................... 164 Power Supply Revision E2 and Older Not Suitable for Upgrading............................ 164 Buffered Transactions ................................................................................................. 164 SRAM Added to Assembly ........................................................................................ 164 Credit Card Vouchers ................................................................................................. 165 Can I use B Platform Firmware in a C Platform Board? ............................................ 165 Using Version C Firmware on B Platform PowerPads ............................................... 165 A Platform Versus B platform Firmware.................................................................... 165 Upgrading the PowerPad ............................................................................................ 166 Version C4.1.0.3 ......................................................................................................... 167 Version C4.0.0.21 ....................................................................................................... 168 Version C4.0.0.20 ....................................................................................................... 168 Version C3.8.0.19 ....................................................................................................... 170 Version C3.6.0.11 ....................................................................................................... 170 Version B3.3.3 ............................................................................................................ 170 B2.4.0 Switching to Central Cashiering ..................................................................... 171 Version B2.3.0 ............................................................................................................ 171 Version B2.3.0 Switching from Exit Mode to Central Mode for a Single Transaction ..................................................................................................................................... 171 Version B2.0.1 ............................................................................................................ 171 Version A1.8.5 & A1.8.6 ............................................................................................ 172 Version A1.8.2 ............................................................................................................ 172 Version A1.7.7 ............................................................................................................ 172 Version 2.2.0 ............................................................................................................... 172 Version 2.0.1 ............................................................................................................... 172 Version 1.8.7 ............................................................................................................... 173 vi • 78-0060-4094-9, Ver. 1 Troubleshooting Manual RC2 ................................................................................................................................. 175 Introducing the RC2 Ramp Controller ........................................................................ 175 Version 1.0.0.15 .......................................................................................................... 176 SCAN DOS ..................................................................................................................... 177 Why does my SCAN DOS system take so long to retrieve information from the SCAN Data Manager? ............................................................................................................ 177 Our SCAN DOS was off-line for awhile, and I don’t want to print out all of the messages during that time. How do I clear the buffer?............................................... 177 I have one device on my SCAN System that intermittently drops offline and then comes back online. What should I check for? ............................................................ 177 Is it possible to run SCAN in Windows? .................................................................... 178 Is it possible to run SCAN DOS with Windows 2000? .............................................. 178 Working With the SCAN DOS Backup Utility .......................................................... 178 Setting Hot Keys ......................................................................................................... 179 ScanNet ........................................................................................................................... 181 Problem Checkpoint setting up ScanNet Server/Client .............................................. 181 SCPMKILL - manually shutting down ScanNet ........................................................ 182 ScanNet Multi-level Security Reset Program ............................................................. 182 Using SQL Statements to Delete Data in ScanNet ..................................................... 182 ScanNet 5.1.2.11G ...................................................................................................... 183 CreateDsn.exe ............................................................................................................. 183 Importing Data to Microsoft Excel 2000 .................................................................... 184 Posting Reader Programming for ScanNet 5 .............................................................. 184 Using ScanNet ScanUpdate.exe.................................................................................. 187 Automatically Bill and Print using Billing and Invoicing .......................................... 188 Running ScanNet on Microsoft Windows XP ............................................................ 188 Navigator Showing Only a Blue Bar .......................................................................... 188 Saving PowerPad Programming Files ........................................................................ 189 Generate an Invoice for No Activity........................................................................... 189 ScanNet 5.1.1.5G ........................................................................................................ 189 ScanNet 5.0 ................................................................................................................. 191 CAMP Shuts Down when Central Only Cards are Used for the First Time at an Exit Reader in ScanNet 5.0.0.33......................................................................................... 195 ScanNet 4.6.6.8 ........................................................................................................... 196 Internet Explorer Requirements For ScanNet ............................................................. 196 ScanNet Serial Numbers ............................................................................................. 197 ScanNet Database Archiver ........................................................................................ 197 Duration by Ticket and Grace Exit Reports................................................................ 243 Central Credit Card ..................................................................................................... 243 Prevent Accidental Shutdown of Sybase/Hide SQL Icon........................................... 244 I deleted a standard credential from the Access Control System (ACS), but the reader still lets the patron into the lot. Why? ......................................................................... 244 PC Requirements for ScanNet .................................................................................... 244 Device intermittently drops offline and comes back online ....................................... 245 Access Duration Report .............................................................................................. 246 Saving database report parameters do not show at the client computer ..................... 246 Troubleshooting Manual 78-0060-4094-9, Ver. 1 • vii Last Card Report ......................................................................................................... 246 Cardlog Conversion .................................................................................................... 246 ScanNet 4.4.2.2 Security............................................................................................. 247 ScanNet prior to 4.4.1.10 getting message “Error 94 invalid use of null” when patrons exit the facility ............................................................................................................ 247 Using a ScanNet server/client setup, when you re-boot the client computer, you cannot connect to the Server computer................................................................................... 248 Scan NT not able to pull Statistics report using macro............................................... 248 Network Interface Connection (NIC) card ................................................................. 248 Receiving errors bringing up agent since loading Scan NT ....................................... 248 Credential Options and set up ..................................................................................... 249 ScanNet Not Locking Out Standard Credentials with Group Control ........................ 250 Scan NT/Sybase 5.0 .................................................................................................... 250 Loading Microsoft Office 2000 on a ScanNet PC ...................................................... 250 System Activity Report: Passback Messages ............................................................. 251 Avoid Unwanted “Door Readers” in ScanNet ............................................................ 251 Searching Credentials ................................................................................................. 251 Updating from Scan NT Versions to a ScanNet Version ........................................... 252 Updating the Database ................................................................................................ 252 Two SQL Statements Available to Copy ID Fields to Name Fields for ScanNet ...... 252 Facility Codes and Credential IDs .............................................................................. 253 Installing ADS Link Version 3.1 ................................................................................ 253 Setting Up Central Access credentials with Billing and Group Control .................... 260 What are some common Sybase SQL statements? ..................................................... 275 How To Set Access Control System With the Same Password As ScanNet .............. 279 Required Update for Central Credit Card ................................................................... 280 Database Does Not Appear to be for ScanNet 4.0.0 or Later Message When Updating Database ...................................................................................................................... 280 Scan NT Update: Subscription Plan, Version 2.0 & Version 3.0 ............................... 281 Things wrong with ScanNet 4.4.1.10.......................................................................... 283 Version 4.6.3.6 ............................................................................................................ 283 Version 4.6 .................................................................................................................. 284 Versions 4.4.2.2 and 4.5.0.14...................................................................................... 285 Version 4.4.1.10 .......................................................................................................... 286 Version 4.4.0.21 .......................................................................................................... 287 Version 4.4 .................................................................................................................. 287 Version 4.3 .................................................................................................................. 288 Scan NT 4.0 ................................................................................................................ 289 Scan NT 3.2 ................................................................................................................ 296 Scan NT 3.1.1.5 .......................................................................................................... 297 Scan NT 3.1.1 ............................................................................................................. 298 Scan NT 3.1.0.6 default user name and password not allowing access to ACS ......... 298 Scan NT 3.1.0 ............................................................................................................. 298 Scan NT 3.0 ................................................................................................................ 299 Scan NT 2.0 ................................................................................................................ 300 SST.................................................................................................................................. 301 viii • 78-0060-4094-9, Ver. 1 Troubleshooting Manual SST CPU DIP Switch Settings ................................................................................... 301 Troubleshooting SST Equipment ................................................................................ 301 SST Ticket Spitter display showing "NOT IN OPERATION" .................................. 302 Differences Between Paid and Unpaid Grace Time ................................................... 302 SST HP-1 and SST HP-4 Transports Improved to Increase Life of Print Head ......... 303 Fix For Abnormal Display .......................................................................................... 303 SST Media Specs ........................................................................................................ 304 Version 12 Transport Repairs ..................................................................................... 305 SST HP-1 Versus SST HP-4 ....................................................................................... 305 Setting Low Ticket Number in SST Spitter ................................................................ 305 SST Re-encode Option for Ticket Spitters ................................................................. 306 Fastest Ticket Issue Speed .......................................................................................... 307 Transient Facility Code ............................................................................................... 307 SST Tickets Stick Together When Issued Causing Jams ........................................... 309 Printing Small Fonts ................................................................................................... 309 SST Merchant Validator ............................................................................................. 309 Introducing the SST HP-4 Transport .......................................................................... 309 Introducing the SST HP-1 Transport .......................................................................... 310 Single Infeed Burster: Version A................................................................................ 311 Sunlight and SST Transport Failure ........................................................................... 311 SST Configuration ...................................................................................................... 312 Omega LCD and SST Omega Standard - Circuit Board Redesigned ......................... 312 Flash Omega Controller .............................................................................................. 312 SST Merchant Validator-SST/HP-1 versus SST/HP-4 ............................................... 312 SST CPU Version A4.0.10 Mandatory Firmware Upgrade ....................................... 313 What is the 24VDC Power Hookup between the SST CPU of the Validator and the PowerPad Power Supply? ........................................................................................... 314 SST CPU Firmware Compatibility ............................................................................. 314 How can you adjust the print head for a HP-1 or HP-4 Transport? ............................ 315 SST CPU 3/1999 ......................................................................................................... 315 SST Omega VC/CC C3.2.2 ........................................................................................ 315 SST Omega Standard C3.1.8 ...................................................................................... 316 SST Omega VC/CC C3.1.5 and B2.6.5 ...................................................................... 316 SST Omega Standard and VC/CC C3.1.1 .................................................................. 316 SST Omega VC/CC C3.0.1 & CCEV B2.5.1 ............................................................. 316 SST Omega Standard B2.2.0 ...................................................................................... 317 SST Omega Standard B1.13.0 .................................................................................... 317 SST Omega VC/CC B2.1.1 ........................................................................................ 317 SST Omega VC/CC 1.1.2 or Previous Losing ValueCard Programming .................. 317 Field Wiring Troubleshooting for All SST Spitters with Push Button ....................... 317 TagMaster ....................................................................................................................... 320 How do I program the communication and Wiegand card format settings for the TagMaster AVI read head? ......................................................................................... 320 TagMaster Error in Labeling J5 .................................................................................. 320 TD-249 ............................................................................................................................ 323 Lane Troubleshooting TD-249 Barcode Ticket Spitter and G-90 CD Gate ............... 323 Troubleshooting Manual 78-0060-4094-9, Ver. 1 • ix Manual Issue ............................................................................................................... 325 Tickets not Cutting Clean ........................................................................................... 325 More than One Ticket Issued ...................................................................................... 325 Issuing Long Tickets ................................................................................................... 325 Tickets Jamming in the Chute..................................................................................... 325 Feed Motor Continues to Run/No Ticket is Cut ......................................................... 326 Ticket not Cut in Proper Location .............................................................................. 326 Time Stamp Gains Time and does not Match Hands on Clock Face ......................... 326 Time Stamp Loses Time or Stops ............................................................................... 326 Blurred Time Stamp on Tickets .................................................................................. 327 Not Time Stamping Tickets ........................................................................................ 327 Time Stamp is Weak or Doubled ................................................................................ 327 Prevent Ticket Jams Caused by Patrons Blocking Ticket Throat ............................... 327 Not Cutting Tickets Completely/Tickets Folding Over Blade ................................... 328 Installing an LCD Display .......................................................................................... 328 Ticket Delays .............................................................................................................. 328 Using the Recall Key on the PowerPad During Processing ....................................... 328 Version A3.3.1 ............................................................................................................ 329 Version A3.3.0 ............................................................................................................ 329 TD-300 Series ................................................................................................................. 331 Firmware Upgrades..................................................................................................... 331 Tickets Jam Before Rotary Cutter............................................................................... 333 Tickets Shoot Out Spitter and Appear to be Ripped, Not Cut .................................... 333 One Motor Continues Spinning With no Ticket in Mechanism ................................. 333 No Printing on Ticket.................................................................................................. 334 Service Mode Tickets do not Vend Gate at PowerPad Exit ....................................... 334 Cap on Thermostats .................................................................................................... 335 Using LEDs to Test Sensors with the Guillotine Type Cutter .................................... 336 Transport Enhanced to Support Guillotine Type Cutter ............................................. 336 LED Display Board Rev B Versus Rev C .................................................................. 336 Signs Replaced by Symbols ........................................................................................ 337 Hardware Changes ...................................................................................................... 337 Ticket Deflector Introduced ........................................................................................ 337 Better Patron Access to Ticket.................................................................................... 337 Change Prevents Lost Springs .................................................................................... 337 Quality Control Checklist ........................................................................................... 338 Hecon Twin Cutter Enhancement ............................................................................... 338 Tickets Difficult to Pull Once They Are Issued.......................................................... 339 Enhancements ............................................................................................................. 340 Retracted Ticket Hopper ............................................................................................. 340 Que Belt Not Spinning ................................................................................................ 340 What are some commonly used parts and part numbers for the TD-300 Spitter? ...... 341 Using LEDs to Test With Rotary Cutter ..................................................................... 341 Paper Clippings ........................................................................................................... 342 ValueCard ....................................................................................................................... 345 Example: ValueCard programming at PowerPad ....................................................... 345 x • 78-0060-4094-9, Ver. 1 Troubleshooting Manual Example: ValueCard Programming at the Spitter Omega .......................................... 349 Sending ValueCard Programming from ScanNet ....................................................... 350 Exit Gate Does Not Vend When You Use ValueCards .............................................. 350 Validated Transient Tickets to Vault/ValueCard Tickets Returned ........................... 351 Version B1.1.2v .......................................................................................................... 351 Introducing the ValueCard System ............................................................................. 351 ValueCard Misunderstandings .................................................................................... 353 ValuePass ........................................................................................................................ 355 Creating ValuePasses offline ...................................................................................... 355 Calculating Central Access/ValuePass Credentials .................................................... 355 Minimum programming for ValuePass ...................................................................... 355 Other Questions .............................................................................................................. 356 Transmit and Receive ICs ........................................................................................... 356 What to Check if Your Site has a Lightning Strike .................................................... 357 Approved Ticket Vendors ........................................................................................... 357 Customer Requested Ship Date .................................................................................. 358 E-mailing SRO Requests ...............................................Error! Bookmark not defined. Running Intercom Wiring Next to the Communication Wiring ................................. 359 New Warranty Exchange Procedure ........................................................................... 360 Product Support Policy for Handling Calls ................................................................ 360 Universal Power Supply Assembly ............................................................................ 360 E-mail Order Verification Process .............................................................................. 360 DIP Switch Settings for Printers ................................................................................. 361 Message buffer sizes for SST Spitter Omegas, Port Controller, Passport Plus, LPI Workabout Handheld, and the ScanNet Central Credit Card. .................................... 362 3rd Party Safety Certification ..................................................................................... 362 Shipping Overnight with UPS Red ............................................................................. 364 ROM Burner for Downloading Firmware .................................................................. 364 Demo Copy of ScanNet .............................................................................................. 365 Parking Jargon ............................................................................................................ 365 Finding Firmware Versions ........................................................................................ 365 LED Fee Display Introduced ...................................................................................... 366 Y2K Compliant Firmware Versions ........................................................................... 366 Prevent Your Warranty From Becoming Void by Shipping Parts Correctly ............. 366 Index ............................................................................................................................... 368 Troubleshooting Manual 78-0060-4094-9, Ver. 1 • xi Note: This manual may reference legacy part numbers and product names. Please refer to the 3M Parking Price Book for current product names or contact your customer service representative with questions. ACT Automatic Cashier Terminal Paper Roll Relief Notch for Seiko/Citizen Printers As a result of the higher paper roll assembly on the new Seiko/Citizen printers, a relief notch has been added on the front flange of the ACT cover to allow the cover to be installed and removed easily. ACT Receipt Door Modified To prevent the door from blocking a patron’s access to the receipt, 3/16” was removed from the bottom of the receipt tray door. Expansion Board for Serial Ports 5 through 8 The PowerPad comes with four serial ports that are defined by the configuration chip. You can view these definitions at the PowerPad by choosing Programming>System Preferences>Config Options>Serial. If you require more than four ports, use a PowerPad expansion board to give you access to ports 5 through 8. You will require more than four ports in the following cases: * You have a DataCap credit card system and a desktop fee display. * You have an ACT with a second Transport. If you have a DataCap credit card system and a desktop fee display, use port 6 for the desktop fee display since you already use port 1 for DataCap credit card. When board. If you are not using a DataCap credit card system, and you are using a desktop fee display, the expansion board is not needed. Drive the display out of the credit card port 1, and use cable 91-11930 (cable, desktop fee display d) to connect the desktop fee display to the PowerPad itself. If you have an ACT with a second transport, use port 6 for the ACT transport. When using port 6 to drive the second transport, use cable 81-19733 (10’ cable, 10 pin to RJ11 ACT). Port 6 must be programmed in order to function with two transports; otherwise it must be unused. When using two transports, the ACT transport must be plugged into Port 6, and the Validator must be plugged into Port 3. If you plug the expansion board in and do not see the extra serial ports, then the Cypress chip on the expansion board needs to be programmed. When the Cypress chip is programmed at the factory, a sticker is attached to the Cypress chip. If the board is not programmed, send it back to have the Cypress chip programmed or contact Customer Service to have a programmed expansion board sent to you. Enable ports 5 through 8 by shunting pin 4 to 2 and pin 3 to 1, on the pins next to the plugs on the expansion board as shown in the example. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 1 If these shunts are not installed, the port that the shunts enable will not work. Serial Port Config Options for Automatic Cashier Terminal To view Serial Port Config Options for Automatic Cashier Terminal (ACT), at the device choose Programming> System Preferences>Config Options>Serial. Here is an example of Serial Port Config Options: Port ROM Explanation 1 Port 1 should only be set to CreditCard with DRV DataCap only if FUNC CreditCard you are using a networking Credit Card system. Otherwise, it is DRV DataCap unused. TYPE 2 FUNC PortComm This is set for communication to ScanNet. DRV PortComm TYPE 3 FUNC Readers DRV Transport TYPE 2 • ACT If there is only one transport in your setup, this port should be the only one defined and the ACT transport must be plugged into Port 3. If there are 2 transports in the system, the Validator must be plugged into Port 3, and the ACT transport must be plugged into Port 6. 78-0060-4094-9, Ver. 1 Troubleshooting Manual 4 FUNC DRV TYPE Printer Epson Tm930 rec: Y jrl: Y val: Y rpt:Y The ACT will not function properly unless you attach the Epson printer or you log on as Attendant 2 with Master status and set the System Preferences for the Printer as Journal, Receipt, Validator and Reports all programmed as “Operational.” If you try to program System Preferences>Printer while logged on as Attendant 1, you will not be able to program the Validator as “Operational.” 5 FUNC Printer Port 5 can also be used for FUNC Printer, DRV Citizen, rec: Y, DRV Seiko 2342 everything else unused (.). TYPE rec: Y jrl: . val: . rpt: . 6 FUNC Readers DRV Transport TYPE 7 FUNC Display DRV Cust Dsp TYPE 2X20: . 4X40: . all: . 8 FUNC Unused DRV TYPE Port 6 must be programmed in order to function with two transports, otherwise it must be unused. When using two transports, the ACT transport must be plugged into Port 6, and the Validator must be plugged into Port 3. This is for the desktop fee display. This port is unused at this time. Axiohm Printer and Controller Board Obsolete The Axiohm printer and controller that are currently designed into the ACT product line are obsolete. The bracketry has been redesigned to accommodate an 80 mm Seiko printer Model LTP2342C-S576. The Seiko printer requires 80 mm paper, which is different than the Axiohm paper. Editing Configuration Chips When working with these devices, you may view and print the options of the configuration (config) chip that has been made special for your site’s needs. The config chip 93C66 is located at U25 in the C Platform circuit board, and the config chip Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 3 1736EPC is located at U20 of the B Platform circuit board. At the device, choose Programming>System Preferences>Config Options>Config, and you will see the settings that have been burned into the config chip for your site. This is an example of an Auditor PowerPad config printout: Device APP* Attendants 200 Merchants 208 Merch Per Key 8 Merch Groups 26 Fee Tables 24 Stats Per Type 8 Taxes 6 Txn Buf Size 3940 Vouchers 208 Vouch Per Key 8 Vouch Groups 26 Exchange 0 Ticket Tracking Yes Keymap Qwerty YTD Clear Yes Barcode No Coin Validator No Coin Dispenser 0 Alt Payment 8 LPI Yes Tour Number 0 Taipei No Print Exceptions Yes ValueCard 26 ValueCard Per Key 1 ValueCard Groups 26 ValueCard Full Yes POF Multilingual No 4 • ACT 78-0060-4094-9, Ver. 1 Troubleshooting Manual C Taipei Receipt No C Vault Msg No Credit Card InOUT No A3 Multilingual No Hotel No Test No Tax Round Up No C BC NYParks No *APP = Auditor PowerPad APS = Automatic Paystation XV = Credit Card Exit Verifier ACT = Automatic Cashier Terminal SPTR = PowerPad Spitter If you receive a config chip that does not have your ordered options, you may edit your config chip for a maximum of two weeks. After two weeks, the config chip will initialize itself and return to the original burned options that the chip came with. To edit your config chip, choose Programming>System Preferences>Config Options>Config>choose the (F-3 [-] END) key and then press the down arrow one time. You will be one line under the last config option on the page, and your cursor will move one space to the right. Type fapd and then press your (TIME/Yes) key. An editable column will appear on the right side of the config options. Once you make all of the desired changes, you must escape all of the way out of the device, and then log back on as the administrator. Go back to Programming>System Preferences>Config Options>Config, and then choose the (Prog/Print) key. This will print out what the original options are, and also the edited desired options for the device. Fax this printout to Customer Service to have the options changed and a new config chip sent to you. To view Serial Port Config Options, at the device, choose Programming>System Preferences>Config Options>Serial. Here is an example of Serial Port Config Options: P# Rom 1 FUNC DRV TYPE CreditCard DataCap 2 FUNC DRV TYPE PortComm PortComm 3 FUNC DRV TYPE Readers Transport Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 5 4 FUNC DRV TYPE Printer Epson Tm950 rec: Y jrl: Y val: Y rpt: Y To view Input Config Options, at the device, choose Programming>System Preferences>Config Options>Input. Here is an example of Input Config Options: Recp 3 1 1 Cash Drawer 1 3 2 Cash Drawer 2 4 3 Exit Arm Loop 6 4 Exit Rst Loop 7 5 Gate Status 9 6 Exit Dev Enab 10 7 Lost 12 8 Aux Vend To view Output Config Options, at the device, choose Programming>System Preferences>Config Options>Output. Here is an example of Output Config Options: Recp 4 15 1 Cash Drawer 1 13 2 Cash Drawer 2 11 3 Duress 9 4 VC Gate 7 5 Gate 5 6 Custom 3 7 Display Out 1 8 Logon Light To have a new config chip sent to you, it is mandatory that you provide a printout of the config options. If you wish to have a config chip programmed for an existing site, you must send a printout of the options that you would like to have; otherwise, there is a risk that it will be programmed incorrectly, especially if changes were made in the field that 3M is not aware of. 6 • ACT 78-0060-4094-9, Ver. 1 Troubleshooting Manual Axiohm DIP Switch Settings and Wire Connections for ACT ACT or CCXV Fee Display Common Troubleshooting If you are using a PowerPad power supply to drive the fee display for a Credit Card Exit Verifier, or an Automatic Cashier Terminal, and the fee display doesn’t show up, you may have to adjust some settings. The fee display is not defined in the Config Chip, but you should check the config settings to make sure that it is set for the correct device. In the PowerPad, go to Programming>System Preferences>Config Options>Config, and make sure it says CCXV, or ACT. Inside of the power supply, make sure that the 3-pin din next to U7 (74HC08) is shorted with a shunt going to Display. If it is in the Relay position, change it to display. Check to see if you have power to the fee display by checking the backlight. The backlight should continuously be on. If it isn't, you have to adjust the potentiometer on the Power Supply located by U6 (LT1054) to get voltage to the display. Because the potentiometer is a 50-turn pot, you have to adjust it accordingly. You may have to adjust this pot because of variances in the field that are different than its previous test environment. If you adjust it too far, you will be able to hear and feel it click. If all else fails, you possibly have bad drivers for the display which can be replaced in the field. These 2 chips are U7 (74HC08), and U6 (LT1054). If the fee display still does not respond to these troubleshooting tips, send the PowerPad power supply in for repair. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 7 Device Addresses Stuck on Zero When you first set up your facility, you must define each device at the facility with a unique device number per port. It has been reported that customers have not been able to set the addresses on certain PowerPad driven devices such as an ACT or an APS. At the factory, we have discovered that it is a manufacturing defect. There is usually something wrong with the address DIP switch circuit, or perhaps the surface mount resistors on the back of the circuit board. There is no way for a technician to fix this in the field, so if this symptom is found in the field, the board will have to be sent in for repair. PowerPad Power Supply Revision E2 and Older Not Suitable for Upgrading to ACT or MG-1500 Spitter or Exit Verifier Rev E2 and earlier is not suitable to upgrade because of a hardware upgrade needed to fix noise on the display circuit. If a Rev E2 power supply board without the hardware upgrade is used in an ACT or MG-1500 Spitter or Exit Verifier, you will see multiple characters on the display (part #82-20059). The earlier style PowerPad power supply Rev D does not have a Port 3 connector (data connection to the PowerPad expansion board) or the RECP 10 (extra field input for receipt and cancel buttons) needed for ACT or MG1500 Spitter. Because these two connections cannot be made to the earlier PowerPad power supply version D and older, a customer wishing to upgrade their system to a different device must order a new power supply that has these two connections. Currently we use Rev F power supplies. Upgrade Instructions for multiple characters on ACT, APS, MG-1500 Spitter and Exit Verifier, SST Ticket Spitter and Exit Verifier, Display 82-20059 To improve the performance of the display enable-switching circuit. The previous circuit is subject to electrical noise, causing multiple characters on display PowerPad Power Supply Rev E2 to Rev E3 Hardware Upgrade ECO #748 Change PowerPad Interface PCB part # (90-11167) from Rev E2 to Rev E3. To perform the modification for Rev E2 to Rev E3, 2 trace cuts, 2 jumper wires, and the removal of Q1 part # (11-8020) are required. 8 • ACT 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 9 If your power supply board still has this original circuit in it, you have to perform a hardware upgrade, otherwise, you will see multiple characters on the display. 10 • ACT 78-0060-4094-9, Ver. 1 Troubleshooting Manual You must cut the trace indicated by the yellow marker. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 11 You must run two jumper wires between the 3 yellow X marks. At the top left, you must cut the trace wire as indicated by the yellow marker. You must remove Q1 (bottom right of screen shot). 12 • ACT 78-0060-4094-9, Ver. 1 Troubleshooting Manual Close up of the trace wire located under U5. This shot shows the 2 jumper wires connecting the three points that were indicated earlier by the 3 yellow X marks and the trace wire that has been cut as indicated by the yellow marker. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 13 This shot shows the transformer has been removed and the trace has been cut as indicated earlier by the yellow marker. Replace U5 and reinstall the board in the power supply. Version C3.6.1.3 The following enhancements were implemented: * Support was added for the Sinclair Oil credit card in the PowerPad and the ScanNet Central Credit Card System. * The PowerPad platform has been enhanced to support the Citizen and Seiko 2342 14 • ACT 78-0060-4094-9, Ver. 1 Troubleshooting Manual printer. This printer is a replacement for the Axiohm receipt printer that is used in the APS and ACT. * After inserting a transient ticket into an APS, the patron may elect to pre-pay the fee up to a programmed fixed end time. The patron will press the “Pre-Pay” button and the APS will recalculate the fee from the ticket issue time through the programmed fixed end time. Upon payment of the fee, the patron will receive an exit pass with the fixed end time encoded and printed on the ticket. The exit pass will allow the patron to leave without any further charge up to the fixed end time plus any programmed grace time. Version C3.6.0.11 The following new development and enhancements were implemented: *The rounding error that occurred when using backout taxes with fees calculated from fee tables has been corrected. *The situation that forced a Void Incomplete message when fee computations required more than 10 seconds to complete has been corrected by increasing the time allowed for the SST to respond to a poll to 1 minute. *The timeout value (1-999 seconds) for waiting for a message from the License Plate Recognition (LPR) system is now programmable in the LPR menu of the PowerPad. *A patron can now use a credit card to prepay for a transient ticket on an SST Ticket Spitter that has been programmed appropriately. The ticket is valid for a programmable length of time. If the patron exits the parking facility within the time period, no additional fees are assessed. *The situation that caused addon taxes to act like backout taxes has been corrected. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ACT • 15 16 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual APS Updating the Mars Bank Note Acceptor to Accept New Bills Whenever the US Government issues new bills, you must update your Automatic Pay Station's Mars Bank Note Acceptor to accept these new bills. See this Sodeco Support Tool Installation, Programming and Utility Instruction document for more details on part numbers, pricing, and procedures on how to install the software, run the software, and some other troubleshooting tips to keep in mind when using the Sodeco Support Tool. Sodeco Support Tool Installation, Programming and Utility Instructions Updating the Mars Bank Note Acceptor to Accept New Bills If you have a Mars BSN 385 or a Mars BNA51/56 or Mars BNA52/57 Bank Note Acceptor, update the unit to accept these new U.S. Government bills by following the instructions provided. This update requires the use of the Sodeco Support Tool software which is a third-party software package provided by Mars. 3M offers two choices to upgrade the note acceptor for accepting the new $20.00 bill. 1) Send your note acceptors in to be upgraded by the DRC. You must request an SRO for this upgrade. The upgrade part# is 01-7095 with list price of $300.00 per unit. 2) Purchase the upgrade kit and perform it yourself. You will order : Item 1* 2* 3* 4 5 Qty 1 1 1 1 1 Part# 41-17396 11-25553 11-25555 41-17398 41-17399 Description BNA50/51/52X Software Upgrade BNA55/56/57X Software Upgrade BSN385 Series Software Upgrade Security Key With Dongle Sodeco Calibration Papers (pkg of 10) List Price $805.00 $805.00 $805.00 $755.00 $ 35.00 Note: a. b. c. d. The software upgrade (items 1*, 2*, or 3*) must be ordered according to the note acceptor model. You only need one unit of Software Upgrade per company. You may upgrade as many note acceptors as you wish with one license. The same rule applies for the security key and dongle. Some distributors may already own a security key/dongle from the $5/$10 bill upgrade in 2000. If you do, you do not need to purchase another one. Unless you have several note acceptors to upgrade, one package of calibration paper will be enough. Contact your Mars representative or 3M Customer Service for additional information. Warning! Turn the power OFF before removing the cover to the BNA unit. Installing new software (EPROM) (please check with Mars or 3M Product Support as this step may not be necessary) Note: Software goes inside note acceptor 6.1 or higher. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 17 1. Remove the top cover of the Mars’ BNA unit after the power is turned off. 2. Green lever opens and locks BNA 542 note acceptor. Use the green lever on left to close. 3. Locate the PC board at the front of the unit. Loosen the two Phillips head screws and slide back and up to expose board to install the firmware chip. One screw on the corner and the other screw on the middle plate have to be removed. 4. Locate the firmware IC and replace it with a new Mars BNA version. Note that the fuse is a 3.15 Amp 250V fuse. Refasten the board and replace the cover. 5. Install the Sodeco Support tools which are on a CD-ROM available from Mars or 3M Customer Service. It is advisable to allow the Sodeco icon to be placed on your PC desktop at the end of the installation process. 6. Copy the Note Variant files to a directory on your hard drive (C:/Mars/Variant). You can leave the files on the floppy disk but access time will be slower. 7. Install an RS-232 cable between the Comm port on the PC and the Data port on the rear of the Bank Note Acceptor (DB-9 female to DB-25 male). 8. Install the software key on the computer’s LPT1 port. 9. You must have a cash vault in place. 10. You must clean the optical sensors inside the banknote acceptor before proceeding. 11. Turn on the APS power switch. 12. If you already have the Sodeco Support Tool installed, skip to “Updating the Mars BNA Series.” 18 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual Installing the Sodeco Support Tool Software 13. Insert your auto-start Sodeco CD. If it does not auto-start, double-click the set up icon. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 19 14. Click Yes. 15. Click Next. 20 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 16. Enter your User Name and Company Name. Click Next. 17. Click Next. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 21 18. Choose Typical and Click Next. 19. Click Next. 22 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 20. Click Next. 21. Installation will install to 100% and you will see the next screen: Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 23 22. Click Yes. 23. Click OK. 24. Click Yes. 24 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 25. Rainbow driver will install to 100% and you will see the next screen: 26. Click OK. 27. Click Yes. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 25 28. Click Finish. Updating the Mars BNA Series • • • • • • Copy the Note Variant files to a directory on your hard drive (C:/Mars/Variant). You can leave the files on the floppy disk but access time will be slower. Install an RS-232 cable between the Comm port on the PC and the Data port on the rear of the Bank Note Acceptor (DB-9 female to DB-25 male). Install the software key on the computer’s LPT1 port. You must have a cash vault in place. You must clean the optical sensors inside the banknote acceptor before proceeding. Turn on the APS power switch. 1. Double-click on the Sodeco Support Tool icon. 26 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 2. Choose BNA5 Range Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 27 3. BNA5 Range will appear in the top left combo box. 4. Press the Diagnostics button. 28 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 5. when the screen comes up, Type #, Click Enter. The note acceptor should then reset and display the following screen. If it does not reset, you may be experiencing communication problems. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 29 6. Click the F9 key to display the note acceptor type. 7. Click the Configuration Download button. 30 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 8. Choose which comm port you are hooked up to and Click Next. 9. You will see this message as it is reading the banknote acceptor data. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 31 10. Browse out to the Note Variant files (C:/Mars/Variant). 11. Once you have the configuration file selected (NOTEWAYS.LST), Click Open. 32 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 12. Click Next. Note: if you click on the Advanced tab, a screen appears showing two windows. The right window displays a list of files currently loaded in the Acceptor while the left window displays a list of files from the location you selected. Each file in the left window has a green check mark indicating that this file is selected to be downloaded. Click Next if you go to this window. 13. Click Yes. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 33 14. Click Next. Note: The reference paper is supplied with its maximum width and length. A sheet should be cut to match the width of the note, but the length should not be altered. 15. You will see this screen as it prepares the banknote acceptor. 34 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 16. Insert the Sodeco Calibration paper when you see this screen. 17. This message displays while the banknote acceptor reads the calibration paper. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 35 18. Click Start download. 36 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 19. The program will delete all notes previously in the note acceptor, and add all new notes to the note acceptor. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 37 20. Click No. 38 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 21. Download Completed. 22. Click the Diagnostics button. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 39 23. The Diagnostics screen will open up. 40 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 24. Choose Commands>Recovery>Auto. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 41 25. Choose Commands>Set>Out of Operation>Automatic. 42 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 26. Choose Commands>Set>Baud Rate>4800. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 43 27. Click Enter 28. Type CAL 29. Click Enter 30. Type WOR 31. Click Enter 32. Green Led will light up on the acceptor. At this point, you will insert the Sodeco Calibration Paper touching only the edges of the paper. The white calibration paper is used to calibrate the optics and set limits on the length of the bank notes inserted. To Test the Bills 1. 2. 3. 4. Click Enter Type WOR Click Enter Green Led will light up on the acceptor. At this point, insert any bill. The unit will either accept it or reject it. 5. If accepted, the software will display the note type that has been inserted. Note: The following is an example denoting a new $20.00 bill: VUSEE3 .> 6. Click Enter 44 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 7. Type REF 8. Click Enter 9. Retrieve the note. 10. Example of what the window will look like. Updating the Mars BSN Series 1. Install the update EPROM on Board B (middle board) in the Mars BSN. (check with Mars or 3M Product Support to see if this is necessary). 2. Run the Mars software. In the upper left corner of the window, set the product to the BSN3 range. 3. Click the Configuration/Download button, and go through the downloading process download the new bill information. 4. Once the downloading process is complete, click the Audit/Test or Diagnostics button to change screens. 5. At this point, the new bill information is in the BSN, but it must be reset before you can proceed. Click on the Configuration/Download button. Listen for the BSN to reset, which is indicated by the sound of the motor turning. 6. After the BSN resets, click on the Cancel button and then click on the Audit/Test or Diagnostics button. 7. Scroll down to the last line of Current Bill Information displayed on the screen. 8. Click on the line and enter “w” (for work). The green light on the BSN should go ON indicating that you are now ready to calibrate. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 45 9. Insert an object into the side of the BSN to activate the reset switch. The green light will go out and the following message will appear on the screen: “Select banknote-way to initialize.” 10. Enter the work length. The screen will display the following: “o/o-04initialization LENGTH/5.” 11. Insert the Sodeco Calibration Paper which is available from Mars or 3M Customer Service. After the BSN accepts the calibration paper, enter “r” (for refund). The BSN will eject the calibration paper. 12. Enter “w” and reinsert the calibration paper. Enter “r” again. Repeat this process five times. The message “o/o-04-initialization LENGTH/4” will be displayed each time with a decrementing number at the end. When the process has been completed five times, the calibration will be complete and the BSN will be updated and ready to use. Note: If the above procedure does not result in a successful update, you must clear the memory and then repeat the above procedure. To clear the memory, follow these steps: Clearing the Memory 1. Remove the middle CPU board, and locate the battery on the left-hand side. 2. Follow the board trace from the plus (+) side of the battery to locate a soldered square on the board. This solder must be removed to drain the RAM. Allow at least 30 seconds before resoldering. 3. Power down the unit and clear the memory on the APS CPU Board. 4. Verify that the new bank notes are added correctly by going to Programming/Notes&Coins/Note Vault and verifying that the Type header lists the appropriate value for the listed bank notes, that the Status header shows all bank notes as Active, and the Value header lists the correct value for each respective bank note. To Test the Note Acceptor at the APS 1. 2. 3. 4. 5. 6. Turn the APS off. Reconnect the data communications serial interface. Clear the memory on the APS CPU board. Turn on the power to the APS. Verify that the Bank Note Acceptor resets when the power is restored to the APS. Verify that the new bank notes were added correctly by going to Programming>Notes&Coins>Note Vault and confirming that the Note header lists USC and USD for all bank notes; the Type header lists the appropriate value for the listed bank notes; the Status header shows all bank notes as Active; and, the Value header lists the correct value for each respective bank note. 7. Verify that the new bank notes work in the APS when calculating fees. Other Troubleshooting Tips To View the Last 100 Error Codes 1. Click Enter 2. Type DIS ALL 46 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual 3. Click Enter 4. This shows status of all notes. These are not error codes. 5. USAC1 through USAC4 are status files for $1.00 bill. Note: US – US note A - $1.00 Bill 1, 2, 3, 4 – position inserted (There are four status files for each bill because there are four ways you can insert the bills). A – Active 00000000 – times inserted Two dashes means the file is good. If the file shows up as * or X, it is corrupted. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 47 6. Starting at 47029 and down to 00092, these are the last recorded error codes. Contact 3M for meaning on your specific codes. Note: There are no errors shown in the above example. 7. *R1 – Cash Box removal the numbers are counters (not an error). To Display the Optical Sensor Regulation Values Use this command to display the regulation settings for the measuring elements and the motor. As the optical sensors get dirty, the sensor becomes stronger in order to overcome the problem. 1. Click Enter 2. Type DIS REG 3. Click Enter First line displayed: • Setting for the left-hand inlet light-barrier 48 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual • Setting for the right-hand inlet light-barrier • Setting for the length light-barrier Then, one line displayed for each reading head: • Setting for the green LED No. 1 • Setting for the green LED No. 2 • Setting for the red LED No. 1 • Setting for the red LED No. 2 • Setting for the infrared LED No. 1 • Setting for the infrared LED No. 2 The displayed settings are conversion values for the DAC (-4095, 4 characters). Last line displayed: • Setting for the motor to run forwards at low speed. • Setting for the motor to run forwards at normal speed. • Setting for the motor to run backwards at low speed. • Setting for the motor to run backwards at normal speed. The setting represents the power applied to the motor (0=0% et 255 = 100% of the maximum power) Unique sequence: DIS REG> 0045 0052 1365 1373 1271 1268 1109 1476 1111 1366 053 154 1862 0547 0557 0535 0511 054 LIMITS Inlet barriers L+R Length barrier LED measuring heads 0575 0658 0507 0540 160> 0495 0515 0490 0539 Out of service LOW <9 < 100 < 100 0553 0519 0466 0506 Setting Values for: Light barriers left/right-hand/length Settings head 1 Settings head 2 Settings head 3 Settings head 4 Motor Power OK Warning HIGH 9<ok<163 100<ok<3071 100<ok<3071 > 163 > 3071 > 3071 Out of service HIGH > 175 = 255 = 4095 = 4095 PowerPad and APS Keys Making Noise, but not Performing Function Some keys on the PowerPad are two times the width of most keys, and most don’t know that underneath these keys are two positions that could potentially be pressed, depending on how the key is installed. Some of these keys are RECEIPT, RECALL, VOID, and CLEAR. If the keys are installed backwards, they will still emit a beep noise when pressed to let the operator believe the key was installed properly. 3M is implementing new testing measures that will catch this manufacturing issue, but we wanted to let you know that you can fix this problem in the field by turning the key around. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 49 Device Address Stuck on Zero See Device Addresses Stuck on Zero under ACT. CashCode Instead of Mars A new CashCode Note Acceptor (CashCode FL Validator, Part # 43-16768) will now be used in all APS units unless a customer specifically requests the Mars BNA unit. Introducing CashCode Note Acceptor Due to the increase in cost from our vendor, 3M has changed the Bank Note Acceptor options for the Automatic Pay Station. Currently, if you require note acceptance for your Automatic Pay Station, you would order the Mars unit, either model BNA 57 (with escrow) or model BNA 56 series (without escrow). Both units are available in the 13-bill option 2,000-note capacity self-stacking vault or the 6-bill option 1,000-note capacity self-stacking vault. Effective September 8, 2003 the price of the BNA 56 & 57 will be raised. BNA 56* Series Old Price New Price 13-Bill $21,420.00 $24,420.00 6-Bill $18,870.00 $21,870.00 *BNA 56 Series will be obsolete as of September 30, 2003. BNA 57 Series Old Price New Price 13-Bill $25,977.00 $27,977.00 6-Bill $22,746.00 $25,746.00 In an attempt to keep the price from escalating, we selected another Bank Note Acceptor that is comparable to the BNA 56 series; it will become its replacement. ***New Product Offering*** The CashCode Note Acceptor package is $15,000 list, for all countries. The Cashcode Note Acceptor part numbers are as follows: USA 43-16768 USA/Canada 43-16769 Canada 43-16770 Australia 43-16771 China 43-16772 Malaysia 43-16773 Mexico 43-16774 New Zealand 43-16775 USA/Mexico 43-16776 50 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual Contact the factory for additional countries. Features: * Multi-width bill validation that provides self centering of notes. * Flexible Sense-a-Click™ sensor paks is an advance sensor technology that improves valid bill recognition and protects against counterfeits. * Quick and easy Smart Stick memory software updates (upgradeable in the field). * Single-stacking cassettes reduce jamming. * Visual diagnostics on board for easy service. * Beltless transport system. * Four-way bill validation. * Standard 15-note acceptance. * 1000-note capacity self-stacking vault. * Two security locks. * Note: The CashCode acceptor does not offer an escrow feature. APS Not Spitting Notes 1) If power supplies for the note dispensers are below 34VDC or above 38VDC you will see problems like the note dispenser going offline. There is a gold colored power supply that you can adjust the potentiometer to correct the voltage problem. 2) When there are only 50 notes left in the note dispenser, the APS will not dispense any more notes. 3) You can program either notes or dollar balance. 3M suggests using notes to prevent bad math. Status: Var. Cnt.–Number of notes Var. Amt.–Dollar amount Fixed Cnt.–Fixed number of notes Fixed Amt.–Fixed Dollar amount Unused–hopper/dispenser will not work. Editing Configuration Chips for Auditor PowerPad, Automatic Pay Station, Credit Card Exit Verifier, Automatic Cashier Terminal, and MG-1500/ML3500 Spitter See Editing Configuration Chips under ACT. Automatic Pay Station: Switch Replaced The switch with the actuator arm on the back of the note dispenser security door on the Automatic Pay Station (APS) was recently replaced with a switch that has a plunger instead. The new switch is adjustable to allow for cabinet and Note Dispenser tolerances. The new switch eliminates the situation in which the switch actuator arm was snagging the cables on the note dispenser assembly. To take advantage of this change, you need to Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 51 order a new switch and a new note dispenser security door. The same lock can still be used. Pre-Pay Option for the APS The Pre-Pay function allows a patron to Pre-Pay a parking fee at an APS. This allows patrons to exit faster because their ticket has already been paid for ahead of time. To use this feature, program the Pay AnyTime key for Fixed Tm (Fixed Time), and create a window to allow Pre-Pay to work. Example: 8/8/02 07:00 8/8/02 17:00 Repeat every (1)* (Days)* This means that you can Pre-Pay for your ticket between 7:00 and 17:00, that day. In the example, one minute after 17:00, the date will change to the following day, provided you have 1 Days programmed. A customer enters the lot at 7:00 in the example. When the customer inserts the ticket at an APS at 8:00, a normal fee will be generated for one hour. The customer pushes the Pre-Pay key, and it will generate a charge as if it were 17:00 that day. At $1.00 an hour, the initial charge would be $1.00, and after pressing the Pre-Pay key, it will be $10.00. The APS uses the lost ticket input wired to the Pre-Pay input in order for the Pre-Pay option to function correctly. You have to map the input for APS Pre-Pay to the lost ticket input, which is #4 on RECP 14. The configuration option inputs have to be programmed as following: RECP 14 9 Receipt 10 Cancel 11 APS Pre-Pay Note: You cannot order both the Lost Ticket option and the Pre-Pay option for the same APS because the button for each of these functions occupies the same location. Note: Do not confuse the Pre-Pay Fee function with the Pay AnyTime function. The Pay AnyTime feature allows a patron to Pre-Pay a parking fee at a Central Cashiering location. The Pre-Pay Fee function is used at an APS. Thus, information about parking rates and the Pre-Pay feature must be prominently posted for patrons to see prior to making a decision to use Pre-Pay or not. For more information about the Pay AnyTime function, refer to your Auditor PowerPad Fee Computer Operator Manual. Note: There is no automatic refund if the patron exits the facility before the max time that they have paid for. If the patron pays up to 17:00 that day, and exits at 16:00, special arrangements will have to be made through management to return the money to the patron. *Other programming options include the following: Repeat every (Programmable as 1 - 99) (Programmable as days or weeks). You set when the date field changes. General Information *The APS needs a burster for lost tickets. *The APS only uses Master and Supervisor attendants. No cashiers are used (they cannot 52 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual function). *When the door is closed, the PowerPad inside logs off. (PowerPad inside displays: "enter new Txn – please insert ticket", and the customer fee display on the outside displays: “please insert ticket”) *When door is open, the PowerPad inside logs on. (The patron display shows: “Out of service”, and the PowerPad inside displays: "log on Attendant 1") *Void is only programmed at ScanNet, you cannot program the void key inside the APS. *There are 5 security switches: Main Door, Note Dispenser Door 1, Note Dispenser Door 2, Coin Door, Coin Vault *The APS is only used as a Central Cashier. *The current APS uses an Epson 300 Journal printer (optional). This option records all transactions if not connected to scan. *The APS can program exceptional transactions. *The APS cannot filter only credit card transactions because it is considered a transaction, and they are all considered the same. *Datacap DataTran or Central Credit Card System is used with credit card transactions. *The coin acceptor is a Mars Cash Flow 430. *The coin module lists what coins are accepted. *On the coin module there are 2 letters that appear sideways that shows what country the module is programmed for. Example: US-United States, AS- Australia *The Dispensers hold up to 2000 notes each. *The coin vault can hold 4000 coins. *The coin vault holds coins that are not dispensed, or excess coins from full hoppers. *There is a 2000 note capacity in the note vault. If the note vault is filled to capacity, you can program the APS to shutdown. Common Troubleshooting If it is a B platform-If the coin vault report is not resetting to zero, make sure that the Input/Output board U11 is in its socket, and that the battery is good. If it is a B platform-If board won’t boot up, the IC’s on the Input/Output board may not be programmed. These have to be in place with identification stickers. U15 – APS2B U16 – APS1B If the patron display is lit up with boxes, but no information, you must adjust the potentiometer setting next to the display connection on the Input/Output board. The note acceptor, Mars BNA542, includes an escrow unit, which prevents money laundering. The escrow unit holds onto notes until either cash due is satisfied, or fifteen bills are in escrow. If the transaction is cancelled, it will spit out the stack of bills that has been held in the escrow unit. After fifteen bills have been inserted, it will not accept the 16th bill. It will not spit out the bills after the transaction has been cancelled after fifteen bills have been inserted. You will be issued a credit slip. The words ***credit slip*** are in 3 point font. If fourteen bills have been inserted, and the transaction has been Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 53 cancelled, it will return the fourteen bills in escrow. There is a 2000 note capacity in the note vault. If the note vault is filled to capacity, you can program the APS to shutdown. Mars BNA541 does not have an escrow unit included. Everything inside of the APS operates with 24VDC except for the two note dispensers. They have their own power supply running at 36V. When there is only 50 notes left in the note dispenser, the APS will not dispense any more notes from note dispenser Not Asking Cash Amount When Reinserting Note Dispenser This is due to the Main door being closed before seeing a hopper or vault reinserted. If a customer is using only 1 Note hopper cassette and 1 Note acceptor vault to change the money out in their APS, this will create a problem with the firmware as the APS normally expects to see a new cassette or vault inserted right after the previous ones were removed. In a bad example of what not to do, the customer was removing the hopper and vault, closing the APS door and going back to a secure location to add money to the hopper and remove notes from the vault. Then they would come back and reinstall these. The problem was that the APS would not give the correct insertion prompts and therefore they couldn't tell the APS how much money they were inserting or were they able to tell the Note acceptor vault that it was empty. Again, this is due only to the Main door being closed before seeing a hopper or vault reinserted. 3M would advise any new sales to include an extra hopper(s) as well as an extra Note Vault to prevent this problem. Stopped Taking Bank Notes Log on to the programming terminal in the APS and go to the Report menu. Once there, select Status Report, and view/print it out. The Status Report will give a status listing of all Coin and Note Handling devices (if so programmed) in the APS. You would then look at the Note Vault information to determine if the unit was “Present,” “Working,” “Communicating,” or find the applicable Error Code. If there is an Error Code, the complete list can be found in your APS manual. The Error Code is a 2 digit numerical or alphanumeric code that is easily translated. For example, if the Status Report showed a code of 54, this would translate as “Light Barrier of BSN 385 faulty.” You would then look at the Exit Chute of the Note Acceptor to see if the outlet flap was stuck in the open position. 54 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual Program to Pull Reports Since the APS does not use any attendants to process transactions, it is not necessary to program these. If however, you require the people who cycle the Note Vault and Hopper to pull reports, these individuals will need to be added to the Attendant List. They will need to be given Supervisory status, as this will give them permission to pull reports but not to alter the programming of the APS. Lastly, remember to program these additions at the APS unit and not in ScanNet. Sending the list out from ScanNet will overwrite Attendant #1 in the APS. This attendant is reserved as a Cashier and is logged on and off as the APS door is opened. Attendant #1 in ScanNet is a Master, which would change the Cashier status in the APS to a Master if sent out from ScanNet. Language Changed to Italian There was a problem found in B2.4.7 firmware where the patron display will change to the Italian language on its own. B3.3.2 firmware addresses this problem, and is available on our web site, but remember before upgrading any APS, a new config chip will be required. Axiohm Receipt Printer DIP Switch Settings and Wire Connections Sodeco Support Tool/HyperTerminal You may have wondered from time to time about the many different devices that reside inside your Automatic Pay Station unit. One of the most sophisticated of these is the Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 55 Mars Note Acceptor Unit. Made in Switzerland, this precise unit is capable of reading notes inserted in any direction with a 97% acceptance rate. What most people do not realize is the amount of data that you can retrieve by hooking up a laptop PC to this device. What You Can View By connecting to the Note Acceptor, you can access the following types of information: • A display of the Notes in the system, their status, and whether there is corrupt data associated with a particular note. This is useful if you have a particular note that is not being accepted. • A display of the various Counters that tell you how many notes have been processed for a given amount of time, as well as how many total notes have been through the system. This is useful for setting up preventative maintenance on the Note Acceptor. • A display of Failure History that keeps a running total of the last 100 Out of Service Codes. This is useful for distinguishing between one-time problems and systematic patterns that require more attention. These are just a few of the useful types of information you can view if you decide to get “hooked” on the Mars Note Acceptor Unit. How to Get Hooked To connect to the Note Acceptor, you need a PC running Windows 95 with a serial port for communications. Windows 95 has a pre-loaded accessory called HyperTerminal that works quite well. You will also need an RS-232 cable (DB9-DB25) to connect the PC to the Note Acceptor. Note Validator Variant First Thing Loaded After Cold Start If you change Motherboards in your Automatic Pay Station, always remember to do a Cold Start (Service Jumper J17) before turning the unit on for the first time. The APS Note Validator variant is the first thing that is loaded when the unit is turned on for the first time. If the unit is not Cold Started, then the Note Validator program stays resident in Random Access Memory (RAM) and the APS bypasses this routine upon start-up. A recent service call proves why it is important to do a Cold Start when changing Motherboards. A customer wanted to know why a recently repaired Note Validator was showing that U.S. Currency was programmed into it when it should have been set for the customer’s foreign notes. After going through the usual troubleshooting procedures, we realized that the customer had upgraded his APS Motherboard and had not dumped the memory prior to turning the unit on. I asked the customer to dump the memory and then reboot the APS, This loaded the foreign notes file into the RAM on the APS Motherboard, and the situation was resolved. Since we had tested the board here at the factory, it was loaded with the variant from a U.S. Note Acceptor. The board was shipped to the customer with the original programming in it. Since data was still resident in RAM, the APS had no way of knowing that a different Note Acceptor was connected. We now make sure that all boards tested have their memory erased before shipping. So remember this tip when receiving a new Motherboard from us: Always Cold Start, just to be sure. 56 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual BNA 51 and 52 Series Note Acceptors Discontinued Mars Electronics discontinued its 51 and 52 Series Note Acceptors late last year and replaced them with the 56 and 57 Series. You can upgrade current BNA 52 units to a BNA 57 by installing an upgrade kit (Mars Part #BNA 9521K-571). Output 5/Voice Annunciation *Output 5 (Terminals 3 and 4 on the output connector) previously unused, is now mapped as “gate vend.” This allows the option of using an output with the completion of a transaction. *Voice Annunciation was added as a new optional feature to provide audio instructions to patrons during transactions, through a combination of prerecorded or user-programmed voice messages. The package consists of a voice unit, speaker, and ultrasonic sensor. Version C4.0.1.5 The PowerPad firmware has been enhanced to support a Cashcode Serial Driver for the Automatic Pay Station. Version C3.6.1.3 The following enhancements were implemented: * Support was added for the Sinclair Oil credit card in the PowerPad and the ScanNet Central Credit Card System. * The PowerPad platform has been enhanced to support the Citizen and Seiko 2342 printer. This printer is a replacement for the Axiohm receipt printer that is used in the APS and ACT. * After inserting a transient ticket into an APS, the patron may elect to pre-pay the fee up to a programmed fixed end time. The patron will press the “Pre-Pay” button and the APS will recalculate the fee from the ticket issue time through the programmed fixed end time. Upon payment of the fee, the patron will receive an exit pass with the fixed end time encoded and printed on the ticket. The exit pass will allow the patron to leave without any further charge up to the fixed end time plus any programmed grace time. Version C3.6.0.11 The following new development and enhancements were implemented on the above named products: *The rounding error that occurred when using backout taxes with fees calculated from fee tables has been corrected. *The situation that forced a Void Incomplete message when fee computations required more than 10 seconds to complete has been corrected by increasing the time allowed for the SST to respond to a poll to 1 minute. *The timeout value (1-999 seconds) for waiting for a message from the License Plate Recognition (LPR) system is now programmable in the LPR menu of the PowerPad. *A patron can now use a credit card to prepay for a transient ticket on an SST Ticket Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 57 Spitter that has been programmed appropriately. The ticket is valid for a programmable length of time. If the patron exits the parking facility within the time period, no additional fees are assessed. *The situation that caused addon taxes to act like backout taxes has been corrected. Version B3.3.2.0 - New Config Chip Required when Upgrading If you have an Automatic Pay Station with B Platform hardware and you want to upgrade the firmware from a previous B version to B3.3.2.0. or later, you must obtain a new config chip. Some changes were made to the internal structure of the config chip to make them compatible with Version B3.3.2.0. Existing config chips will prevent the coin hoppers from coming online when used with Version B3.3.2.0. You must provide Customer Service with your existing options (preferably a printout from the APS), so they can advise you on how to order the config chip. Platforms B and C prior to C.3.3.0.2/Facility Codes above 512 The Auditor PowerPad (Platforms B and C) will only process Facility Codes of 512 and below. If a ticket or ValueCard is created with a Facility Code higher than 512, it will not be processed. Therefore, until further notice, you should only use Facility Codes of 512 or below. Version C3.2.0.2 This version includes the following changes: *The number of coin and note dispensers available in Coin and Note Dispenser programming is now limited to the number of dispensers supported in Automatic Pay Station (APS) configuration programming, eliminating the issue with coin and note dispensers not dispensing change properly. *The intermittent issue of printing not appearing on transient tickets was resolved. *A Fixed Fee type was added to the list of merchant account types, which allows a fixed fee to be programmed to charge patrons in lieu of the actual parking fee due. The difference between the actual parking fee and the fixed fee is added to the merchant’s account. *The message “Maximum reached” is displayed when an attempt is made to add uses to a ValueCard that already has been assigned the maximum number of uses allowed (254). No additional uses may be added to a card containing the maximum. *A change to the power cycling of the coin dispensers has resolved an issue with coin dispensers running continuously instead of advancing to the next dispenser when the dispenser runs out of coins while it is dispensing change. Version 3.2.0 The upcoming Scan NT release (Version 3.2.0) will include programming for the Automatic Pay Station (APS). Some of the Auto Pay Station programming will be located in “Preferences.” The rest will be located in the PowerPad/APS programming 58 • APS 78-0060-4094-9, Ver. 1 Troubleshooting Manual window. In the Preferences window, users will be able to perform the following: * Configure the preferences for Notes and Coins. * Set the Lost Ticket Cancel Time. * Activate the Credit Card System. * Print a Signature Slip. Keep in mind the following when programming the APS from Scan NT: * Before you use the APS, you must first configure the Preferences for Notes and Coins. * The Notes and Coins programming menu allows you to set up Note & Coin Acceptors and Dispensers. Version A1.8.0 Among many other new features, this new version allows you to view or print a list of the options you have purchased by using the Config Options menu item. It also allows you to use the Credit Card, Voucher and ValueCard features simultaneously. By addressing timing issues, this new version also resolves situations in which tickets have become stuck in the SST Parker. Troubleshooting Manual 78-0060-4094-9, Ver. 1 APS • 59 60 • CF-803i 78-0060-4094-9, Ver. 1 Troubleshooting Manual CF-803i CF-803i: English 7.1.34UN and Spanish 7.1.34EN 3M released versions of the CF-803i. These versions include the following changes: *A discount value using stamps now appears on receipts and is included in the discount total on reports. *With two or more terminals in a facility at separate entrances, vehicle counts match between the terminals. *Terminals no longer lose data and/or memory when turned on. *The following issue was resolved in the automatic version: If a valid card was read with no vehicle on the loop, access was granted and the gate vended for the next vehicle to enter the loop without that vehicle’s card being read. *The license plate number now prints on Bar Code exit tickets. *In the English version, the grammar for several messages was corrected. *An extra 24 hours is no longer charged to the fee when the date changes from February 28 to March 1 in non-leap years. Troubleshooting Manual 78-0060-4094-9, Ver. 1 CF-803i • 61 62 • CF-803i 78-0060-4094-9, Ver. 1 Troubleshooting Manual CCEV (Credit Card Exit Verifier) Version C2.8.1.4 3M released version C2.8.1.4 of the CCEV. This version includes the following changes: *CCEV that does not utilize credit card payment processing, an appropriate message is displayed instructing the patron to use the intercom. If a ticket is still in the Transport of the CCEV and the patron has no means to make payment, the ticket is voided and is taken by the Transport when the patron leaves the loop. *The Printer Programming menu was modified to exclude various programming fields only if BEMATECH MP2OF1 fiscal printer is selected. CCEV Serial Expansion Board The Serial Expansion Board (Part No. 92-10372) was eliminated from the CCEV. This board provided additional input for the Receipt button. Now the Receipt button can be mapped to a spare unit on the main CPU board. When programming PowerPad configurations for the CCEV, Input 5 is mapped for Receipt Input. In the CCEV power supply, Field Input 1 on Recp 10 is moved to Input 7 on Recp 3. Crossover Exit Verifier DIP Switch Settings To make an Exit Verifier a crossover Exit Verifier, you need to change the DIP switch settings. Refer to the latest version of the Exit Verifier manual (R44/45.M.6/00.H.1) for the proper settings for a crossover Exit Verifier. Note that these settings are not listed in the old version of the Exit Verifier manual (R17.M.10/95-3/98.K.4), but they are in the latest version. Programming Crossover Exit Verifiers When using an Exit Verifier as a crossover device to a secondary area, access to the secondary area can be restricted to only monthly patrons, and transient patrons can be denied access. This is accomplished using the Facility code. The Facility code assigned to the transient ticket by the SST Ticket Spitter needs to be different from the Facility code used by the monthly patrons. The monthly Facility code would be programmed into the Exit Verifier but the Facility code assigned to the transient tickets by the SST Ticket Spitter would not be. transient patrons would then be denied access to the secondary area because they would not have the proper Facility code. You must have firmware version C3.1.4V or B2.6.4V or later installed in the SST Omega in the Exit Verifier for this to work properly. Troubleshooting Manual 78-0060-4094-9, Ver. 1 CCEV (Credit Card Exit Verifier) • 63 64 • CCEV (Credit Card Exit Verifier) 78-0060-4094-9, Ver. 1 Troubleshooting Manual Gate Gates Tips & Tricks During Installation Here are some tips to keep in mind while installing a gate: 1. When installing a gate, check to see if the 115/230-volt jumper on the power board is in the correct position. 2. Before installing the Omega Controller, spray the pins, the connector and the config module with contact cleaner. This should also be done periodically after installation to ensure a good connection. 3. Move the gate up and down several times before installing the gate arm. 4. When installing Full signs on the top of gates, caulk around the top and bottom of the square mounting post where it mates with the Full sign and the top of the gate housing. Before mounting the Full sign, seal the wire holes and mounting bolt holes. 5. If the gate arm drops before starting up, adjust the limit switch cams. 6. After completing the installation, remove the small screw from the cap of the gear reducer. This allows the gear reducer to have a vent. If you do not remove the screw, expansion and contraction can cause the seals in the reducer to leak oil. After Installation Here are some tips you might find useful after installation, while the gate is in operation: 1. If you see a build up of black dust on the inside of the gate, check the alignment of the pulleys. 2. Periodically check the tightness of the set screws on the motor shaft pulleys and gear reducer pulleys. 3. If you see black bars and no characters displayed on a G-90 Omega, it is possible the SuperCap has discharged. To remedy this situation, power down the control power. Close Dip Switch #2. Hold down the Menu button on the Omega, and turn on the power to the Omega. In other words, do a “Cold Start.” 4. If the gate arm stays up after a vehicle passes over the closing loop, the rebound sensitivity may not be set appropriately. To remedy this situation, perform the following procedure. With the gate in the down position, Cold Start the Omega. If this does not resolve the issue, change the motor rebound sensitivity to 9. The default is 5. Type of Motor Oil for Gate Reducer The reducers in all barrier gates are filled with a synthetic lubricant. Check the fluid level regularly. Draining and refilling should not be necessary unless you observe an external leak. If your site glass is located at the top of the speed reducer, the sight glass should show an air pocket when at an acceptable level. If lubricant is required, use Mobil SHC 629 synthetic gear lubricant. If this is not available, use Mobil 1 Synthetic Oil. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Gate • 65 G-90 LCD Config Module, “No Config” Message To ensure that the LCD Omega always reads the Config Module, solder a jumper wire across R02 (22k ohm resistor). This change effects the old style G-90 LCD Config Module that is no longer in production. This potential problem is identifiable by the “No Config” message on the LCD Omega display. G-89 Gate Warning Labels The WARNING label will now be applied to both sides of the gate cabinet. Both labels will be centered and approximately 8 inches below the top of the gate cabinet. Omega Controller In November 2003, The front silkscreen was modified to indicate polarity for capacitor C38. New Flash Omega Controller Beginning with revision K, the Omega LCD Controller no longer has a socketed EPROM. Firmware is instead stored in a Flash memory device on the circuit board, so you can load or update firmware via a serial connection from a computer with the FlashProgrammer program. The FlashProgrammer program, oload.bin file, flash firmware file and FlashProgrammer Instructions are available at the 3M web site on the Firmware Depot page. Flash files have a .FLASH extension in the Included Files column and show the IC Type as FLASH. You can tell at a glance that you have a revision K Omega by the membrane switches that replaced the previous push-button switches. Troubleshooting Loop Detection for a G-90 CD Gate If you are experiencing any difficulties with loop detection, try these steps for troubleshooting: If you are experiencing any difficulties with loop detection on your G-90 CD Gate, try these steps for troubleshooting: 1. Place a metal gate door on the ground over loop A in front of the Card Reader, Ticket Spitter, or other device that may be inhibited. The loop under the gate door acts like a metal detector. 2. Inside the gate, look at the LED lights under A on the Omega Controller and determine if the blinking LED light under T (tuning) has changed to a solid LED light under P (presence). If your device is in a base mode/sub mode other than base mode 1, sub mode 1, this would indicate that the loop is enabled. (Base mode 1, sub mode 1 bypasses loop A.) 3. If no presence is indicated, change your gate mode to base 1, sub 1 to see if there is a vend signal. 4. If you have a vend signal to the gate in base mode 1, sub mode 1, change the base and sub mode back to the original base and sub mode, and try using another controller. If you do not have another controller, make sure there is presence at the B loop by following the above steps for the B loop. 5. If there is a B presence, remove the wires for the A and B loops from the Omega backplane board, and place the wiring for the B loop into the board in the A loop position. If the LED for A indicates there is an A presence (actually from the B loop), the 66 • Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual A loop is faulty. 6. If there is no A presence, you may have a faulty controller or a faulty path to the controller via the backplane board. Make sure none of the leads on the Omega Controller are bent. For further troubleshooting, loop analyzers are available for testing loop frequency. I am getting erroneous transient backward and illegal forward messages from gates installed in a parking deck structure. What could be causing this? There is normally rebar or wire mesh in the concrete of a parking structure. We recently had a case in which the detector loops were placed below the level of the wire mesh. The detectors will not function properly in this situation and can give you these erroneous messages. The loops should be placed no more than one inch deep, and they must be above any wire mesh or rebar. Careful consideration should be given to loop placement and deck architecture when installing lane equipment in these situations. Please consult with the 3M Systems Engineering Department if you have any questions or concerns about a particular installation. Why does my Reversing lane constantly show “illegal reverse” or “illegal forward” and generate inaccurate lot counts? This condition can occur with any G-90 CD Gate or G-90 LCD Gate. It can be caused by manually raising the Gate Up switch, or it can be caused by commands in ScanNet or in the gate itself. You can correct this condition and cancel loop counting by using Override (Input A4). This can be accomplished in one of two ways: 1. Hardwire gate Override (Input A4) to Gate Common to a toggle switch or key switch. 2. In ScanNet, wire Gate Common to Control Out (2) to gate Override (Input A4). Then, through ScanNet commands, check Control Out (2) On and send it to the gate. The Gate Arm is Stuck in the Up Position. What should I do? While trouble shooting a gate, don't forget that the gate can actually be working. Sometimes when we think the gate is broken, we overlook the reason why the gate arm will not come down. After changing the omega, we jump to the conclusion that the backplane board is bad if the problem isn't resolved. Think of reasons on why the gate arm is up. Some reasons include the following: *Raise/Lower is activated. In a CG gate, you can remove the wire from terminal 40 to see if normal operation is restored. After identifying that the input is constantly shorted, determine why the input is shorted. Causes of this occurring can be something as innocent as a mechanically latching switch left closed, shorting terminal 40 to common *The safety edge switch is shorted, and constantly telling the gate that there is something in the path of the gate arm. If your CG gate has a safety edge, remove the wire from Troubleshooting Manual 78-0060-4094-9, Ver. 1 Gate • 67 terminal 39 to see if normal operation is restored. If normal operation is restored, then the safety edge switch is shorted. Replace the switch. *Over-ride is activated in an LCD or CD gate. You can remove the wire from terminal 4 to see if normal operation is restored. After identifying that the input is constantly shorted, determine why the input is shorted. Causes of this being on can be a mechanically latching switch has been left closed, shorting input 4 to common. Remember, with LCD and CD gates, we have the benefit of input LED's to tell us what input has been activated. If we see that LED 4 (Override) or LED 8 (Raise/Lower) is constantly lit, we know that the gate arm will not come down until both of these input's are out. Solutions may vary for different gate models. Check the following: All Gates: 1. Check for power, circuit breaker feeding power to the operator, or internal fuse. Check position of the "power" and "auto/manual" switches. The power switch should be in the "on" position and the auto manual switch should be in the auto position. 2. Has the thermal overload been tripped on the motor? (red reset on the bottom of the motor, push hard) 3. Have the drive belts inside the operator broken or fallen off? 4. Is the gate arm wedged against an object? 5. Is there more than one device controlling the opening? 6. Is the Safety Edge circuit tripped? 7. Is the motor control relay stuck in? 8. Are both limit switches made? G-90/500 Gates: 1. Is the opening signal contact remaining constant? For example, card reader output, push button, radio receiver 2. Is the primary power properly polarized, thus making shorted field wires vend gate? 3. Is the loop detector presence light on or has the fuse on the loop detector blown creating a constant presence output? Motor Troubleshooting Take both limit switches off. Take the gate arm off. Normal Operation: Put the gate switch in the up (manual) position. The gate arm will move as if it is going up. Put the gate switch in the auto (down) position. The gate arm will move as if it is going down. Troubleshooting: Check the wiring on the gate motor itself. Wiring for the two very different motors in our G90 gates. Lesson Motor: White to L1----- Red to Middle---- Blue to L2 68 • Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual Franklin Motor: White to L1----- Red to L2----Blue to Middle Check the wiring on the motor plug. From left to right in all gates, the wiring should be: Red, Blue, . *If the Red and Blue wires are switched, then the gate will operate backwards. *If the White wire is in any other position other than the correct position, motor damage may occur. Loops vs. Frequency The frequency on adjoining lanes should be separated by 20KHZ minimum or more to avoid “cross talk”. An optimal range for each loop is between 220KHZ and 380KHZ. Generally, the B loop will be higher than the A loop. The difference between A-High (switch on the omega) and A-Low will be approximately 20K minimum. The same theory applies to loop B. G89 Gate-I am using an MP-6000 (black box). When a car vends the gate while on loop B, the arm goes up about 6 inches, and comes right back down. If the patron holds the card in the reader, it will eventually vend. Is there something I can check? Open the MP-6000, and look to see if K3 is wired correctly. K3 is the small relay mounted on the opposite side of the power plug. Make sure that the black wire (common) is going to contact number 7 (B Common). If it is on 9 (A Common), you have to desolder the wire and move it to the correct contact. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Gate • 69 70 • Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual Lane Troubleshooting Troubleshooting Loop Detection for a G-90 LCD or CD Gate. If you are experiencing any difficulties with loop detection, try these steps for troubleshooting: 1.Place a metal gate door on the ground over loop A in front of the card reader, Ticket Spitter, or other device that may be inhibited. The loop under the gate door acts like a metal detector. 2.Inside the gate, look at the LED lights under A on the Omega controller and determine if the blinking LED light under T (tuning) has changed to a solid LED light under P (presence). If your device is in a base mode/sub mode other than base mode 1, sub mode 1, this would indicate that the loop is enabled. (Base mode 1, sub mode 1 bypasses loop A.) 3.If no presence is indicated, change your gate mode to base 1, sub 1 to see if there is a vend signal. 4.If you have a vend signal to the gate in base mode 1, sub mode 1, change the base and sub mode back to the original base and sub mode, and try using another controller. If you do not have another controller, make sure there is presence at the B loop by following the above steps for the B loop. 5.If there is a B presence, follow these steps to test the A loop: a. Remove the wires for the A and B loops from the Omega backplane board, and place the wiring for the B loop into the board in the A loop position. b. If the LED for A indicates there is A presence (actually from the B loop), the A loop is faulty. If there is no A presence, you may have a faulty controller or a faulty path to the controller via the backplane board. Make sure none of the leads on the Omega controller are bent. For further troubleshooting, loop analyzers are available for testing loop frequency. TD-249 to CD gate What color wires are you using for the following terminals?: Ticket Spitter CD Connection Panel 5------------------------A7 (Ticket Request Input) 7------------------------A2 (gate vend) 8------------------------A17 for LCD/A13 for CD (Gate common) 3------------------------C4 (Ticket Issue Common) 4------------------------D4 (Ticket Issue) Each color you are using at the Ticket Spitter must match up with the color wire used at the gate. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Lane Troubleshooting • 71 Once you verify that all the wiring is correct, test the gate first: During this test, ignore the Spitter completely. Do not pull the ticket and let the buzzer go off while the ticket is in the throat. At the gate, take a piece of wire approximately 1 foot long to jumper terminals for testing to simulate different inputs to the gate. Step 1: If you are not already in Base Mode 2, Sub Mode 3, put the gate in this mode. Place a gate over loop A to simulate a car being on the loop. At the gate, you will notice that the LED under A on the Omega Controller has stopped blinking on T (tuning), and is now solid under P (presence). If you do not get this result, see Troubleshooting Loop Detection for a G-90 LCD or CD Gate. Step 2: Inside the CD gate, jumper A13 to A7. You will see the LED for input 7 come on while this contact is being made. This contact is only momentary, so you will touch the two terminals once and remove the jumper. This is your ticket request, and by shorting this input, a ticket should be dispensed at the Spitter. Ignore the Spitter for now. Step 3: Inside the CD gate, jumper A13 to A2. You will see that the LED for input 2 will come on while the contact is being made. This is also a momentary contact, and as soon as the gate starts to raise, you can remove the jumper. This is your gate vend B, and by shorting this point after shorting the ticket request, the gate will raise. If the gate does not raise, then the problem with the lane is in the Gate. Initialize the gate’s Omega Controller and repeat steps 1-3. If the gate still does not raise, initialize the memory in the Omega Controller, and repeat steps 1-3 above. If the gate still does not raise, go to monitoring/config/settings, and see what Base Mode Sub Mode the Omega Controller is registering as. If it is anything other than Base Mode 2 Sub Mode 3, check DIP switch 1 on the connection panel. It should be set for 1,3, and 5 closed, everything else open. If it is not set correctly, change settings, and initialize the gate. Go to monitoring/config/settings again, and check the Base/Sub mode. If it is still not Base Mode 2 Sub mode 3, then you have any of these three problems: 1. The Omega is not recognizing the correct Base/Sub mode because of internal circuitry, which has gone bad. Replace the Omega Controller. 2. The Connection panel has a bad path between the Config Module and the Omega Controller. Replace the connection panel 3. You have a bad Config Module. Replace the Config Module with one that is working correctly. You can also try putting the gate in No Config mode to see if the Controller will work via an alternate route to DIP switch #4 on the Connection panel. 72 • Lane Troubleshooting 78-0060-4094-9, Ver. 1 Troubleshooting Manual On DIP switch #4 on the Connection panel (Top Left), set the DIP switches for the following Base Mode 2 Sub Mode 3. This is No Config Mode #3, DIP switch 4 all open. With the power off, take out the config module, and initialize the gate. Go into Monitoring/Config Settings, and see if it says Base Mode 2 sub mode 3. If it does, then repeat steps 1-3 described above. If the gate still does not raise, replace the Omega Controller with another one that is in a working gate, and then test the lane again. If the gate still does not raise, use the override switch to see if the gate will raise. If the gate goes up, this proves that the mechanics of the gate are in working condition, and the controller is faulty for not sending the proper signal to the relay that controls the gate arm. If the gate still does not raise, go into menu, commands, raise gate. If the gate goes up, it proves that all inputs and outputs are good. If the LED for Gate Up comes on, but the gate does not raise, then the problem is going to be one of the following: 1. The path to the input or output is bad 2. The input or output relay on the controller is bad 3. Both the Omega Controller and the path on the connection panel are bad. Swap out suspected bad parts with known good parts to test thoroughly. Once you have the gate operating correctly, test the lane out as described in the beginning of the document. If you have trouble after verifying that the gate is good, then the problem is going to be with the Spitter. 95% of the time when there is a problem with a lane, the problem is going to be with the gate. LCD or CD gate/Passport Plus Card reader/No arming. Make sure that the Omega is in Base mode 1, Sub mode 1. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Lane Troubleshooting • 73 Step 1. Switch Bank 1 for the config module, has to be set to the following: 1 – Closed 2 – Closed 3 – Open 4 – Closed 5 – Closed 6, 7, and 8 are unused (keep open) If it is not, turn the gate off, and change the DIP switches to the above setting. Initialize by holding the monitor/menu button down and turning the gate on while continuing to hold the button down until you see the words monitor and menu flashing back and forth on the display. Step 2 At the Omega, go to Monitor> Config> Settings. Make sure that the Omega thinks it is in B1 S1. This indicates Base mode 1 Sub mode 1. If the Omega does not indicate that it is in B1 S1, then you have any of these three problems: 1. The Omega is not recognizing the correct Base/Sub mode because of internal circuitry, which has gone bad. Replace the Omega Controller. 2. The Connection panel has a bad path between the Config Module and the Omega Controller. Replace the Connection panel. 3. You have a bad Config Module. Replace the Config Module with one that is working correctly. You should try to put the gate into No Config mode if you suspect that the controller is good, and that the path to DIP switch 4 is good. We can bypass the config module by putting the gate in No Config mode. No Config Mode: Turn the Gate off and pull out the config module. Set DIP switch 4 to the following: 1 – Closed 2 – Open 3 – Open 4 – Open 5, 6, 7, and 8 are unused (keep open) Initialize by holding the monitor/menu button down and turning the gate on while continuing to hold the button down until you see the words monitor and menu flashing back and forth on the display. Repeat step 2 above and see if the Omega indicates that it is in B1 S1. If it still does not, 74 • Lane Troubleshooting 78-0060-4094-9, Ver. 1 Troubleshooting Manual then you have one of the following 2 problems: 1. The Omega is not recognizing the correct Base/Sub mode because of internal circuitry, which has gone bad. Replace the Omega Controller. 2. The Connection panel has a bad path between the Config Module and the Omega Controller. Replace the Connection panel. Step 3 Take a jumper wire, and short between Common, (A17 on a LCD gate) or (A13 on a CD gate) to A1. You will notice that the input LED 1 will come on while the contact is being made. This is a momentary contact, so as soon as the gate starts going up, you should take the jumper off of the gate. This is your gate vend A, and by shorting this point the gate will raise. If the gate does not raise, perform a memory dump by turning off the controller power and closing DIP switch 2 (service only). Wait 5 minutes for the battery to be discharged, and open the switch again. Initialize by holding the monitor/menu button down and turning the gate on while continuing to hold the button down until you see the words monitor and menu flashing back and forth on the display. Repeat step 3. If the gate still does not raise, use the override switch to see if the gate will raise. If the gate goes up, this proves that the mechanics of the gate are in working condition, and the controller is faulty for not sending the proper signal to the relay that controls the gate arm. If the gate still does not raise, go into menu, commands, raise gate. If the gate goes up, it proves that all inputs and outputs are good. If the LED for Gate Up comes on, but the gate does not raise, then the problem is going to be one of the following: 1. The path to the input or output is bad 2. The input or output relay on the controller is bad 3. Both the Omega Controller and the path on the Connection panel are bad. Swap out suspected bad parts with known good parts to test thoroughly. Move the gate door or your piece of metal over loop B. This is going to fool the gate into thinking that there is a car on the loop. At the gate, you will notice that the LED under B on the Omega Controller has stopped blinking on T (tuning), and is now solid under P (presence). If you do not get this result, see Lane Troubleshooting - I think my loops are bad. How can I trouble shoot them? Take the gate door off of the loop, and the gate will reset itself. If it does not, then you will be experiencing Omega Controller problems. Replace and retest. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Lane Troubleshooting • 75 76 • Lane Troubleshooting 78-0060-4094-9, Ver. 1 Troubleshooting Manual LCD or CD Gate Basic Inputs and Outputs In order to verify what is programmed on the config module, you can view the config Input/Output options or settings. Config #23-16023 is a basic config for gates, and Config #23-16014 is a basic communicating gate config. To check Input/Output options, perform the following steps: 1. In Monitor mode, press the Config button until you see the menu you are looking for. 2. Once you have found the menu you want to view, press the Scroll button to scroll through the options. You can view the options in this window, or you can see what inputs or outputs are defined in the Input or Output menu. The table below lists the basic inputs and outputs associated with the LCD Omega. Basic Inputs Basic Outputs 1 - Vend A 1 - Gate Up (Normally Open)* 2 - Vend B 2 - Gate Up (Normally Closed)* 3 - Rebound 3 - Vend A Enable 4 - Override 4 - Vend B Enable 5 - Full A 5 - Pulse A 6 - Full B 6 - Pulse B 7 - Ticket Request 7 - Presence A 8 - Raise/Lower 8 - Presence B 9, 10, 11 - Undefined 9 - Illegal Forward 12 - Config/Tune 10 - Illegal Reverse 13, 14, 15, 16 - Undefined 11 - Monthly Forward 12 - Transient Forward *There are two Gate Up outputs because the gate is connected to a double pole/double throw relay, so one is always going to be active. Settings tell the operator what base mode and sub mode the gate is working in and also list sensitivities and device numbers. Not Reading Config Module If you have a new Model G-90 LCD Series Barrier Gate and have been swapping Configuration Modules between gates, you may notice that the gate may not operate as expected. The reason for this may be because the Omega LCD Controller is not reading the config. Try this simple procedure. Power down the gate and remove the Omega LCD Controller. Close DIPswitch #2 for five minutes and then reopen. Plug the Omega back in Troubleshooting Manual 78-0060-4094-9, Ver. 1 LCD or CD Gate • 77 and cold start the unit. This procedure will ensure that the new config setting is read correctly. Cold-starting the Omega Controller in the G-90 CD Gate Holding down the monitor/menu key while turning on the Omega controller may erase memory. The sensitivity will revert to default and the time zone programming may be erased. Every time the Omega controller is powered, it will automatically reload the config settings regardless if you hold down the monitor/menu key or not. Break the bad habit of holding down the monitor/menu key every time you turn the gate back on. *if your hardware locks up or does not respond to just turning the CD gate off and back on, you still may need to cold-start the Omega. Perform a cold-start by holding the Monitor/Menu button down and turning the gate on while continuing to hold the button down until you see the words “monitor” and “menu” flashing back and forth on the display. If you are just performing preventative maintenance on the gate, it is not necessary to cold-start the gate. Using EDC-1000 to Stop Free Gate from Vending When Desired Count is Reached If a customer has a G-90 CD gate set as base mode 2, sub mode 1(free gate) connected to an EDC-1000, you can set the counter to stop the gate from vending when the EDC-1000 reaches a desired count by changing wiring at the gate as described in the following steps: 1. Set the gate to base mode 2, sub mode 3 and change the wiring so the full B input (A6) can be used. 2. Install a jumper wire from A2 to D4. 3. Install a jumper wire from A7 to common. 4. Install a jumper wire from C4 to common. 5. If A6 is not pulled to common, as soon as a patron drives on loop A, the gate will raise as if it is in free mode. 6. Once you pull A6 to common, the gate will not let the patron enter the lot due to the full B input. 7. Wire the EDC 1000 so the normally open contact is between A6 and common. 8. When the EDC 1000 reaches 0 (counting down), the contact will close, pulling A6 to common. Multiple Readers Operating from One Built-in Power Supply on the G-90 CD Gate If you plan to use multiple read heads wired to one Passport Plus controller, you may do so by wiring the read heads parallel to each other. Both of the read heads will be powered from the same Passport Plus controller. If one of the read heads has a Wiegand setting, and the other read head uses a Dyna setting, then you are need two different Passport Plus controllers because of the different shunt settings and programming. If you are planning 78 • LCD or CD Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual to use multiple Passport Plus controllers in a lane, you can only operate one Passport Plus controller per power supply. Warning Labels The WARNING label will now be applied to both sides of the gate cabinet. Both labels will be centered and approximately 8 inches below the top of the gate cabinet. Circuit Board Redesigned The circuit board has been redesigned using surface mount components and flash memory. The flash memory eliminates the use of EPROMS and allows the firmware to be updated using a computer or laptop with the FlashProgrammer software (available from the 3M web site along with new firmware). Tactile switches and keycaps were replaced with a membrane keypad. The LCD display mounting hardware was removed. The PCB and enclosure are now procured as a complete assembled unit from the assembly house. Losing Programming Powering the LCD/CD Gate You lose programming if you have older version firmware in the LCD or CD Omega. When powering up the gate with older firmware, you must not “cold start” the Omega. That is, you must not hold down the Menu key while powering up. The only time you should cold start the Omega is when changing configuration settings or if the unit is locked up. You will need to reprogram certain items upon cold starting, such as time zones, ValueCard IDs, back-out timers, and sensitivity settings. 3M recently released two new versions of the G-90 CD Gate (Versions B2.4.4 and C3.0.1). With these new versions, six programmable functions will retain their value, and not revert to the default value, even during a push-button Cold Start, that is, when the Monitor/Menu button is pressed while the gate electronics are being power-cycled. These six functions are: 1. No-loop backout time 2. Loop backout time 3. Gate up arm 4. Rebound up time 5. Rebound sensitivity 6. Broken arm sensitivity Master/Slave CD Gate Both the master and slave gate have to be in Base mode 2 sub mode 3. You must have either standard configs (CD-16023) or standard communicating (CD-16014) configs to operate. Verify that the monitoring config outputs D16 and C16 are active. These are normally open contacts. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LCD or CD Gate • 79 Wiring for the gates are as follows: Master Slave C16-------------A8 Raise/ Lower D16-------------A14 Common Omega Displays only Black Bars This can happen upon installation or can occur suddenly after the gate has been working fine. The Omega LCD program has possibly degraded as the backup Supercap power was discharged while the gate was in storage and/or unplugged. The supercap did not completely discharge and the program did not completely collapse. The Omega LCD has to have been unplugged for several weeks for this discharging to take effect. Because it cannot easily be determined how long the Omega LCD may have been stored before the gate was installed, it is a good idea to perform the following service action after any G-90 LCD gate installation: 1. Power down the Omega. 2. Close DIP switch #2 on the Omega and wait five minutes. 3. Reopen DIP switch #2. 4. Hold down the monitor/ menu key while powering back up until the display reads monitor/menu. This is considered a cold start with memory initialization. All programming will be lost after performing this procedure. LCD Gate: Loop Detector not Resetting after Tailgate If you have a Model G-90 LCD Series Barrier Gate, sensitivity switch #4 should be open to avoid concerns such as the loop detector not resetting after tailgate detection. To ensure proper operation, be sure that switch #4 is open on all Model G-90 LCD Series Barrier Gates. CD Gate Introduction 3M began shipping an enhanced version of the popular Model G-90 LCD Series Gate, called the Model G-90 CD Series Barrier Gate. The “CD” stands for Compact Design, which describes the main difference between the LCD gate and the CD gate. The compact design connection panel used in the CD gate combines functions of the power board and the terminal connection board used in the LCD version into a single board. In addition to reducing the space requirements in the gate, the enhanced design provides many other benefits. For example, by reducing the number of parts, we greatly improved the gate’s reliability—a key objective of the CD connection panel. Some of the improvements included in the CD connection panel included the following: * Elimination of one entire circuit board assembly. * Elimination of the interconnection cable between the power board and the terminal connection board. * Elimination of one of the transformers. A new single transformer handles all power 80 • LCD or CD Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual requirements. * Elimination of most wire crimps. The panel uses PC mounted switches and other components that virtually eliminate the rest of the wires and crimps on the LCD power board. * New configuration module design with new technology for improved performance. * Improved manufacturability for consistent quality. * Pluggable terminal strips to enhance, simplify, and automate production testing. The pluggable terminal strips will significantly simplify the process required for changing connection panels in the field as well as installation and service. The terminals used are the same as those used on the Passport Plus, Auditor PowerPad and other 3M products. The terminal numbers are consistent with the LCD connection panel so there is no need to relearn the system. Because spare terminals and some of the Input Common terminals have been removed, new engineering drawings are available. The FSO (full sign output) relay is now standard in every G-90 CD gate and the second auxiliary relay is still available as an option. The mounting brackets on the new CD panel are compatible with the mounting facilities of both the G-90 and G-90 LCD gates for compatibility and upgrade ability. The existing Omega LCD is also directly compatible with the new CD connection panel. The new Configuration Module is a small, compact module that has been potted for protection and handling. The device is an encapsulated pc board that utilizes surface mounted technology. This factory-programmed micro controller (a 20pin, 8-bit, fully static, EPROM/ROM-based micro-controller) plugs into the power board and defines the software options used in the gate. The configuration DIP switches are no longer located on the Config Module. The switches are now positioned on the connection panel itself making it easier to replace and exchange Config Modules. Testing has shown the new design technology used in the Config Module to be more robust with varying power conditions. The new CD connection panel is also standard in all current production models of SST Ticket Spitters and Exit Verifiers. The SST version includes a new 24 VDC fan that improves performance and simplifies operation with various international requirements. Rebound Circuit The Model G-90 CD Gate has a Rebound Circuit which forces the gate arm to move upward when a load increase causes an increase in circuit current. The Rebound Circuit protects customers from getting trapped under the gate arm and being injured. The Sensitive Reversing Logic on a limited number of G-90 CD Gates shipped between June 11, 1999 and June 30, 1999 may not operate as expected. Rebound resisters may have been inadvertently transposed. On 120 volt gates, the rebound may be continuously triggered during normal operation, while on 220 volt gates, the rebound may not be tripped when initiated properly. To remedy this situation, a jumper located under the CD connection panel must be moved in order to apply the correct resistance. Orders affected by this situation have been tracked and customers have been informed of the situation and its remedy. What To Do For 120V gates, verify that the Rebound Circuit is not too sensitive by vending and resetting the gate with a gate arm attached. If the Rebound Circuit is tripped with no Troubleshooting Manual 78-0060-4094-9, Ver. 1 LCD or CD Gate • 81 pressure applied to the gate arm, follow the instructions below or contact a Customer Service Representative. For 220 volt CD Gates, contact a Customer Service Representative. Instructions for changing the jumper on the Model G-90 CD Gate (120V) 1. Turn the gate power OFF. 2. Disconnect the gate from AC power source. 3. Remove the Omega LCD Controller. 4. Remove the three (3) 9/16 inch ring nuts on the control switches. 5. Gently lift the aluminum cover up and off the PC board. If necessary, disconnect the wires from the tabs of the convenience outlet. Otherwise, hold the cover out of the way. 6. Inspect the two (2) resistors in locations R1 and R2. Resistor R1 should be a 470W (Yellow-Violet-Brown). Resistor R2 should be 1.8k W (Brown-Gray-Red). If the values are correct, go to step 12. If R1 and R2 are transposed, go to step 7. 7. Locate the “VSEL” jumper on the right side of the PC board. Figure 1 shows a section of a normal G-90 CD Gate Connections Panel with the VSEL label. 8. Remove the jumper. 9. Install the jumper onto the existing 240 position. 10. Place correction label over existing PC board silk-screening. The jumper should now be on 120 position. Figure 2 shows a section of a G-90 CD Connections Panel on which the jumper position has been changed. 11. If disconnected, reconnect outlet wires. 12. Reinstall cover by setting the two tabs into the holes in the PC board and placing the cover over the board. 13. Fasten the cover with the three ring nuts. 14. Reinstall the Omega LCD Controller. 15. Reconnect the AC power. 16. Turn the gate ON. The rebound should now work properly. LCD/CD B Platform Omega Communication Wave Forms Using a digital oscilloscope on the 422 communications plug, pins 1 and 2 should look like the following waveform, with the scope set to 1V per division, set at 10ms, and probe set to 1X: 82 • LCD or CD Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual On the 422 communications plug, pins 4 and 5 should look like the following waveform, with the scope set to 1V per division, set at 10ms, and probe set to 1X: *You will get two waveforms if you have an 8 MB Crystal in the Port Controller. If you have a 4 MB Crystal in the Port Controller, you will only see one waveform. *Pin 3 is ground, so there should be no waveform. LCD/CD C Platform Omega Communication Wave Forms Using a digital oscilloscope on the 422 communications plug, pins 1 and 2 should look like the following waveform, with the scope set to 1V per division at 1ms: On the 422 communications plug, pins 4 and 5 should look like the following waveform, with the scope set to 1V per division at 1ms: *You will get two waveforms if you have an 8 MB Crystal in the Port Controller. If you have a 4 MB Crystal in the Port Controller, you will only see one waveform. *Pin 3 is ground, so there should be no waveform. Omega Version C3.0.5 and B2.4.8/No Config Mode Problems Configs with the EPROM versions mentioned above don't work in no config mode. Customers will either have to burn an older version EPROM, update to the latest C3.0.5, or get a config module that works into the gate until they can update their firmware. These firmware versions were released so that gates used with the Omega now use the proper default configuration values for inputs 1-5 when they are run without a Troubleshooting Manual 78-0060-4094-9, Ver. 1 LCD or CD Gate • 83 configuration module. Also, the issue that caused the Omega gates to occasionally ignore the “lot full” signal was corrected. Version B2.4.7 and C3.0.4 3M released two versions of the Omega LCD Controller (versions B2.4.7 and C3.0.4). In these versions, an initialize no longer causes a false “Broken Arm” message. Version C3.0.1 The following changes are included in version C3.0.1s of the SST Omega Controller (standard): * The firmware works with both the old and new serial chip for communications with the SST Transport as well as the PC language display. * The amount of time the SST Omega Controller waits for a response from the SST device has been lengthened. This prevents the SST Omega Controller from timing out when a transient ticket is issued, which prevents another ticket from being issued. * The default configuration values have been changed so that the SST Ticket Spitter/Exit Verifier can run without a configuration module. Version B2.6.0 The following changes are included in version B2.6.0s of the SST Omega Controller (standard): * The amount of time the SST Omega Controller waits for a response from the SST device has been lengthened. This prevents the SST Omega Controller from timing out when a transient ticket is issued, which prevents another ticket from being issued. * The default configuration values have been changed so that the SST Ticket Spitter/Exit Verifier can run without a configuration module. Version B2.1.2 3M has changed the handling routines for transient and monthly disable commands sent from SCAN to the Omega LCD. The reason for the change, which was implemented in version B2.1.2 of the firmware, was to ensure that all vehicles can exit a facility as appropriate during “lot full” situations. Version B2.1.1 To help with troubleshooting in the field, 3M has added a “Ticket Issue” message to the event history for the LCD Gate with the Omega LCD Controller (Version B2.1.1). This message appears immediately following a Ticket Request (TKT REQ) message if the gate accepts the request and sends a signal to the Ticket Spitter to issue a ticket. If you experience a situation in which a ticket is not issued as expected, you can use this feature to help determine the reason for the ticket not being issued. 84 • LCD or CD Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual Version B2.1.0 This new version allows you to distinguish credit card transactions from other types of transactions for tracking purposes. Base Mode 5 Sub Mode 1 Does Not Work Base Mode 5 Sub Mode 1 requires a straddling of loop C and A and then just an A presence in order to auto issue from the ticket spitter. The manual defines the distance between loop C and loop A as 11’. There are cars that fall short of this measurement and they will never be able to be on both loops at the same time, and they will not be able to activate the auto issue in order to enter the lot. On the other side of the spectrum, If the car is longer than 11’, (like a truck), they never leave loop C, and they will not be able to get a ticket from the auto-issue ticket spitter either. Base Mode 5 Sub Mode 1 does not work, but there is a workaround that keeps the basic idea for this mode operational. You have to operate the gate in Base Mode 2 Sub Mode 2, and manually hook up Loop C to inhibit the card reader. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LCD or CD Gate • 85 Mode DIP Switch Settings Base Mode 1 Sub Mode 1 > Pay in with no arming loop. 1 2 3 4 5 6 7 8 Closed Closed Open Closed Closed Open Open Open Base Mode 2 Sub Mode 1 > Pay in free out. 1 2 3 4 5 6 7 8 Closed Open Closed Closed Closed Open Open Open Base Mode 2 Sub Mode 2 > Pay in with arming loop for auto spitter only. 1 2 3 4 5 6 7 8 Closed Open Closed Closed Open Open Open Open Base Mode 2 Sub Mode 3 > Pay in with arming loop for push-button spitter/ card reader. 1 2 3 4 5 6 7 8 Closed Open Closed Open Closed Open Open Open Base Mode 3 Sub Mode 1 > Pay in, Pay out with arming loop for entry and exit devices. 1 2 3 4 5 6 7 8 Closed Open Open Closed Closed Open Open Open Base Mode 3 Sub Mode 2 > Pay in Pay out with arming loop for entry auto spitter and exit devices. 1 2 3 4 5 6 7 8 Closed Open Open Closed Open Open Open Open Base Mode 3 Sub Mode 3 > Pay in Pay out with arming loop for entry auto spitter and exit Fee Computer. 1 2 3 4 5 6 7 8 Closed Open Open Open Closed Open Open Open 86 • LCD or CD Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual Base Mode 5 Sub Mode 1 > Pay in Pay out with arming loop for entry reader and auto spitter only. (Does not work, see above) 1 2 3 4 5 6 7 8 Open Closed Open Closed Closed Open Open Open Base Mode 5 Sub Mode 2 > Pay in Pay out with escape lane. 1 2 3 4 5 6 7 8 Open Closed Open Closed Open Open Open Open Base Mode 6 Sub Mode 1 > Pay in Pay out with directional arming loop for entry devices. 1 2 3 4 5 6 7 8 Open Open Closed Closed Closed Open Open Open Omega Controller Counts Option Configuration modules for the LCD Omega and the SST Omega Controllers have a large number of options that you can purchase. One group of options that is least understood is called Counts. You purchase each Count option individually when you want to be able to count activity in an off-line parking system. In order to get access to the Count information, you may have external counters (such as the EDC 1000) wired to Count outputs or you may get information manually from the LCD or SST Omega Controller directly. If you have SCAN software, you have access to the most often used Count values. SCAN uses various status and report displays to give these statistical values. If you do have off-line options in any of your configuration modules, you will see them on the SCAN Reports/G-90 LCD Counter Report screen. Normally, this screen has four counters used with SCAN that are resettable and non-resettable. These counters include the Motor Current Rebound, the Rebound Presence B, the Tune Loop, and the Power Up. All other Counts are individually purchased external options. They may be resettable only, non-resettable only, or a mixture of both. SCAN detects these external Counts, and the software allows you to reset the resettable counters. Each time you perform a cold start, you lose all resettable values in either SCAN or off-line system Omega Controllers. You can get access to all other SCAN countable statistics by using the monitor system screens listed below: Monitor GATE system • Single LANE status (includes ILL FWD or REV and BACKOUT, etc.) • All LANES status (indicates normal parking sequence of activities) • Single LOT counts (shows current parking lot conditions and total ILL FWD or REV) • All LOT counts (shows the same as above but includes all lots configured in SCAN) • All AREA counts (includes counts for each separate area of the lot) Monitor READER system • Monitor FACILITY counts (total counts in parking lot) • Monitor PEAK counts (total counts in the highest count time period) Troubleshooting Manual 78-0060-4094-9, Ver. 1 LCD or CD Gate • 87 SCAN Count information is scattered among the above screens in the system. In an offline system, the information has to be pulled manually from the LCD or SST Omega Controllers. Lane Troubleshooting TD-249 Barcode Ticket Spitter and G-90 CD Gate You can use these notes to troubleshoot any problems with a TD-249 and G-90 CD gate lane. First, note which wire colors are going to which terminals on the TD-249 Ticket Spitter connection panel. Also note what wire colors are going to what terminals between the two connection panels. Each wire color you are using at the ticket spitter must be the same color wire used at the gate according to the following wiring diagram: Connection Panel for the Spitter: Connection Panel for the Gate: 5 A7 (Ticket Request Input) 7 A2 (gate vend) 8 A13 (gate common) 3 C4 (Ticket Issue Common) 4 D4 (Ticket Issue) Once you verify that all the wiring is correct, test the gate. During this test, ignore the Spitter completely. Do not pull the ticket, and let the buzzer go off while the ticket is in the throat. At the gate, take a piece of wire approximately 1 foot long to jumper terminals for testing to simulate different inputs to the gate. * Step 1: If you are not already in Base Mode 2, Sub Mode 3, put the gate in this mode. Place a gate door over loop A to simulate a car being on the loop. At the gate, you will notice that the LED under A on the Omega Controller has stopped blinking on T (tuning), and is now solid under P (presence). If you do not get this result, see G-90 CD/LCD FAQs Gate Loop Detection. * Step 2: Inside the CD gate, jumper A13 to A7. You will see the LED for input 7 come on while this contact is being made. This contact is only momentary, so you will short the two terminals one time and then remove the jumper. This is your ticket request, and by shorting this input, a ticket should be dispensed at the Spitter. Ignore the Spitter for now. * Step 3: Inside the CD gate, jumper A13 to A2. You will see the LED for input 2 come on while this contact is being made. This is also a momentary contact, and the jumper should be removed as soon as you see the LED light up. After the LED for input 2 lights up, the gate should start to raise. This is your gate vend B, and by shorting this point after shorting the ticket request, the gate will raise. If the gate does not raise, then the problem with the lane is in the Gate. Cold start the gate and repeat steps 1-3. Perform a cold start by holding the Monitor/Menu button down and turning the gate on while continuing to hold the button down until you see the words “monitor” and “menu” flashing back and forth on the display. If the gate still does not raise, perform a memory initialization by turning the controller power off and closing DIP switch 2 (service only.) Wait 5 minutes for the battery to discharge, and open the switch. Perform a cold start as described on page 3 in step 3. If the gate still does not raise, go to monitoring/config/settings, and see what Base Mode Sub Mode the controller thinks it is in. If it is anything other than Base Mode 2 Sub Mode 3, then check how DIP switch 1 on the connection panel is set. It should be set as 88 • LCD or CD Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual follows: DIP Switch Bank 1 1 - Closed 2 - Open 3 - Closed 4 - Open 5 - Closed 6 - Closed 7 - Closed 8 - Closed * 6, 7, and 8 should be kept closed in the G-90 CD gate so that it will display the correct Base Mode, Sub Mode in the ScanNet System Activity Monitor. If a DIP switch was not set correctly, change the DIP switch as shown in the example and perform a cold start as described on page 3 in step 3. Go to monitoring/config/settings again, and check the Base/Sub mode. If it is still not Base Mode 2 Sub mode 3, then you have any of these three problems: * The Omega is not recognizing the correct Base/Sub mode because of internal circuitry, that is malfunctioning. Replace the Omega controller. * The connection panel has a bad path between the config. module and the Omega controller. Replace the connection panel. * You have a malfunctioning config. module. Replace the config module with one that is working correctly. If you suspect that the config. module is bad, put the gate in No Config mode. To operate in No Config mode, set all the switches on DIP switch bank 4 on the connection panel to open. With the power off, take out the config module, and cold start the gate as described on page 3 in step 3. Go to monitoring/config settings, and see if the gate registers Base Mode 2 Sub Mode 3. If it does, then repeat steps 1-3 described above. If the gate still does not raise, replace the Omega controller with another one that is in a working gate, and then test the lane again. If the gate still does not raise, use the override switch to see if the gate will raise. If the gate raises, this proves that the mechanics of the gate are in working condition, and the controller is faulty for not sending the proper signal to the relay that controls the gate arm. If the gate still does not raise, go to menu/commands/raise gate. If the gate raises, it proves that all inputs and outputs are good. If the LED for Gate Up comes on, but the gate doesn’t raise, then the problem is one of the following: * The path to the input or output is malfunctioning. * The input or output relay on the controller is malfunctioning. * Both the Omega controller and the path on the connection panel are malfunctioning. Swap out suspected bad parts with known good parts to test thoroughly. Once you have the gate operating correctly, return to step 1 in the beginning of these troubleshooting instructions. If you still experience problems after verifying that the gate is good, the problem is in the spitter. Most of the time when there is a problem with a lane, the problem is going to be with the gate. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LCD or CD Gate • 89 Lane Troubleshooting Passport Plus Card Reader and G-90 CD Gate 1. Check for power, circuit breaker feeding power to the operator, or internal fuse. Check position of the “power” and “auto/manual” switches. The power switch should be in the “on” position and the auto manual switch should be in the auto position. 2. Has the thermal overload been tripped on the motor? (red reset on the bottom of the motor, push hard) 3. Have the drive belts inside the operator broken or fallen off? 4. Is the gate arm wedged against an object? 5. Is there more than one device controlling the opening? 6. Is the Safety Edge circuit tripped? 7. Is the motor control relay stuck in? 8. Are both limit switches made? 9. Switch bank 1 of the connection panel must be set to the following: 1 – Closed 2 – Closed 3 – Open 4 – Closed 5 – Closed 6, 7, and 8 are unused (keep closed) If it is not, turn off and change the DIP switches to the above setting. Perform a cold start by holding the Monitor/Menu button down and turning the gate on while continuing to hold the button down until you see the words “monitor” and “menu” flashing back and forth on the display. 10. At the Omega LCD Controller, go to Monitor> Config> Settings. Make sure that the Omega is in base mode 1, sub mode 1, (B1, S1). If the Omega does not indicate B1, S1, then you have one of these problems: * The Omega is not recognizing the correct base/sub mode because of internal circuitry, which is faulty. Replace the Omega LCD Controller. * The connection panel has a bad path between the configuration module and the Omega LCD Controller. Replace the connection panel. * You have a bad configuration module. Replace the configuration module with one that is working correctly. Bypass the configuration module by setting the gate to No Config mode if you suspect that the configuration module is faulty. Turn the gate off and pull out the configuration module. Set DIP switch 4 on the connection panel to the following: 1 – Closed 2 – Open 3 – Open 4 – Open 5, 6, 7, and 8 are unused (keep open) Perform a cold start as described in step 9. Repeat step 10 above and see if the Omega indicates that it is in B1, S1. If it still is not, then you have one of the following problems: * The Omega is not recognizing the correct base/sub mode because of internal circuitry, which is faulty. Replace the Omega LCD controller. 90 • LCD or CD Gate 78-0060-4094-9, Ver. 1 Troubleshooting Manual * The connection panel has a bad path between the configuration module and the Omega controller. Replace the connection panel. 11. Take a jumper wire, and short the connection panel inputs between A1, (vend A) and A13, (common). You will notice that the input LED 1 will come on while the contact is being made. This is a momentary contact, so as soon as the gate starts raising, take the jumper off. By shorting these contacts we simulate a vend from the reader. If the gate raises by shorting out the inputs, but does not raise when using the reader, then you have a faulty reader. Make sure the ID is valid and go through the usual testing of the reader to fix the problem. The Last Card Report can be helpful when troubleshooting the reader. If the gate does not raise when shorting the inputs, perform a memory initialization by turning the controller power off and closing DIP switch 2 (service only). Wait 5 minutes for the battery to discharge, and open the switch. Perform a cold start as described in step 9. Repeat step 11. If the gate still does not raise, use the override switch to see if the gate will raise. If the gate raises, this proves that the mechanics of the gate are in working condition, and the Omega controller is faulty for not sending the proper signal to the relay that controls the gate arm. If the gate still does not raise, go to Menu> Commands> Raise gate. If the gate raises, it proves that all inputs and outputs are good. If the LED for Gate Up comes on, but the gate does not raise, then the problem is one of the following: * The path to the input or output is bad. * The input or output relay on the Omega controller is bad. * Both the Omega controller and the path on the connection panel are bad. Swap out suspected bad parts with known good parts to test. Move the gate door over loop B. This is going to simulate a car being on loop B. In the gate, you will notice that the LED under B on the Omega controller has stopped blinking on T (tuning), and is now solid under P (presence). If you do not get this result, see Troubleshooting Loop Detection for a G-90 CD Gate under the Gate header above. Take the gate door off the loop, and the gate will reset itself. If it doesn’t, then you will be experiencing Omega controller problems. Replace and retest. Troubleshooting Manual • 91 78-0060-4094-9, Ver. 1 92 • LD-23 78-0060-4094-9, Ver. 1 Troubleshooting Manual LD-23 I have an LD-23 loop detector, and it is not working correctly. Is there some troubleshooting I can do in the field? The nut has to be on the component side of the board. Not the other side. If this is wrong it will short the board. Make sure that the jumper is there between the CPU and U2. If the board still does not function after checking and correcting these problems, then send the board in for repair. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LD-23 • 93 94 • LD-23 78-0060-4094-9, Ver. 1 Troubleshooting Manual LPI New LPI Hand Held Computer With 10K Capacity This new version will offer all the same features of the current Hand Held Computer, with one additional benefit—10K capacity. This means that the new model will be able to hold data for lots with up to 10,000 spaces. Like the current model, this new HHC is based on the PSION Workabout Hand Held Computer. It is equipped with an alphanumeric keypad for entering information. It has a modified user interface, a backlit display for night viewing, and a contrast button, which can be used to lighten or darken the display. Also, like the current model, it will connect to the SCAN Facility Management System or to the ScanNet Central Management System. There will be no operational difference visible to the customer, between the new model and what is currently being shipped. What Is The License Plate Inventory System? The purpose of the License Plate Inventory System is to prevent fraudulent ticket use. It does this by conducting inventories to track how long each vehicle has been staying in a parking facility and comparing this to the entry time for the presented transient ticket. What Is a Hand Held Computer? A Hand Held Computer is a portable device used to collect license plate and state/providence information associated with the vehicles parked in a facility and to transfer that information to SCAN or ScanNet. Information is collected using one of two methods: the Collection method or the Entry method. The Collection method consists of downloading the current information pertaining to a specific area and then driving or walking through the facility to verify the information space by space or to correct the information as appropriate. The information is uploaded upon completion of each area. The Entry method consists of recording the information as vehicles enter an area and then periodically uploading the information. In this method, vehicles are not tied to particular spaces. Here are some notes to keep in mind when using the new LPI HHC. * Unless dealing with small facilities, each operator should only download information on one area of the facility at a time. Once this area is verified and uploaded, a new area can be downloaded for checking. * The size of a single area, or group of areas, downloaded at once is limited to 2000+ spaces. * You can use the OFF button to conserve battery power. Simply hit the ON button where you left off. * The PSION has a contrast button, which you can use to lighten or darken the screen image to suit your taste. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LPI • 95 Scan NT Update: License Plate Inventory The License Plate Inventory (LPI) feature will be included in the release of Scan NT Central Management System Version 3.1.1. The LPI feature for Scan NT is a set of applications designed to collect License Plate data, manage the LPI database, maintain the inventory, and generate reports. These applications can execute on the same or different computers provided they have access to Scan NT and the Scan NT database when needed. Included in the system is a Hand-Held Manager, which enables the user to do the following: *Detect whether a hand-held computer is connected to one of the serial ports *Move data between the Scan NT computer and the hand-held computer *Store information in the database tables The LPI administration and utility tools allow users to perform the following functions: *Access standard reports *Generate reports *Search for a license plate *Maintain a “Hot Plate” list *Manually reconcile inventory data *View the License Plate Inventory table *Edit global license plate parameters, *Configure the rows and spaces in a lot *Configure hand-held computers and serial ports *Maintain the locality list LPI looks up the inventory data as follows: 1. When Scan NT is started, the Lookup Manager starts to manage the instances of the License Plate Find module. 2. Upon request from a Fee Computer, the License Plate Find module looks up a license plate in the database and returns the results to the requesting Fee Computer. Receiving an “LPI PORT OPEN” Message If you ever received an “LPI PORT OPEN” message when connecting the LPI hand held WorkAbout, it means that ScanNet, the modem, or some other application is already using the serial port you are trying to connect to. Check your computer ports and connect the LPI handheld to an unused port. Afterwards, you must configure the LPI system to use the new port. When I try to print a report showing the LPI inventory, I get an Error 1000: field (inv.plate) cannot be a 0 length string. To fix this, you must go to Sybase, search for the offending records, and then delete them directly from the database. Follow the instructions below on how to accomplish this task. 96 • LPI 78-0060-4094-9, Ver. 1 Troubleshooting Manual Choose sa_scan and click OK. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LPI • 97 Right click and view data on table_LPI_INVENTORY This gives you a view of the complete database: 98 • LPI 78-0060-4094-9, Ver. 1 Troubleshooting Manual When you edit the Command to read: SELECT * FROM "scan"."table_LPI_INVENTORY" where inv_Plate='123ABC' You will see it narrow the search down as follows: Delete highlighted areas shown below: In the front of the command, insert the word delete. Hit execute. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LPI • 99 Some more examples on searches: *NOTE the last character is a single quote; single quote, not a double quote. You can search for specific entries by changing this to ‘0’ or ‘00’ SELECT * FROM "scan"."table_LPI_INVENTORY" where inv_Plate='' SELECT * FROM "scan"."table_LPI_INVENTORY" where inv_Plate='0' SELECT * FROM "scan"."table_LPI_INVENTORY" where inv_Plate='00' SELECT * FROM "scan"."table_LPI_INVENTORY" where inv_Plate='000' SELECT * FROM "scan"."table_LPI_INVENTORY" where space_ID='' SELECT * FROM "scan"."table_LPI_INVENTORY" where space_ID='0' 100 • LPI 78-0060-4094-9, Ver. 1 Troubleshooting Manual As long as you keep the spelling of the columns correct, you can search on anything. You must narrow down your search before deleting anything, to prevent deleting good information. *NOTE the last character is a single quote; single quote, not a double quote. Troubleshooting Manual 78-0060-4094-9, Ver. 1 LPI • 101 102 • LPI 78-0060-4094-9, Ver. 1 Troubleshooting Manual Netport Introducing the NetPort The NetPort is a central communications processor that acts as an interface between communicating devices and the ScanNet Central Management System using TCP/IP (LAN) communications. The NetPort offers a number of advantages over previous serial Port Controller devices. The NetPort communicates with ScanNet at 10 megabits per second. This virtually eliminates the delay between the NetPort and ScanNet. Although throughput remains the same (each message still goes from an individual device to the NetPort to ScanNet) the turnaround time has been cut in half. The NetPort uses an Ethernet connection instead of a comm port, so is easier to have more NetPorts within a single system. Each NetPort can communicate up to 32 devices, and each system may have a maximum of 253 NetPorts. In ScanNet Version 4.6.1.8 and later, there is no limit to the number of NetPorts on one system because of the multiple subnets in this system. The NetPort may be used in place of the serial Port Controller. The two function identically, with the following exceptions: Message Device Communication Buffer Port Controller 9600-baud max 2K RAM Buffer NetPort 10MBS on 10 MBS Network. effective rate depends on Network traffic. 64K RAM Buffer NetPort Features The NetPort includes the following features: * Communication speed of 10 megabits on a 10-megabit network * 64K RAM message buffer space * Capability to communicate to and from ScanNet to set the following programming options: Passback Mode, Resync Mode, Resync Time, and, Primary Overstay Time * Capability to perform Passback Control for up to 100,000 IDs NetPort Passback Control Feature Passback is defined as a card attempting two consecutive entries into or two consecutive exits out of a parking area. The NetPort is capable of sending an unsolicited Passback message to ScanNet when it detects a Passback. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Netport • 103 The NetPort Passback Control feature has three modes: (1) OFF, during which vehicles are not checked for Passback; (2) PASSIVE, during which IDs are checked for Passback and when a violation occurs, a Passback message is sent to ScanNet but the violator is not prevented from entering or exiting and area; and (3) FULL, during which IDs are checked for Passback and when a violation occurs, a Passback message is sent to ScanNet and the violator is not allowed to enter or exit an area. Prohibited movement as a result of a Passback may be overridden on a single-card basis via ScanNet or by an optional daily resynchronization of all cards at a specific time. Primary Area Control/with 100K readers Now it does in the NetPort Version A2.1.0. NetPort is a central communications processor that acts as an interface between communicating devices and the ScanNet Central Management System using TCP/IP (LAN) communications. The NetPort offers a number of advantages over previous serial Port Controller devices. The NetPort uses an Ethernet connection instead of a COM Port, so it is easier to have more Netports within a single system. Each NetPort can communicate with up to 32 devices, and each system may have up to a maximum of 253 NetPorts. In the latest version of ScanNet, 4.6.1.8, there is no limit to the number of NetPorts because of the multiple subnets in this system. The NetPort may be used in place of the serial Port Controller. The two function identically, with a few exceptions (see introducing the NetPort). You can now use 100K readers with Primary Area Control in the NetPort. Because of the extra RAM, the ID range goes to 100K. The latest version of NetPort is A2.2.3. On the other hand, The Port Controller does not have enough RAM to support this feature. You can not have both 100K and Primary Area Control using a Port Controller. You can only have either 100K only or Primary Area only. Editing Port Controller Info Previously, if you edit Port Controller information in ScanNet Properties (Devices tab) and then apply your changes, your NetPort’s IP addresses are deleted from the Scan_NT.ini file. If you are using multiple subnets (new functionality in ScanNet), since the IP addresses must be in the ini file, you must reenter them if they are deleted. (You may want to print your ini file before editing Port Controller information to keep a record of your IP addresses.) This issue is resolved in ScanNet Version 4.6.5.3. Netport Changes Passback Detection Passback detection has been added to NetPort. Passback occurs when patrons “pass back” a card to another patron in order to gain illegal access to the parking facility. AntiPassback prevents a cardholder from passing back a card. Anti-Passback requires that a card be used in an entrance reader before it can be used in an exit reader and vice versa. NetPort works in two modes: Full or Passive Anti- Passback. In Full Anti-Passback, 104 • Netport 78-0060-4094-9, Ver. 1 Troubleshooting Manual access is denied and a record of the violation is printed if a card is not used in sequence. Passive Anti- Passback allows cards to be passed back but prints a record of the passback. NetPort also has the Auto- Resync functionality. This function is useful if your facility allows free access or exit during certain time periods. If you have an Anti-Passback system and your parkers try to enter or exit out of sequence the next day, the system either prints a violation (Passive Anti-Passback) or does not allow these cardholders to gain access again (Full Anti-Passback). By selecting Auto-Resync, you can set a certain time to allow each cardholder one free exit or entrance before Anti-Passback activates. When Auto-Resync occurs, NetPort prints a message stating that the system was automatically resynced and the time of the Resync. All cardholders who exited the system the previous night without using the card reader may gain access in the morning. Once this “free” entry has been used, the system then tracks entries and exits and does not allow re-entry out of sequence. Auto-Resync time will occur once every twenty-four hours at the time you indicate. There are two types of Auto- Resync time: One Shot and Exit Cycle: 1. One Shot. One Shot is used for allowing patrons either a free entry or a free exit prior to re-implementing Anti-Passback. 2. Exit Cycle. Exit Cycle Resync causes all ID numbers to be cycled for entrance reader usage. Exit Cycle Resync helps you void lost tickets by preventing your patrons from using their cards to exit unless they have used them to enter that day. Once the system has been resynced, parkers are allowed one free exit. The next day they must use their cards to enter the facility. Initializing From ScanNet You can now initialize NetPort from ScanNet. When you initialize, you will receive a “Power Failed, Memory Lost” message on your ScanNet PC. NetPort Programming Instructions 1. Launch a terminal emulator program, select the desired comm port, and set the baud rate to 115,200. If TeraTerm Pro is used, click on Setup then Serial Port to set the parameters. 2. Attach the DB-9 to RJ-45 serial adapter to the selected comm port on the PC. 3. Connect the RJ-45 connector of the serial adapter to the NetPort. See below for appropriate connections. RJ-45 9-Pin Sub-D 2-------------5 4-------------7 5-------------8 6-------------3 7-------------2 4.Apply power to the unit. 5. Within 3 seconds of power-up press the A key. This will invoke the monitor program in the NetPort. You should see the prompt, “es86mon:” 6. Type “xa” and press Enter to erase the existing flash memory. 7. Once the erasing is complete, type “w netport” and press Enter to begin programming Troubleshooting Manual 78-0060-4094-9, Ver. 1 Netport • 105 the unit. You should see the message, “Begin hex file transfer (using XON/ XOFF) now...” 8. Click on the File” pull-down menu. Then click on Send File. A File dialog box will open. 9. Select the directory where the program file “Netport.hex” exists. Then open the file. This will begin the download process. At completion, you should see the message “Device programmed successfully.” Ignore the note. 10. Type “p” and press Enter. Make sure “autorun” is set to 1. If not, complete Steps 11 through 13. Otherwise go to Step 14. 11. Type “p autorun 1” and press Enter. You will get a warning asking if you want to test the change before making it permanent. 12. Respond by pressing N. 13. Then confirm your decision by pressing Y. 14. Type “l” (small case letter L) and press Enter. Make sure “netport” is at address 8000:0000. If not, repeat Steps 6 through 9. 15. Return to Step 3 to begin programming a new device. Setting NetPort Addresses When you change the address of a NetPort with the rotary switches, it is recommended that you use the following sequence. First, change the switch positions to “0, 0”, and then cycle the power or hit the reset switch. Next, set the switches to the desired positions, and again cycle the power or hit the reset switch. Setting the switches to zero and resetting clears out the old settings and is similar to Cold Starting an Omega Controller. Version A2.2.4 An enhancement was made to increase stability and eliminate the issues with pulling lane and cashier reports from the PowerPad. Version A2.2.3 100K readers when used with a NetPort now handle passback correctly when the entrance or exit reader is offline at the time of use. 106 • Netport 78-0060-4094-9, Ver. 1 Troubleshooting Manual Passport 360 Version 1.1.2.4 The following enhancements have been implemented: * The polling situation that occurred with the Passport 360 when a card was being read has been corrected. The reader polls the Port Controller (or NetPort) to check Passback status. With the Passport Plus, the reader would grant access if it did not get a reply back from the port (offline). The Passport 360 reader was waiting for an extended period of time for the reply and still it would not always grant access. Now the Passport 360 performs exactly like the Passport Plus. * When using a keypad with a Passport 360 card reader, Access Granted messages are now being sent correctly to the System Activity Monitor in ScanNet . * “Please Wait” no longer displays when using Host-Based cards. * Issue Levels are now being read and sent correctly to the Passport 360 card reader. * Updating to this version requires updating Passport 360 PDA Programming Utility software to V1.3 and Dyna 3 to VA2.3.1 PDA Software 1.3 The component of the programming utility that receives the Group/Issue Level table from the reader has been fixed. Prior to this fix, the component was not always pulling back or sending the correct data. Updating to this version requires updating Dyna 3 to VA2.3.1 and Passport 360 to V1.1.2.4 Dyna III A2.3.1 The Dyna 3 Read Head now reads Format 2 cards correctly on all of the fields. Prior to this fix, ID Groups/Issue Levels were not being read correctly on large numbered IDs. Updating to this version requires updating the Passport 360 PDA Programming Utility software to V1.3 and Passport 360 to V1.1.2.4 PDA to Passport 360 Serial Connection The Passport 360 Card Reader can be programmed with the Passport 360 Programming Utility on your PDA using infrared (IR) or serial communications. Infrared communications uses the built in infrared transceivers of the PDA and the Passport 360 Card Reader to transfer information. In order to use serial communication, a Palm Serial HotSync Cable and a 9-pin (male to female) null modem connector for serial connection are needed. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport 360 • 107 Use the above cable with a null modem adapter that you can get at Radio Shack part number 26-264B. It is a female DB9 to Male DB9. Program to change the application options to Serial Port, with the splash screen enabled, with the baud rate at 19.2K. Plug the serial cable into the top left serial port indicated by the red arrow. 108 • Passport 360 78-0060-4094-9, Ver. 1 Troubleshooting Manual Replacing Passport Plus Passport 360 is an intelligent access control device that can function in online or offline systems. The 360 offers advanced security for parking facilities, buildings, or anywhere control devices are needed to limit access. The Passport 360 can be programmed by a user-friendly PDA (personal digital assistant) via infrared interface, the ScanNet Central Management System, or an existing MiniSCAN Port Controller. Orders with Passport Plus logic modules will still be processed for a limited time beyond June with a ship date less than 30 days. You will be notified when Passport Plus logic modules are running low. 3M will not sell new MiniSCAN systems with the Passport 360, but for existing systems, the Passport 360 will work online with the MiniSCAN Port Controller. It will print out Access Granted messages along with the card ID number, time and date, off line/on line status, and whether it is an entrance or exit. You can program the Passport 360 with a Hand Held Computer through the MiniSCAN Port Controller. In order to program directly, you must use a PDA. How can I program the Passport 360 reader? Several 3M devices do not have a socketed EPROM. Firmware is instead stored in a Flash memory device on the circuit board, so you can load or update firmware via a serial connection from a computer with the FlashProgrammer program. For more instruction, see the Flash Instructions and Flash Programmer Program at 3M.com in the Firmware Depot. Introducing the Passport 360 Card Reader System 3M’s new Passport 360 Card Reader features a wide range of technology and programming flexibility. It allows you to match a variety of configurations and reader technologies to your specific application. Features The Passport 360 can function offline for stand-alone operation, or online with ScanNet for host-based operation. This reader can be programmed using ScanNet over a network or using a handheld PDA (personal digital assistant) connected via an infrared port. The Passport 360 stores up to 3,000 transactions and can store information for up to 100,007 ID numbers. Four programmable inputs: Monitor, Inhibit, Egress, and Link. Two programmable relay contact outputs for pulsed or latched activation are available on the Passport 360. The Passport 360 supports Wiegand, Dyna (barium ferrite), Radio AVI, Proximity, Bar Code, and Magnetic Stripe read heads. Firmware updates can be performed via a serial connection from a computer with the 3M FlashProgram program. Display shows messages for all three card types: Standard, Central Only, and ValuePass. Programming information is retained in battery backed RAM. Information stored includes: Valid and Void Status Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport 360 • 109 16 Time Zones 16 Groups 6 Facility Codes 16 Holidays Programmable Input Optional Components Keypad. A 4 x 4 matrix keypad can be added to the system. Intercom. Two universal mounting intercoms are available. Display. A 2-line, 16-position alphanumeric LCD display is available. General Information The Passport 360 Card Reader customized firmware features are programmable options in the card reader. You can select the way you want it to operate and it has the ability to emulate the majority of ScanNet online and offline Passport Plus Functionality. The 360 packages are easier to order with no additional firmware option required making future system upgrades such as ValuePass or Series readers straightforward. The following should be noted: In MiniSCAN systems, the Passport 360 has not been tested with the MiniSCAN Port Controller. Testing will be scheduled to evaluate the reporting capabilities through the Port Controller. The Passport Plus had a count input which counted pulses; currently the Passport 360 does not. The Passport 360 was not designed to work with our existing Elevator Package; the Passport Plus logic board will continue to be used for this product. Due to low volumes, the Passport 360 will not be packaged with the Magstripe read heads 544 and 740 (New orders). These read heads generate an encrypted output, which has not been tested for compatibility with the current Passport 360. Testing will be scheduled for evaluating the ability to support existing sites. All other existing read head technology that 3M has supported is supported with the Passport 360. Soon to follow will be part numbers for ordering field upgrades to existing sites. Version 1.1.1.3 The situation in which the Reader Type was not setting correctly in the Passport Plus Programming: Reader Options (Secondary Options) screen in ScanNet has been corrected. PDA Software 1.2 The situation in which the Reader Type was not setting correctly on the Reader Options screen on the handheld PDA has been corrected. 110 • Passport 360 78-0060-4094-9, Ver. 1 Troubleshooting Manual PDA Software 1.1 3M has initially released the PDA software that can be used to program Passport 360 Card Readers. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport 360 • 111 112 • Passport 360 78-0060-4094-9, Ver. 1 Troubleshooting Manual Passport Plus 27128A EEPROM Obsolete The 27128A EEPROM is no longer available, but you can use a 27256 EEPROM in place of the 27128A chip. * Choose SGS Thompson. * Choose the device type 27256. * When burning the 27256 to replace an existing 27128, you must specify the device range 4000-7FFF. The 27128A EEPROM was used in Passport Plus and Port Controller. Downloading Firmware/Which Systems Matches the Firmware SCAN DOS Passport Plus Logic ValuePass Top and Bottom Passport Plus Logic ValuePass Top and Bottom S16K ScanNet Passport Plus Logic Camp Reader/Camp Posting Reader Top and Bottom Passport Plus Logic Camp Reader S16K Top and Bottom Camp Reader (only) Top and Bottom Both Systems Dyna 3 Passport Plus Logic and Universal Track 2 Reader Passport Plus Series 16K Passport Plus Series 24K Passport Plus Series 100K Passport Plus Elevator Passport Plus Keypad Passport Plus Barcode Spitter Programming Universal Track 2 Reader Universal Track 2 Read system only works with non-validated transient tickets. Follow these steps to make sure programming is correct: *The facility has to be set to a number other than zero *The logic module jumper has to be configured for Weigand *Card Data Configuration has to be set for ValueCard.(In ScanNet only) *ID Status does not need to be set *Has to be a Door reader Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 113 Universal Track 2 reader not reading or showing Alien Card In the past Universal Track 2 readhead required for you to tape back the unused Yellow and Orange wire to prevent them from shorting our on other wires. Because of recently made changes, you now have to tie these two unused wires to common (TB1 pin 8). If you don’t make this change, the readhead will either not read at all, or read an alien card message in the System Activity Monitor. Programming for TagMaster AVI Read Head Install the MagPass software you can get from 3M.com>FAQs>TagMaster AVI, and refer to the recommended settings in the installation document also available on the TagMaster AVI FAQ page. AWID Prox reader MR-1824 Inconsistency In Read Range This particular read head is not compatible with the 3M logic module power supply. In some cases, the read range has been acceptable (16 to 24 inches), and in other cases, it has not been acceptable (2 to 10 inches). Solution: The MR-1824 reader is pulsing ON and OFF at 50% duty cycle. This explains why the read range is sometimes acceptable and other times it is not. A recommended power supply is available from AWID (part # PS12-1A @ $ 35.00 each) - this is a plug in transformer capable of providing 1 amp of linear, regulated power with excellent dynamic loading characteristics. This power supply was tested in the field by AWID and ITR of Georgia employees with the following result: the MR-1824 was achieving 2 inches of range when powered by the 3M Logic Module, when the PS12-1A was connected (plugged in to the Barrier/Gate Control) the MR-1824 immediately read at 19 to 20 inches! Wiring for HID Read Head Here is the wiring for the HID read head: PP+ TB1 HID Read Head 3 Data 1 4 Data 0 8 Ground There is different wiring for 5 VDC OR 12 VDC: Power wire goes to For 5 VDC TB1 Pin 1 For 12 VDC TB3 Pin 1 114 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual Wiring for Amtech Read Head Here is the wiring for the Amtech read head: PP+ TB1 Amtech Read Head 3 Data 1 4 Data 0 8 Ground Wiring for Motorola Card Read Head Here is the wiring for the Motorola read head: PP+ TB1 Motorola Read Head 3 Data 1 4 Data 0 8 Ground There is different wiring for 5 VDC OR 12 VDC: Power wire goes to For 5 VDC TB1 Pin 1 For 12 VDC TB3 Pin 1 Programming CASI-RUSCO Cards This is what is required to use with our parking system: 1. The readers must be updated to Host-Based only logic modules. 2. The Card Data Configuration must be set as CR (CASI-RUSCO)- Hardware is set for Weigand. 3. The id's programmed on the card must be 12 digits or less. This is because the Central Access ValuePass Configuration is limited to 12) 4. The read head used is a 940-w Prox. Lite. DIP switches must be set to Weigand mode. #3 above will be altered in a later version of ScanNet to accommodate up to 20 characters. This read head will use the entire number on the card as the Host-Based credential ID. No math formula is required to convert this ID because facility is not used in the Card Data Configuration. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 115 Card Data Configuration for Weigand Read Heads Prox. ASP/ ESP 27 Old Prox. ESP 26 ABA/ISO Standard Prox. ESP Bit Bit 26 Bit Data Bit count 27 26 26 Bit direction MSB 1st MSB 1st MSB 1st ID Start Bit 0 1 1 # Bits in ID 13 12 16 Fac. Start Bit 14 13 17 # Bits in Fac. 13 12 8 Low Parity NONE NONE NONE Bit Count 0 0 0 High Parity NONE NONE NONE Bit Count 0 0 0 Start Group 0 0 0 Length 0 0 0 Start Issue 0 0 0 Length 0 0 0 Radio Card Dorado 544 Insert, 740 Swipe or Sensor Mag Swipe SmartPass Amtech SIA 36 26 26 Bit direction MSB 1st MSB 1st MSB 1st ID Start Bit 0 1 1 # Bits in ID 13 16 16 Fac. Start Bit 16 17 0 # Bits in Fac. 13 8 0 Low Parity NONE NONE NONE Bit Count 0 0 0 NONE NONE Data Bit count High Parity NONE 116 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual Bit Count 0 0 0 Start Group 0 0 0 Length 0 0 0 Start Issue 0 0 0 Length 0 0 0 Card Data Configuration for Bar Code Read Heads Bar Code Length 8 to 8 ID Start 0 ID Length 4 Facility Start Bit 4 Facility Code Length 4 Start of Group Number 0 Length 0 Start of Issue Number 0 Length 0 Type of Bar Code 3 of 9 Getting Errors Programming Series Readers As a default, Series Readers are all assigned 8 groups and 2 issue levels. Whenever initializing the Passport Plus controller, it will default the Series Reader to 8 groups and 2 issue levels. If you perform a reader setup, you do not program the Passport Plus Controllers. By performing reader setup, you program ScanNet only. To prepare the Passport Plus Controller to accept a different configuration other than 8 groups and 2 issue levels, you must either program the Passport Plus Controllers low level by going to Programming>Passport Plus>group/issue level, or setting up a block send ID issue in the Event Control System of ScanNet. Passport Plus D-Type Firmware Shows as Door Reader If your Passport Plus shows up as a door reader, verify that you have a jumper wire between TB3 connector 7 and 10, and power cycle. If it still is not an entry or exit reader determined by DIP switch 7, close DIP switch 8 and check ScanNet to see if it went offline as an entry or exit reader. Re-open DIP switch 8. If the Passport Plus continues to come up as a door reader, initialize it twice, and check to see if it is the right type of reader again. If it is still not the correct type of reader, close DIP switch 8, make sure the reader goes offline, initialize the reader while it is offline, and then open DIP switch 8 again. Check to see if the desired results were met. If all else fails, jumper out the super Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 117 cap (short the positive side to the negative side in order to discharge it). Remember to delete duplicate devices from ScanNet. Passport Plus Product Line Discontinued On June 1, 2003 the Passport Plus product line will be discontinued and replaced by our new product the Passport 360. The Passport 360 controller takes the place of the Passport Plus logic module, the Passport Plus Series logic module and the Passport Plus Host-Based logic module. No additional firmware options are needed for the Passport 360 controller to work with HostBased, Standard, Series, or ValuePass readers. As of May 23, 2003, all new orders for a reader Access System, either online with ScanNet or stand-alone, must use the 360 part numbers. Also, Passport Plus orders that are scheduled to ship after May 31 may be converted to the new Passport 360. Individual notification will be sent to inform you of these existing orders (best effort). Should you have any questions regarding this notification, please do not hesitate to call your regional manager or your customer service representative. Passport Plus Expansion Boards There are three types of Passport Plus Controllers that need an additional expansion board to function properly: * Keypad * 24K and 100K * Host-Based Use the following guide when upgrading a Passport Plus to one of these types of readers. Keypad: There are two different types of expansion boards used for Passport Plus Keypad. 904383 (MEDKI) is the earlier type PC board, used for the earlier type keypads. You can identify this type of keypad by a double row connector which the connector cable plugs into. 93-854_ or 93-8542 used to be silk screened onto the earlier style keypad. This earlier style board is obsolete and has been replaced with the later style keypad expansion board. The later style expansion board (93-8542 PC board, keypad MEDKI) has a single row socket labeled P2 that a single row flex cable plugs into. You also need a later style keypad to function with the new setup. The later style keypad has a single row of pins on it that the single row flex cable plugs into. The firmware version A3.0.1 is used in both the earlier and later style expansion board, and there is no conflict with the firmware. If your customer experiences a problem with the older style keypad expansion board, you may send it to the Depot Repair Center since they still repair these earlier style boards. If you choose to, you may upgrade to the later style keypad. The part number to upgrade a Passport Plus to a Keypad is 62-15413, and comes with all necessary parts. 24K and 100K: When using extended memory for a 24K and 100K Passport Plus, you will need part number 93-8545 (PC board, assembly MEDKI memory) and the appropriate firmware. This expansion board has extra RAM that the extended memory firmware needs for 118 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual storage of all the card information. Passport Plus, 8K, 16K, 24K and 100K firmware keep all information about the card at the reader. CAMP (Central Access Management Program) keeps all information about the card at ScanNet. Host-Based: Host-Based readers are different from the others because all card information is stored in ScanNet. Only the range of the cards that are to be converted* is stored at the Passport Plus Host-Based card reader. Host-Based readers are capable of sharing space in the Passport Plus in order to allow you to use Host-Based and Passport Plus, Host-Based and 8K, or Host-Based and 16K. These options require different firmware packages, but use the same MEDKI expansion board. When using Host-Based firmware, you will need the MEDKI expansion board, part number 92-8845 (PC Board ASSY, ValuePass reader MEDKI). Through Customer Service, you can order an upgrade package that specifically fits your parking needs. If you are using a standard Passport Plus and wish to upgrade, it is highly recommended that you purchase a field upgrade package, because of the additional hardware requirements that will be included. You may contact Customer Service for part number and pricing information at 877-777-3571. *CAMP uses a formula to convert the standard ID and Facility Code into a credential number that is used by ScanNet. For 27 bit cards, the formula is 32,768 X Facility Code + Physical ID number. For 26 bit cards, the formula is 65,536 X Facility Code + Physical ID number. For a quicker conversion process, there is a program available in ScanNet that will convert the ID to the credential needed by ScanNet. This program is located under Utilities>Credential ID Calculation. Upgrade Dyna II to a Dyna III Dyna II was the predecessor to the more recent Dyna III read head. In order to upgrade the Dyna II to the Dyna III, you need a new Dyna III read head with the Dyna III software in it. The logic module and the logic module firmware stays the same. Dyna Kontrol Kards consist of magnetic barium ferrite material sandwiched between durable polyester card layers. Encoding information is accomplished by polarizing spots in the magnetic material. The polarity and location of the spots create the identification information. Barium ferrite is factory encoded and embedded within the card, making duplication and counterfeiting difficult. When the card is inserted into the reader, a magnetic head with non-moving sensor coils reads the encoded data for identification purposes. Passport Plus Losing Memory Bad Chips: Measure the voltage across the ram, between pins 14 and 28. You should have 4.7VDC, which is perfect; (you need 1V to hold memory in your ram chips. Check to see what type of brand name rams you have in your PP+ bottom board and top board if you have one. Having mismatched rams have always caused a problem in the past, so this could contribute to a problem. If you have to replace your RAM chips, we recommend Toshiba ram Part # TC55257DPL-85L, which you should be able to obtain at Radio Shack. In the past, Hitachi Rams had a habit of not communicating with the top board. If you are using a top board, consider changing your Ram chips to the Toshiba name brand. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 119 Missing Jumpers: There are jumpers located next to the ram chip U17. Make sure the following jumpers exist, and are in the following position: Shorted Diode: Make sure that the diode D8 is not shorted. Check continuity from the anode to the cathode with your Common side of your Multimeter on the cathode. You should see -3.695, or something indicating some type of resistance. Check continuity with your Common side of your Multimeter on the anode. You should see around 21 Mega ohms. If you measure 0 ohms in both directions, send the PP+ in for repair. The part number for this is: DIODE 11-7041 749A PP+ MEMORY VB. Series-16 with Prox Readers When using 16K Passport Plus with Proximity Readers, you must have, the Card ID Number set to use 14 data bits in the Card Data Configuration. You should not set this number to 13 because 13 data bits only gives you a maximum 8,191 possible Card ID Numbers. Fourteen data bits gives you 16,383 possible Card ID Numbers. It has been common practice to set the Card Data Configuration for the 27-bit ASP Proximity Readers to have only 13 data bits designated for the Card ID Number. The ID start bit position is 0. The Facility Code start bit position is designated as 14. This leaves data bit 13 unused, so you can select 14 data bits for the ID and not affect the Facility Code. PC Control over Host-Based Cards 3M has introduced two on-line readers that interface with the ScanNet Central Access Management System (CAMP) and provide a wide-range of capabilities. Using the ScanNet Access Control System (ACS), programmed Credentials are automatically placed in the readers that are associated with the Access Package. The Access Control System allows the user to associate the Credential with a Facility Code and patron(s) and/or vehicle(s). In addition, the user may assign each Credential, patron and vehicle to an Account. Optional features in the ACS include Central Access, Billing, and Invoicing. 120 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual The Access Control System allows you to configure the Host-Based Readers with one or more of the following types of Credentials: 1. Standard Credentials. An access control method that employs reusable Credentials. The patron either prepays or receives a bill for the uses of this Credential. This type is often used for “monthly” parkers. Time Zones and Credential IDs must be stored in the readers. Access granted/ denied decisions are made by the Card Reader. 2. Central Access Credentials. Has all the features of Standard Credentials. In addition, all access requests to the controlled area are processed by a central computer. This is most often used to group Credentials together (Group Control) and then limit the number of entries of the group at any given time to a portion of the total. For example, the group “Car Pool A” has 5 members but only one member at a time is granted access. With online communications, access requests to the controlled area are processed by a central computer to grant or deny access. The central computer validates the following before granting access: a. Credential validity b. Paid-through date of the account c. Anti-passback d. When and where access is being requested e. Group Control The ScanNet Central Access Management Program (CAMP) processes the access requests from readers to grant or deny access. CAMP validates Credential Validity, Passback, time/space analysis, Group Control and ValuePass information. CAMP maintains a history of access-related information for all Credential types. To take advantage of all these features, two new readers are being offered: the basic CAMP Reader, and a full-featured Passport Plus CAMP Reader. Basic CAMP Reader The basic CAMP Reader provides a cost-effective alternative with all the functionality of a host-based reader, but without support of standard access cards. It does not have built-in intelligence (meaning programming decisions are made at the central PC). It is offered in two models, with and without an LCD display. The basic CAMP Reader includes the ValuePass Reader and the CAMP Reader PC Board assemblies. The CAMP Reader PC Board assembly is a modified version of the Passport Plus PC Board assembly. The basic CAMP Reader includes the following features: 1. It can send an Access message to ScanNet. 2. It accepts configuration information from ScanNet to set the ID ranges, text messages to display to the patron, and Granted/Denied default action to take if the reader is offline. 3. From ScanNet, it receives Access Request responses containing the Granted/Denied action, messages to display, and other data required for the intended use. 4. It can also send an Access Granted or Denied message back to ScanNet informing the host of the action taken by the reader and whether the action was: on-line, that is, performed by the reader because of a response from the host; or offline, that is, performed by the reader as defined by the default offline Granted or Denied flag. The basic CAMP Reader does not support standard access cards and is not supported by the Hand Held Computer. Note: diagnostics can be started by strapping Input E and doing Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 121 a Cold Start. Passport Plus CAMP Reader The full-featured Passport Plus CAMP Reader combines all the basic CAMP Reader features with the standard Passport Plus features. Like the Passport Plus, this is an intelligent reader with a distributed processing architecture. Decisions are made at the reader and do not require external memories for operation. The Passport CAMP Reader includes the ValuePass Reader and the Passport Plus Logic PC Board assemblies. Resync Explanation Customer#1 drives into parking lot. Customer#1 is "in". The gates are raised. Some lots do this because there are no attendants on duty after a certain time. Customer#1 drives out. Customer#1 did not use his card. The following day: Customer#1 drives up to the parking lot. Customer#1 can't get in, because Customer#1 is in "pass back". Customer#1 is in pass back because he didn't use his card to exit the lot. Customer#2 drives into parking lot. Customer#2 is "in". The gates are raised. Customer#2 drives out. Customer#2 did not use her card. The parking lots cards are "re-synced". The following day: Customer#2 drives up to the parking lot. Customer#2 can get in, because Customer#2 was allowed one free entrance or exit into the lot before re-instating the anti-pass back system. If Customer#2 passes back her card to her friend Customer#1, Customer#1 will not be able to get in. Customer#1 will be in "pass back" with Customer#2's card. Card Readers Showing Up as Door Readers In order to change Passport Plus door readers to entrance or exit readers, you must do the following: 1. Place a jumper on TB3 Pin 7 (Input F) to TB3 Pin 10 (com) 2. Set DIP switch 7 Open for exit Closed for entrance 3. Initialize reader using the hand held computer or SCAN command menu. ScanNet Not Locking Out Standard Credentials with Group Control Because you are using standard credentials rather than central credentials, the reader keeps track of valid ID's and facility codes. Credential validity is not checked or controlled by Camp if the credential is standard. CAMP cannot lock-out standard overlimit credentials. The other option for standard readers is to charge a fee for the credentials that are group-over-limit. This is the only way to enforce a group limit with 122 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual standard credentials. If a parking operator requires for ScanNet to lock out group-over-limit credentials, then they will have to upgrade their readers to Host-Based readers and set up their system as a central access with group control. Nesting Area Reader Type 1-Original 2-Original 3-Area 1 4-Area 2 Crossover 5-Area 2 Street 6-Area 2 Crossover 7-Area 1 Keypad Programming This example automatically programs access codes for the Keypad. After programming, you have to display what IDs were programmed, so that you may assign them to users. Plug in Log On? NO Initialize HHC YES ARE YOU SURE? YES Log On? YES Password> YES Operate Online YES Password> YES Main Menu Select A-E/U-W/R B ID# Send ID Commands NO Program Status NO Program GRP/ISSU NO Program Privl ID NO Prog Keypad Acces YES From device NO From File YES From New File YES Menu * ACCESS CODES* EDIT/DISP (display)/SEND Z EDIT Create Acces Cod YES length FR: 0004 YES to : 0004 YES Create FR:0001 YES to: 0 0 0 6 YES (note that at this time, the handheld has automatically created the IDs you need.) You are at Create Acces Cod Fr:0006 ESC Create Acces Cod ESC Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 123 Menu * ACCESS CODES* EDIT/DISP/SEND X Disp View from :0001 YES (note: write down every code from code #1 – code#6 to give to your patrons. the computer has predefined the codes for you.) #1: XXXX YES #2: XXXX YES #3: XXXX YES #4: XXXX YES #5: XXXX YES #6: XXXX YES (note that the rest of the IDs are all 0, showing that they are not programmed. You will see the un-programmed IDs if you continue to hit YES. To scroll back up to the top, hit NO.) hit ESC to get out of the list. Menu * ACCESS CODES* EDIT/DISP/SEND W Send send to device YES should say DONE !! If sent to the passport plus successfully. Press ESC until back at Main Menu. Main Menu Select A-E/U-W/R E Mode reader options YES reader options 1 NO reader options 2 YES from device NO from file YES from new file YES Menu * Reader Options 2* EDIT/SEND Z Edit Access Msg. On YES *Passback Override Valid G# NO 1 turns on YES moves over one space NO 2 turns on YES moves over one space. Continue process turning on all groups with following sequence: NO YES NO YES NO YES NO YES NO YES NO YES *Cards For Groups Valid G# NO 1 turns on YES moves over one space NO 2 turns on YES moves over one space. Continue process turning on all groups with following sequence: NO YES NO YES NO YES NO YES NO YES NO YES *KeyPad for groups Valid G# NO 1 turns on YES moves over one space NO 2 turns on YES moves over one space. Continue process turning on all groups with following sequence: NO YES NO YES NO YES NO YES NO YES NO YES *Length of Code variable NO fixed YES # of digits:4 YES Original RDR YES Menu * Reader Options 2* EDIT/SEND W Send send to device YES should say DONE !! If sent to the passport plus successfully. Press ESC until back at Main Menu. Unplug Handheld computer 124 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual Weather Striping When upgrading a standard Passport Plus Card Reader Logic Module to a ValuePass System, make sure that the piece of weather striping provided is installed. Place the weather striping over the two exposed crystals on the bottom board of the logic module, then install the MEDKI PC board. This will prevent the bottom of the PC board from shorting out on the metal crystal enclosures. Passport Plus reader setup as displayed in Sybase Central In Programming>Passport Plus>Reader Setup, when you define which type of readers you have, you can go to Sybase Central, and the values in the table_acs_reader_setup should be displayed as follows: Reader Type model groups issue_levels max_ids Passport Plus 0 8 16 8191 Series 8K with any issue level 1 16 1 8191 Series 16K with any issue level 2 16 1 16384 Series 24K with any issue level 3 16 1 24576 100K 4 16 1 100007 Universal Track 2 and Standard Logic A3.3.0 This version includes the following changes: 1. Added support for SST transient tickets on the Universal Track 2 Read Head. As a result, you cannot use 0 as the Facility Code on issued tickets. 2. Added support for Duplicate IDs, which can be supported in ScanNet as long as different Facility Codes are used. Posting Reader A1.8.6 ValuePass posting reader A1.8.6 only creates even if you put it on add, disp, or anything else other than create. It will change on the LCD display, but it doesn't actually change. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 125 Host-Based Logic A1.2.5 & A3.4.5/Series 16K A3.4.5 *When a “from” ID number entered into the ScanNet Central Management System is larger than a “to” ID number, the reader reports an error to ScanNet rather than cold starting. *Readers now send only one access request to ScanNet per ID presented. Exceptions to this are when: (1) Inhibit is being used and a vehicle moves off the loop and then back on, (2) a different Credential is read prior to presetting the ID, or (3) the time limit of three minutes has passed since the last request. This feature may be disabled by setting delay between reads to zero. *To use the Inhibit input, you no longer need to select Group 5. The following change affects the Passport Plus Series 16K and 24K (Version A1.9.2) and the Passport Plus Series 16K (Version A3.4.5): *The Inhibit input and the Passback Override function now work properly for all groups. Host-Based Logic A3.4.5 When using a Host-based Credential, CAMP will now only send a request to ScanNet once, except under certain circumstances which are listed below. This change was made to alleviate the high number of requests that can occur when using AVI Readers and to cut down considerably on the time-outs that can result from too many requests. One of three things must happen before the logic will resend a request for a previously read card. These are: The logic is using Inhibit and the car moves off the loop and back on again. A different Credential is read prior to reinserting the original card. A time limit of three minutes has expired since the previous request. If this feature is not desired, it can be disabled by setting the Delay Between Reads to zero. Host-Based Logic 3.4.2 This version allows the user to set up a Passport Plus Card Reader as an Entry/Exit or Door Reader without having to initialize the memory on the Reader. For the Reader to function as an Entry or Exit Reader, you must still install a jumper from Terminal 7 to Terminal 10 on TB3 of the Logic Module, but now instead of initializing, just power cycle the Reader. After turning the reader back on, it will be programmed as an Entry or Exit Reader depending on how DIP Switch #7 on SW1 is set (closed = entry; open = exit). Host-Based Logic A1.2.1/Series 8K & 16K Host-Based Logic A3.4.1 When a CAMP Reader receives a message from ScanNet, the message does not set the reader as a posting reader. Instead, the CAMP Reader reads the entry/ exit DIP switch to determine the reader type. 126 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual Series 100K Logic A1.9.2 The firmware for the 100K Series Reader has been modified so that the use of a facility code is no longer required. If the facility code bit length is set to zero in the Card Data Configuration (only for Weigand and barcode), the facility code will not be checked for validity. Series 16K Logic A1.9.1 If you are using PP+ 16K version A1.9.1, there is a known issue of Inhibit not working. This version of firmware was only released for a short time, but every now and then it pops back up, and people want to know what is wrong with their reader. The fix for this is to upgrade to the latest version of 16K reader firmware. Series 100K Logic A1.8.1 3M has released Version A1.8.1 (S100K) of Passport Plus. Support for reading ValueCards and Bar Code have been added in this version. Standard Logic D3.3.1 not vending the output (remotely or by card) The Passport Plus firmware D3.3.1 doesn’t vend the output (remotely or by card ). This occurs only when the reader is initialized via a HHC or ScanNet. It appears initializing the reader twice in a row resolves this problem. If the reader is to be initialized it must be done twice. Standard Logic A3.3.1 This version gives users the option of disabling the Bar Code Ticket Spitter ticket number assumption on bad reads. If DIP switch #7 is open, the Ticket Spitter will not assume a ticket number on a bad read. Instead, it will ignore the read. This allows tickets to be manually swiped at a Bar Code Ticket Spitter. If DIP switch #7 is closed, the Ticket Spitter will assume the ticket number on a bad read and send that number to ScanNet in a Ticket Issued message. Closed is the default setting. Standard Logic A1.9.0/Series 100K Logic A1.9.1 1. Access granted/denied, bad facility code, etc., messages have been extended to handle duplicate IDs. 2. Passport Plus Series Readers and the Passport Plus 100K Reader can now read ValueCards and transient tickets. In addition, Series 16K and 24K Readers can also read Cassi-Rusco cards. 3. Readers will no longer process data from the read head until the reader has initialized itself upon power-up. In addition, the following change was made to the Passport Plus 100K Reader: 1. Weigand support has been added. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 127 Standard Logic May 1999 This new version incorporates the following changes: * The Passport Plus now has the added capability to read ValueCards in addition to Dyna, Bar Code, and Weigand. * Verification of the Facility Code length set by SCAN’s Card Data Configuration is zero. Also, if the Facility Code is zero, SCAN’s Last Card Report displays the fact that the Facility Code was bad. * If a Bar Code card ID exceeds the uppermost card value accepted by the Reader, a bad ID message is sent to SCAN instead of a bad Facility Code. Dyna 3 Read Head A2.2.0 The Dyna Card Read Head (Dyna 3) firmware has been enhanced to support the E0 version of the 68HC11 processor. Lane Troubleshooting Passport Plus Card Reader and G-90 CD Gate 1. Check for power, circuit breaker feeding power to the operator, or internal fuse. Check position of the “power” and “auto/manual” switches. The power switch should be in the “on” position and the auto manual switch should be in the auto position. 2. Has the thermal overload been tripped on the motor? (red reset on the bottom of the motor, push hard) 3. Have the drive belts inside the operator broken or fallen off? 4. Is the gate arm wedged against an object? 5. Is there more than one device controlling the opening? 6. Is the Safety Edge circuit tripped? 7. Is the motor control relay stuck in? 8. Are both limit switches made? 9. Switch bank 1 of the connection panel must be set to the following: 1 – Closed 2 – Closed 3 – Open 4 – Closed 5 – Closed 6, 7, and 8 are unused (keep closed) If it is not, turn off and change the DIP switches to the above setting. Perform a cold start by holding the Monitor/Menu button down and turning the gate on while continuing to hold the button down until you see the words “monitor” and “menu” flashing back and forth on the display. 10. At the Omega LCD Controller, go to Monitor> Config> Settings. Make sure that the Omega is in base mode 1, sub mode 1, (B1, S1). If the Omega does not indicate B1, S1, then you have one of these problems: * The Omega is not recognizing the correct base/sub mode because of internal circuitry, which is faulty. Replace the Omega LCD Controller. * The connection panel has a bad path between the configuration module and the Omega LCD Controller. Replace the connection panel. 128 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual * You have a bad configuration module. Replace the configuration module with one that is working correctly. Bypass the configuration module by setting the gate to No Config mode if you suspect that the configuration module is faulty. Turn the gate off and pull out the configuration module. Set DIP switch 4 on the connection panel to the following: 1 – Closed 2 – Open 3 – Open 4 – Open 5, 6, 7, and 8 are unused (keep open) Perform a cold start as described in step 9. Repeat step 10 above and see if the Omega indicates that it is in B1, S1. If it still is not, then you have one of the following problems: * The Omega is not recognizing the correct base/sub mode because of internal circuitry, which is faulty. Replace the Omega LCD controller. * The connection panel has a bad path between the configuration module and the Omega controller. Replace the connection panel. 11. Take a jumper wire, and short the connection panel inputs between A1, (vend A) and A13, (common). You will notice that the input LED 1 will come on while the contact is being made. This is a momentary contact, so as soon as the gate starts raising, take the jumper off. By shorting these contacts we simulate a vend from the reader. If the gate raises by shorting out the inputs, but does not raise when using the reader, then you have a faulty reader. Make sure the ID is valid and go through the usual testing of the reader to fix the problem. The Last Card Report can be helpful when troubleshooting the reader. If the gate does not raise when shorting the inputs, perform a memory initialization by turning the controller power off and closing DIP switch 2 (service only). Wait 5 minutes for the battery to discharge, and open the switch. Perform a cold start as described in step 9. Repeat step 11. If the gate still does not raise, use the override switch to see if the gate will raise. If the gate raises, this proves that the mechanics of the gate are in working condition, and the Omega controller is faulty for not sending the proper signal to the relay that controls the gate arm. If the gate still does not raise, go to Menu> Commands> Raise gate. If the gate raises, it proves that all inputs and outputs are good. If the LED for Gate Up comes on, but the gate does not raise, then the problem is one of the following: * The path to the input or output is bad. * The input or output relay on the Omega controller is bad. * Both the Omega controller and the path on the connection panel are bad. Swap out suspected bad parts with known good parts to test. Move the gate door over loop B. This is going to simulate a car being on loop B. In the gate, you will notice that the LED under B on the Omega controller has stopped blinking on T (tuning), and is now solid under P (presence). If you do not get this result, go to 3M.com/Value Added Reseller/FAQs for Gate “I think my loops are bad. How can I trouble shoot them?” Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 129 Take the gate door off the loop, and the gate will reset itself. If it doesn’t, then you will be experiencing Omega controller problems. Replace and retest. Codes for D Type Firmware D type versions of Passport Plus Logic Module firmware improve the intermittent problem where the reader would lose memory. In the event of a checksum error the reader will send a code message to the System Activity Monitor in ScanNet indicating the area in memory where the error occurred. The reader will still maintain the programming in most cases. 01 - Non-zero value found in un-used RAM. 02 - Current ScanNet Message Pointer was corrupted. 03 - Next ScanNet Message Pointer was corrupted. 04 - RAM block #1 was corrupted. 05 - RAM block #2 was corrupted. 06 - RAM block #3 was corrupted. 07 - RAM block #4 was corrupted. 08 - RAM block #5 was corrupted. 09 - Programming RAM guard number was corrupted at startup. 10 - Programming RAM checksum was corrupted at startup. 11 - Programming RAM guard number was corrupted at run-time. 12 - Programming RAM checksum was corrupted at run-time. 13 - Stack Overflow 14 - Stack Underflow Keep in mind that this enhancement was added for the benefit of our firmware developers and if you experience any of these messages in your ScanNet System Activity Monitor, you should keep a record for a few days, and e-mail your regional Product Support Technician with the results. Host-Based Logic D3.4.5/Host-Based Series 16K D3.4.5 An enhancement was implemented to correct the situation in which the reader would intermittently lose memory. In the event of a checksum error, the reader will send a code to the System Activity Monitor in ScanNet indicating the area in memory in which the error occurred. In most cases, the reader will maintain the programming. Series 16K D1.9.2 and Series 24K D1.9.3 An enhancement was implemented to correct the situation in which the reader would intermittently lose memory. In the event of a checksum error, the reader will send a code to the System Activity Monitor in ScanNet indicating the area in memory in which the error occurred. In most cases, the reader will maintain the programming. 130 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual Standard Logic D3.3.2 An enhancement was implemented to clear all memory prior to each initialization command. Standard Logic D3.3.1 The situation that intermittently caused the reader to lose memory has been corrected. In the event of a checksum error, the reader will send a code to the System Activity Monitor in ScanNet indicating the area in memory where the error occurred. The reader will still maintain the programming in most cases. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Passport Plus • 131 132 • Passport Plus 78-0060-4094-9, Ver. 1 Troubleshooting Manual Port Controller B1.8.7 Hides "Enter Retry Mode" Message The message "Enter Retry Mode" is a code letting the user know that since the Port Controller was busy at the time a request was made, the Port Controller sent the message back to the device to be buffered until the Port Controller is no longer busy. Getting these messages is normal, but if you prefer to not see these messages, a firmware upgrade is available that no longer displays these messages. This was changed in Version B1.8.7. 27128A EEPROM Obsolete The 27128A EEPROM is no longer available, but you can use a 27256 EEPROM in place of the 27128A chip. * Choose SGS Thompson. * Choose the device type 27256. * When burning the 27256 to replace an existing 27128, you must specify the device range 4000-7FFF. The 27128A EEPROM was used in Passport Plus and Port Controller. Getting Non-existent Devices after Replacing the Port Controller If the Port Controller was previously in use on another system, or for another lot, and the memory was not drained before installing it, whatever devices were in use on that system will be reported to ScanNet from the Port Controller’s memory. When installing a Port Controller on one system that was in use on another system, it is recommended that you drain the memory before bringing it on-line. To drain memory, you must short out the super cap, or carefully remove the ram chips (U15 and U16) and reinsert them. Port Controller 2MHz Processor A new 2-megahertz microprocessor (part #11-9173) and an 8-megahertz clock crystal (part #11-3247) are now available for the SCAN Port Controller (version B 1.7.3). For Bar Code Ticket Tracking systems and SCAN ValuePass Systems, these improvements virtually eliminate time-outs. For most systems, these improvements also allow you to operate at a baud rate of 9600 instead of the factory-set 4800-baud. This allows data to travel more quickly through your system, thereby improving overall system performance. To make use of the new 9600-baud firmware, you need to reset the appropriate settings on the Port Controller, Passport Plus Card Reader logic module, and any other devices in your system. To change the baud setting in the Port Controller, locate the Dipswitches on the bottom board. Open the 4800-baud switch and close the corresponding 9600-baud switch for each set or port. To change the baud setting in the Passport Plus Logic Module, move the jumper from the 4800-baud position to the 9600-baud position. Please note that the Auditor 2+2 and Auditor 2C Fee Computers cannot operate at 9600- Troubleshooting Manual 78-0060-4094-9, Ver. 1 Port Controller • 133 baud. Model G90/ CG90 gates have to have a hardware upgrade to operate at 9600-baud. There is a physical jumper wire soldered to 4800-baud setting that has to be de-soldered, and resoldered to 9600-baud rate. Editing Port Controller Information If you edit Port Controller information in ScanNet Properties (Devices tab) and then apply your changes, your NetPort’s IP addresses are deleted from the Scan_NT.ini file. If you are using multiple subnets (new functionality in ScanNet), since the IP addresses must be in the ini file, you must reenter them if they are deleted. (You may want to print your ini file before editing Port Controller information to keep a record of your IP addresses.) This issue is resolved in ScanNet 5.1. Pin-out Between Port Controller and Computer DB9 DB25 1 ---------- 8 2 ---------- 3 receive 3 ---------- 2 transmit 4 ---------- 20 (optional clear to send) 5 ---------- 7 ground 6 ---------- 6 7 ---------- 4 request to send 8 ---------- 5 clear to send 9 ---------- 22 11 (optional clear to send, not used) Port Controller Upgrade If a customer has a 32 device, SRAP, SCAN Port Controller that was shipped after October 1997, it should already be Scan NT compatible. To make sure, the port controller must have the following: *A #63B03 CPU chip *An 8-megahertz crystal *DIP switches set for 9600 baud rate Older SCAN Port Controllers (32 device) that don’t have the correct CPU chip and crystal can be upgraded by sending them to the Depot Repair Center, or they can be upgraded in the field. The following two parts would be needed in order to upgrade in the field: *Part #11-9306 (IC, HD63B03RP 2 MHz processor) *Part #11-11636 (Crystal, 8 MHz) Version B1.8.6 Error detection and recovery for device communications have been enhanced. This version supports SRAP firmware. 134 • Port Controller 78-0060-4094-9, Ver. 1 Troubleshooting Manual Version B1.8.5 The Port Controller has been enhanced to improve error handling, which results in a reduced risk of losing a transaction message. Version B1.8.3 3M recently revised the Port Controller firmware so that exiting a secondary area via a street reader no longer causes a Passback message. Version B1.7.5 & 100k Version B1.8.1 3M recently released enhanced firmware versions for the standard Port Controller (Version B1.7.5) and the Port Controller used with the 100k Passport Plus Card Readers (Version B1.8.1). These new versions allow multiple devices (which have been prespecified) to be programmed simultaneously from the Scan NT Central Management System. Note: the Scan Facility Management System (DOS-based system) enables you to program just one device at a time. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Port Controller • 135 136 • Port Controller 78-0060-4094-9, Ver. 1 Troubleshooting Manual PosiDRIVE Three Position Door Safety Switch The PosiDRIVE gate comes equipped with a Door Safety Switch located at the top right of the door opening. When the door is attached to the cabinet and closed, the door presses the switch in, restoring power to the motor. When the door is taken off the cabinet, the door safety switch disconnects power to the motor under ALL circumstances. The Door Safety Switch is a three position safety switch that when manually pulled out, will restore power to the motor. This is useful if a technician who is inexperienced with a PosiDRIVE is working on the gate, and is unaware of the “Power Fail Raise” feature. If the door safety switch is bypassed by pulling out the switch (not normally recommended) and the circuit breaker switch is turned off for any reason, the system will respond to this as a line power failure. After 10 seconds, the gate will activate under battery power and raise the arm. Use extreme caution when servicing the gate and be aware of this condition. This is why the door safety switch should not be bypassed unless absolutely necessary. If you are troubleshooting the gate and need to have power on the motor in order for the gate arm to raise or lower for testing purposes, pull the Door Safety Switch out. Power is supplied to the PosiDRIVE gate motor with the switch pulled out or pushed in which is the usual state made by the door. Distributors who are unaware of the “Pulled out” state have sent good CPU boards in for repair, not understanding that they had to pull the switch out in order to test the PosiDRIVE motor function. When we receive these boards, we pull the door switch out and hit the reset button on the I/O Board, and have had no problems as the board is returned into full operation. We then cycle the board for 24 hours continuously and have not seen any of these boards fail. Following this reset procedure can reduce costly downtime and returns. If you are having difficulty troubleshooting a PosiDRIVE gate, remember to follow the reset procedure by pulling the door switch out and pressing the reset button on the I/O board. Be aware of the three different positions of the safety switch: *Pushed in (The switch is held in by the technician or the door). The motor has power and the gate may be raised or lowered for testing. Be aware of the “Power Fail Raise” feature. *Middle position (The door has been taken off and the switch is not pulled out). The motor power is removed, and the gate will not raise or lower. *Pulled out (The technician manually pulls the switch out). The motor has power and the gate may be raised or lowered for testing. Be aware of the “Power Fail Raise” feature. Balancing the Gate Arm During operation, if the arm starts to raise and then returns to the down position or starts to come down and then returns to the up position, it is probably not balanced correctly. During operation, if the arm bounces at the stop when it raises or lowers, it is also not balanced correctly. With the power OFF, the battery backup disconnected, and the arm unlocked (See manual for how to do this.), you should be able to position the arm near the middle of its range of motion, and it should move very little or not at all. If the arm Troubleshooting Manual 78-0060-4094-9, Ver. 1 PosiDRIVE • 137 moves to either extreme, it is not properly balanced. To achieve proper balance, you must have the correct number of springs installed for the length of the gate arm, and you must adjust the spring tension to complete the balancing. Complete instructions for installing the springs and adjusting the tension can be found in the PosiDRIVE manual. Version 1.2.1/Backout Timer The situation that caused the gate arm to lower when a car was on the B loop before vending the gate has been corrected. DIP switch 7 has been programmed so that when in the open position, the backout timer is disabled. When DIP switch 7 is closed, DIP switches 3 and 4 are accessed to determine the timer period (15, 30, 45, or 60 seconds). Warning Labels The WARNING label will now be applied to both sides of the gate cabinet. Both labels will be centered and approximately 8 inches below the top of the gate cabinet. Improved Gate Arm Design The aluminum gate arms have been improved to provide better stability in arms 14 feet and longer. The arm package includes a round aluminum arm and the appropriate number of springs for the length ordered. As of October 1, 2003 all PosiDRIVE gates will be shipped with the round arm. All future orders should reference the new Gate Arm Package part numbers listed below. Part Number Description Price 53-14059 Gate Arm Package, Round, PosiDRIVE 10Ft $163.00 53-14060 Gate Arm Package, Round, PosiDRIVE 12Ft $173.00 53-14061 Gate Arm Package, Round, PosiDRIVE 14Ft $189.00 53-14062 Gate Arm Package, Round, PosiDRIVE 16Ft $199.00 53-14063 Gate Arm Package, Round, PosiDRIVE 18Ft $214.00 53-14064 Gate Arm Package, Round, PosiDRIVE 20Ft $224.00 53-14082 Gate Arm Package, Round, Sectional, 20Ft $245.00 Spare Arms or replacement (includes end caps and reflective tape) 53-14065 Gate Arm Only, Round, PosiDRIVE 10Ft $112.00 53-14066 Gate Arm Only, Round, PosiDRIVE 12Ft $122.00 53-14067 Gate Arm Only, Round, PosiDRIVE 14Ft $138.00 53-14068 Gate Arm Only, Round, PosiDRIVE 16Ft $148.00 138 • PosiDRIVE 78-0060-4094-9, Ver. 1 Troubleshooting Manual 53-14069 Gate Arm Only, Round, PosiDRIVE 18Ft $163.00 53-14070 Gate Arm Only, Round, PosiDRIVE 20Ft $173.00 NOTE: You will still be able to order the rectangle arms for replacement or spare for existing sites only. The round arms and the rectangle arms are not interchangeable. PosiDRIVE Gate Heaters Discontinued The PosiDRIVE heaters are no longer needed. As a result, the harness assembly and thermostat have been removed. Temperature sensitive components on the circuit boards have been redesigned and the boards are now coated to prevent damage from condensation. In addition, the Motor Gearbox is now filled with a synthetic lubricant from the factory that performs across the entire temperature range. New Mainspring A new heavy-duty version of the PosiDRIVE mainspring has been developed. This spring replaces the standard spring in the following gate arm packages: 53-14012 Gate arm, posi, 10ft 53-14013 Gate arm, posi, 12ft 53-14014 Gate arm, posi, 14ft 53-14015 Gate arm, posi, 16ft 53-14016 Gate arm, posi, 18ft 53-14017 Gate arm, posi, 20ft 53-14059 Gate arm, round, 10ft 53-14060 Gate arm, round, 12ft 53-14061 Gate arm, round, 14ft 53-14062 Gate arm, round, 16ft 53-14063 Gate arm, round, 18ft 53-14064 Gate arm, round, 20ft Gear Box Lubricant The gearbox lubricant on the PosiDRIVE Security Gate was changed to allow motor operation at very low temperatures without a heater. Arm of PosiDRIVE Gate Does Not Raise When Power is Lost Yes, Auto Raise is one of the new features of the PosiDRIVE gate. In order for this feature to be enabled, you must have the battery backup assembly installed. It does not come installed from the factory. Also, you must have DIP Switch #8 on the CPU Board Troubleshooting Manual 78-0060-4094-9, Ver. 1 PosiDRIVE • 139 set in the Open position. One other important note about this feature is that the battery backup is not intended to operate the gate. It is only intended to raise the gate once upon power loss. Wiring Red/Green Light The PosiDRIVE gate is not supplied with an auxiliary relay, therefore you will have to provide a 24VDC relay that will be mounted inside of the gate. The PosiDRIVE gate provides a 24VDC output to use in this application. On the relay, normally closed is connected to the green light, and normally open is connected to the red light. The switch is a single pull single throw relay. This red/green light addition is a completely manual operation where an attendant will flip the switch to change the light from green to red or vice versa. Follow the diagram below for details on wiring this feature: Version 1.1.1 The external operator switch now operates as the Manual/Auto switch, which keeps the gate up indefinitely without the gate lowering due to a timeout period. 140 • PosiDRIVE 78-0060-4094-9, Ver. 1 Troubleshooting Manual PowerPad “Ticket Jam” Message When Ticket is Inserted Into Validator Since I programmed my PowerPad to put validated tickets “into vault,” my Validator displays a “Ticket Jam” message when a ticket is inserted. Does the Validator have a burster or parker in it? Is DIP Switch #5 closed on the CPU board? If you program the PowerPad to send validated tickets “into vault,” the corresponding Validator must have a burster or parker, and DIP Switch #5 must be closed. If these conditions aren’t met, the Validator will display a “Ticket Jam” message when it tries to move a validated ticket to the rear of the Transport into the vault. If you program the PowerPad to return the tickets instead of sending them to the vault, you do not need to have a burster or parker or close DIP Switch #5. Merchant (Hole-Punch) Validator Setup The Merchant Validator is a Hand operated device that allows merchants to hole-punch patrons' parking tickets, for parking fee discounts. When the ticket is inserted into the SST Validator the PowerPad calculates the fee and processes the account info. automatically. Merchant Validators are used with HP-1 transports and PowerPads, (version 2.0 or higher with the Voucher option) you must also verify dipswitch # 7 is closed on the SST CPU Bd. The Hole Punch Validator has a code number, which coincides with a programmable Hole Punch Account. Under programming choose "Accounts" The first Account number is a descriptor field to name the account. (you can use any account number "A" through "Z") The second account number is the actual Hole punch validation number. Program account "Status" as "Validation/ Voucher. Then program the type of deduction. At the Hole Punch Validator make sure the tickets are inserted correctly With the Mag stripe appearing on the left and facing upward. Verify the slide is in the correct position for each hole Punch BE CAREFUL NOT TO PUNCH OVER PREVIOUS HOLES!! Merchant (Hole-Punch) Validator Which ID Should a Particular Store Get At a new location (with no existing Merchant Validator) it makes no difference which ID a store gets, as long as the store is properly referenced to that ID number in the PowerPad. An exception to this would be when IDs are pre-assigned. In this case, each store must receive its pre-assigned numbered mechanism. Regardless of how the numbers are assigned, a merchant MUST end up with the mechanism that the PowerPad thinks he or she has. The PowerPad will associate that number with that merchant. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 141 Merchant (Hole-Punch) Validator Cashier Accidentally Validates Ticket in Zone that was Already Used This would destroy both validations. It is imperative that cashiers be properly trained on how to use the Validators. If a validation is performed on top of another, it will likely produce additional holes in the validation zone. This would result in a single validation zone with more holes in it than either of the single validations would have produced. When read by the exit equipment, the pattern will not correspond to either of the individual validations. It will be up to the cashier to manually determine (by the ink stamp) which validations were performed. The problem with this is that both ink stamps would be in the same location as well. This may make both stamps difficult or impossible to read, and the customer may get nothing. Merchant (Hole-Punch) Validator Ticket Inserted Wrong Way The Merchant Validator handle has a small notch such that when a ticket is inserted the proper way, the tab on the ticket rests in this notch. The tab will not fit this notch if the ticket is inserted the wrong way. The Merchant Validators will also have a small silkscreened graphic on them to show the proper magnetic stripe orientation (similar to that at a gas pump or supermarket for credit cards). In addition, the cashiers again must be properly trained. If all this fails and a ticket is inserted incorrectly, holes will be punched through the magnetic stripe making it unreadable. Merchant (Hole-Punch) Validator Location of Holes on Ticket Matching Account Number Below is an example of an SST ticket with a Hole-punch validation of 15. This table shows what different accounts hole punch should look like when you punch a ticket. X stands for no hole while O stands for hole. 1 2 3 4 5 XXXO XXXO XXXO OOOX 142 • PowerPad XXXO XXXO XXOX XXOX XXXO XXXO XXOX OOXO 78-0060-4094-9, Ver. 1 XXXO XXXO XOXX XOXX XXXO XXXO XOXX OXOO Troubleshooting Manual 6 7 8 9 10 XXXO XXXO XOOO OXXX XXXO XXXO OXXX XOOO XXXO XXXO OXXX OXXX XXXO XXXO OXOO XOXX XXXO XXXO OOXO XXOX 11 12 13 14 15 XXXO XXXO OOOX XXXO XXXO XXXO OOOX OOOX XXXO XXOX XXXO XXOX XXXO XXOX XXXO OOXO XXXO XXOX XXOX XXXO 16 17 18 19 20 XXXO XXOX XXOX OOOX XXXO XXOX XOXX XOOO XXXO XXOX XOXX OXXX XXXO XXOX XOOO XOXX XXXO XXOX XOOO OXOO 21 22 23 24 25 XXXO XXOX OXXX XOXX XXXO XXOX OXXX OXOO XXXO XXOX OXOO XOOO XXXO XXOX OXOO OXXX XXXO XXOX OOXO XXXO 26 27 28 29 30 XXXO XXOX OOXO OOOX XXXO XXOX OOOX XXOX XXXO XXOX OOOX OOXO XXXO XOXX XXXO XOXX XXXO XOXX XXXO OXOO 31 32 33 34 35 XXXO XOXX XXOX XOOO XXXO XOXX XXOX OXXX XXXO XOXX XOXX XXXO XXXO XOXX XOXX OOOX XXXO XOXX XOOO XXOX Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 143 36 37 38 39 40 XXXO XOXX XOOO OOXO XXXO XOXX OXXX XXOX XXXO XOXX OXXX OOXO XXXO XOXX OXOO XXXO XXXO XOXX OXOO OOOX 41 42 43 44 45 XXXO XOXX OOXO XOOO XXXO XOXX OOXO OXXX XXXO XOXX OOOX XOXX XXXO XOXX OOOX OXOO XXXO XOOO XXXO OXXX 46 47 48 49 50 XXXO XOOO XXOX XOXX XXXO XOOO XXOX OXOO XXXO XOOO XOXX XXOX XXXO XOOO XOXX OOXO XXXO XOOO XOOO OOOX Editing Configuration Chips When working with these devices, you may view and print the options of the configuration (config) chip that has been made special for your site’s needs. The config chip 93C66 is located at U25 in the C Platform circuit board, and the config chip 1736EPC is located at U20 of the B Platform circuit board. At the device, choose Programming>System Preferences>Config Options>Config, and you will see the settings that have been burned into the config chip for your site. This is an example of an Auditor PowerPad config printout: Device APP* Attendants 200 Merchants 208 Merch Per Key 8 Merch Groups 26 Fee Tables 24 Stats Per Type 8 Taxes 6 Txn Buf Size 3940 Vouchers 208 Vouch Per Key 8 144 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual Vouch Groups 26 Exchange 0 Ticket Tracking Yes Keymap Qwerty YTD Clear Yes Barcode No Coin Validator No Coin Dispenser 0 Alt Payment 8 LPI Yes Tour Number 0 Taipei No Print Exceptions Yes ValueCard 26 ValueCard Per Key 1 ValueCard Groups 26 ValueCard Full Yes POF Multilingual No C Taipei Receipt No C Vault Msg No Credit Card InOUT No A3 Multilingual No Hotel No Test No Tax Round Up No C BC NYParks No *APP = Auditor PowerPad APS = Automatic Paystation XV = Credit Card Exit Verifier ACT = Automatic Cashier Terminal SPTR = PowerPad Spitter If you receive a config chip that does not have your ordered options, you may edit your config chip for a maximum of two weeks. After two weeks, the config chip will initialize Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 145 itself and return to the original burned options that the chip came with. To edit your config chip, choose Programming>System Preferences>Config Options>Config>choose the (F-3 [-] END) key and then press the down arrow one time. You will be one line under the last config option on the page, and your cursor will move one space to the right. Type fapd and then press your (TIME/Yes) key. An editable column will appear on the right side of the config options. Once you make all of the desired changes, you must escape all of the way out of the device, and then log back on as the administrator. Go back to Programming>System Preferences>Config Options>Config, and then choose the (Prog/Print) key. This will print out what the original options are, and also the edited desired options for the device. Fax this printout to Customer Service to have the options changed and a new config chip sent to you. To view Serial Port Config Options, at the device, choose Programming>System Preferences>Config Options>Serial. Here is an example of Serial Port Config Options: P# Rom 1 FUNC DRV TYPE CreditCard DataCap 2 FUNC DRV TYPE PortComm PortComm 3 FUNC DRV TYPE Readers Transport 4 FUNC DRV TYPE Printer Epson Tm950 rec: Y jrl: Y val: Y rpt: Y 146 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual To view Input Config Options, at the device, choose Programming>System Preferences>Config Options>Input. Here is an example of Input Config Options: Recp 3 1 1 Cash Drawer 1 3 2 Cash Drawer 2 4 3 Exit Arm Loop 6 4 Exit Rst Loop 7 5 Gate Status 9 6 Exit Dev Enab 10 7 Lost 12 8 Aux Vend To view Output Config Options, at the device, choose Programming>System Preferences>Config Options>Output. Here is an example of Output Config Options: Recp 4 15 1 Cash Drawer 1 13 2 Cash Drawer 2 11 3 Duress 9 4 VC Gate 7 5 Gate 5 6 Custom 3 7 Display Out 1 8 Logon Light To have a new config chip sent to you, it is mandatory that you provide a printout of the config options. If you wish to have a config chip programmed for an existing site, you must send a printout of the options that you would like to have; otherwise, there is a risk that it will be programmed incorrectly, especially if changes were made in the field that 3M is not aware of. Credit Card Clearing Houses for Datacap DataTran POS System In order to use the point of sale (POS) credit card system, your account must be set up at a clearing house. These are the current clearing houses that 3M supports for POS transactions: Alliance Data Systems/Sears Payment Terminal (ADS/SPT) CardNet Envoy (Nashville) Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 147 First Data (FDR) GPS/NDC MAPP VisaNet D The Datacap DataTran does not support: NaBanco SPS Host CPU Error Messages The PowerPad uses the Motorola 68000 series CPU that contains self diagnosing error messages that users may encounter during the usage of their PowerPad. These messages are meant to warn a user about interruptions to normal activity, or help pinpoint an area that has been affected by some type of problem. If you get one of these errors, you may not need to send your PowerPad in for repair. The following are interrupt errors that may be caused by a power failure or interruption while you are in the middle of a transaction: * E 256 Unused RAM interrupt error. * E 257 Watchdog interrupt error. The watchdog monitors the voltage levels of critical circuits. * E 258 Process memory checks interrupt error. * E 259 Print queue lost interrupt error. “P 259 7/31/03 7:00”. This message means that the PowerPad was in a printing process and this process was interrupted. The print queue also may be lost, and messages that would have normally been printed will be lost. In the above example, the printing process was interrupted on July 31, 2003 at 7:00. In the case of a problem error, the 3M Depot Repair Center uses these errors to fix problems more efficiently. If you see any of these errors, you should send your PowerPad in for repair: * E 26 Real time clock error. The Dallas time clock circuit is malfunctioning. The PowerPad will always keep the correct date and time, even if you initialize it. The only way for the time to change is if you change it in programming. If you see any erroneous time (00:98 for example) or if the time changes unexpectedly, you have a clock circuit error. * E 27 Watch dog timer error. The watchdog circuit is malfunctioning. If the voltage level is unacceptable, the watchdog will turn the voltage to the circuit off. * E 28 A serial port from number 0 through 4 may be malfunctioning. The most common malfunctioning port is number 4, the printer port. * E 29 A serial port from number 5 through 11 may be malfunctioning. * E 30 The barcode reader is malfunctioning. If you should get any of these uncommon errors, you should also send your PowerPad in for repair: * E3 Address error. * E4 Illegal instruction error. * E5 Zero divide error. The PowerPad is trying to divide something by zero that it shouldn’t be. * E6 Instruction error. * E7 Trap instruction error. 148 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual * E8 Privilege violation. * E9 Trace error. * E10 Emulator error. * E11 Emulator error. * E12 through E23 are unassigned. * E24 Random interrupt error. * E25 Unused. * E31 Unused. If you get any other errors that have not been mentioned, you may be experiencing a CPU failure. Since these codes originate at the CPU, if the CPU fails, it may return a code that has not been assigned. PowerPad Fee Computer Tips and Tricks Changing Your System’s Ticket Validation Device The PowerPad Fee Computer allows you to choose whether you want cashiers to use the printer or the SST Ticket Validator for validating tickets. To change the device used for validation, do the following: 1. At the Transaction screen, press the Prog/Print key. The Program menu will be displayed. 2. Select SYSTEM PREFERENCES. The SysPref-Program menu will be displayed. 3. Select TRANSACTION. The Transaction-Program menu will be displayed. 4. Select FEE TABLE. 5. In the Validator field of the Fee Table for which you want to change the validator device, select SST or PRINTER. If you select SST, cashiers will use the SST Validator for validation. If you select PRINTER, cashiers will use the printer for validation. Processing Unreadable Tickets If a ticket is unreadable with an SST PowerPad, the best way to process it is as a TimeBased Lost Fee transaction. First, a master attendant must program the Lost key appropriately. To program the Lost key for time-based transactions, do the following: 1. At the Transaction screen, press the Prog/Print key. The Program menu will be displayed. 2. Select KEYS. The Keys-Program menu will be displayed. 3. Select LOST KEY. The Program Lost Key menu will be displayed. 4. In the Status field, select BY TIME. 5. Press the Esc key to return to the previous menu. Once the Lost key is programmed appropriately, cashiers can use it to process TimeBased Lost Fee transactions, by doing the following: 1. Manually enter the time that is printed on the unreadable ticket. Then press the Lost key. The PowerPad will calculate the parking fee and display the amount due. 2. Collect the fee from the patron. Enter the amount the patron paid and press the Cash key. The PowerPad will ask for a blank ticket. 3. Insert a blank ticket into the SST Validator or printer (depending on how your PowerPad is programmed) for validation. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 149 4. Staple the validated ticket to the unreadable ticket for auditing purposes. Updating C-3 fee Display from Auditor II to PowerPad Yes, but you will need to purchase a new PC board and a new cable. The PC ASSY, PowerPad LCD Fee Display part number is 92-10054. The Cable, 15 Cond. 22 AWG Shielded part number is 11-11466 "Lost not Active" Message When Entering Date and Time for Lost Tickets You need to program the lost key status to be BY TIME. You can have a flat amount associated with this fee, which will produce this flat fee only when you press the lost key by itself. If you have more than one fee table that you want to be able to enter the date and time to produce a fee, you will have to program the lost key to be BY TIME next to all involved fee tables. Clearing Memory on New PowerPads It is recommended that you clear the memory on new PowerPads before programming them for the first time. While all PowerPads are thoroughly tested before being shipped to you, sometimes the memory can become corrupted during shipment. CCXV Fee Display or ACT Fee Display Common Troubleshooting If you are using a PowerPad Power Supply to drive the fee display for a Credit Card Exit Verifier, or an Automatic Cashier Terminal, and the fee display doesn’t show up, you may have to adjust some settings. The fee display is not defined in the Config Chip, but you should check the config settings to make sure that it is set for which device it is. In the PowerPad, go to Programming/ System Preferences/ Config Options/ Config, and make sure it says CCXV, or ACT. Inside of the Power Supply, make sure that the 3-pin din next to U7 (74HC08) is shorted with a shunt going to Display. If it is in the Relay position, change it to display. Check to see if you have power to the fee display by checking the backlight. Cover the light sensor to fool the display into thinking it is night. The backlight should come on. If it doesn’t, you have to adjust the potentiometer on the Power Supply located by U6 (LT1054) to get voltage to the display. Because the potentiometer is a 50-turn pot, you have to adjust it accordingly. You may have to adjust this pot because of variances in the field that are different than its previous test environment. If you adjust it too far, you will be able to tell because you will be able to hear, and feel it click. Lastly, if all else fails, you possibly have bad drivers for the display, which you will have to replace. These 2 chips are U7 (74HC08), and U6 (LT1054). If the fee display still 150 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual doesn’t respond to all of these troubleshooting tips, send the PowerPad Power Supply in for repair. Reduced Exit Time Account Validation If you have ever been confused when using the Reduced Exit Time Account Validation on an PowerPad, the following two points may help clear up the confusion: 1. When the Account key is pressed; the PowerPad will reduce the exit time by the predetermined amount and give a validation of the difference between the original end time and the new end time. If the fee is the same with both end times, the validation amount will be zero. 2. When the Account key is pressed again, the PowerPad will still take the original end time and reduce it by the predetermined time. Each time the Account key is pressed; the same validation will be applied. 3. When a numeric key is pressed prior to the Account key, the PowerPad will multiply the predetermined amount by that number and then subtract the new time from the end time. For example, if the Reduced Exit Time is programmed for 15 minutes and the 2 key is pressed followed by the Account key, the time used for the reduction will be 30 minutes (15 x 2). Also remember that any validation is directly determined by the fee structure and how the validation is used. It is a good idea to test the results to see if the validation is what was intended before applying it. Auto Rate Feature Have you ever wondered what the Auto Rate feature in the PowerPad fee table is used for? If so, the following description should prove helpful. The Auto Rate feature is used to change the fee structure that is used to automatically calculate parking rates on a specific date. If you anticipate a change in parking rates to occur on a specific date, you can write a new fee structure in advance. You would specify this fee structure in the Auto Rate field along with the date of the change over. Customers entering the lot before the date of the rate change will be charged according to the old rates. Customers entering the lot after the date of the rate change will be charged the new rates. PowerPad: MC3486 Receive IC If you are using the MC3486 Receive IC in the PowerPad power supply, you must use a chip manufactured by Motorola. The Texas Instruments IC MC3486 will not work. The IC is located at U1 on the power supply board. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 151 PowerPad Display Shows Correct Characters but Wrong Spacing Some recently manufactured displays seem to occasionally exhibit this symptom. This only occurs on a few units and does not happen very often. While we are working with the manufacturer to determine the cause, we have implemented a solution in the PowerPad software. The solution is available in software Version B2.4.3 (or higher; current production is Version B2.5.0). When you experience incorrect spacing as described above, log off, then log right back on. The spacing should be normal again. SST PowerPad Ticket Validator Power Supply 3M has eliminated the individual power supply for all new SST Validators. The Validator will now be powered from the PowerPad Interface (power supply). The SST Validator power will be supplied by pins 5 and 6 on receptacle 6 of the Interface. This will eliminate the high voltage going into the SST Validator, which will now be powered by 24 VDC versus the previous 110 VAC. The new design will help to reduce the ambient temperature in the SST Validator enclosure. The Epson Printer will continue to have its own power supply. Desktop Fee Display Communication All PowerPad (APP) platforms can accommodate the use of the Desktop Fee Display. There are a couple of things that need to be understood when using the Desktop Fee Display. Converting to RS232 Communications First, the Desktop Fee Display uses RS232 communications to receive the display data. Therefore, when connecting to Comm Port #1 on the APP Power Supply, a Comm Isolator/Converter must be used to convert from RS422 to RS232 used by the Desktop Fee Display. Using Fee Display With Credit Card Option The other point to be aware of is, if you have both the Credit Card option and a Desktop Fee Display, you must have an expansion board to provide an additional communications port. This is because Comm Port #1 on the APP Power Supply and the RJ11 jack normally used for the Credit Card communications line on the APP CPU Board are the same communications port. You cannot have Credit Card and a Desktop Fee Display without this expansion board. The Desktop Fee Display is plugged directly into the expansion board using Port # 5. The Credit Card communications line is plugged into the RJ11 jack on the APP CPU Board. For Revision K1 or later APP CPU Boards, we have developed, and will soon be releasing, a cable that allows the Desktop Fee Display to be plugged directly into the RJ11 jack on the APP CPU Board. Again, this can be done only if you are not using the Credit Card option. PowerPad Currency Exchange Feature The Currency Exchange feature is available as an optional software package on the current production versions of the PowerPad. It is not a new feature, but it has not been widely publicized and many users are unaware of its existence. This article describes the purpose of this feature and tells how to program the Exchange Keys for exchange rates. 152 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual The Currency Exchange feature is most helpful in situations where patrons who pay fees with foreign currency require change. Since local currency is the base currency recognized by the PowerPad, change is given in local currency. This could potentially lead to a shortage of local currency and/or unusually large amounts of withdrawals being reported on the Cashier Report. Facilities can avoid this situation by using the Currency Exchange feature to maintain different types of currencies. Up to four different types can be maintained. Operators at each facility can monitor currency levels, and when they drop to a certain point, deposit funds in the drawer. Each facility would have to establish its own specific procedure for handling this situation. Programming the Exchange Keys for Exchange Rate Please note that to use the Currency Exchange feature, you must first purchase this optional package and have it configured on your PowerPad. Contact 3M Customer Service to purchase the package. To program the Exchange Keys for the exchange rate, do the following: 1. Under Keys, choose EXCHANGE KEYS. The Program Exchange Keys screen will appear. The cursor will be at the X1 Key Status field. 2. Press the Date/No key until EXCHANGE is displayed 3. Press the Time/Yes key. The cursor will move to the Name field. 4. Type the name of the currency, such as US Dollar, Yen, Peso, and so forth. 5. Press the Time/Yes key. The cursor will move to the Symbol field. 6. Type the symbol of the currency. 7. Press the Time/Yes key. The cursor will move to the Symbol Placement field 8. Press the Date/No key to select LEFT or RIGHT. 9. Press the Time/Yes key. The cursor will move to the Decimal Digits field. 10. Press the Date/No key to select ONE or TWO. 11. Press the Time/Yes key. The cursor will move to the Exchange Rate Decimal Digits field. 12. Type the number of digits for the exchange rate. (Note: This field requires typing the number of digits rather than pressing the Date/No key to select the number.) 13. Press the Time/Yes key. The cursor will move to the Exchange Rate field. 14. Type the exchange rate. 15. Press the Time/Yes key. The cursor will move to the X2 Key Status. 16. Repeat Steps 2 through 15 to program additional Currency Exchange keys. 17. Press the Esc key to return to the previous menu. C Platform PowerPad Memory I/O Expansion Board Due to the redesign of the PowerPad to the C platform and due to part obsolescence, a new memory I/O expansion board was developed. This board is not compatible with B platform PowerPads. PowerPad Expansion Board Problem A problem was recently observed on a PowerPad that had an expansion board installed. The validated tickets would not be sent to the vault and some of the programming menus Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 153 were missing. When the expansion board was removed the tickets would be sent to the vault and the missing menus returned. As it turns out, a hardware problem with the expansion board was responsible for these symptoms. Replacement of the expansion board resolved this problem. Differences Between Paid and Unpaid Grace Time Paid grace time is the time it takes the patron to exit the lot after paying for a ticket at a central Pay Station or PowerPad. If the patron does not exit within the allotted time frame, they will be directed to a cashier or charged according to the programmed repay ticket fee number under SST Ticket Spitter programming. Unpaid grace time is the time a patron enters a lot, decides that they no longer want to park in the lot (could be full) and leave without paying by inserting their ticket at an exit PowerPad, Exit Verifier, or Automatic Cashier Terminal. When a patron exits within unpaid grace time by inserting the ticket into the device, the transport will print the date and time of the grace exit, and also print “Exit In Grace” on the ticket. If the ticket is manually entered into the PowerPad because it was unreadable, the printer does not validate the ticket like a normal fee generating transaction would, but it will automatically vend the gate, and print on the journal tape of the PowerPad “Exit Pass Accepted” along with the date and time, and the exit pass number. You can change the programming to also validate lost or manual tickets by changing unpaid grace time programming to 0 under Programming>System Preferences>Grace Time>Unpaid grace time and include the grace time within the fee table itself. This way there will be a $0.00 fee generated, and the PowerPad will ask you to insert a ticket so that it can be validated. Validated Tickets to Vault If you program a PowerPad to return validated tickets or to keep them in the vault, it has no effect on the ValueCard operation. The ValueCard operation is set up to return each card after it is used so the customer can use it again and again. The only way for the system to capture a card is if the card is expired, has no value or is on the blacklist. To have the card captured in such instances, you need to program it under the ValueCard System Preference programming. Another option is to order a CPU update kit (part #8719574). This kit provides the parts necessary to update your own boards. Printer Continuously prints “******257*****date/time.” This will happen if the printer cable has been accidentally plugged into the SST Port on the PowerPad. To recover, you must clear the PowerPad memory and reprogram the PowerPad. 154 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual Maximum Number of Cashiers Logged On at One Time * The maximum number of cashiers that can have report data stored in a PowerPad at one time is 12. * If a thirteenth cashier attempts to log on before one or more of the previous 12 have cleared their Cashier Reports, a “Clear Cashier Rpt” message will be displayed. * To continue, you must log on as a Master and clear at least one Cashier Report. * If you have 12 cashiers logged on, when you log on with the Master password, you will only be allowed to log on under Tutor Mode. * After clearing one cashier, you can then log off, and log back on under Transactions Mode. * Since there are 11 cashiers and one Master logged on under Transactions Mode, the twelfth cashier will not be able to log on. * The original 11 cashiers will still be able to log on and process transactions. Customize Financial Reports The PowerPad Fee Computer allows you to choose a variety of options associated with the Financial Report feature, including which fields will print and when, whether or not a master/supervisor must print a report before clearing its data, how the Reports Feature will interface with SCAN or ScanNet, and who can override mandatory commands. To program the Financial Reports feature, perform the following steps: 1. Log on to the Fee Computer. The Transaction screen will be displayed. 2. Press the Prog/Print key. The Program menu will be displayed. 3. Press the F6 (Page Down) key to move to the second page of the Program menu. The second page will be displayed. 4. Select System Pref. The SysPref Preferences menu will be displayed. 5. Press the F6 (Page Down) key to move to the second page of the SysPref Program menu. The second page will be displayed. 6. Select Reports. The Program Reports screen will be displayed. 7. With the cursor in the Cashier Report At Logout field, determine if you want the Cashier report to print every time an attendant logs off. a. If you want the Cashier report to print every time an attendant logs off, press the Date/No key until Yes is displayed. Then press the Time/Yes key and go to Step 8. b. If you do not want the report to print automatically, press the Date/ No key until No is displayed and go to Step 9. 8. With the cursor in the Report Print Items field, determine the data you want to include when the Cashier report is printed. a. To print all the fields in the report regardless of whether they contain data, press the Date/No key until All is displayed. Then press the Time/Yes key and go to Step 9. b. To print only the fields with data, press the Date/No key until Used is displayed. Then press the Time/Yes key and go to Step 9. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 155 9. With the cursor in the first Local/Print field, determine whether or not you want to require that data be printed before it can be cleared from memory. Note that only an attendant designated as master or supervisor can clear data from memory. a. To require data to be printed before it can be cleared, press the Date/ No key until Mandatory is displayed. Then press the Time/Yes key and go to Step 10. b. To allow data to be cleared without being printed, press the Date/No key until Optional is displayed. Then press the Time/Yes key and go to Step 10. 10. With the cursor in the ScanSend field, establish how the Reports feature will interface with SCAN or ScanNet. a. To require a master or supervisor to send a report to SCAN or ScanNet before erasing its data, press the Date/No key until Mandatory is displayed. Then press the Time/Yes key and go to step 11. b. To require a master or supervisor to print then erase accumulated data without sending the data to SCAN or ScanNet, press the Date/ No key until Optional is displayed. Then press the Time/Yes key and go to Step 11. 11. With the cursor in the Override field, determine who if anyone is allowed to skip mandatory commands. a. To allow only those attendants designated as a master to skip mandatory commands, press the Date/No key until Master is displayed. Then press the Time/Yes key and go to step 12. b. To allow supervisors to skip the mandatory commands, press the Date/No key until Supervisor is displayed. Then press the Time/Yes key and go to Step 12. c. To not enable any attendant to override a command, press the Date/ No key until Unused is displayed. Then press the Time/Yes key and go to Step 12. 12. Repeat Steps 9 through 11 for all remaining reports or press Esc to return to the previous menu. “Ticket Being Printed” Message Shows When No Ticket is Present Several conditions can cause this message to appear, including: the Burster being unplugged, the Buster mechanism separating from the Transport, the Burster malfunctioning, or the Transport malfunctioning. Be sure the Burster is plugged in and the Buster mechanism has not separated from the Transport. Then, if necessary, have the Burster or Transport repaired. 156 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual Clearing Cash Reports The PowerPad does not allow you to clear your own report in Transaction mode. You must log off in Transaction mode and log on in Tutor mode. This will allow you to clear your own report. Or you can have another Supervisor or Master log on to clear your report. Alternative Use of Repay Feature Do you want to re-encode your SST Ticket to automatically default to a fee table other than the default fee programmed at the PowerPad? The following example shows you how. It refers to a fee table that is a little higher than the default because the patron uses 3valet parking after entering the lot with a ticket from the Ticket Spitter. For this example, the patron must pay at an Exit Cashiering device. Here’s how to program: 1. In ScanNet, go to Programming> SST Ticket Spitter, and pull programming from the Ticket Spitter. 2. Under Repay Ticket Fee #, enter the number of the fee table you want the ticket to refer to once it has been validated. (This is explained further below.) 3. Send the programming back to the device. 4. In ScanNet, go to Programming>PowerPad, and pull Fee Tables programming from the PowerPad. 5. Be sure the default fee table’s Grace Time is long enough for the ticket to be validated within grace so no fee is generated. The time it takes for the patron to receive the ticket from the Ticket Spitter and give it to a valet parking employee to validate it has to be considered. The time the patron has to wait in line also has to be accounted for. The SET TKT NUMBER setting increments with each ticket issued. If the value you enter for LOW TKT NUM is lower than the current SET TKT NUMBER value, you will never get a Low Tickets message. This message is only sent once. It is not sent each time a ticket is issued after the low-ticket threshold is reached. When determining what threshold to use, that is, whether you want the Low Tickets message when there are 300, 500, or 1,000 tickets left, you should take into account how many tickets are issued on a busy day and how much time it normally takes for new tickets to be installed. 6. Make sure that the fee table the Ticket Spitter is programmed to use for Repay is programmed at the PowerPad. 7. The PowerPad that the valet parking employees use has to be in Central Cashiering. 8. The PowerPad on which the final validation will take place should be in Exit Cashiering in order to take the issued ticket off the issued ticket stack. Here’s how it works: 1. The patron enters the parking lot with a transient ticket, pulls up to valet parking, and hands the ticket to the valet parker. 2. The parker inserts the ticket into a Central Cashiering PowerPad SST Validator, the fee $0.00 comes up, and the parker hits the Cash key. 3. The ticket is validated and put in the car for the patron to exit with at a later time. 4. The patron returns for his or her car, and after receiving it, is presented with the ticket that the valet parker had validated in his Central Cashiering PowerPad SST Validator. 5. The patron can use this ticket in an Automatic Cashier Terminal (ACT) or at an Exit Cashiering PowerPad SST Validator. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 157 6. Once the ticket is inserted into either the ACT or the SST Validator, the PowerPad automatically recognizes the new default fee for repay. On the PowerPad display at the top left, the new fee (FX) is displayed. 7. The patron pays the fee and exits the lot. Credit Card Point-of-Sales Equipment Collects Parking Fees As parking operations search for ways to cut costs, they are increasingly turning to automated payment systems. The 3M credit card processing systems allow parking facilities to collect fees with point-of-sale (POS) parking control equipment. The unmanned POS equipment can be located at the entry and exit traffic lanes for complete automation of the parking fee payment with cashless transactions. Point-of-sale devices that can be equipped with credit card features include the SST PowerPad, SST Ticket Spitter, Credit Card Exit Verifier, and the SST Automatic Pay Station. The parking facility can be configured to issue a ticket at the entrance and accept payment at the exit with a credit card, using a stand-alone “Ticket In/Credit Card Out” configuration, or be designed with ticketless entry and exit lanes, using a PC-based “Credit Card In/Credit Card Out” configuration. Credit authorization is integrated seamlessly with the credit card processor built into the SST parking control equipment. The credit card processor (with built-in modem) transmits the transaction information to the financial processing network for authorization and settlement. The point-of-sale terminal inside the equipment displays the transaction total, automatically authorizes and captures the transaction for settlement, and prints credit information on the customer receipt and/or journal tape. 3M engineers have designed the Smart System Transport (SST®) to accommodate a wide range of ticket handling capabilities, including issuing and reading tickets, and accepting ISO standard credit cards from one mechanism. This single slot transport simplifies the transaction process. The credit card processor used with the SST equipment is the DataTran™ 162 External Financial Processor (manufactured by Datacap Systems, Inc.). This processor handles all transactions with the financial network (sometimes referred to as the “clearing house network”), batch functions, and reporting. This unit is certified with over twenty credit card processing networks. Information Needed In order for you to use the Credit Card System, the following information must be programmed into the DataTran: • The financial processing network you will be using. When ordering the system, it is necessary to specify what network is used by the merchant’s credit card processor. There are two financial processing networks which have been incorporated into the 3M system and approved to date: (1) Global Payment Systems (GPS) - using MAPP, a host-based network, and (2) Sears Payment System (SPS) - using a terminal-based network. 3M can program other networks (such as NDC/Visanet, etc.) for a development fee. You or the merchant need to contact the processor sales rep, and let the processor know that the merchant is implementing or converting to Integrated POS using DataTran for network interface (rather than credit card terminals). You will also need to know the merchant parameters required for the Integrated POS installation. • Your account information, which is referred to as Merchant Parameters. Your bank or service provider must provide this information to 3M before the equipment can be shipped. You must obtain the appropriate forms from 3M and have the bank or service 158 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual provider complete the necessary account information. It may take as long as six weeks to obtain this information. Instead of providing the information to 3M, you can program the account information through a standard PC with a serial port using a software program, provided by Datacap, called Pop Set-Up. Setting Up the Credit Card System To use the PowerPad for credit card processing, you must activate the Credit Card system in the SST Ticket Validator. To do this, complete the following steps: 1. Log on to the PowerPad and press the Prog/Print key. 2. From the Program menu, select System Pref. 3. From the System Pref menu, select Credit Card. 4. In the Activate Credit Card field, press the Date/No key until Yes is displayed. Then press the Time/Yes key. 5. In the Print Signature Slip field, press the Date/No key until Yes is displayed. Then press the Time/Yes key. 6. Press the Esc key to return to the previous menu. You must also program the Alternate Payment key to process credit cards. To do this, complete the following steps: 1. Log on to the PowerPad and press the Prog/Print key. 2. From the Program menu, select Keys. 3. From the Keys menu, select Alt Payment Key. 4. In the Alt Payment field, enter the name of the Credit Card attendants can accept. Then press the Time/Yes key. 5. In the Status field, press the Date/No key until Credit Card is displayed. Then press the Time/Yes key. 6. In the Type field, press the Date/No key until the Credit Card you want to accept is displayed, or until “All Cards” is displayed. Then press the Time/Yes key. 7. Repeat steps 4 - 6 until you program all the types of payments you want to accept. Then press the Esc key. Automatic Pay Stations and PowerPads with motherboards of Rev G. or higher can be upgraded for credit card processing. See the Credit Card System Installation and Operation Manual for more details. Clearing the YTD Lane Report For both B and C platforms, but not platform A, the Clear YTD Config option should be set to “Yes” to ensure that the YTD Lane Report is cleared. If the PowerPad does not have Clear YTD as a Config option, you cannot perform this function. DIPswitch #6 on the PowerPad CPU Board should also be set to “Open” to allow the YTD Lane Report to be cleared. If DIPswitch #6 is closed, the YTD Lane Report cannot be cleared. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 159 PowerPad Internal DIP Switches DIP Switch Value 1 1 2 2 3 4 4 8 5 16 6 Year To Date (YTD) Clear. Open = On. Closed = Off. (You must purchase the YTD Clear option for the PowerPad). This will give you the ability to clear YTD totals which are usually non-resettable. 7 Close to terminate communication for port 2 (commonly used for ScanNet). Otherwise keep open. 8 Close to terminate communication for port 1 (commonly used for the earlier style DataCap). PowerPad Not Vending Gate If the PowerPad will not vend the gate, try this test: 1. Program the No Sale Key to vend the gate. 2. If you press the No Sale Key, the gate should vend. 3. If you look inside the PowerPad power supply, you will notice that the relay labeled GATE V RLY will fire, and the LED next to the relay will flash every time you press the No Sale Key. 4. If the relay doesn’t fire, then the problem is between the PowerPad and the power supply. a. It is possible that the config output for Recp 7, output 5 is not set for “Gate.” Check the Config>Outputs for the PowerPad. It should be set like the following: Programming>System Preferences>Config Options>Output. Recp 4 15 1 Cash Drawer 1 13 2 Cash Drawer 2 11 3 Duress 9 4 VC Gate 7 5 Gate 5 6 Custom 3 7 Display Out 1 8 Logon Light If Recp 7, Output 5 is set incorrectly, you may edit your config chip for a maximum of two weeks. After two weeks, the config chip will initialize itself and return to its original burned options. For more information on editing the config chip, see Editing 160 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual Configuration Chips for Auditor PowerPad, Automatic Pay Station, Credit Card Exit Verifier, Automatic Cashier Terminal, and MG-1500/ML-3500 Spitter . If this is not the problem, continue troubleshooting the system. b. Replace the PowerPad only. It could have malfunctioning circuitry that is not sending the appropriate message to the power supply. c. Replace the 50-pin connector between the PowerPad and the power supply. It could have a broken wire. d. Replace the power supply. The power supply relay or circuitry could be malfunctioning. 5. If the relay does fire, but the gate still does not raise, there is a problem between the power supply and the gate. a. Check the power supply by putting a Multimeter on outputs 7 and 8 (gate vend). When you press the No Sale Key, you should see a temporary short across these two terminals. If you don’t see the short, then the problem is the power supply. Send the power supply in for repair. b. If the relay fires, and the power supply outputs close on 7 and 8 (gate vend), then the problem is either the wiring between the power supply and the gate, or the gate itself. Test the wiring by installing a wire between outputs 7 and 8 on the power supply. If you see the input light up at the gate, then the wiring between the power supply and the gate are ok. c. Since a. nor b. were the cause, the problem is in the gate. replace the gate’s Omega controller. To test the gate, short the two wires at the gate that the power supply relay would have shorted. Depending on the mode, you may need to create loop A presence by placing a metal gate door across the loop. PowerPad Not Vending Drawer If the PowerPad will not vend the drawer, try this test: 1. Program the No Sale Key to vend the drawer. 2. If you press the No Sale Key, the drawer should open. 3. If you look inside the PowerPad power supply, you will notice that the relay labeled CASH D. 1 RELAY will fire, and the LED next to the relay will flash every time you press the No Sale Key. You will also hear the solenoid inside of the cash drawer firing every time you press the key. 4. If the relay doesn’t fire, then the problem is between the PowerPad and the power supply. a. It is possible that the config output for Recp 15, output 1 is not set for “Cash Drawer 1.” Check the Config>Outputs for the PowerPad. See page 1 of the February 2003 Field Service Tips issue for Config Outputs. If Recp 15, Output 1 is set incorrectly, you may edit your config chip. For more information on editing the config chip, see Editing Configuration Chips for Auditor PowerPad, Automatic Pay Station, Credit Card Exit Verifier, Automatic Cashier Terminal, and MG-1500/ML-3500 Spitter . If this is not the problem, continue troubleshooting the system. b. Replace the PowerPad only. It could have malfunctioning circuitry that is not sending the appropriate message to the power supply. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 161 c. Replace the connector between the PowerPad and the power supply (50-pin connector). It could have a broken wire. d. Replace the power supply. The power supply relay or circuitry could be malfunctioning. 12. If the relay does fire, but the drawer still does not open, there is a problem between the power supply and the drawer. a. Make sure that the cash drawer is wired properly. Cash drawer 1 should be wired to the power supply in the connector labeled CASH DRW. Verify that the drawer is wired as follows: 1 – Black 2 – Red 3 – Green 4 – White b. If the cash drawer is wired properly, the relay is firing, but the drawer is still not opening, the solenoid is bad. Send the drawer in for repair. 162 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual Deciphering the Journal Tape L# 1 Current PowerPad is Lane number 1 (typically seen on power up) A# 1 Currently logged on attendant is Attendant 1 (typically seen on power up) A02 Validation for ticket/Type and amount is defined under account A02 P+ The plus key added this amount M- The minus key subtracted this amount L02 Lost ticket/Fee generated with Fee Table 2 m1, m2, m3, or miscellaneous key numbers 1, 2, 3, or 4 m4 NO SALE A# 1 Attendant 1 has hit the No Sale Key Create VC 000000001 IL 01 0001 Create ValueCard 1 (in lane 1 by attendant 1) LP License Plate number Time Excpt Time exception. (License plate was marked as in with the LPI Hand Held, but the patron is exiting the lot with a ticket that was spit during the time they were already parked. This could be due to the patron purchasing an illegal ticket.) LPI Override Attendant decided to accept the “illegal” ticket that was spit during the stay in the parking lot No Response Com No response from ScanNet Bad Fac Code Bad facility code ccard credit card vc ValueCard Debit Debit type ValueCard Access Access type ValueCard Month Monthly type ValueCard Keys Making Noise but Not Performing Function Some keys on the PowerPad are two times the width of most keys, and most don’t know that underneath these keys are two positions that could potentially be pressed, depending on how the key is installed. Some of these keys are RECEIPT, RECALL, VOID, and CLEAR. If the keys are installed backwards, they will still emit a beep noise when Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 163 pressed to let the operator believe the key was installed properly. 3M is implementing new testing measures that will catch this manufacturing issue, but we wanted to let you know that you can fix this problem in the field by turning the key around. Device Address Stuck on Zero When you first set up your facility, you must define each device at the facility with a unique device number per port. It has been reported that customers have not been able to set the addresses on certain PowerPad driven devices such as an ACT or an APS. At the factory, we have discovered that it is a manufacturing defect. There is usually something wrong with the address DIP switch circuit, or perhaps the surface mount resistors on the back of the circuit board. There is no way for a technician to fix this in the field, so if this symptom is found in the field, the board will have to be sent in for repair. Power Supply Revision E2 and Older Not Suitable for Upgrading Rev E2 and earlier is not suitable to upgrade because of a hardware upgrade needed to fix noise on the display circuit. If a Rev E2 power supply board without the hardware upgrade is used in an ACT or MG-1500 Spitter or Exit Verifier, you will see multiple characters on the display (part #82-20059). For instructions to perform the upgrade, see “Upgrade Instructions for multiple characters on ACT, APS, MG-1500 Spitter and Exit Verifier, SST Ticket Spitter and Exit Verifier, Display 82-20059” under the header ACT. The earlier style PowerPad power supply Rev D does not have a Port 3 connector (data connection to the PowerPad expansion board) or the RECP 10 (extra field input for receipt and cancel buttons) needed for ACT or MG-1500 Spitter. Because these two connections cannot be made to the earlier PowerPad power supply version D and older, a customer wishing to upgrade their system to a different device must order a new power supply that has these two connections. Currently we use Rev F power supplies. Buffered Transactions The PowerPad comes with two RAM chips, which gives you a buffer space of approximately 3,939 basic transactions (with no PowerPad configuration). Your buffer space will be decreased depending on the size of your PowerPad configuration like fee tables, attendants, and ValueCard. You can increase the PowerPad buffer size to 14,022 basic transactions (with no configuration) by adding RAM to the PowerPad in IC locations U6 and U8. You will need to order two ICs, 512KF*8 SRAM chips, part number 11-9313 from your Customer Service Representative. SRAM Added to Assembly Two SRAMS, U4 and U8 were added to the PowerPad assembly. This increases the total RAM to 2 MB, which allows for a larger transaction buffer and prevents lost transactions. 164 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual Credit Card Vouchers Credit card vouchers allow your customers to use their credit cards for discounts and eliminate extra voucher tickets that the customer will have to carry. To program the account key status for validation or voucher, enter the first eight digits of the credit card that is to be discounted, choose the type and amount (example fixed amount of $1.00) and if you want the customer to have a maximum limit of $1.00, you must program the limit as $1.00. At the SST PowerPad, the cashier will generate a fee (example $5.00) by inserting a transient ticket. When the cashier inserts the patron’s credit card, the patron will receive a voucher discount of $1.00, and the total fee will now be $4.00. The patron may use the same credit card to pay for the $4.00 fee. Can I use B Platform Firmware in a C Platform Board? No. You can use C platform PowerPad firmware in a B platform CPU board, but you cannot use B platform firmware in a C platform CPU board. At present "C" version PowerPad software (C2.9.0, C3.3.0, C3.3.1 etc.) is compatible with both "B" and "C" platform PowerPad hardware. Starting with version C3.4.0, the software will not be backwards compatible with the "B" boards. The last "C" software version released for "B" boards is C3.3.1.3. The C platform PowerPad CPU board was introduced in November of 2000. 3M redesigned the PowerPad CPU board for the following reasons: *Increased CPU speed from 12MHZ to 16MHZ *Address Xilinx and Rockwell dual acia obsolescence issues. Using Version C Firmware on B Platform PowerPads When using Version C software with a B platform PowerPad, you may experience Aborted By Device errors in the ScanNet log or Timeout errors at the PowerPad when sending multi-block programming to the PowerPad. This normally occurs when communicating to the PowerPad at 9600 baud using a NetPort Controller. The solution to this is to decrease the rate to 4800 baud. The problem is caused by the limitation of the hardware architecture of the B platform PowerPad. You should not experience this using Version C software with the C platform PowerPad hardware. A Platform Versus B platform Firmware Currently, Version A1.8.14 is the most recent firmware for the A platform PowerPad. Version B3.3.3.2 is current for the B platform. The B platform firmware supports the Hotel Package, Extended Transaction Buffer, Hole Punch Validator, and Expanded Accounts options. In order to change from A platform firmware to B platform, both hardware and software changes are required. PowerPad Fee Computer Platforms: Platform A/Platform B 3M has enhanced the PowerPad to increase performance. In doing so, the amount of RAM and ROM memory has been doubled in the new Platform B. 3M Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 165 started shipping PowerPads with version B.2.0.1 firmware and associated hardware as of October 1, 1998. Because this new platform is different from the A.1.x.x platform, the required hardware and software is unique for each. It is important to note that the PowerPad with version B.2.x.x firmware is not compatible with the PowerPad with version A.1.x.x firmware. Config PROMs and system odd and even EPROMs cannot be interchanged. They will not work with the incorrect PowerPad platform. The version numbers will increment as we add enhancements and other changes to the software. The important point to keep in mind is to check for an “A” or a “B” in the version number. This indicates a major difference. When a customer orders an option upgrade to an PowerPad, it is important to note the firmware version, including the platform, and indicate this on the order. That way, Production will burn the correct config. If the version is not noted, Production will assume the version is B.2.x.x. The same process must be followed when a customer orders an update for the system odd and even EPROMS. 3M will continue to support Platform A; however, new features and enhancements will be designed for Platform B only. Upgrading the PowerPad If you have a ver I, it can only be A platform. Version J can physically be upgraded to A or B, but it isn't allowed unless they have permission from Manufacturing Supervisor. It hasn't been ECO's for customers; therefore, DRC has to get Manufacturing Supervisor's approval for it. There was an ECO issued for the upgrade to be done in production only. For rev. J you have to cut traces and run wires to successfully upgrade the PowerPad. K1 can be upgraded for both A or B. K1 can use C software. I or J power pads can't be upgraded to C ver. You can put version C firmware in a version B board, but the C2.7.3 and earlier than that can not go into A.P.S. Only the C2.7.4 Can go into all three, B version PowerPad, C version PowerPad, or APS. At present "C" version PowerPad software (C2.9.0, C3.3.0, C3.3.1 etc.) is compatible with both "B" and "C" platform PowerPad hardware. As we add more features in the "C" version software, we increase the risk of problems occurring in the "B" platform hardware. This is due to the out-dated architecture and slower processor speed of the "B" platform boards. Starting with version C3.4.0, the software will not be backwards compatible with the "B" boards. The last "C" software version released for "B" boards is C3.3.1.3; this is for the PowerPad Fee Computer (APP), the Automatic Cashier Terminal (ACT), and the Credit Card Exit Verifier (CCXV). The last version for the APS is C2.7.4. If a customer wants to order a new feature that's not supported in the "B" platform, they'll 166 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual need to purchase new motherboards. We will still fix bugs as they are reported in "B" version software but will not add any new features. The "C" character will be changed to "B" so the next version will be B3.3.2. For APP, ACT and CCXV. The APS will be B2.7.5. Version C4.1.0.3 The following enhancements have been implemented to the PowerPad platform firmware: * ScanNet now receives enough information from the PowerPad to properly fill out the Grace Exit Report and the Duration by Tickets Report. * Coins that are set to Unused are no longer being accepted. * In Grace exits are now being sent to ScanNet. * The MG-1500 Ticket Spitter no longer prompts for an “Action Card” when it should not. * Event Mode now works correctly at the MG-1500 Ticket Spitter. * When the programming for LPI is changed to Mandatory and Days Not Found is set to 1, programming is no longer lost when fee table 13 is accessed. * The intermittent situation where a transient ticket was inserted into the APS for payment, payment was made, but the ticket failed to be returned to the customer has been fixed. * When you issue a series of ValueCards with a burster, the device automatically dispenses each ticket without needing an attendant to pull out each one. If the previous ValueCard is still in the throat, it will briefly be pulled back in and then ejected again. You will have to pull the last ValueCard out of the throat before the system will be ready for the next transaction. There is a few seconds delay between each ValueCard issuance. * When using Continuous Fee, if you enter a ticket number due to the ticket being unreadable, the PowerPad now generates the correct continuous fee. * Credit Card Signature Slip functions have been returned to normal. A cash credit slip, issued by an APS, may be printed with a receipt only if the Config Options/Taipei Receipt is set to Yes. When set to Yes, and the receipt key is set to Automatic, you can print both a receipt and credit slip on one document. * Power Fail Mem OK messages from PowerPad-based devices now appear correctly in the ScanNet System Activity Monitor window. * Added code to dynamically allocate FeeCalc memory. If two SRAM chips are installed, the system allocates 11000 bytes for FeeCalc use. The two-chip configuration supports 16 segments, with 40 rate blocks per segment. If four SRAM chips are installed, 63000 bytes are allocated for FeeCalc use. The four chip configuration supports 99 segments with 40 rate blocks per segment. Other FeeCalc enhancements include: * FeeCalc memory is now checked when a segment is copied, a new segment is created, or a new rate block is added. * The FeeCalc Memory Full message now displays long enough to read. * The FeeCalc Memory Full message is now sent to the journal and sent to ScanNet as an alarm. * Boleta and Factura (Receipt and Invoice) numbers no longer change when operating in Tutor Mode. Receipts created while in Tutor Mode are marked as such. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 167 * Six additional Pre-Pay keys were added to the Keys/Pay Any Time field. A total of 12 keys are now available. The Cashier and Lane reports were also enhanced to support breakout information regarding Pre-Pay usage. * The configuration situation that caused THU to display in the NYParks config option field has been correction. This occurred when an older application config ROM chip was used with newer application firmware, and the new application firmware contained options that the config ROM did not. * Remote Debit, Remote Logoff and Remote Vend have been added. * You can now issue a credit slip (from the Burster) when using a voucher that has been cancelled. (Requires ScanNet version 5.1.2.13L1 or higher for full functionality.) Version C4.0.0.21 The PowerPad firmware has been changed to include the following: * Changed the way memory is allocated for fee calculation. If four SRAM chips are installed, the PowerPad will dynamically allocate additional memory. * All enhancements and new features from C4.0.0.20 are included in C4.0.0.21. Note: All new PowerPads come with four SRAM chips. If upgrading a customer who only has two SRAM chips, it is suggested that two additional SRAM chips (Part number 11-9313) be installed. Version C4.0.0.20 Several enhancements and new features were implemented including the following: Enhancements * The PowerPad will now ignore the cashiering type on the SST tab from the ScanNet>Programming>PowerPad/APS>Preferences. To program cashiering type from ScanNet, use the Lane Description tab on the PowerPad/APS Programming>Preferences screen. * When using credit cards at a PowerPad, credit card number entry is not required to complete the transaction. A “Manual CC Number Entry” field has been added to the System Pref/Credit Card menu to be programmed as either Mandatory or Optional. If Mandatory is selected, the cashier must manually enter the credit card number to complete the transaction. If Optional is selected, the credit card may be entered but is not required to complete the transaction. NOTE: In the ACT, this field is hidden during unmanned operation. To use this feature, the attendant must be logged on in manned mode (attendant 2+). * The information that is printed on the ticket and receipt when a prepaid parking ticket is issued will now reflect all of the relevant information. The receipt header is now programmable from the receipt menu. Up to 24 characters of the header will now be displayed. * The maximum value for a ValueCard debit card is $10,485.75 USD. The creation and add-on procedures now limit input values to this amount. * The PayAny field on the Program PayAnyTime screen now works correctly when set to Variable. * The Manual indication on validated lost tickets by time has been restored. No 168 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual additional adjustments are necessary. * A new field called “Service Code” has been added to the credit card Alt Paymt key programming. Setting the Service Code to Credit will permit actual credit cards otherwise already defined. Setting the Service Code to Debit will permit acceptance of actual debit cards that require no PIN. Setting the Service Code to Any will permit both types of cards and is the default. * The issue where the APS journal printer printed out “System Buffer Full” every instance a note vault cassette was removed has been corrected. * ValueCard transaction programming is now defaulted to “Armed and Gate.” * The delay/hesitation issue has been addressed when inserting a ticket into an SST Ticket Spitter Model MG-1500. * The issue where you couldn’t cancel after pressing the Alternate Payment key with only one credit card type programmed has been corrected. * Configs can now be programmed with the function of Credit Card with the Ingenico driver. * The issue where the time was not advancing on the customer display has been corrected. * The SST Ticket Spitter Model MG-1500 now sends the ticket to ScanNet ticket tracking properly while it is in “Event” mode. * The issue when inserting a parking ticket and not letting the transport take it in, causing a false start has been corrected. * Receipt and invoice numbers can be reset by the master attendant making these numbers different from transaction numbers, since transaction numbers are not resettable. * The “Please Wait” message seen during the note vault initialization process has been changed to be shown briefly. * Programming the ACT or SST Ticket Spitter Model MG-1500 for the Issue Ticket Key, “Mark Paid Tickets Used” set to “Yes” properly sends the ticket to ScanNet ticket tracking to the validated ticket stack. * When using the ACT or SST Ticket Spitter Model MG-1500 programming for the Issue Ticket Key with “Issue Prepaid Ticket” set to Yes and “Mark Paid Tickets Used” set to No puts the ticket on the paid stack. * Override is now tied to both ticket tracking programming and backout programming. * Using an account key set to “Charge” no longer causes the printer to go offline and come back online. Account charging now works correctly. * Automatic Cashier Terminals and Credit Card Exit Verifiers now vend when a patron uses either a transient ticket or ValueCard. * Errors for incorrect credit card entry at the PowerPad have been corrected. * Access type ValueCards are now treated as exit or entry depending on PowerPad lane configuration. New Features (Customer Specific) * When programming the Automatic Cashier Terminal or SST Ticket Spitter Model MG1500 programming for the Issue Ticket key, “Mark Paid Tickets Used” has been enhanced so the field is available when issuing Pre-paid tickets. This was developed for the Kennedy Center in Washington, DC. * PowerPad programming was enhanced to allow you to program the boleta/factura receipt printing, a feature that was added to the PowerPad to allow the cashier to print Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 169 either a boleta (standard receipt) or a factura (business receipt/invoice). This was developed for Lima, Peru. * Serial Communication between PowerPad lane devices and the Central Tower Controller (CTC) is now supported. The CTC is a central server to control automatic vehicle parking. This was developed for Ban Chaio, Taiwan. Version C3.8.0.19 The following enhancements were implemented: * The situation that caused the credit card number to print in the ticket field on the receipt when processing credit card in/credit card out transactions has been corrected. * Monthly ValueCards now work correctly when the Ticket Spitter is out of tickets. * The situation that caused the PowerPad to reset after creating a voucher has been corrected. * MG-1500 Ticket Spitters, with the ValueCard Capture feature activated, will now operate properly and capture expired monthly ValueCards. * The situation that prevented the Full status from changing when a full cash box was emptied and reset has been corrected. * All ValueCards created and processed in the PowerPad will now be read and verified at the time of creation. * Full ValueCard functionality has been added to the MG-1500 Ticket Spitter. Version C3.6.0.11 The following development and enhancements were implemented: * The rounding error that occurred when using back-out taxes with fees calculated from fee tables has been corrected. * The situation that forced a “void incomplete” when fee computations required more than 10 seconds to complete has been corrected by increasing the time allowed for the SST to respond to a poll to 1 minute. * The time-out value (1-999 seconds) for waiting for a message from the LPR system is now programmable in the LPR menu of the PowerPad. * A patron can now use a credit card to prepay for a transient ticket on a SST Ticket Spitter that has been programmed appropriately. The ticket is valid for a programmable length of time. If the patron exits the parking facility within that time period, no additional fees are assessed. * The situation that caused add-on taxes to act like back-out taxes has been corrected. Version B3.3.3 This version includes the following changes: * The PowerPad would force a void incomplete transaction if the fee computation took longer than 10 seconds. It now has 60 seconds to compute the fee. * The issue with incorrect rounding in backout taxes from a calculated fee has been resolved. * Creating a ValueCard with the First Use option now works properly when start and end 170 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual dates are entered. B2.4.0 Switching to Central Cashiering To change the cashiering mode on PowerPads (Version B2.4.0), you need to go to the Lane Description menu and follow the prompts. This feature used to be found under the Ticket Tracking menu for Bar Code systems or the SST menu for SST systems. However, it was moved under the Lane Description menu to support the new Bar Code Central Cashiering feature. Please note that in the ScanNet Central Management system, you will still find the Cashiering Mode feature under the SST menu, not under the Lane Description menu. Version B2.3.0 If you update your PowerPad Fee Computer to Version B2.3.0 and you have a Fee Display, you must move Jumper “J4” in the Power Supply to the position marked “display.” Recent changes to the software now look at this jumper setting. Version B2.3.0 Switching from Exit Mode to Central Mode for a Single Transaction If you have firmware Version B2.3.0, you can do so by pressing the Jump key immediately after pressing the Shift key. Version B2.0.1 Changes that affect the PowerPad Fee Computer include the following: * The operation of the License Plate Inventory (LPI) key when used in conjunction with magnetic media has been modified. * Users who were previously unable to use cashier cards while in the Report or Program mode can do so now. Changes that affect the Automatic Pay Stations and Credit Card Exit Verifier include the following: * In situations where a ticket is returned to a patron because of an error (for example, a used ticket), the error message will now stay on the LCD screen until the ticket is retrieved. * Users who were previously unable to insert a transient ticket within grace time after running a backout credit card transaction can now do so. Some changes that affect all three products include the following: * The SCAN Facility Management System can no longer be used to change the printer ports. The ports are designated by the config chip. * The Alternate Fee field for merchant programming now allows two digits instead of one. Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 171 Version A1.8.5 & A1.8.6 The following changes were included in Version A1.8.5: * Users can now set the paid and unpaid grace time to 0 without the PowerPad automatically vending the gate when a ticket with a stay period of less than one minute is inserted. * When users use Config Options to print the note dispenser status, the status on the LCD display now matches the printed status. The following changes were included in Version A1.8.6: * When the PowerPad is in the Central Cashiering mode, the option to vend the gate is now present. * The Vouchers feature is now Y2K compliant. * The Void count is now saved for Attendant #12. Version A1.8.2 This version addresses several situations that you may be experiencing with older PowerPad versions. The ValueCard Anti-Passback feature was corrected so that the disabled flag is checked as appropriate, the ValueCard option was changed so that the correct fee table number displays on all ValueCards, and communication between the SST and the PowerPad was improved. These changes affect PowerPads used in Fee Computer, Automatic Pay Station, and SST Exit Verifier programming terminals. Version A1.7.7 If the PowerPad and DataTran lose connection, some credit card customers may be inadvertently charged twice. Version A1.7.7 of the PowerPad includes a safeguard to prevent this. Version 2.2.0 The following changes have been made to the PowerPad (Version 2.0.0): * Transient tickets, ticket vouchers, and regular vouchers, all of which have three data fields each, are now Y2K compliant. *With the SST/HP-4 Transport, the message on the Exit Verifier or Automatic Cashier Terminal display reads “unreadable, try again” instead of “insert correctly.” The message on the PowerPad display reads “unreadable ticket.” Version 2.0.1 This version includes a number of significant enhancements. Among other improvements, we added the Cashier Card feature; added support for Lost By Time values associated with License Plate Inventory (LPI) transactions; expanded receipt headers and trailers up to six lines each; implemented the Hotel ValueCard package; improved Year 2000 functionality to support all exit times from 1990 to 2005; 172 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual and increased the maximum number of merchants supported to 640, the number of vouchers to 208, and the number of ValueCards to 26. These changes affect the PowerPad Fee Computer, the Automatic Pay Station, and the Exit Verifier. Version 1.8.7 If you are using an PowerPad Fee Computer, an Automatic Pay Station, or a Credit Card Exit Verifier and you complete a transaction in tutor or cashiering mode, the SST Transport will now encode tickets as “used.” Subsequently, the Exit Verifier would not process tickets marked “used.” Troubleshooting Manual 78-0060-4094-9, Ver. 1 PowerPad • 173 174 • PowerPad 78-0060-4094-9, Ver. 1 Troubleshooting Manual RC2 Introducing the RC2 Ramp Controller The New Ramp Controller 2 (RC2) replaces our existing Ramp Controller. RC2 can perform everything that our previous Ramp Controller did plus more. The RC2 provides additional control to your parking system and offers high reliability and flexibility in configuring up to five lanes. Features * Communicates counts, loop status and device status to ScanNet. * Counts vehicles in multiple lanes or ramps entering or exiting in the parking facility. * Provides ScanNet with the data necessary to maintain an accurate, real time vehicle inventory for each of the facility parking areas, lots and zones. * Directs traffic into or away from parking areas by activating or deactivating “Full” or “arrow” signage systems. * Eight digital outputs (pulsed or latched) are mapable for various lane-control. (Standard usage is “Full” signs or counters.) * Five mapable self-tuning vehicle detectors, which can be set up in various lane configurations. It monitors up to two bi-directional lanes, five uni-directional lanes, or a combination of the two. * Controls up to four high voltage relays, such as 3M’s “Full” signs at 115/220VAC. * Programmable via an IR interface using a personal digital assistant (PDA.) * Tune and reset vehicle detectors. * Tailgate Recognition System. Pricing Part Number Description List Price 12-10415 RC2 Junction Box $3,200.00 12-10416* RC2 Power Supply $1,500.00 * Note: Power supply handles up to 10 RC2s depending on the wire gauge used and the length of the wire run. See Wire Run Specifications. Troubleshooting Manual 78-0060-4094-9, Ver. 1 RC2 • 175 Wire Run Specifications Up to Ten Daisy-Chained Ramp Controllers to One Power Supply Maximum Distance – From Power Supply Wire Gauge to Last Daisy-Chained RC2 #16 AWG (1.50 mm2) 550 feet (168 meters) #14 AWG (2.50 mm2) 880 feet (268 meters) #12 AWG (4.00 mm2) 1,400 feet (427 meters) Up to Ten Ramp Controllers Connected Directly to One Power Supply Maximum Distance – From Power Supply Wire Gauge Directly to RC2 #16 AWG (1.50 mm2) 2,800 feet (853 meters) #14 AWG (2.50 mm2) 4,500 feet (1,372 meters) #12 AWG (4.00 mm2) 7,000 feet (2,134 meters) * Note: Ten COM and ten +24 VDC connections for this are provided in the power supply terminal block. Version 1.0.0.15 The Ramp Controller 2 is now available for purchase. The 3M Ramp Controller 2 works in conjunction with the ScanNet Central Management System to count vehicles entering or exiting ramps and/or lanes in a parking facility. You can download firmware updates to the Ramp Controller 2 via the Flash Programmer utility. The Flash Programmer utility and the Ramp Controller 2 Program Utility version 1.2 for the Palm PDA is now available on the 3M web site. 176 • RC2 78-0060-4094-9, Ver. 1 Troubleshooting Manual SCAN DOS Why does my SCAN DOS system take so long to retrieve information from the SCAN Data Manager? When SCAN collects data, it separates the data into many files according to the type of message and by individual devices. As a result, many files are created daily. DOS file systems limit the number of files per directory. As the number of files saved exceeds approximately 6000 in a single directory, your computer has difficulty finding information in that directory. Thus, the hard drive labors to retrieve data. To shorten the retrieval time, use the SCAN copy and delete options to remove older data from the drive, and periodically defrag your hard drive to optimize the drive’s free space. Our SCAN DOS was off-line for awhile, and I don’t want to print out all of the messages during that time. How do I clear the buffer? You need to delete the Print Spooler file. ($$$Pfile$$$) Follow these steps: From the main menu Go to the Disk Utilities Menu Then Delete menu Then Unique Files Select drive "c", then for the file type toggle the F9 key until "Print Spooler File" appears Press the "Enter" key The Print Spooler file will appear and prompt you for $$$PFILE.$$$? Are you sure? Press the "Y" key for deletion. I have one device on my SCAN System that intermittently drops offline and then comes back online. What should I check for? There are a couple of things to check. First, have any devices been changed recently? You may have two devices on-line with the same address. Second, you may need to check other devices in your system other than the one that seems to be going off-line. SCAN continuously communicates to various devices via a port controller. Occasionally, a device may drop off-line, or a number of devices may drop off-line. The device that SCAN shows as being off-line may not actually be the one that is offline. It could be the previous device or the one that follows the device that is indicated as being the off-line. Removing the 422-communication connector from either of these two suspected devices should cause all devices on the port controller to come back on-line. Change the Transmit and Receive ICs. If this does not provide the solution, disconnect all communication cables from all devices and plug one in at a time, while constantly monitoring SCAN. Verify that devices come on-line and stay on. If plugging in a one device causes another device to go off-line, the device that was plugged in could be the offending device. Troubleshooting Manual 78-0060-4094-9, Ver. 1 SCAN DOS • 177 Is it possible to run SCAN in Windows? The current SCAN Facility Management System is a DOS-based system. Although it may run in Windows for a short period of time, it was not designed to run in Windows and 3M does not recommend doing so because errors could result. If you are in Windows and want to run SCAN, reboot your computer in DOS by choosing “Shut Down” from the Start menu and then choosing “Restart in MS DOS Mode.” Then you can run SCAN through DOS. Do not simply choose “MS DOS Prompt” from the Programs menu in Windows. When you do this, you are actually running an emulation version of DOS through Windows, which does not support true DOS operating features. Scan NT, the new facility management system scheduled for release later this year, is a Windows NTbased system. Is it possible to run SCAN DOS with Windows 2000? No, Windows 2000 does not have a true DOS mode, therefore it can not run SCAN DOS. You will have to use Windows 95 or Windows 98 using MS-DOS 6.2. Running DOS from the Start Button/ Programs/ Accessories/ Command Prompt is not a true DOS environment. You will have to start up in DOS mode when first booting up the computer. Working With the SCAN DOS Backup Utility The following information will help you use the SCAN Backup Utility to organize and store your data efficiently. The SUBST command enables you to fool DOS by directing file output to any subdirectory on the hard drive or a floppy drive by assigning that path its own drive letter. For example: If you use the subdirectory :\DATA\DOC\PERSONAL\ frequently, you could assign that path a drive letter such as G:\ and include that command in your AUTOEXEC.BAT file. Once the command is executed, you need only type Dir G:\ to view the contents of the C:\DATA\DOC\PERSONAL\ subdirectory. To save the file ABC.DAT to that same subdirectory, use the path G:\ABC.DAT. To use the extended drive letter extensions, you must have the LASTDRIVE=n statement in your CONFIG.SYS file, where n is the last drive letter you will need to identify up to M. Typically, F would not be used because this is usually reserved for the server drive designation in a network configuration. For SCAN backup routines, you should preformat the floppy or Zip drive with a subdirectory for each of the report or data types you will be archiving. List each line, as it will appear in the AUTOEXEC.BAT. In the following example, the lines in italic would appear in the AUTOEXEC.BAT. SUBST G: A:\A2RPTS96 (Auditor reports for 1996) SUBST H: A:\TXNS0896 (Auditor transactions for 8/96) SUBST I: D:\CLOG0997 (9/97 cardlog, where D is Zip Drive) CONFIG.SYS would include the line LASTDRIVE=I for this example. If you are referencing removable media such as floppies or Zip disks, have the appropriate disk labeled and installed prior to using the logical drive reference. If the wrong disk is in the floppy drive, you will get an error reading the drive because the path you have specified for that logical drive letter is not on the floppy being read. Avoid storing more than 2000 files in any subdirectory and never more than 200 in a root directory. (Root directories are not recommended for data storage.) This rule allows you to remove unnecessary files 178 • SCAN DOS 78-0060-4094-9, Ver. 1 Troubleshooting Manual before you exceed the DOS file limit, which can slow down your system and cause irreparable damage to the disk drive data forcing you to reformat the drive and lose all the drive data. One final note: Before making changes to your CONFIG.SYS and AUTOEXEC.BAT files, have a backup bootable disk with a copy of both files on it. Setting Hot Keys When setting hot keys in SCAN, do not change the setting for Control-V. This key combination is factory set to display the version and serial number of your SCAN system. When you call for help and need to check your SCAN version, you can press Control-V to find out what it is. Troubleshooting Manual 78-0060-4094-9, Ver. 1 SCAN DOS • 179 180 • SCAN DOS 78-0060-4094-9, Ver. 1 Troubleshooting Manual ScanNet Problem Checkpoint setting up ScanNet Server/Client 1. Check your networking permissions between both computers. If you are not networked properly, the client machine appears to work only part way. Can you ping from the server to the client, and from the client to the server by computer name? Choose Start>Run and type “cmd” and click on OK. After command prompt, type ping X (where X is the other computer name, and not the IP address of the other computer). You should get a reply both ways, otherwise, you are not networked correctly. ScanNet requires IP address resolution by name. If you can not ping it by name, but you can ping it by address, then you need to add an entry into the LMHOSTS or HOSTS file depending on your system. Contact Product Support at 877-777-3571 for further information on this subject if needed. 2. Each computer is going to have its individual computer name, but when setting up the client, it has to have the same computer name as the server computer in Configuration>ScanNet Properties. 3. Also check in Windows Explorer>Scan_NT folder>Initial folder>Scan_NT.ini and make sure that the computer name listed in the initialization folder is the server computer name. It is listed there at least four times. It will be in the initialization folder more times per Port Controller configured in ScanNet. There can’t be any spaces in this name. 4. Both computers have to have the ODBC configured exactly the same way. 5. TCPIP has to be checked in both computers under ODBC. 6. Both computers have to have a name and password that is exactly the same defined to log on to the computer. In Microsoft Windows 2000, go to Settings, Control Panel, Users and Passwords. The user name and password you log in with at the ScanNet server computer must exist as a user on the ScanNet client computer. If it does not exist, you will not be able to access the database on the server computer from the client computer. 7. The “Guest” user account must be enabled on both the server and client computers. If it is not, ScanNet will only appear to be working only part way. 8. In ScanNet 4.X, under Systems>Access Control Systems>Credential Maintenance>System Maintenance>System Option Form, the ASI Host Name has to be the server computers name. * Only the server computer will have the database service configured on it. The clients will hook up to the database on the server computer through the Sybase service, through the network. * 3M recommends at least a 2M bps connection between the two computers. You can accomplish this connection using a switch or a HUB. The networking connection in between the server computer and the client requires the full 2M bps connection that 3M specifies for full capabilities of a ScanNet server/client setup. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 181 SCPMKILL - manually shutting down ScanNet In the past when you were not able to shut down ScanNet normally, you had to manually shut down the ScanNet processes in this order: 1. cmddisp.exe 2. db_serv.exe 3. dbeng6.exe 4. dm.exe 5. evnt_srv.exe 6. messdisp.exe 7. monitor.exe 8. monserve.exe 9. scannt.exe 10 scan_dc.exe 11. scpm.exe 12. msglog.exe Now you can accomplish the same task by following one simple step. 1. Go to your Start menu, and select run, and after open: type "scpmkill" and click on run. You can do this more than once if you feel that the program is not responding fast enough. You will see the message: "Core has stopped running. close ScanNet and restart..." click ok, and close ScanNet. If you have a service, don't forget to start it before you start ScanNet. ScanNet Multi-level Security Reset Program Multi Level Security (MLS) for ScanNet allows the system administrator to assign permissions to users so that certain users will be allowed to use specific applications such as pulling reports. If somehow the administrator password is changed and forgotten, there is a program available that will restore the default administrator user name (administrator) and administrator password (fapd). You may obtain this program by calling Product Support at 877-777-3571 where you will also receive a password good for one day only. If you intend to run this program on another day, you will have to contact the Product Support Group at 877-777-3571 and ask for the MLS reset program password for the day. There are two default groups, administrators and supervisors. Administrators have all permissions to all applications and may create new security groups and new users. Supervisors are only allowed to create and assign users to groups to which they are assigned to themselves. Using SQL Statements to Delete Data in ScanNet In the past, some ScanNet users may have used SQL statements in Sybase Central to manipulate data in order to work around issues for their specific site. Over time, 3M has eliminated the need for this type of data manipulation by enhancing ScanNet so intervening at an SQL level is no longer necessary. We would like to inform you that some SQL statements that may have been ideal to run in the past are no longer recommended, because they can create database corruption. In ScanNet, there are many 182 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual intervening database tables, and if you delete data from a particular table, you can create “orphaned” data that can no longer be accessed. An example of this is deleting a credential in the credential table, and leaving patron data in the patron table. Now you have patron data in your database that no longer has a credential related to it because you deleted the data you needed in order to gain access to that data. In order to use ScanNet correctly, delete the credential information from the Access Control System, and the Access Control System will do all the work involved in the database to make sure no “orphaned” data remains. ScanNet 5.1.2.11G The following issues have been resolved with this release of ScanNet: * The bak_scan database now reflects all of the configuration tables in the current sa_scan database. * The Database Archiver now runs error free and no longer aborts during a purge. * The Custom Reports button is now accessible on the ScanNet Database Reports window. * The Billing Summary Report now displays the correct information. * The Aged Receivables Report, generated from the Billing and Invoicing window, now displays the correct information. IMPORTANT! When running the Database Archiver manually, be sure to take the focus off of the ScanNet Database Archiver window by clicking on the desktop. DO NOT press the spacebar or the Enter key to refresh the screen; doing so will start the archive process over again. CreateDsn.exe During ScanNet installation, you will see the ScanNet ODBC Setup Wizard which is the same as running the CreateDsn.exe program (ScanNet>Bin>CreateDsn.exe). You may access and run this executable file at any time to configure your ODBC entries and ScanNet databases as a stand alone, or as a client/server. 1. In the ScanNet folder, find and double-click on CreateDsn.exe, (ScanNet>Bin>CreateDsn.exe) 2. In the ScanNet ODBC Setup Wizard - Start window, click the Next button. 3. In the ScanNet ODBC Setup Wizard - Current Configuration window, choose Keep Existing Configuration (program will exit) and choose Finish, or Create New Configuration and click the Next button. 4. In the ScanNet ODBC Setup Wizard - Create New Server window, select which database server you wish to create: Stand Alone Database (single machine), Client/Server Database (multiple machines), or No Change (program will exit) and then click the Next button. 5. If you choose Stand Alone Database, in the ScanNet ODBC Setup Wizard - Database File Setup window, specify the location of your databases, and then click the Next button. It will return all the parameters you have chosen, and when you choose finish, it will complete programming. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 183 6. If you choose Client/Server Database, in the ScanNet ODBC Setup Wizard Client/Server Database Service Setup window, choose Create New Database Service on Current Computer or Use Existing Database Service (on this computer or remote computer), and then click the Next button. 7. If you choose Create New Database Service on Current Computer, in the ScanNet ODBC Setup Wizard - Database File Setup window, specify the location of your databases, and then click the Next button. In the ScanNet ODBC Setup Wizard - New Definition window, name the service and then click the Next button. It will return all the parameters you have chosen, and when you choose Finish, it will complete programming. 8. If you choose Use Existing Database Service, in the ScanNet ODBC Setup Wizard Existing or Remote Server Definition window, enter the name of the existing service and then click the Next button. It will return all the parameters you have chosen, and when you choose Finish, it will complete programming. Importing Data to Microsoft Excel 2000 You can import ScanNet data into Microsoft Excel in order to work with data in Excel spreadsheets. Note: To do this, you must set up the ODBC DSN. 1. In Excel, click New Database Query (Data>Get External Data> New Database Query). 2. In the Choose Data Source window, click the Databases tab, and then select the ScanNet database you want to pull the report from (sa_scan or bak_scan) and click the OK button. 3. In the Query Wizard - Choose Columns window, go to the Available tables and columns list box. Highlight each table and column you want to include, and click the right arrow button to move the item to the Columns in your query list box. Then click the Next button. 4. In the Query Wizard - Filter Data window, select the columns you want to include in the Column to filter box, and then click the Next button. 5. In the Query Wizard - Sort Order window, specify how you want to sort your data in the Sort by drop-down menu, and then click the Next button. 6. In the Query Wizard - Finish window, click Return Data to Microsoft Excel, and then click the Finish button. 7. In the Returning External Data to Microsoft Excel window, select Existing Worksheet, and make sure that the data will begin in the box =$A$1 (the default cell) and click the OK button. Posting Reader Programming for ScanNet 5 ScanNet ValuePass Posting Readers are used with ScanNet ValuePass cards, to create cards, add value to cards, and refund value from cards. A key switch on the reader is used to indicate whether values are being created, added to, or refunded. 02/07/2003 Current Posting Reader (Host only) Version A1.2.5 Before you begin: Know the device and port controller number of the posting reader Know that you should never bill ValuePasses 184 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Know the range of IDs being used for host-based credentials – Central and ValuePass. These must be different than any standard credential being used. You are limited to two ranges. Have the CAMP program running You must use the Basic Setup program in ScanNet 5.0 Access Control System>Access maintenance. Program the reader type Program reader setup Program account setup (Optional) ScanNet 5.0 will display the name of the account as well as the account number. Program Add fixed Value (Optional) Program Access Configuration Program Package Setup. You use this to associate a fee to the ValuePass. You must use Type = ValuePass. Fee (extra fees on top of Fee Types): Monthly Fixed – A flat fee charged monthly. This will populate the paid-through date option in billing. Unpaired Fee Amount – A flat fee that will be charged when the card is used twice in a row (or more) at an entrance or twice in a row (or more) at an exit. This is otherwise known as passback. Fee Types (the normal fee for the credential or ValuePass) None – no normal fee Flat Rate – A flat (fixed) fee is charged to the card for each trip (one entrance and one exit) through the garage. Variable Rate – A PowerPad fee table is used to calculate what the fee will be based on the duration of time spent inside of the garage. Program Use Central Credit Card Processing>Check ValuePass Auto Recharge in order to automatically recharge the ValuePass when the trigger amount is reached. (Optional) This automatically charges the credit card kept on record in the Credentials>ValuePass Tab. The patron decides what the flat charge amount will be when the credit card is automatically charged. You must have the Central Credit Card Option. Passport Plus Programming: Choose Programming>Passport Plus>Central Access ValuePass Configuration. Program the range of IDs being used for host-based credentials – Central and ValuePass. These must be different than any standard credential being used. You are limited to two ranges. Choose Reader Type = Posting and send to posting reader only Pick Entry/Exit and send to host based readers Posting Reader Programming: Choose System>Access Control System>Posting Reader Programming. Choose Programming>Create Posting Reader Programming (See Charge Method below) Click on the Save button to apply Posting Reader Create Programming to posting reader. Choose Load to view programming from the posting reader. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 185 Save and Load Posting Reader functions are saved in the database and assigned to particular reader(s). Click on Programming>Addon/Refund Posting Reader Programming (See Charge Method below) Click on the Save button to apply Posting Reader Create Programming to posting reader. Choose Load to view programming from the posting reader. Save and Load Posting Reader functions are saved in the database and assigned to particular reader(s). Charge method: Uses: number of trips (one entrance and one exit) that the credential may use. Looks at the start date and time Looks at the end date and time Reader will display the uses balance Dollar – (DOL): decrements a dollar value from the ValuePass. You must have a fee code assigned to the package. Looks at the start date and time Looks at the end date and time Reader will display the dollar balance Duration – (DUR): will let a patron in and out of the facility based on total amount of time allotted to stay in the lot. Looks at the start date and time Looks at the end date and time Calculates total time spent in the parking lot based on time in and time out, and subtracts total time spent in the lot from total amount of time allotted to stay in the lot. Time: will let a patron in and out of the facility based on start and end date and time. Looks at the start date and time Looks at the end date and time This can be Fixed or Offset Fixed is the date and time on that date the card will expire on Offset is the number of days from the current computer date and hours from 00:00 on that date. (For start and expire) Example: Offset expire days 1 Offset expire hours 11 If the computer date is 9/25/00 when the card is created then it will expire on 9/26/00 at 11:00 AM. Add-on “offset” will add days and set time to expire date of the ValuePass. If the patron enters the lot in between the start and end date and time, they will be allowed access. You should always have an end date assigned to these type of cards Coming soon: Max uses per day Max days use Days after first use Group control 186 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Using ScanNet ScanUpdate.exe You can upgrade the ScanNet database while you are upgrading ScanNet, or you an upgrade the ScanNet database manually by running the ScanUpdate.exe program (ScanNet>Bin>ScanUpdate.exe). During ScanNet installation, you will see the ScanUpdate window with the message “This program will update the database from Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 187 ScanNet 4.6.3 (Release) or later to version X.X.X.X. Do you wish to continue?” X.X.X.X is the version of ScanNet you currently have on the computer. You may access and run this executable file for the following reasons: * After installation you realize that the database service was not running. * ScanUpdate.exe could not connect to the database. * To test an earlier ScanNet database for your customer without downgrading your ScanNet. * An inexperienced technician has not upgraded the database, and has only upgraded the ScanNet version. To run the ScanUpdate.exe program manually, follow these directions: Note: ScanUpdate.exe will only update databases that have an ODBC DSN with the word “scan” in them to the current ScanNet build. 1. In the ScanNet folder, find and double-click on ScanUpdate.exe, (ScanNet>Bin>ScanUpdate.exe). 2. In the ScanUpdate window, click the Yes button to upgrade, or click the No button to exit. 3. ScanUpdate will automatically connect and upgrade the databases that have the word “scan” in the ODBC DSN. 4. When ScanUpdate.exe finishes, the ScanUpdate window will display the message “Done.” Click the Close button to exit. * Note: When installing ScanNet, you do not need to stop the installation and run ScanUpdate.exe manually. If you encounter a problem in upgrading the database, continue the ScanNet upgrade process, and run ScanUpdate.exe manually afterwards. * Note: Do not confuse ScanUpdate.exe with ScanUpgrade.exe. Automatically Bill and Print using Billing and Invoicing You can accomplish this through the Event Control System in ScanNet 5. At the ScanNet Main Navigator, click Systems>Event Control System>View>Action Definitions>Add a new action definition, name it “Bill and Print”>Add Step. To build the event, choose System Function>Billing and Invoicing (all accounts will automatically be defaulted once you select Billing and Invoicing)>and then choose Print Credential Usage (most detailed on all credentials), Print Account Summary (summary of accounts only), or Print Credential Summary (summary of each credential). Once you have the action defined, click Apply and create a time to run this action once a month. Once you have the time, you can map the action to the event, and the system will automatically bill once a month. Running ScanNet on Microsoft Windows XP When running ScanNet on Microsoft Windows XP, you should use the Windows Classic Scheme in the Display Properties, Appearance tab in order for the windows in ScanNet to align properly and open to the right size. Navigator Showing Only a Blue Bar If you are experiencing this problem, 3M has developed a program that you can run that will restore your ScanNet Navigator Bar to its original size. Call Product Support at 877- 188 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual 777-3571 and specify if you are using Windows XP, 2000, or NT. Saving PowerPad Programming Files Saving PowerPad program files when using ScanNet is always recommended for facilities with PowerPads. However, sending earlier PowerPad program files after upgrading ScanNet or the PowerPad may cause some missing programming at the PowerPad. There are programming options in current ScanNet and PowerPad builds that did not exist in the past, and the result of sending that earlier program file with a new ScanNet build and/or to a later PowerPad can cause strange fields in some of the programming options. If you are experiencing problems with your PowerPad, make sure you do not have an invalid programming entry in the programming area you are experiencing a problem with (you can do this by toggling your Date/No key on the PowerPad to see what options you have). Once you have located an invalid programming entry, change the programming option, pull the programming back to ScanNet from the PowerPad, and resave your programming file. Generate an Invoice for No Activity You can generate an invoice for no activity in the Billing and Invoicing Facility Information window. The first time you open the Billing and Invoicing window, the Facility Information window opens. In this window, there is a “Generate invoice even if no account activity for the selected billing period” field. If you want to see an invoice for $0.00 with no activity, click the checkbox so that a check mark appears. You can also get to the Facility Information window by opening the Billing and Invoicing window and choosing File>Facility Info. ScanNet 5.1.1.5G *Microsoft Internet Explorer 6.0 is a requirement for ScanNet 5.1.X builds. New features in this release: *An enhancement was made to the Group Counts Monitor that allows you to view the credentials for each group within a facility (select the group and then click the Details button). The credential information includes the credential ID, patron’s first and last name, in/out status, last time the credential was used at a reader, facility code, and physical ID. Note that if the credential has more than one patron associated with it, the credential’s information will be listed once for each patron associated with it. *The Sign Control Application has been reprogrammed and no longer consumes unlimited system resources, which caused the system to lock up during busy times. The Sign Controller window now allows for two print options: Regular Print or Word Print. *Support was added for continuous fee processing for repay fees. If the patron pays but does not exit until a later time, when the patron does exit and pays for the additional time, the additional amount is calculated from where the original fee left off and not from the beginning of the fee table. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 189 *An Ignore Default button was added to the Credentials window, allowing you to bypass default information when setting up credentials. *The LPI System has been enhanced to allow you to insert, update, and delete records in the LPI current inventory. Inventory totals now appear when viewing the LPI inventory and search results. Also, you can now filter by lot when viewing the LPI inventory. *The online devices in the Device Activity Monitor and the System Activity Monitor now appear dark green. All of the device trees in Device Control are now sorted in ascending order (when editing devices, sending and getting programming, and sending commands). *The ScanNet Database Reports window now displays only the most common reports. To display additional reports in the list, select Configuration>Configure Report List and move the reports you want to list to the Reports Displayed box. *Support was added for the Passport 360 Card Reader. *A “G” was added to the end of the version number for ScanNet to indicate a general release. The following are prior issues that are resolved in this release: *When adding the Action Steps “Run File” or “Run File and Wait” in the Event Control System, you are prompted to select a program file, and only .pgm files are listed in the Select Program File window. If you need to select another file type, such as an .exe file, to list these in the Select Program File window, select “All files” in the “Files of type” drop-down list box. *In the LPI system, in the current LPI inventory, an error may occur if the license plate field is empty. You can now manually delete the LPI record and print the current database. *The ValueCard Exception Report now shows only ValueCard patron information if the Access Control System (ACS) has a ValueCard database. *The “from” and “to” amounts in the PowerPad Programming Statistics Revenue Report now appear correctly. *The Transaction Summary Report now shows ticket and lane numbers for voided transactions. *When using Global Payments dialup in the Central Credit Card System, floor limit transactions declined because of “no phone line” are now saved correctly in the decline list. *The Transaction Summary Report now shows ticket and lane numbers for voided transactions. *When using Credit Card In/Credit Card Out, cards that exit within the grace period no longer remain on the issued stack. *In the Credentials window, the Account, Facility, Group, and Package drop-down lists are now sorted alphabetically. Type the first letter of the information that you wish to access to position the list. *When selecting a Group ID in the parameter field of the Credential ID Report, a dll error is no longer generated. *ValueCards have been removed from the Access Control System In/Out Report since their access is not tracked like other credentials. ValueCards are in the ACS only for a patron database. *The operator ID and date/time are now set in the Credential Log Report when any 190 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual credential, patron, or vehicle information is modified. *In the Credentials window, a duplicate license plate number and/or patron name is now detected and prevents the credential from being saved. *The PowerPad Statistics Reports now show graphs. *In the Credentials window, messages for false validation errors no longer display. *Physical ID can now be used as search criteria in the Find field in the Credential Explorer. *The message “If you have purchased this option please run Basic Setup” has been removed from the ACS. *Saved queries in the Credential Explorer can now be deleted, and duplicates will no longer appear in the list. *Only one session of CAMP can now run. *ValueCard Access Reports now show only ValueCard type patrons. *Tickets exiting within the unpaid grace time are now moved from the Issued stack to the Validated stack when exiting through a PowerPad-based exit device. Tickets paid at an APS or central PowerPad are now moved from the Paid stack to the Validated stack when exiting through a PowerPad-based exit device (Exit Cashier Booth and Credit Card Exit Verifier). *The Central Credit Manager now has a programmable option to close a batch based on the transaction amount. *The Group ID in the ACS has been modified to accept alphanumeric values. *CAMP now properly charges a flat rate to ValuePass cards using Free In/Pay at Exit. *CAMP no longer stops responding when a Central Access Card is used for the first time at an exit device. *The ValuePass Balance and the Create/Addon Reports have been reformatted. *Central Credit Reports are now sorted by transaction date and time as well as the existing sort criteria. *Light migrating the database no longer causes Multilevel Security failure. *Credentials with the Days Use constraint set can now be reopened without error. *The ACS now loads correctly if you check the menu Start Up with Credential Form. *The Restore process no longer causes errors for MLS objects. When restoring to an empty sa_scan, the Multilevel Security will default to user name: “administrator”/password “fapd”. *Adding the first credential to an empty database is now handled correctly. ScanNet 5.0 ScanNet version 5.0 has a new Access Control System, log reporting capabilities, new database reports, and user-friendly interface. The new features in this version of ScanNet also include complete billing capabilities, and many other features detailed below. New Features in ScanNet 5.0: Administrative Log * Allows the user to view logged information about security and event activity including the following: * Logs which users logged on and off and when. * Logs which ScanNet applications were accessed by each user. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 191 * Logs which users attempted to access applications they do not have the security permissions to access. * Logs events that have taken place in ScanNet including programming sent to a device, printing of a report, or editing a credential. Group Counts Monitor * Allows the user to view real time group usage, including current count, group limit, and the last access time. * Allows the ability to update group counts and limits and reset all group counts to zero from the Group Counts Monitor window. Group over limits appear in red type. Access Control System * All new menus and windows. * The Access Control System security is included in ScanNet Security. Credential Explorer * In the Access Control System, Credential Explorer allows the user to make queries on credential data and make changes to selected credentials. Queries can be saved for future use. * Allows the user to resync the passback status for any credential type, add and refund ValuePass value, change credential validities, and much more. Basic Setup * In the Access Control System, Basic Setup is a setup program that allows the user to configure the ACS to meet the needs of the facility. The Basic Setup user must know what is necessary for the facility before configuring all components for the ACS. * Certain components available for ScanNet will not be visible unless they are valid for the site’s registration number. The registration number can be updated and changed at any time. The first time the user enters the ACS, Basic Setup MUST be run at least once to ensure proper operation of the ACS. * Basic Setup can be run again at any time. New ValuePass Features * Days After First Use * Days Used * Max Days Use * Auto Recharge (Requires the ScanNet Central Credit Card System.) * Auto Delete of Expired ValuePasses (Requires an end date constraint, “Delete Expired ValuePasses” checked in Basic Setup, and an Event Control action set up to run daily.) Billing and Invoicing * All new menus and windows. * Billing can be done using any or all of the following: * Variable rate * Flat rate * Late fee * Unpaired fee * With or without tax applied * Payments may be applied to multiple invoices. Automatic Billing * Requires an Event Control action to run monthly and you must bill all accounts. Automatic Credit Card Billing 192 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual * Requires the ScanNet Central Credit Card System. Delinquent Status Valid/Void Option * In Basic Setup, you may determine if a credential’s status is valid or void when it is Delinquent. Installing ScanNet 5.0 for the First Time If you are installing a new site, and/or starting with a blank database, you only have to follow the steps under the headings “Installing ScanNet 5.0” and “Setting up ScanNet 5.0 for the First Time”. Skip all other steps referring to upgrading or the Database Validator program if you are working with a fresh install. Complete instructions for installing ScanNet 5.0 for the first time can be found in the ScanNet 5.0 manual. Upgrading to ScanNet 5.0 from Version 4.6.3.6 or Later When updating a database from an earlier version of ScanNet, you must follow all instructions in this Field Service Tips newsletter. 3M has developed the Database Validator program to check if your existing database from ScanNet version 4.6.3.6 or later is compatible to be upgraded to the ScanNet version 5.0. Because there have been many major changes to the structure of ScanNet, it is absolutely necessary to run the ScanNet Database Validator program to confirm that the existing data in the current database is compatible with ScanNet version 5.0. If there are incompatible fields in the database, the Database Validator program will find these fields and create an html document reporting all of these errors. The Database Validator is only an investigation and reporting tool, and it will not alter data in your ScanNet database. Before Upgrading to Version 5.0, Make Sure of the Following * Your current ScanNet version must be 4.6.3.6 or later. * Your current Sybase version must be 6.0.4. * Your Microsoft Internet Explorer version must be 5.5 or later. * The existing database must be copied and saved to a safe location. * If you have standard credentials with a 0 facility code, standard credentials must be changed to a non-zero number. Verify which standard credentials are set to the zero facility code. Find out what facility code is on the cards and enter that number in the Facility Set Up Form if necessary. In the Change Facility Codes Form select the ID range for the standard cards (make sure that the range is standard type only) and change the Old Facility Code from zero to the New Facility Code number that is determined by what the Facility Code is on the cards. These forms are located in ScanNet version 4.6.3.6 under Systems>Access Control Systems>Credential Maintenance>System Maintenance. Installing the Database Validator Program 1. Save a copy of your existing database to a safe location. It is important to save a copy of your database to use as a safety net if unexpected errors occur during the installation that cause irreparable damage to your database. 2. Find the V5.0.0.33 folder on the ScanNet version 5.0 CD and double-click it. 3. Install the Database Validator from the CD, as follows: a. Double-click Install.bat and follow the directions to install. You must use Install.bat because this runs several executable programs that need to be installed. If you try to install using setup.exe, then you only install one part of the necessary installation. Running the Database Validator Program 4. Run the Validator as follows: (ScanNet can be running) a. Click on Start>Programs>Federal APD>Database Validator to run the Database Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 193 Validator program. You can also run the Database Validator program by double-clicking on DBValidator.exe in C:\CheckDatabase. b. Once you run the program, it will generate a report that will list any discrepancies in the database. The Save As button in the Validator window will no longer be grayed out. Choose Save As to save the html document in the folder C:\CheckDatabase. c. In order to prevent overwriting any previously saved Validator reports in html format, change the name of the report to a unique name. (e.g., 2002_10_26.html, or YearMonthDay.html) d. If you choose to print the report, print it in landscape mode. e. Database Validator Report On the last page of the report, you will see a summary of all Fatal Errors, Notices, and Information from the existing database. If there are any Fatal Errors, you will need to either change the data in ScanNet so that it is compatible with version 5.0, or command SQL statements in Sybase to either delete or change the incompatible data to compatible data. If you are uncomfortable with working with database manipulation, it may be in your best interest to send a copy of your site’s sa_scan database to 3M for evaluation. Depending on the amount of work that needs to be done to your database, there may be a fee involved with this course of action. f. If you have Fatal Errors that you do not know how to fix, call Product Support at 877-777-3571 with the Validator report. NOTE: Verify that the Validator version you are using matches to version of ScanNet you are updating to. To do this, look at the Database Report that the Validator program saves and the version will be displayed in the top box called Database Version next to Target. The latest Validator program is included with each version of ScanNet. To uninstall Validator go to Start>Settings>Control Panel>Add/Remove Programs and remove the program Validator. To reinstall Validator, follow the steps in 2 and 3 as described above. 5. Resolve all Fatal Errors listed in the Validator report. 6. After resolving all Fatal Errors run the Database Validator program again to insure that no Fatal Errors are reported. * Do not install ScanNet 5.0.0.x until all Fatal Errors have been resolved. * Notices and Information messages can be ignored. Installing ScanNet 5.0 Install ScanNet version 5.0.0.x. There are complete instructions for this in the Installation Instructions. * Carefully note the registration number constraints, as shown in Example 1. * NOTE: Cancel the installation if a new registration number is needed. Contact Customer Service at 3M to verify the options for your serial number. If you do not have permission for the options you desire, a new registration number is required. Contact Customer Service, your 3M sales representative, or your distributor to order a new registration number. Registration numbers cannot be given over the phone. * Document any errors you encounter when installing ScanNet 5.0. The easiest way to do this is to take screen shots of the errors and paste them in a Microsoft Word document. Running the Validator Program After Installing ScanNet 5.0 7. Run the Validator again after installing ScanNet 5.0 and save the report as described in step 4c on page 3. 194 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual 8. There should be no Fatal Errors or Notices in the Validator Report. If you encounter any Fatal Errors or Notices, follow the directions as described in steps 4e and 4f on page 3. 9. When the Database Validator program runs without error, start the ScanNet core. Setting Up ScanNet 5.0 for the First Time 1. From the ScanNet Main Navigator, select Systems>Access Control System>Access Maintenance. Then, in the Access Control System window, click the Basic Setup button on left side of window. 2. Carefully go through each window, and make all the selections that apply to your system. Note the following: * Reader Setup now requires you to apply read head information. * The Access Packages window contains all fee information with new features that are listed in the beginning of this newsletter under “New Features in ScanNet 5.0.” * In the Access Packages window, you must select a type when setting up an access package. For each access package, use the Type drop-down list box to select one of the following types: * Central Access Monthly * ValuePass * Standard. * When Billing and Invoicing is purchased, you must set up at least one account in the Access Control System. A warning will be displayed and you must use the Credential Explorer after updating to 5.0 to select credentials and add accounts to them. Otherwise, you have to uncheck the “Use Billing” option in the Basic Setup program. * If the site is experiencing any problem that cannot be resolved normally, it is imperative that an experienced technician can visit the site and document exactly what the issue is. Call Product Support at 3M while at the site to determine how to solve the issue. The customer/ technician should be trained to capture screen shots of all errors and be able to provide a detailed description of the problem. CAMP Shuts Down when Central Only Cards are Used for the First Time at an Exit Reader in ScanNet 5.0.0.33 Central only cards used for the first time at an exit causes CAMP to shut down in ScanNet version 5.0.0.33. This only happens with central only card types, and does not happen with standard or ValuePass cards. If a central only card is used the first time at an exit, you will get the following error: Run time error Integrity constraint violation: column ‘change_type’ in table_acs_valuepass_log’ cannot be null. In order to prevent this error from occurring, you must use the newly created central only card the first time at an entry reader. Afterwards, you can use the card normally. In order to work around the problem, you may let your patrons out of the lot using the transient ticket that they originally came in with after validating the ticket. Explain to the customer that they must use the ticket to exit the lot the first day, and then use the central only card normally afterwards. If you choose to fix the problem rather than work around the problem, 3M has an SQL Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 195 statement that will resolve this issue for 5.0.0.33 and the problem will be fixed in the 5.1 release of ScanNet. If you are experiencing this problem and are familiar with SQL statements, call Product Support at 877-777-3571 and request the SQL statement. If you are not experiencing this problem, do not request this statement. If you are unfamiliar with SQL statement execution, we do not recommend you try this course of action, and encourage you to perform the work-around until the 5.1 release of ScanNet is available. 3M is not responsible for database corruption caused by an inexperienced technician. ScanNet 4.6.6.8 New feature with this release: * Support was added for the Passport 360 Card Reader. The following are prior issues that have been resolved in this release: * The date field is no longer truncated in ValuePass reports. * When adding a report, you may now specify a parameter file. This allows third party developers to supply parameter windows. Other enhancements to parameter files for developers include: multiple line specifications for select, from, and where clauses of the view definition; addition of the “group by” clause; ability to specify a generic sql statement to be run before building a view; ability to specify a view other than the first one to send to the Crystal control; ability to not supply all parameters automatically to all views. * Formatting issues were corrected on the ValuePass Usage Report. * When a credit card is used for entry, table_LPR now handles it correctly. * The Account Summary Report now reports all accounts correctly and is formatted correctly. * In the PowerPad programming>Statistics>Revenue Report, the to and from amounts are now setting properly when ending with cents. * The Transaction Summary Report now shows ticket and lane numbers for voided transactions. * Balances are now displaying correctly in the Miscellaneous Invoice window. * When using Global Payments dialup in the Central Credit Card System, floor limit transactions declined because of “no phone line,” floor limit transactions are now saved correctly in the decline list. * The Transaction Summary Report is now formatted correctly. Internet Explorer Requirements For ScanNet ScanNet version 5.1 requires Internet Explorer version 6.0. Internet Explorer 6.0 is included with your ScanNet installation disk. Prior versions of ScanNet requires Internet Explorer 5.5 or later. IE version 5.5 was included on the ScanNet CD so you could install it easily if you do not have the most recent version. Some systems may have difficulty installing IE 5.5, especially if they have an existing ScanNet installation on the system, and have never updated Internet Explorer. When starting the IE 5.5 setup, a typical error message may be: “Setup was unable to install all of the components. Please close all applications and try running setup again.” 196 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Restarting the system will not help, as the install never gets past this point. In this situation, the following steps may resolve the problem: 1. Go to the C:\WINNT\SYSTEM32 directory (presuming Windows NT was installed on the C drive). Find and rename the following dll files: a. Rename wintrust.dll to wintrust.old b. Rename wininet.dll to wininet.old c. Rename urlmon.dll to urlmon.old 2. Restart the system. 3. When the system comes back up, run IE 5.5 setup. This should properly install now. 4. After the installation is finished, restart the system if it doesn’t automatically restart. 5. Reapply Windows NT Service Pack 6a, and then restart the system again. 6. Install ScanNet 4.5 following the normal installation procedure. ScanNet Serial Numbers When installing or updating ScanNet to version 4.3.x.x or later, you must enter the correct, original registration number that was supplied with the software when purchased. This number can be found on the back of the customer’s ScanNet CD case. If you do not use the correct registration number, the customer will not have the licenses for the number of devices and/or consoles that were purchased. As a result, ScanNet will only allow a very limited number of functions to be performed, and for all practical purposes the system will be inoperable. The registration number on NFR versions of ScanNet will not give the proper licensing for a customer’s system. It is critical that you make sure that you have the correct registration number before you begin installing ScanNet. If you discover that you have entered the incorrect registration number, you can correct this without reinstalling ScanNet. From the menu bar on the ScanNet Main Navigator bar, select File>Options, choose the Registration tab. Enter the correct registration number. You must then restart the ScanNet Core. If you cannot locate the customer's correct registration number, you can obtain this number from 3M. You must mail or fax your request to your Customer Service Representative with the following information: 1. Distributor Name 2. Project Name 3. Sales Order Number 4. Requestor’s Name 5. Requestor’s Phone Number 6. Requestor’s Signature We will then mail the requested customer’s registration number to the distributor’s address of record. We cannot give out registration numbers over the telephone. ScanNet Database Archiver As the size of your facilities database increases, you may experience a slow down of ScanNet’s performance. In order to keep ScanNet running at an optimal level, you will need to maintain your databases by archiving your sa_scan (current database) to your bak_scan (backup database). In the ScanNet Main Navigator bar, click on Utilities>Database Archiver, and set up how Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 197 often you are going to copy the data from sa_scan to bak_scan, and delete old data from sa_scan based on the Purge After time. If you have your Purge After time set to 90 days, anything from the past 90 days will remain in sa_scan, and anything 91 days old or older will be deleted from sa_scan. This data will no longer be in sa_scan, but this data will still be kept in bak_scan. You need to keep this information in bak_scan in order to pull reports related to older data. By clicking Schedule, you can program how often the database archiver is run. If you have the Start at time set to 3:00 AM, it will run every day that is checked at 3:00 AM. It is a good idea to have this run every day, because it will not take as long to finish. If you wait two days, ScanNet will have two days worth of information to process, and it will take twice as long. If you wait a month, then it is about 30 days of information to process, so you may have to wait 30 times as long for the ScanNet Database Archiver to run. If the Database Archiver was never set to backup or purge, the end result will be a very large sa_scan and an empty bak_scan, as shown in example 1 of the Database Archiver Example. If the Database Archiver was set to backup but not to purge, the end result will be a very large sa_scan and a very large bak_scan as shown in example 2 of the Database Archiver Example. If the Database Archiver was set to backup and purge after 90 days, the end result will be a smaller sa_scan and a very large bak_scan. Anything older than 90 days will be deleted from sa_scan, but still be kept in bak_scan as shown in example 3 of the Database Archiver Example. The best way to archive information is to split the bak_scan into quarters. If the Database Archiver was set to backup and purge after 90 days, with the bak_scan being saved off after the quarter had ended, you can continue to control the size of your bak_scan database. The end result will be a smaller sa_scan and a smaller bak_scan. Anything older than 90 days will be deleted from sa_scan, but still be kept in bak_scan as shown in example 4 of the Database Archiver Example. Example 1 *Note that 4.24 MB is the size of a database with no data in it. Database never set to backup or purge Example 2 198 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Database set to backup but not to purge Example 3 Database set to backup and purge after 90 days Example 4 Database set to backup and purge after 90 days, with the bak_scan being saved off after the quarter had ended. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 199 Example One This is how the ScanNet tree looks like in this example. Create a folder in the DB folder called archived_data, and in that folder, create a folder for each individual database. The names of the folders cannot have any spaces if you plan to connect and record data to them. The DB folder in this example contains the live sa_scan database and the live bak_scan database that is still recording data from the facility. Once you save off the database and set up the System DSN in order to pull reports, you will no longer be recording data into the database. The folder containing the archived bak_scan database should be named so that you can identify the database. Once you save off the database, you will no longer be able to record new data to the database, unless you redirect the path to the database in the bak_scan System DSN (or if you have a Service, in the Sybase Central ScanNet Server). 200 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual The folder containing the archived sa_scan database should be named so that you can identify the database. Once you save off the database, you will no longer be able to record new data to the database, unless you redirect the path to the database in the sa_scan System DSN (or if you have a Service, in the Sybase Central ScanNet Server). Feb_2003_bak_scan The following screen shots show how you are supposed to set up the System DSN for an archived bak_scan. Choose the Troubleshooting Manual button 78-0060-4094-9, Ver. 1 ScanNet • 201 Adaptive Server Anywhere should already be highlighted, so choose Finish. 202 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Name the Data Source name the same name as the folder that the archived database is going to be kept in so that you can identify which database you are going to be pulling information from. The user ID is still scan and the password is scan. The server name should be the same name as the folder that the database is contained in with “_server” added to the end of the name. The database name = bak_scan The database file = C:\Scan_NT\DB\archived_data\Feb_2003_bak_scan\bak_scan.db Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 203 TCP/IP should not be checked. The advanced tab should be set like the example. Feb_2003_sa_scan The following screen shots show how you are supposed to set up the System DSN for an archived sa_scan. 204 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Choose the button Adaptive Server Anywhere should already be highlighted, so choose Finish. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 205 Name the Data Source name the same name as the folder that the archived database is going to be kept in so that you can identify which database you are going to be pulling information from. The user ID is still scan and the password is scan. 206 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual The server name should be the same name as the folder that the database is contained in with “_server” added to the end of the name. The database name = sa_scan The database file = C:\Scan_NT\DB\archived_data\Feb_2003_sa_scan\sa_scan.db TCP/IP should not be checked. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 207 The advanced tab should be set like the example. Sybase Central ScanNet Server The Parameters for executable should look like this. 208 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Example 2 In this example, we are currently in the first quarter of 2003 (1_QTR_2003_bak_scan) The DB folder does not contain any bak_scan database. There is an archived_data folder in the DB folder that has 6 folders in it. The first four folders contain a blank bak_scan database and bak_scan log that has been copied from the SQL folder. When you first set up your system, these bak_scan databases will be identical. The last two folders are sa_scan databases that have been split from year 2002. The fifth folder contains an sa_scan with data ranging from January 2002 through June 2002, and the sixth folder contains an sa_scan with data ranging from July 2002 through December 2002. In this example, we can tell that this particular site did not archive their data in the year 2002 from sa_scan, so the database had to be split. These two folders are set up in the archived_data folder so that a System DSN can be created and a database report can be pulled from ScanNet from a previous year. In this example, this is the live bak_scan database that the live sa_scan is backing up to. At the end of March 2003, the user is going to manually change the System DSN in order to stop copying data to the first quarter of 2003 (1_QTR_2003_bak_scan), and start copying data to the second quarter of 2003 (2_QTR_2003_bak_scan). At that time, 2_QTR_2003_bak_scan will be the live bak_scan database that the live sa_scan is backing up to. 1_QTR_2003_bak_scan will contain data from January 2003 through March 2003. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 209 In this example, this is a future bak_scan with no data in it. At the end of June 2003, the user is going to manually change the System DSN in order to stop copying data to the second quarter of 2003 (2_QTR_2003_bak_scan), and start copying data to the third quarter of 2003 (3_QTR_2003_bak_scan). At that time, 3_QTR_2003_bak_scan will be the live bak_scan database that the live sa_scan is backing up to. 2_QTR_2003_bak_scan will contain data from April 2003 through June 2003. In this example, this is a future bak_scan with no data in it. At the end of September 2003, the user is going to manually change the System DSN in order to stop copying data to the third quarter of 2003 (3_QTR_2003_bak_scan), and start copying data to the fourth quarter of 2003 (4_QTR_2003_bak_scan). At that time, 4_QTR_2003_bak_scan will be the live bak_scan database that the live sa_scan is backing up to. 3_QTR_2003_bak_scan will contain data from July 2003 through September 2003. In this example, this is a future bak_scan with no data in it. At the end of December 2003, the user is going to manually change the System DSN in order to stop copying data to the fourth quarter of 2003 (4_QTR_2003_bak_scan), and start copying data to the first quarter of 2004 (not shown). At that time, 1_QTR_2004_bak_scan (not shown) will be the live bak_scan database that the live sa_scan is backing up to. 1_QTR_2004_bak_scan will contain data from January 2004 through March 2004. 210 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual In this example, the database from the year 2002 was not maintained, so it had to be split. This database is from the first 6 months in 2002 (January through June). In order to pull data from the database, you will have to set up the sa_scan in the archived folder in a folder that will identify what time period the data in this database is from. You must create a System DSN that will point to this database when you pull a database report. The sa_scan archived database is used for database reports only. In this example, the database from the year 2002 was not maintained, so it had to be split. This database is from the last 6 months of 2002 (July through December). In order to pull data from the database, you will have to set up the sa_scan in the archived folder in a folder that will identify what time period the data in this database is from. You must create a System DSN that will point to this database when you pull a database report. The sa_scan archived database is used for database reports only. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 211 1_QTR_2003_bak_scan 1_QTR_2003_bak_scan is the current bak_scan database, so is has to be called bak_scan in the System DSN while it continues to be the current bak_scan. 212 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 213 In this example 1_QTR_2003_bak_scan is the current bak_scan database, so TCP/IP has to be checked. If it were a copied database, TCP/IP would not be checked. 214 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual 2_QTR_2003_bak_scan Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 215 216 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual C:\Scan_NT\DB\archived_data\2_QTR_2003_bak_scan\bak_scan.db In this example 2_QTR_2003_bak_scan is not the current bak_scan database, so TCP/IP cannot be checked. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 217 3_QTR_2003_bak_scan 218 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 219 C:\Scan_NT\DB\archived_data\3_QTR_2003_bak_scan\bak_scan.db In this example 3_QTR_2003_bak_scan is not the current bak_scan database, so TCP/IP cannot be checked. 220 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual 4_QTR_2003_bak_scan Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 221 222 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual C:\Scan_NT\DB\archived_data\4_QTR_2003_bak_scan\bak_scan.db In this example 4_QTR_2003_bak_scan is not the current bak_scan database, so TCP/IP cannot be checked. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 223 Jan_through_June_split_sa_scan 224 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 225 C:\Scan_NT\DB\archived_data\Jan02_thru_Jun02_split_sa_scan\sa_scan.db Network TCP/IP has to be unchecked. 226 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Jul_through_Dec_split_sa_scan Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 227 228 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual C:\Scan_NT\DB\archived_data\Jul02_thru_Dec02_split_sa_scan\sa_scan.db Network TCP/IP has to be unchecked. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 229 230 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Sybase Central ScanNet Server The Parameters for executable should look like this: -x tcpip -ti 0 -gp 4096 -n scan_db_service C:\Scan_NT\db\sa_scan.db -n sa_scan C:\Scan_NT\DB\archived_data\1_QTR_2003_bak_scan\bak_scan.db -n bak_scan Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 231 How To Change Targets For bak_scan at the End of March 2003 You will need to redirect the bak_scan database by completing the following 2 steps: • Change the System DSN to connect to 2_QTR_2003_bak_scan (it was previously directed to 1_QTR_2003_bak_scan) • Change 2_QTR_2003_bak_scan to 1_QTR_2003_bak_scan Change the bak_scan target to reflect the second quarter (2_QTR_2003_bak_scan). The only thing you have to change is the number from 1 to 2. The Parameters for executable should look like this: -x tcpip -ti 0 -gp 4096 -n scan_db_service C:\Scan_NT\db\sa_scan.db -n sa_scan C:\Scan_NT\DB\archived_data\2_QTR_2003_bak_scan\bak_scan.db -n bak_scan 232 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Double click on 2_QTR_2003_bak_scan to change it to 1_QTR_2003_bak_scan Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 233 Highlight the 2 and change it to 1. Click on the Database tab and change both of the 2s (shown highlighted in this example) to 1. 234 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Your System DSN should look like this. From the ScanNet main navigator bar, you can click on Reports>Database Reports Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 235 Choose Configuration>Report from Database Here you can choose which database you want to obtain a report from. 236 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual If you choose to report from a database other than sa_scan, the database name will appear in the bottom right of the report menu. Example 3 (You must change 3 windows at end of quarter) Target is 1_QTR_2003_bak_scan instead of just bak_scan Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 237 238 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 239 240 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual TCP/IP must be checked when this is the active bak_scan. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 241 242 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual -x tcpip -ti 0 -gp 4096 -n dennis_db_server C:\Scan_NT\db\sa_scan.db -n sa_scan C:\Scan_NT\db\archived_data\1_QTR_2003_bak_scan\bak_scan.db In this type of setup, when you need to change the target to Quarter 2, you have to change the targets for 1_QTR_2003_bak_scan and 2_QTR_2003_bak_scan in your System DSN, Your database archiver, and your Server Setting. Duration by Ticket and Grace Exit Reports The Duration by Ticket and Grace Exit reports were designed for use with Central Cashiering and the Pay Any Time feature. They report only on SST Exit Verifier devices and not PowerPads. They include in-grace exit information, which is not reported by PowerPads. Central Credit Card If you are using the Central Credit Card feature of ScanNet, you must make sure that you have it turned on. You do this by going to Configuration/ ScanNet Properties and checking the Central Credit Card box in the Program Startup and Shutdown section on the ScanNet tab. You also need to select the proper credit card processor in the Credit Card Manager under View/Options. (ScanNet must be restarted after making this selection.) You need to have a modem installed in your ScanNet computer, and the Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 243 software from your credit card processor must be installed and running. Central Credit Card is an optional ScanNet feature that can be purchased and used in place of the DataCap terminal that has been previously used at the Auditor PowerPad. Prevent Accidental Shutdown of Sybase/Hide SQL Icon When you set up ScanNet as a stand-alone, without configuring a service, the SQL icon in the System Tray will automatically be there, and the only way to get rid of it is to set it up as a service that does not interact with the desktop. When you create a service, under Choose Options, "Allow service to interact with the desktop" has to be checked if you want to see the SQL Icon in the System Tray. If this is not checked, you will not see the icon on the desktop. 3M suggests that you choose to not allow the service to interact with the desktop, because if someone opens the screen, and closes the screen using the Close (X) button located at the top right of the window, they will accidentally shut down the service. If the service is shut down, ScanNet has no way to connect to the database. Information will be lost. I deleted a standard credential from the Access Control System (ACS), but the reader still lets the patron into the lot. Why? If you delete a standard access card from the ACS, it is not made invalid at the readers. You need to first change the ID status to Invalid and save the credential. This will then be sent to the readers, and the card will no longer be valid at the readers. Once the credential is made invalid at the readers, it can then be deleted from the ACS. The exception is in ScanNet version 5.1, you can delete the credential without first changing the ID status to Invalid, and the ACS will update the reader so that the credential will be invalid at the reader. PC Requirements for ScanNet Hardware Requirements: Pentium 4, 2.2GHz or Higher 512K cache 256MB DDR SDRAM or Higher 40GB 7200rpm hard drive or better 20x min./48x max. CD-RW drive 56K PCI data/fax modem U.S. Robotics Sportster Two serial ports (COM1 & COM2) If you connect more than one port controller to the computer, you will need a multiport adapter. One unidirectional parallel port Sound Blaster sound card with speakers 32MB video card 244 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual PCI 10/100 Twisted Pair Ethernet 17 in color monitor (16.0 in v.i.s., .27dp) Keyboard and 2-Button Scroll Mouse Software Requirements: Operating System Microsoft Windows NT Workstation 4.0, Microsoft Windows NT Server 4.0, Microsoft Windows 2000 Professional, Microsoft Windows 2000 Server, Microsoft Windows 2003 Server or Microsoft Windows XP. Sybase Central Prior to ScanNT 4.2.X, we used Sybase SQL Anywhere 5.0. From ScanNet 4.2.X to 4.5.X, we used Sybase 6.0.3. Currently from ScanNet 4.6.X and 5.1 it is required that you use Sybase 6.0.4.3799. When you install Sybase SQL Anywhere, choose the Sybase SQL Anywhere Server (including the Engines and SQL Remote). When you install Sybase Adaptive Server Anywhere (Sybase 6.0.3 or Sybase 6.0.4.3799), Choose Network server (includes Personal server with SQL Remote). Uncheck UltraLite development components, MobiLink synchronization server and jConnect. When you install Sybase it will ask for Licensed Seats. You can enter as many seats as you want, because your ScanNet serial number will limit how many Clients you have connected to your ScanNet Server. If you enter the number 1 in the Licensed Seats field, and later decide to connect another Client to the server, you will have to reload Sybase to add more licensed seats to make the proper connection. If you enter the number 20 under Licensed Seats, and only have permission to 1 Computer, you will not have connectivity to any Client. If you update your ScanNet serial number for permissions to more than one, all you have to do is go to the ScanNet main navigation bar, choose file/Options/Click on the Registration Tab/Enter the new Registration number/and click OK. Since you already set Sybase to accept the extra connections you will not have to reload Sybase. Crystal Reports (optional) If you choose to use Crystal Reports, be sure to purchase the correct version. Prior to ScanNT 4.0.X, we used Crystal Reports Professional, Standard, or Development 6.0. From ScanNet 4.0.X to 4.5.X, we used Crystal Reports 7. Currently with ScanNet 4.6.X and 5.1 it is required that you use Crystal Reports 8.5. Crystal Reports 6, 7 and 8 are not backwards compatible, or compatible in any way. They are to be run using their respectable drivers meant to work with either 6 alone, 7 alone, or 8 alone. PC Anywhere (optional) If you choose to use PC Anywhere, be sure to purchase the latest version. Device intermittently drops offline and comes back online There are a couple of things to check. First, have any devices been changed recently? You may have two devices on-line with the same address. Second, you may need to check other devices in your system other than the one that seems to be going off-line. SCAN continuously communicates to various devices via a port controller. Occasionally, a device may drop off-line, or a number of devices may drop off-line. The device that SCAN shows as being off-line may not actually be the one that is offline. It could be the previous device or the one that follows the device that is indicated as being the off-line. Removing the 422-communication connector from either of these two suspected devices should cause all devices on the port controller to come back on-line. Change the Transmit Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 245 and Receive ICs. If this does not provide the solution, disconnect all communication cables from all devices and plug one in at a time, while constantly monitoring SCAN. Verify that devices come on-line and stay on. If plugging in a one device causes another device to go off-line, the device that was plugged in could be the offending device. Access Duration Report The Access Duration Report provides information about fees assigned to credentials, based on entries and exits, and also fees for illegal entries and exits. You can choose to print either a detail or a summary version of this report. The detail report includes the following information for each access: customer ID, credential ID, facility code, entry time, exit time, entry device, exit device, and fee assigned. The report also totals fees for each credential. If a credential has an unpaired exit (two consecutive), then for one exit, no entry time will appear, the exit device ordinal will be listed for both the entry and exit device, and the fee assigned will be 0.00. If a credential has an unpaired entry (two consecutive), then for one entry, no exit time will appear, the entry device ordinal will be listed for both the entry and exit device, and the fee assigned will be 0.00. When you print the report, you may enter in the Parameters Window a fee to be included on the report for all unpaired entries and exits. The summary report includes a fee summary for each credential. Note: For a credential to appear on the report, it must be associated with an account (must have an account ID). For fees to appear on the report, you must be using Billing and Invoicing. Note: This article was taken out of the ScanNet Manual Version 5.1. For details on other reports, refer to the ScanNet manual. Saving database report parameters do not show at the client computer ScanNet database reports allow you to specify the report parameters for the items to be included in the report and to save it as a custom report. If there are multiple consoles deployed on the ScanNet system, each such custom report must be created and saved at each console where they will be viewed as well as at the ScanNet host computer. ScanNet users must have read and execute privileges for reports in order to view them. Last Card Report If a card doesn’t work, you can use the report to help determine whether the cause is the card or the logic module. You can also use the Last Card report to figure out the correct facility code to use during an install. In addition, if card numbers wear off, you can use the Last Card report to identify the card number. The report also displays issue level and provides a reason why a card did not vend a gate. Cardlog Conversion If you are upgrading from the SCAN Facility Management System (DOS-based system) to the Scan NT Central Management System, you do not need to manually re-enter all the 246 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual fields in the Cardlog database. The new version of Cardlog (Conversion Application) will automatically map the source cardlog fields to the destination Scan NT database tables when you enter a default access package code for ranges of IDs. The latest Cardlog Conversion file is now located within the “Scan NT Support” section of the Distributor Resource Center of the 3M web site. Cardlog Conversion is no longer available in ScanNet 5.0. The last version of ScanNet with Cardlog Conversion is ScanNet version 4.6. ScanNet 4.4.2.2 Security #1. When you create a user name with capital letters, or a combination of capital letters and small case letters, and you don't log in using the same letter casing, it will register as an invalid user, and you may or may not be able to access some of the permissions that were given to the group. There was a work around for this problem and that would be to create all users with all lower case letters, and when the person logs on, they have to log on using all lower case letters in their user name. #2. The other problem was when you create a group with all read, write, and execute permissions, the last four (commands, programming, configuration, and utilities) did not show a (rwx) at the end of each of the four applications, even though permission had been granted. This was apparent when you were viewing the security groups window, and highlighted the all_access group (whatever you named it) to view what permissions where programmed. This was only a cosmetic problem, because all the users located under this group could still access commands, programming, configuration, and utilities when they logged on using their user name and password. Permission was not denied when they used these applications. Problems #1 and #2 are fixed in ScanNet 4.5.0.14. My suggestion is to upgrade ScanNet to 4.5.0.14, and you should have no more problems with security. The System Maintenance, Systems Options form in the ACS has to have the Host Computer name in it. ScanNet prior to 4.4.1.10 getting message “Error 94 invalid use of null” when patrons exit the facility An issue is present in ScanNet versions prior to 4.4.1.10 (released in May) that causes CAMP to stop responding when Billing is active and a Credential (any type) exists that has no fee associated with it. A workaround for this is to select a flat fee type and enter a fee amount of 0.00 in the Fee Set Up Form for the fee structures that are associated with the Packages used by these Credentials. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 247 Using a ScanNet server/client setup, when you re-boot the client computer, you cannot connect to the Server computer. You get a message that the DB service is not running. If you re-boot the server, the client connects like it should. Also, if you do not restart the server, and you wait 2 minutes, the client server connects to the Server correctly. The above anomaly only happens with certain operating systems. To fix this problem, follow these directions: Update your Sybase for 6.0.4.X to 6.0.4.3799. There are fixes that Sybase has made to 6.0.4 that correct the problem in this build. You can download the patch from the Sybase web site at http://www.sybase.com/ Click on My Sybase and log on with a user name and password that is provided as a free service from Sybase. Click on the link on the left hand side of the page, “developer” Click on the “mobile and wireless developer” Click on EBFs/Patches And from there select SQL Anywhere Studio. This will bring you to the page where all Sybase documents are stored (and where the document that you are looking for is located. Make sure you select “ALL” The file you need is located under the heading: Platform: Windows Make sure your service is shut down before running update. After updating, go to Start> Programs> Sybase> Sybase Central, and when you click on Tools> Plug-ins, it should say 6.0.4.3799 Scan NT not able to pull Statistics report using macro Install the database patch, or install Version 3.2. The database patch can be found on the 3M Web Site. You can order Version 3.2 from your 3M Customer Service Representative or download it from the web site. Network Interface Connection (NIC) card If you have Scan NT, you need an NIC card upon installation of Windows NT in order for Network Services to operate properly. Windows NT will “see” this card and load appropriate drivers. Receiving errors bringing up agent since loading Scan NT One way to prevent this is to be sure there are no spaces in the computer name. To change the computer name, go to the network control panel and change the computer name in the .ini file. You need to make this change in all four places in the .ini file. After you change the .ini file, save the changes and then reboot. You should not receive any more errors. 248 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Credential Options and set up There are four types of Credentials in the Scan NT System: Standard Credentials, Central Access Credentials, Central Access ValuePasses, and ValueCards. You can set up the first three types of Credentials with different options to meet the needs of your parking facility. The following lists the options: (A) Standard Credentials with No Billing (B) Standard Credentials with Billing (C) Central Access Credentials with No Billing or Group Control (D) Central Access Credentials with Group Control (E) Central Access Credentials with Billing but No Group Control (F) Central Access Credentials with Billing and Group Control (G) Central Access ValuePasses with No Billing or Group Control (H)Central Access ValuePasses with Group Control (I) Central Access ValuePasses with Group Control and Billing The following procedure leads you through the process of setting up the options. The steps marked with an asterisk (*) in the front are required for all options. Skip those steps that are not required for the options you are setting up: 1. In the Device Activity or Device Manager window, ensure the Readers are online, and in the Edit Device window, ensure data is correct and edit if applicable. 2. Configure the Readers in the Passport Plus Programming window. Required steps: Set up the Card Data Configuration, Options, Reader Set Up and Central Access ValuePass Configuration (For Options C to I). 3. Establish Access Configurations. Required steps: Create Access Configurations (Check the Central Access box for Options C to I), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4. (Required for Options F to I.) Configure and Save the PowerPad Fee tables if you desire to select RATE in Step 6. 5. (Required for Options E to I.) Enter the name and address you want to appear in the invoice into the System Options form. 6. (Required for Options B, and E to I.) Configure the Fee Set Up Form. Required fields: Fee Code, Fee Desc, and Fee Type. If you select FLAT in the Fee Type field, enter an amount into the Fee Amount field. 7. Edit the Package Set Up Form. Required fields: Package Type (Must be S for Options A, B, D, and H. For Option I, set up two Package Codes: One with Package Type S and choose the fee code in the Fee Code field to link the Fee Code to the Package, the other with Package Type G and Fee Code but do NOT choose Config ID). You choose the fee code in the Fee Code field to link the Fee Code to the Package. 8. (Required for Options B, and E to I.) Set Up the Accounts. Required fields: Customer ID. 9. (Required for Options D, F, H, and I.) Establish the DBA or Group Control. Required fields: DBA or Group ID, Name, Group Limit. Don’t select a Package C de if you desire patrons to pull tickets when the group limit is exceeded. Select the Package Code that is associated with a Fee Code so that if the group limit is exceeded, the patron can enter the facility without pulling a ticket but get billed. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 249 10. Enter Credentials into the Credential Sales form. Required fields: In the credential tab, Customer ID, Credential ID, DBA or Group ID (Mandatory for Options D, F, H, and I), Package Code (Central Access Package for Options C to I), Credential Validity, and Issue Level fields. Optionally, License Plate and State fields in the Vehicle tab and the Patron ID field in the Patron tab. 11. (Required for Options G to I.) Establish the ValuePass Options. Required fields: Credential ID, Charge Method, and Amount Paid. ScanNet Not Locking Out Standard Credentials with Group Control Because you are using standard credentials rather than central credentials, the reader keeps track of valid ID's and facility codes. Credential validity is not checked or controlled by CAMP if the credential is standard. CAMP cannot lock-out standard overlimit credentials. The only option for standard credentials with group control is to charge a fee for the credentials that are group-over-limit. This is the only way to enforce a group limit with standard credentials. If a parking operator requires for ScanNet to lock out group-over-limit credentials, then they will have to upgrade their readers to CAMP readers and set up their system as a central access with group control. Scan NT/Sybase 5.0 As Scan NT databases get larger, we have noticed a degradation of performance, especially for systems with many devices. One solution is to increase the amount of memory the database engine uses for cache. This can be accomplished by completing the following steps: 1. From the control panel, click the ODBC icon. 2. From the ODBC Data Space Administrator window, select the sa_scan entry and choose the Configure button. 3. From the SQL Anywhere ODBC Configure window, choose the Options button. 4. In the Startup Options window, add “-c 8000” to the end of the Start command. The default cache size is 2048K; this makes it 8000K (almost 8MB). According to technicians at Sybase, a good rule of thumb is to keep the cache at about 10 percent of the total database file size for optional performance. However, we have found that if the cache size is too large, the database engine won’t start; it won’t even give an error message. “Too large” will vary depending on the amount of RAM on the computer. Note that increasing the size of the cache caused a system with approximately 50 devices (mostly gates) controlling five lots to go from virtually unusable (extremely slow response due to unprecedented system activity) to normal operation. Loading Microsoft Office 2000 on a ScanNet PC Microsoft Office 2000 or Microsoft Access 2000 should never be loaded onto a computer after loading the ScanNet Central Management System. ScanNet uses some Microsoft Access 97 files and loading Microsoft Office 2000 or Microsoft Access 2000 after ScanNet has been installed will overwrite these files. Also, you should always run the latest Service Pack (currently 6A) after installing anything that requires the operating 250 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual system disk to be used if you have an NT system. If you have a Windows 2000 Professional Computer, which came with Microsoft Office 2000 (which will include Access 2000), when you load ScanNet onto the computer, you will overwrite the 2000 files with the 97 files that ScanNet needs. The computer will prompt you to ask if you want to replace your newer files with the older files. Replace your new files with the files included on your ScanNet installation CD for ScanNet to operate properly. With ScanNet version 4.6 and later, there is no longer an issue. System Activity Report: Passback Messages For Host-based Credentials only, to get a listing of Passback messages in the System Activity report, use Message Type as your parameter and pick Passback as the Message Type. Note that this Message Type is not currently tied to a Credential ID or reader when pulling the report. Avoid Unwanted “Door Readers” in ScanNet When a standard Port Controller is power cycled or initialized from SCAN DOS commands, occasionally unwanted devices (door readers) can inadvertently be created. This occurs because, when power cycled or initialized, the standard Port Controller clears its internal device table. Then, when it comes on line and ScanNet asks for an Active Device Report (ADR), there are no devices on line. When there are messages buffered in the Port Controller, these messages get sent to ScanNet before the devices come on line. If this happens, any message from any device will be assigned to a device type 0 (door reader). This creates door readers where they don’t belong, and stores the data from those messages as coming from a door reader. What Can Be Done The easiest way to avoid these unwanted door readers from being created is to unplug the RS232 cable from the Port Controller before power cycling or initializing. Another option is to disconnect the RS422 (devices) from the Port Controller and allow enough time for all messages to be cleared from the buffer before power cycling or initializing. In the event of a power failure, either both the ScanNet computer and all Port Controllers should be on the UPS or ScanNet should not be on a UPS. It will always take a computer longer to boot than the Port Controllers. Searching Credentials As a reminder, many people have asked questions about how to search for information in the Access Control System. If the user is at the Credential Sales Form, there is a “Search Data” button that allows the user to search the Credential Database on the various fields in that database. The steps are: (1) Highlight the field you wish to search on; (2) Click the binoculars from the toolbar; and (3) Enter the value for which you want to search. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 251 You can search for a complete match, or a partial match depending upon the criteria you define. Once you locate the record you are looking for, you can double click on that record and pull up the Credential for that record. Updating from Scan NT Versions to a ScanNet Version When installing ScanNet for the first time, the scannet.exe does not overwrite the old scan_nt.exe. This means that shortcuts or icons to the old executable will still exist. Before you start up ScanNet for the first time, delete any shortcuts from the desktop and remove any Scan NT references from the 3M folder. To delete the Scan NT references, follow these steps: 1. Right click the Start tab. 2. Click on “Open All Users.” 3. Double click the 3M folder. 4. Right click and delete anything Scan NT (such as help, navigator). 5. Recreate desktop shortcuts if desired. Updating the Database If you are updating your ScanNet installation and you have moved your database from its default location, you must be aware of one possible source of problems. The installation process will place new, blank databases in the Scan_NT\DB\SQL folder as well as update the working databases. If you have moved or copied these databases, you must make sure that you replace your old blank databases with new ones after the updating is complete. If you try to use the old blank databases, you will encounter errors due to an incorrect database structure. Two SQL Statements Available to Copy ID Fields to Name Fields for ScanNet In ScanNet version 4.X and earlier, when you chose an account or DBA group from a drop down combo box, you would only see the ID number that represented the account or DBA group name. These users of ScanNet entered names in the ID fields in the account and DBA group forms so when they chose the account or DBA group from the combo box, they would see the name instead of the ID. When these users upgrade, ScanNet 5.0 only displays the name fields, and the ID fields are hidden. This causes names entered in the ID fields to not be displayed. These SQL statements can be run separately or together depending on the need, and are ONLY for ScanNet users who had ScanNet version 4.X and earlier, and entered the information backwards so they would be able to see the name in the earlier Access Control System GUI. Accounts One of the SQL statements will copy the account ID fields to the account name fields allowing the user to see the account names in the Credential window. This SQL statement should only be used if your existing account names are an ID number rather than the name you had originally given it. You will not be able to change it back the way it was after executing this statement. After executing the statement, the Credentials window will 252 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual display the value that had been in the ID fields. DBA Groups The other SQL statement will copy the DBA group ID fields to the DBA group name fields allowing the user to see the DBA group names in the Credential window. This SQL statement should only be used if your existing DBA group names are an ID number rather than the name you had originally given it. You will not be able to change it back the way it was after executing this statement. After executing the statement, the Credentials window will display the value that had been in the ID fields. Going forward, customers will enter names in the name field and everything will run smoothly. If you see names in the combo box for accounts and DBA group in the Credentials window, DO NOT run either SQL statement because you will have ID entries displayed in the Name field. If you mistakenly run either SQL statement, you cannot undo your changes, and you will have to manually rename each account back the way it was, and you will have to resave each group as a new group name and delete the groups that are displayed improperly. Be sure you need the Account, DBA group, or both SQL statements before running it. Call Product Support at 877-777-3571 for details on these SQL statements. Facility Codes and Credential IDs Central Access (or Host-Based) Credential IDs in ScanNet must have a facility code of 0. Standard Credential IDs must have a valid facility code that is not 0. Standard Credentials that have a facility code of 0 will not show up in the Credential History on the Credential Sales Form. Central Access Credential IDs that have an assigned facility code (not the one physically encoded on the card) other than 0 will not function properly. Installing ADS Link Version 3.1 Create a folder on your C: called spslm and unzip the contents of the file spslm.zip into this new folder. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 253 Right Click on My Computer, go to Properties, and choose the Advanced tab in the System Properties window. Click on the Environment Variables button. Click on New… and add the new Variable Name: pcpos Variable Value: c:\spslm Click on OK. 254 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Double click on PATH under System Variables, click inside of Variable Value and hit the end key. Add the following with no spaces: ;c:\spslm Install the service by going to the Start button, and choosing Run… Type CMD and click on the OK button. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 255 Go to the spslm dir. By typing cd spslm then the enter key Type the following: service –install=ADS_PCPOS –PCPOS=C:\SPSLM Reboot the computer Check the service by going to the Control Panel, services. ADS_PCPOS should be Started and Automatic. 256 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual In order for Central Credit Card to work, you will need at least ScanNet 4.5 and C platform C3.4.0.8 PowerPad. Your ScanNet serial number also has to have Central Credit Card permissions with it. Edit the phone numbers by doing the following: At the command prompt, go to the spslm directory and type in “confedit” to enter the TID# and the Company ID#. Choose Merchant Information by pressing the M key. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 257 Enter the Company ID# and the Terminal ID#. Enter over to Save and Exit the Merchant Information by choosing X, and Configuration Main Menu by choosing X. Go back to Command prompt. Type in “phncard” to edit the primary and secondary phone numbers, and all other phone options. 258 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Choose Network File Editor by selecting the N key. Enter the Primary and Secondary Phone numbers, and use defaults for the rest of the settings. After editing the information, hit the ESC key and type X to exit the program. Check Central Credit Card in the ScanNet Properties window Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 259 Make sure that all of the options for Central Credit Card are all set correctly under View Options. Setting Up Central Access credentials with Billing and Group Control Step by step screen shots on how ACS Billing and Group Control should be set up with explanations on what the System Activity Report, the Access Durations Report, and what the Monthly Billing Invoice have in common. 260 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 261 262 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 263 264 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Put your Fee Table .PGM in the Scan_NT folder in order for the Fee Set Up Form to automatically recognize the fee rate. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 265 266 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 267 268 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 269 If you pull an Access Durations Report now, you will get the following: Run Billing as shown below. 270 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Once you run the Billing, you will see the Monthly Billed Amount on the Access Duration Report as shown below: Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 271 To print invoices, enter the following information. 272 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Do not reset the Billing Flag for the customer until the customer pays for their Bill. Enter the Cash received. You cannot view the Monthly Billing Invoice; you can only print it. Once you Reset the Billing Flag, the Access Durations Report will go back to showing only Access Durations, no Monthly Billed Amount will be shown. Main differences between the Monthly Billing Invoice and the Access Durations report On the billing report for the above Access Duration and System Activity Report, it will show a bill for the following: Sears: 00000000000000033698 3/1/2002 11:16:12 AM IN 00000000000000033695 3/1/2002 11:16:12 AM IN 00000000000000033693 3/1/2002 11:16:12 AM IN 00000000000000033681 3/1/2002 11:16:12 AM IN 00000000000000033695 3/1/2002 11:04:58 AM IN Group Over Limit/Exit 00000000000000033681 3/1/2002 11:04:56 AM IN Group Over Limit/Exit Total Due $3.00 $3.00 $3.00 $3.00 $5.00 $1.00 $18.00 Hudson’s: 00000000000000033702 3/1/2002 11:16:13 AM IN 00000000000000033701 3/1/2002 11:16:13 AM IN $0.00 $0.00 Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 273 00000000000000033682 3/1/2002 11:16:13 AM IN 00000000000000032769 3/1/2002 11:16:12 AM IN 00000000000000032769 3/1/2002 11:05:12 AM IN Group Over Limit/Exit 00000000000000033682 3/1/2002 11:05:01 AM IN Group Over Limit/Exit Total Due $0.00 $0.00 $1.00 $5.00 $6.00 You will notice that these totals do not add up to the Access Durations Totals, and here is why: In the Access Durations Report The first line under credential: Number is the initial check for if the credential is in a Group or not, and what the charge would be if they are not in a group. EXAMPLE: Customer ID: 1 credential: 00000000000000033681 facility code: 0000000000 Central Access Only DUR FEE 03/01/2002 11:03:24AMREADI P01 D04 03/01/2002 11:04:00AMREADE P01D0 1sec 1.00 03/01/2002 11:03:00AMREADI P01 D04 03/01/2002 11:04:00AMREADE P01D0 1sec 1.00 Monthly Billed Amount 03/01/2002 11:16:12 3.00 Total for credential: 00000000000000033681 facility code: 0000000000 5.00 It will add this charge to the total for the credential and the Customer. If they are not Group Over Limit, this will be the only charge line. The second line is the Group Over Limit Charge. This charge will be added to the total for the credential and the Customer. The Last line to take note of is the Monthly Billed Amount. This will reflect a charge as long as there is a fee associated with the credential via the package code. It has to be a Standard Package code in order to bill monthly fees. In the Monthly Billing Invoice If a customer is using Group Control, then they will not be charged for the credential unless they are Group Over Limit, or unless they have a fee associated with the credential via the package code. Billing ignores any fees associated with the credential if they are within the Customer’s Group limit. On the Access Durations Report If you ignore the first line under credential: Number, and add everything else up, it will come to the same totals as in the Monthly Billing Invoice. The line to be ignored is the line starting with the date and the time showing seconds. The reason that the first line shows seconds, and the rest only Show xx:xx:00 is because the first instance of time under the credential reflects the computer time from CAMP. The rest of the times in the Access Durations Report reflect times from the reader, where the Dallas Time Clock does not have a second’s field. 274 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual What are some common Sybase SQL statements? Changing credential Types What to accomplish To change all credential types to standard To change all credential types to central access only To change all credential types to central access + ValuePass To change all credential types to ValueCard What table to edit table_acs_credential table_acs_credential table_acs_credential table_acs_credential Set a credential Type if Nothing was Picked What to accomplish What table to edit To set credential types to table_acs_credential standard if nothing was picked To set credential types to central access only if nothing was picked To set credential types to central access + ValuePass if nothing was picked To set credential types to ValueCard if nothing was picked Delete All credentials What to accomplish Delete all credentials table_acs_credential table_acs_credential table_acs_credential What table to edit table_acs_credential Delete credentials not padded with Zeros What to accomplish What table to edit Delete credentials not padded with Zero Troubleshooting Manual table_acs_credential SQL Statement Update table_acs_credential set value_pass=0 Update table_acs_credential set value_pass=1 Update table_acs_credential set value_pass=2 Update table_acs_credential set value_pass=3 SQL Statement Update table_acs_credential set value_pass=0 where value_pass is NULL Update table_acs_credential set value_pass=1 where value_pass is NULL Update table_acs_credential set value_pass=2 where value_pass is NULL Update table_acs_credential set value_pass=3 where value_pass is NULL SQL Statement Delete table_acs_credential SQL Statement Delete table_acs_credential where credential_id not like ‘00%’ 78-0060-4094-9, Ver. 1 Notes about SQL Statement This statement uses single quotes. ScanNet • 275 Delete a Block of credentials What to accomplish What table to edit Delete credentials within a range table_acs_credential SQL Statement Delete table_acs_credential where credential_id between ‘X’ and ‘Y’ Changing Passback Settings for Central Access Only* What to accomplish What table to edit Change Passback Settings for table_acs_credential Central Access Only to Soft Change Passback Settings for table_acs_credential Central Access Only to Hard Change Passback Settings for table_acs_credential Central Access Only to Exempt *Standard IDs are NULL Set Issue Level to 01 if Customer Left Field Blank What to accomplish What table to edit Set issue level to 01 if the table_acs_credential customer left the field blank Reset DBA Group Count to Zero What to accomplish What table to edit Reset DBA Group Count to table_acs_dba_group Zero 276 • ScanNet 78-0060-4094-9, Ver. 1 Notes about SQL Statement This statement uses single quotes. X = first number in range. Y = second number in range. credential IDs are 20 characters long. SQL Statement Update table_acs_credential set pass_back=0 Update table_acs_credential set pass_back=1 Update table_acs_credential set pass_back=2 SQL Statement Update table_acs_credential set issue_level=1 where issue_level is NULL SQL Statement Update table_acs_dba_group set group_count=0 Troubleshooting Manual Retrieve Issued Ticket Stack from Original Database after a Light Migrate What to accomplish What table to edit SQL Statement Notes about SQL Statement Retrieve the issued table_ticket_issue This is a three step ticket stack from the process. original database after First save a blank text a light migration. file to the C drive and call it tktissue.txt. Make sure you are connected to the original database. Unload This is the second table_ticket_issue to step. While ScanNet ‘c:\tktissue.txt’ is connected to the original database, run this SQL statement. This loads the data from the issued stack to the text file you created. After running this statement, disconnect from the original database, and connect to the migrated database. Load This is the last step if table_ticket_issue you are using exit from ‘c:\tktissue.txt’ cashiering only. If you are using central cashiering, follow the next steps to load the paid stack as well. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 277 Retrieve Paid Stack from Original Database after a Light Migrate Retrieve the paid table_ticket_paid stack from the original database after a light migration. Unload table_ticket_paid to ‘c:\tktpaid.txt’ Load table_ticket_paid from ‘c:\tktpaid.txt’ Set DBA Group to 1 if Field is NULL What to accomplish What table to edit Set DBA Group to 1 if Field is table_acs_credential NULL. SQL Statement Update table_acs_credential set dbaorgroup_id=1 where dbaorgroup_id is NULL Delete Lots so They Will Not Show Up in the System Activity Monitor What to accomplish What table to edit SQL Statement Delete lots so that they will not show in the System Activity Monitor table_GCS_lots Update table_GCS_credential set deleted=1 where ord_lot =X Change credentials from Issued to Unissued What to accomplish What table to edit Change credentials from table_acs_credential issued to unissued 278 • ScanNet 78-0060-4094-9, Ver. 1 This is a three step process. First save a blank text file to the C drive and call it tktpaid.txt. Make sure you are connected to the original database. This is the second step. While ScanNet is connected to the original database, run this SQL statement. This loads the data from the paid stack to the text file you created. After running this statement, disconnect from the original database, and connect to the migrated database. This is the last step if you are using central cashiering Notes about SQL Statement X = the ord_lot number you want to mark as deleted. Do not delete the default lots where ord_scan = 0 SQL Statement Update table_acs_credential set cred_validity=‘unis’ Troubleshooting Manual Change Billing to Y for credentials What to accomplish What table to edit Change billing to Y for table_acs_credential credentials SQL Statement Update table_acs_credential set bill=‘Y’ Change Billing to NULL for credentials What to accomplish What table to edit Change billing to NULL for table_acs_credential credentials SQL Statement Update table_acs_credential set bill = (NULL) How To Set Access Control System With the Same Password As ScanNet 1. Click Systems on the ScanNet Navigator Bar 2. Choose Access Control System 3. Choose credential Maintenance 4. Now you will have to log on with the factory default. a. name administrator b. password fapd 5. Now choose the following: a. System Maintenance b. Tools c. Security d. User and Group Accounts 6. Now in this box you will add the name, and password that you want to work in Access Control System a. Now click on the new button b. Now enter the name of the person that you will be allowing to automatically enter Access Control. c. Now enter the personal id. This would be the password that they are using to get into ScanNet. d. Now click on the ok button 7. Now that you have added them, you need to assign some parameters for them. a. Now click on the drop down box next to the name’s, and choose the person that you just added. b. Now that they are showing in the box go down and use the add/remove buttons and put admins, and users into the box on the right. c. Now click on the Clear Password button d. Now click the Ok button 8. Now you should exit out of the Access Control System 9. Now you can Log back into the Access Control System, but this time use the Name that you added earlier, and leave the password blank. 10. Now click on the Ok button 11. Now choose the following: a. System Maintenance b. Tools Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 279 c. Security d. User and Group Accounts 12. Now click on the drop down box and select the name of the person that you have entered. 13. Now choose the tab Change Password. a. Leave old password blank b. Type in new password (same as used to enter ScanNet) c. Then Verify it. d. Now click on the Ok button Now you can exit Access Control, and re-enter. It should not ask you for a password any longer. Required Update for Central Credit Card In order for Central Credit Card processing to work properly with the current release of the ScanNet Central Management System (ScanNet) and the Auditor PowerPad, you must perform two upgrades. ScanNet must be upgraded to Version 4.6.1.8 and all PowerPads must be upgraded to Version C3.6.0.11. Performing these upgrades will correct the following situations that tend to occur in the current versions of the PowerPad and ScanNet: * The PowerPad Preferences does not accept all programming from ScanNet. This is evident by first sending Preferences programming to the PowerPad, and pulling it back from the PowerPad to verify if programming was sent. It will appear as if it has been sent correctly, but if you look at the PowerPad itself, only Activate Credit Card System will be programmed as Yes, and the rest, including Central Credit Card, will be programmed as No. This in turn will allow credit cards to be processed without approval and will be in the database, but not reportable for the customer. Upgrading the PowerPad to Version C3.6.0.11 will allow correct programming to be sent. * ScanNet does not have the correct range defined for Diners Card. Certain numbers will come up at the PowerPad as unknown card type. Upgrading ScanNet to Version 4.6.1.8 will allow for correct identification of all Diners Cards. ScanNet Version 4.6.1.8 also includes some revised reports and allows for printouts of certain screens. Database Does Not Appear to be for ScanNet 4.0.0 or Later Message When Updating Database If you do not have your database service running or are not connected to the database for other reasons, you will get the message "The currently installed sa_scan database does not appear to be for ScanNet 4.0.0 or later. You MUST perform a database migration manually before using this database with ScanNet." If you know that your database is newer than 4.0.0 when you are upgrading just continue installing the newer build. NEVER CANCEL UPDATE WHEN UPGRADING SCANNET. If you do, database corruption can occur. After the installation is complete, you have to update the database manually. First see if you can connect to the database through the ODBC by clicking on test connection in the System DSNs. After verifying a good connection, go to Windows Explorer by right-clicking the Start menu and choosing Explore. Expand the Scan_NT 280 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual folder, and open the folder located inside of the Scan_NT folder called Bin. Find the program called ScanUpdate.exe and double-click on this file to run the update program. Choose Yes to upgrade your database. If you still get an error after choosing Yes, then you have a problem connecting to your database possibly due to database corruption. Scan NT Update: Subscription Plan, Version 2.0 & Version 3.0 INSTALLATION Scan NT, as with many contemporary software packages using a relational database, requires that certain protocols be followed for proper operation. For many of us, this is a new experience that can be daunting at first. It is highly recommended that your technical support staff become acquainted with configuring ODBC (Open DataBase Connectivity) Administrators and System DSN’s (Data Set Name) - which is just one aspect of ODBC. 3M offers regularly scheduled training classes to help you with these topics. Scan NT uses Sybase SQL Anywhere (version 5.5.04) - an industry standard for database deployment. SQL (pronounced “see-quel”), stands for Structured Query Language. This “engine” is used to manage databases on a single computer, or for managing databases using a client/server arrangement on networks. Setting up the database is critical to running Scan NT. As an example, the database is where pertinent information, such as the device configuration (for gates, readers, fee computers, etc.) and financial reports, are stored. As you can see, setting up this database properly is critical. For those of you who ordered the Scan NT Subscription Plan and need assistance with installation, contact your regional office or the System Support Group in Novi. VERSION 2.0 This stand-alone (non-networking) version of Scan NT provides utilities for parking control and revenue control. Gates, ticket dispensers, and fee computers can be programmed, monitored and controlled by the system. One of the many features we’re sure you’ll like is the “click, drag and drop” icons to setup the entry/exit traffic lanes in an installation. At the same time, the Count Control System is extremely easy to custom design for different levels and lots. VERSION 3.0 This release of Scan NT will encompass basic Access Control with the parking package. Access Control will enable you to program, monitor, and audit card readers (among other features). New features include setting up “Credentials” - a more encompassing term used to describe the previous term “ID number.” A Credential may be an individual, a company, a vehicle, or any other parameter that describes how the information is sorted. The following product specifications outline some of the features and enhancements you’ll find in Version 3.0: 1. Event Control System a) Define Events (Timed Events) b) Define Action Scripts (Macros) 2. Access Control a) Passport Plus Card Reader Communication b) Access Control Programming Screens i) Reader Commands ii) Setup Readers Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 281 iii)Setup Agency iv) Setup Group Control v) Setup Port Controller c) Add Access Control to System Activity Window d)Add Access Control Database Tables e) Reporting for Access Control i) Patron List ii) Patron Exception Summary iii) Patron Exception Detail iv) Patron Summary v) Patron Detail with Filters vi) Time Zone vii) ID Status viii)ID Group Issue ix) Door Status x) Last Card f ) Access Control GUI (Graphical User Interface) i) Patron ii) Time Zone iii) Options iv) Drag & Drop/Create Devices v) Access Granted/Denied vi) Passback vii)Time Zone Violation 3. Send to Multiple Devices 4. Active Device Report 5. Security (One Password per Application Screen) a) Scan NT i) Revenue ii) Commands b) Counts i) Gate Count ii) Gate Monitor iii) Configuration c) Access Control d) Event e) Monitor f ) System Activity Monitor 6. Application Service Interface (ASI) for two-way communications 7. Accounts Receivable a) Credential File 8. Conversion of Card Log from SCAN Facility Management System At the 1998 NPA trade show in September, the entire Access Control package was demonstrated to the parking operators in attendance. The accounts receivable (A/R) integration with the Solomon Software general ledger package demonstrated how Credentials would be monitored, and how accounts would be billed. This is a very 282 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual exciting feature of Scan NT in that it is the only central management system on the market with this enterprise wide accounting capabilities. Things wrong with ScanNet 4.4.1.10 Three issues were discovered in ScanNet version 4.4.1.10. These are important and a special release is being prepared in which they will be corrected. While these issues are important, they will not cause a system failure and there are workarounds for them. The first is that getting passport plus programming from a file fails, causing an error. The error is “Power Builder Application Error (R1005). Application terminated.” Passport Plus programming can still be accomplished through all other normal methods. The second is that in the Counts Configuration window, a lot, sub-lot, or facility can easily be deleted unintentionally. When deleting a lane, lot, or sub-lot, you may be prompted to confirm deletion of the next higher lot, sub-lot, or facility. While there is an opportunity to decline the deletion, you will not be expecting the deletion of these items and could easily confirm the deletion of the entire facility. The third issue is that in the ECS when creating an action step to program PowerPad devices, APS does not show up in the device list (when there are such devices configured and online). This special release will also include the remedy for the accumulation of temporary files that are created by Crystal Reports when reports are generated. Use of this feature will involve setting up a macro to run at the desired interval. More details of this will be included in the release notes. If you have not already loaded release 4.4.1.10 and do not need to for other reasons, use the latest version of ScanNet. Version 4.6.3.6 Version 4.6.3.6 of the ScanNet Central Management System (ScanNet) was released in May 2002. This release includes the following new features: * The Central Credit Card System reports have been enhanced and are now available in Database Reports. You must delete all prior Credit Card reports that you may have added to Database Reports before you install this version of ScanNet. *You may now enter NetPort IP addresses in the Scan_NT.ini file using ScanNet Properties, rather than having to edit the ini file directly. *You may now inhibit the displaying of the ScanNet “splash” screen that is displayed when ScanNet starts up and as a background for the Commands and Programming applications. This screen may slow some systems. *You may now turn on 100K Reader functionality in ScanNet Properties, rather than having to edit the ini file directly. *Support was added for Central Credit Card processing with Global Payments (East) (leased line, host mode). The following are prior issues that are resolved in this release: *When you edit port controller information in ScanNet Properties (Devices tab) and then apply your changes, your NetPort’s IP addresses remain in the Scan_NT.ini file. *You may now program the ID Status for elevator controllers, 100K Readers, and ValueCards for the entire ranges of possible IDs. *When programming timer events in the Event Control System, the times you enter will remain as you enter them. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 283 *Double-clicking a field in the Count Configuration will no longer cause the system to fail. *The APS is now included as a choice in Report Selection for revenue reports. *In LPI Configuration, you assign one Hand Held name regardless of the number of Hand Held computers you are using, and data will be downloaded when you perform the download from the LPI to ScanNet. *When printing a database report, only the devices related to the report will be available for selection in the parameter window, rather than all devices. *In the Central Credit Card System, if the PowerPad loses communication with ScanNet before the approval of a credit card transaction is received and the PowerPad times out, a reversal for the transaction will be processed. *Voided credit card transactions now appear correctly on credit card reports. *In the Central Credit Card System, void transactions will no longer be lost if they occur when ScanNet or the credit card system is being started and is not fully running yet. *The Central Credit Card System and the Database Archiver may now be open at the same time. *credentials that are denied for invalid time zone are no longer marked as “in” by CAMP. *In the Central Credit System, approved credit card floor limit transactions may now be voided. *The search function in License Plate Inventory now works correctly for license plate numbers collected in entry mode. *When the credential ID Report is run, the validity parameter “issued” now works properly. *Incomplete approved credit card transactions that are voided at the PowerPad and automatically voided in the Central Credit Card System are now being updated in the database correctly. *You may now program a time zone within 22:59 to 23:59 without error. *In the Event Control System, when you create an Action to program readers and select an individual programming item (such as Holidays or ID Status) the event will now run properly. Coming soon is version 5.0 with a new Access Control System and new Billing and Invoicing System. Version 4.6 3M released version 4.6 of the ScanNet Central Management System (ScanNet) in January 2002. This release includes the following new features: *The NetPort functionality in ScanNet has been enhanced to allow multiple subnets. You must enter the IP address of each NetPort in the Scan_NT.ini file (in the DM section, at the end of the line defining the port number). You no longer need to configure the HOSTS file for the NetPort. (See ScanNet Tips on page 4 for more about this functionality.) *Support was added for Central Credit Card processing with First Data Merchant Services and with Paymentech. *Functionality was added in the Central Credit Card System for printing the current batch, batch history, floor limit list, and decline list from within the application. 284 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual *Functionality was added in the Central Credit Card System for setting credit card processor options and for setting batch history view options. *The LPR Entry and Exit Reports were added. These are used with license plate recognition to track license plates at entries and/or exits via the ticket number. The following are prior issues that are resolved in this release: *The Central Credit Card resubmit functionality works correctly. *The Access Durations Report works properly for ValuePasses with dollar values and Central Access credentials, if group control is being used. *In the Billing, Invoicing, and Payment System, when group control is used, when the group limit is violated, credentials are now billed properly. *Deleted lots no longer appear in the Monitor and in the Event Control System Step Builder. *The coins and notes totals are no longer missing in the current balance on the APS Lane Report. *In the Central Credit Card System, incorrect dollar values and negative numbers no longer appear as a result of the system rounding dollar amounts for display. Versions 4.4.2.2 and 4.5.0.14 Two versions of the ScanNet Central Management System (versions 4.4.2.2 and 4.5.0.14) were released. version 4.4.2.2 version 4.4.2.2 includes the following new feature: *A macro has been added to the Event Control System (ECS) that allows you to automatically delete the contents of the C:\Temp folder on a regular basis to increase hard drive space for optimal system performance. To set up the macro, first follow the instructions in the ScanNet Operator Manual for creating an action. When the Step Builder is displayed, select Run File and Wait. When you are prompted to select a file, in the “Files of type” box, select “All files.” Then browse to find and select the Delete.bat file located in the Scan_NT\Bin folder on the drive where you installed ScanNet. After you set up the action, follow the steps in the manual for editing when timer events occur and linking events to actions. An error message may display after you create the action and click the Apply button. If this happens, click OK when prompted to close the windows and to terminate the application. The macro will be present when you restart the ECS. This version also includes the following resolutions of prior issues: *Device Control no longer closes when you retrieve reader programming from a file. *In the ECS, when you create an action to apply to PowerPad, APS are now displayed in the Select Device list. *In the ECS, when you create an action to pull reports for all PowerPad, the action is now correctly saved as such, instead of as all APS. *In the Counts System, when you delete an item, the system now displays the correct prompt to confirm or decline deletion if there are associated “child” items. When you delete an item, only the selected item and any associated items are deleted. When you decline deletion when prompted, no items are deleted. version 4.5.0.14 Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 285 version 4.5.0.14 includes the following new features: *The Central Credit Card System in ScanNet processes credit card transactions that occur at a PowerPad and are sent to ScanNet, and those entered manually in ScanNet. The system transmits these transactions to a credit card processor (outside company) for authorization. *The Unreadable/Lost Tickets Validation feature allows you to replace a ticket for a patron who has an unreadable or lost ticket, by sending the pertinent information from ScanNet to a PowerPad or APS in the facility. For an unreadable ticket, ScanNet sends the ticket number, lane number, and fee number. For a lost ticket, ScanNet sends the fee number, and the fee displays for the patron. *The ValuePass Create/Addon and ValuePass Usage reports were added. *The ValueCard Create/Addon Report was enhanced to allow you to select either normal or incomplete (void) transactions. This version also includes the following resolutions of prior issues: *The credential ID Report now correctly reports data when you choose the account parameter. *The user name in ScanNet Security is no longer case sensitive. *The ValuePass Posting Reader now displays addon and refund transaction values instead of balance values. *When you delete a patron or a vehicle for a credential, the credential is no longer inadvertently deleted. Version 4.4.1.10 The ScanNet Central Management System (version 4.4.1.10) was released at the end of May 2001. Resolutions of Prior Issues version 4.4.1.10 includes the following resolutions of prior issues: *You no longer need to have devices online for CAMP to start properly. *In ScanNet Security, the administrator user may no longer be deleted from the Administrator group. *CAMP now counts group entries and exits that occur when Readers are offline. *The Access Durations Report now reports data as intended when only one credential is selected. This includes information for usage and duration ValuePasses, and properly reports data for accounts with alphanumeric IDs. *Several resolutions for various other reports, including the Cashier and Lane Summary reports, ValueCard Creation Report, and Transaction Summary Report. Refer to the Release Notes shipped with this version for a complete list of the resolved issues as well as operating tips. New Features Also included in the release are the following new features: *In ScanNet Security, you may now assign execute permission to specific macros in the Event Control System. *ScanNet version 4.4.1.10 resolves the issue that would sometimes prevent connecting more than once to the database using Sybase Central. This resolution does require upgrading to Sybase version 6.0.4. 286 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual *CAMP now allows exits in group over-limit cases, even when no fee is attached to the group package code. Version 4.4.0.21 3M released version 4.4.0.21 of ScanNet. This version resolves the following issues: *In Passport Plus Programming, to set an Inhibit Input, you can use any Reader Input, 16. Also, if you program more than one Reader Input while in the Monitor Input mode, the programming is now saved correctly. *ValuePass Readers and Posting Readers now display duration balance. *ValuePasses created using Posting Readers now enter a record to the financial table. Also, the end time for a ValuePass created using a Posting Reader is now entered into the database correctly. *Posting Readers now calculate the correct end date for a refund. *You can now use multiple Posting Readers in the same ScanNet system without causing the Central Access Management Program (CAMP) to stop responding. *The License Plate Inventory (LPI) database records now print correctly. *Database reports now print without a blank page preceding the data. *The Issued Ticket report and the Validated Ticket report now print correctly. *A new report “Void Complete Transaction Summary report” was added to the set of standard reports. This report is identical to the Transaction Summary Report except it only reports on those transactions that were voided after completion. *You can now pick an account as a parameter in the Parameter window for database reports. *The System Activity Alarm window no longer shows Filtering as a valid user option. It is grayed out. *You can now access the Trip Resolver window. *ScanNet no longer overwrites the PowerPad key mapping which had been causing the <Shift><Jump> feature (Exit/Central Cashiering toggle) to be inoperable. The <Shift><Jump> feature now operates correctly. Version 4.4 Version 4.4 of the ScanNet Central Management System, released in early February 2001, includes these new features: Multi-Level Security The Security configuration has been enhanced to allow you to assign more specific permissions to users for the applications in ScanNet. You may assign read, write, and execute permissions to users for specific areas in ScanNet applications like Reports, Programming, Configuration, and so forth. The system administrator assigns permissions by setting up security groups, assigning permissions to the groups, and then assigning users to the groups. Database Split In Database Archiver, you may now split a ScanNet database into multiple databases, using specific dates to determine where the split occurs. Splitting a database copies a database into the segments you define and to the locations you define; the original database remains intact in its original location. New Macro in the Event Control System A new macro in the Event Control System (ECS) allows you to program the resync of all hostbased credentials to occur at specified times. In previous versions of the software, this programming had to be done manually. The macro is available in the ECS Step Builder as Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 287 Reset>Host- Based Passback. You may select either a one-shot resync, which gives each credential a free in or out, or an exit-cycle resync, which marks all credentials as out. Note that the resync of standard credentials is still handled by the Port Controller. ValuePass Posting Reader Load Programming In ValuePass Posting Reader Load Programming, you can now view values, either create or add on/refund, that were previously programmed and stored in the database for a specific Reader. You may change these values if necessary and then reapply them to the same Reader or apply them to a different Reader. version 4.4 Additional Features credential ID Calculation Utility This utility can be used to determine the ID number to assign to a specific credential. Using this utility, you enter the credential’s Physical ID number and facility code and specify whether the reader type is a 26-bit or 27-bit, and the utility displays the credential ID number you should assign to the credential. CardLog Conversion Program This program has been enhanced to allow users to convert multiple CardLog files. This is possible with the addition of the facility code field. Version 4.3 Version 4.3.0 of the ScanNet Central Management System was released in December. The release includes many new features. Access Durations Report The Access Durations Report provides information about fees assigned to credentials, based on entries and exits, and also fees for illegal entries and exits. When you run the report, on the Parameters Screen you may enter a flat fee to be included on the report for all unpaired entries and exits. Paid Thru Date Also in this release, you can use the Paid Thru Date, which is entered on the Cash Receipts form, to control access to customer’s credentials, based on whether their payments are current or delinquent. To do this, you can set up an Event Action in the Event Control System, which checks the Paid Thru Date of all credentials marked to be billed (Bill field on credential Sales Form is set to Y), and if this date is later than the current date, the credential’s status is set to/kept at Issued (valid). If the Paid Thru Date is before the current date, the credential’s status is set to Delinquent and the credential will be denied access. You can use another Event Action in the Event Control System to send blocks of Standard credentials to Readers, so that they have the most current credential validities. Registration Number Control version 4.3 also includes registration number control for the number of devices and the number of console connections. To connect to the proper number of devices and consoles, when you install ScanNet, you must use the registration number included with the software that was purchased for the facility. If you have more devices online than the registration allows, ScanNet applications will not run after you install 4.3. Also, you will be allowed to connect to ScanNet with only the number of consoles that the registration allows. After you install version 4.3, if you purchase additional device or console connections for your existing ScanNet software, you do not have to reinstall ScanNet. Instead, you may enter your new registration number, provided to you when you purchase the additional connections, by using the new Change Registration feature File>Options from the ScanNet Main Navigator). If you attempt to start ScanNet Core 288 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual and a message window is displayed indicating the ScanNet registration number you entered during installation is an invalid one, you have either entered the number incorrectly or are attempting to use a number that is not a valid ScanNet registration number. ScanNet Core will not start until you either install ScanNet using your valid registration number or change the registration number to your valid registration number by using the new Change Registration feature. ODBC Setup Wizard Another feature in this new version, added to the ScanNet installation program, is an ODBC Setup Wizard, which guides you through the ODBC configuration of your ScanNet databases, for either a stand alone or a client/server system. The wizard gives you the option of keeping your existing configuration or creating a new one. If you choose to create a new one, the wizard deletes the existing one. If you have a client/server system, the wizard allows you to define the database server name. If you need to make changes to your configuration after you install ScanNet, you may run the ODBC Setup Wizard by running the CreateDsn.exe file from the Scan NT\Bin folder on the drive where you installed ScanNet. Other Features Also in 4.3, the Compact Database feature in Database Archiver has been enhanced to allow you to select the database you want to compact. Other features in 4.3 are support for Elevator Control programming, 500 attendants at the PowerPad, and 16 Groups with 1 Issue Level for Series Readers. A later release of ScanNet version 4.3 will include multilevel security. Scan NT 4.0 In this version, you will see new features, options, and enhancements. Three of the most significant enhancements include the addition of the Central Access System, the Billing/Invoicing/Payment Systems, and changes to the Credentials folders. The Central Access System offers a method of pre-selling parking passes to parking patrons by offering Value Passes and/or Credentials. This value added concept in prepay parking is ideal for a wide range of applications, especially those featuring repeat customers, special event parking, promotional campaigns, and courtesy packages. Parking operators will be able to produce and sell decrementing-parking passes with a specific value assigned to each pass. Users will also be able to control the Doing Business As (DBA) or Group feature. You will be able to set up the Group limit and method to charge DBA or Group if the limit is exceeded. You will also be able to create and maintain Fee Structures and associate the appropriate Fee Table file to the parking package. The Billing/Invoicing/Payment System will produce an invoice with information gathered for the desired billing period from various sources. This new system will also enable users to record the information regarding the payments, make miscellaneous charges and adjustments, print detailed and summary invoices, and reset accounts at the end of a billing cycle. In Version 4.0, you will also see changes in the Credential feature. Using the Recycle ID form, you will be able to change the status of Credentials to grant or deny their access based upon whether the parking fees are paid. You will also be able to add Credentials to the Access Control System quickly using two new forms: the Load Credential Record Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 289 and the Express Credential Form. These are just a few of the new features and enhancements that will be available to you when the new version of Scan NT is released. Look for further updates in future issues. 290 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Setting Up the Central Access ValuePasses with Billing and Group Control NOTE: Add CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. Billing option will be activated for ValuePasses when the group limit is exceeded. 1. In the Devices window, ensure the Readers are online and data is correct. 2.Configure the Readers in the Passport Plus Programming window. Note: Set up the Card Data Configuration, Options, Reader Setup and ValuePass ID Ranges 3.Establish Access Configurations. Note: You must create Access Configurations (Must check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4.Configure the PowerPad Fee tables. 5. Enter your name and address into the System Options Form. 6.Configure the Fee Set up Form. Note: You must enter values into the Fee Code, Fee Desc, Fee type fields, and if you select FLAT in the Fee type field, you must also enter an amount into the Fee Amount field. 7.Edit the Package Setup Form. Create separate package for group control. Setting Up the Standard credentials with Billing Option NOTE: Before you set up the Billing option, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. 1. In the Devices window, ensure the Readers are online and data is correct. 2.Configure the Readers in the Passport Plus Programming window. Note: Set up the Card Data Configuration, facility codes, Options, and Reader Setup 3.Establish Access Configurations. Note: You must create Access Configurations (Must not select the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4. Enter your name and address into the System Options Form. 5.Configure the Fee Set up Form. Note: You must enter values into the Fee Code, and Fee Desc. fields. You must select FLAT in the Fee type field, and enter an amount into the Fee Amount field. 6.Edit the Package Setup Form. Note: You must edit Package Type (Must be S) and Config ID (Must be a Basic Access Configuration). You choose the fee code in the Fee Code field. 7.Set up the accounts. Note: You must edit Package Type (Must be G) and Config ID (Must be a Central Access Configuration). You choose the fee code in the Fee Code field. Note: You must enter values into the Customer ID, and Name fields. 8.Set up the accounts. 8.Enter credentials into the credential Sales Form. Note: You must enter values into the Customer ID, and Name fields. Note: In the credential tab, you must select Standard as the credential Type; You must enter values into the credential ID, Package Codes, credential Validity, and Issue Level fields; You must select Y from the Billing dropdown list box. You must enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. 9.Establish the DBA or Group Control Note: You must enter alphanumeric values into the DBA or Group ID, Name, and Group Limit fields. You must select a Package Code. 10.Enter credentials into the credential Sales Form. Note: In the credential tab, you must select Central Access ValuePass as the credential Type; You must enter values into the credential ID, DBA or Group ID, Package Codes, credential Validity, and Issue Level fields; You must select Y from the Billing drop-down list box. You must enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. NOTE: Anti-passback and Passback status resynchronization are not applicable when you are using Standard credentials. NOTE: If you want to view history data for Standard credentials, you need to enter CAMP.exe in the Additional field in the Advanced tab of the ScanNT Properties window. 11.Establish the ValuePass Options. Note: On the Access Forms menu, click Central Access ValuePass. In the Central Access ValuePass form, you must enter values into the credential ID, Charge Method, Amount Paid, and Payment Method fields. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 291 Setting Up the Central Access ValuePasses with Group Control but No Billing NOTE: Before you set up the Central Access ValuePasses, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. Setting Up the Central Access credentials with Group Control but No Billing NOTE: Before you set up the Central Access credentials, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. 1.In the Devices window, ensure the Readers are online and data is correct. 1.In the Devices window, ensure the Readers are online and data is correct. 2.Configure the Readers in the Passport Plus Programming window. 2.Configure the Readers in the Passport Plus Programming window. Note: Set up the Card Data Configuration, Options, Reader Setup and credential ID Ranges Note: Set up the Card Data Configuration, Options, Reader Setup and credential ID Ranges 3.Establish Access Configurations. 3.Establish Access Configurations. Note: You must create Access Configurations (Must check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. Note: You must create Access Configurations (Must check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4.Configure the PowerPad Fee Table. 4.Edit the Package Setup Form. Create separate package for group control. 5.Edit the Package Setup Form. Create separate package for group control. Note: You must edit Package Type (Must be G) and Config ID (Must be a Central Access Configuration). You may need to edit values in the Package Code and Package Name fields. 6.Set up the accounts. (Optional) Note: You must enter values into the Customer ID, and Name fields. 7.Establish the DBA or Group Control Note: You must enter alphanumeric values into the DBA or Group ID, Name, and Group Limit fields. 8.Enter credentials into the credential Sales Form.* Note: In the credential tab, you must select Central Access ValuePass as the credential Type; You must enter values into the credential ID, Package Codes, DBA or Group ID, credential Validity, and Issue Level fields; You should select N from the Billing drop-down list box. You must also enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. Note: You must edit Package Type (Must be G) and Config ID (Must be a Central Access Configuration). You may need to edit values in the Package Code and Package Name fields. 5.Set up the accounts. (Optional) Note: You must enter values into the Customer ID, and Name fields. 6.Establish the DBA or Group Control Note: You must enter alphanumeric values into the DBA or Group ID, Name, and Group Limit fields. 7.Enter credentials into the credential Sales Form. Note: In the credential tab, you must select Central Access credential as the credential Type; You must enter values into the credential ID, Package Codes, DBA or Group ID, credential Validity, and Issue Level fields; You should select N from the Billing drop-down list box. You must also enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. 9.Establish the ValuePass Options. Note: On the Access Forms menu, click Central Access ValuePass. In the Central Access ValuePass form, you must enter values into the credential ID, Charge Method, Amount Paid, and Payment Method fields *NOTE: The ValuePass tab in the credential Sales Form provides read-only data. 292 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Setting Up the Central Access ValuePasses with No Billing or Group Control NOTE: Before you set up the Central Access ValuePasses, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. Setting Up the Central Access credentials with No Billing or Group Control NOTE: Before you set up the Central Access credentials, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. 1.In the Devices window, ensure the Readers are online and data is correct. 1.In the Devices window, ensure the Readers are online and data is correct. 2.Configure the Readers in the Passport Plus Programming window. 2.Configure the Readers in the Passport Plus Programming window. Note: Set up the Card Data Configuration, facility codes, Options, Reader Setup and ValuePass ID Ranges Note: Set up the Card Data Configuration, facility codes, Options, Reader Setup and ValuePass ID Ranges 3.Establish Access Configurations. 3.Establish Access Configurations. Note: You must create Access Configurations (Must check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. Note: You must create Access Configurations (Must check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4.Edit the Package Setup Form. 4.Edit the Package Setup Form. Note: You must edit Package Type (Must be S) and Config ID (Must be a Central Access Configuration). You may need to edit values in the Package Code and Package Name fields. Note: You must edit Package Type (Must be S) and Config ID (Must be a Central Access Configuration). You may need to edit values in the Package Code and Package Name fields. 5.Set up the accounts. (Optional) 5.Set up the accounts. (Optional) Note: You must enter values into the Customer ID and Name fields. Note: You must enter values into the Customer ID and Name fields. 6.Enter credentials into the credential Sales Form.* 6.Enter credentials into the credential Sales Form. Note: In the credential tab, you must select Central Access ValuePass as the credential Type; You must enter values into the credential ID, Package Codes, credential Validity, and Issue Level fields; You should select N from the Billing dropdown list box. You must enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. Note: In the credential tab, you must select Central Access credential as the credential Type; You must enter values into the credential ID, Package Codes, credential Validity, and Issue Level fields; You should select N from the Billing drop-down list box. You must enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. 7.Establish the ValuePass Options. Note: On the Access Forms menu, click Central Access ValuePass. In the Central Access ValuePass form, you must enter values into the credential ID, Charge Method, Amount Paid, and Payment Method fields. *NOTE: The ValuePass tab in the credential Sales Form provides read-only data. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 293 Setting Up the Central Access credentials with Billing but No Group Control NOTE: Before you set up the Central Access credentials, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. 1. In the Devices window, ensure the Readers are online and data is correct. 2.Configure the Readers in the Passport Plus Programming window. Setting Up the Standard credentials with No Billing Option 1.In the Devices window, ensure the Readers are online and data is correct. 2.Configure the Readers in the Passport Plus Programming window. Note: Set up the Card Data Configuration, facility codes, Options, and Reader Setup. 3.Establish Access Configurations. Note: Set up the Card Data Configuration, Options, Reader Setup and credential ID Ranges 3.Establish Access Configurations. Note: You must create Access Configurations (Must check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4. Enter your name and address into the System Options Form. 5.Configure the Fee Set up Form. Note: You must enter values into the Fee Code, and Fee Desc. Fee type fields, select FLAT in the Fee type field, and enter an amount into the Fee Amount field. 6.Edit the Package Setup Form. Note: You must edit Package Type (Must be S) and Config ID (Must be a Central Access Configuration). You choose the fee code in the Fee Code field. Note: You must create Access Configurations (Must NOT check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4.Edit the Package Setup Form. Note: You must choose Package Type (Must be S). 5.Set up the accounts. (Optional) Note: You must enter values into the Customer ID, and Name fields. 6.Enter credentials into the credential Sales Form. Note: In the credential tab, you must select Standard as the credential Type; You must enter values into the credential ID, Package Codes, credential Validity, and Issue Level fields; You should select N from the Billing drop-down list box. You must enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. 7.Set up the accounts. Note: You must enter values into the Customer ID, and Name fields. 8.Enter credentials into the credential Sales Form. Note: In the credential tab, you must select Central Access credential as the credential Type; You must enter values into the credential ID, Package Codes, credential Validity, and Issue Level fields; You should select Y from the Billing drop-down list box. You must enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. 294 • ScanNet NOTE: Anti-passback and Passback status resynchronization are not applicable when you are using Standard credentials. NOTE: If you want to view history data for Standard credentials, you need to enter CAMP.exe in the Additional field in the Advanced tab of the ScanNT Properties window. 78-0060-4094-9, Ver. 1 Troubleshooting Manual Using the Billing, Invoicing, and Payment System NOTE: Before you use the Billing, Invoicing, and Payment System, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. 10.Configure the Billing Form. Setting Up the Central Access credentials with Billing and Group Control NOTE: Before you set up the Central Access credentials, you need to enter CAMP.exe into the Additional field in the Advanced tab of the ScanNT Properties window. Note: You must enter values into every field except the Comments field. 1.In the Devices window, ensure the Readers are online and data is correct. 11.Print the invoices. 2.Configure the Readers in the Passport Plus Programming window. 12.Record the information in the Cash Receipt Form. Note: You must enter values into the Customer ID, Journal Date, and Receipt Amount fields 13.Make adjustments with the Miscellaneous Invoicing and Adjustment Form. Note: You must enter values into every field except the Comments field. 14.At the end of a month, reset the accounts with the Month End Form. Note: Set up the Card Data Configuration, Options, Reader Setup and credential ID Ranges 3.Establish Access Configurations. Note: You must create Access Configurations (Must check the Central box), assign Readers to one Access Configuration, configure a new Time Zone, and add Time Zones to the selected Readers. 4.Configure the PowerPad Fee tables. 5. Enter your name and address into the System Options Form. 6.Configure the Fee Set up Form. Note: You must enter values into the Fee Code, and Fee Desc. Fee type fields, and if you select FLAT in the Fee type field, you must also enter an amount into the Fee Amount field. 7.Edit the Package Setup Form. Create separate package for group control. Note: You must edit Package Type (Must be G) and Config ID (Must be a Central Access Configuration). You choose the fee code in the Fee Code field. 8.Set up the accounts. Note: You must enter values into the Customer ID, and Name fields. 9.Establish the DBA or Group Control Note: You must enter alphanumeric values into the DBA or Group ID, Name, and Group Limit fields. You must select a Package Code. 10.Enter credentials into the credential Sales Form. Note: In the credential tab, you must select Central Access credential as the credential Type; You must enter values into the credential ID, Package Codes, DBA or Group ID, credential Validity, and Issue Level; You should select Y from the Billing drop-down list box in the credential tab. You must enter values into the License Plate, and State fields in the Vehicle tab and the Patron ID field in the Patron tab if you want to configure these two tabs. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 295 Scan NT 3.2 In this version we have added new functionality and options, and other changes. These changes include: Automatic Pay Station, Netport, PowerPad Initiated Reports, and Lot Sign Controller. The Netport will replace the standard Port Controller. It will function identically to the Port Controller except it will communicate faster, have more buffer space, and control 100,000 card IDs with auto-resync. You can send the following types of reports from a PowerPad Fee Computer: *Cashier *Account (Daily and Year-To-Date) *Lane (Daily and Year-To-Date) *Timecard *Tax (Daily and Year-To-Date) *Statistics (Daily and Year-To-Date) Note that sending reports from the PowerPad to Scan NT will clear the data on the PowerPad Fee Computer. In this release, users will also be able to specify the values for a particular parameters of database reports and save the specified values in a customized report. Users can also retrieve the predefined and customized reports to view. The Graphical User Interfaces (GUIs) used for retrieving PowerPad and database reports have changed. The new database report GUI enables users to specify the date and the range of credential IDs and groups, and to select multiple devices and message types to be included in the reports. In this release, Scan NT will also include the Lot Sign Controller Configuration and the Sign Control Application in the Scan NT Counts program. The Lot Sign Controller Configuration window will allow the user to relate a sign to a specific lot. The Sign Control Application will run whenever the Scan NT Agent runs. Whenever there is a count change, it will send the current count to the corresponding sign. If the lot is full, the corresponding sign will display the word “FULL” in red. If the lot is already full and one more card comes in, the word “FULL” will blink. Some other miscellaneous changes include: Poll Delay Time, Hexadecimal Numbering, and enhanced Graphical User Interfaces for retrieving PowerPad and database reports. Poll delay time is a specified number of seconds delay after Scan NT Core is up before it begins to poll devices. This provides time for the Event Control System to initialize. Hexadecimal numbering is now used to number Port Controllers. This is especially significant for users who have more than 100 Port Controllers in their facility. Hexadecimal numbering is base 16, which means it has 16 numerals. We represent this with 0 to 9 for the first 10 numbers (just as in decimal) and A to F for the six remaining numbers. Thus, A = 10, B = 11, C = 12, and so forth. (Remember, 0 is the first numeral, not 1.) Important notice when installing Scan NT 3.2.0: If you migrated the database from an older version and had an existing Cardlog, you must run the “credup.exe.” patch. This will pad all existing Credentials with the zeros needed to work with version 3.2.0. Also, when converting the SCAN Facility Management System (DOS-based system) Cardlog to Scan NT Credentials, you must use Version 1.7 for Scan NT Versions 3.1 or earlier, and use Version 1.8 for Scan NT Version 3.2. If you inadvertently use the old version with Scan NT 3.2, run credup.exe to get the zeros in the credentials. The “Cardlog Conversion” and “Credup.exe” files can be downloaded from the Scan NT Support page on the 3M web site. 296 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual Other questions about Scan NT 3.2 Q: Why won’t my System Activity Monitor display any messages? A: A Network Adapter Card (NIC) or a Network Loop-back Adapter (a simulated Windows NT adapter) must be installed with associated drivers in order for the messages to display. Q: How do I know if I have a Network Adapter/Network Loop-back Adapter? A: Right click on the Network Neighborhood icon, click Properties, then click in the Adapter tab. It should show if either a physical adapter is installed or the Loop-back Adapter is installed. Also, check under the Control Panel, Services, and the “Server” service should show as installed and running. If it is not installed, you must install the Windows NT networking services. Q: My computer is active on a network, or I have installed a Network Adapter or a Loopback Adapter, but I still do not have any messages in the System Activity Monitor. Why? A: First, check the ASI Host Console window to insure the messages are being sent from Scan NT to the ASI Host. The ASI Host icon is located next to the Scan NT icon on the lower right-hand corner of the screen. Click on the ASI Host icon, and the Scan Asi Host window will display. The top part of the screen should show a connection from the system activity monitor. The bottom right part of the screen should show system activity messages as they are sent from Scan NT to the ASI Host. If message are not being received from Scan NT, but you do have a system activity connection, check the following: * Open the Task Manager and check for multiple instances of the messdisp.exe running in the Processes tab. If there is more than one messdisp.exe running, shut down Scan NT completely. Then from the Task Manager, highlight the messdisp.exe that is still running and select End Process. Restart Scan NT. * Make sure that Scan NT is still polling devices. This can be done by checking the Device Manager console window to see if the polling counter is incrementing. You can also check in the Task Manager to make sure that the DM.EXE process is running. If not, shut down and restart the TPM Agent. If Scan NT is stopping the polling process, you must install the V3.1.1.7 patch, which you can get from the 3M Web Site. If messages are being received from Scan NT but you do not have a system activity connection, recheck that the appropriate adapter is installed. Make sure the network card is properly operating. Use the Event Viewer to check the Windows NT event log file for any messages like “Network Card Not Found.” Scan NT 3.1.1.5 One of the enhancements included in this version is License Plate Inventory (LPI) functionality. LPI contains a set of applications to collect license plate data, manage the LPI database, and maintain the LPI inventory. These applications can execute on the same or different computers, provided they have access to Scan NT and the Scan NT database. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 297 Scan NT 3.1.1 The License Plate Inventory (LPI) feature will be included in the release of Scan NT Central Management System Version 3.1.1. The LPI feature for Scan NT is a set of applications designed to collect License Plate data, manage the LPI database, maintain the inventory, and generate reports. These applications can execute on the same or different computers provided they have access to Scan NT and the Scan NT database when needed. Included in the system is a Hand-Held Manager, which enables the user to do the following: *Detect whether a hand-held computer is connected to one of the serial ports *Move data between the Scan NT computer and the hand-held computer *Store information in the database tables The LPI administration and utility tools allow users to perform the following functions: *Access standard reports *Generate reports *Search for a license plate *Maintain a “Hot Plate” list *Manually reconcile inventory data *View the License Plate Inventory table *Edit global license plate parameters, *Configure the rows and spaces in a lot *Configure hand-held computers and serial ports *Maintain the locality list LPI looks up the inventory data as follows: 1. When Scan NT is started, the Lookup Manager starts to manage the instances of the License Plate Find module. 2. Upon request from a Fee Computer, the License Plate Find module looks up a license plate in the database and returns the results to the requesting Fee Computer. Scan NT 3.1.0.6 default user name and password not allowing access to ACS The default user name and password (administrator, fapd) may not allow access if you have Microsoft Access installed on your PC. Try using the user name admin and the password amcdot to gain entry. Scan NT 3.1.0 3M has released Bar Code Ticket Tracking as part of Scan NT Central Management System Version 3.1.0. This release includes an Issued Ticket Manager and a Validated Ticket Manager. The Issued Ticket Manager will allow users to display and print an Issued Ticket report that does one or more of the following based on the information in the Issued Ticket file: *Lists all active issued tickets *Lists selected issued tickets *Computes revenue for all issued tickets *Computes revenue for selected issued tickets 298 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual If the user chooses to select issued tickets, choices for selection criteria will include issue devices, ticket number ranges, or issue time ranges. The user will also be able to decide the ticket type to be included in the report as well as the selection conditions. After an Issued Ticket report is displayed, the user will be able to print the report. The Validated Ticket Manager will allow users to display and print a Validated Ticket report that does one or more of the following based on the information in the Validated Ticket file: *Lists all active validated tickets *Lists selected validated tickets Like the Issued Ticket Manager, the Validated Ticket Manager will allow the user to select criteria, ticket type, and conditions to define the report. However, with the Validated Ticket Manager, the user will have more criteria from which to choose. Both the Issued Ticket report and the Validated Ticket report will display the data in a multi-column table. Additional columns of ticket data may also be shown. Users will have the option to select which columns they want to have displayed on the ticket list screen. By default the ticket number, issue lane, paid time, total fee, and ticket type will be displayed. On the Validated Ticket report, a separate box will show the full details of any single selected ticket. Scan NT 3.0 3M is pleased to announce that Version 3.0 of the Scan NT Central Management System has shipped on schedule. Included in this release is Access Control, Security (password protection), sending to multiple devices, and Credential Files. The Access Control portion is the software bundle that relates to the Passport Plus Card Reader. It includes reader programming, reports, and reader communications. The Send to Devices function allows the user to send commands to multiple devices. The devices that are in this package are Auditor PowerPad Fee Computers, communicating barrier gates, Ticket Spitters, Exit Verifiers, and Passport Plus Card Readers. An important feature that has been added to Scan NT is the Security Package. This feature allows a user to setup and control who has access to certain functions and areas of the program. These areas are Scan NT itself, Security Administration, the Scan NT Agent, Count Configurations and Monitoring, Access Control Configuration, Access Control, Database Archival Scheduling, and the Event Control System. The final package in this release is the Credential File. “Credential” is a more encompassing term used to describe the previous term “ID Number.” A Credential may be an individual, a company, a vehicle, or any other parameter that describes that describes how the information is sorted. The Credential File is equivalent to the SCAN Facility Management System’s (DOS-based program) card log. The Scan NT Central Management System (Version 3.0) has been released and shipped to distributors and end-users who have order the Scan NT Subscription Plan. The Subscription Plan provides for one year of unlimited access to all technical updates of the software with a Not For Resale (NFR) CD-ROM. In addition to the NFR programs, nine sites are also receiving the program. These sites are in Louisiana, North Carolina, Tennessee, and Texas. 3M technicians will assist the Troubleshooting Manual 78-0060-4094-9, Ver. 1 ScanNet • 299 local distributor with the setup and installation of the software. Currently, we are working on the next release of the Scan NT System. Next versions and enhancements will be more frequent and smaller. For instance, Version 3.1 will feature Barcode Ticket Tracking, ValueCard, and Multiple Connections/Consoles. Version 3.2 will feature the Automatic Pay Station, License Plate Inventory, additional reports, and Multi-Level Security. Version 3.3 will feature the completed Event Control System, Internet access, ActiveX Controls, and Internationalization. Version 4.0 will feature Centralized Credit Card, the complete Accounts Receivable package, ValuePass, and Group Control. The open architecture of the Scan NT System has enabled 3M to contract portions of the software development to independent software developers. 3M and the Scan NT Team thanks each of these companies and individuals for their efforts to bring this product to market on schedule. Scan NT 2.0 Scan NT Version 2.0/Build 35 was released and the first thirty Not For Resale (NFR) programs where shipped to distributors across the country. Scan NT/Version 2.0 has the following functionality and the ability to: * Communicate with Auditor PowerPad Fee Computers, Model G- 90 LCD Series Barrier Gates, Model CG-90 Barrier Gates, SST Ticket Spitters, and SST Exit Verifiers * Send, pull, save, and create programming * Send commands * Pull, clear, and print 14 standard reports * Display messages * Provide counts and real-time monitoring 300 • ScanNet 78-0060-4094-9, Ver. 1 Troubleshooting Manual SST SST CPU DIP Switch Settings Switch number Open Closed Baud Rate 1 9600 default 19.2K Transport Type 2 All others HP4 Print Head Type 3 Rohm Gulton, Mitani Burster/ Parker Unit 4 Absent Present Burster In-feed Type 5 Dual Single Print Head Mech. 6 All others (motor) HP series (solenoid) Hole Punch Validations 7 Off On Function In Test Mode 7 Led pattern test Motor speed test Operating Mode 8 Normal Test Troubleshooting SST Equipment It doesn’t happen often, but technicians troubleshooting SST equipment have replaced known bad parts and a short time later the device exhibited the same failure. You may even notice a bad part actually damaging good test equipment. This is hard to troubleshoot because you don’t know where the defective circuit is and this particular circuit is intertwined between all the parts that complete the unit. These are some scenarios to be aware of: Bad SST CPU, may cause: * ICs to be damaged on the Burster or Parker * damage to Transport or Burster * damage to Omega Controller * the display to show “OUT OF OPERATION” * bad printing on ticket * bad read or write to the mag stripe * a good Transport to seem bad when it is not Bad SST CPU Breakout Board, may cause: * bad physical printing on the ticket * bad encoding or writing to the ticket * bad reading of the ticket Bad Omega Controller, may cause: * damage to the SST CPU communication circuit Bad Burster or Parker, may cause: * damage to the SST CPU Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 301 Bad Transport, may cause: * damage to SST CPU * damage to SST CPU Breakout Board Remember that your cables are also suspect when troubleshooting a system, but they are not known to cause damage to parts if they are bad. If you have already swapped individual parts of the system with no success, you may need to replace all parts in the system like the Transport, Burster, SST CPU and SST CPU Breakout Board in order to rule out damaged parts. If you change all parts at one time and the system works correctly, it may be best to have all of the old parts serviced to protect your test equipment and prevent other system failures when using this equipment. Most of the time, the SST CPU will be the main culprit. This article is designed to help you identify related equipment and what parts need to be replaced and serviced depending on failure. For example, if a Transport is not physically printing on the ticket, only the Transport, SST CPU, or SST CPU Breakout Board should be suspected. The Burster or Parker could remotely be responsible if during ticket travel, the thermal print surface of the ticket is scratched or damaged in any way. The Omega controller is not involved in Transport printing, so if the failure is the Transport not physically printing on the ticket, the Omega controller should not be sent in for repair. SST Ticket Spitter display showing "NOT IN OPERATION" Getting a “NOT IN OPERATION” message means that there is no communication between the SST CPU and the Omega controller. This can be due to one of these problems: 1. The Omega is not communicating to the SST CPU because of a bad communication circuit. 2. The SST CPU has a malfunctioning communication chip. 3. The cable between the SST CPU and the Omega controller is faulty or unplugged. The part number for the cable that connects the two together is 91-4670. Swap components with known good components and send bad equipment in for repair. Differences Between Paid and Unpaid Grace Time Paid grace time is the time it takes the patron to exit the lot after paying for a ticket at a central Pay Station or PowerPad. If the patron does not exit within the allotted time frame, they will be directed to a cashier or charged according to the programmed repay ticket fee number under SST Ticket Spitter programming. Unpaid grace time is the time a patron enters a lot, decides that they no longer want to park in the lot (could be full) and leave without paying by inserting their ticket at an exit PowerPad, Exit Verifier, or Automatic Cashier Terminal. When a patron exits within unpaid grace time by inserting the ticket into the device, the transport will print the date and time of the grace exit, and also print “Exit In Grace” on the ticket. If the ticket is manually entered into the PowerPad because it was unreadable, the printer does not validate the ticket like a normal fee generating transaction would, but it will automatically vend the gate, and print on the journal tape of the PowerPad “Exit Pass 302 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual Accepted” along with the date and time, and the exit pass number. You can change the programming to also validate lost or manual tickets by changing unpaid grace time programming to 0 under Programming>System Preferences>Grace Time>Unpaid grace time and include the grace time within the fee table itself. This way there will be a $0.00 fee generated, and the PowerPad will ask you to insert a ticket so that it can be validated. SST HP-1 and SST HP-4 Transports Improved to Increase Life of Print Head The guide pin cap (part number 80-19624) has been moved 0.015” upward allowing a credit card to pass beneath the thermal head without scraping the print element. This will prevent premature print head failure. A new HP-1/HP-4 preventative maintenance and repair video (part number 11-25238) is available that shows how to make this and other repairs. Contact Product Support at 877-777-3571 for more information on obtaining this video. Fix For Abnormal Display You can fix this issue by upgrading the firmware and performing a hardware upgrade. Follow these steps to fix the display issue: 1. Upgrade the firmware to C3.1.8 for standard SST, and C3.2.2 for VC/CC SST equipment. 2. Replace the 6.8 micro farad capacitor (part number 11-6065) on Pins 1 and 2. This capacitor is electrolytic, so the positive side must go to pin 2. This is the capacitor that we had people remove in an attempt to fix the issue the first time. This capacitor is needed to stabilize the power supply. See diagram. 3. Solder a new capacitor (part number 11-25206 – 1000 PF 10% 100V) onto the display from pin 1 to 6 for the SST Ticket Spitter and SST Exit Verifier only. This suppresses noise spikes on the enable line. See diagram. Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 303 4. You must use the short length flat ribbon cable (part number 82-20504 Cable Assy, SST display flat Ribbon 16 pin). The cable that we previously used causes noise on the display, and cannot be used in this application. Contact Customer Service for pricing and availability. The wrong cable for the SST Omega driven devices is part number 81-19436, the original round cable. Note this fix is for SST Omega driven devices only, and the 1000 PF capacitor and flat ribbon cable is not for PowerPad driven devices like the ACT, APS, or Credit Card Exit Verifier. PowerPad driven devices need the 6.8 micro farad capacitor and the round cable part number 11-3244. SST Media Specs The SST AutoRead System offers monthly access control and ValueCard utilities with the SST Ticket Spitter and the SST Exit Verifier. Extensive testing has provided detailed information on what type of media may be used with the different Transport mechanisms to yield the best results in terms of performance. When using the SST/HP-1 Transport, paper tickets or 10 point (.010 inch) polyester cards can be used to create monthly cards or ValueCards. Thicker stock is not acceptable and may create errors when reading the data encoded on the magnetic stripe. This, in turn, may create a greater frequency of unreadable tickets or cards. Paper ticket stock should only be used to create a ValueCard if the pass is designed for a one-shot application. If the customer demands a thicker card for monthly access, we suggest the SST/HP-4 be used. The SST/HP-4 Transport will accept cards of credit card thickness and allows for four-way insertion of the card. Cards made of thinner stock (such as the 10 point ValueCard) may also be used with these Transports. It is important to note that random encoding errors created by a single Transport in the system will disable the card’s use throughout the system. Ensuring that the “Verify Write” feature is activated can minimize the effect of random encoding errors. Specifications for the tickets/cards used in the SST System are: SST/HP-1 Paper Ticket (All Transport (10 pt Transports) ValueCard) SST/HP-4 Transport (Credit Card Size) Size 2.125" x 3.375" (54mm x 85.7mm) 2.125" x 3.375" (54mm x 85.7mm) International Standard: ISO/IEC 7810 (Identification Cards, Physical Characteristics) Thickness 0.0073 in. (7.3 mill) 0.010 in. (10 mill) International Standard: ISO/IEC 7810 (Identification Cards, Physical Characteristics) Stock Thermal 10 pt Polyester International Standard: ISO/IEC 7810 (Identification Cards, Physical Characteristics) Magnetic 1/4" (standard), 1/4" (standard) International Standard: ISO/IEC 304 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual Stripe 1/2" (available) 7810 Version 12 Transport Repairs PC boards used in the SST Transport Version 12 or earlier versions are no longer available. As of December 1, 2001, the SST Transport Version 12 and prior versions will be repaired on a “best effort” basis (as parts are available) and Transport versions prior to 12 will no longer be upgraded to Version 12. As Version 12 SST Transports come in for repair they will be evaluated in a timely fashion as to whether or not they can be repaired. The customer will be notified if the unit is unable to be repaired and will be given the option to replace it with an HP-1 Transport at a special pricing discount. The special pricing discount is $1,700.00 net which includes the SST HP-1 Transport Assembly, CPU Board, and the Update Kit. The original unit will not be returned. Only complete Version 12 Transports that are not repairable are eligible for the special pricing discount on an HP-1. SST HP-1 Versus SST HP-4 1. HP1 breakout boards that are piggy-backed onto the SST CPU have a voltage regulator and a transistor on them with 3 resistors and one cap. HP1 breakout boards do not have the 4 LED's or the 7406 IC chip that the HP4's have. 2. HP4 breakout boards have a 7406 IC chip and 4 LED's, which make sure that all the read heads are active. You can't use an HP4 breakout board on an HP1 because it doesn't have the flux detection circuit. Always make sure when working with Version 8 - 12, when updating the transport to an HP1 or HP4, you must install the respective breakout board, otherwise you will damage your SST CPU which will result to hundreds of dollars in repairs, or an un-repairable state. Make sure that you also change your dip settings to reflect your changes. Your SST CPU has to be C1 or higher. Setting Low Ticket Number in SST Spitter Under Programming SST Spitter, Set Low Ticket Num. This number doesn't move. That is because this is the ticket number [defined by the SET TKT NUMBER] that will cause the spitter to send the LOW TICKETS message to scan For example: I set the LOW TKT NUM to 10, and start with ticket # 0, I was able to spit 9 tickets without any message at ScanNet. When I spit the 10th ticket, the message in red: LOW TICKETS appeared at ScanNet. If you have 5000 tickets in your box of tickets, and you set the LOW TKT NUM to 4500, you will get a LOW TICKETS message at ScanNet if the ticket number that the box starts with is ticket number 0.[defined by the SET TKT NUMBER]. If you go into your Spitter, and the current SET TKT NUMBER is 35467, and you put a new box of 5000 Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 305 tickets into the spitter, you have to take out the remaining tickets, install the new box, and set the new LOW TKT NUM to 35467 + 4500 = 39967 [If you want to be alerted once the Ticket Spitter only has 500 tickets left in it.] Take into account how many tickets can be spit in one very busy day, because it may take a manager a whole day to get over to the Ticket Spitter to reload the tickets. You will only get this message once, when the ticket number has been reached. Another Example: When I set the LOW TKT NUM to 1 I got a LOW TICKET message at ScanNet the first time I spit a ticket If the starting SET TKT NUMBER is 0 or otherwise. If the LOW TKT NUM is programmed to be lower than the existing SET TKT NUMBER, the first time you spit a ticket after programming, the message LOW TICKET will appear at ScanNet. SST Re-encode Option for Ticket Spitters Do you want to re-encode the SST Ticket to automatically default to a fee table other than the default fee programmed at the PowerPad? This example refers to a fee table that is a little higher because the Patron uses valet parking after entering the lot with a ticket from the ticket spitter. Here's how to program: 1. In ScanNet go to Programming SST Ticket Spitter, and pull programming from the spitter. 2. Under Repay ticket fee #, put the number of the fee table that you want the ticket to refer to once it has been validated. (this is explained further below) 3. Send the programming back to the device. 4. In ScanNet go to Programming Auditor PowerPad, and pull Fee Tables programming from the PowerPad. 5. Make the default Fee Table's Grace Time is long enough for the ticket to be validated within grace so no fee is generated. The time it takes for the parking patron to receive the ticket from the spitter and give it to a valet parking employee to validate it has to be considered. The time the patron has to wait in line has to also be accounted for. 6. Make sure that the fee table that the spitter is programmed to use for Repay is programmed at the PowerPad. 7. The PowerPad that the valet parking employees use has to be in central cashiering. 8. The PowerPad that the final validation occurs on should be in Exit Cashiering in order to take the issued ticket off the issued ticket stack. Here's how it works: 1. The Patron enters the parking lot with a transient ticket. 2. Pulls up to Valet parking, and hands the ticket to the Valet parker. 3. The Valet Parker inserts the ticket into a central PowerPad SST Validator, and the fee $0.00 comes up, and he hits the cash key. 4. The ticket is validated, and put in the car for the Patron to exit with at a later time. 5. The patron returns for his or her car, and after receiving it will also be presented with 306 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual the ticket that the Valet Parker had validated in his central PowerPad SST Validator. 6. The patron can use this ticket in an ACT, automatic cashier terminal, or at an exitcashiering PowerPad SST Validator. 7. Once the ticket is inserted into either the ACT or the SST Validator, the PowerPad will automatically recognize the new default fee for repay. On the PowerPad display at the top left, the fee table will display the new fee (FX). 8. The Patron pays for their stay, and exits the lot. Fastest Ticket Issue Speed Pre-Issue and Pre-encode are the fastest settings for ticket issue speed. Both of these settings are actually the same setting in that they both burst the ticket and position the ticket just behind the Read/Write head of the Transport. When a car is present on loop A, it will encode the ticket and wait for the patron to press the Ticket Issue Button. The ticket is still inside of the Transport at this time, just on the other side of the mouth of the Transport. If the patron backs out of the lane and doesn’t press the Ticket Issue Button, the ticket will be repositioned inside the Transport, and be once again, parked just behind the Read/ Write head. Park-Issue is the second fastest. This setting will burst the ticket and park the ticket in the burster. When the patron presses the Ticket Issue Button, it will travel through the Transport, be encoded and printed on, and then be issued to the patron. The Normal tickets setting is the slowest. This setting will wait for the patron to push the Ticket Issue Button before bursting the ticket, writing to the ticket, writing on the ticket, and then issuing the ticket to the patron. Number Function Switch Position 4 Normal tickets Open 4 Park-Issue tickets Closed 4 Pre-Issue tickets Open 4 Pre-Encode tickets Closed 5 Normal tickets Open 5 Park-Issue tickets Closed 5 Pre-Issue tickets Closed 5 Pre-Encode tickets Open Transient Facility Code Facility codes are used to prevent customers from using tickets that they might have received from a different lot. If you decide to keep 0 as the facility code (it is the default), it may be possible that the parking lot down the street uses 0 as their facility code as well. To protect your lot from foreign tickets, select a unique number for your parking lot’s facility code. The facility code in the first position is always the transient facility code (regular tickets). When you are using a ValueCard system, you should isolate transient Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 307 tickets from monthly tickets. 308 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual Facility codes in the second through sixth positions can be programmed to reflect the ValueCard facility codes programmed at the PowerPad. SST Tickets Stick Together When Issued Causing Jams Place a golf ball on the inside fold of the ticket stack after the tickets have been loaded into the Burster. The additional pressure should help separate the tickets and prevent sticking. Printing Small Fonts You can choose large print (24 characters) or small print (30 characters with the year printed on the ticket). HP-4 Transports can only print small print and must have DIP Switch #2 on the CPU closed. SST/HP-1 or pre SST/HP-1 Transports are DIP Switch programmable through the SST Omega Switch Bank #2, DIP Switch #7 (Open for small print; Closed for large print). You must have SST Omega software Version B2.1.0 or greater and SST CPU Version A3.9.3. For “B” Version Auditor PowerPads, you can program the print size under “Sys Preferences > SST > Small print.” You must have at least Version B2.2.1 firmware in the Auditor PowerPad and SST CPU Version A3.9.3. The small print option is not available with platform “A.” SST Merchant Validator 3M introduced the SST Merchant Validator, a non-powered, hand-operated device that allows merchants to offer time, fee and/or percentage discounts for up to 624 merchant accounts. The store attendant simply inserts the SST ticket into the mechanism, which encodes the merchant information via hole punch technology for the predetermined discount. Custom logo ink stamps are available with the device. When a validated, holepunched ticket is fed into an SST Ticket Validator or Automatic Pay Station with an SST/HP-1 Transport, the transport reads the ticket and the holes, and sends the appropriate data to an Auditor PowerPad Fee Computer (with a Voucher option). In addition to punching the tickets, the unit also stamps the code number on the ticket so that the attendant can enter the number manually. Each SST Merchant Validator is coded at the factory. Up to 999 different codes are available. A non-resettable counter is built into the unit for accounting control. The SST Merchant Validator option can be added to any SST site that is using the new SST/HP-1 Transport and a PowerPad with a Voucher option. Introducing the SST HP-4 Transport 3M introduced the SST/HP-4 Transport, a High Performance Transport that features four magnetic read/write heads. Two heads are located on the top half of the transport assembly, and two are located on the lower half - which allows the transport to read/write tickets inserted in any one of four ways. The remaining components are based on the SST/HP-1 Transport design. For instance, the print system uses the Mitani thermal print head, which mounts to a simple holder with an integral ticket driver. This holder Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 309 assembly is raised and lowered very quickly by a solenoid. The solenoid operation is the key to the unit’s speed performance (a ticket with a single line of print can be issued in approximately 1.1 seconds). The unique ticket diverter has also simplified the system. The diverter is responsible for sealing and opening the ticket channel when the print head is in the raised position. This is critical in order to prevent bent or mutilated tickets from jamming on the edges of the opening. The diverter design replaces the print fingers used on SST Transports version 12 and older. The SST/HP-4 Transport is capable of processing transient tickets, access cards, vouchers, and credit cards. Introducing the SST HP-1 Transport January 1999 marked the start of production of the SST HP-1 Transport—3M’s High Performance Single-Head Transport. The HP-1 Transport is the most significant redesign of the SST product line since it was introduced. Task Force Goals In designing the HP-1 Transport, the SST Task Force began with the following goals: * Improve the print speed performance * Improve reliability * Reduce the number of parts * Reduce the number of field adjustments * Improve the serviceability * Maintain compatibility with an upgrade path * Add the capability to automatically read hole punch validations Reduced Ticket Issue Time The time required to issue a ticket has been significantly reduced with the new high performance Transport. A radically new mechanical print system reduced the time to issue a ticket in the Pre-issue mode by over 40 percent. A ticket with a single line of print can be issued in approximately 1.1 second compared to approximately 1.9 seconds with the previous model. The print speed improvement also reduces the time to print PowerPad validation information for additional performance improvement at the exit lane. Fewer Parts, Fewer Adjustments, Fewer Repairs The engineers also focused on part reduction and simplification. The new print system completely eliminates the majority of components on the top half of the Transport. These parts include the DC print motor, print cam, print head position sensors, print head pressure springs, print fingers, and print slides. Removal of these components resulted in the elimination of the need for complicated field adjustments. The research conducted by the SST Task Force recently identified that the print linkage and print fingers eliminated from the HP-1 were the number one service repair issue in the previous model. The new print system uses the same thermal print head with minor mechanical modifications. The print head now mounts to a simple, but slick, holder with an integral ticket driver. This holder assembly is raised and lowered very quickly by a solenoid. The solenoid operation is the key to speed performance. However, the unique ticket diverter design was the breakthrough that significantly simplified the system. The diverter is responsible for sealing and opening in the ticket channel when the print head is in the raised position. This is critical in order to prevent bent or mutilated tickets from jamming on the edges of the opening. This was previously accomplished by the complicated print fingers that would spread open to 310 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual allow the print head to lower onto the ticket and then mesh closed when the print head raised. Hole Punch Reader System Added The removal and simplification of the print system opened up a lot of space on the top half of the SST assembly. This not only makes it easier to service, but it also made it possible to add new features. The Task Force took advantage of this opportunity by adding a new hole punch reader system. This is a simple optical reading system that enables a 4x4 hole punch code matrix, supporting up to 624 validation codes, to be read along with the magnetically encoded data all in a single pass of the ticket. In fact, up to four-hole punch validations can be read without any ticket reading delays. The best news is that this new capability is included standard with every HP-1 SST Transport. A new hand operated tabletop Validator will soon be available to create the hole punch validations. Compatibility Maintaining compatibility and providing an upgrade path always poses a challenge when re-engineering an existing product. A new adapter circuit board was designed to make the new HP-1 Transport with the radically different print system and all new hole punch reading system work with the existing CPU board. The adapter board is compatible with Rev D and upgraded Rev C CPU boards that also have the 26-pin connector (JP-1) present on the board. A longer print cable is required for the adapter board. Version 3.8.1 or higher software is required, and Dip Switch #6 allows you to select the original SST Transport or the new HP-1 (closed = HP-1). Single Infeed Burster: Version A 3M has been shipping Version A Single-Infeed Bursters since July of 1998. When installing one of these new Bursters, please note that both DIP Switches #4 and #5 need to be closed in order for the Burster to function. This is contrary to all other versions, which required only DIP Switch #4 to be closed. Also, you must have SST CPU software version 3.6.0 or greater to use the Version A Single-Infeed Burster. Sunlight and SST Transport Failure Sunlight can enter the Transport from the front or back depending on the angle of the sun and its alignment with each of these openings. In the July/August 1998 issue of Field Service Tips, we wrote about how the SST Validator enclosure was redesigned to prevent ambient light from entering the Transport. The louvered enclosures may still allow sunlight inside depending on how the Transport is aligned with the sun. If you find that during a certain part of the day, every day during a certain time of the year, the SST Validator seems to “lose” the ticket, this can be due to sunlight entering the Transport and “blinding” the infra-red optical sensors that “see” the ticket. One way to prevent the light from entering the back of the Transport is to create a shade for it. To reduce the amount of light entering the front, you can install a trim plate (part # 30-0139) on the Ticket Spitter. Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 311 SST Configuration Transport Version CPU Version CPU Firmware Version 8 C or D 9 C or D 3.4.0 or higher Gulton Printhead 10 C1 or D 3.6.0 or higher Clockless Generator, New PO5 Board 11 C1 or D 3.6.0 or higher Clockless Generator, New PO1 or PO2 Boards 12 C1 or D 3.6.0 or higher Clockless Generator, New PO1 or PO2 Boards HP-1 C1 or D 3.8.1 or higher HP-1 Breakout Board with JP1 Connector HP-4 C1 or D A4.0.1 or higher HP-4 Breakout Board with JP1 Connector Other Characteristics Rohm Printhead Omega LCD and SST Omega Standard - Circuit Board Redesigned The circuit board has been redesigned using surface mount components and flash memory. The flash memory eliminates the use of EPROMS and allows the firmware to be updated using a computer or laptop with the FlashProgrammer software (available from the 3M web site along with new firmware). Tactile switches and keycaps were replaced with a membrane keypad. The LCD display mounting hardware was removed. The PCB and enclosure are now procured as a complete assembled unit from the assembly house. Flash Omega Controller Beginning with revision K, the Omega LCD Controller no longer has a socketed EPROM. Firmware is instead stored in a Flash memory device on the circuit board, so you can load or update firmware via a serial connection from a computer with the FlashProgrammer program. The FlashProgrammer program, oload.bin file, flash firmware file and FlashProgrammer Instructions are available at the 3M web site on the Firmware Depot page. Flash files have a .FLASH extension in the Included Files column and show the IC Type as FLASH. You can tell at a glance that you have a revision K Omega by the membrane switches that replaced the previous push-button switches. SST Merchant Validator-SST/HP-1 versus SST/HP-4 Both the SST/HP-1 and the SST/HP-4 Transports can read tickets hole-punched by the SST Merchant Validator if the ticket is inserted with the arrow on top and pointing toward the Transport. Since the SST/HP-1 Transport will only accept the ticket if it is 312 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual inserted this way, the Merchant Validator (hole-punch) validation will always be read when the ticket information is read. However, since the SST/HP-4 Transport can accept the transient ticket four different ways (any direction, top or bottom), the Merchant Validator (hole-punch) validation will only be read if the ticket is inserted with the arrow on top and pointing toward the Transport. If the ticket is inserted in any other way the full fee will be charged. If this happens, the patron may cancel the transaction and then insert the ticket the correct way to allow the Transport to read the Merchant Validator (hole-punch) validation on the ticket to apply the discount. SST CPU Version A4.0.10 Mandatory Firmware Upgrade In July 2002, an enhancement to the SST CPU (Version A4.0.10) was released to initialize the print head to the up position and clear the print data register before applying power to the print head power solenoid. This changes the setup sequence and helps minimize damage to the print head. Some distributors are still operating under earlier firmware versions, and as a result, their print heads become damaged. If you continue to operate under earlier versions of software, and you send your Transport in for repair because of print head damage, your warranty may be voided. It is mandatory that all SST CPU firmware be upgraded to version A4.0.10 to prevent the warranty from being voided. Version A4.0.10 is available at the 3M web site. Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 313 What is the 24VDC Power Hookup between the SST CPU of the Validator and the PowerPad Power Supply? The SST CPU gets its 24VDC from the PowerPad power supply exit pass/XV trans connector, pins 5 and 6. Connections: SST CPU PowerPad power supply 2-------------------5 3-------------------6 SST CPU Firmware Compatibility SST CPU firmware versions prior to A4.0.9 cannot be used on an SST CPU Rev D1 or later board. The transport motor will not run. Version A4.0.9 is backward compatible with previous SST CPU board revisions however. 314 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual How can you adjust the print head for a HP-1 or HP-4 Transport? SST CPU 3/1999 3M has made the following changes to the SST CPU: * To enable Hole Punch Sensor reporting, you must now close Dip Switch #7. * You can now print up to 42 characters per line using the small font. SST Omega VC/CC C3.2.2 * If a patron inserts a ticket into the SST, and then pulls it back out causing a false start, the Omega will recover and re-issue a command to pull the ticket back in. Previously, the Omega issued this command only once and if the patron pulled the ticket back out, the SST would not attempt to pull the ticket in again. * Support has been added for the patron display. Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 315 SST Omega Standard C3.1.8 * Device time will now be reported properly in messages to ScanNet. * An “X” from a Crossover Verifier can now be requested to print on line 4 of the ticket instead of line 2. This option can be set using SW6 on DIP switch 2 on the terminal board. When closed, the “X” will print on line 2. When open, the “X” will print on line 4. * If a patron inserts a ticket into the SST, and then pulls it back out causing a false start, the Omega will recover and re-issue a command to pull the ticket back in. Previously, the Omega issued this command only once and if the patron pulled the ticket back out, the SST would not attempt to pull the ticket in again. * Support has been added for the patron display. SST Omega VC/CC C3.1.5 and B2.6.5 The SST Omega (Versions C3.1.5v and B2.6.5v) was enhanced to allow the Omega to recover and reissue a command to the SST to attempt to read a ticket again after a patron has quickly pulled it right after inserting it into the SST (before the SST has attempted to read it). SST Omega Standard and VC/CC C3.1.1 3M recently released an updated version of the SST Omega Controller (Version C3.1.1). Changes made in this version affect the standard Omega Controller and the ValueCard/Credit Card Omega Controller. The following changes affect standard Controllers: 1. A Cold Start no longer erases programming. 2. The proper year now displays consistently on the Patron LCD Display. 3. An “X” is printed between the fee number and the lane number on the second line of the ticket when a crossover Exit Verifier changes the fee number. The following changes affect Controllers with the ValueCard/Credit Card option: 1. A Cold Start no longer erases ValueCard programming. 2. An Issued Ticket message is no longer sent to ScanNet when a ticket is issued after a ticket jam. 3. The proper year now displays consistently on the Patron LCD Display. 4. The SST device now keeps ValueCards upon completion of the transaction when the value is decremented to the minimum value instead of upon the next insertion. 5. An “X” is printed between the fee number and the lane number on the second line of the ticket when a crossover Exit Verifier changes the fee number. SST Omega VC/CC C3.0.1 & CCEV B2.5.1 This version of the SST Exit Verifier and the Credit Card/ValueCard Exit Verifier (Version C3.0.1/B2.5.1) includes the following change: On units that have an SST/ HP-4 Transport, the message “Insert Card/Ticket” is displayed on the LCD instead of the 316 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual message “Insert Arrow First.” SST Omega Standard B2.2.0 3M recently released SST Omega Controller (Version B2.2.0). This new version included the following changes: * When SST Ticket Dispensers accept ValueCards and credit cards, “Push For Ticket” is displayed instead of “Insert Card.” * Support for the SST/HP-4 Transport has been added to the Omega SST Controller. SST Omega Standard B1.13.0 3M has released a new version of firmware for the SST Omega Controller. Version B1.13.0 will ensure that the SST Omega is Year 2000 compliant. SST Omega VC/CC B2.1.1 3M has released a new version of the SST Omega (Version B2.1.1VC/CC). This new version addresses some issues that were present in the previous version and adds some enhancements. For example, we: * Increased the maximum number of transient fee tables to 24 for both pay and repay modes. * Changed the time zone verification to reject a ValueCard upon exiting if its start date and time and the time zones indicate the user was in the lot during an invalid time for that card. * Added an “Exit Pass” bit for attendants to use when a ValueCard is rejected. * Modified the “Display Options” function under the Programming menu so that users can use the Up and Down keys to scroll through the options in either direction. * Changed the Fee Table Minutes field so that users cannot enter a value greater than 255 because the program is unable to store numbers greater than 255. SST Omega VC/CC 1.1.2 or Previous Losing ValueCard Programming If you have an SST Ticket Spitter that is programmed to accept the ValueCard (version 1.1.2 or previous) and have not made any changes to the configuration module Dipswitches, do not hold down the Menu button while powering up the Omega Controller. If you do, you will lose all ValueCard programming data. Field Wiring Troubleshooting for All SST Spitters with Push Button Test wiring versus operational wiring SST Ticket Spitters are wired for testing purposes, and may not be wired for operational use when it leaves its test environment. This testing wiring that is wrong for shipment is - Common of push button on B9 and N.O. on A11. The way it should be wired, correct for shipment is - Common of push button on B9 and Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 317 N.O. on B7. Spare terminal note On the G90-CD Gate, the backplane board has 2 places where inputs and outputs can be connected. One side is soldered directly to the backplane board, and the other side is a pluggable connector. If you take a Multimeter and measure across these two points, they should show as a short, because they are the same point. The exception to this rule is the point between the soldered-in side and the pluggable side of the B7 and B8 connectors are not connected. These two inputs are labeled as SPARE, and since they are not connected, there are actually four spare terminals. If you have a push button wired to B7, you have to connect the gate Ticket Request Input (A7) directly to the same terminal that you have the push button wired to. Be sure that when you are using your Multimeter to measure between the two input or output points on the backplane board you tighten down the soldered in side before measuring. There is a gap between the screw on the top of the connector, and the circuit board itself. By tightening down the screw, you are sure to close the connection. 318 • SST 78-0060-4094-9, Ver. 1 Troubleshooting Manual Troubleshooting Manual 78-0060-4094-9, Ver. 1 SST • 319 TagMaster How do I program the communication and Wiegand card format settings for the TagMaster AVI read head? Install the MagPass software you can get from 3M.com>FAQs>TagMaster AVI, and refer to the recommended settings in the installation document also available on the TagMaster AVI FAQ page. TagMaster Error in Labeling J5 We have found recently that the labels on the TagMaster read head is labeled differently depending if you have the earlier style TagMaster boards or later style TagMaster boards. Currently we are having our customer hook the input signal to J5 pin 5. Do not refer to IN3A, because in the later style TagMaster boards, there are two IN3A connections. TagMaster Wiring Details: The original TagMaster full view of connections. 320 • TagMaster 78-0060-4094-9, Ver. 1 Troubleshooting Manual This is the original TagMaster that we based our documentation on. This picture shows a close up of the labels on J5 and J6. This is the original TagMaster that we based our documentation on. This is how we have it connected up here in Novi. Troubleshooting Manual 78-0060-4094-9, Ver. 1 TagMaster • 321 As you can see, J5 is labeled differently than what is described in our documentation. J5 pins 5 and 6 are both labeled IN3C. You should use connector J5 pin 5. 322 • TagMaster 78-0060-4094-9, Ver. 1 Troubleshooting Manual TD-249 Lane Troubleshooting TD-249 Barcode Ticket Spitter and G-90 CD Gate You can use these notes to troubleshoot any problems with a TD-249 and G-90 CD gate lane. First, note which wire colors are going to which terminals on the TD-249 Ticket Spitter connection panel. Also note what wire colors are going to what terminals between the two connection panels. Each wire color you are using at the ticket spitter must be the same color wire used at the gate according to the following wiring diagram: Connection Panel for the Spitter: Connection Panel for the Gate: 5 A7 (Ticket Request Input) 7 A2 (gate vend) 8 A13 (gate common) 3 C4 (Ticket Issue Common) 4 D4 (Ticket Issue) Once you verify that all the wiring is correct, test the gate. During this test, ignore the Spitter completely. Do not pull the ticket, and let the buzzer go off while the ticket is in the throat. At the gate, take a piece of wire approximately 1 foot long to jumper terminals for testing to simulate different inputs to the gate. * Step 1: If you are not already in Base Mode 2, Sub Mode 3, put the gate in this mode. Place a gate door over loop A to simulate a car being on the loop. At the gate, you will notice that the LED under A on the Omega Controller has stopped blinking on T (tuning), and is now solid under P (presence). If you do not get this result, see G-90 CD/LCD FAQs Gate Loop Detection. * Step 2: Inside the CD gate, jumper A13 to A7. You will see the LED for input 7 come on while this contact is being made. This contact is only momentary, so you will short the two terminals one time and then remove the jumper. This is your ticket request, and by shorting this input, a ticket should be dispensed at the Spitter. Ignore the Spitter for now. * Step 3: Inside the CD gate, jumper A13 to A2. You will see the LED for input 2 come on while this contact is being made. This is also a momentary contact, and the jumper should be removed as soon as you see the LED light up. After the LED for input 2 lights up, the gate should start to raise. This is your gate vend B, and by shorting this point after shorting the ticket request, the gate will raise. If the gate does not raise, then the problem with the lane is in the Gate. Cold start the gate and repeat steps 1-3. Perform a cold start by holding the Monitor/Menu button down and turning the gate on while continuing to hold the button down until you see the words “monitor” and “menu” flashing back and forth on the display. If the gate still does not raise, perform a memory initialization by turning the controller power off and closing DIP switch 2 (service only.) Wait 5 minutes for the battery to discharge, and open the switch. Perform a cold start as described on page 3 in step 3. If Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-249 • 323 the gate still does not raise, go to monitoring/config/settings, and see what Base Mode Sub Mode the controller thinks it is in. If it is anything other than Base Mode 2 Sub Mode 3, then check how DIP switch 1 on the connection panel is set. It should be set as follows: DIP Switch Bank 1 1 - Closed 2 - Open 3 - Closed 4 - Open 5 - Closed 6 - Closed 7 - Closed 8 - Closed * 6, 7, and 8 should be kept closed in the G-90 CD gate so that it will display the correct Base Mode, Sub Mode in the ScanNet System Activity Monitor. If a DIP switch was not set correctly, change the DIP switch as shown in the example and perform a cold start as described on page 3 in step 3. Go to monitoring/config/settings again, and check the Base/Sub mode. If it is still not Base Mode 2 Sub mode 3, then you have any of these three problems: * The Omega is not recognizing the correct Base/Sub mode because of internal circuitry, that is malfunctioning. Replace the Omega controller. * The connection panel has a bad path between the config. module and the Omega controller. Replace the connection panel. * You have a malfunctioning config. module. Replace the config module with one that is working correctly. If you suspect that the config. module is bad, put the gate in No Config mode. To operate in No Config mode, set all the switches on DIP switch bank 4 on the connection panel to open. With the power off, take out the config module, and cold start the gate as described on page 3 in step 3. Go to monitoring/config settings, and see if the gate registers Base Mode 2 Sub Mode 3. If it does, then repeat steps 1-3 described above. If the gate still does not raise, replace the Omega controller with another one that is in a working gate, and then test the lane again. If the gate still does not raise, use the override switch to see if the gate will raise. If the gate raises, this proves that the mechanics of the gate are in working condition, and the controller is faulty for not sending the proper signal to the relay that controls the gate arm. If the gate still does not raise, go to menu/commands/raise gate. If the gate raises, it proves that all inputs and outputs are good. If the LED for Gate Up comes on, but the gate doesn’t raise, then the problem is one of the following: * The path to the input or output is malfunctioning. * The input or output relay on the controller is malfunctioning. * Both the Omega controller and the path on the connection panel are malfunctioning. Swap out suspected bad parts with known good parts to test thoroughly. Once you have the gate operating correctly, return to step 1 in the beginning of these troubleshooting instructions. If you still experience problems after verifying that the gate is good, the 324 • TD-249 78-0060-4094-9, Ver. 1 Troubleshooting Manual problem is in the spitter. Most of the time when there is a problem with a lane, the problem is going to be with the gate. Manual Issue If every barcode ticket issued is a manual issue ticket, most likely, the jumper from the Barcode Logic TB3 pin 2 (input-A) to the Barcode Power Supply TB2 pin 2 (input-A) is missing. If there are no jumpers between these 2 points, then every ticket will be a "manual" ticket. If there is still no improvement after installing the jumper and initializing the Passport Plus, the Passport Plus Barcode Logic may be faulty. Swap out this unit with another working unit to test. Tickets not Cutting Clean Cutter blades are self-sharpening. If the blades are dull from mishandling, request a factory exchange. More than One Ticket Issued There are two things to check 1. Check sending device or push-button switch for proper operation. If sensing device fails or push-button switch shorts, a second ticket may be issued after the first is pulled from the ticket slot. 2. Verify that the detector is properly tuned. If the detector is faulty, then contact customer service for repair. Issuing Long Tickets Check that both trigger springs are in place and the positioning lever is seated in the notch located on the Index cam. See the TD-249 manual for drawing description. Tickets Jamming in the Chute 1. Check cutter for proper lubrication. Verify that it returns to the down position. Lubricate moving blade and cutter link with machine grade oil. DO NOT LUBRICATE THE SOLENOID. See the manual for drawing description. 2. Check cutter return spring. Cutter must drop clear of chute. See the TD-249 manual for drawing description. 3. Check width of the ticket. Ticket width must not exceed 2 and 1/64 inches for AP, 2 and 33/64 inches for RC. 4. Verify that the Ticket Retainer Spring is shaped to contour of feed wheel. See the TD249 manual for drawing description. Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-249 • 325 Feed Motor Continues to Run/No Ticket is Cut There can be two solutions to the problem. 1. Your index switch has to be adjusted. On the inside of the index cam (the one with the three triangular notches), loosen the 2 bolts. Rotate the clutch assy. backwards by grasping the plastic wheel and making a very small adjustment (1/8 cm maybe), and tighten down the 2 adjusting bolts. To test if the adjustment made was good, hold in the solenoid assembly located by the clutch release arm, and manually turn the clutch assembly and make sure that the 2 positioning levers go into the triangular notches before it stops turning. If the clutch assembly is difficult to turn after adjustment has been made, you have turned the plastic wheel back too far. Loosen the bolts again, and readjust. The clutch should turn freely. 2. The Index switch is bad. See image for details on operation of switch. You should use a Multimeter to test for continuity. Ticket not Cut in Proper Location To adjust cut location, loosen Ticket Feed Adjustment Bolts. Make sure position lever is engaged in slot. Then rotate wheel forward or back to properly position the ticket at the cutter. Tighten the adjustment bolts securely. Time Stamp Gains Time and does not Match Hands on Clock Face No, you cannot fix this problem. The type section is improperly adjusted. Contact customer service for a repair or replacement. Time Stamp Loses Time or Stops First verify that power is on. If it is, the Type Section alignment with clock motor may be off. When the Type Section is in place, the spring wheel clutch should engage the drive wheel. If the spring clutch does not contact the drive wheel, space out the spring clutch with a flat washer. If the spring clutch applies too much pressure against the drive wheel, 326 • TD-249 78-0060-4094-9, Ver. 1 Troubleshooting Manual space out the clock drive with flat washers. See the TD-249 manual for drawing description. If this adjustment does not fix the problem, the clock motor may be defective. Contact customer service for replacement. Blurred Time Stamp on Tickets 1. Clean type wheels with small toothbrush. 2. Verify that Type Section is properly latched in place. 3. Check the Type Section Retaining Ring on Type Section hinge pin. It must be in place with the proper spacing washer. 4. Check condition of the ribbon. Replace if worn or if folding has occurred. Not Time Stamping Tickets 1. Check ribbon for proper positioning. 2. Time stamp plunger should slide up and down easily. 3. Check time stamp module. 4. Check clock switch. It should be "ON". Time Stamp is Weak or Doubled You should check the ribbon to see if it is worn. If the ribbon is good, check to see if the solenoid is malfunctioning. The plunger could be bouncing causing a doubled looking stamp. Prevent Ticket Jams Caused by Patrons Blocking Ticket Throat If you have a TD-249 Ticket Spitter with an extended length ticket option, a handy new product is available just for you. The product, called a “Diverter Hood,” was designed to prevent ticket jams caused by patrons holding their hands over the ticket throat while the ticket is being issued or by patrons pulling tickets out sideways. Both scenarios transmit pressure to the feeding ticket and cause the sprocket holes on the ticket to tear causing the next ticket to jam. If you experience this situation, the Diverter Hood from Southland Printing can provide a solution. This part replaces the front panel trim plate (part #300139) and extends the ticket downward. Because of the way the product is designed, patrons can only pull the tickets downward instead of sideways, and the ticket is Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-249 • 327 protected until it is fully extended. Our tests show the product works great. It comes with tamper resistant mounting hardware and can be ordered from their part #DH-1. Not Cutting Tickets Completely/Tickets Folding Over Blade If your TD-249 Ticket Spitter is not cutting tickets completely, or if the tickets are folding over the guillotine blade instead of being cut, try the following procedure instead of replacing the cutter blade. Looking straight into the Ticket Spitter head, remove the left side mounting screw for the (fixed) upper cutter blade. Install a washer .582 x .260 x .005 (31-0505) between the frame and the cutter blade. Reinstall the mounting screw and test. Installing an LCD Display 3M recently revised the Bar Code Ticket Spitter to allow installation of an LCD display. Now, if this Ticket Spitter is equipped with an LCD display, the date and time will be displayed on the first line and the version number and version date will be displayed on the second line. When a ticket is issued, or manually swiped, the second line will display “Entry/ Entrada” for about three seconds. Ticket Delays If you are using the TD-249 Ticket Spitter with a Model G-90 Series gate, one reason you may be experiencing delays is because the capacitor in the One-Ticket Package (OTP) circuit needs to be replaced. The 100uF capacitor should be changed to a 150uF capacitor. Using the Recall Key on the PowerPad During Processing A manager at a parking garage calls and says that a customer has been in the facility for only a few minutes and the Fee Computer is charging too much. The lot has a Bar Code Autoread System (with Bar Code Ticket Spitters at the entry, Bar Code Auditor PowerPad Fee Computers at the exit), communicating to a remote SCAN Facility Management System (with Ticket Tracking) to which you do not have immediate access. As you drive to the site, keep in mind what is functioning: the Bar Code Ticket Spitter is 328 • TD-249 78-0060-4094-9, Ver. 1 Troubleshooting Manual sending data to the SCAN System, and the PowerPad is calculating a fee. When you arrive at the site, pull a ticket and have an attendant process the transaction. Press the Recall key to get a detailed description of how the PowerPad arrived at the calculated fee. Compare the printed time and date on the ticket to that of the electronic entry time shown on the Fee Computer record. Aha! You notice that the ticket you just pulled shows a time as a year ago. You observe the attendant transaction and the printed entry time does not match the electronic time in SCAN, resulting in a miscalculation. If you have a Hand Held Computer with you, program and synchronize the Bar Code Ticket Spitter Logic Module time/date with the Fee Computer as soon as possible. That’s not all. Check that an errant command has not been sent and that the Port Controller is updating the Logic Module with the correct time and date. Repeat pulling a test ticket and verify proper fee calculation. If this still does not fix the problem, you may have duplicate tickets in your issued ticket stack, and you need to clear these old tickets out in order to have the system functioning properly again. If you have duplicate tickets in your issued ticket stack, you will get an “error 1000 integrity constraint violation” in your ScanNT log followed by an “error 4503 error adding ticket XXXXXXXXXXXXXXXX to issued ticket stack” Version A3.3.1 3M recently enhanced Passport Plus to give users the option of disabling the Bar Code Ticket Spitter ticket number assumption on bad reads. If DIPswitch #7 is open, the Ticket Spitter will not assume a ticket number on a bad read. Instead, it will ignore the read. This allows tickets to be manually swiped at a Bar Code Ticket Spitter. If DIPswitch #7 is closed, the Ticket Spitter will assume the ticket number on a bad read and send that number to ScanNet in a Ticket Issued message. Closed is the default setting. Version A3.3.0 3M recently released a new version of the Bar Code Ticket Spitter (Version A3.3.0). This new version includes the following change: The Bar Code Ticket Spitter will now process tickets with the number of digits from six to eight. Previously, it could process tickets with six-digit numbers only. The maximum ticket number support by the Bar Code Ticket Spitter is 16,000,000. Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-249 • 329 330 • TD-249 78-0060-4094-9, Ver. 1 Troubleshooting Manual TD-300 Series Firmware Upgrades 1.5.2.4 to 1.5.3.1 To correct the situation that caused random TD-320 Mag encode failures, the uninitialized configuration register has been fixed. The barcode unit takes longer than the TD-310 to power up. As a result, the barcode unit was not recognizing the configuration strings sent by the TD-310. A delay was added to the TD-310 to wait for the barcode unit to power up before sending the configuration strings. Note: This version requires the latest TD300 mag file. All Mag Encoder boards must be updated. 1.5.1.1 to 1.5.2.4 The in-feed and staging motors are now controlled by a position loop. This provides for a tighter tolerance when cutting the ticket at the tabs. The time-outs were shortened to further limit the damage caused by extensive ticket jams. This version of firmware should only be used with mechanisms containing 1 in-feed sensor. Menu #15 allows you to choose between 1 and 2 sensors—the default setting is 1. 1.5.0.10 to 1.5.1.1 Ensures that tickets are consistently and accurately cut on the perforation. Menu selections on the Programmer screen must be configured before loading tickets to determine which mechanism is being loaded. The original mechanism used a rotary cutter and two sensors (menu #14 = 0, menu #15 =2). The latest mechanism uses a guillotine cutter and one sensor (menu #14 = 1, menu #15 = 1). 1.4.6.1 to 1.5.0.10 The TD-300 Series transport has been enhanced to support a guillotine type cutter, which replaces the rotary type originally used. This enhancement is supported in firmware via two new programming menus. Menu #14 allows toggling between the rotary cutter “0” and the new cutter “1.” Menu #15 allows toggling between using 1 sensor (used with the guillotine cutter) and 2 sensors (used with the rotary cutter). The firmware is backward compatible with older mechanisms; however, new mechanisms will require this firmware to operate. 1.4.5.2 to 1.4.6.1 Added contingency scenarios for encoder failure. Slows mechanism down so that ticket cutter sensor will see the gap between tickets every time. Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-300 Series • 331 If a failure occurs, the transport mechanism will shut down after a 3 second time out period. 1.4.1.2 to 1.4.5.2 Under certain circumstances when a ticket jam occurred, the Infeed motor continued to run. This new revision software all motors now will shut off after a time out period. Added a menu option to the programmer that will allow the user to program where the ticket cutter will cut the ticket. 1.2.0.2 to 1.4.1.2 Bar code now reads ticket while it is in motion Infeed motor moves at a constant slow velocity Pulsing cutter enable line to prevent overheating of internal resistor Fixed intermittent problem with duplicate ticket numbers being sent to ScanNet 1.1.3.4 to 1.2.0.2 No longer using brake and friction to determine where the ticket will stop in the throat. The ticket is now precisely controlled when entering the throat area. Boot and application version numbers are now displayed ion the hand held programmer. 1.1.2.2 to 1.1.3.4 Ticket type for back-out and assumed tickets wasn’t being sent to ScanNet correctly causing no ticket type to be listed in Issued ticked manager. This has been fixed. Software version number of the programmed flash in the TD-300 can be viewed on the TD-300 programmer display. 1.1.1.1 to 1.1.2.2 Ticket number for Mag applications can only be 6 digits. Modified programmer so only 6 digits can be entered in for the issue ticket number. When setting the low-ticket count number to 99,999 (its maximum value), the number immediately changes to 34,463, and then decrements correctly as each ticket is issued. The number now decrements correctly from 99,999. 1.1.0.1 to 1.1.1.1 On power-up or reset, the programmed parameters return to the default values. Both the application and boot flash programs must be updated. 332 • TD-300 Series 78-0060-4094-9, Ver. 1 Troubleshooting Manual 1.0.0.12 to 1.1.0.1 The TD-300 series ticket spitter now supports downloading of firmware through the debug port on the controller board via a laptop PC. Flash program files and user manual is posted on 3M “firmware Depot” web page. Supports large and small printer fonts. This is a programmable item (item 12 on the programmer). The default is large font. 1.0.0.11 to 1.0.0.12 Ticket would intermittently be issued too close to the edge of the ticket throat and fall out. This version fixes this problem. 1.0.0.11 Initial release of TD-300 series Tickets Jam Before Rotary Cutter If you take a flashlight and look inside of the metal encasing of the ticket cutter, you will see 2 tabs that you can adjust by using a screwdriver and sliding them back and fourth. These 2 tabs have to be aligned exactly over the top of the perforated ticket edge. If they are not, then the tickets will jam just before getting cut. These 2 tabs keep the ticket straight before and after the tickets are cut. Tickets Shoot Out Spitter and Appear to be Ripped, Not Cut There is a sensor located by the ticket cutter, which senses the gap between each ticket. When this sensor sees this gap, it sends a signal, which cuts the ticket. If this sensor is either faulty, or dirty, it won't be able to sense the ticket, therefore advancing "one long ticket" as far as the spitter is concerned. Because the spitter works so fast, the spitter mechanism works like a burster, breaking the tickets apart before spitting them onto the ground. One Motor Continues Spinning With no Ticket in Mechanism This is an indication that you have a bad shaft encoder. There are three shaft encoders in all of the TD-300 series ticket spitters. If there is play in the shaft (the shaft can be slid Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-300 Series • 333 back and forth), then the shaft can push through the encoder, causing damage to it. With the use of an E-clamp and a wave-washer, you can reduce play. No Printing on Ticket There is a thumb screw located under the print head of the ticket spitter that can be adjusted. By turning this screw, you can press the ticket closer to the print head, or increase the gap between the print head and the ticket. You may add some Loctite to the thumbscrew in order to make it sturdy after adjusting it. There is also a ribbon cable that may be plugged in backwards if you still are not getting satisfactory results after adjusting the thumb screw. You may also want to make sure that you are printing on the non-thermal side of the ticket itself. The print should be right on the edge of the ticket, and right next to the magnetic stripe. The other thing to look for is that there is a ribbon cable behind the print cartridge that may be pushing the cartridge out too far. Make sure that the crease in the ribbon is as flat as it can get, so that the print head is making full contact with the ticket. Service Mode Tickets do not Vend Gate at PowerPad Exit Tickets issued in Service Mode in the TD-300 Series Ticket Spitter will do everything but vend the gate when someone tries to use them at an exiting device like a PowerPad. In this mode, various maintenance and service functions are performed and tickets are not issued to patrons, which makes this mode non-standard. A service ticket is issued by switching the Ticket Spitter into the Service Mode from either the Display Mode or the Programming Mode. Switch the Ticket Spitter into the Service Mode by holding down Button 3 and Button 4 simultaneously for at least 1.5 seconds. After switching the Ticket Spitter into the Service Mode as discussed above, the attendant presses the “Push for Ticket” button. The Ticket Spitter issues a Service Ticket with a Service Identifier printed on it and an alarm sounds. A Service Ticket message is sent to ScanNet if the Ticket Spitter is online. The attendant removes the Service Ticket from the Ticket Spitter and the alarm ceases to sound. A vend signal is issued from the Ticket Spitter to a lane control device, such as a gate, where the gate will raise on the way in, but if this same ticket is used at an exit device like a PowerPad it will not vend the gate. It essentially puts the PowerPad in tutor mode. 334 • TD-300 Series 78-0060-4094-9, Ver. 1 Troubleshooting Manual Cap on Thermostats TD-300 Series Ticket Spitters come equipped with a local heating assembly that keeps the printhead at an optimal temperature. At 30 degrees F the thermostat will turn on. When the heater is on, you will measure no voltage across the thermostat. At 45 degrees F, the thermostat will turn off the heater. When the heater is off, you will measure 24VDC across the thermostat. At room temperature, the heater should never be on. The thermostat is malfunctioning if it comes on at room temperature or if it doesn’t come on at 30 degrees F. You can fix this problem by checking if the cap on the thermostat is pressed on completely. There is a plunger on the inside of this cap that makes contact with the other side of the thermostat, and if it cannot make contact, the thermostat will not be able to shut off. By pressing the metal cap and the thermostat together, you will be able to fix the thermostat that controls the heat for the print head. Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-300 Series • 335 Using LEDs to Test Sensors with the Guillotine Type Cutter You can use the LEDs on the TD-300 Motor Driver Board to Test Sensors with the Guillotine Type Cutter. With no tickets in the TD-300 mechanism, LEDs SNR2, PWM1, PWM2, PWM3, DIR1, DIR2, and DIR3 should be on. *Note: Disregard the LEDs for the encoder status. These LEDs are E1CA & E1CB, E2CA & E2CB, and E3CA & E3CB. The LED pattern for all encoders is determined by the point in the encoder cycle. The following scenario uses one ticket for testing purposes: When the ticket is inserted into the mechanism, the first sensor it reaches is the feed sensor. When a ticket is in front of the feed sensor, SNR2 should turn off. When the ticket clears the feed sensor, SNR2 should come back on. *Note: If you are using a string of tickets, SNR2 should stay off. When the ticket reaches the queue sensor, SNR3 should turn on. As the ticket is printed, the printer sensor SNR5 should blink on and back off. As the ticket enters the throat, SNR6 should turn on and stay on until the ticket is either retracted or pulled by the patron. *Note: Ticket retract time, program variable D08 on the TD-300 programmer, should be set to at least 5. D08 should not be set to zero (0) unless you don’t want the ticket to be retracted. There is no default setting for the retract option. Transport Enhanced to Support Guillotine Type Cutter The TD-300 Series transport version 1.5.0.10 has been enhanced to support a guillotine type cutter, which replaces the rotary type originally used. This enhancement is supported in firmware via two new programming menus. Menu #14 allows toggling between the rotary cutter and the new cutter and Menu #15 allows toggling between using 1 sensor (infeed only) and 2 sensors (infeed and cutter). The firmware is backward compatible with older mechanisms; however, new mechanisms will require this firmware to operate. Remove the tickets from the Transport before upgrading to the new firmware. Use the table below to program the TD-300 Ticket Spitter: Earlier (Rotary New (Guillotine Menu Cutter) Cutter) 14 0 1 15 2 1 LED Display Board Rev B Versus Rev C If you are using the LED display board revision B and want to upgrade to revision C, note that the polarity for power is reversed in revision C and you must change the P3 power connector to the following: Pin 1 = +24V Pin 2 = ground If you do not make this change before upgrading from revision B to revision C, you will damage the new revision C board. 336 • TD-300 Series 78-0060-4094-9, Ver. 1 Troubleshooting Manual Signs Replaced by Symbols The TD-300 Series Ticket Spitter was first released featuring a white plastic “Please Take Ticket” sign that was lit from behind. That sign was then replaced by a simple gray “Please Take Ticket” sticker that is used on the SST Ticket Spitter. 3M no longer applies a “Please Take Ticket” sticker to the side of the TD-300 Series Ticket Spitter. Instead, we have implemented new universal graphical symbols in place of signage for the TD-300 Series Ticket Spitter. The picture on the push button shows an international push for ticket symbol. This minimizes language options in our product line, making it universal. The signs that will be eliminated are “Please Take Ticket” located on the side of the Ticket Spitter hood, “Push for Ticket” located on the button that you press to obtain a ticket, and “Lot Full” located on the front of the Ticket Spitter. If a customer needs the instruction on the side to take a ticket, it will be ordered as a separate line item and sent separately. The part number for the English “Please Take Ticket” sticker is 30-11247. When these push buttons were first introduced, they were round, but shortly, the shape will change to square for aesthetic reasons. In the near future, we will be implementing the new square buttons and the universal graphical symbols in the SST Ticket Spitter product line. Notification will be sent when that takes place. Hardware Changes To correct weather related problems based on field observations, the following enhancements were implemented: The weather stripping scheme for the hood was modified. A ground wire was added from the transport to the cabinet. The thermostat that controls the main heater was moved. Ticket Deflector Introduced The switch to the guillotine cutter exposed a small area above the cutter that could allow a curled ticket to escape and not be captured by the ticket guides. This caused the ticket to not be issued, and required a service person to clear it out. To correct this situation, a new part (30-25363, Ticket Deflector) was added to the TD-300 series transports. This small metal tab helps to direct tickets into the ticket guides as they exit the guillotine cutter. Better Patron Access to Ticket A thumb notch has been added to the TD-300 series ticket trim plate to provide patrons with better access to the ticket when it is issued from the TD-300 series Transports. Change Prevents Lost Springs The spring notches on the printer mounting bracket (P/N 30-12533) have been changed to slots to prevent loss of springs during operation and service. Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-300 Series • 337 Quality Control Checklist This checklist is used by Quality Control to ship the TD-300 Series Ticket Spitter. Make sure shipping the TD-300 has not disturbed any of the items in this checklist. 1. TD-300 Part Number 32-12592 TYPE 2. TD-310 Part Number 32-12593 3. TD-320 Part Number 32-12594 1. Three motor drive pulleys secure 2. Four large belts tight 3. Three motor belts secure 4. Three encoder caps secure 5. Belt alignment placement correct GEARS AND BELTS 6. Make sure that all of the screws/nuts that hold the ticket guides to the side panels are in place. Make sure there is no free play in the three large drive pulleys. 7. Check that the underside of the three large drive pulleys are not contacting anything CABLES AND WIRES 1. Sensor cables not broken 2. Lower optical sensor (on bottom of unit) cable not broken 3. All wires secure with tie wraps 4. Encoder wires not broken 5. Motor wires secure at controller board 6. Wires are routed properly (not in ticket path or contacting rotating shafts) MOTOR 1. Four motor screws secure on all three motors 2. Motor belt pulley secure 3. Motors turn easily by hand PRINTER 1. Ribbon included 2. Two springs present 3. Print ribbon cable secure in PC board and print head SCANNER (TD-310 ONLY) 1. Four mounting screws tight 2. Cable and connector in place 3. Washers on top two screws (inside) MAG ENCODER (TD-320 ONLY) 1. Mag encoder board secure 2. All wires on mag board secure 3. Mag head moves freely in holder OVERALL APPEARANCE 1. Serial label 2. E-clips and washers on pulley shafts (clips in grooves) 3. All pan head screws checked with hand screw driver Hecon Twin Cutter Enhancement To prevent the Hecon Twin Cutter motor from burning out in the event that multiple tickets enter the cutter section, the following enhancement has been implemented: 338 • TD-300 Series 78-0060-4094-9, Ver. 1 Troubleshooting Manual * The Smart Cutter board assembly is now mounted to the Transport using three 3M x 16mm male/female hex standoffs. The cutter plugs into J1 on the Smart Cutter board. J12 of the Motor Controller board connects to J2 of the Smart Cutter board via cable assembly part number 30-25440. * Existing Transports may be upgraded by ordering part number 32-22379, which includes: P.C. Board Assembly, Smart Cutter Cable Assembly, Smart Cutter 3M x 16mm male/female hex standoffs. Tickets Difficult to Pull Once They Are Issued A simple adjustment can fix the problem in which the patron is having difficulties pulling out the ticket. You must adjust one or both of the shafts that support the tension pulleys for both belts. Start by loosening the screw on the lower right side and the lower left side, and slightly move the shaft either back or forth and re-tighten both screws. While adjusting the shaft to the desired tension, you must make sure the shaft remains perpendicular to both sides of the mechanism. If you loosen one side of the shaft, you must make the same adjustment to the other side of the shaft. It is best to start with the lower shaft first, and if the adjustment is still not satisfactory, you can adjust the upper shaft making sure the tickets do not get jammed at the ticket throat. Right side Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-300 Series • 339 Left side Enhancements The following enhancements have been implemented: * A Ticket Hopper (P/N 30-25439) has been added to the TD-300 and TD-320 transports to provide a means for capturing retracted tickets. * The Bar Code Bracket (P/N 30-12551) was modified to include a Ticket Hopper function. * A pre-made wiring harness has been added to the Bar Code system on the TD-310. Retracted Ticket Hopper The TD-300 mechanism comes with the new Retracted Ticket Hopper. This ticket hopper is designed to catch tickets that have been retracted by the TD-300 Ticket Spitter. The ticket hopper will hold a maximum of 70 – 80 tickets before becoming full. You must empty these retracted tickets before it becomes full based on the amount of retracted tickets your TD-300 collects. The ticket hopper can be ordered and attached to earlier versions of the TD-300 Ticket Series mechanisms. For TD-300 and 320, the part number for the Retracted Ticket Hopper is 30-25439. For TD-310 Bar Code Bracket has been modified to act as a ticket hopper for the TD310. The part number for the Bar Code Bracket is 30-12551. Note: If you do not remove the retracted tickets once you have reached a maximum of 70 – 80, the last retracted ticket may be pulled back into the mechanism by the top belt causing two tickets to be issued to the customer. Que Belt Not Spinning When the TD-300 spitter is first started up, the queue belt should spin. If the queue belt doesn’t spin on startup, then the cutter sensor may have failed. To check the cutter sensor, follow the directions in last month’s August/September 2002 issue under “Using LEDs on the TD-300 Motor Driver Board to Test Sensors.” It is important to not confuse the cutter sensor with the feed sensor. The feed sensor is located closer to where the tickets are loaded into the mechanism. 340 • TD-300 Series 78-0060-4094-9, Ver. 1 Troubleshooting Manual What are some commonly used parts and part numbers for the TD-300 Spitter? 31-12505 - shaft encoder 31-12508 - cutter sensor 11-7063 - positioning sensor 31-10352 - controller 32-10354 - motor driver 30-12526 - cutter 31-12511 - ribbon cartridge for printer 32-10355 - Magnetic Unit Controller Using LEDs to Test With Rotary Cutter With no tickets in the TD-300 mechanism, LEDs SNR2, PWM1, PWM2, PWM3, DIR1, DIR2, and DIR3 should be on. *Note: Disregard the LEDs for the encoder status. These LEDs are E1CA & E1CB, E2CA & E2CB, and E3CA & E3CB. The LED pattern for all encoders is determined by the point in the encoder cycle. The next scenario uses one ticket for testing purposes: When the ticket is inserted into the mechanism, the first sensor it reaches is the feed sensor. When a ticket is in front of the feed sensor, SNR1 should light up. When the ticket travels up the mechanism, the next sensor it reaches is the cutter sensor. SNR2 should turn off. As the ticket travels, SNR1 should turn off and SNR2 should stay off. When the ticket clears the cutter sensor, SNR2 should come back on. When the ticket reaches the queue sensor, SNR3 should turn on. *Note: If you are using a string of tickets, SNR2 should stay off and SNR1 should stay Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-300 Series • 341 on. As the ticket is printed, the printer sensor SNR5 should blink on and back off. As the ticket enters the throat, SNR6 should turn on and stay on until the ticket is either retracted or pulled by the patron. *Note: Ticket retract time, program variable D08 on the TD-300 programmer, should be set to at least 5. D08 should not be set to zero (0) unless you don’t want the ticket to be retracted. There is no default setting for the retract option. Paper Clippings When tickets in the TD-300 series spitter are cut at improper lengths, there are small strips of paper that easily break off during ticket travel. These cut off pieces or chaff will eventually lodge themselves in the sensors along the area of ticket travel. If the sensors become blocked a ticket jam will occur. Before making programmable adjustments, make sure the ticket is already being cut close to the ticket separation (within 1/8 in. or 1 to 2mm). If the sensors do not already allow this to happen, you may need to watch the ticket cut sensor LEDs as the ticket moves slowly through the channel to determine if the sensors need to be cleaned or repaired (replaced). When making adjustments, it is impossible to see the point where the ticket is being cut. The cutter operates in the middle of the cutting unit and hides the ticket cut line. The pictures below show the cutter with a view of the left side having a ticket coming out of the cutter. The right picture shows the right side of the cutter with the ticket barely visible. 342 • TD-300 Series 78-0060-4094-9, Ver. 1 Troubleshooting Manual The midpoint between ticket gaps lies approximately .65mm from the each ticket. The total length of the ticket tab is about 1.30mm. The most desirable cutting locations on the tab are about ±.33mm beyond the .65mm midpoint. 1.30mm Gapbetweentickets Programming command P 13 extends the ability to cut a ticket beyond the 1.30mm length of the tabs to about 3.50mm using programming values of ±50. The total cutting range of the TD-300 is defined by the heavy lines on each side that Cut Tolerance .33mm extend well beyond the ticket gap/tabs. +5 -50 Estimate the location of where the cutter cuts now and determine if you must move the cut to ‘zero’ for a perfect cut. Use the pictures below to calculate a value. .65mm Direction of ticket travel Troubleshooting Manual 78-0060-4094-9, Ver. 1 TD-300 Series • 343 The pictures on the left below show typical TD-300 series tickets. The ticket labeled ‘+50’ on the left has been maladjusted for a +50 value and has excess ticket material on the left. The ticket labeled ‘-50‘ has been maladjusted for –50 and has a different amount of excess material on the right. Can you estimate the location of where the cutter cuts now and determine what number between ±50 it could be set at to cut in the center of the ticket separator tabs? Answer: -22. -50 +50 Direction of ticket travel The picture on the right side indicates an adjustment made for -22. The adjustment leaves an almost equal amount of tab length on each side of the tickets. If you wish to make the difference between the tab lengths more equal, what final adjusting would you do, if any? Answer: If you see the tabs on the right being just a little longer, you may want to reset it to -20, -19, or –18 to reposition the cut. 344 • TD-300 Series 78-0060-4094-9, Ver. 1 Troubleshooting Manual ValueCard Example: ValueCard programming at PowerPad Value Card Programming @ PowerPad this makes value card =$100.00 the cost of this card is $1.00 Program key> Value Card> Master accounts> Creation Press any key (A) Status active Create from front Print: on Facility code 1 Timezone group: 1 Issue level fixed: 1 First use: no Start date: fix today Start time: fix now End date: unused Total value: fixed $100.00 Total uses: unused Max daily use: unused Fee number fixed: 1 Constant fee fixed: no Second area req fixed: no Cash paid: fixed $1.00 Cards to make fixed: 1 Printable session info Session start: unused Session end: unused Program key> Program key> System Pref> SST Validated tickets return Lost tickets from: front SST Failure Mode: Operational Small print: no Skip lines 3 Facility codes: 1 2 3 Program> System Pref> Value Card Activate value card system: yes PowerPad exit type secondary Minimum value check: yes Minimum value: +0.00 Gracetime: 0 Charge Fee after grace: yes Flat Value Charge: no Use charge: no Troubleshooting Manual 78-0060-4094-9, Ver. 1 ValueCard • 345 Set fee number: unused Passback: off Update passback: on Timed antipassback: off Capture expired: yes Capture no value: yes Capture Blacklist: yes Overstay: off Fac.code Monthly Access Debit 1 no no yes Program> Alt Paymt Key ValueCard Status: Value Card Alt Paymt 2 Status: unused Program> Value Card> Set Time Zones> TZ1 00:00-2359 MTWTFSSH YYYYYYYY Group 12345678 Y Program> Value Card> ID Status> Set ID Numbers Valid from 00001 to 24575 Value Card Programming @ PowerPad this makes value card =100 uses the cost of this card is $1.00 Program key> Value Card> Master accounts> Creation 346 • ValueCard Press any key (B) Status active Create from front Print: on Facility code 2 Timezone group: 1 Issue level fixed: 1 First use: no Start date: fix today Start time: fix now End date: unused Total value: unused Total uses: 100 Max daily use: unused Fee number fixed: 1 Constant fee fixed: no Second area req fixed: no Cash paid: fixed $1.00 78-0060-4094-9, Ver. 1 Troubleshooting Manual Cards to make fixed: 1 Printable session info Session start: unused Session end: unused Program key> Program key> System Pref> SST Validated tickets return Lost tickets from: front SST Failure Mode: Operational Small print: no Skip lines 3 Facility codes: 1 2 3 Program> System Pref> Value Card Activate value card system: yes PowerPad exit type secondary Minimum value check: yes Minimum value: +0.00 Gracetime: 0 Charge Fee after grace: yes Flat Value Charge: no Use charge: no Set fee number: unused Passback: off Update passback: on Timed antipassback: off Capture expired: yes Capture no value: yes Capture Blacklist: yes Overstay: off Fac.code Monthly Access Debit 2 no yes no Program> Alt Paymt Key ValueCard Status: Value Card Alt Paymt 2 Status: unused Program> Value Card> Set Time Zones> TZ1 00:00-2359 MTWTFSSH YYYYYYYY Group 12345678 Y Program> Value Card> ID Status> Set ID Numbers Valid from 00001 to 24575 Value Card Programming @ PowerPad this makes value card =99 days Troubleshooting Manual 78-0060-4094-9, Ver. 1 ValueCard • 347 the cost of this card is $1.00 Program key> Value Card> Master accounts> Creation Press any key (C) Status active Create from front Print: on Facility code 3 Timezone group: 1 Issue level fixed: 1 First use: no Start date: fix today Start time: fix now End date: fix duration Date: Days: 99 Total value: unused Total uses: unused Max daily use: unused Fee number fixed: 1 Constant fee fixed: no Second area req fixed: no Cash paid: fixed $1.00 Cards to make fixed: 1 Printable session info Session start: unused Session end: unused Program key> Program key> System Pref> SST Validated tickets return Lost tickets from: front SST Failure Mode: Operational Small print: no Skip lines 3 Facility codes: 1 2 3 Program> System Pref> Value Card Activate value card system: yes PowerPad exit type secondary Minimum value check: yes Minimum value: +0.00 Gracetime: 0 Charge Fee after grace: yes Flat Value Charge: no Use charge: no Set fee number: unused Passback: off Update passback: on Timed antipassback: off Capture expired: yes Capture no value: yes 348 • ValueCard 78-0060-4094-9, Ver. 1 Troubleshooting Manual Capture Blacklist: yes Overstay: off Fac.code Monthly Access Debit 3 yes no no Program> Alt Paymt Key ValueCard Status: Value Card Alt Paymt 2 Status: unused Program> Value Card> Set Time Zones> TZ1 00:00-2359 MTWTFSSH YYYYYYYY Group 12345678 Y Program> Value Card> ID Status> Set ID Numbers Valid from 00001 to 24575 Example: ValueCard Programming at the Spitter Omega Value Card Programming @ Spitter/ Exit Verifier Omega This example is for Full ValueCard: monthly, dollar, and uses. V Card Time Zones Z1 00:00-23:59 M-H Group 1 Set Fee Table Fee 1 Flat Rate 0100 (=$1.00) WSTRT SUN 00:00 WEND SUN 00:00 Day Start 00:00 Eve Start 00:00 Cycle Win off D1 00000 D1 001 10 1 D2 00000 D2 000 00 0 Set ID Status ID Blk: Valid S:00001 E:24575 View Valid ID's S:00001 E:24575 Troubleshooting Manual 78-0060-4094-9, Ver. 1 ValueCard • 349 SST Value Card Value Card on Debit Pay off Check Value on Min Value +000000 In grace Fee : 1 Grace 0000 Min $ After Grace On Fee On Accss On Accss Fee: 000100 (this will charge $1.00 plus flat rate on Set Fee Table, in this case=$2.00) Use On Access Off Passback Off Update Pssback On Verify Write On Time Passback Off Keep Expired On Keep No Value On Keep Blacklist On SST Verifier Set Facility Fac 1_=001 ..D Fac 2_=002 .A. Fac 3_=003 M.. SST Spitter Set Facility Fac 1_=001 ..D Fac 2_=002 .A. Fac 3_=003 M.. Sending ValueCard Programming from ScanNet There are two ValueCard settings that cannot be sent from ScanNet, and need to be programmed at the PowerPad. One of these settings is for the arming loop. To use the PowerPad to program the arming loop, go to Programming/System Preferences/Transaction/ValueCard and then select whether you want to use the arming loop and whether to vend the gate and drawer. The other ValueCard setting that must be programmed at the PowerPad is whether you want to use the maximum number of IDs (24,575). When you try to send a status for the maximum number of IDs from ScanNet, only 24,567 are sent. Another point to keep in mind when programming ValueCard settings is that it is recommended that you only select one ValueCard type for each facility code in the SST device programming. That is, select only monthly, access, or debit for any single facility code. Exit Gate Does Not Vend When You Use ValueCards Make sure the ValueCard feature is programmed properly through the Auditor PowerPad. If the Vend option is not programmed appropriately, the gate will not vend. This is not 350 • ValueCard 78-0060-4094-9, Ver. 1 Troubleshooting Manual programmed at the factory. To program the PowerPad for ValueCard: (1) Go to System Preferences. (2) Select Transaction. (3) Select ValueCard. (4) Program the Vend option as desired. (Choose Gate or Gate & Drawer to ensure the gate will vend.) For PowerPad ValueCard Exit: Make sure that the jumpers are placed on the PowerPad Power Supply between inputs 7 to 9, and 8 to 10. This will jumper your Reader 2 output (9 and 10) to your Gate Vend (7 and 8). ValueCard uses the Reader 2 output for counting purposes. Make sure that 7 and 8 in the PowerPad Power Supply are wired to Gate Vend A between A1 (Vend A) and A12 (Common). Vend B will not work for ValueCard. See the ValueCard Operators Manual for more information. Validated Transient Tickets to Vault/ValueCard Tickets Returned If you program a PowerPad to return validated tickets or to keep them in the vault, it has no effect on the ValueCard operation. The ValueCard operation is set up to return each card after it is used so the customer can use it again and again. The only way for the system to capture a card is if the card is expired, has no value or is on the blacklist. To have the card captured in such instances, you need to program it under the ValueCard System Preference programming. Version B1.1.2v Two important changes include reporting of unreadable cards to SCAN and enhancements to the patron display. Unreadable ValueCards are ejected and a message is sent telling SCAN that the card is unreadable. A message also appears on the patron display. The patron display was enhanced in two important ways. First, when a lot is full but is still accepting ValueCards, the display reads “ValueCard Only” rather than “Lot Full.” Second, once a ValueCard is processed and returned to the patron, the message on the patron display no longer says, “Please take card.” Instead, it displays either: “Access Granted” or an explanation of why access was not granted. Introducing the ValueCard System As parking operators continue to look for innovative revenue-generating options that will please both themselves and their patrons, 3M continues to offer creative solutions. One such solution is the ValueCard System, a rechargeable card access system that allows parking operators to create a variety of monthly access cards, debit cards, or combination access/debit cards on demand. Standard SST® plastic tickets or plastic-coated cards can be created at the cashiering station. The ValueCard system also offers a wide range of payment options that provide unique revenue opportunities for a parking operation. ValueCard Configuration Options The ValueCard System can operate in three configurations: • Monthly Access Cards. These cards are valid for a specific period and feature anti- Troubleshooting Manual 78-0060-4094-9, Ver. 1 ValueCard • 351 passback capabilities. The ability to create and process monthly access cards is available in all ValueCard Systems. • Debit Cards. You assign each debit card a value by start/end time, number of uses, or dollar amount. Each time a patron uses a debit card, the system decrements a value from the card. • Combination Access/Debit Cards. These cards combine the features of the monthly access and debit cards. They enable contracted space while allowing the card holder to use the same card as a debit card at another location. Payment Options In addition to controlling transient parkers, the system can also be configured to control monthly parking passes, prepay (voucher) tickets, special event tickets, advance sale tickets, and decrementing tickets. Popular applications for the ValueCard System include: • Parking operators who want to offer proprietary prepay or monthly parking passes to be used in any parking facility. • Municipalities who want to presell “city” voucher or discount tickets for special events, or monthly cards for employees. • Universities who want to sell debit cards for campus-wide parking or advance tickets for special events. • Medical centers who need to pre-issue decrementing tickets or vouchers for visitors and employees. Hardware Components Devices that can be equipped with ValueCard features include: • SST Auditor PowerPad™ Fee Computer for creating ValueCards and processing ValueCard transactions in conjunction with the SST Ticket Spitter®/Exit Verifier. • SST Ticket Spitter/Exit Verifier (with push-button operation) for controlling entry into a parking facility and updating ValueCards in conjunction with the Fee Computer. • SST Automatic Pay Station for processing ValueCards in a Central Cashiering system. Minimum requirements include the Ticket Spitter and the Fee Computer. The ValueCard operates optimally with the Model G-90 LCD Series™ Barrier Gate with the Omega LCD. It can operate as a stand-alone system or on-line with the optional SCAN Facility Management System. ValueCard Programming For a system to accept and process ValueCards, it must be programmed accordingly. The minimum programming required includes: • Time Zones • IDs • Time and Date • Starting Ticket Number at the ValueCard Ticket Spitter • Facility Codes (for monthly access and debit cards) • Fee Structure (for debit cards) The ValueCard Operator Manual provides detailed information on ValueCard programming. 352 • ValueCard 78-0060-4094-9, Ver. 1 Troubleshooting Manual As a reminder, once your system has been programmed with the appropriate ValueCard data, you should not hold down the Menu key on the SST Omega Controller during power-up or you will lose all the IDs and Time Zones that have been programmed. The only time you should hold down the Menu button is when you are changing a DIP switch setting or performing service on the SST Ticket Spitter or Exit Verifier. After performing such service, you must reprogram the ValueCard data. Creating ValueCards You create ValueCards using an Auditor PowerPad Fee Computer. There are two options for creating ValueCards: • Front Create ValueCards. This option produces individual monthly tickets or plastic cards from the front of the SST Ticket Spitter and it involves manually inserting each ticket or card. • Rear Create ValueCards. This option uses a ticket Burster device in conjunction with paper fanfold tickets to produce a large volume of tickets or cards in a hands-free environment. ValueCard™ Features and Benefits The ValueCard System allows parking operators the unique opportunity to: Create passes on-site for monthly access cards, debit cards, voucher tickets, discount tickets, special event tickets, and proprietary prepay tickets Add value to a Pass on demand Assign start/end times, number of uses, or dollar value at the cashier station Issue standard SST magnetic stripe paper tickets or plastic coated cards Operate as a stand-alone system or an on-line system Use a dual-purpose SST Ticket Spitter and Exit Verifier to eliminate separate readers Take advantage of full anti-passback features ValueCard Misunderstandings 1. The end time does not use the “minutes” field. This means that if you program an end time at 10:30 the actual end time on the ValueCard will be 10:00. 2. When creating a “first use” ValueCard you MUST use an exit cashiering type PowerPad. (What happens for first use is it will put the end time as programmed when used at a non-exit type device.) If you create it at a central PowerPad the end time is used and programmed from creation, not first use. Also the card must be used at an entrance device first. 3. When using passback the cashiering type of the PowerPad will determine how the card must be used. When created at an exit cashiering PowerPad, The ValueCard must be used at an entrance first. If created at a central cashier station, it may be used at an entrance or an exit first. 4. System Preferences>Transactions>ValueCard must be programmed to vend the monthly ValueCards. This is currently not programmable through ScanNet. (3/8/02) 5. Using the Add-on function at an APS, it will not display the new end date. 6. Using the access “uses” function, remember, an exit device will always take off one use by default. If “charge use” is checked (general options) at the entrance it will take off a use when entering (as well as the exit). If it is checked at the exit device it will charge two uses. Troubleshooting Manual 78-0060-4094-9, Ver. 1 ValueCard • 353 7. When using an access value, or debit card be sure to check “charge fee after grace” or the card will never be charged. 8. There is no Resync. for passback on a ValueCard, and if using passback be sure update passback is set to on. 9. If there is no minimum value programmed the value on the card will go negative. 10. Currently PowerPad spitter supports MONTHLY ValueCards only. (3/8/2002) 354 • ValueCard 78-0060-4094-9, Ver. 1 Troubleshooting Manual ValuePass Creating ValuePasses offline If a ValuePass is created offline, one of the following three scenarios will take place: (1) If the Posting Reader is offline, the messages will be buffered at the Reader and be sent to the ScanNet Central Management system when the Reader comes back online. (2) If the Port Controller is offline, the messages will be buffered at the Port Controller and be sent to ScanNet when the Port Controller comes back online. (3) If the ScanNet system is shut down, the Port Controller will have buffered the messages for the ValuePass creation, but the system will begin polling the devices for messages before CAMP starts up. This could result in some of these messages getting lost. Increasing the start-up poll delay will allow more time for CAMP to start up before the system begins polling. Calculating Central Access/ValuePass Credentials For Dyna Readers and 3M Wiegand Readers, which are 27-bit, you calculate the formula this way: Credential ID = Number assigned to card + (32,768 x Facility Code). However, for some 26-bit Wiegand Readers, the following formula may be required: Credential ID = Number assigned to card + (65,536 x Facility Code). For Bar Code Readers, the Credential ID numbers are the numbers on the cards. If you enter the ID range correctly, when you swipe a card at a Reader, the Credential ID will be displayed in the CAMP window. Recently, a Credential ID Calculation program has been added to ScanNet under the Utilities menu. This program will automatically calculate the formula for you. Minimum programming for ValuePass There is programming that must be done before going into Basic Setup. Follow this list of minimum programming from top to bottom. Programming>Passport Plus Card Data Configuration Central Access/ValuePass Configuration Options Reader Setup Programming>PowerPad Fee Tables Systems>Access Control System>Access Maintenance>Basic Setup In Basic Setup, you need to address the following: Facility Name Reader Type Reader Setup (should match Programming>Passport Plus>Reader Setup) Check "Allow ValuePass Credentials" Access Configuration (Must have at least one Central type) Package Setup Troubleshooting Manual 78-0060-4094-9, Ver. 1 ValuePass • 355 Other Questions Transmit and Receive ICs Device IC Function IC Type IC Designation Part No. PP+ Logic Module Transmit Sn75174 U3 11-9171 Receive Ua9637 U5 11-9124 Transmit Sn75174 U15 11-9171 Receive Mc3486n U14 11-9214 SST & LCD Omega Rev C, H Transmit/ Receive Max489EPD U19 11-9322 Standard Omega Transmit Sn75172 U20 11-9125 Receive Ua9637 U21 11-9124 Transmit Sn75172 U3 11-9125 Receive Sn75173 U4 11-9138 Transmit Sn75174 U3 11-9171 Receive Ua9637 U5 11-9124 Transmit Sn75172 U2, U6 11-9125 Receive Ua9637 U1, U4 11-9124 Auditor PowerPad Transmit Sn75174 U2 11-9171 Power Supply Receive Mc3486n U1 11-9214 Receive Sn75158 U6 11-9296 Sn75174 U28 11-9171 Ua9637 U29 11-9124 SST & LCD Omega Rev B Auditor 2 Port Controllers Comm. Isolators Auditor PowerPad Rev A, B Transmit Receive 356 • Other Questions 78-0060-4094-9, Ver. 1 Troubleshooting Manual Comm controller Dual ACIA Auditor PowerPad Rev C Hand Held Computer U16, U17 11-9272 Xmit/ Rcv, RS422 Max489EPD U22,U23 11-9322 Xmit/ Rcv, RS232 LT1081CN U17, U18, U20 11-9189 Comm controller Quad UART U21 11-9323 Transmit/ Receive 11-9186 Sn 75176 U1 What to Check if Your Site has a Lightning Strike 1. Unplug the communication cable from all devices 2. Check the Port Controller lights to see if TX RCV is blinking 3. Ensure that the Port Controller is communicating with the computer. If it is not communicating, change the Transmit and Receive chips in Port Controller. (*Remember to change IC’s with power off) Plug devices in one at a time. If device is off-line or pulls another device off-line, change Transmit and Receive chips. 4. If changing the Transmit and Receive chips does not work, leave the device unplugged from the communication line and finish checking the remaining devices. *Note: The Port Controller must be working before you can test other devices. Approved Ticket Vendors Supplier Ticket Type TDTD-256 Barcode SST 249 2 ½" x 2" x 4" 2 1/8" x 3 3/8 " 2" x 4" 6" ValueCard 2 1/8" x 3 3/8" 10 pt polyester Single Double sided sided thermal thermal Digital Printing Co. 777 N. Georgia Ave. Azusa, CA 91702 Tel: (626) 334-1244 Fax: (626) 334-5663 Electronic Data Magnetics PO Box 7208 Troubleshooting Manual 78-0060-4094-9, Ver. 1 Other Questions • 357 High Point, NC 27264 Tel: (336) 882-8115 (800) 336-8115 Fax:(336) 882-0106 Litho Formas SA de CV Filiberto Gomez 15 Fracc. Ind. Tlainepantla Edo. De Mexico, 54030 Mexico Tel: (+ 525) 565-8008 Fax: (+ 525) 390-8695 Moore Concord House 1st Floor, 15-17 Blaxland Rd. Rhodes, NSW 2138 Australia Tel: (+ 612) 795-4222 Nagel Druek Kempen GmbH PO Box 10 05 80 D-47882 Kempen Germany Tel: (+ 49) 21 52/20 99 0 Fax: (+ 49) 21 52/5 30 08 Southland Printing Co. PO Box 7263 Shreveport, LA 71137 Tel: (318) 221-8662 (800) 241-8662 Fax: (318) 221-8738 Toledo Ticket Co. 3963 Catawba Street Toledo, OH 43612 Tel: (419) 476-5424 (800) 533-6620 Fax: (419) 476-6801 Customer Requested Ship Date The 3M Customer Service Department is requesting that customers include a Customer Requested Ship Date when placing purchase orders. Please do not request “ASAP” as your requested ship date. If the requested ship date is “ASAP,” the date will default to one week from the receipt of the purchase order(s) for parts and two weeks for equipment. Note that some equipment requires a longer lead time than two weeks. This 358 • Other Questions 78-0060-4094-9, Ver. 1 Troubleshooting Manual list of equipment and the associated lead times are listed below. If you do not want your order to be shipped within the standard two week period, you can request a later ship date and that date will be honored. The above information is very important for all orders, especially on large orders, so that 3M can meet your desired ship dates and avoid early or late deliveries. Long lead-time parts: Parts Lead Time United States APS 6 weeks International APS 12 weeks ACT 4 weeks TagMaster products 3 weeks Special paint 6 weeks Prox cards 4 weeks Custom silkscreen cards 6 weeks TD-300 series 4 weeks All other parts and equipment 2 weeks Running Intercom Wiring Next to the Communication Wiring Running intercom wire next to the communication wire in the same conduit is not recommended because of interference caused by the communication wire. A person speaking on an intercom will hear communication distortion caused by the communication wire. Since the communication wire is wound upon itself, the communication will not be affected by the presence of the intercom wire. It would be best Troubleshooting Manual 78-0060-4094-9, Ver. 1 Other Questions • 359 to install the intercom wire inside of a separate conduit away from the communication wire. New Warranty Exchange Procedure No warranty exchanges will be processed without first contacting the Product Support Group. After a member of the Product Support Group determines that you are experiencing a problem that is covered under warranty, they will take the steps necessary for you to get a warranty exchange. When you call, please provide the Product Support Group with your company name, contact name, original sales order or PO number, project or site name, part number, serial number if applicable, and a description of the defect. If a part is returned for credit and is not defective, or if the defects were caused by something not covered under our warranty, you will be charged $75.00, and the unit will be returned to the customer. Product Support Policy for Handling Calls In April 2003, the Product Support Group started logging all calls to a call tracking system. This system enables us to track and follow through with every call received. We are tracking your information to enable us to provide you with better support. If you are a distributor of 3M and are calling for technical support your call will be routed to the Product Support Operator. The Product Support Operator will then ask you for your name, distributor name, site name, phone number, and a brief description of the issue. The Product Support Operator will immediately assign the call to the next available Product Support Technician after the information is documented, and a technician will call you back. Once the Product Support Technician has received the call, our goal is to return the call within 15 minutes. If you call back on the same issue, you must provide the name of the technician that is working with you to the Product Support Operator. The Product Support Operator will then route the call to the technician that is assigned to your issue. If the currently assigned technician is not available when you call back, the Product Support Operator will have the next available technician return your call. Universal Power Supply Assembly Two 5A fuses were added to the Universal Power Supply Assembly. These fuses are necessary for the operation of the power inlet module. E-mail Order Verification Process In an effort to serve you better, 3M will be initializing an e-mail order verification process. We learned that many distributors prefer the order verification to be sent via electronic format (PDF file). If you would prefer to have the order verification to be sent to one of your company’s representatives via e-mail, then there will no longer be a need to wait for a mailed copy. You will be sent the order verification on the same day the 360 • Other Questions 78-0060-4094-9, Ver. 1 Troubleshooting Manual order is entered, which will allow instant review and feedback if there are any questions regarding the order. Your company will soon be receiving an e-mail response form in the mail. Please respond with the appropriate e-mail address. DIP Switch Settings for Printers Printer Type Switch Number Switch 1 Switch 2 Okidata 9 pin 1 ON ON 2 ON off 3 ON ON 4 ON off 5 off off 6 ON off 7 off ON 8 ON off 1 off off 2 off off 3 off off 4 off off 5 off off 6 off ON 7 off off 8 off off Epson TM-U950 Troubleshooting Manual 78-0060-4094-9, Ver. 1 Switch 3 Other Questions • 361 Epson TM-U930 1 off off off 2 off off off 3 off off off 4 ON off off 5 ON off off 6 ON off off 7 ON off off 8 ON off off 9 off 10 off Message buffer sizes for SST Spitter Omegas, Port Controller, Passport Plus, LPI Workabout Handheld, and the ScanNet Central Credit Card. SST Spitter Omega message buffer size There is a buffer in the SST Omega named MSG_BUF that is 1800 bytes. That would allow seven full-sized (i.e. 256-byte) messages to be stored there or 180 messages sized at 10 bytes each. This message buffer is used in connection with a variable named MSG_LOST which is incremented if there is no room in the buffer for another message. Port Controller can buffer between 600 - 1000 transactions PP+ can buffer around 600 transactions LPI Workabout Handheld can hold up to 2000 lot spaces ScanNet Central Credit Card can buffer up to 1200 transactions *Note: depending on the message, the space designated for buffering can become smaller with larger messages buffering to it. 3rd Party Safety Certification The issue of safety is a great concern to all of us. As an equipment manufacturer, 3M goes to great lengths to make sure all hardware components meet and exceed industry safety standards and regulations. 3M products are evaluated and tested for safety risks by independent, third-party safety certification organizations: Underwriters Laboratories, Inc. (UL) for products sold in the US and Canada, and by SGS UK Ltd for products sold in the European Union bearing the CE Mark. With this testing, 3M products are certified to pass stringent safety requirements. UL Marks - What they look like and what they mean. There are several types of UL Marks. Each has its own specific meaning and significance. The only way to determine if a product has been certified by UL is to look for the UL Mark on the product itself. The only products eligible to carry the UL Mark are ones that have had samples evaluated to meet UL requirements. The UL Mark is found on the serial tag of 3M products. This is 362 • Other Questions 78-0060-4094-9, Ver. 1 Troubleshooting Manual one of the most common UL Marks. If a product carries this Mark, it means UL found that samples of this product met UL’s safety requirements. These requirements are primarily based on UL’s published Standards for Safety. Underwriter Laboratory introduced the new UL C/US Listing Mark in early 1998. The products with this type of mark have been evaluated to meet Canadian safety requirements, as well as U.S. requirements. Most 3M products will display this Mark. The European Union CE Conformity Mark Standardization in the European Union (EU) has taken an ever-increasing importance as the borders have been eliminated between Member States and the founding principle of free movement of goods is applied throughout the EU’s territory. The “new approach” to standardization has resulted in new requirements, the use of harmonized European standards, and the affixing of the CE Mark to products. The CE (European Conformity) Mark is a symbol that manufacturers affix to products or machines to indicate that a product conforms to all relevant European directives and standards. The CE mark is a mandatory legal requirement for virtually allelectrical devices, and specifically safety related products, sold into European Union and European Free Trade Area countries (including Austria, Belgium, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxemburg, The Netherlands, Norway, Portugal, Spain, Sweden, and the United Kingdom). You should not confuse the CE marking with another mark, certificate, or approval issued by an accredited certification body (such as UL). To ensure safety and EMC compliance, 3M went to an European third party for testing and certification. The testing laboratory used is referred to as a “Notified Body” for safety and a “Competent Body” for EMC. This voluntary certification included conformity-assessment for: 1. Electromagnetic Compatibility (EMC) Directive (BSEN 60335-1995, BSEN 609501992, BS7002-1992). This directive states that all apparatus placed on the EU/EEA market must meet electromagnetic compatibility criteria. The apparatus shall be constructed so that: a. The electromagnetic disturbance it generates must not exceed a level, which would affect the proper operation of radio and telecommunications equipment and other apparatus. b. The apparatus has an adequate level of immunity to electromagnetic disturbance to enable it to operate as intended. 2. Low Voltage (LV) Directive (EN 60950, EN 60204-1). This directive states that all electrical equipment marketed in the EU/EEA that has voltage rating between 50V and 1000V AC or between 75V and 1500V DC must not endanger the safety of persons, animals, or property when installed and operated as intended. 3M contracted with the independent European testing lab SGS UK Ltd to assess conformity to a number of products so that the CE marking could be affixed and certified. SGS is the world’s largest independent test and inspection company, is NAMAS accredited for a wide range of tests, and is appointed as a “Competent Body” under the EMC Directive. SGS is also a “Notified Body” under the Machinery, Low Voltage, and Medical Devices Directives. They are qualified and certified to perform each test and inspection of compliance. Gary Ward, Vice President of Research & Development, and Bill Harden, Engineering Technician, spent time at the testing facility in England and came back with a new appreciation of the European marketplace and its regulations. To order products with the Troubleshooting Manual 78-0060-4094-9, Ver. 1 Other Questions • 363 CE Mark, add the following options to the standard product: Part Number/Description (CE Mark Option) 87-19710 SST Ticket Spitter (Model MG 1000/220V) 87-19710 SST Exit Verifier (Model ML 3000/220V) 93-10263 SST Auditor PowerPad Fee Computer (220V) 43-17382 SST Automatic Pay Station (Model SST 1000/220V) 23-16512 Model G-90 CD Barrier Gate (220V). It is important to note that the CE marking is a proclamation made by the manufacturer that their equipment meets the standards established by the European body directives. Therefore, the CE Mark is a self-proclaiming certification statement that must be supported by the company wishing to do business in the European Union. The CE Certification process is mandatory for doing business in any of the participating countries, especially for safety related products such as parking products. The following list clearly states what the CE marking is and is not: The CE marking is a declaration for customs inspectors and allows the product to be placed on the market. The CE marking is not for sales, marketing, or promotion, and it cannot guarantee sales The CE marking is not a quality marking The CE marking is not a mark of certification or approval Lastly, The CE marking is not for components (with a few exceptions). The CE marking can be described as a “passport for industrial products,” allowing them to circulate freely throughout the European Economic Area (EEAA). It is a mandatory conformity marking that shows the compliance of products with all provisions of 16 directives that relate to safety, public health, consumer protection, or other essential requirements. Bill Harden from R&D and Ted Kopp from Engineering have been spearheading this team effort. 3M is now shipping its first SST System to Europe since these directives have taken effect. Shipping Overnight with UPS Red When you request UPS red, you are specifying a specific carrier that may be costly. Whenever possible, you should simply use the term “overnight” as long as the carrier is not an issue. Then the 3M Shipping department will use its expertise to choose the most cost effective method and carrier in order to get your shipment to you in the required time frame. For your information, domestically, we use UPS and Federal Express, depending on which one is more cost effective, and we use Federal Express or DHL internationally. ROM Burner for Downloading Firmware We suggest the EMP-10 or EMP-20 ROM Burner and the E-10-S8 Data Eraser by NeedHams Electronics. Contact NeedHam's at (916) 924-8037 or www.needhams.com for more information. 364 • Other Questions 78-0060-4094-9, Ver. 1 Troubleshooting Manual Demo Copy of ScanNet You can join the 3M ScanNet Subscription Plan. This plan is yet another valuable tool that will provide you with the technical support that our customers need for this product. 3M will provide you one year of access to all of the technical updates for our ScanNet software. You will receive a ScanNet N.F.R. (Not For Resale) CD-ROM. This "live" ScanNet program may be installed on as many of your company's computers as you deem necessary. This will allow sales and service personnel the advantages of working with the product as they need to without any security keys or time outs. This exciting offer also allows you to receive 4 quarterly software updates. The updates will be sent out to you on a CD-ROM. Your subscription also includes documentation and updated manuals that include the enhancements. Your subscription begins when you receive your ScanNet N.F.R. CD-ROM. However, you need to send your purchase order for this service to your regional sales office in order for us to process the order. So, send them in now! The cost of this service is $600.00 per year, payable in U.S. funds. Pricing subject to change. We will invoice you when the program begins and we ship you the ScanNet N.F.R. CD-ROM. Fax your purchase orders in now! Reference part number: 89-12523. Parking Jargon Have you ever wondered what abbreviations like SRAP or MRAP stand for, or what is meant by terms like “Revenue Control”, “Access Control”, or “Parking Control”? Maybe you’ve heard these terms or read them in 3M correspondence but were unsure what they meant. Well, here’s some information to help you make sense of it all. SRAP stands for Scan Revenue Access Parking. MRAP stands for MiniScan Revenue Access Parking. Revenue Control is the term for products that control the way revenue is collected at a parking facility. These products include Auditor PowerPad Fee Computers and Automatic Pay Stations. Access Control products allow specific patrons access to a facility. These products include Card Readers and related equipment. Parking Control products allow vehicles to enter and exit a facility at appropriate times. These products include gates, loop installation kits, and Full signs. Finding Firmware Versions Users often contact the System Support Group for help in determining what version of firmware is installed on a specific piece of equipment. The following list was compiled to assist you in finding various firmware versions. SCAN DOS Facility Management System: From the Main Menu screen, press Control and v at the same time. The SCAN version, date, and order number will be displayed in the lower left corner of the screen. ScanNet: go to the main navigation bar, and choose Help/ about ScanNet. It will tell you the version in this screen. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Other Questions • 365 Auditor PowerPad (Fee Computer, Programming Terminal for the Automatic Pay Station, and Credit Card Exit Verifier): The firmware version appears in the lower right corner of the PowerPad display when logging off. Passport Plus and ValuePass: The ROM on the lower board is labeled with the firmware version. G-90 LCD Barrier Gate: At the Omega LCD Controller, go to the Monitor mode. Press the Misc button until the version number and date are displayed. LED Fee Display Introduced The LED Fee Display shows the customer a significant amount of data in large, highintensity LED fonts measuring 2.3 inches in height. This makes it easier to see and read the display even in high sunlight conditions. The unit is mounted into an all aluminum enclosure and comes with all hardware necessary for booth or pedestal mounting. There is also a heater option for severe cold applications. The LED Fee Display interfaces with any Auditor PowerPad Fee Computer via the standard parallel Fee Display port. The unit has a built-in diagnostic mode for easy field servicing. Overall dimensions of the unit are: 18.3”L x 5.83”W x 2.5”D. Y2K Compliant Firmware Versions * Auditor 2,2+2,2C Fee Computer All Versions * PowerPad Fee Computer...Platform A1.8.6 or Platform B2.2.0 (or higher) * Bar Code PowerPad...Platform A1.8.6 or Platform B2.2.0 (or higher) * Bar Code Ticket Spitter...Version 2.9.7 or higher * Credit Card Exit Verifier...Platform A1.8.6 or Platform B2.2.0 (or higher) * Passport Plus Card Reader...Version A3.0.1 or higher * Port Controller (MiniSCAN)...Version A1.7.8 or higher * Port Controller (SCAN)...Version A1.7.8 or higher * SCAN...Versions dated post January 1998 Facility Management System Software...(see minimum computer specifications) * Scan NT...Version 2.0 or higher Central Management System...(see minimum computer specifications) * SST Automatic Pay Station...Platform A1.8.6 or Platform B2.2.0 (or higher) * SST Omega Controller...Version 1.13.0 or higher * SST ValueCard Omega...Version B2.1.1 or higher Prevent Your Warranty From Becoming Void by Shipping Parts Correctly When shipping parts in for repair that are still under warranty, be sure to return the part in the packaging that you originally received the part in. If you no longer have this 366 • Other Questions 78-0060-4094-9, Ver. 1 Troubleshooting Manual packaging, you may package the part in a static proof bag, and secure the part in a box to prevent the part from becoming damaged during shipping. You may use packaging peanuts to secure the part as long as the static electricity bag is sealed so that no packaging peanuts can get inside of it. Shipping a box in which the part comes in contact with packaging peanuts is not permitted, and your warranty will be void. You cannot use packaging peanuts directly on the part because static electricity will damage it. Troubleshooting Manual 78-0060-4094-9, Ver. 1 Other Questions • 367 Index 3 3rd Party Safety Certification, 377 A Access Control System ACS same password as ScanNet, 293 ACT Addresses Stuck on Zero, 22 Axiohm, 17 Axiohm DIP Switch, 21 C3.6.0.11, 29 C3.6.1.3, 28 Config Options, 16 Editing Configuration Chips, 17 Expansion Board, 15 Fee Display, 21 Power Supply, 22 Receipt Door, 15 Relief Notch, 15 Serial Port, 16 Serial Ports, 15 ADS Link Install, 267 Amtech Wiring, 129 Approved Ticket Vendors for TD-249, TD-256, Barcode, SST, and ValueCard, 372 APS 3.2.0, 72 A1.8.0, 73 Addresses Stuck on Zero, 22 Axiohm, 69 B3.3.2.0, 72 Bank Note Acceptor, 31 BNA 51, 71 BNA 52, 71 C.3.3.0.2, 72 C3.2.0.2, 72 C3.6.0.11, 71 C3.6.1.3, 71 C4.0.1.5, 71 368 • Index CashCode, 64 Common Troubleshooting, 67 General Information, 66 Keys Not Working, 63 Language Changed to Italian, 69 Not Spitting Notes, 65 Note Validator Variant, 70 Pre-Pay Option, 66 Pull Reports, 69 Reinserting Note Dispenser, 68 Sodeco Support Tool, 31, 69 Stopped Taking Bank Notes, 68 Switch Replaced, 65 Voice Annunciation, 71 AWID Read Range, 128 Axiohm ACT, 17 DIP Switch Settings, 21, 69 B Bar Code Card Data Configuration, 131 C CASI-RUSCO Programming, 129 CCEV C2.8.1.4, 77 Crossover DIP Switch Settings, 77 Crossover Exit Verifiers, 77 Serial Expansion Board, 77 CCXV Fee Display, 21 CD introduction, 94 Master/Slave, 93 Multiple Readers, 92 Rebound Circuit, 95 CF-803i 7.1.34EN, 75 7.1.34UN, 75 Config Module 78-0060-4094-9, Ver. 1 Troubleshooting Manual No Config, 80 Credit Card Exit Verifier B2.6.4V, 77 C3.1.4V, 77 Customer Requested Ship Date, 374 D DIP switch Omega, No Config, 87, 88 Omega, reset, 89 Dyna II Upgrade to Dyna III, 133 Dyna III A2.3.1, 121 E EDC-1000 Stop Free Gate, 92 Editing Configuration Chips ACT, 17 E-mail Order Verification, 375 E-mailing SRO Requests, 374 F Finding Firmware Versions, 380 G Gate Arm Up, 81 G89, 83 Illegal Forward, 81 Illegal Reverse, 81 Loop Detection, 80 Loops vs. Frequency, 83 Motor Oil, 79 Motor Troubleshooting, 82 Tips & Tricks, 79 Transient Backward, 81 H HID Wiring, 128 Host-Based A1.2.5, 140 A3.4.5, 140 Troubleshooting Manual I Introducing LPI, 109 L Lane Troubleshooting LCD or CD gate with Passport Plus with no arming, 87 loop detection for G90 CD gate, 85 Passport Plus Card Reader and G-90 CD Gate, 104 TD-249 Barcode Ticket Spitter and G90 CD Gate, 102 wiring TD-249 to LCD or CD gate, 85 LCD Tailgate, 94 LCD or CD B2.1.0, 99 B2.1.1, 98 B2.1.2, 98 B2.4.7, 98 B2.6.0, 98 Base Mode 5 Sub Mode 1, 99 Base/Sub Modes, 100 C3.0.1, 98 C3.0.4, 98 Cold-starting, 92 Config Module, 91 Counts Option, 101 Inputs and Outputs, 91 Losing Programming, 93 Warning Labels, 93 LCD or CD firmware B2.4.8, 97 C3.0.5, 97 LD-23 Troubleshooting, 107 LED Fee Display Introduced, 381 Lightning Strike What to Check, 372 Loop Detection Gate, 80 LPI Error 1000, 110 LPI PORT OPEN, 110 Notes, 109 78-0060-4094-9, Ver. 1 Index • 369 Version 3.1.1, 110 P M Message buffer sizes SST spitters, Port Controller, Passport Plus, LPI Workabout Handheld, and ScanNet Central Credit Card, 377 MG-1500 Power Supply, 22 Motor Oil Gate, 79 Motorola Wiring, 129 N NetPort 100K readers, 118 A2.2.3, 120 A2.2.4, 120 Addresses, 120 Changes, 118 Editing Port Controller, 118 Features, 117 Introducing, 117 Passback, 117 Primary Area Control, 118 Programming, 119 No Config Mode Not Working, 97 O Omega B2.4.83.0.5, 97 C3.0.5, 97 Circuit Board Redesigned, 325 Communication Waveform for B Platform, 96 Communication Waveform for C Platform, 97 Display, 94 Flash, 80, 325 Surface Mount, 93 370 • Index Parking Jargon, 380 Passport 360 1.1.1.3, 124 1.1.2.4, 121 Downloading Firmware, 127 General Information, 124 Introducing, 123 Programming, 123 Replacing Passport Plus, 123 Serial Connection, 121 Passport 360 PDA 1.1, 125 1.2, 124 1.3, 121 Passport Plus 27128A EEPROM, 127 A3.3.0, 139 Amtech, 129 AWID, 128 Bar Code, 131 CASI-RUSCO, 129 Discontinued, 132 Door Readers, 136 D-Type Firmware, 131 Expansion Boards, 132 HID, 128 Host-Based, 134 Keypad programming, 137 Losing Memory, 133 Motorola, 129 Programming Universal Track 2, 127 Reader Setup, 139 Reader Type, 137 Resync, 136 Series-16 with Prox Readers, 134 TagMaster, 128 Universal Track 2, 128 Weather Striping, 139 Weigand, 130 Passport Plus Posting A1.8.6, 139 Passport Plus Series 16K A3.4.5, 140 Port Controller 27128A EEPROM, 147 78-0060-4094-9, Ver. 1 Troubleshooting Manual 2MHz Processor, 147 B1.7.5, 149 B1.8.3, 149 B1.8.5, 149 B1.8.6, 148 Editing Scan_NT.ini file, 148 Enter Retry Mode, 147 Non-existent Devices, 147 Pin-out, 148 Upgrade, 148 Port Controller 100K B1.8.1, 149 PosiDRIVE 1.1.1, 154 1.2.1, 152 Arm Not Raising on Power Loss, 153 Backout Timer, 152 Balancing Gate Arm, 151 Gear Box Lubricant, 153 Heaters Discontinued, 153 Improved Gate Arm, 152 New Mainspring, 153 Red/Green Light Wiring, 154 Three Position Switch, 151 Warning Labels, 152 Power Supply Upgrade Instructions, 22 PowerPad 1.8.7, 187 2.0.1, 186 2.2.0, 186 A Versus B Firmware, 179 A1.7.7, 186 A1.8.2, 186 A1.8.5, 186 A1.8.6, 186 Address Stuck on Zero, 178 Auto Rate, 165 B Firmware in C Board, 179 B2.0.1, 185 B2.3.0, 185 B2.4.0, 185 B3.3.3, 184 Buffered Transactions, 178 C Firmware in B Board, 179 Troubleshooting Manual C Platform PowerPad Memory I/O Board, 167 C3.6.0.11, 184 C3.8.0.19, 184 C4.0.0.20, 182 C4.0.0.21, 182 C4.1.0.3, 181 Clearing Cash Reports, 171 Clearing Houses for Datacap DataTran POS System, 161 Clearing Memory, 164 Clearing YTD Lane Report, 173 CPU Error Messages, 162 Credit Card Vouchers, 179 Currency Exchange Feature, 166 Customize Financial Reports, 169 Desktop Fee Display, 166 Display Characters Wrong Spacing, 166 Editing Configuration Chips, 158 Expansion Board Problem, 167 Fee Display Troubleshooting, 164 Internal DIP Switches, 174 Journal Tape, 177 Keys Not Working, 63, 177 Lost Not Active, 164 Max Number of Cashiers, 169 MC3486 Receive IC, 165 Merchant (Hole-Punch) Validator Cashier Accidentally Validates, 156 Merchant (Hole-Punch) Validator Location of Holes, 156 Merchant (Hole-Punch) Validator Setup, 155 Merchant (Hole-Punch) Validator Ticket Inserted Wrong Way, 156 Not Vending Drawer, 175 Not Vending Gate, 174 Paid and Unpaid Grace Time, 168 POS System, 172 Power Supply, 22 Power Supply Revision E2 or Older, 178 prints *****257*****date/time, 168 Reduced Exit Time, 165 Repay Feature, 171 78-0060-4094-9, Ver. 1 Index • 371 SRAM Added to Assembly, 178 Ticket Being Printed Message, 170 Ticket Jam Message, 155 Tips and Tricks, 163 Updating C-3 fee Display from Auditor II to PowerPad, 164 Upgrading, 180 Validated Tickets to Vault, 168 Validator Power Supply, 166 Which ID Should a Particular Store Get, 155 Prevent Your Warranty From Becoming Void, 381 Printer DIP Switch Settings, 376 Product Support Policy, 375 Programming Series Readers, 131 R RC2 1.0.0.15, 190 Introducing, 189 ROM Burner, 379 Running Intercom Wiring Next to the Communication Wiring, 374 S SCAN DOS Backup Utility, 192 Clear Print Buffer, 191 Device Intermittently Offline, 191 Hot Keys, 193 SCAN Data Manager, 191 Windows 2000, 192 Windows Operating System, 192 Scan NT 2.0, 314 3.0, 313 3.1.0, 312 3.1.0.6, 312 3.1.1, 312 3.1.1.5, 311 3.2, 310 4.0, 303 Subscription Plan, 295 372 • Index ScanNet 4.3, 302 4.4, 301 4.4.0.21, 301 4.4.1.10, 261, 297, 300 4.4.2.2, 261, 299 4.5.0.14, 299 4.6, 298 4.6.3.6, 297 4.6.6.8, 210 5.0, 205 5.1.1.5G, 203 5.1.2.11G, 197 Access Duration Report, 260 accidental deletion of lots, 297 Accidental Shutdown of Sybase, 258 Agent, 262 APS not showing up in device list, 297 Automatically Bill and Print With Billing and Invoicing, 202 CAMP Shutting Down, 209 Cardlog Conversion, 261 Central access credentials with Billing and Group Control, 309 Central access credentials with Billing but no Group Control, 308 Central access credentials with Group Control but no Billing, 306 Central access credentials with no Billing or Group Control, 307 Central access ValuePasses with Billing and Group Control, 305 Central access ValuePasses with Group Control but no Billing, 306 Central access ValuePasses with no Billing or Group Control, 307 Central Credit Card, 257 Central Credit Card Required Update, 294 Copy ID Fields to Name Fields, 266 CreateDsn.exe, 197 Credential Options and Setup, 263 Database Archiver, 211 Database Does Not Appear to be for ScanNet 4.0 or Later Message, 294 78-0060-4094-9, Ver. 1 Troubleshooting Manual Delete standard credential from the ACS, but the reader still works, 258 Demo Copy, 380 Device Offline/Online, 259 Duration by Ticket Report, 257 Facility Codes and Credential IDs, 267 Generate Invoice With No Activity, 203 Grace Exit Report, 257 IE Requirements, 210 Importing Data to Excel 2000, 198 Last Card Report, 260 MLS Reset, 196 Navigator Showing Only a Blue Bar, 202 NIC Card, 262 Not Locking Out Standard Credentials, 136 Not Locking out Standard Credentials with Group Control, 264 Office 2000, 264 Passback Messages, 265 PC Requirements, 258 Posting Reader ScanNet 5, 198 Power Builder Application error, 297 Saving database report parameters do not show at client computer, 260 Saving PowerPad Programming Files, 203 ScanUpdate.exe, 201 SCPMKILL, 196 Searching Credentials, 265 Serial Numbers, 211 Server/ Client, 262 Server/Client, 195 SQL Statements, 196 Standard credentials with Billing, 305 standard credentials with no Billing, 308 Statistics Report, 262 Sybase 5.0, 264 Unwanted Door Readers, 265 Updating Database, 266 Updating Scan NT to ScanNet, 266 Troubleshooting Manual using Billing Invoicing and Payment systems, 309 Windows XP, 202 Series 16K A3.4.5, 140 Shipping Overnight with UPS Red, 379 SST Abnormal Fee Display, 317 Circuit Board Redesigned, 325 Configuration, 325 Field Wiring Troubleshooting, 330 Flash Omega, 325 HP-1 and HP-4, 317 HP-1 or HP-4 printhead adjustment, 328 HP-1 Versus HP-4, 319 Introducing HP-1, 323 Introducing HP-4, 322 Issue Speed, 321 Low Ticket Number, 319 Media Specs, 318 Merchant (hole-punch) Validator, 322 Not In Operation, 316 Paid and Unpaid Grace Time, 316 Re-encode Option, 320 Single Infeed Burster Version A, 324 Small Fonts, 322 Sunlight and Transport Failure, 324 Tickets Sticking Together, 322 Transient Facility Code, 321 Troubleshooting, 315 Version 12 Transports, 319 SST CPU 3/1999, 328 A4.0.10, 326 DIP Switch Settings, 315 Firmware Compatibility, 327 Wiring diagram for 24VDC, 327 SST Omega B1.13.0, 330 B2.2.0, 330 C3.1.1, 329 C3.1.8, 329 SST Omega VC/CC 1.1.2, 330 B2.1.1, 330 B2.5.1, 329 78-0060-4094-9, Ver. 1 Index • 373 B2.6.5, 329 C3.0.1, 329 C3.1.1, 329 C3.1.5, 329 C3.2.2, 328 Sybase, 262 SQL statements, 289 T TagMaster Error Labeling J5, 333 Program the communication and Wiegand card format settings, 333 Programming, 128 Wiring Details, 333 TD-249 A3.3.0, 343 A3.3.1, 343 Blured Time Stamp on Tickets, 341 Feed Motor Continues to Run/No Ticket is Cut, 340 Installing LCD Display, 342 Issuing Long Tickets, 339 Lane Troubleshooting, 337 Manual Issue, 339 More than One Ticket Issued, 339 Not Cutting Tickets Completely/Tickets Folding Over Blade, 342 Not Time Stamping Tickets, 341 Prevent Ticket Jams, 341 Recall Key, 342 Ticket Delays, 342 Ticket not Cut in Proper Location, 340 Tickets Jamming in Chute, 339 Tickets not Cutting Clean, 339 Time Stamp Gains and does not Match Hands on Clock Face, 340 Time Stamp Loses Time or Stops, 340 Time Stamp Weak or Doubled, 341 TD-300 common parts list, 355 TD-300 Series 1.0.0.11, 347 1.0.0.11 to 1.0.0.12, 347 374 • Index 1.0.0.12 to 1.1.0.1, 347 1.1.0.1 to 1.1.1.1, 346 1.1.1.1 to 1.1.2.2, 346 1.1.2.2 to 1.1.3.4, 346 1.1.3.4 to 1.2.0.2, 346 1.2.0.2 to 1.4.1.2, 346 1.4.1.2 to 1.4.5.2, 346 1.4.5.2 to 1.4.6.1, 345 1.4.6.1 to 1.5.0.10, 345 1.5.1.0 to 1.5.1.1, 345 1.5.1.1 to 1.5.2.4, 345 1.5.2.4 to 1.5.3.1, 345 Better Patron Access to Ticket, 351 Cap on Thermostats, 349 Enhancement for Guillotine Cutter, 350 Enhancements, 354 Hardware Changes, 351 Hecon Twin Cutter Enhancement, 352 LED Display Board Rev B Versus Rev C, 350 No Printing on Ticket, 348 One Motor Continues Spinning with No Tickets in Mechanism, 347 Paper Clippings, 356 Prevent Lost Springs, 351 Quality Control Checklist, 352 Que Belt Not Spinning, 354 Retracted Ticket Hopper, 354 Service Mode Tickets, 348 Signs Replaced by Symbols, 351 Ticket Deflector Introduced, 351 Tickets Difficult to Pull, 353 Tickets Jam Before Rotary Cutter, 347 Tickets Shoot Out Ripped, Not Cut, 347 Using LEDs to Test Sensors with Guillotine Cutter, 350 Using LEDs to Test Sensors with Rotary Cutter, 355 Transmit and Receive ICs For all devices, 371 U Universal Power Supply Assembly, 375 UT2 78-0060-4094-9, Ver. 1 Troubleshooting Manual A330, 139 Alien Card, 128 Not Reading, 128 Programming, 127 Tickets to Vault, 365 ValuePass Calculating Central Access/ValuePass Credentials, 369 Creating offline, 369 Minimum Programming, 369 V ValueCard B1.1.2V, 365 Exit Gate Does Not Vend, 364 Introducing, 365 Misunderstandings, 367 Programming at PowerPad, 359 Programming at Spitter Omega, 363 Sending ValueCard Programming from ScanNet, 364 Troubleshooting Manual W Warranty Exchange, 375 Weigand Card Data Configuration, 130 Y Y2K Compliant Firmware Versions, 381 78-0060-4094-9, Ver. 1 Index • 375 376 • Index 78-0060-4094-9, Ver. 1 Troubleshooting Manual oll TollFree: Free: 877-777-3571 877-777-3571 Global Number: 3M 3M Global Number: 512-984-9255 512-984-9255 www.3M.com/ www.3M.com/MVSS MVSS For For sales sales and and service, service, contact contact your your 3M 3M Value Value Added Added Reseller. Reseller: Troubleshooting Manual 78-0060-4094-9, Ver. 1 Index • 377
© Copyright 2025 Paperzz