User Manual

For the

CMTU Controller/Emulator

Table of Contents

  1.1 System Overview
  1.2 Emulator
  1.3 Controller

2 CMTU Emulator Information
  2.1 General
  2.2 Operation
  2.3 Tapes
  2.4 Things to watch for

3 CMTU Controller Information
  3.1 General
  3.2 Scripts
  3.3 Operation
  3.4 Application Settings
  3.5 Debug

4 Common Functions
  4.1 Log
  4.2 Configuration
  4.3 About
  4.4 Debug Filter

5 Installation
  5.1 Hardware
  5.2 Software

1 Introduction

1.1  System Overview

The Controller program was not designed for the normal users but to assist the programming team in development. It is offered now as a tool for support staff to assist in converting tape to disk files to be used by the Emulator

The CMTU Controller/Emulator is a Win32/Win64 program that replaces the USH-26. It uses a PCI NTDS card, currently two cards are supported to communicate to the USH-26 (in controller mode) and the UYK 507 (in emulator mode). The prototype worked in both a high end PCs with 4 MB of RAM. The NTDS cards tested were:

  1. GET Engineering
    PCI NTDS Parallel board
    Part Number: 10074501
    Driver: 50700741; and

  2. Sabtech Industries
    Swift PCI NTDS Type A/B/C/H board SW-02102-00
    Rev E;

No additional hardware is required from the PC side. The card comes with transition modules to connect to an M81511 connector that is the same as the connector on the back of the USH-26. To emulate the USH-26 existing cables from the UYK can be used. To connect to the USH-26 and control it special cables need to be used with both ends terminating in M81511 connectors.

1.2  Emulator

The Program starts by default in CMTU Emulator mode. The NTDS card connects to the UYK via the existing cable for the USH-26. It emulates the four drive bays of the USH-26 using a configurable directory structure on the hard drive, floppy, zip drive, or CDRom (for read only files). There are always four empty tapes in the drives unless a recorded tape is selected to be in a specified drive. Recording capacity is restricted only by the space available on the hard drive.

1.3  Controller

It is expected that the NTDS card will be connected to an USH-26 CMTU for this mode to work. In this mode all CMTU commands are available in the form of a script file. The default drive is zero. You may select drives and tracks with the script. The script can then be run, this sends the commands in it to the CMTU. A typical script for reading a file would be MC D1T0 RW FR RW. This would master clear the system, assign drive 1 track 0, rewind the tape, read the first file (until a tape mark is encountered), and then rewind the tape. Scripts can be saved and loaded for reuse or built on the fly. The File Read command reads the file and writes it to the default directory with the default name Tape_D1T0_1_Data.Dat

2 CMTU emulator Information

2.1  General

The CMTU Emulator replaces the USH-26 CMTU drive. It emulates all of the USH functions including the four drive bays. The UYK computer connected to the emulator will function as if it were connected to an USH-26. Tape files can be stored on any medium available to the PC.

2.2  Operation

Before the emulator is started it must be configured, this is explained in chapter 4.2. A default configuration is provided so the device will work as is. This default configuration simulates four blank tapes loaded in the drive bays.

Start CMTU
Start CMTU To start the emulator, simply click the power switch on the CMTU Emulator.
  Once emulation has started, the power button turns into the Cancel button , this is now used to stop the emulator.
  The USH-26 Master Clear toggle is the Master clear for the Emulator. It resets all the parameters for the NTDS Card. (Do not click this while emulation is in progress)
Debug Mode The Debug Mode check box determines the amount of detail reported to the log screen. It is checked by default.

2.3  Tapes

The Tape Section on the Emulator tab allows the user to simulate the placing of tapes into drives. This is done through directory selection and tape selection boxes. For convenience a blank tape is available in any selected directory. By inserting a blank tape you override the default directory set in the configuration for that drive bay.

Tape files are stored in directories with names corresponding to the tape names with the prefix "Tape_". The tape directories are marked as Hidden and System. This makes them invisible using a normal list box, so don't try to find the files using explorer.

Tape Available To put a drive in the the bay, click on the empty drive bay.
Read-Only Tape Selected Tape is Read-Only. You will not be able to write to this tape!
Eject Tape You can eject the tape by clicking the eject button.
Drive is ready Drive ready indication..

