Overview | Software Location | Activation | User Interface | LOTEM | Menu Options | Shortcut Buttons | See also links

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 diagnostic tool for running tests on local and remote nodes connected over the Internet or by a modem. JOIND runs under any Windows platform (2000/NT/98/95), and it is currently used as the Lotem family diagnostics tool. The JOIND is used at the manufacturing plant, at the machine integration lines and in the field.

 

Instructors, field engineers, Response Center personnel and others involved in supporting the Lotem platesetters should be acquainted with the JOIND diagnostics tool. Using this tool is highly recommended during the troubleshooting.

 

The JOIND supports three main user levels - User, Service and Expert (Manufacture/Field). System behavior varies according to the current user level. The difference is mainly in the menu options available for each user and in the level of messaging. Although it is possible for any user to use the system at any level, we do not recommend doing so. Field needs are different from manufacturing needs. At all levels, the same hardware is tested, but the results are shown in different detail, depending on the level selected.

The JOIND system is comprised from three main components: 

 

• A Client Component

The JOIND Client is executed on the client computer over a Java Virtual Machine (JVM). It is the front end of the JOIND system, and it passes user requests to the JOIND Server, which may be located on the same PC, or on a remote computer that is being diagnosed. 

• A Server Component

The JOIND Server, JServer, is executed over the Java Virtual Machine (JVM) on the remote computer (for example, the Lotem) that is being diagnosed. JServer negotiates between client requests and the required diagnostic application on the server (remote) computer. It is not necessary to activate JServer when running diagnostics locally.

• Diagnostic Applications

The Diagnostic Applications are located on the Creo platform, the server. The application(s) receive and execute test requests and return an appropriate status responses. Lotem 800 diagnostics and Lotem 400 diagnostics are two examples of diagnostic applications.

Software Location

The JOIND Diagnostics is not distributed as a stand-alone application. It is part of the S/W package that is installed on the Creo device. For example, for the Lotem 800 it is installed with the Lotem Software Kit.

However, it is possible to download a JOIND client that enables you (1) to run a demo mode of the JOIND on any Windows-based computer, and (2) to connect as a client to a JOIND Server on a Creo device (e.g. Lotem) and test this device from remote. The JOIND Client is available here, and the JOIND Demo - here.

  Activation

Note
Before using the JOIND diagnostics for the first time on a Lotem machine, it is required to load the Lotem application and then to close it. After this, the diagnostics can be loaded and used.

Running Diagnostics Locally

A JOIND local session does not require connection to other computers. To run JOIND locally, do the following:

1. After installation of the Lotem Software Kit, two buttons appear on the desktop: the Lotem application button and the diagnostics button.  Before you can run the diagnostics, close the Lotem application. Double click on the Diagnostics button and the software will load. If the Diagnostics button is not available on the desktop, locate the diagnostics directory on the hard disk, and double-click the Joind.bat.
   
   Note
   The JOIND can receive various command-line arguments that influence its behavior.
    

2. In case of the Lotem, the diagnostics will load without further interaction with the user. However, in some cases you will get the JOIND Startup dialog. On Page 1 of the JOIND Startup procedure enter localhost in the Name/Address of Server field, and click Next:
   
   
   
   

3. From Page 2 of the JOIND Startup procedure, select a device from the Device For Testing list and click Finish:
   
   

Note
In case of the Lotem diagnostics, The software asks the operator whether there is a plate in the Lotem. The dialog even includes buttons to open the doors to check the plate's position. If these is a plate, then the software automatically disables the relevant test for drum speed, etc.

Running Diagnostics Over a Modem

In this configuration, both sides of the connection communicate through a modem. The client PC dials to a modem located at the customer site. Once the dial-up connection is established, the JOIND Server must be activated on the server (the tested hardware) side, by running the JServer.bat. On the Lotem, the JServer.bat can be found in the Start button - Programs - Diagnostics group.

