Browse Prior Art Database

SELF TEST OF A DISTRIBUTED MICROPROCESSOR CONTROL SYSTEM

IP.com Disclosure Number: IPCOM000025125D
Original Publication Date: 1983-Oct-31
Included in the Prior Art Database: 2004-Apr-04
Document File: 2 page(s) / 70K

Publishing Venue

Xerox Disclosure Journal

Abstract

A control system for a copier or reproduction machine in which a master controller and a number of sIave controllers are connected by a serial communication line. All controllers have on-board microprocessors and individual self-test routines, the self-test routines including an initial routine for testing the controller memory core followed by routines for testing the controller hardware functions. The master controller is given control of a hardware reset line to all the slave controllers.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 70% of the total text.

Page 1 of 2

XEROX DISCLOSURE JOURNAL

A control system for a copier or reproduction machine in which a master controller and a number of sIave controllers are connected by a serial communication line. All controllers have on-board microprocessors and individual self-test routines, the self-test routines including an initial routine for testing the controller memory core followed by routines for testing the controller hardware functions. The master controller is given control of a hardware reset line to all the slave controllers.

When power is first applied to the machine, the master controller commences to execute its own self-test routines. Upon successfully completing testing of the memory core portion of the master controller, the master controller releases the reset line to the slave controllers which in response thereto begin execution of their own self-tests. When the master completes its self-tests, timed such that the slave controllers have also completed their own self-tests, the master controller attempts to communicate with each of the slave controllers over the serial communication line. If a slave controller fails to respond, the master controller knows that the slave controller has failed the core port.ion of its self-tests, and displays this condition to the machine Tech Rep. Where communication is established, each slave controller is queried by the master controller to determine if the slave controller has passed or failed the non-core portion of the self-tes...