Research Division EED/Controls Software Group

Release Note 139.2

ARCNET Display Application

Cynthia A. Chopp

Introduction

The ARCNET Display Application was designed using VAX C
code and its display using Motif. It will be located on the EPICURE Menu. To run the program,
type menu at the $ prompt, move the cursor onto ARCNET Display,
text and press return.

The application is designed to display arcnet node numbers
from user selected arcnet modules, along with their module type.
This information will be retrieved from both the
actual module, and a central file. The house numbers of modules are
stored only in the central file and will also be displayed. Status
output for both central file and actual module are messages related to the
search or returning of information asked for.
The central file is located in the usr$disk1:[hdwdocs.cratemap] area and
named arcnet.dat. It is solely maintained
by Mike Kuplic (x4068). All new node numbers to be added, must first go
through Mike, for them to be valid. The ability to reinitialize node
numbers of modules is allowed by everyone.

Screen Display

The main display of the program is divided into three sections. The first
section, or top of the screen, is where users select information; the bottom
left corner, contains information from the central file; and the bottom right
corner contains information from the actual module. Diagram A shows what the
program will look like when it is run.

User Selected Information

The user must select the source class, crate value, and slot value of the module, for information
to be returned. The source class selections are displayed in an options menu.
This menu contains the selections of Experimental E0 Area, Meson M0 Area,
Neutrino N0 Area, and Proton P0 Area.
Both the crate value and slot value selections are done using a scale
bar. Valid scale values are 0 through 255 for crate numbers, and 1 through 24
for slot numbers.
By moving the scale bar left or right, users can select the value needed.
The user will never type in any input to make selections. When the selections
are done, users must press the Press Here To DISPLAY READBACKS button to view
information.
The program will search for the information requested by checking the central
file first, and then the actual module. Once information is found and/or returned,
it will be displayed on the screen. In Diagram B an example is shown of a user
selecting source class Meson M0 Area, crate number 210, and slot number 9
to display
what data is found in the central file and from the actual module. Please note that
the node numbers are different, and will be reinitialized later in this document
as another example.

If both the file and module return valid data/normal status the Press
Here To UPDATE Module button will become valid and turned on to use. Users may press
this button to update the module displayed. If the user makes any changes to their
selections (source class, crate, slot) the UPDATE Button will become invalid or turned off.
On reinitializing a node number, the program will take the information
found in the central file and write it to the module. After reinitializing has taken
place, information is recollected from the module and displayed to show
that the module was reinitialized.

File Information

The central file contains information on arcnet modules. It holds the
source class, crate value, slot value, and house number on all arcnet
modules. The central file is defined automatically when the user runs the program
from the General Menu. If the user chooses to run it outside the menu,
the user must type the following at the $ prompt:

$ define ARCNET_FILE usr$disk1:[hdwdocs.cratemap]arcnet.dat

If the program is run without this file defined an error message will appear
on the screen in the file status location.
An example of this can be seen in Diagram C. The program will continue to
run and retrieve information from the actual module, but will not allow the user
to update any modules.
If the data asked for is not found in the central file, the following error
message will be displayed: Module Not Found In File in the file
status location.

Actual Information

Actual information is that which is being returned from the arcnet
module through Data Acquisition or da_ calls. Both module type, and node number are returned.
If normal status is not returned, an error message will be
displayed. The following is a list of possible status error messages:
Normal Status, No Active Module Found, Camac Time Out,
Crate Offline, Camac Read Parity Error, Camac Write Parity Error,
No Q Error, and No X Error. An example of one of these errors, can
be seen in Diagram D.

Other errors that may appear are ERROR Define ARCNET.DAT which means
the logical for the arcnet data file is not defined, go see the system
manager; ERROR FILE Format is BAD in which the user should see Mike
Kuplic; ERROR da_add_cam_req_nam, ERROR da_proc_req_wait, ERROR da_get_add_status,
and ERROR Writing to Module in which there was a da_ error or DAR Server lost.

Menubar

The program's menubar consists of one selection, that being EXIT. On selecting
Exit, the option of Exit Program appears. Once the user selects that,
the program terminates.

Example of Reinitializing a Node Number -- Diagrams Included

Viewing Diagram B the user selects the criteria of source class Meson M0 Area,
crate number 210, and slot number 9. (As noted earlier in this
document the node numbers for central file and actual module did not match.)
After selecting the criteria, and noticing that the returned data is valid/normal status
the user presses the UPDATE button to reinitialize the node number of the module selected.
Diagram E shows a reinitialization, and what the module now reads to
prove the change took place. If the user does not wish to update the module, they may make other
selections and press the DISPLAY button. Any time the user gets valid data returned for
both the file and module, the UPDATE button will be valid.
Please note that the user can exit the
program at any time.

Conclusion

The purpose of this program is to allow operators to change modules that
have failed, put in new working modules in place of the bad modules, and set
the new modules' node numbers to validate them.
This program is also helpful in finding out what modules
are located out in the field.