Note
Activation of the server side will be upon a specific request by telephone, to an administrator or operator located on site.  

Note
The JServer can receive various command-line arguments that influence its behavior.

On the client side (the dialing PC):

1. Establish a dial-up connection to the customer site.

2. Run Joind.bat from the diagnostics directory.

3. In Page 1 of the JOIND Startup procedure, enter the name or address of the server in the Name/Address of Server field and click the Next button. For example, if the IP address of the tested device is 192.9.100.2:
   
   
   
   

4. From Page 2 of the JOIND Startup procedure, select a device from the Device For Testing list and click the Finish button.

Running Diagnostics Over the Internet

To run the JOIND over the Internet, access from the client station (the dialing PC), located outside of the customer site, should be available for the tested equipment. If, for example, the customer has a Firewall protecting his local network from outside, then ports 555 and 556 must be opened for diagnostics purposes. This can be done on a per-request or permanent basis.

Access to the Internet can be either through a network card installed on the dialing PC, or through a modem used to dial-up to an Internet Service Provider (ISP).

Note
It is not recommended to run diagnostics over the Internet because of communication speed limitations.

Run JServer.bat on the server (the tested platform) side. This is done by an administrator/operator located at the customer site. The JServer is activated only upon specific request, by telephone, from the remote support engineer.

On the client side:

1. Dial up to the ISP if you are using a modem to access the Internet.

2. Run Joind.bat from the diagnostics directory.

3. In Page 1 of the JOIND Startup procedure, enter the the name or address of the server in the  Name/Address of Server field and click the Next button.

4. From Page 2 of the JOIND Startup procedure, select a device from the Device For Testing list and click the Finish button.

User Interface

The JOIND Client user interface includes two main components:

 

• 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 contents are dynamic and are suited to the application and to the environmental conditions that may change between sessions.

• Menu options enable the control of operations performed on the tree. The menus are composed of fixed options, relevant for all applications, and of dynamic options which vary between applications.

This section describes the Diagnostics Main Window, its various menus and their options. The numbers in the table following the illustration correspond to the numbers in the illustration.

 

 

Name	Description
1 - Menu Bar	The Menu Bar holds all operations that can be performed on the Test Tree. Refer to the table of Menu Options for a description of the Menu Bar options.
2 - Buttons Bar	The buttons on the Buttons Bar are shortcuts for commonly used menu options. Refer to the table of Shortcut Buttons for a description of these buttons.
3 - Test Tree Window	The Test Tree Window is where a hierarchical test tree of the device under test is displayed. It is also where the results of test executions will be shown. Each tested device has a unique test tree. All upper-case letter names in the tree (6) are nodes that hold sub-topics. Lower-case names (7) are test entries that can be executed. A test is selected for execution by checking its checkbox (8). When checking a node with sub-topics, all the sub-topics are selected as well. To actually run the selected set of tests, select Run from the Control menu (1), or click the Run shortcut button (2). Test results will be displayed under the Last Result column of the Test Tree Window (5). If the Loop flag is On, the number of pass and fail results will be summarized for each test.
4 - Faulty Test Window	The Faulty Test Window is initially empty. As tests are executed, a list of faulty tests is built up in this window. This list can be used to select a faulty test for rerunning (16) and for viewing the description of the failure (17).
5 - Test Results	The result for a test's last execution is shown under the Last Result column in the Test Tree Window (3). If the Loop flag is On, the # Pass and # Fail columns will also be filled, according to test results. The result for a node with sub-topics (6) is a summary of the sub-topics' results. If all sub-topics passed, the summary is also a pass result. If one or more of the sub-topics failed, the summary will give a fail result.
6 - Node Entry	A Node Entry is an entry in the test tree that has sub-topics beneath it. It is written in upper-case letters. If a Tree Node is selected for testing, all it's sub-topics are also selected.
7 - Test Entry	A Test Entry is written in lower-case letters. It has no sub-topics, and it represents a test.
8 - Test Checkbox	To select a node or test for execution, click the Test Checkbox. When the Run command is selected, all checked tests are executed.
9 - Current Test Name	When a test is executed, its full name and location in the tree is displayed in the Current Test Name field.
10 - Test Progress Bar	The Test Progress Bar indicates the progress of a single test.
11 - Batch Progress Bar	The Batch Progress Bar indicates the progress of the batch of tests.
12 - Test Result Summary	The Test Results Summary field summarizes the number of passed, failed and suspected results received so far for the batch or loop currently being executed.
13 - Batch Result LED	The Batch Result LED indicates whether all tests in the current batch passed, or whether a failure was detected. Initially, the LED is yellow. It is green during a batch execution as long as the tests have passed so far. Upon the first failure, the LED turns red.
14 - Non-Batch Test (Default)	A node (6) or test (7) colored gray indicates that, by default, it isn't included in a selected batch. However, after selecting the batch, it is possible to add this node/test to the batch.
15 - Non-Batch Test	A test (7) colored white indicates that this test can never be included in a batch. This means that this test can only be executed by itself.
16 - Rerun Checkbox	Faulty tests can be selected for a rerun by checking the Rerun Checkbox in the Faulty Test Window (4).
17 - Faulty Test Name	The error description for a faulty test can be accessed by clicking on the Faulty Test Name on the Faulty Test Window (4).
18 - Startup Summary LED	The Startup Summary LED indicates a success or failure of the JOIND startup process. A green LED indicates a startup success. A red LED indicates a failure, in which case it is possible to click on the LED to receive a summary of the startup procedure.

