Lotem 800 Family Diagnostics Version 3.75.x Release Notes The Lotem 800 Diagnostics for Version 3.75.x is a software package that enables testing the hardware of the Lotem 800 Family products: Lotem 800 engine equipped with a thermal head, with or without MCU or Proofing capability, (Lotem 800v/Quantum/MCU/Spectrum), locally as well as from remote. The diagnostics package is included in the official Lotem 800 Family version 3.75.x CD-ROM. This document covers the following issues Overview Installation and activation Diagnostics guidance Diagnostics startup process Main test subjects Coverage level Feedback and contact information

Overview

The JOIND - Java Over the Internet Diagnostics - is a Creo client/server diagnostics controller that runs either locally or over a TCP/IP connection. It is an online diagnostics tool for running tests on local and remote nodes connected over the Internet or a modem. The JOIND is the engine for running the Lotem diagnostics.

The user interface of the JOIND includes two main components:

• A hierarchical tree control that represents the functionality of the application activated on the server computer. Functions of the application are selected and executed from this tree. The tree content is dynamic and is suited to the application and to the environmental conditions that may change between sessions.
• Menu options enable the control of operations that are done on the tree. The menus are composed of fixed options, relevant for all applications, and of dynamic options that vary between applications.
  

Installation and Activation

The official Lotem 800 Family version 3.70.x CD-ROM includes both expose and diagnostics applications. The size of the diagnostics software is approximately 55MB and is located under the expose application environment.

When the CD installation is complete, the diagnostics icon will be placed both on the PC desktop and in the Start menu (similar to the expose application). Double-click the diagnostics icon to start the application.

Note: Expose and diagnostics applications cannot run together. Before activating the diagnostics, verify that the expose application is closed.

Diagnostics Startup Process

Once it has been initiated, the startup process includes:

• Verification of communication between the PC and the platesetter.
• Embedded software is initialized and loaded (if needed). The DDB is initialized only when accessing the DDB chapter in the test tree.
• Electronic boards are initialized.
• Hardware configuration is identified.

The failure results of these sub processes (if they exist) are summarized in the Startup Process dialog, shown automatically when the startup process is completed. In addition, a red/green indicator is shown in the right side of the diagnostics main dialog.

Note: During the startup process, the Plate Location dialog is displayed. Since the existence of the plate in the platesetter limits the tests, it is very important to select the correct location of the plate (if it exists), otherwise, the platesetter may be damaged. If the plate is loaded, it is recommended to use the 'Unload Plate'button to unload the plate.

Main Test Subjects

The following components are tested:

• Power supply
• Boards
• Platesetter

The platesetter hardware coverage is done by the bottom-top approach (an integrated approach).

• Bottom-top approach
  The default test sequence goes from the simple and basic hardware (P.S. and communication) through the platesetter boards (opto-mechanic drivers) to the main platesetter units (motors, detectors, etc.). It is recommended to fix the problems in the sequence that they appear in the diagnostics test tree.
• Integrated Approach
  Every platesetter unit receives input and sends output. When selecting a unit (FRU) to be tested, the diagnostics automatically checks these connections in order to maximize the coverage of the selected unit. In advance, it is possible to change (through the JOIND menu) the 'integrated' mode to the 'stand alone' mode.
  

Coverage Level

Additional components tested in this release:

• Local3, left and right
• Enable/disable for focus, resolution and spiral motors
  Note: If the registry field is '0', the diagnostics tree will not include those tests
• Platesetters with Omron^® interlocks
• New loading system motors
• Local3 MCU loader
• Quantum platesetters (drum & carriage units)
• Diagnostics for MCU

Systems and subsystems that are not tested in this version:

• DSM board
• Optic head
• Loading System's vacuum section
• Vacuum only for Lotem with GTO (Omron)

Note: When testing boards in the board category, the parts that cause the platesetter's movements are not tested. Only in the platesetter categories, is everything checked without any limitations.

Feedback and Contact Information

Diagnostics tools are developed for all Creo devices and platforms. We will continue to be in close contact with the field in order to improve the hardware coverage testing and the user interface. Your feedback on the Diagnostics is extremely important to us. Therefore, a special report template is available in the diagnostics root directory:

• Bug Report.doc (in Word 97 format)
  
• Bug Report.txt (in plain text format)
  

A completed bug report and any other comment/request/remark/question, can be e-mailed to diagnostics@creo.com