IEC 62286 pdf download – Service diagnostic interface for consumer electronics products and networks – Implementation for IEEE 1394

IEC 62286 pdf download – Service diagnostic interface for consumer electronics products and networks – Implementation for IEEE 1394
1 Scope
This International Standard specifies the requirements that have to be implemented in futureproducts that incorporate a digital interface, and service diagnostic software developed forthese products.The Service Diagnostic Interface (SDl) requires the use of a PC (desktop orlaptop) into which service diagnostic software can be loaded.A part of this PC software has tobe standardised while another part of this PC software is manufacturer/product related.
To reach a common approach in servicing all products from all manufacturers, it is necessaryto standardise specific items in the products (Device Under Test/DUT) as well as in thediagnostic software on the PC.
The Service Diagnostic Interface (SDI) is based on the lEEE 1394:1995 specification becausethis interface will be used in most future products. The use of this connection and existingcommunication protocols enable implementation in products at low cost, and gives maximumflexibility and efficiency.
The sDl consists of:
. Specific hardware and software requirements of the DUT.
Specific requirements of the PC:
– the Service software,
– an lEEE 1394 interface (to be built in if not already present).The connection between the PC and the DUT.
This specification is a minimal specification necessary to be able to carry out computeriseddiagnosis and covers the standardised software of the PC as well as the standardisedsoftware and provisions in the DUT.
lf an IEEE 1394 interface is present on the product，then the requirement for productidentification as described in’ this document ‘(see 6.3) is mandatory. In addition，allcommunication for any service application should go through the IEEE1394 interface only, asdescribed in this document (in clause 7).
2Normative references
The following referenced documents are indispensable for the application of this document.For dated references, only the edition cited applies. For undated references, the latest editionof the referenced document (including any amendments) applies.
IEC 61883-1:2003,Consumer audio/video equipment – Digital Interface – Part 1:GeneralIEEE 1212:2001,Microprocessor Systems – Control and Status Registers(CSR): Architecturefor microcomputer buses
IEEE 1394:1995,IEEE Standard for a High Performance Serial Bus – FirewireIEEE 1394a:2000，IEEE Standard for a High Performance Serial Bus –
Amendment 1
3Terms, definitions and abbreviations3.1Terms and definitions
For the purposes of this International Standard, the following terms and definitions apply.
3.1.1
configuration ROM
area of memory within an IEEE 1394-enabled device which holds specific information aboutthe device,as defined in lEEE 1212.Device information is held in a hierarchy of directorieswithin the ROM
3.1.2
EACEM unit directorysee unit directory
3.1.3
Hw_version
hardware version.IEEE 1212 optionally uses this to identify diagnostic software
3.1.4
instance directory
second level in the directory hierarchy. The instance directories provide a method to groupunit architectures (software protocols) to identify shared physical components.This directorycontains the offset into memory of various Unit directories, including the EACEM unit directory
3.1.5
IEEE1394 repeater
another lEEE 1394 device in the network capable of relaying or repeating data. This devicemay have more lEEE 1394 sockets and can provide a suitable connection into the system
3.1.6
Key_ID
Key iDentifier. IEEE 1212 use this to identify the contents of the remaining 3 bytes of aquadlet in a directory. Key_ID is 6 bits long: the proceeding 2 bits are the type，whichidentifies whether the data in the following 3 bytes is immediate (i.e. they contain the actualdata) or whether the 3 bytes are an offset to another place in memory
3.1.7
minimal Ascn
IEEE 1212 defines a limited set of Latin characters that can be used for text. The particularset specified in SDl uses the 1 byte coding specified in lEEE1212
3.1.8
model_ID
model IDentifier. IEEE 1212 optionally provide this to identify the model.The model shouldrepresent a family or class of products and should not be unique to individual devices