The JOIND Menu Options

This section briefly describes the JOIND menus and sub-menus in the following order:

• File Menu

• View Menu

• Control Menu

  • Loop Sub-Menu

  • Rerun Sub-Menu

  • Mode Sub-Menu

  • Log Level Sub-Menu

  • Control Flags Sub-Menu

  • Debug Flags Sub-Menu

• Level Menu

• Help Menu

File Menu

Menu Option	Description
Save Error Buffer	The Error Buffer holds error information describing a hardware (or software) fault detected by a test. The Error Buffer is a set of temporary HTML pages. These pages are removed upon a Reset Errors request, or before running a new test when the Clear Errors flag is ON. They are also removed when the JOIND quits. It is possible to save the Error Buffer HTML pages by using the Save Error Buffer command. These files are copied to a sub-directory under JServer\Html\ErrorHistory. This sub-directory is named according to the current date and time.
Save Results	The Save Results option saves the test tree into an HTML file, along with the test Pass/Fail results.
Load Symptom	Use the Load Symptom option to select a symptom from a predefined set of symptoms describing possible faults or problems in the tested device. A list of possible actions to solve to problem will be displayed. For some of the symptoms, a set of tests will be automatically selected in the test tree. This set can be run, for verifying the hardware connected to the specified symptom.
Save Batch	A test batch is a set of tests executed as a group. A batch is defined by setting a check mark for two or more tests in the test tree. A batch definition may be saved to a file by selecting the Save Batch command. When using this command, it is required to supply a file name. This batch can later be loaded back from the file by using the Load Batch command.
Load Batch	After a test batch has been saved to a file as described above, it can be reloaded with the Load Batch command. The list of all previously saved batches will be displayed, and one must be selected for loading. Check marks will be assigned to all tests defined in the loaded batch, and may be executed with the Run command under the Control Menu.
Load Quick Batch	A test batch is a set of tests executed as a group. Normally, a batch is defined manually by setting a check mark for two or more tests in the test tree. Quick Batch is a predefined set of tests. By selecting the Load Quick Batch command, a check mark is assigned to all tests that are predefined to be part of the Quick Batch. To execute the batch, select the Run command from the Control Menu.
Import Log File	A log file is created on every JOIND session. Its location is on the Server side. The Import Log File command imports the current log file from the Server to the Client.
Download Client from Web	Download Client from Web enables downloading a new JOIND  client from the Creo web site.
Exit	The Exit command quits JOIND. If JOIND has been remotely activated (Internet or modem), then the Server stays active and ready for a new connection.
Exit and Log Off	The Exit and Log Off command quits JOIND. If JOIND has been remotely activated (Internet or modem), then the Server is also terminated. A new connection to the Server requires a new initialization of the Server.

