Dolev 4press - Troubleshooting & Diagnostics
Diagnostics Overiew

Diagnostics Check
Diagnostics Files
System Requirements
Diagnostics Configuration Modes
The Diagnostic Handler
The CKPRO external program to test the PC

Diagnostics Check

The Diagnostics checks the following units:

The Electronics Unit:
- HOMC - OPTICAL MECHANICAL CONTROLLER.
- CRI - CONTINUOUS RESOLUTION INDEXER.
- STROBE5
- DRIVERS:
  - DC Motor driver
  - Spinner DC Brushless driver
  - Stepper driver
INTEGRATION – Power Supplies, Panel, Signals Between boards, Com Ports, Cassettes ...
MECHANICS – Motors, Detectors, Encoders and etc...
OPTICS – Ldr, Ldt, Nd Filter (Static and Dynamic Optics)

Diagnostics Files

Diagnostics is loaded from 1.44 MByte diskette.

Diagnostics consists of the following files on two diskettes:

COMMAND.COM	Dos 6.20 system file. (With 2 more Hidden Files)
AUTOEXEC.BAT	Batch file which is activated automatically after the BOOT and runs the Diagnostics in the Configuration Mode defined by the SETUP.
CONFIG.SYS	Configuration file for DOS which activates ANSI mode. SMARTDRV.EXE (DiskCache program).
SETUP.EXE	Setup Utility for Diagnostics Configuration Mode (see section Diagnostics Configuration Modes below).
DIAG.EXE	Diagnostic Tests Program.
UTIL.EXE	Utilities Program for Adjustment, Operation, etc...
RUNBATCH.BAT	Batch file to run external programs and return to UTIL.EXE
DIAG_REM.BAT	Batch file for remote RS232 communication with DIAG. This batch is activated with port number & Baud Rate parameters. Example: diag_rem 1 9600.
DIAG_BAT.EXE	Linking Program Between Diagnostics and Application.
DLIST.EXE	External program to list DOS files.
DIAG.DOC	General Documentation (this file).
DIAG.TST	Tests Description (in use by "LC" List Current command).
OMC.XIL	OMC Xilinx configuration file.
CRI.XIL	CRI Xilinx configuration file.
STROBE.XIL	STROBE Xilinx configuration file.
2018MASK.XIL	Mask file for 2018 Xilinx.
3030MASK.XIL	Mask file for 3030 Xilinx.
OMC.WCS	OMC 80196 Code file.
CRI.WCS	CRI 80196 Code file.
OMC_MEM.WCS	OMC 80196 Code file.
CRI_MEM.WCS	CRI 80196 Code file.

Subdirectory WIN	DIAG_TRM.EXE - Windows program to run Terminal Emulation. DIAG.TRM - Diagnostics Setup for Windows Terminal.

Subdirectory DOS HIMEM.SYS -	SMARTDRV.EXE - DiskCache Utility. (not included in version 1.2A) ANSI.SYS - MODE.COM - Configures System Devices. In use Before CTTY.

System Requirements

Free Base Memory - above 400 KB.
Diagnostics Programs use also the Extended Memory (if exist) for Disk Cache and Dynamic Overlays.
Floppy Drive 3.5" 1.44 MB (see Diagnostics Files section above).
Typing and Display I/O Devices depend on Configuration Mode.

Diagnostics Configuration Modes

Diagnostics can be operated in one of the following configurations, shown in the figure below and described in the following table.
Run SETUP.EXE only to Change the Configuration Mode.
1. Default (factory setting) Configuration Mode is PANEL.
2. There are three ways to run SETUP:
  1. In LAPTOP (or External PC or HADAS (Monitor Mode)):
            - Insert the DIAG diskette into the LAPTOP floppy drive.
            - Type "A: <Enter>" to change to floppy drive.
            - Type "SETUP <Enter>" to run the program.
  2. From RS232 Emulation Modes (HOST, DIRECT, LAPTOP) -
            - Activate the Diagnostics.
            - Type "Q <Enter>" to Quit from Diagnostics.
            - In the DOS prompt Type "SETUP <Enter>".
After the Change of the Diagnostics Configuration Mode,
User must Verify that the DIAG diskette is in the HADAS and Reboot the HADAS (Switch Off than Switch On).

diag1.gif (6338 bytes)
TABLE 1 – DIAGNOSTICS CONFIGURATION MODE

diag2.gif (4615 bytes)
DOLEV 4PRESS DIAGNOSTICS CONFIGURATION MODES CONNECTIONS

The Diagnostic Handler

The Diagnostic Handler is an on-line interactive program, enabling access to the diagnostic tests of the DOLEV plotter. All the diagnostic tests are stored on the disk, and are executed by the Handler.
The Handler is a complete service/maintenance tool enabling in-depth diagnostic testing.
The Handler uses the following symbols:

1-9	The numeric character that activates one of the following: BRANCH - name with all capital letters. Test - name with small letters. If the BRANCH is activated the new menu will appear. If the Test is activated the status PASS/FAIL will be appear after the test execution.
/	Short Batch operation of a specific sub-menu.
//	Long Batch operation of a specific sub-menu.
R	(Return) Move to the previous system utilities menu
B	(Back) Move up one level in the test tree structure
H	(Home) Move to the top level of the test tree
Q	(Quit) Quit from the diagnostic program
FL	(Loop Flag) For Loop Operation
EM	(Error Message) To observe the error message buffer after test/tests failure. Type 'R' to Return to main menu.
EE	(Error Buffer) To observe the error buffer after test/tests failure. Type 'R' to Return to main menu.
LO	List Output File (see FI). In DIAG.EXE -> DIAG_OUT.TXT In UTIL.EXE -> UTIL_OUT.TXT * the last executed test has been written to file.
LC	List Current Test option lists the help on the active (with arrow on it) test, so user can read about the test without run it.
?	in Utility describes additional options in UTIL handler.
FN	SingleStep Flag toggle (see FA).
FI	FileOut Flag toggle (see FA). Use LO to see the created file.
FO	shOwcode Flag toggle (see FA).
FA	Assistance Flag is been now widely used by the program, so some important results can be displayed, even the test PASS. Example: DcVoltage Test with the FA (Flag Assistance option) will dispaly all power supplies results on the screen. Perform: FA <CR> FN <CR> x <CR> to run the test which index is x. Because of the single line use for Assistance results, for the test with several results use "FN" - SingleStep Flag, or "FI" - Flow to Disk flag. Note that "FN" or "FI" flags are active only when combined with "FA" or "FO" flags.

The CKPRO external program to test the PC

DIAG_CPU diskette is the general package, common to all projects, which are based on PC: HADAS, DOLEV 800, TELEPRESS ... etc.
The program can be used to check the LAPTOP also.
Note that the MEMORY and HardDisk test might take long time (depends of the size).