IEC 62286-2003 pdf – 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 future products that incorporate a digital interface, and service diagnostic software developed for these products. The Service Diagnostic Interface (SDI) requires the use of a PC (desktop or laptop) into which service diagnostic software can be loaded. A part of this PC software has to be 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 necessary to standardise specific items in the products (Device Under Test/DUT) as well as in the diagnostic software on the PC. The Service Diagnostic Interface (SDI) is based on the IEEE 1394:1995 specification because this interface will be used in most future products. The use of this connection and existing communication protocols enable implementation in products at low cost, and gives maximum flexibility and efficiency. The SDI consists of: • Specific hardware and software requirements of the DUT. • Specific requirements of the PC: – the Service software, – an IEEE 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 computerised diagnosis and covers the standardised software of the PC as well as the standardised software and provisions in the DUT. If an IEEE 1394 interface is present on the product, then the requirement for product identification as described in this document (see 6.3) is mandatory. In addition, all communication for any service application should go through the IEEE 1394 interface only, as described in this document (in Clause 7). 2 Normative 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 edition of the referenced document (including any amendments) applies.
4 Different types of service diagnostics 4.1 Stand-alone products In this situation, a connection is made between the diagnostic PC and the DUT, where the DUT is from any manufacturer and of any type. 4.2 A/V or multimedia network In this situation, a connection is made between the diagnostic PC and a network of A/V or multimedia products. In an A/V or multimedia network, several different products are interconnected and not all of them are necessarily from the same manufacturer. In this case, the SDI must be able to list the products on the network, detect which product is causing a problem, and diagnose the product concerned. 4.3 Remote diagnosis In addition to the configurations described above (stand-alone product or network), a link can be made (for example via telephone, Internet, etc.) between the diagnostic PC in the workshop and a DUT/network at the customer’s home. Therefore, if a product has both an IEEE 1394 interface and a remote connection capability, this product should be able to transfer the diagnostic data, as described in this document, through the remote connection. It has to be specified how this type of communication is carried out, and which level of diagnosis will be possible. These items are not in the scope of this document, and will be defined later on. 5 Specification of the SDI 5.1 General The SDI consists of: • hardware and software, both in the DUT and in the test equipment (“tester”); • the connection between the tester and the DUT. The total SDI can be divided into the elements specified in 5.2 and 5.3.
Tester software requirements 6.1 Interface to manufacturer service program The common application, from which a possible example is described in Annex A, is able to launch the manufacturer’s service program; the manufacturer’s service program shall fulfil the following requirements: The manufacturers service program shall be installed in a subdirectory located immediately under the main SDI installation directory. The subdirectory name shall be that of the manufacturers ID. The service program is launched with the following command line: vvvvvv<SEP>SPvvvvvv/SDI/GUID:hhhhhhhhllllllll/CON:z/HWV:wwwwww • <SEP> is the standard file-system sub-directory separator of the tester platform, for example “\” on Windows . • vvvvvv is the ASCII representation of the Vendor_ID in hexadecimal. • /SDI informs the service program that it has been started from the common application. • /GUID:hhhhhhhhllllllll, where “hhhhhhhh” is the ASCII representation of the Company_ID + Chip_ID_hi in hexadecimal, and “llllllll” that for Chip_ID_lo, together making the GUID. • /CON:z, where “z” is the ASCII representation of the connection type (“R” = remote, “D” = direct). • /HWV:wwwwww, where “wwwwww” is the ASCII representation of the hardware version in hexadecimal (if available).