View Menu

Menu Option	Description
Errors	A test that detects hardware (or software) faults writes the error data into a set of HTML files composing the Error Buffer. The Errors command loads the HTML browser and lists the faulty tests. By selecting a test from this list, the relevant error information is displayed.
FaultyFruList	Displays a list of suspected faulty FRUs, as detected by the last test session. This list is displayed automatically when the JOIND is at User Level or Service Level.
Test Log File	The Test Log File holds information sent to it from both the JOIND and the test. JOIND uses this file to record initialization messages during system startup. When a test is executed, JOIND records the test name into the file, and the test adds relevant data. The Test Log File command opens the HTML browser for viewing this file.
Test Log History	A Test Log File is created for every JOIND session. When JOIND quits, this Test Log File is renamed according to the current date and time, and is copied to the Log History directory. The Test Log History command activates the HTML browser and loads the list of Test Log Files located in the Log History directory. Any of the listed files can be selected for viewing.
Results File	The Results File holds information sent by JOIND. For each executed test, JOIND uses this file to record the date and time of execution, the loop number, the name of the test and the test result. If the Rerun mechanism is ON, results for all reruns will be recorded. The Results File command activates the HTML browser on this file.
Results History	A Results File is created for every JOIND session. When JOIND quits, the Results File is renamed according to the current date and time, and is copied to the Results History directory. The Results History command activates the HTML browser and loads the list of Results Files files located in the Results History directory. Any of the listed files can be selected for viewing.
Startup Summary	The Startup Summary command displays the HTML file containing startup information through the HTML browser. This information is specific for the tested device, and is not available for all devices.
Software Configuration	When the Software Configuration command is selected, the software version information of JOIND (Client and Server) and of the diagnostic DLLs is recorded into an HTML file and is displayed through the HTML browser.
Hardware Configuration	When the Hardware Configuration command is selected, hardware information is recorded into an HTML file and is displayed through the HTML browser.

Control Menu

Menu Option	Description
Run!	The Run command initiates a test session. Tests in this session are marked in the checkboxes. When the Loop Off is selected, the test session terminates after each test has been executed. When the Loop On is selected, the test session repeats until the loop termination condition is reached.
Run Until Fail	The Run Until Fail command initiates a test session. Tests in this session are marked in their checkboxes. When the Loop Off is selected, the test session terminates after each test has been executed, or until the first failure is detected by any test, whichever comes first. When the Loop On is selected, the test session repeats until the loop termination condition is reached, or once a failure is detected, whichever comes first.
Loop Sub-Menu	The Loop Sub-Menu is used to select one of four possible definitions: Off, Until Abort, Until Fail or N Cycles. These options define whether a loop is executed on a given test, and what is the loop termination condition is.
Rerun Sub-Menu	The Rerun Sub-Menu enables an automatic test rerun mechanism according to predetermined conditions.
Mode Sub-Menu	The Mode Sub-Menu is used to toggle between the Stand Alone mode and the Integrated mode.
Log Level Sub-Menu	The options under the Log Level Sub-Menu are default or max details. These define the amount of data recorded to the Test Log File.
Control Flags Sub-Menu	The Control Flags Sub-Menu contains various flags that influence the behavior of JOIND during test or batch executions.
Debug Flags Sub-Menu	The Debug Flags Sub-Menu is used to set various debugging flags to ON or OFF. These flags define which data is displayed by a test during execution.
Reset Errors	The Clear Errors Flag controls whether the contents of the Error Buffer will be cleared prior to any test session. When the Clear Errors Flag is set to OFF, the Reset Errors command can be used to immediately clear the contents of the Error Buffer.
Clear Selections	The Clear Selections Flag controls whether the checkboxes indicating which tests are executed will remain or be removed after a test session. If the Clear Selections Flag is set to OFF, the Clear Selections command can be used to clear all check marks immediately.
Clear Test Log File	A Test Log File is automatically created every time JOIND is initiated. Data is recorded to this file during the JOIND life cycle, and this data can be viewed at any time using the Test Log File command. The Clear Test Log File command enables the user to remove the contents of the Test Log File.
Clear Results File	A Results File is automatically created every time JOIND is initiated. Data is recorded to this file during the JOIND life cycle, and this data can be viewed at any time using the Results File command. The Clear Results File command enables the user to remove the contents of the Results File.