To boot Software Updater from a floppy disk - Select the A: drive. Select the tape Software Updater and press the arrow key to assign the file to drive 0. You would next start the emulator from the Emulator tab and proceed to initiate boot procedures on the UYK.

2.4  Things to Watch For

There is a danger in re-writing to virtual tapes. While using the CMTU Emulator, there is no limit to the size of tape file. Files are stored as File #1 Track 0 and so on. When you re-use a tape to write a file, you overwrite the files one by one, regardless of file size. The emulator program does not actually allow you to overwrite a file. The program will rename the second file to File #1 Track 0 version 1 an so on. But if you were to try to read back that tape, the version 0 file would be returned. An advanced user could locate the tape directory and remove the earlier versions, but it is easier to just use a new virtual tape. Be careful!

3 CMTU Controller Information

3.1  General

The CMTU Controller allows users to control a USH-26 to read and write CMTU magnetic tapes. Status information from the USH-26 is displayed using the status lights at the top of the program screen. These lights are updated every time the status is returned from the USH-26.

3.2  Scripts

Control of the USH-26 is achieved through the use of a script language. Scripts are created by clicking on the desired function on the right side of the script selection tab.
Save Script to File Once created, a script may be saved for future use by clicking on the Save Script File button.
Load Script from File Scripts may be re-loaded by clicking on the Load Script File button.

3.3  Operation

Start CMTU When the Run button is clicked, the script will be executed. A record of the process will be created and displayed on the Log screen. The Log screen is automatically selected on completion of any script.

3.4  Application Settings

VAX Byte Ordering orders bytes 4 3 2 1 instead of 1 2 3 4 Do Not Save Block Headers causes the program to save only a one word block header instead of the 6 words normally saved in a DSK file.

WDS Tape analysis requires that you de-select VAX byte ordering and select Do Not Save Block Headers. (This selection is available on the Script tab)

History Tape Analysis also requires that you de-select VAX byte ordering and select Do Not Save Block Headers. (This selection is available on the Script tab)

3.5  Debug

The Debug tab is included in this release to assist in testing. It allows the sending of single instructions to the USH-26, also the creation of sequence files to test the correct transfer of words.

4 Common Functions

4.1  Log

The Log tab is a text box where the Emulator or Controller can dump messages and timings of its operation. This screen is helpful in determining correct operation. Whenever the program fails to function properly the log file should be saved and forwarded to TSSC for analysis.
Start CMTU To save the log file, select the Save Log Button . This opens a standard windows file dialog box.
Start CMTU To clear the Log, select the Clear Log Button . Once cleared the log is forever gone.

4.2  Configuration

The Configuration tab allows the user to adjust the configuration of the program which includes: the type of NTDS card (Sabtech or GET); the Device number (for multiple card installation); Byte ordering format; Interface speed (NTDS Fast or Slow); and the default directory for file storage.

The NTDS card, Device number, and Interface speed are selected via drop down combo boxes. The defaults are the Sabtech Swift PCI ABCH card, Device NTDS0, and NTDS Fast (do not select NTDS Slow unless you are certain you are connected to an NTDS Slow device! The NTDS Slow setting will burn out an NTDS Fast card due to higher voltages!).

The Byte ordering is selected with two radio buttons the default is PC format.

To change the default directory click on the edit box containing the directory name. Drive selection and Directory selection boxes will appear. Select the desired directory and press the arrow button to commit the change.

4.3  About

The About tab is an information page with contact and version information. Check it out to see our logo.

4.4  Debug Filter

The Debug Filter tab allows for the selection of individual commands to be trapped and sent to the Log. By default all commands are selected. This is a useful tool when the log files become too large and you know what you are looking for.

5 Installation

5.1  Hardware

To install the NTDS card follow the instructions provided by the manufacturer. Initial installation is quite simple; however, switching between Sabtech cards or upgrading cards or trying to install multiple cards can become quite complicated. The success of much of this depends on the hardware configuration of the PC.

The short instructions are insert the card into an empty slot (depending on the PC not all slots work so try another one if problems are encountered) and run the install program provided by the manufacturer.

5.2  Software

The software is delivered on a CD with an install program. Run the install program and all files will be copied.