Lotem800V Version 3.60 and 3.70 Release Notes - December 2002 Release Notes The Lotem800 Diagnostics -for Version 3.60 & 3.70 is a software package that enables testing the hardware of the Lotem800 products family: Lotem800 engine equipped with Fiber or Thermal Head, with or without MCU or Proofing capability, (Lotem800v\Quantum\MCU\Spectrum), locally as well as from remote. The diagnostics package is included in the official Lotem800 Family version 3.60.x & 3.70.x CD-ROM. This document covers the following issues Overview Installation & Activation Diagnostics Startup Process Main Test Subjects Coverage Level Feedback and Contact

Overview

The JOIND - Java Over the Internet Diagnostics - is a Creo Client/Server diagnostics controller that runs 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 & Activation

The official Lotem800 Family version 3.70.x CD-ROM includes both Expose & Diagnostics applications. The size of the Diagnostics software is about 55 MB and it is located under the Expose application environment.

When the CD installation is complete, the Diagnostics icon is located on the PC desktop and in the 'Start' button (similar to the Expose Application). To activate the Diagnostics application, double-click the Diagnostics icon.

Note: Expose and Diagnostics applications cannot run together. Before activating the Diagnostics, verify that the Expose Application is off.

Diagnostics Startup Process

The startup process of the diagnostics, once it is initiated, includes:

• Verification of communication between the PC and the Machine.
• 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 exist) are summarized in the Startup Process window that is shown automatically when the startup is completed. In addition, a red/green indicator is shown in the right side of the diagnostics main screen.

Note: During the startup process, the Plate Location dialog is displayed. Since the existence of the plate in the machine limits the tests, it is very important to select the correct location of the plate (if it exists). Otherwise, the machine 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
• Machine

The machine 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 machine boards (opto-mechanic drivers) to the main machine units (motors, detectors, etc.). Fixing the problems in the sequence they appear in the diagnostics test tree is recommended.

• An Integrated Approach

  Every machine 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:

• Local 3 Left and Right
• Enable and Disable for Focus, Resolution, and Spiral motors
  Note: If the registry field is "0", the diagnostics tree will not include those tests
• Com 6 External Loop Back for the NUC Board
• Com ILp External Loop Back for the NUC Board
• Support Machine with Omron
• Support MCF Revision "C" (Power supply, all sproc, xilinx done & 12v)
• MCF Revision “C” Comp Level P & N (Not Full Diagnostics)
• MCF Revision “A” Comp Level P
• New loading system motors
• DDB Fully tested, (under explicit direction from engineer.)
• Local 3 MCU Loader
• Quantum machine (drum & carriage units)
  
  Systems and subsystems that are not tested in this version:
  • DSM Board
  • Optic Head
  • Loading System's Vacuum Section
  • MCU System (excluding the Local3 of the MCU which is tested, if installed.)
  • Vacuum only for Lotem with Gto (Omron)

· Note: When testing boards in the Boards category, the parts that cause the machine movements are not tested. Only in the Machine categories, is everything checked without any limitations.

· Note: Occasionally, when leaving the diagnostics session, some 'exceptions' pop up on the screen. Press "Ignore" button until the diagnostics application is totally terminated.

Feedback and Contact

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 on the Diagnostics root directory:

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

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