Loop Sub-Menu

Menu Option

Description

Off Until Abort Until Fail N Cycles...

These four options under the Loop Sub-Menu define the termination condition of a single test or batch of tests running in a loop: Off - The test or batch of tests are executed one time. Until Abort - The test or batch of tests are executed in an infinite loop until the user presses the Stop Button and aborts the loop. Until Fail - The test or batch of tests are executed until the first fail occurs, or until the user presses the Stop Button and aborts the loop. N Cycles... - The user selects the number of loops to be executed. The loop terminates after completing the set number of loops, or once the user manually aborts the loop by pressing the Stop Button.

Rerun Sub-Menu

Menu Option

Description

Off On Fail Always N Reruns...

These three options under the Rerun Sub-Menu define the rerun mechanism for executed tests. The test result will be the result of the last execution for each test. All results can be viewed in the Results File. Off - No test rerun will be done. On Fail - A rerun will be done on tests that fail. Always - A rerun will be done for every test. N Reruns... - Allows the user to select the number of reruns.

Mode Sub-Menu

Menu Option	Description
Stand Alone Integrated	When the Stand Alone flag is ON, a selected test will operate only on the specific hardware defined for it. When the Integrated flag is ON, the same test may also check related hardware components. * This flag is not used by all tests

Log Level Sub-Menu

Menu Option

Description

Default Max Details

The Test Log File holds information sent to it from JOIND and from the test. JOIND uses this file to record initialization messages during system startup. When a test is executed, JOIND records the test name and result in the file. The amount of data saved by a test in the Test Log File depends on the Log Level. When the flag is set to Default, default data is stored. Additional data may be recorded in the file when the flag is set to Max Details. The Test Log File can be viewed with the Test Log File command in the View Menu. * This flag is not used by all tests

Control Flags Sub-Menu

Menu Option	Description
Clear Errors	When the Clear Errors flag is set to ON, the contents of the Error Buffer is cleared before each test session. When this flag is set to OFF, the data stored in the Error Buffer accumulates. When the Clear Errors is set to OFF, it is possible to clear the contents of the Error Buffer by using the Reset Errors command.
Clear Selections	To activate a test session, set the checkmarks beside the test names and select the Run command. Once a test session is completed, the checkmarks may remain (if the Clear Selections flag is set to OFF) or can be cleared (if the Clear Selections flag is set to ON). When the Clear Selections flag is set to OFF, the checkmarks can be cleared using the Clear Selections command.
Use Test-Timeout	Most of the tests in the test tree have a time limit. While a test is executing, the test progress bar shows the progress of the test according to this limit. If, for some reason, the test duration is longer than the allocated time limit, and the Use Test-Timeout flag is ON, the test will terminate before the end of the normal completion cycle. When the flag is set to OFF, the test execution will not be interrupted.
Group Error Codes	Errors detected by a test are stored in the Error Buffer. These errors are sorted and displayed according to error codes. When the Group Error Codes flag is set to ON, errors with the same error code are grouped together and are displayed as a single error. When the flag is set to OFF, each error has its own entry in the Error Buffer.
Add Faults at End of List	When a test fails, it is added to the list of faulty tests. If the Add Faults at End of List is set to ON, the faulty tests will be added at the bottom of the list. If the flag is OFF, the faulty tests will be added at the top of the list.

