![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
|||
Product |
Potentially any platform and/or version of Print Console. It has been encountered recently with some defective Adaptec 2944 UW differential cards on the new Dell platforms. | ||
Platform |
Dell |
||
Operating system |
Windows NT |
||
|
|
|||
Symptoms |
Job fails and the Print Console History screen shows the “SCSI Asynchronous Transfer Request” error message. | ||
|
|
|||
Cause |
This is caused by a faulty SCSI card. Essentially, when Print Console is about to send the raster data to the device over the SCSI connection, the SCSI card needs to be in synchronous SCSI communication mode, not asynchronous mode. For some reason, these cards attempt to send the data in asynchronous mode. In Platesetter electronics there is a QLogic SCSI controller chip that is controlled by the device’s Motorola micro-controller. The way our data path electronics are designed, the ONLY way that raster data can make it into the output device’s imaging engine raster buffers is by using synchronous SCSI mode. In synchronous mode, you simply tell the Qlogic chip how much you want to transfer, and it then streams the SCSI data right through the chip into the raster buffers using DMA. The Motorola micro-controller itself cannot even access the raster data buffers—they are not in its memory space. Asynchronous mode is used for the bus handshaking protocol phase, not for the image raster data transfer phase. |
||
|
|
|||
Solution |
Replace SCSI card. The replacement SCSI adapter from DELL (AHA2944UW/DELL) MUST be, at minimum, BIOS revision 2.20. The older revision 1.32S11 BIOS has a 50% chance of producing the error. Alternate solution: Follow the steps in 2944UW SCSI Controller BIOS Update Procedure—this procedure addresses the problem with BIOS rev.1.32S11 of Adaptec’s 2944UW Differential SCSI controller, installed in PE2400 servers, causing the error mentioned above. |
||
|
|
|||
Technical contact(s) |
|||
Submitted by |
|||
Date submitted |
03 May 2000 |
||