1 / 7

Page 1 of 7

Next Screen, Page Down. Common Problems and Resolutions. Initial Scanner Installation Problems The initial installation of the (TS215- TS230) and the USB drivers is where the majority of problems show up.

glynis
Download Presentation

Page 1 of 7

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Next Screen, Page Down Common Problems and Resolutions • Initial Scanner Installation Problems • The initial installation of the (TS215- TS230) and the USB drivers is where the majority of problems show up. • Be sure that the TS230 Driver Auto Install program has been run, then make sure the scanner is connected through the USB cable to the PC and that the PC is up and running. Verify that the scanner is plugged into a USB 2.0 port. • (A USB 1.1 port can cause delays of over 30 seconds to complete the firmware load). • Note: Review the various documents in the drivers folder regarding the certified driver. This is required for these models. • Power on the scanner and observe the top right LEDs (This is the normal sequence to expect). • The right LED should turn red, initially indicating that power is getting to the scanner. • When an application acquires the scanner, the right LED will turn green. • The scanner is now ready to use. • Right LED Does Not Come On – Check the power connector. The power supply should show an LED lit up, indicating that • it has power. Be sure you are using the correct power supply. 30 VDC input into the scanner. • Left LED Does Not Come On – The left LED is used to indicate the presence of a document in the entry pocket when the right LED has turned green. Be sure the document is moved far enough into the pocket and is down against the base plate. Use the HTL demo program to view the ‘Doc’ sensor activity. See the Problem Diagnostic section. • Blinking Right LED – This indicates an error condition. Possible power supply (low voltage) or bad motherboard. • ScanDemo - Error When Launching Application - • A solid failure to bring up the Scandemo program, indicated by the error message on the screen that it cannot locate the • Scanner, can fall into several categories. Ensure that the USB cable is connected, the scanner is powered on and then • Reboot the PC. In some cases it may help to disconnect other USB devices attached to the same PC. • Start Scandemo.exe from it’s own directory. • (–125) Error This usually indicates the scanner is not seen by the PC. Recheck the power and USB connections. Turn the scanner power switch off, then back on and observe the LEDs on the top panel. It should follow the sequence defined previously. Also, check the PC Device Mgr to be sure USB support is enabled and the ports are active. • Note: The device will show as ‘TSDevice’ or ‘Tellerscan’ in Device Manager for certified drivers. If it does not show as one of those devices, try reloading the USB driver Utility. Turn off any locally attached printers to test for driver interference. Page 1 of 7

  2. Next Screen, Page Down Common Problems and Resolutions Document Feeding Problems – (Note: most jamming and feeding problems can be eliminated or avoided by proper and timely cleaning, and periodic adjustment of the double feed roller setting) There are 5 common feeding error codes that show up using ScanLite. These same codes should also be displayed by any imaging application using the TS230 scanner. (-212) No checks in the feeder – This occurs when a scan cycle has be initiated, but no documents are detected in the entry area. While this error can happen simply by manually selecting a scan with no documents present, it could be that the ‘Check Present Sensor’ is not functioning properly. Check that it is not blocked and appears to cycle on and off when a document is placed, then removed from the entry hopper. TIP: A wooden toothpick can be carefully inserted under the outside LED (with the left cover removed) to raise the LED off of the base plate a small amount. (-216) No feeding. Unable to load document. –This occurs when the first document in the stack did not make it to the Sync sensor in the given amount of time. Typical causes are that the document(s) have a heavily curled or bent front edge or front lower corner. This causes the documents to catch or be slowed up getting through the double feed rollers. If you have not been getting piggy backing of other documents, then review the Double Feed Roller Adjustment for loosening the setting ½ turn (for TS230) and retest. The scanner rollers may need to be cleaned (see the cleaning procedure section) or the eyebrow modified (see the adjustment section). NOTE: Weak or poor feeding could be caused by a worn or intermittent DF clutch and shaft. This is the shaft that mounts the inner, dense foam separation roller. The Sprague clutch may need to be replaced along with the shaft. (-217) Two or more documents in the check path –This error is probably the most common. It can be caused by scanning very slick, new documents or documents stuck together with static. Check the Double Feed Roller Adjustment and tighten 1 turn (TS230) and retest. See the adjustment for the TS230. TIP: Sometimes proper document preparation is needed by handling the documents, sorting through them or providing a slight indent so the papers are not so flat. This helps to remove excess static and to allow better separation. (-220) Document is jammed in track– The-220 error code is a fairly common error and can occur for a variety of reasons. This typically indicates that a document was stopped in the track, slowed in the track or did not fully exit on time. See the next page, ( page 3), for more detailed information for causes of -220 errors. (-553) No Print Head – Check that an ink jet cartridge is installed. If it is, pull out and reseat the cartridge. Try a new cartridge. The ribbon connector cable going to the main board maybe need to be reseated or the main board may be bad. Page 2 of 7

  3. Next Screen, Page Down Common Problems and Resolutions • Document Feeding Problems (Causes for -220 errors) • First, define the jamming symptom- Where does the leading edge of the document stop when the error occurs? • The four typical areas are: • a) It did not make it to the sync sensor - look for a bad or misaligned sync sensor which shows active all of the time. • b) It’s just after the first turn - this could be a ‘running out of torque’ condition caused by the main drive motor making a high pitched sound right before the jam condition. Check the path rollers and idlers for binds. Rotate one of the main drive rollers to move the entire belt drive and feel for abnormal effort needed to turn the rollers. This could be caused by a binding bearing, idler or stepper motor. Check if it runs OK with the center cover removed. • TIP: You can turn the last main drive roller by hand and walk a document through the path slowly to determine if it’s catching on something. Use ScanDemo or ScanLite and the Eject function to run documents through the scanner at full and half speeds to test under power. • Check that the application is using TS2DLL.DLL (V4.4.3 or higher). • Important: The TS230Firmware.bin file also needs to be checked. It should be at a compatible level with the TS2dll.dll. • Check with Digital Check if there is a question about code levels. Typically, if the demo code works and the application does not, then a code level mismatch is likely. Since late 2007, TS2dll V4.4.3 and firmware V1.0.3.0 (319,384 bytes) is stable and is what comes with the API files in V8.70. The TS230 works best on API code V8.7X or newer. • It’s just before or entering the scanheads - There could be interference from the ink jet platform or the MICR read head.Visually look down from the top to observe the clearances. You should see some clearance where the ink jet platform is not catching the leading edge and that the MICR head backup roller is touching the head, but rotates freely. Check for debris • by the MICR head area. Open the scanhead area to check for debris on the walls or lens and rollers hung up or out of position. • d) The document goes all of the way through to the exit pocket and then gives the error – • - If a -220, this is referred to as the ‘False -220 error and is not a symptom that should come up with a TS230 model. • - If a -607, this is an error as a result of the firmware and TS2dll being mismatched. Check for current levels per above. Page 3 of 7

  4. Next Screen, Page Down Common Problems and Resolutions Image Quality Problems - Run a TIF image and a 16 shade gray scale of the same check as a reference point before you start. Heavy Background – Make sure the scanhead lens are clean (see Cleaning section). Use ScanDemo to run a 200x200 TIFF image with Edge Detection turned off (use the 200x200 mode). Then run the same check using TI200x200 mode (see the Running ScanDemo section). The 2nd image should be acceptable and show little or no significant background. If it still looks too dark, run the Scanhead calibration procedure. Check and reseat the connectors going to the CIS modules, if they are not taped to secure them. Blotchy or Faded Areas - Scan a standard, clean background check using 200x200 16 shade grayscale mode. This should give you a reference image that shows whether the image has a uniform shading or exhibits voids or streaking across the document. If it does not look fairly uniform, then run the Scanhead calibration procedure (see Maintenance Program section). Problem With Ink Jet Buildup On Rear Scanhead Lens The symptom is a shaded line across the rear image where the ink jet endorsement line is. The build up may be caused by the type of documents being endorsed. Slick surfaces may not allow the ink to dry in time. Determine the frequency of build up and the type of documents that are typically scanned. Check where on the document the endorsement starts. It may be starting early or too close to the leading edge. Sample of ink build up on rear scanhead lens Page 4 of 7

  5. Next Screen, Page Down Common Problems and Resolutions Black Front or Rear Images – If experiencing black or mostly black images, check and reseat both ends of the CIS wiring connectors. On early models, pay particular attention to any debris that may be shorting the top two solder pins shown below. Clean off any debris and then power off the scanner and back on to retest. If the black images come back or cannot be corrected, replace the CIS wiring harness that goes from the CIS to the motherboard. Page 5 of 7

  6. Next Screen, Page Down Common Problems and Resolutions Broken ‘H’ bracket idlers and Outer Wall – Constant jamming may be caused by a cracked idler bracket or idler bracket mounting on the outside wall after the separator rollers. Any of the six idlers could have a cracked mounting on older units built between summer of 2006 and the end of October 2006. The newer style of idler material is a light gray. The older units built prior to this time frame with black plastic are not affected. Replace all of the six idlers with the newer style. The typical failure is the first idler or a cracked wall mount. First idler bracket Page 6 of 7

  7. Next Screen, Page Down Common Problems and Resolutions MICR Errors – Test the MICR with a set of known good checks to use as a reference. Random MICR Errors – Random @ symbols showing up along the top of the Scandemo screen indicates an erratic failure. Check that there are no power supply or other electromagnetic devices within six inches of the scanner. Run through the cleaning procedure (see Supplies & Cleaning section) to properly clean the entry and main drive rollers so that they are not slipping when moving the document. Visually look down where the MICR read head is in the outer path. The spring loaded backup roller should be visibly touching the MICR read head. Make sure that the ink jet platform is not skewed or interfering with the document path. Important - Review the Adjustment & Removals section regarding drive belt tension. Too tight and the belt can ‘cog’ or bind. Replace all older style tan colored belts. Too loose and the slack can cause jitter when a character is running across the head. Note: Review a comment in the Maintenance section about changing the bias setting for the MICR in the config file. Specific MICR Errors - @ symbols that continually show up in the same position on the MICR line could indicate a drive path problem. Check for binds in the drive belt by turning it through several complete cycles. Review the Adjustment & Removals section regarding double feed adjustment. Also look for binding or broken idler rollers in the first corner or something catching the leading edge of the document in the scanhead area. The TS230 double feed adjustment may be too tight. Ink Jet Testing – You can use ScanDemo to test the inkjet. Select the Endorse / Sort button. Enter in text or one of the sample BMP files included in the Samples folder on the CD into the field to test the print function. Use can also use Scanlite and select ’Endorse’ to print a predefined print string on the document. The ink jet cartridge may need to be reseated by carefully removing it and re-inserting it. Be sure that the cartridge snaps into place. See TS230 Service Manual section 5.5 The ink is water based so use a damp cloth to wipe across the nozzles horizontally to clean the print head. MISC: Scanner stops talking to the PC – Symptom -The scanner will appear to disconnect from the PC when sitting idle for a period of time. Resolution – If you have not run the V1.8 USB Utility or newer, you can turn off the Power management feature on the PC operating system manually. Turn off the Power Mgmt feature for each USB Root Hub under Windows Device Manager for USB Devices. Open Properties for each Root Hub, then the Power Mgmt tab. Reboot the PC. Page 7 of 7

More Related