Debug Flags Sub-Menu

Menu Option	Description
Assistance	When the Assistance flag is set to ON, the Assistance dialog box opens. This dialog box displays miscellaneous information sent by the test as it runs. * This flag is relevant for only some of the tests.
Show Code	When the Show Code flag is set to ON, the Show Code dialog box opens. This dialog box displays miscellaneous information sent by the test as it runs. * This flag is relevant for only some of the tests.
Single Step	When the Single Step flag is set to ON, the Single Step dialog box opens. This dialog box displays miscellaneous information sent by the test as it runs. After displaying a line of data, the test pauses, and the Single Step dialog box allows the user to select one of the following: Step - The test resumes and sends another message to the dialog box. Run  - The test resumes and completes its work without sending additional data to the Single Step dialog box. * This flag is relevant for only some of the tests.
Log Assistance	When the Log Assistance flag is ON, the Assistance information (described above) is also redirected to the Test Log File. The log file can be viewed using the Test Log File command in the View Menu.
Log Show Code	When the Log Show Code flag is ON, the Show Code information (described above) is also redirected to the Test Log File. This log file can be viewed in the HTML browser using the Test Log File command in the View Menu.
Show Exp/Rec	Normally data is sent to the Error Buffer when a hardware (or software) error is detected. When the Show Exp/Rec flag is ON, data is sent to the error buffer even when the hardware is not faulty. * This flag is relevant for only some of the tests.
Record Test Duration	When the Record Test Duration flag is ON, the test duration (in seconds) is stored in the Results File. This Results File can be viewed in the HTML browser using the Results File command in the View Menu.

Level Menu

Menu Option

Description

User Service Expert (Field) Expert (Manufacture)

The JOIND system supports three main user levels - User, Service and Expert (Manufacture/Field). The system behavior varies according to the current user level. The difference is mainly in the menu options available for each user and the in level of messaging. The User Level operates on a test tree that provides indications on faulty FRUs (Field Replaceable Units). The Expert Level operates on an enhanced tree and reports detailed error messages that enables fault detection for even the lowest-level hardware components. The Service Level is in between these two. Although it is possible for any user to use the system at any level, we do not recommend doing so. Field needs are different from manufacturing needs, and using the Expert Level in the field will result in unnecessary and irrelevant data.

Help Menu

Menu Option	Description
Online Help	Displays the JOIND Online Help file.
JOIND Components and GUI
Activating the JOIND
The JOIND Main Window
The JOIND Menu Options
About JOIND...	Displays the JOIND's version number and date.

Shortcut Buttons

The following shortcut buttons are available for easier navigation through the JOIND utility:

 

Button	Shortcut
	The Run Button is a shortcut to the Run command, runs the tests that have been selected in the check boxes.
	The Stop Button is used to stop a test running in loop or an executing batch of tests.
	The Wait Button is displayed after the Stop Button is pressed until the current test is completed.
	The Errors Button is a shortcut to the Errors command.
	The Quick Error Button enables quick access to the Error Buffer of a selected test.
	The Loop Off Button is a shortcut to the Loop Until Abort command, for toggling the button to Loop On.
	The Loop On Button is a shortcut to the Loop Off command, for toggling the button to Loop Off.
	The Assistance Button is a shortcut to the Assistance command.
	The Load Symptom Button is a shortcut to the Load Symptom command. You can select a symptom from a predefined set of symptoms describing possible faults or problems in the tested device.
	The Exit Button is a shortcut to the Exit command, to exit this software.
	The Help Button is used to select specific menu options or tree nodes when help is required.

See also links

• Diagnostics - Internal Self-Study Guide [PDF, 917KB]
• Lotem 800 Diagnostics