Xerox Phaser 6510 Mac Software
by admin
Xerox Phaser 6510 Mac Software Average ratng: 7,3/10 3699 reviews
Xerox® Phaser 6510 Color Printer / Xerox® WorkCentre 6515 Color Multifunction Printer Information Assurance Disclosure February 2017 - 3 - Figure 2: 6510/6515 (Back) 1. Download office 2008 mac full. Lower Paper Tray 2. Upper Paper Tray 3. Special Paper Feed 4. Power Button and Optional NFC 7. Pioneer ddj sx drivers for mac. Touch Screen User Interface 8. Document Feeder 9. Phaser 6510 Colour Printer, A4, 28/28ppm, Duplex, USB/Ethernet/Wireless, 250-Sheet Tray,50-Sheet Multi-Purpose Tray, Sold £183.00. Xerox Phaser 6510 Software Release 64.51.1 (MAC OSX). Phaser 6510 Xerox Phaser 6510 Software Release 64.51.1 (MAC OSX) Product support Phaser 6510. Support Drivers & Downloads Xerox Phaser 6510 Software Release 64.51.1.
- Xerox Phaser 6510 Color Printer ® ® User Guide. Page 218: Physical Specifications 499 mm (19.6 in.) 499 mm (19.6 in.) Height 347 mm (13.7 in.) 497 mm (19.6 in.) Weight 24 kg (53 lb.) 31 kg (68 lb.) Standard Configuration Configuration with Optional 550-Sheet Feeder Xerox Phaser 6510 Color Printer ® ® User Guide.
- Take a look at the Xerox Phaser 6510 colour laser printer specifications and discover the latest features, including print speeds of up to 30 ppm.
Error Codes List page 1
Xerox Phaser 6510 Mac Software Windows 10
Xerox 6510 Software
- Code: 002-500
- Description: UI Error RAP
002-500 CUI scan panel UI detection error. - Remedy: 1. Switch off then switch on the machine, GP 4.
2. Ensure that all connectors on the UI assembly, PL 1.1 Item 1 and the ESS Board, PL 18.1 Item 5 (MFP), PL 18.5 Item 5 (SFP) are securely connected. Ensure that all surface mounted modules on the ESS Board are securely connected.
3. Check the wiring between the ESS Board and the UI assembly.
4. Reload the software, GP 9. 5. If the fault persists, install a new components as necessary: • UI assembly, REP 1.1.1. • ESS Board, REP 18.1.5 (MFP), REP 18.5.5 (SFP).
- Code: 003-311
- Description: IIT CDI I/F Mismatch
003-311 During controller initialization, the IIT CDI I/F has insufficient information from the IIT. - Remedy: 1. Obtain the log file using the log tool. Perform 2.6 Log RAP • If there was a reboot after the error had occurred and hence was unable to obtain the log, set NVM (700-530) to “0” to perform log collection and return the NVM (700- 530) to “1” after completing the procedure.
2. Change any possible mechanical settings for corrective actions or detection conditions and repeat the operation.
3. Check the version of Controller ROM. If it is not the latest, download and update to the latest software revision. (Refer to GP 9 Firmware Version Upgrade)
4. Switch the power off then on.Get the procedures for reproducing an error according to the operation that was performed when the error occurred. a. Check the exact occurrence timing during job execution. b. Check the job settings from the Panel. c. Collect other information as much as possible to reproduce the error.
5. Obtain logs immediately after the error has occurred without turning the power off and on. Perform 2.6 Log RAP.
6. The ESS Board rarely fails, contact Technical Support for further instructions.
- Code: 003-318, 003-319
- Description: IIT Software Fail
003-318 IIT software is corrupt.
003-319 Video driver detection fail. - Remedy: 1. Switch off then switch on the machine, GP 4.
2. Ensure that all connectors on the MCU Board, PL 18.1 Item 1 (MFP), PL 18.1 Item 5 (SFP) and the ESS Board, PL 18.1 Item 5 (MFP), PL 18.5 Item 5 (SFP) are securely connected. Make sure all surface mounted modules on both Boards are securely connected.
3. Reload the software, GP 9.
4. If the fault persists, install a new ESS Board, REP 18.1.5 (MFP), REP 18.5.5 (SFP).
- Code: 003-320 . 003-343
- Description: IISS-ESS Communication Fail
003-320 IISS sending error 1 detected by the controller. An abnormal parameter is set as the argument for the send function.
003-321 IISS sending error 2 detected by the controller. After commands were sent twice from the controller, the controller could not receive acknowledgment from the IISS.
003-322 IISS sending error 3 detected by the controller. After commands were sent twice from the controller, the controller could not receive acknowledgment from the IISS.
003-323 IISS sending error 4 detected by the controller. After commands were sent twice from the controller, the controller could not receive acknowledgment from the IISS.
003-324 IISS sending error 5 detected by the controller. After commands were sent twice from the controller, the controller could not receive acknowledgment from the IISS.
003-325 IISS sending error 6 detected by the controller. After commands were sent twice from the controller, the controller could not receive acknowledgment from the IISS.
003-326 IISS sending error 7 detected by the controller. After commands were the controller, the controller could not receive acknowledgment from the IISS.
003-327 IISS sending error 8 detected by the controller. After commands were sent twice from the controller, the controller could not receive acknowledgment from the IISS.
003-328 IISS sending error 9 detected by the controller. After commands were sent twice from the controller, the controller could not receive acknowledgment from the IISS.
003-329 IISS receiving error 10 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-330 IISS receiving error 11 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-331 IISS receiving error 12 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-332 IISS receiving error 13 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-333 IISS receiving error 14 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-334 IISS receiving error 15 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-335 IISS receiving error 16 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-336 IISS receiving error 17 detected by the controller. The NAK that notifies of the occurrence of a transmission failure is received.
003-337 IISS receiving error 18 detected by the controller. There was no response to the power on command sent to the IISS after restoring from power saver mode.
003-338 IISS receiving error 19 detected by the controller. Incorrect argument error for sending.
003-339 IISS receiving error 20 detected by the controller. Transmission establishing error for sending.
003-340 IISS receiving error 21 detected by the controller. Synchronous send error.
003-341 IISS receiving error 22 detected by the controller. Transmission error for sending.
003-342 IISS receiving error 23 detected by the controller. Incorrect argument error for receiving.
003-343 IISS receiving error 24 detected by the controller. Synchronous receive error. - Remedy: 1. Switch off then switch on the machine, GP 4.
2. Ensure that all connectors on the MCU Board, PL 18.1 Item 1 (MFP), PL 18.1 Item 5 (SFP) and the ESS Board are securely connected. Make sure all surface mounted modules on both Boards are securely connected.
3. Reload the software, GP 9.
4. If the fault persists, install a new ESS Board, REP 18.1.5 (MFP), REP 18.5.5 (SFP).
- Code: 003-344
- Description: IISS-ESS X Hotline Fail
003-344 X Hotline failure during power on. - Remedy: 1. Switch off then switch on the machine, GP 4.
2. Ensure that all connectors on the MCU Board, PL 18.1 Item 1(MFP), PL 18.1 Item 5 (SFP) and the ESS Board are securely connected. Make sure all surface mounted modules on both Boards are securely connected.
3. Reload the software, GP 4.
4. If the fault persists, install a new ESS Board, REP 18.1.5(MFP), REP 18.5.5(SFP).
- Code: 003-345, 003-346
- Description: PIO Mismatch RAP
003-345 X PIO Unmatch Fail 1 When a job fail was received from the IISS, an error of the X hot line was detected.
003-345 X PIO Unmatch Fail 2 When IIT image delivered was received from the IISS, an error of the X hot line was detected. - Remedy: 1. Switch off then switch on the machine, GP 4.
2. Ensure that all connectors on the MCU Board, PL 18.1 Item 1 (MFP), PL 18.1 Item 5 (SFP), and the ESS Board, PL 18.5 Item 1 (MFP) PL 18.5 Item 5 (SFP) are securely connected. Make sure all surface mounted modules on both Boards are securely connected.
3. Reload the software, GP 4.
4. If the fault persists, install a new ESS Board, REP 18.5.1 (MFP), REP 18.5.5 (SFP).