Vous êtes sur la page 1sur 93

Tester Simulator Menu

Manual for MIL-STD-1553


Tester/Simulator Cards and
BU-65590UX USB Device
MN-69065S0-001
The information provided in this Users Guide is believed to be accurate; however, no
responsibility is assumed by Data Device Corporation for its use, and no license or
rights are granted by implication or otherwise in connection therewith.
Specifications are subject to change without notice.
Please visit our web site at www.ddc-web.com/ for the latest information.
1

105 Wilbur Place, Bohemia, New York 11716-2426


For Technical Support 1-800-DDC-5757 ext. 7771
Headquarters - Tel: (631) 567-5600, Fax: (631) 567-7358
United Kingdom - Tel: +44-(0)1635-811140, Fax: +44-(0)1635-32264
France - Tel: +33-(0)1-41-16-3424, Fax: +33-(0)1-41-16-3425
Germany - Tel: +49-(0)89-15 00 12-11, Fax: +49-(0)89-15 00 12-22
Japan - Tel: +81-(0)3-3814-7688, Fax: +81-(0)3-3814-7689
World Wide Web www.ddc-web.com/

All rights reserved. No part of this Users Guide


may be reproduced or transmitted in any form or by
any means, electronic, mechanical, photocopying,
recording, or otherwise, without the prior written
permission of Data Device Corporation.

REV F January, 2008


2001 Data Device Corp.

RECORD OF CHANGE
Revision
A
B

Date
October, 2001
March, 2002

Pages
Original Issue
Corrections

ix, 1, 15,
17, 35, 43,
49
1, 8, 10,
11, 12, 49

December, 2002

August, 2004

61
All

September, 2005

67, 69+

January, 2008

1-8, 15,
19, 21, 25,
26, 28, 31,
32, 39-41

Data Device Corporation

Description

All

Replace BU-65558 part number with BU65570M part number.


IRIG Flag description corrected.
Edits occur on the following pages;
1-2, 6, 10-13, 15-16, 18-24, 27-33, 35-36,
appendix a (all)
Set Output Trigger function modified, Set
Discrete 0-3, Reset Discrete 03 functions
added, removed Appendix D.
Added BU-65590UX specific notes and
descriptions to indicated pages

BU-69065 Manual

TABLE OF CONTENTS
LIST OF FIGURES .................................................................................................................... IV
LIST OF TABLES....................................................................................................................... V
SOFTWARE LICENSE AND POLICIES ................................................................................... VI
Update Policy......................................................................................................................................... vii
Technical Support ..................................................................................................................................viii
Customer support: ............................................................................................................................viii
Headquarters: ...................................................................................................................................viii

HOW TO USE THIS MANUAL .................................................................................................. IX


Text Usage.............................................................................................................................................. ix
Symbols and icons.................................................................................................................................. ix
Trademarks.............................................................................................................................................. x

INTRODUCTION .........................................................................................................................1
What is included in this manual? .............................................................................................................1
System Requirements.............................................................................................................................. 1

SOFTWARE INSTALLATION .....................................................................................................2


Windows 9x/2000/XP, Windows NT...................................................................................................2
DDC 1553 Card Manager For Windows 9x/2000/XP............................................................................6
DDC 1553 Card Manager For Windows NT ............................................................................................9

SOFTWARE OPERATIONS

Bus Controller Mode (BC) ............................................14

Remote Terminal Mode (RT) .................................................................................................................14


Monitor Mode (MT) ................................................................................................................................14
Replay Mode..........................................................................................................................................14

TESTER/SIMULATOR MENU OPERATION ............................................................................15


Tester/Simulator Menu (Windows/MXI-II)..............................................................................................15
Conventions......................................................................................................................................16
Verifying Proper Card Initialization ...................................................................................................17
Setup for BC Operation..........................................................................................................................18
Setup BC Dialog ....................................................................................................................................18
BC Properties ...................................................................................................................................18
Status Mask ......................................................................................................................................19
Frame................................................................................................................................................19
Messages .........................................................................................................................................19
BC_LOG ...........................................................................................................................................19
Edit BC Message Dialog ........................................................................................................................20
Command Word................................................................................................................................20
Message Options..............................................................................................................................21
Intermessage Routines.....................................................................................................................21
Data Word (Starting Data Table) ......................................................................................................21

Data Device Corporation

ii

BU-69065 Manual

Error Injection ...................................................................................................................................21


BC Example: ..........................................................................................................................................22
Setup for Remote Terminal Operation...................................................................................................25
Setup RT Dialog.....................................................................................................................................25
Data Tables ......................................................................................................................................25
RT Default Status .............................................................................................................................26
Accept Dynamic Bus Control............................................................................................................26
Error Injection ...................................................................................................................................26
Legality Detection .............................................................................................................................26
RT Example: .....................................................................................................................................26
Data Tables............................................................................................................................................27
RT Example Setting Up Data Tables................................................................................................29
Setup for Monitor Operation ..................................................................................................................29
Capture .............................................................................................................................................30
MT Example:.....................................................................................................................................32
Run Screen ............................................................................................................................................33
Stack Viewer.....................................................................................................................................34
Setup for Replay Operation ...................................................................................................................39
Generate C Code...................................................................................................................................40
Error Injection.........................................................................................................................................41

APPENDIX A.............................................................................................................................43
RTL Error Messages..............................................................................................................................43

APPENDIX B.............................................................................................................................62
Intermessage Routines ..........................................................................................................................62
Definition of Routines.............................................................................................................................64

APPENDIX C.............................................................................................................................73
Communication Stack Structure ............................................................................................................73
IRIG FLG ..............................................................................................................................................74
FLS FLG.................................................................................................................................................75

INDEX........................................................................................................................................78

Data Device Corporation

iii

BU-69065 Manual

LIST OF FIGURES
Figure 1 Menu Install Welcome ...............................................................................................2
Figure 2 License Agreement....................................................................................................3
Figure 3 Install Directory ..........................................................................................................3
Figure 4 Select the Start Menu Group ..................................................................................... 4
Figure 5 Install Optional DDC 1553 Library .............................................................................5
Figure 6 Installation Complete .................................................................................................5
Figure 7 Install Done, Reboot ..................................................................................................6
Figure 8 Control Panel .............................................................................................................7
Figure 9 DDC 1553 Card Manager .......................................................................................... 7
Figure 10 Card Manager Modify .............................................................................................. 8
Figure 11 Control Panel .............................................................................................................9
Figure 12 DDC 1553 Card Manager ........................................................................................10
Figure 13 Device Driver Status ................................................................................................10
Figure 14 Manage Non-PnP Devices ......................................................................................11
Figure 15 Add New Device ......................................................................................................11
Figure 16 Configuring the Card................................................................................................12
Figure 17 Modify Device ..........................................................................................................13
Figure 18 Tester/Simulator Main Dialog ..................................................................................16
Figure 19 Setup BC Dialog ......................................................................................................18
Figure 20 Edit BC Message Dialog..........................................................................................20
Figure 21 Example Edit BC Message Dialog...........................................................................23
Figure 22 Example Edit BC Message Confirmation ................................................................23
Figure 23 Example Setup BC Dialog .......................................................................................24
Figure 24 Remote Terminal Setup Document .........................................................................25
Figure 25 Edit Data Table ........................................................................................................28
Figure 26 MT (Monitor) Setup Document ................................................................................29
Figure 27 MT (Monitor) Filter ...................................................................................................31
Figure 28 Mode Code Legality.................................................................................................31
Figure 29 MT (Monitor) Cmd Mask ..........................................................................................32
Figure 30 Run Window ............................................................................................................33
Figure 31 Stack View ...............................................................................................................34
Figure 32 Search Command Word ..........................................................................................36
Figure 33 Search Status Word.................................................................................................37
Figure 34 Search Data Word ...................................................................................................38
Figure 35 Search Exception.....................................................................................................38
Figure 36 Replay Setup Document..........................................................................................39
Figure 37 Generate Code ........................................................................................................40
Figure 38 Error Injection ..........................................................................................................41

Data Device Corporation

iv

BU-69065 Manual

LIST OF TABLES

Table 1 Intermessage Routines ...............................................................................................63


Table 2 Monitor Message Header............................................................................................73
Table 3 Error Codes.................................................................................................................76

Data Device Corporation

BU-69065 Manual

SOFTWARE LICENSE AND POLICIES


LICENSE. DDC grants a license to the individual and/of corporate
licensee to use the Program Product (the set of computer programs
and machine readable and printed materials supplied with this
package for a term beginning on the date you accept this Agreement
and continuing until termination. This license agreement is
automatically terminated if you violate any of the terms and conditions
of this License Agreement. You may terminate this agreement at any
time by destroying all copies, modifications, and original materials
supplied with the Program Product and destroying any portions of the
DDC Program Product merged in any form.
USE OF THE PROGRAM PRODUCT. You may use the Program
Product only on the Card with which the product was purchased. You
may copy the program for backup or transfer to any machine. Reverse
compiling and disassembling of programs in object format are
prohibited. Title to the program is not transferred to you by this
license. Any attempted sublicense, assignment, or other transfer of
the programs or the rights and obligations of this Agreement without
the prior written consent of DDC shall be void.
RESTRICTIONS. You may not use, copy, modify, merge, or transfer
the Program Product or any portion or modification thereof in whole or
in part, except as expressly provided in this Agreement.
LIMITED WARRANTY. DDC warrants the distribution diskette(s) upon
which the Program Product is provided to be free from defects in
materials and workmanship under normal use for a period of one year
from the date of purchase by the original purchaser. FOR BREACH
OF ANY WRITTEN OR IMPLIED WARRANTY ON THIS PRODUCT,
THE CONSUMER IS LIMITED TO THE REPLACEMENT OF THE
DEFECTIVE DISKETTE(S).
Note: Some states do not allow the exclusion or limitation of incidental or
consequential damages so the above limitation or exclusion may not
apply to you.

DDC makes no other warranty of any kind, either expressed or


implied, and no warranty that the program product is free of errors.
DDC and its authorized dealers shall not be liable for the cost of any
repair of correction required for defective DDC program product
material except as stated in this paragraph.

Data Device Corporation

vi

BU-69065 Manual

SOFTWARE LICENSE AND POLICIES


GENERAL TERMS. This is the only agreement between User and
DDC regarding this Program Product and it may be modified only by a
written agreement between those parties. This agreement cannot be
modified by purchase orders, advertising or other representation by
any person. If any provision of this agreement shall be held invalid,
illegal, or unenforceable, then the validity, legality and enforceability of
the remaining provisions shall not be affected or impaired thereby.
The laws of the State of New York shall govern this agreement. By
opening or keeping the package, you acknowledge that you have read
this agreement, understand it and agree to be bound by its terms and
conditions.

Update Policy
We will update the product as new functions are developed or major
bugs are fixed, to the extent of the warranty period. These updates will
be made available on our web site from time to time. Prior to calling
DDC for updated material, please visit our web site for the latest
versions.

Data Device Corporation

vii

BU-69065 Manual

SOFTWARE LICENSE AND POLICIES

Technical Support
In the event that problems arise beyond the scope of this manual, you
can get in touch with DDC by calling:
Customer support:

1-800-DDC-5757, ext. 7771


Headquarters:

1-631-567-5600, ext. 7771


Fax: 1-631-567-5758 to the attention of DATA BUS Applications.
DDC also has an Internet World Wide Web site, which allows
customers to easily download new revisions of software and
documentation. The Internet address is www.ddc-web.com.

Data Device Corporation

viii

BU-69065 Manual

HOW TO USE THIS MANUAL


This manual uses typographical and iconic conventions to assist the
reader in understanding the content. This section will define the text
formatting and icons used in the rest of the manual. This manual is
formatted with a Scholar Margin where many tips, symbols or icons
will be located.
For the full text of this manual, BU-65572i will be used to identify both
the BU-65572i and the BU-65570i. BU-65572v will be used to identify
both the BU-65572v and the BU-65570v. BU-65572t will be used to
identify both the BU-65572t and the BU-65570t. In those cases where
there is a difference, the appropriate part number will be identified.

Text Usage

BOLD text that is written in bold letters indicates important information and
table, figure, and chapter references.
BOLD ITALIC will designate DDC Part Numbers.
Courier New is used to indicate code examples.
<> - Indicates user entered text or commands.

Symbols and icons


The Idea/Tip icon will be used to identify a handy bit of supplementary
information that may be useful to the user.

The Note icon signifies important supplementary information that will be


useful to the user.

The Caution icon identifies important information that presents a


possibility of damage to the product if not heeded.

Much stronger than a Caution, the Warning icon presents information


pertaining to hazards that will cause damage to the product and
possible injury to the user.

Data Device Corporation

ix

BU-69065 Manual

HOW TO USE THIS MANUAL

The Reference icon indicates that there is related material in this


manual or in another specified document.

The Disk Icon describes information that is related to software.

Trademarks
All trademarks are the property of their respective owners.

Data Device Corporation

BU-69065 Manual

INTRODUCTION
The BU-69065 Tester/Simulator Menu provides a graphical user
interface (GUI) for DDCs series of Tester/Simulator products.
The Menu has the capability to simulate a Bus Controller, all 31
Remote Terminals, and a Monitor simultaneously on each of the
installed buses. There is additional capability to synchronize the
onboard time tags of all of the operating cards with one command. All
software and updates are posted on the DDC website.
The Tester/Simulator Menu provides access to the full functionality of
the DDC 1553 Tester/Simulator cards without having to write or
compile a single line of code, by providing the user an intuitive
graphical interface. Presently, there is no Menu software provided for
the BU-65572I, BU-65572T, BU-65572v and the BU-65570M running
under DOS. The BU-65572I, BU-65572T, BU-65572v and BU65570M drivers should be installed, configured and operating correctly
before operating the menu software.
The BU-65590UX USB Device is also supported with the Tester
Simulator Menu (version 5.0.1 or later). The BU-65590UX can only be
used as either a BC, or MT, or one RT at a time. Concurrent operation
of all three modes is only supported with DDCs Tester Simulator
Devices.

What is included in this manual?


This manual contains a detailed installation and users guide for the
BU-69065 Tester Simulator Menu.

System Requirements
IBM compatible PC with a Pentium processor or better.
Windows 9x/2000/XP, Windows NT operating system.
One of DDCs Tester/Simulator Cards.
For BU-65590UX
USB 2.0 Port.
Windows 2000/XP.
BU-69092S0 Rev 2.0.3 or later.

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION
Windows 9x/2000/XP, Windows NT
Before installing the BU-69065 software, make sure that the DDC
Tester Simulator card has been installed as described in its
associated hardware manual.
Note: The BU-65590UX is only supported under Windows 2000/XP.
Note: If a card has not been installed the software can still be used to create
setup files.

1) Run the setup.exe program located on the BUS-69065S0


(Windows 9x/2000/XP, Windows NT) installation disk. This will
cause the installation program to start and display the dialog.

Figure 1 Menu Install Welcome


2) Click the Next button to continue the installation. When the Next
button is clicked, a License Agreement dialog will be presented.

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION

Figure 2 License Agreement


3) Read the license agreement and click the Yes button to continue
with the installation.
Note: You must answer Yes to continue with the installation.

The next dialog will enable the selection of the installation directory.

Figure 3 Install Directory

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION
4) The default directory is C:\Program Files\Data Device Corp\1553
TestSim. This may be altered by clicking on the Browse button,
and navigating to the desired directory. Once the directory is set
then click the Next button. The following dialog window will enable
the selection of the Start Menu group where the TestSim menu will
be installed.

Figure 4 Select the Start Menu Group


5) If a different menu group is desired, then an existing menu group
can be selected from the list or a new group name can be entered
in the edit box.
6) To continue installing the menu software on the hard disk, click the
Next button after establishing the desired menu group.

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION

Figure 5 Install Optional DDC 1553 Library


7) If you are using a BU-65590UX and have not installed the BU69092S0 EMACE Plus SDK, then you will need to install the
optional library. Leaving the check box checked will start the
installer for the EMACE Plus SDK BU-69092S0.

Figure 6 Installation Complete

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION
8) The installation will provide a dialog that will enable the user to
view the Release Notes and Readme files. The dialog will also
have the option to launch the DDC 1553 Card Manager. Click the
Finish button.
Note: It is important to run the DDC 1553 Card Manager at least once in
order to establish logical device numbers for each of the installed
Tester Simulator devices. (See DDC 1553 Card Manager section)

Figure 7 Install Done, Reboot


9) As a final step for installation of the GUI Menu, the computer must
be re-booted. Click Ok to restart the computer.

DDC 1553 Card Manager For Windows 9x/2000/XP


Once the hardware and software is installed, the device can be
configured. Device configuration is performed through the use of the
DDC 1553 Card Manager located in the Windows Control Panel.
The following are basic instructions to configure a card in Windows
9x/2000/XP. If you are using Windows NT skip to the NT section.
Note: The BU-65590UX is only supported under Windows 2000/XP.

The DDC 1553 Card Manager is used to assign a device number


(logical number) for the card you are using. This number is used by
the RTL to identify the card. By default, an installed card will have a
Device number of none. The user must select a number from 0 to 31.

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION
1) Turn on the computer.
2) Open the Windows Control Panel by clicking on the Start button.
Then click on the Settings option. Finally, click on Control Panel.

Figure 8 Control Panel


3) Double-Click on the DDC 1553 Card Manager icon (circled in the
screen image above).

Figure 9 DDC 1553 Card Manager


4) Select an installed Device (i.e., BU-65572I2-300, BU-65570M1300, BU-65572T2-300, or BU-65590UX) and click the Modify
button.
Note: Each card must be assigned to a unique (unused) device number from
0 to 31; card numbers cannot be shared.

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION
5) The Modify Card Number window will appear:

Figure 10 Card Manager Modify


6) Unselect the None option by clicking on the drop down list.
7) Next, select a device number to associate with the card by
clicking on the list box and choosing a device number.
8) When finished, click on the OK button.
9) The DDC 1553 Card Manager window should display the device
with a device number mapped to the card. The card status should
read Device Ready.
10) Click on the Close button to complete card configuration. The
card is now ready for use.

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION

DDC 1553 Card Manager For Windows NT


Once the hardware and software is installed, the device can be
configured. Device configuration is performed through the use of the
DDC 1553 Card Manager located in the Windows Control Panel.
The following are basic instructions to configure a card in Windows
NT.
Note: BU-65590UX is not supported under Windows NT.

The DDC 1553 Card Manager is used to assign a device number


(logical number) for the card you are using. This number is used by
the RTL to identify the card. By default an installed card will have a
Device number of none. The user must select a number from 0 to 31.
1) Turn on the computer.
2) Open the Windows Control Panel by clicking on the Start button.
Then click on the Settings option. Finally, click on Control Panel.

Figure 11 Control Panel


3) Double-Click on the DDC 1553 Card Manager icon (circled in the
screen image above).

Data Device Corporation

BU-69065 Manual

SOFTWARE INSTALLATION

Figure 12 DDC 1553 Card Manager


4) Click on the Driver button to specify the driver type of the card.
Note: Each card must be assigned to a unique (unused) device
number from 0 to 31; card numbers cannot be shared.
5) From the list of drivers, select the card type ( driver choices are
Tester/Simulator PCI (BU-65572I) or Tester/Simulator PCMCIA
(BU-65570M)) and click on the Start button.

Figure 13 Device Driver Status


6) Click the Close to close the window. If the device is a Plug and
Play device (PCI BU-65572i) then skip to step 14. If the device
installed is a PCMCIA card (BU-65570M or BU-65558) then
continue with the next step.
7) To set up the Non-plug and play Devices click on Setup Non-PnP
Device button. This will open the Manage Non-PnP Devices
window.

Data Device Corporation

10

BU-69065 Manual

SOFTWARE INSTALLATION

Figure 14 Manage Non-PnP Devices


8) Click on the Add Device button. This will bring up an Add New
Device Window.

Figure 15 Add New Device

9) Choose the BU-65570M or BU-65558 Tester/Simulator under the


Part Number pull-down menu.

10) The Add New Device window will display the card information
(card type, number of channels, and memory size). To added the
card to the DDC 1553 Card Manager click on the Add button.

11) The card now has to be configured. The default values of the card
for interrupt, Base Memory address, and I/O address are set. The
user may change these values by click on the appropriate drop
down box.

Data Device Corporation

11

BU-69065 Manual

SOFTWARE INSTALLATION
Note: Windows NT provides a tool that can be used to locate used and
unused system resources such as Interrupt, memory and I/O ports. To
access this capability, run the NT Diagnostics program. This program
is located at the START / PROGRAMS / ADMINISTRATIVE TOOLS
menu selection. Once NT Diagnostics has been started, the
Resources tab should be selected. This will display a dialog showing
the interrupts that are presently being used by the system and the
installed hardware drivers. There are buttons on the bottom of the
dialog that will change the view from the Interrupts to I/O ports, or
memory. To correctly configure the BU-65570M or BU-65558 card, an
unused interrupt, two contiguous unused 8-bit I/O ports, and 32K
contiguous bytes of lower memory must be available for use by the
card.

Figure 16 Configuring the Card

12) Once the card is configured, click on the Ok button. This will bring
back the Manage Non-PnP Device Window. To exit out of this
window click on Close button. You will be prompted to reboot your
computer. After rebooting open the card manager again.

13) Once the DDC 1553 Card Manager is open, the device will be
listed under the installed devices.

Data Device Corporation

12

BU-69065 Manual

SOFTWARE INSTALLATION
14) Select the device you have installed and click on the Modify
button. This will bring up the Modify Device window. In this window
you must select a card number (Logical Device Number) for your
device. Click on the drop down box for Device Number and select
a number.

Figure 17 Modify Device


Note: If a previously assigned device number is selected, and the Prompt on
Replace option is checked on the DDC 1553 Card Manager the
following warning will appear:

Clicking on Yes will overwrite the previously assigned device


number.
If the Prompt or Replace option was not selected, a warning
will not be displayed and the new device number will
automatically overwrite the previously assigned device
number.
15) After selecting a Device Number, click on the Ok button. The
device is now configured and ready to use. To exit out of the DDC
1553 card Manager click on the Close button.

Data Device Corporation

13

BU-69065 Manual

SOFTWARE OPERATIONS
Bus Controller Mode (BC)
The Bus Controller mode can be configured to perform the
following tasks:
Initialize the card
Enable/Disable BC operation
Create messages, frames, and data tables
Inject errors
Run the BC

Remote Terminal Mode (RT)


The Remote Terminal mode can be configured to perform the
following tasks:
Initialize the card
Create data tables and initialize them with data
Establish any error responses
Attach interrupt intermessage routines to the data tables
Inject errors
Run the RT

Monitor Mode (MT)


The Monitor mode can be configured to perform the following
tasks:
Initialize the card
Setup Message Filter tables
Setup Legalization tables
Specify monitor file for stack storage
Run the MT

Replay Mode
The Replay mode; this application is used to replay a previously
captured stack file. This can be a stack file from a previous version
of DDC Tester/Simulator as well as this version. This version of
replay is capable of simultaneously monitoring during replay.
Replay mode can be configured to:
Initialize the card.
Select stack file
Select Remote Terminals that will be emulated by the replay
Select stack file for simultaneous monitor
Run Replay

Data Device Corporation

14

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


The Tester/Simulator Menu is provided for Windows 9x/2000/XP,
Windows NT. This program is initiated by selecting Start | Programs |
Data Device Corp | 1553 Tester Simulator | 1553 Tester Simulator
Menu. When the program starts, the user will have the option to open
a new file or an existing file from a list.
The paragraphs that follow describe the setup needed to operate the
Tester/Simulator as a BC, a RT, Monitor, and Replay. There is also a
description on how to inject error, use the Stack Viewer and to
generate C code using the Tester Simulator program.
The BU-65590UX can only operate as either a BC, one RT, or MT.
Error Injection, Replay Mode, and C code generation are not
supported with the BU-65590UX.

Tester/Simulator Menu (Windows/MXI-II)


The Tester/Simulator Menu provides access to the full functionality of
the DDC 1553 Tester/Simulator cards without having to write or
compile a single line of code, by providing the user an intuitive
graphical interface. Presently, there is no Menu software provided for
the BU-65572v running under DOS or other UNIX type operating
systems. The BU-65572v drivers should be installed, configured and
operating correctly before installing the menu software. The menu is
presently only available for Windows operations running through a
MXI-II interface.
Open the menu by clicking Start | Programs | Data Device
Corporation | 1553 Tester Simulator | 1553 Tester Simulator
Menu. To start a new session, select the radio button for Create a
New File and click okay. This will create a graphic document that
displays a representation of the 1553 bus, showing the BC, 32 RTs, a
Monitor and Replay Icons. There are also icons for Couple and Load.
This is a feature that is only available on the BU-65572i, BU-65572T
and BU-65572v cards.

Data Device Corporation

15

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Figure 18 Tester/Simulator Main Dialog


Conventions

From this dialog, a graphic representation of the 1553 bus can be


seen. Each element on the bus is a control that will access the
appropriate setup screen.
Double-clicking on an icon will activate a setup screen for the
selected device.
If the icon is single-clicked, then the device will be toggled
between active and inactive. In the inactive (grayed-out), the
device will not be emulated on the bus. In this state, even if the
device is setup, it will not operate on the bus.
If the Couple icon is clicked, it will toggle between transformer
and direct coupling. (Only for the BU-65572i, BU-65572T and
BU-65572v cards)
If the Load icon is clicked, it will toggle between None, Full
(37.5 ohms), and Half (78 ohms). (Only for the BU-65572i,
BU-65572T, and BU-65572v)

Data Device Corporation

16

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Verifying Proper Card Initialization

The user must first setup the Active Card Number. The default
card number is 0. This can be changed by clicking on File |
Active Card in the menu bar.

Clicking on the Self-Test button


will run a self-test on the
card itself. This test will reset the card, test the shared RAM,
and test the on board DSP.

Clicking on the Ver button allows the user to check the version
of the card, RTL, the driver version, the part number of the
device, and the protocol that the RT will run (1553B).

Data Device Corporation

17

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Setup for BC Operation


A MIL-STD-1553 Bus Controller is the only device on the bus that is
permitted to initiate communications. A typical communication
scenario involves one or more messages that are processed over a
specified period of time (frame time). The Bus Controller uses this
time when the sequences of messages are to be processed
repeatedly. Each sequence of messages are known as a Major
Frame. Each Major Frame may be composed of many Minor Frames.
To setup the BC double click on the BC icon in the BUS VIEW dialog,
this will open the setup BC dialog shown below.

Setup BC Dialog

Figure 19 Setup BC Dialog


BC Properties

The Number of Frames and Forever check box signify the number of
times the BC will execute the major frame. If the BC is to run a finite
number of times then the user will enter the number of times to run the
frame in the Number of Frames box. If the BC should run forever then
the user will check the Forever check box, which will run the BC until
the user stops the card.

Data Device Corporation

18

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


The Response Timeout list box allows the user to set the time the BC
will wait for a response from a RT. If the RT does not respond than a
no response is recorded and the BC moves onto the next message.
The Emulated RT list box specifies the RT address the BC will use.
The Minor Frame box is used to specify the minor frame time. Below
is a display, which shows the percentage of time used in the minor
frame along with the minor frame time.
Status Mask

The Status Mask check boxes determine which bits will set the
Flagged bit in Status exception error. If the box is not checked for a
specific status bit, then the Monitor will ignore that word in the RT
status word. If the box is checked, and that bit is set in the RT status
word then the Flagged bit in Status exception will be created.
Frame

The Frame window lists the BC frame. All messages and frame
symbols will be executed as long as they are listed before an End of
Major frame symbol. The Bus Controller will not send any message
after the End of Major frame symbol. Messages and frame symbols
can be removed by clicking on the Delete button.
Messages

The Messages window lists every message and frame symbol. By


default the Tester Simulator Menu has four frame symbols, Skip,
Break Point, End of Minor and End of Major. The frame symbols and
messages can be added to the frame by clicking on Add or Insert
buttons. Messages can be created by clicking on the New Msg
button.
BC_LOG

When using the BU-65590UX as a BC, the monitor is not available.


The monitor will actually be a log of all messages sent by the BC.

Data Device Corporation

19

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Edit BC Message Dialog


Clicking on the New Msg button will open the Edit BC Message
dialog shown below.
The Message Name drop down list gives a unique name to each
message. The default name is Message_001, which increments by
one each time a new message is created. The message name may
also be edited to a custom name by clicking in the Message Name
box.

Figure 20 Edit BC Message Dialog


The Message Type drop down box allows the user to specify the type
of message. The choices are BC to RT (receive), RT to BC (transmit),
RT to RT, Mode Code, and NOP.
The Starting Data Table drop down box will list each data table
created. This box allows the user to specify which table to use for this
message. When using the intermessage routine Block Data BC, the
Ending Data Table drop down box is used. The Ending Data Table
specifies the last table used in block data transfers.
Command Word

The Command Word fields allow the user to specify the command
the BC will issue. For RT to RT commands, the entries for Command
2 will be shown; otherwise for all other commands only Command 1
will be shown.

Data Device Corporation

20

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


For mode codes, the subaddress field is set to 31 and the word count
represents the mode code. There will be a new drop down list shown
with a list of each mode code. Selecting one of these mode code
values will automatically set the word count field.
Message Options

The Time to Next Msg box will set the delay before the next message
is sent. This value is measured from the beginning of the current
message to the beginning of the next message. If the Use Default
check box is selected than the Tester Simulator Menu will calculate
the minimum time to next message.
The channel the message is sent on is set by selecting either Radio
button A (for Bus A) or B (for Bus B).
Intermessage Routines

Each message can have up to two intermessage routines. The BC


intermessage routines are:
Note: Intermessage routines are not supported with the BU-65590UX.

No Operation, Retry on Alternate Bus, Retry and Remain on Alternate


Bus, Retry on Same Bus, Interrupt on End of Message, Interrupt on
Frame Symbol, Set Service Request Bit in Status, Reset Service
Request Bit in Status, Retry on Same Bus and then on Alternate Bus,
Set Output Trigger, Reset Output Trigger, Wait for Input Trigger, No
Response on Both Buses, Set Busy Bit in Status, Reset Busy Bit in
Status, Skip Next Message, Skip Next Message Once, Block Data BC,
Set Discrete 0, Set Discrete 1, Set Discrete 2, Set Discrete 3, Reset
Discrete 0, Reset Discrete 1, Reset Discrete 2, Reset Discrete 3. For
more information on the intermessage routines see Appendix B.
Data Word (Starting Data Table)

This window allows the user to modify the data for the table specified
in the Starting Data Table drop down list. Double clicking on the data
words will open the Edit Data Table Dialog. For more information
please see the Data Tables section on page 27.
Error Injection

Each Tester Simulator card has the capability of modifying the data it
sends on the MIL-STD-1553 bus. To specify the error injected on the
bus press the Modify button. For more information on error
injection see the Error Injection section on page 41.
Note: Error injection is not supported with the BU-65590UX.

Data Device Corporation

21

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

BC Example:
As an example, assume a Bus Controller must process an RTRT
message that has a Minor Frames time of 1000 secs, and the frame
must be repeated two times. The steps required to setup the BC are
listed below.
1) Select the FILE | NEW menu option to create a new
Tester/Simulator document.
2) The first operation that must be performed is to create the new
messages. To create a new message, double click on the BC icon.
This will bring up the BC Setup Dialog window. From this window
click the NEW MSG button.
3) The Edit BC Message dialog will be presented, allowing the user
to define all aspects of the message. For our example, we will
change the Message Type to a RTRT message. Command 1
will be the receiving RT. The values for the command will be RT
Addr = 1, Sub Addr = 1, Word Cnt = 5. For command 2 the RT
Addr = 2, Sub Addr = 1, Word Cnt = 5.
4) The data table is selected from the Starting Data Table drop-down
list box. If an appropriate data table does not exist, then a new
table may be created. To access the Data Table Edit dialog
double-click on the Data Words display box in this message, and
select New from the Edit Data Table menu.
5) When all message parameters are specified click on the OK
button. A change confirmation dialog box will open up. Click on the
OK button to accept the changes and return to the Setup BC
window.

Data Device Corporation

22

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Figure 21 Example Edit BC Message Dialog

Figure 22 Example Edit BC Message Confirmation


6) After all messages are created, adding the messages to the frame
in the Setup BC screen will create the Frame. Select message one
from the list of Messages, and click on the Insert button to insert
the message before the selected message in the Frame.

Data Device Corporation

23

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Figure 23 Example Setup BC Dialog


Note: When adding messages to the Frame, make sure to insert them
before the End of Major (by default the Frame starts with End of
Major). Starting the frame with End of Major will not run the Frame.

7) To repeat the Frame, enter in the desired number of times the


Frame will be repeated in the Number of Frames text box, for our
example enter in 2. To run the Frame forever, click on the check
box for Forever.
8) To change the Minor Frame Time, enter in a new value in the text
box for Minor Frame Time. For this example we will stay with the
default value.
9) After setting up the BC, click on the X in upper right-hand corner of
the BC Setup window to close the BC setup dialog. With the BC,
and MT enabled, press the RUN button on the Tester Simulator
Main Dialog window to run the BC frame. Since no RTs are
enabled you will get a no response for all RTs receiving a
message.
Note: When changing the Minor Frame Time, the time line will show the
change in Minor Frame Time. If the Minor Frame Time is made to
small for the Frame then the time line will change to a red color
showing the percentage of the Minor Frame Time being used.

Data Device Corporation

24

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Setup for Remote Terminal Operation


The Remote Terminal Setup Document allows the user to setup the
operational parameters for each RT emulated by the
Tester/Simulator board. When a RT is double-clicked on in the main
dialog, the RT Setup dialog will be displayed for the selected RT. For
example if RT_01 were double-clicked, then all of the subaddress
(SA1-SA30) can be modified for that RT. Receive (Rx) subaddresses
can be configured separately from Transmit (Tx) subaddresses using
the Rx/Tx radio buttons at the top of the dialog.
Note: The BU-65590UX can only emulate one RT address at a time. BC
mode cannot be used by the same logical device number when the
BU-65590UX is configured as an RT.

Setup RT Dialog

Figure 24 Remote Terminal Setup Document


Data Tables

Data tables can be linked to a subaddress and edited using the


Current Data Table combo box and the Edit Data Table button
respectively (For more on Data Tables see the Data Table section on
page 27).

Data Device Corporation

25

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


RT Default Status

The Default RT Status can be modified using the check boxes on the
right side of the dialog. The Hex value will be represented below the
check boxes in the list box.
Accept Dynamic Bus Control

The Yes / No radio buttons specify if the RT will accept dynamic bus
control mode. If Yes is selected then the RT will accept the mode
code dynamic bus controller and respond with the Dynamic Bus
controller bit set it the status word. After the time specified in the
Delay list box the RT will become the Bus Controller.
If NO is selected then the RT will respond with a clear status and
continue normal operation.
If desired, the name of the RT can be modified by typing a new name
in the RT Name entry in the lower right corner of the dialog.
Error Injection

Each Tester Simulator card has the capability of modifying the data it
sends on the MIL-STD-1553 bus. To specify the error injected on the
bus press the Modify button. For more information on error injection
see the Error Injection section on page 41.
Note: Error injection is not supported with the BU-65590UX.

Legality Detection

This legality is described in the Legality section on page 31.


RT Example:

1) Continuing with our example from the Bus View Window, double
click on RT 1. Since our message is setup to send 5 words to RT 1
we must associate a data table with this RT at Sub address 1.
First we will click on the Rx Radio button; this will give all the
receiving Subaddresses for RT 1.
2) Click on the Edit Data Table button. This will open the edit data
window. Click on the New button twice, to create two new data
tables. We need to setup 2 tables, one for transmitting, and one
for receiving. After creating two tables click on the OK button (For
more details on Data Tables see the Data Table Section).

Data Device Corporation

26

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


3) Click on Subaddress 1 for Rx in the RT 1 setup window. From the
drop down list select Table_001. Table_001 is now assigned to
RT1-SA1 for all receive commands. Next RT2 must be setup.
4) Close the setup window for RT1 by clicking on the x in the upper
right-hand corner of the RT1 Setup window. Double click on RT 2
to open the setup window.
5) From the RT setup window check the radio button for Tx. This

shows all Tx subaddress for RT 2.


6) To assign a data table to subaddress 1, select Table_002 from the drop
down list for Current Data Table.
Note: Block mode for RT data tables is specified by selecting a data table for
the Starting Table, and then selecting a data table for the Ending
Table. Data tables must be set to Block Data RT in the Intermessage
Routines for Data Tables list in the Edit Data Table screen. In the
block mode, all tables must be contiguous and increasing.

7) The setup for the RTs is now complete. Close out of the RT setup
window by clicking on the x in the upper right-hand corner of the
RT2 Setup window.

Data Tables
The Edit Data Table dialog contains a list of all data tables created. At
a minimum the list will contain Illegal_Rx (index 0) and Illegal_Tx
(index 251) data tables. All data words that a data table contains are
displayed in a list on the lower left of the screen. Data tables can be
created, deleted, read, or written to using the buttons New, Delete,
Read, and Write respectively.

Data Device Corporation

27

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Figure 25 Edit Data Table

The number of data words a data table contains can be set using the
Table Size edit box and then clicking the Table Size drop down box.
Data words in the selected data table can be easily modified by either
double clicking on the word itself or by specifying all words to be a
certain value using the Specify edit box and clicking the Specify
button.
Data words can be displayed in Octal, Hex, or Decimal using the Data
Display radio buttons.
Two intermessage routines can be set for each Data Table. These
routines are No Operation, Set Service Request Bit in Status, Reset
Service Request Bit in Status, Interrupt after accessing Data Table,
Interrupt after Mode Command, Interrupt after Command Template
Match, Interrupt after Mode Command Template Match, Time-Tag
(Store RTC in a Circular Queue), Set Output Trigger, Reset Output
Trigger, Wait for Input Trigger, No Response on Both Buses, Set Busy
Bit in Status, Reset Busy Bit in Status, Block Data RT, Set Discrete 0,
Set Discrete 1, Set Discrete 2, Set Discrete 3, Reset Discrete 0, Reset
Discrete 1, Reset Discrete 2, and Reset Discrete 3. For more
information on the intermessage routines see Appendix B.
Note: Intermessage routines are not supported for the BU-65590UX.

Data Device Corporation

28

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


RT Example Setting Up Data Tables

1) For this example Table_002 must be setup. From the list of data
tables select Table_002.
2) The default size of the table is 32 words. In this example, only five
data words are being sent, therefore we must edit the values of
data words 1 through 5.
3) Click on the Specify button to set the data in the table to 1234.
4) Click on the OK button to exit the Edit Data Table window.

Setup for Monitor Operation


The Tester/Simulator boards can operate as real-time message
monitor at the same time it is processing BC frames and all 31 RTs.
The monitored information is saved to a stack file, which may be
viewed once the monitor has been halted. As described in the
Hardware Manual, the monitor is able to react to trigger inputs via the
D-Type connector as well as command and exception triggering.

Figure 26 MT (Monitor) Setup Document

Data Device Corporation

29

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


Capture

The Immediate selection causes the monitor to start capturing data as


soon as the RUN button is clicked.
The Trigger selection will cause the card to wait for a positive TTL
pulse at the trigger input of the D-Type connector. Once this input is
present, the monitor will start capturing data.
The capture Command setup allows the definition and masking of the
desired command word bits to be established. The command word
bits are entered into the appropriate edit boxes for RT Address, T/R,
Sub-Address and Word Count. Pressing the CMD MASK button
displays the command mask edit dialog and the command mask bits
can then be modified.
Exception instructs the monitor to start storing data once the selected
exception has occurred on the bus. Any combination of exceptions
may be selected from this list.
Pre and Post Trigger options allow the user to set how many
messages will be captured before a capture event or how many
messages the Tester/Simulator will wait until capturing begins after
the capture event.
Status Mask

The status mask check boxes determine which bits will set the
Flagged bit in Status exception error. If the box is not checked for a
specific status bit, then the Monitor will ignore that bit in the RT status
word. If the box is checked, and that bit is set in the RT status word,
then the Flagged bit in Status exception will be created. This
exception can then be used to trigger the monitor to start capturing the
bus traffic to the stack file. For our example we will use the default
settings (Capture Immediate).
Response Timeout

The RT Response Timeout (default is 14s) can be user specified


from 2s to 29s. This determines how long the monitor will wait
before the next transmission is decoded as a command word and
whether the current message is set with the no response exception.
Filtering

The Filtering button located on the MT Setup screen pops up the


Monitor Filter dialog. The monitor filter determines which messages
the monitor should capture and which messages should be ignored.

Data Device Corporation

30

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


Filtering may be performed based on RT address, sub-address,
Transmit/Receive bit, and bus.

Figure 27 MT (Monitor) Filter


Legality

The Legality button allows the user to define all legal and illegal
mode code messages. If the message is defined as illegal, the
Tester/Simulator will flag the message in the stack file as illegal. This
illegal message may also be used to trigger the monitor to start
capturing data into the stack file.

Figure 28 Mode Code Legality


Note: Intermessage routines are not available for the BU-65590UX.

Data Device Corporation

31

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Cmd Mask

The Cmd Mask button is used in conjunction with the command


word capture option to set which bits are dont care in the command
word.

Figure 29 MT (Monitor) Cmd Mask


Hard Disk Storage

Hard Disk Storage allows the user to specify stack file name, file
location and size. The size can be set as a discrete number of
messages, or the entire unused portion of the hard drive. The stack
file name can be entered into the edit box, or selected using the
standard windows file open dialog.
The Enable DMA check box was added to the Tester/Simulator Menu
in version 4.4.13. This box is not available when using the BU65570M, BU-65558 PCMCIA cards, and the BU-65590UX USB
Device.
New setup files created with version 4.4.14 of the Tester/Simulator
Menu or later will not have the Enable DMA check box checked by
default. The Enable DMA check box will be checked for any setup
files created with old versions of the Tester/Simulator menu.
Enabling DMA will allow the monitor to use the Tester/Simulator cards
DMA buffer when creating a stack file. If DMA is disabled than the
monitor will use the cards shared memory to store any captured MIL1553 data.
MT Example:

1) Select the Monitor by double-clicking on the MT icon in the Bus


View window.
2) The Tester/Simulator monitor can set the Capture Flag in a
message once a particular event has been detected. The event

Data Device Corporation

32

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


can be an External Trigger, an Exception condition, a specified
command word, or Immediate (the default state).
3) When all of the monitor parameters have been established, click
on the X button in the upper right-hand corner of the MT setup
window to close this window.
4) At the Bus View Dialog click on the run button to start the card.
This will bring up the Run Screen showing the activity of the bus.

Run Screen
The Run document displays the runtime parameters. All messages
are tabulated according to RT address. For each RT, the messages
are further sorted into columns designating error conditions such as
no response timeout, invalid data, and bit in status. The last column
lists the total number of messages monitored for the RT.

Figure 30 Run Window


Other status information is present on the Run Window. There are four
indicators, which show the current activity of the BC, RT, MT and
Replay functions. If the indicator is green, then the function is
operating. Otherwise it hasnt been started. Stack file name, total
commands and invalid commands are also displayed and dynamically
updated as messages are being processed.

Data Device Corporation

33

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


From this document there is a control button
that allows halting the
Tester/Simulator Boards. This will cause the message processing to
stop at the completion of the present message.
If the Continue button
is pressed, the message processing will
continue from the point that it was stopped.
The View Stack button causes the stack file specified in the MT Setup
document to be opened and displayed using the Stack viewer.
From our example, we see the lights for the BC, RT, MT are on while
the card is active. Once the card has completed operations, these
lights are turned off indicating the card has stopped. The Run Screen
also displays the two RTs that were emulated from our example.
Since we ran the frame twice each RT has two messages sent to it.
The total number of commands sent by the BC is four.
Stack Viewer

The Stack Viewer document displays previously captured stack files


that have been saved to disk. The default stack file presented to the
Run screen is the MyStack.fls. The file name may be modified in the
Monitor setup screen. The tag fls stands for Fixed Length Stack.

Figure 31 Stack View

Data Device Corporation

34

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


The previous versions of the DDC Tester/Simulator saved the monitor
information to a stack file with the .stk extension. This stack file used
a packed message format such that each message took only as much
space in the file as needed by the message. The Fixed Length Stack
uses a fixed amount of bytes for each message. Irrelevant of the size
of the message, the number of bytes used in the stack file for each
message is 80. This is equal to 8 header words*2 plus 32 data
words*2. This stack file format uses more space on the hard drive but
allows much faster storing and reading, and provides increased stack
file view performance.
Existing .stk stack files will have to be converted using the Stack File
Converter utility provided with the software. This utility will convert FLS
to STK files and vice-versa.
When a stack file is opened using the Tester/Simulator Menu, the
program changes to its Stack Viewer interface. This interface includes
movement options for traversing the message list, search options for
finding a particular type of message, and display options for displaying
data and time stamps in different formats. Messages are numbered
and displayed in the order in which they were received.
Each message is represented in the stack file. The stack file lists each
message by number, and gives a time that it issued by the BC. The
dt (delta time) represents the time it took for the message to
complete.
The stack viewer also shows the command word that was sent in the
message with any data, and the returned status word. If any error bits
are flagged then the exception is shown.
On the right side of the message is a graphical representation of the
message that was sent. Blue arrows represent mode codes. The
graphical representation of the message shows the bus the message
was sent on, the number of data words that were sent, and to which
RTs. If the message was a mode code, then the code will be
displayed below the arrow.

Data Device Corporation

35

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Searching

The Stack file may be searched for a Command Word, Status Word,
Data Word, or an Exception. The user may also cycle through the
stack file by using the Movement buttons.
Command Tab Allows the user to search for a command word in
the stack file. The user is able to enter in the command by using the
drop down boxes for RT address, Tx/Rx, Subaddress, Word
Count/Mode code. After selecting a number from the drop down box,
the binary value will appear in the command word.

Figure 32 Search Command Word


Status Tab Allows the user to search for a status word in the stack
file. The Status Word box displays the Hexadecimal value of the
Status bits. The Status Mask shows the Hexadecimal value of the
Terminal Address. The user may search by Terminal address by
selecting the appropriate Terminal Address number from the drop
down box. The user may also set the binary value of bits 15-11 to
dont care by clicking on them.

Data Device Corporation

36

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Figure 33 Search Status Word


The user may also select the status bits to search for. By clicking once
on them the bits become set. A second click sets the bit as dont care,
and a third click sets the bit value back to zero.
Data Tab Allows the user to search for a data word in the stack file.
The user can either enter in the hexadecimal value of the data word or
they may enter in the decimal value in the Data Word Decimal box.
The user also has the option of masking all the bits. The Data Word
box displays the Hexadecimal value of the word that is being
searched. The Data Mask box shows the Hexadecimal value of the
bits that are being masked.

Data Device Corporation

37

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Figure 34 Search Data Word


Exception Tab Allows the user to search for an exception or all
exceptions in the stack file. The user must click on the desired
exceptions.

Figure 35 Search Exception


Zero Time

By clicking on the Zero time at current message Button


the user
sets the time at current message to zero. Any previous messages will
have a negative time.
Data Radix

The user may choose the radix of the data by clicking on the Bin, Oct,
Dec, Hex buttons.

Data Device Corporation

38

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Setup for Replay Operation


The newest addition to the Tester/Simulator software is the Replay
mode. Once the replay parameters have been setup, the
Tester/Simulator Boards can reconstruct any DDC Tester/Simulator
stack file previously captured. This mode of operation allows the user
to capture bus traffic on a system in the field, and replay it in the lab.
This can be a very important debugging and integration tool. Another
very important function of the Tester/Simulator Boards is that they
are capable of replaying a previously stored stack file, and monitoring
the replay to a new stack file simultaneously.
Note: Replay mode is only supported with the BU-65570/72 and BU-65558
cards.

The replay setup document, accessed from the Tester Simulator


Setup tab, provides the controls to select the replay file, which is a
previously captured stack file, the RT response time, the replay start
requirements and the number of times the file should be replayed.

Figure 36 Replay Setup Document


Replay Start

The Tester/Simulator Boards can start the replay immediately when


the RUN button is pressed, or can wait for an external trigger to be
presented to the D-Type connector. This allows for synchronization
with other external RTs on the bus, or with the monitor function of the
Tester/Simulator Boards.
RT Response Time

RT Response Time designates the expected time allowable for an RT


response. This applies to internally emulated RTs and all external
RTs.

Data Device Corporation

39

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


Replay File

Replay File designates which stack file should be used during replay
operation. This file may be entered directly into the edit box, or
selected using the standard Windows File Open dialog. The replay file
name must not be the same as the monitors stack file. A pop-up
message will be displayed if they are the same.
The emulated RTs are selected and deselected by double-clicking the
icons in the main dialog screen. All RTs can be enabled or disabled
by clicking the All RTs Enable or Disable buttons. Enabled RTs are
displayed as a solid element on the bus, and disabled RTs are
displayed as a ghost element on the bus.
Note: If an RT was present on the bus when the stack file was created and
the RT is enabled in the replay setup, then the Tester/Simulator
Boards will replay all message responses recorded from this RT in
the stack file. If the RT was present, and is disabled in the replay
setup, then it should be physically present on the bus on which the
messages are being replayed. If the RT is not present, then every
message that involves this RT will cause a no response error.

Generate C Code
The Tester Simulator Menu has an added feature of creating the Csource code of your setup file. By clicking on the Generate Code
button
in the menu bar, the Tester Simulator program will output
your setup file to a C file.

Figure 37 Generate Code

Data Device Corporation

40

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION

Note: Code generation is not available for the BU-65590UX. Code


Generation will only generate code for the Tester Simulator RTL.

The user may select to have code written to run the RT, BC, and
generate interrupts for the BC and RT. After this window is closed the
user is prompted to save the generated code to a file.

Error Injection
Error injection allows the user to inject errors in a message being sent
by the BC, or set an error for a particular RT. The Tester/Simulator
can inject the following types of error: Bit Count, Word Count, Glitch,
Inverse, or Gap. A graphical representation of the error being injected
is displayed at the bottom of the dialog.
Note: Error injection is not supported for the BU-65590UX.

Figure 38 Error Injection


Error Types

Bit Count allows the user to add or take off bits from the message
being sent by the BC. The user can either add up to an extra three bits
to the message or leave off up to three bits. The user can also select
which word the error should be injected into. The graphical
representation deciphers the injected error by changing the wave
pattern. Red and white lines represent bits that are being left off the
message. A solid red line represents extra bits added to the message.

Data Device Corporation

41

BU-69065 Manual

TESTER/SIMULATOR MENU OPERATION


Cycling through the range will show the lines change on the graphical
representation shown at the bottom of the screen.
Word Count allows the user to add or take off words from the
message. The range of words changes from 32 to +1 words. Like the
Bit Count error, there is a graphical representation of the number of
words in the message. As the user cycles through the number of
words, the graphical representation is updated to show the injected
error.
Encoding Error

Adding an Encoding Error will change the Manchester waveform of


the given word. The two types of Encoding Errors are Glitch and
Inverse. Glitch errors will delay the start of the bit between 50ns to
3s.
Inverse Errors will invert the Manchester waveform bit for an interval
between 50ns to 3s.
Gap Error

Gap Error inserts a gap between two words in the frame. The range
of the gap is 3s to 32s. A graphical representation of this is shown
of the bottom of the screen. As the user scrolls between the words,
the gap will move. The gap will also become smaller and bigger as the
user changes gap time.
Response Error

The user may also inject an error so that the RT does not respond on
a particular bus, both buses, or the wrong bus. The user may also
have the RT respond late to the message. The RT can be
programmed to wait 12s to 30s. The RT can also be programmed
to have an error of being the wrong RT.

Data Device Corporation

42

BU-69065 Manual

APPENDIX A
RTL Error Messages
This appendix defines the RTL error codes and their corresponding messages. The error
codes are returned by RTL routines whenever an illegal condition is detected and they are
intended to facilitate the debugging of user programs. The error messages can be obtained by
calling "ddcGetErrorMessage".
000 NO_ERROR
Self explanatory.
101 NO_SPACE_FOR_TABLE
This message appears after calling the routine "ddcDefTableSize when insufficient memory is
available for a data table.
102 ILLEGAL_TABLE_ID
This message appears after calling the routine "ddcDefTableSize" when the argument "id" is
out of range. The range must be 1 - 1023.
103 ILLEGAL_TABLE_SIZE
This message appears after calling the routine "ddcDefTableSize" when the argument "size" is
out of range. The range must be 0 - 32.
121 FRAME_OVERFLOW
This message appears after calling the routine "ddcDefFrame" when the time required by a
major frame exceeds 232 microseconds.
122 MINOR_FRAME_OVERFLOW
This message appears after calling the routine "ddcDefFrame" when the time required by a
minor frame exceeds the minor frame time.
123 ILLEGAL_FRAME_LENGTH
This message appears after calling the routine "ddcDefFrame" when the argument "length" is
out of range. The range must be 1 - 1024.
141 ILLEGAL_FRAME_POSITION
This message appears after calling the routine "ddcRunBc" when the argument "pos" is out of
range. The range must be 1 - length (where length is the argument passed to
"ddcDefFrame").

Data Device Corporation

43

BU-69065 Manual

APPENDIX A
142 ILLEGAL_RUN_TIMES
This message appears after calling the routine "ddcRunBc" when the argument "times" is out
of range. The range must be -1 - 100,000,000.
161 ILLEGAL_MINOR_FRAME_TIME
This message appears after calling the routine "ddcDefMinorFrameTime" when its argument is
out of range. The range must be 0 - (232-1).
181 LOCK_BIT_TIME_OUT
This message appears when the data table read by the routine "ddcReadData" was not
released after being accessed by the card (BC/RT). This error is relevant only when data is
double-buffered.
201 ILLEGAL_GAP_ERROR
This message appears after calling "ddcDefRt" when the argument defining the gap error is
out of range. The range must be 3 - 5.
202 ILLEGAL_RESPONSE_TIME
This message appears after calling "ddcDefRt when the argument defining the late response
error is out of range. The range must be 12 - 30.
203 ILLEGAL_ALTER_TADR
This message appears after calling "ddcDefRt" when the argument defining the terminal
address or alternate terminal address is out of range.
204 ILLEGAL_LENGTH_ERROR
This message appears after calling "ddcDefRt" when the argument defining the word length or
word count error is out of range.
205 ILLEGAL_STATUS_ENC_ERR
This message appears after calling "ddcDefRt" when the parameters
ENCODE_STATUS_GLITCH or ENCODE_STATUS_INVERSE which define the status
encoding error have illegal values.
206 ILLEGAL_WORD_ENC_ERR
This message appears after calling "ddcDefRt" when the parameters
ENCODE_WORD_GLITCH or ENCODE_WORD_INVERSE that defines the data encoding
error have illegal values.

Data Device Corporation

44

BU-69065 Manual

APPENDIX A
207 ILLEGAL_ERROR_TYPE
This message appears after calling "ddcDefRt" when the argument defining the error type is
illegal.
208 ILLEGAL_DBC_DELAY
This message appears after calling "ddcDefRt" when the argument defining the delay after
accepting bus control is out of range. The range must be 40 - 130,000.
221 ILLEGAL_BUFFERING_MODE
This message appears after calling "ddcDefDataBuffering" when its argument has an illegal
value. The value must be either SINGLE or DOUBLE.
241 NOT_INIT_STATE
This message appears when a routine which should only be called in the INIT state was called
in another state. This error is not applicable to this library. It is only applicable to older versions
of the library.
242 NOT_HALT_STATE
This message appears when a routine which should only be called in the HALT state was
called in another state.
243 NOT_RUN_STATE
This message appears when a routine which should only be called in the RUN state was
called in another state.
244 NOT_HALT_OR_RUN_STATE
This message appears when a routine which should only be called in the HALT or RUN state
was called in the INIT state. This error is not applicable to this library. It is only applicable to
older versions of the library.
245 NOT_BCRT_HALT_STATE
This message appears when a routine which should only be called in the HALT or
RUN_MONITOR states was called while the BC/RT was running.
246 NOT_MON_HALT_STATE
This message appears when a routine which should only be called in the HALT or RUN_BCRT
states was called while the Monitor was running.
247 NOT_BCRT_RUN_STATE
This message appears when a routine which should only be called when the BC/RT is running
is called when it is halted.

Data Device Corporation

45

BU-69065 Manual

APPENDIX A
248 NOT_MON_RUN_STATE
This message appears when a routine which should only be called when the Monitor is
running is called when it is halted.
249 RUN_STATE
This message appears when the card is in the run state and a routine is called that cannot be
executed in run state.
250 CARD_NOT_ACTIVE
This message appears after calling the routine "ddcResetCard." When the card is not active
the routine "ddcResetCard" will not be able to run and will fail.
251 CARD_IS_NOT_READY
This message appears after calling a routine which resets the card ("ddcResetCard" or
"ddcLoadSetupToCard") when the versions of the DDC software and hardware are not
compatible.
252 RESET_IN_PROGRESS
This message appears after calling the routine "ddcResetCard" while other routines are trying
to access the card.
253 NOT_ENOUGH_MEMORY
This message appears after routines that access memory are called (ddcResetCard,
ddcEnableDma). These routines check to see if there is enough available free memory, if not
then the error is returned.
254 UNSUPPORTED_OS
This message appears if the operating system that the Tester/Simulator Menu is running on is
unsupported.
255 IOCTL_FAILED
This message appears if an IO control call made from the Runtime Library to the device driver
fails.
256 MMAP_FAILED
This message appears if the memory mapping call made from the Runtime Library to the
device driver fails.
257 MUNMAP_FAILED
This message appears if the memory un-mapping call made from the Runtime Library to the
device driver fails.

Data Device Corporation

46

BU-69065 Manual

APPENDIX A
258 INVALID_HANDLE
This message appears if the card device handle passed back from the system is invalid.
268 SYMBOL_CHECK_SUM_8
The above messages appear after calling "ddcResetCard" if the file ".i0" either incompatible
with the software version or its contents have been corrupted. The RTL software should be reinstalled from the original diskette.
269 CANNOT_OPEN_DDC_SYM
This message appears when the routine "ddcResetCard" cannot find the file ".i0".
281 ILLEGAL_LEGALITY
This message appears after calling the routine "ddcDefFrame" when the argument "legality" is
not equal to either YES or NO.
282 ILLEGAL_MODE_CODE
This message appears after calling the routine "ddcDefModeLegality" when the argument
"mode_code" is out of range. The range must be 0 - 31.
283 ILLEGAL_FIRST_MC_IMR
This message appears after calling "ddcDefModeRoutine" when the argument defining the first
intermessage routine is out of range. The range must be 1-127.
284 ILLEGAL_SECOND_MC_IMR
This message appears after calling "ddcDefModeRoutine" when the argument defining the
second intermessage routine is out of range. The range must be 1-127.
301 ILLEGAL_EMUL_TADR
This message appears after calling routines "ddcDefEmulateRt" or "ddcDefEmulateBc" when
the argument "tadr" is not in the range 0 30 for the RT and 0 31 for the BC.
302 ILLEGAL_EMULATE_BC
This message appears after calling the routine "ddcDefEmulateBc" when the argument
defining BC emulation has an illegal value. The value must be YES or NO.
303 ILLEGAL_EMULATE_RT
This message appears after calling the routine "ddcDefEmulateRt" when the argument
defining RT emulation has an illegal value. The value must be YES or NO.

Data Device Corporation

47

BU-69065 Manual

APPENDIX A
321 NO_SUCH_CODE_FILE
322 NO_BCRT_CODE_FILE
323 NO_IMRLIB_CODE_FILE
324 NO_MON_CODE_FILE
These messages appear when the file "*.io" cannot be opened or read properly.
341 ILLEGAL_MESSAGE_ID
This message appears after calling the routine "ddcDefMessage" when the argument defining
the message id is out of range. The range must be 1 1023.
342 ILLEGAL_CMD_TYPE
This message appears after calling the routine "ddcDefMessage" when the argument defining
the message type has an illegal value. The values must be RECEIVE, TRANSMIT, MODE, or
RT_RT.
343 ILLEGAL_MSG_ERR_TYPE
This message appears after calling the routine "ddcDefMessage" when the argument defining
the injected error type has an illegal value.
344 ILL_MSG_BIT_WORD_ERR
This message appears after calling the routine "ddcDefMessage" when the argument defining
the word in which the BC should inject extra bits is out of range. The range should be 0 - 32.
345 ILL_MSG_BIT_IN_WRD_ERR
This message appears after calling the routine "ddcDefMessage" when the argument defining
the number of extra/missing bits to be injected by the BC is out of range. The range should be:
1 - 3.
346 ILLEGAL_ENCODE_ERR_TYPE
This message appears after calling the routine "ddcDefMessage" when the argument defining
the encoding error type has an illegal value. The legal values are ENCODE_WORD_GLITCH
or ENCODE_WORD_INVERSE.
347 ILLEGAL_GAP_TIME_ERROR
This message appears after calling the routine "ddcDefMessage" when the argument defining
the gap time in the error injected by the BC has an illegal value. The legal values are 3, 4 or 5
microseconds.

Data Device Corporation

48

BU-69065 Manual

APPENDIX A
348 ILLEGAL_GAP_WORD_ERROR
This message appears after calling the routine "ddcDefMessage" when the argument defining
the location of the gap error injected by the BC is out of range. The gap is injected before word
N, where N must be in the range 1 - 32.
349 ILL_MSG_EN_BEGIN_WRD
This message appears after calling the routine "ddcDefMessage" when the argument defining
the location of the encoding error injected by the BC is out of range.
350 ILL_MSG_EN_WIDTH_ERR
This message appears after calling the routine "ddcDefMessage" when the argument defining
the width of the encoding error injected by the BC is out of range. The width of the encoding
error (glitch or inverse) must be in the range 1 - 60.
351 ILLEGAL_MESSAGE_BUS
This message appears after calling the routine "ddcDefMessage" when the argument defining
the bus has an illegal value. The value must be BUS_A or BUS_B.
353 ILLEGAL_FIRST_MSG_IMR
This message appears after calling the routine "ddcDefMessage" when the argument defining
the first intermessage routine is out of range. The range must be 1-127.
354 ILLEGAL_SECOND_MSG_IMR
This message appears after calling the routine "ddcDefMessage" when the argument defining
the second intermessage routine is out of range. The range must be 1-127.
355 ILLEGAL_TADDRESS
This message appears after calling the routine "ddcDefMessage" when the terminal address is
not compatible with the communication type field in the message structure.
356 ILLEGAL_SUBADDRESS
This message appears after calling the routine "ddcDefMessage" when the subaddress is not
compatible with the communication type field in the message structure.
382 ERROR_IN_COMMAND
This message appears when the host cannot pass instructions to the card. The card should be
reset.
383 COMMAND_DID_NOT_START
This message appears when the card is unable to complete a handshake with the host. The
card should be reset.

Data Device Corporation

49

BU-69065 Manual

APPENDIX A
384 COMMAND_DID_NOT_END
This message appears when the card is unable to complete a handshake with the host. The
card should be reset.
413 CARD_SELF_TEST_FAILED
This message appears after calling the routine "ddcResetCard" when the card self-test has
failed. If the problem persists, the card should be returned for repair.
431 ILLEGAL_BCST
This message appears after calling the routine "ddcSetAmpt" when the value for the amplitude
is out of the range from 0 to 4095. The PCI cards amplitude is greater than the PCMCIA card
(256).
441 ILLEGAL_AMPLITUDE
This message appears after calling the routine "ddcSetAmp" with an argument that is out of
range. The range must be 0 - 4096.
442 ILLEGAL_AMPLITUDE_PCI
This message appears when a routine which should only be called when the Monitor is
running is called when it is halted.
451 ILLEGAL_RESP_TIMEOUT
This message appears after calling the routine "ddcSetRespTimeout" with an argument that is
out of range. The legal values are: 14, 16, 18 and 20.
461 ILLEGAL_LAST_STATUS_TADR
This message appears after calling the routine "ddcDefLastStatus" when the argument that
defines the RT address is out of range. The range must be 0 - 30.
471 ILLEGAL_MAP_TADR
This message appears after calling the routine "ddcDefRtMapBlock" when the argument that
defines the RT address is out of range. The range must be 0 - 31.
472 ILLEGAL_MAP_SADR
This message appears after calling the routine "ddcDefRtMapBlock" when the argument that
defines the subaddress is out of range. The range must be 1 - 30.
473 ILLEGAL_MAP_TR_BIT
This message appears after calling the routine "ddcDefRtMapBlock" when the argument,
which defines transmit or receive has an illegal value. The legal values are either TRANSMIT
or RECEIVE.

Data Device Corporation

50

BU-69065 Manual

APPENDIX A
474 ILLEGAL_MAP_TABLE_ID
This message appears after calling the routine "ddcDefRtMapBlock" when the argument,
which defines the first or last data table ID is out of range. The range must be 0 - 251.
481 ILLEGAL_WR_ID
This message appears after calling the routine "ddcWriteData" when the argument, which
defines the data table ID is out of range. The range must be 0 - 251.
483 ILLEGAL_WR_COUNT
This message appears after calling the routine "ddcWriteData" when the argument, which
defines the number of words to be copied is out of range. The range must be 1 - 32.
484 ILLEGAL_WR_POS
This message appears after calling the routine "ddcWriteData" when the argument, "pos",
which defines the position in the table where the first word shall be copied, is incompatible with
the argument "count". The value of "pos" must be in the range 1 - 32 and the value of
"pos+count" must not exceed 33.
491 ILLEGAL_WR_MC_TADR
This message appears after calling the routine "ddcWriteModeData" when the argument
defining the RT address is out of range. The range must be 0 - 31.
492 ILLEGAL_WR_MODE_CODE
This message appears after calling the routine "ddcWriteModeData" when the argument
defining the mode code is out of range. The range must be 16 - 31.
501 ILLEGAL_RD_MC_TADR
This message appears after calling the routine "ddcReadModeData" when the argument
defining the RT address is out of range. The range must be 0 - 31.
502 ILLEGAL_RD_MODE_CODE
This message appears after calling the routine "ddcReadModeData" when the argument
defining the mode code is out of range. The range must be 16 - 31.
511 NO_NEW_MESSAGES
This message appears after calling the routine "ddcReadLastMonMessage" when the Monitor
has received no new messages since the routine was last called.
512 THIRD_BUFF_INT_ENABLED
This message appears after calling "ddcReadLastMonMessage" when the interrupt "1/3 of
circular buffer" is enabled instead of masked.

Data Device Corporation

51

BU-69065 Manual

APPENDIX A
522 INSUFFICIENT_MEMORY
This message appears after calling "ddcResetCard" when there isn't enough room in the host's
RAM.
523 ILLEGAL_IDEA_SYM
This message appears after calling the routine "ddcResetCard" when the ".i0" file is corrupted.
531 ILLEGAL_SET_BIT_TADR
This message appears after calling a routine that sets (resets) a bit in an RT's status when the
argument specifying the terminal address is out of range. The range must be 0 - 30.
532 ILLEGAL_SET_BIT_NO
This message appears after calling the routines "ddcSetReservedBit" or
"ddcResetReservedBit" when the argument specifying the bit location is out of range. The
range must be 1 - 3.
533 NOT_READY
This message appears after calling a routine to set/reset a status bit before a previous request
has been completed.
534 ILLEGAL_IMMEDIATE
This message appears after calling a routine that sets (resets) a bit in an RT's status when the
argument "immediate" has an illegal value. The value must be either DDC_YES or DDC_NO.
541 ILLEGAL_SELECT_TADR
This message appears after calling the routines "ddcSelectMessage", "ddcDeselectMessage",
"ddcSelectAllMessages" or "ddcDeselectAllMessages" when the argument defining the
terminal address is out of range. The range must be 0 - 31.
542 ILLEGAL_SELECT_TR
This message appears after calling the routines "ddcSelectMessage" or
"ddcDeselectMessage", when the argument defining transmit/receive is out of range. The legal
values are 0 (receive) and 1 (transmit).
543 ILLEGAL_SELECT_SADR
This message appears after calling the routines "ddcSelectMessage" or
"ddcDeselectMessage", when the argument defining subaddress is out of range. The range
must be 0 - 31.

Data Device Corporation

52

BU-69065 Manual

APPENDIX A
551 ILLEGAL_CAPTURE_TYPE
This message appears after calling the routine "ddcCaptureEvent" when the argument defining
the capture type has an illegal value. The legal values are: CAPTURE_IMMEDIATE,
CAPTURE_COMMAND_TEMPLATE, CAPTURE_EXCEPTION, CAPTURE_TRIGGER.
552 ILLEGAL_CAPTURE_EXCEPTION
This message appears after calling the routine "ddcCaptureEvent" when "type"="
CAPTURE_EXCEPTION" and par1 (which defines the exception condition) is out of range.
The range must be 0 - 8.
553 ILLEGAL_CAPTURE_TRIGGER
This message appears after calling the routine "ddcCaptureEvent" when "type"= "
CAPTURE_TRIGGER" and par1 (which defines the output trigger pin) is out of range. The
range must be 0 - 3.
561 ILLEGAL_EXCEPTION_BITS
This message appears after calling the routines "ddcDefMonExceptionStatus" or
"ddcDefBcExceptionStatus" when the argument defining the status bits to be flagged by the
Monitor or BC is out of range. The range is 0 - 0x7FF.
571 ILLEGAL_STACK_TYPE
This message appears after calling the routine "ddcDefMonitorStack" when the argument that
defines the stack type has an illegal value. The legal values are: CYCLIC or NON_CYCLIC.
572 CANNOT_READ_STACK
This message appears after a call to either "ddcReadLastMonMessage", or
"ddcReadMonStack" and the stack file is corrupted.
581 UNDEFINED_CARD_STATE
This message appears after calling the routine "ddcCardState" when the CARD_STATE
structure has illegal values (see routine "ddcCardState" for legal values).
591 ILLEGAL_FIRST_DTAB_IMR
This message appears after calling the routine "ddcDefTableRoutine" when the argument
defining the first intermessage routine is out of range. The range must be 1 - 128.
592 ILLEGAL_SECOND_DTAB_IMR
This message appears after calling the routine "ddcDefTableRoutine" when the argument
defining the second intermessage routine is out of range. The range must be 1 - 128.

Data Device Corporation

53

BU-69065 Manual

APPENDIX A
601 ILLEGAL_IN_MSG_POS
This message appears after calling the routine "ddcInsertMessage" when the argument "pos"
is out of range. The range must be 1 1024.
602 IN_MSG_NOT_READY
This message appears after calling the routine "ddcInsertMessage" when the card has not
completed the previous special request.
603 IN_MSG_BC_NOT_EMULATED
This message appears after calling the routine "ddcInsertMessage" when there is no emulated
BC.
611 ILLEGAL_CARD_NUMBER
This message appears when the IDEA card number is set out of the legal values of 0 through
7. This message is for backwards compatibility with the IDEA cards.
621 CANNOT_OPEN_STORE_FILE
This message appears after a call to "ddcStoreDriverVariables" when the file cannot be
opened. Check to see the location of the file, and if the file exists.
622 CANNOT_WR_TO_STORE_FILE
This message appears after a call to "ddcStoreDriverVariables" when the file cannot be written
to. Check the properties of the file (make sure not Read-Only -- or not already open).
623 CANNOT_CLOSE_STORE_FILE
This message appears after a call to "ddcStoreDriverVariables" when the file cannot be
closed.
631 CANNOT_OPEN_VARS_FILE
This message appears when a call to the routine ddcStoreDriverVariables when the file
name that is passed in by the user is incorrect name.
632 CANNOT_READ_VARS_FILE
This message appears when a call to the routine ddcStoreDriverVariables when the file
name that is passed in by the user is incorrect name.
633 CANNOT_CLOSE_VARS_FILE
This message appears when a call to the routine ddcStoreDriverVariables when the file
name that is passed in by the user is incorrect name.

Data Device Corporation

54

BU-69065 Manual

APPENDIX A
641 RESET_BEFORE_LOAD_FAILED
This message appears after calling the routine "ddcResetCard" when the DSP failed to boot.
642 NO_INIT_MK2_CODE_FILE
This message appears when a routine which should only be called when the Monitor is
running is called when it is halted.
643 MON_SHARED_MEM_ADR_ERR
This message appears after calling the routine "ddcResetCard" when there is a hardware
problem in the Monitor shared memory.
644 BCRT_SHARED_MEM_ADR_ERR
This message appears after calling the routine "ddcResetCard" when there is a hardware
problem in the BCRT shared memory.
645 MON_SHARED_MEM_DATA_ERR
This message appears after calling the routine "ddcResetCard" when there is a hardware
problem in the Monitor shared memory.
646 BCRT_SHARED_MEM_DATA_ERR
This message appears after calling the routine "ddcResetCard" when there is a hardware
problem in the BCRT shared memory.
647 NOT_DDC_HW
This message appears after calling the routine "ddcResetCard" when the DDC card is not
detected.
648 SELF_TEST_FAILED
This message appears after calling the routine "ddcResetCard" when the card's self-test has
failed.
671 SELF_TEST_FAILED
This message appears after calling the routine "ddcResetCard" when the card is of an
unknown type.
683 ILLEGAL_BUS_STATE
This message appears after calling the routine "ddcSelectBus" when the argument defining
the Monitor Bus state has an illegal value. Legal values are: OPEN or CLOSE.

Data Device Corporation

55

BU-69065 Manual

APPENDIX A
742 STP_CANNOT_OPEN_FILE
This message appears after calling the routine "ddcReplayRunBC" or ddcReplayRunRTs
when the Stack file cannot be opened.
800 WRONG_RBF_VERSION
This message appears when there is a failure in the FPGA or the version of the FPGA does
not match the version of the RTL.
801 WRONG_EMBEDDED_VERSION
This message appears when the "i0" version does not match the version of the RTL.
802 WRONG_DRIVER_VERSION
This message appears when the driver version that is installed on your system does not match
with the .dll that is installed in you windows\system directory.
803 CANNOT_ENABLE_CARD
This message appears when Card Services cannot gain access to the cards resources. This
message pertains to DOS only.
804 CANNOT_REGISTER_CARD
This message appears when Card Services cannot gain access to the card. This message
pertains to DOS only.
805 LOG_DEV_NOT_FOUND
This message appears after a call to the routine "ddcResetCard" when the Logical Device
number assigned to the card is not the card you are running in your program. Check the
active card number in the Tester Simulator Menu against the Logical Device Number in the
DDC 1553 Card Manager.
806 LOG_DEV_NOT_TESTSIM
This message appears after a call to the routine ddcResetCard when the Logical Device
number that is assigned to your card is not a Tester Simulator Card.
807 NO_NT40_MULTIPLE_CARDS
This message appears when using Windows NT. Multiple numbers of the same card are not
supported in Windows NT.
808 DMA_NOT_SUPPORTED
This message appears after a call to "ddcEnableDma", "ddcDisableDma", or
"ddcReadDmaStack" when the Tester Simulator Card does not support DMA. The BU65570M PC card does not support DMA.

Data Device Corporation

56

BU-69065 Manual

APPENDIX A
809 DMA_TOO_SMALL
This message appears when the amount of DMA allocated is too small for our card. The
Tester Simulator cards need at least 64K (up to 1M) for DMA.
810 AMPLITUDE_NOT_SUPPORTED
This message appears after a call to the routine "ddcReadAmp" when the Tester Simulator
card does not support software programmable amplitude. The BU-65570i, BU-65570v, BU65572T and the BU-65570M, are not supported.
811 IRIG_NOT_SUPPORTED
This message appears after a call to "ddcEnableIrig" or "ddcReadIrig" and the Tester
Simulator card does not have IRIG support. The BU-65570M card does not support IRIG.
812 COUPLING_NOT_SUPPORTED
This message appears after a call to "ddcSetCoupling" when coupling cannot be set in
software. The BU-65570M card does not allow the user to program the values for coupling.
813 INVALID_COUPLING
This message appears after a call to "ddcSetCoupling" when an invalid value for coupling is
set. For valid values for coupling see "ddcSetCoupling."
814 INVALID TERMINATION
This message appears after a call to "ddcSetCoupling" when an invalid value for termination is
set. For valid values for termination see "ddcSetCoupling."
815 INVALID_BUS_CONFIG
This message appears after a call to "ddcSetCoupling" when the value for the termination is
incompatible with your bus configuration. The Tester Simulator card cannot be set for Full
Termination and Transformer Coupled.
816 INVALID_IRIG_TIME
This message appears after a call to the routine "ddcSetIrig" when an invalid value of the IRIG
time is set. For the correct values of IRIG see "ddcSetIrig"
817 IRIG_ALREADY_PRESENT
This message appears when a call to the routine ddcSetIrig when there is an external source
of the IRIG clock. If there is an external source of the IRIG clock then the user cannot specify
IRIG time.
818 VXI_LIBRARY_NOT_INSTALLED
This message appears when using the BU-65572v card and the user does not have NI_VXI
support installed.
Data Device Corporation

57

BU-69065 Manual

APPENDIX A
819 VXI_REG_COMMUNICATION_ERROR
This message appears when using the BU-65572v card and the National Instruments software
returns an error when doing a Read/Write command.
820 VXI_MEM_COMMUNICATION_ERROR
This message appears when using the BU-65572v card and the National Instruments software
returns an error when accessing the memory.
824 IRQ_INSTALL_FAILED
This message appears when the interrupt that was assigned to the device failed to start.
Checks to see if there are any conflicts with this interrupt for the Tester Simulator card and any
other device installed in your system.
825 SELF_BOOT_NOT_SUPPORTED
This message appears when a call is made to ddcResetCard with the self boot features
enabled and the card being initialized does not possess the self-boot feature.
826 MON_STACK_OVERFLOW
This message appears when a call is made to ddcRead_mon_stack or
ddcRead_mon_stack_part and a message stack overflow had occurred.
827 CARD_NOT_READY_READ_RTC
This message appears when a call is made to ddcRead_mon_stack or
ddcRead_mon_stack_part and a message stack overflow had occurred.
828 CARD_NOT_READY_WRITE_RTC
This message appears when a call is made to "ddcSet_rtc" and the runtime library is unable to
write the RTC within 2msec.
829 CARD_NOT_READY_IRIG
This message appears when a call is made to "ddcEnableIrig" and the runtime library is
unable to enable IRIG because the card is busy.
830 VXI_A16_ONLY
This message appears when the DMA feature of a VXI card is being utilized and the NI-VXI
controller must be set to share memory in A32 space in order for this to be accomplished.
831 CARD_NOT_READY_SYNCHRONIZE
This message appears when a call is made to "ddcSynchronizeAllCards" and the runtime
library cannot perform this operation because the card is busy.

Data Device Corporation

58

BU-69065 Manual

APPENDIX A

832 CARD_NOT_READY_DEF_BC_EXCEPTION_STATUS
This message appears when a call is made to "ddcDef_bc_exception_status" and the runtime
library cannot perform this operation because the card is busy.
833 CARD_NOT_READY_DEF_EMULATE_BC
This message appears when a call is made to "ddcDef_emulate_bc" and the runtime library
cannot perform this operation because the card is busy.
834 CARD_NOT_READY_DEF_MINOR_FRAME_TIME
This message appears when a call is made to "ddcDef_minor_frame_time" and the runtime
library cannot perform this operation because the card is busy.
835 CARD_NOT_READY_RUN_BC
This message appears when a call is made to "ddcRun_bc" and the runtime library cannot
perform this operation because the card is busy.
836 CARD_NOT_READY_RUN_CONTINUE
This message appears when a call is made to "ddcRun_continue" and the runtime library
cannot perform this operation because the card is busy.
837 CARD_NOT_READY_SKIP_NEXT_MESSAGE
This message appears when a call is made to "ddcSkipNextMessage" and the runtime library
cannot perform this operation because the card is busy.
838 CARD_NOT_READY_INIT
This message appears when a call is made to "ddcResetCard" and the runtime library cannot
perform this operation because the card is busy.
839 CARD_NOT_READY_SET_RESP_TIMEOUT
This message appears when a call is made to "ddcSetRespTimeout" and the runtime library
cannot perform this operation because the card is busy.
840 CARD_NOT_READY_CAPTURE_EVENT
This message appears when a call is made to "ddcCapture_event" and the runtime library
cannot perform this operation because the card is busy.
841 CARD_NOT_READY_DEF_MON_EXCEPTION
This message appears when a call is made to "ddcDef_mon_exception_status" and the
runtime library cannot perform this operation because the card is busy.

Data Device Corporation

59

BU-69065 Manual

APPENDIX A

842 CARD_NOT_READY_DEF_MON_STACK
This message appears when a call is made to "ddcDef_monitor_stack" and the runtime library
cannot perform this operation because the card is busy.
843 CARD_NOT_READY_RUN_MON
This message appears when a call is made to "ddcRun_mon" and the runtime library cannot
perform this operation because the card is busy.
844 CARD_NOT_READY_SELECT_BUS
This message appears when a call is made to "ddcSelect_bus" and the runtime library cannot
perform this operation because the card is busy.
845 CARD_NOT_READY_REPLAY_RUN_BC
This message appears when a call is made to "ddcReplayRunBC" and the runtime library
cannot perform this operation because the card is busy.
846 CARD_NOT_READY_REPLAY_RUN_RTS
This message appears when a call is made to "ddcReplayRunRTs" and the runtime library
cannot perform this operation because the card is busy.
847 CARD_NOT_READY_RUN_RT
This message appears when a call is made to "ddcRun_rt" and the runtime library cannot
perform this operation because the card is busy.
848 CARD_NOT_READY_DEF_LEG_BCST
This message appears when a call is made to "ddcDef_legality_bcst" and the runtime library
cannot perform this operation because the card is busy.
849 CARD_NOT_READY_DEF_LEG_DET
This message appears when a call is made to "ddcDef_legality_detection" and the runtime
library cannot perform this operation because the card is busy.
850 CARD_NOT_READY_DEF_INT_CMD_TEMPL
This message appears when a call is made to "ddcDef_int_cmd_template" and the runtime
library cannot perform this operation because the card is busy.
851 LOG_DEV_IN_USE
This message appears when a call is made to "ddcResetCard" and the runtime library
determines that the device is already in use, or it was not shutdown properly.

Data Device Corporation

60

BU-69065 Manual

APPENDIX A
900 ILLEGAL_DAT_POS_MAG
This message appears when a call to the routine ddcfReadDataPart when the value of the
position is greater than 32.
901 ILLEGAL_DAT_POS
This message appears after a call to the routine "ddcReadDataPart" when the specified
position to read from is out of the range of the size of the data block.
902 WARNING_COUNT_READ
This message appears after a call to the routine ddcReadDataPart when the number of
words to be read is greater than the number of remain data words in the table. An example is
when you want to read 10 words starting at position 25, when there are only 32 data words in
a table.
950 CONFIG_FILE_NOT_FOUND
This message appears when a call is made to "ddcResetCard" and the configuration file is
corrupt or cannot be found.
951 DEVICE_MAPPING_ERROR
This message appears when a call is made to "ddcResetCard" and the device memory cannot
be mapped to user address space.
952 HW_NOT_DOS_ENABLED
This message appears when a call is made to "ddcResetCard" and the device is not enabled.
953 HW_DEVICE_NOT_FOUND
This message appears when a call is made to "ddcResetCard" and the device cannot be
found.
954 UNSUPPORTED_CARD_TYPE
This message appears when a call is made to "ddcResetCard" and the device being initialized
is not supported.

Data Device Corporation

61

BU-69065 Manual

APPENDIX B
Intermessage Routines
During each intermessage gap, the BC/RT executes 2 INTERMESSAGE ROUTINES specified
by the user. These routines are chosen from the supplied RTL and they can be assigned to:
Messages issued by the BC
Data tables accessed by emulated RTs
Mode commands executed by emulated RTs
The assignment is accomplished by calling routines "ddcDefMessage", "ddcDefTableRoutine,
and "ddcDefModeRoutine. If a message is internal to the Tester/Simulator card (i.e., between
an emulated BC and an emulated RT), the routine associated with the data table will be
ignored. Also, if the card emulates both RTs in a RT-to-RT message and does not emulate the
BC, only the transmitting RT executes the intermessage routines. The intermessage routines
are downloaded to the card during the RESET process. The following table lists the routines.

Data Device Corporation

62

BU-69065 Manual

APPENDIX B
Table 1 Intermessage Routines
INDEX
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27-30
31
32
33
34
35
36
37
38
39
40-43
44
45-46
47
48

FUNCTION
NO OPERATION
RETRY CURRENT MESSAGE ON ALTERNATE BUS
RETRY CURRENT MESSAGE AND REMAIN ON ALTERNATE BUS
RETRY ON SAME BUS
INTERRUPT ON END OF MESSAGE
INTERRUPT ON FRAME SYMBOL
SET SERVICE REQUEST BIT IN STATUS
RESET SERVICE REQUEST BIT IN STATUS
INTERRUPT AFTER ACCESSING TX/RX DATA TABLE
INTERRUPT AFTER MODE COMMAND
INTERRUPT AFTER TX/RX COMMAND TEMPLATE MATCH
INTERRUPT AFTER MODE COMMAND TEMPLATE MATCH
TIME-TAG (STORE RTC IN A CIRCULAR QUEUE)
RESERVED
RETRY ON SAME BUS AND THEN ON ALTERNATE BUS
SET STATUS BIT IN STATUS
RESET STATUS BIT IN STATUS
SET OUTPUT TRIGGER
RESET OUTPUT TRIGGER
WAIT FOR INPUT TRIGGER
RESERVED
NO RESPONSE ON BOTH BUSES
SET BUSY BIT IN STATUS
RESET BUSY BIT IN STATUS
SET BUSY AND RESET SRQ IN STATUS
SET SRQ AND RESET BUSY IN STATUS
RESERVED
SKIP NEXT MESSAGE
SET_DISCRETE_0
SET_DISCRETE_1
SET_DISCRETE_2
SET_DISCRETE_3
RESET_DISCRETE_0
RESET_DISCRETE_1
RESET_DISCRETE_2
RESET_DISCRETE_3
RESERVED
SKIP NEXT MESSAGE ONCE
RESERVED
BLOCK_DATA_BC
BLOCK_DATA_RT

Data Device Corporation

63

BU-69065 Manual

APPENDIX B

Definition of Routines
Function: NO OPERATION
Index: 1
Description:
This routine defines a null routine.
Used by: BC and RT
Function: RETRY CURRENT MESSAGE ON ALTERNATE BUS
Index: 2
Description:
If a communication error occurs, a retry is performed on the alternate bus. The next time the
message is issued the first bus will be used. The communication error types are:
command sync instead of data sync
invalid data word
gap between data words
no response
invalid status
terminal address error in status
Used by: BC
Function: RETRY CURRENT MESSAGE AND REMAIN ON ALTERNATE BUS
Index: 3
Description:
If a communication error occurs, a retry is performed on the alternate bus. The next time the
message is issued the alternate bus will be used. The communication error types are:
command sync instead of data sync
invalid data word
gap between data words
no response
invalid status
terminal address error in status
Used by: BC

Data Device Corporation

64

BU-69065 Manual

APPENDIX B

Function: RETRY ON SAME BUS


Index: 4
Description:
If a communication error occurs, a retry is performed on the same bus. The communication
error types are:
command sync instead of data sync
invalid data word
gap between data words
no response
invalid status
terminal address error in status
Used by: BC
Function: INTERRUPT ON END OF MESSAGE
Index: 5
Description:
An interrupt is issued to the host (provided the request is not masked) at the end of message.
The interrupt vector indicates whether or not there was a communication error or a bit set in
the status.
Used by: BC
Function: INTERRUPT ON FRAME SYMBOL
Index: 6
Description:
An interrupt is issued to the host (provided the request is not masked) when at the end of the
message the following symbols appear in the communication FRAME (provided the routine is
assigned to the symbol by "ddcDefMessage") :
SKIP
BREAK POINT
END OF MINOR FRAME
END OF MAJOR FRAME
Used by: BC
Function: SET THE SERVICE REQUEST BIT IN STATUS
Index: 7
Description:
This routine sets the service request bit in the basic status of the RT which responded to the
last command.
Used by: BC and RT

Data Device Corporation

65

BU-69065 Manual

APPENDIX B

Function: RESET THE SERVICE REQUEST BIT IN STATUS


Index: 8
Description:
This routine resets the service request bit in the basic status of the RT that responded to the
last command.
Used by: BC and RT
Function: INTERRUPT AFTER ACCESSING TX/RX DATA TABLE
Index: 9
Description:
An interrupt is issued to the host (provided the request is not masked) after an emulated RT
accesses a data table associated with a transmit/receive command. The vector pushed onto
the interrupt request queue defines:
the value of the ME bit in the status
data table number
command word
The type field in the interrupt vector equals 0 or 2.
Used by: RT (for TX/RX messages only)
Function: INTERRUPT AFTER MODE COMMANDS
Index: 10
Description:
An interrupt is issued to the host (provided the request is not masked) after an emulated RT
receives a mode command. The vector pushed onto the interrupt request queue defines:
the value of the ME bit in the status
mode code
command word
The type field in the interrupt vector equals 1 or 3.
Used by: RT (for mode commands only)
Function: INTERRUPT AFTER TX/RX COMMAND TEMPLATE MATCH
Index: 11
Description:
An interrupt is issued to the host (provided the request is not masked) after an emulated RT
accesses a data table associated with a transmit/receive command, which matches a template
as follows:
cmpwd = command AND maskwd.
The compare word (cmpwd) and mask word (maskwd) are defined by the RTL routine
"ddcDefIntCmdTemplate".
The type field in the interrupt vector equals 0 or 2.
Used by: RT (for TX/RX messages only)

Data Device Corporation

66

BU-69065 Manual

APPENDIX B

Function: INTERRUPT AFTER MODE COMMAND TEMPLATE MATCH


Index: 12
Description:
An interrupt is issued to the host (provided the request is not masked) after an emulated RT
executes a mode command that matches a template as follows:
cmpwd = command AND maskwd.
The compare word (cmpwd) and mask word (maskwd) are defined by the RTL routine
"ddcDefIntCmdTemplate".
The type field in the interrupt vector equals 1 or 3.
Used by: RT (for mode commands only)
Function: TIME-TAG
Index: 13
Description:
The 32 bit Real-Time-Clock of the BCRT is stored in a circular queue which contains up to 64
time tags. The time has a resolution of 2 microseconds and a maximum sampling inaccuracy
of 5 microseconds.
Used by: RT
Function: RETRY ON SAME BUS AND THEN ON ALTERNATE BUS
Index: 15
Description:
If a communication error occurs, a retry is performed on the same bus. If the communication is
still unsuccessful, a second retry will be performed on the alternate bus. Subsequent
messages will remain on the alternate bus. The communication error types are:
command sync instead of data sync
invalid data word
gap between data words
no response
invalid status
terminal address error in status
Used by: BC

Data Device Corporation

67

BU-69065 Manual

APPENDIX B

Function: SET STATUS BIT IN STATUS


Index: 16
Description:
This routine sets the status bit in the basic status of the RT that responded to the last
command.
Used by: BC
Function: RESET STATUS BIT IN STATUS
Index: 17
Description:
This routine resets the status bit in the basic status of the RT that responded to the last
command.
Used by: BC
Function: SET OUTPUT TRIGGER
Index: 18
Description:
This routine sets the BC Output Trigger on the D-type connector to logic "1".

Note: This pin is also used for START OF FRAME.

Used by: BC and RT


Function: RESET OUTPUT TRIGGER
Index: 19
Description:
This routine resets the BC Output Trigger on the D-type connector to logic "0".
Note: This pin is also used for START OF FRAME. Used by: BC and RT

Data Device Corporation

68

BU-69065 Manual

APPENDIX B

Function: WAIT FOR INPUT TRIGGER


Index: 20
Description:
The BC/RT waits until the BC input trigger pin is set to logic "1" or until the card returns to the
HALT state. (The pin must be held at logic "1" for a minimum of 5 microseconds)
Used by: BC
Function: NO RESPONSE ON BOTH BUSES
Index: 22
Description:
This routine disables the last active RT and thus allows no-responses to be generated during
the RUN_BCRT state. The RT is re-enabled by calling "ddcDefRt" or "ddcDefEmulateRt".
Used by: BC and RT
Function: SET THE BUSY BIT IN STATUS
Index: 23
Description:
This routine sets the Busy bit in the basic status of the RT that responded to the last
command.
Used by: BC and RT
Function: RESET THE BUSY BIT IN STATUS
Index: 24
Description:
This routine resets the Busy bit in the basic status of the RT that responded to the last
command.
Used by: BC and RT
Function: SET BUSY BIT AND RESET SRQ BIT IN STATUS
Index: 25
Description:
This routine sets the busy bit and resets the SRQ bit in the status word of the RT that
responded to the last command.
Used by: BC and RT

Data Device Corporation

69

BU-69065 Manual

APPENDIX B

Function: SET SRQ BIT AND RESET BUSY BIT IN STATUS


Index: 26
Description:
This routine sets the SRQ bit and resets the busy bit in the status word of the RT that
responded to the last command.
Used by: BC and RT
Function: SKIP NEXT MESSAGE
Index: 31
Description:
This routine causes the BC to skip the next message (and its intermessage routines) in the
frame. The host can re-enable message execution by calling "ddcSkipNextMessage".
Used by: BC.
Function: SET_DISCRETE_0
Index: 32
Description:
This routine sets discrete output pin 0 to a logic 1.
Note: This function is supported by the BU-65570 / BU-65572 PCI, cPCI and VME
cards.

Function: SET_DISCRETE_1
Index: 33
Description:
This routine sets discrete output pin 1 to a logic 1.
Note: This function is supported by the BU-65570 / BU-65572 PCI, cPCI and VME
cards.

Function: SET_DISCRETE_2
Index: 34
Description:
This routine sets discrete output pin 2 to a logic 1.
Note: This function is supported by the BU-65570 / BU-65572 PCI and VME cards.

Data Device Corporation

70

BU-69065 Manual

APPENDIX B

Function: SET_DISCRETE_3
Index: 35
Description:
This routine sets discrete output pin 3 to a logic 1.
Note: This function is supported by the BU-65570 / BU-65572 PCI and VME cards.

Function: RESET_DISCRETE_0
Index: 36
Description:
This routine sets discrete output pin 0 to a logic 0.
Note: This function is supported by the BU-65570 / BU-65572 PCI, cPCI and VME
cards.

Function: RESET_DISCRETE_1
Index: 37
Description:
This routine sets discrete output pin 1 to a logic 0.
Note: This function is supported by the BU-65570 / BU-65572 PCI, cPCI and VME
cards.

Function: RESET_DISCRETE_2
Index: 38
Description:
This routine sets discrete output pin 2 to a logic 0.
Note: This function is supported by the BU-65570 / BU-65572 PCI and VME cards.

Data Device Corporation

71

BU-69065 Manual

APPENDIX B

Function: RESET_DISCRETE_3
Index: 39
Description:
This routine sets discrete output pin 3 to a logic 0.
Note: This function is supported by the BU-65570 / BU-65572 PCI and VME cards.

Function: SKIP NEXT MESSAGE ONCE


Index: 44
Description:
This routine is similar to SKIP NEXT MESSAGE except that the message is executed only
once after it was re-enabled by the host.
Used by: BC.
Function: BLOCK_ DATA__BC
Index: 47
Description:
This routine supports BC block data mode (see ddcDefMessage). Each time the routine is
called it increments the current data table number associated with the message until the
corresponding last_table number is reached whereupon the routine reinitializes it to the
first_table number.
Used by: BC.
Function: BLOCK_ DATA_RT
Index: 48
Description:
This routine supports RT block data mode (see ddcDefRtMapBlock). Each time the routine is
called it increments the current data table number associated with the command until the
corresponding last_table number is reached whereupon the routine reinitializes it to the
first_table number.
Used by: RT.

Data Device Corporation

72

BU-69065 Manual

APPENDIX C
Communication Stack Structure
The COMMUNICATION STACK is a circular buffer that resides in the Monitor's shared
memory. Each monitored message is stored in the form of an 8 word MESSAGE HEADER
followed by data words, unless IRIG is used in which case there is a 10 word MESSAGE
HEADER. The routine "ddcDecodeMonMessage" can be used to read and decode the
communication stack's contents. If the stack file is created by the GUI Menu, it will contain a
dummy first message. This message will be used to encode extra information if necessary.
The messages can be obtained directly from the card's memory or from files of stacks
previously saved by the menu driven version of the DDC software. The MESSAGE HEADER
has the following structure:

Table 2 Monitor Message Header


15

14

IRIG FLG

13

12

11

10

WORD COUNT

CMODE

ILL

XX

CAP

BUS

RECEIVE / MODE COMMAND /SYSTEM DATE


TRANSMIT / INVALIDCOMMAND
TRANSMIT STATUS
RECEIVE STATUS
RTC HIGH
RTC LOW
0

S
W

L
W

ERROR CODE

FLS FLG

IRIG HIGH
IRIG LOW

Data Device Corporation

73

BU-69065 Manual

APPENDIX C
BUS
BUS = 0(1) defines A(B) as the active bus.
CAP
CAP = 1 signifies that the capture event was detected before the end of the message. The bit
remains set for all subsequent messages.
ILL
ILL = 1 denotes an illegal command. The possibilities are:
Transmit broadcast (non-mode) command
Mode command with broadcast forbidden by MIL-STD-1553B
Mode command with incorrect T/R bit
Unimplemented mode commands, as defined by the LEGALITY menu
CMODE
CMODE defines the message type. The possibilities are:
00 - Mode command
01 - Receive
10 - Transmit
11 - RT to RT
WORD COUNT
WORD COUNT defines the actual number of data words in the message stored in the circular
buffer. The field contains 6 bits; values 0 and 32 appear as 000000 and 100000 respectively.
IRIG FLG
If IRIG is enabled for the monitor session, then this value will be 02b. At all other times this
value is 00b.
RECEIVE/MODE COMMAND/SYSTEM DATE
This word contains valid RECEIVE or MODE commands.
If the message encodes IRIG and the stack file is a *.FLS GUI Menu generated stack file, then
the first message in the stack is a dummy message. This dummy message will contain the
computers system date as recorded when the stack file was created. This will allow a stack file
(FLS) to be referenced to a year as well as month, day and second.
TRANSMIT/INVALIDCOMMAND
This word contains TRANSMIT or INVALID commands.
TRANSMIT STATUS
This word contains the STATUS word belonging to a command with T/R=1.
RECEIVE STATUS
This word contains the STATUS word belonging to a command with T/R=0.
RTC HIGH
This word contains the most significant 16 bits of the time-tag.

Data Device Corporation

74

BU-69065 Manual

APPENDIX C
RTC LOW
This word contains the least significant 16 bits of the time-tag. The resolution is 2
microseconds
ERROR CODE
The ERROR CODE is a 6 bit field with the values given in Table 3.
LW
LW = 1 denotes that there was a long word error (time between successive syncs greater than
21 microseconds) in the second to last monitored data word.
V
V = 0 signifies a Manchester encoding error in the last monitored word.
P
P = 0 signifies a parity error in the last monitored word.
SW
SW = 0 signifies a short word error in the last monitored word.

FLS FLG
This 3 bit flag indicates that the stack file is a Fixed Length Stack (FLS) file. A FLS stack file
will only be created by the GUI Menu, and will contain a dummy first message. This format
reserves the maximum number of words per message. If a message is one word long or 32
words long, each entry in a FLS file will use 40 words (16 bit) if the stack does not implement
IRIG (see IRIG FLG), or 42 words if the stack does encode IRIG.
Note:
The bits LW, V, P, and SW have meaningful values only if the ERROR CODE
indicates an INVALID WORD. Erroneous messages always result in an ERROR
CODE with a non-zero value in the 4 least significant bits.

Data Device Corporation

75

BU-69065 Manual

APPENDIX C

Table 3 Error Codes


VALUE

ERROR

00 0000
00 0001
00 0010
00 0011
00 0100
00 0101
00 0110
00 0111
00 1000
00 1001 00 1011
00 1100
00 1101
00 1110
00 1111
01 0000
01 0001
01 0010
01 0011
01 0100
01 0101
01 0110
01 0111
01 1000
01 1001
01 1010
01 1011
01 1100
01 1101
01 1110
01 1111
10 0000
10 0001
10 0010
10 0011
10 0100
10 0101
10 0110

NO ERROR
Wrong RT address in TX status and invalid data
Flagged bit in TX status and invalid data
Invalid data
Invalid command
Flagged bit in TX status and invalid data
Wrong RT address in TX status and invalid data
Invalid data
Invalid command
UNDEFINED

Data Device Corporation

Extra word
Flagged bit in TX status and extra word
Wrong RT address in TX status and extra word
Invalid command
NO ERROR
Flagged bit in TX status
Wrong RT address in TX status
UNDEFINED
Gap in data word
Flagged bit in TX status and gap
Wrong RT address in TX status and gap
Wrong RT address in TX status and invalid data
Invalid data
Flagged in TX status and invalid data
Wrong RT address in TX status and invalid data
Invalid data
Inverse sync (data word)
Flagged bit in TX status and inverse sync
Wrong RT address in TX status and inverse sync
Flagged bit in TX status and invalid data
NO ERROR
Flagged bit in TX status
Wrong RT address in TX status
UNDEFINED
No response (TX)
Wrong RT address in TX status and invalid TX status
Flagged bit in status invalid TX status

76

BU-69065 Manual

APPENDIX C
Table 3 Error Codes
VALUE
10 0111
10 1000
10 1001 10 1011
10 1100
10 1101
10 1110
10 1111
11 0000
11 0001
11 0010
11 0011
11 0100
11 0101
11 0110
11 0111
11 1000
11 1001
11 1010
11 1011
11 1100
11 1101
11 1110
11 1111

ERROR
Invalid TX status
Invalid TX status
UNDEFINED
Early response TX
Flagged bin in TX status and invalid TX status
Invalid status TX
Invalid status TX
NO ERROR
Flagged bit in TX status
Wrong RT address in RX status
UNDEFINED
No response RX
Flagged bit in TX status and no response in RX status
Wrong RT address in TX status and no response RX
status
UNDEFINED
Invalid status RX
Flagged bit in TX status and invalid status
Wrong RT address in TX status and invalid RXstatus
UNDEFINED
Early response RX
Flagged bit in TX status and early RX response
Wrong RT address in TX status and early response
UNDEFINED

The stack resides in the Monitor's shared memory and contains approximately 6K words.
Raw stack data is not available for access from the card. The Monitor stack data must be
transferred to a host buffer via DMA and then processed to a user buffer.

Data Device Corporation

77

BU-69065 Manual

INDEX

841
CARD_NOT_READY_DEF_MON_EXC
EPTION ................................................... 59
842
CARD_NOT_READY_DEF_MON_STA
CK............................................................ 60
843 CARD_NOT_READY_RUN_MON.... 60
844 CARD_NOT_READY_SELECT_BUS60
845
CARD_NOT_READY_REPLAY_RUN_
BC............................................................ 60
846
CARD_NOT_READY_REPLAY_RUN_
RTS.......................................................... 60
847 CARD_NOT_READY_RUN_RT........ 60
848
CARD_NOT_READY_DEF_LEG_BCST60
849 CARD_NOT_READY_DEF_LEG_DET60
850
CARD_NOT_READY_DEF_INT_CMD_
TEMPL .................................................... 60
851 LOG_DEV_IN_USE ............................ 60
950 CONFIG_FILE_NOT_FOUND ........... 61
951 DEVICE_MAPPING_ERROR ............ 61
952 HW_NOT_DOS_ENABLED............... 61
953 HW_DEVICE_NOT_FOUND ............. 61
954 UNSUPPORTED_CARD_TYPE......... 61
Error Messages (RTL)
000 NO_ERROR ......................................... 43
101 NO_SPACE_FOR_TABLE ................. 43
102 ILLEGAL_TABLE_ID ........................ 43
103 ILLEGAL_TABLE_SIZE .................... 43
121 FRAME_OVERFLOW ........................ 43
122 MINOR_FRAME_OVERFLOW ......... 43
123 ILLEGAL_FRAME_LENGTH............ 43
141 ILLEGAL_FRAME_POSITION ......... 43
142 ILLEGAL_RUN_TIMES ..................... 44
161 ILLEGAL_MINOR_FRAME_TIME... 44
181 LOCK_BIT_TIME_OUT ..................... 44
201 ILLEGAL_GAP_ERROR .................... 44
202 ILLEGAL_RESPONSE_TIME............ 44
203 ILLEGAL_ALTER_TADR.................. 44
204 ILLEGAL_LENGTH_ERROR ............ 44
205 ILLEGAL_STATUS_ENC_ERR......... 44

B
BUS_A.............................................................49
BUS_B .............................................................49
C
Capture_Exception...........................................53
Communication Stack......................................73
D
DDC 1553 Card Manager for 95/98/2000 .........6
E
error messages (RTL)
828 CARD_NOT_READY_WRITE_RTC .58
829 CARD_NOT_READY_IRIG ...............58
830 VXI_A16_ONLY .................................58
831
CARD_NOT_READY_SYNCHRONIZE58
832
CARD_NOT_READY_DEF_BC_EXCEP
TION_STATUS.......................................59
833
CARD_NOT_READY_DEF_EMULATE
_BC ..........................................................59
834
CARD_NOT_READY_DEF_MINOR_FR
AME_TIME.............................................59
835 CARD_NOT_READY_RUN_BC........59
836
CARD_NOT_READY_RUN_CONTINU
E ...............................................................59
837
CARD_NOT_READY_SKIP_NEXT_ME
SSAGE.....................................................59
838 CARD_NOT_READY_INIT................59
839
CARD_NOT_READY_SET_RESP_TIM
EOUT.......................................................59
840
CARD_NOT_READY_CAPTURE_EVE
NT ............................................................59

Data Device Corporation

78

BU-69065 Manual

INDEX
451 ILLEGAL_RESP_TIMEOUT.............. 50
461 ILLEGAL_LAST_STATUS_TADR ... 50
471 ILLEGAL_MAP_TADR...................... 50
472 ILLEGAL_MAP_SADR ...................... 50
473 ILLEGAL_MAP_TR_BIT ................... 50
474 ILLEGAL_MAP_TABLE_ID.............. 51
481 ILLEGAL_WR_ID............................... 51
483 ILLEGAL_WR_COUNT ..................... 51
484 ILLEGAL_WR_POS............................ 51
491 ILLEGAL_WR_MC_TADR................ 51
492 ILLEGAL_WR_MODE_CODE .......... 51
501 ILLEGAL_RD_MC_TADR................. 51
502 ILLEGAL_RD_MODE_CODE ........... 51
511 NO_NEW_MESSAGES....................... 51
512 THIRD_BUFF_INT_ENABLED......... 51
522 INSUFFICIENT_MEMORY ............... 52
523 ILLEGAL_IDEA_SYM ....................... 52
531 ILLEGAL_SET_BIT_TADR ............... 52
532 ILLEGAL_SET_BIT_NO .................... 52
533 NOT_READY ...................................... 52
534 ILLEGAL_IMMEDIATE..................... 52
541 ILLEGAL_SELECT_TADR ................ 52
542 ILLEGAL_SELECT_TR...................... 52
543 ILLEGAL_SELECT_SADR ................ 52
551 ILLEGAL_CAPTURE_TYPE ............. 53
552 ILLEGAL_CAPTURE_EXCEPTION . 53
553 ILLEGAL_CAPTURE_TRIGGER ...... 53
561 ILLEGAL_EXCEPTION_BITS........... 53
571 ILLEGAL_STACK_TYPE .................. 53
572 CANNOT_READ_STACK.................. 53
581 UNDEFINED_CARD_STATE............ 53
591 ILLEGAL_FIRST_DTAB_IMR .......... 53
592 ILLEGAL_SECOND_DTAB_IMR ..... 53
601 ILLEGAL_IN_MSG_POS ................... 54
602 IN_MSG_NOT_READY ..................... 54
603 IN_MSG_BC_NOT_EMULATED ...... 54
611 ILLEGAL_CARD_NUMBER ............. 54
621 CANNOT_OPEN_STORE_FILE ........ 54
622 CANNOT_WR_TO_STORE_FILE..... 54
623 CANNOT_CLOSE_STORE_FILE ...... 54
631 CANNOT_OPEN_VARS_FILE .......... 54
632 CANNOT_READ_VARS_FILE.......... 54
633 CANNOT_CLOSE_VARS_FILE ........ 54
641 RESET_BEFORE_LOAD_FAILED ... 55
642 NO_INIT_MK2_CODE_FILE............. 55
643 MON_SHARED_MEM_ADR_ERR ... 55
644 BCRT_SHARED_MEM_ADR_ERR .. 55
645 MON_SHARED_MEM_DATA_ERR. 55
646 BCRT_SHARED_MEM_DATA_ERR 55
647 NOT_DDC_HW ................................... 55
648 SELF_TEST_FAILED ......................... 55

206 ILLEGAL_WORD_ENC_ERR............44
207 ILLEGAL_ERROR_TYPE ..................45
208 ILLEGAL_DBC_DELAY ....................45
221 ILLEGAL_BUFFERING_MODE........45
241 NOT_INIT_STATE ..............................45
242 NOT_HALT_STATE ...........................45
243 NOT_RUN_STATE .............................45
244 NOT_HALT_OR_RUN_STATE .........45
245 NOT_BCRT_HALT_STATE...............45
246 NOT_MON_HALT_STATE ................45
247 NOT_BCRT_RUN_STATE .................45
248 NOT_MON_RUN_STATE ..................46
249 RUN_STATE........................................46
250 CARD_NOT_ACTIVE.........................46
251 CARD_IS_NOT_READY ....................46
252 RESET_IN_PROGRESS ......................46
253 NOT_ENOUGH_MEMORY..........46, 47
268 SYMBOL_CHECK_SUM_8................47
269 CANNOT_OPEN_DDC_SYM ............47
281 ILLEGAL_LEGALITY ........................47
282 ILLEGAL_MODE_CODE ...................47
283 ILLEGAL_FIRST_MC_IMR ...............47
284 ILLEGAL_SECOND_MC_IMR ..........47
301 ILLEGAL_EMUL_TADR....................47
302 ILLEGAL_EMULATE_BC .................47
303 ILLEGAL_EMULATE_RT..................47
321 NO_SUCH_CODE_FILE.....................48
322 NO_BCRT_CODE_FILE .....................48
323 NO_IMRLIB_CODE_FILE..................48
324 NO_MON_CODE_FILE ......................48
341 ILLEGAL_MESSAGE_ID...................48
342 ILLEGAL_CMD_TYPE.......................48
343 ILLEGAL_MSG_ERR_TYPE .............48
344 ILL_MSG_BIT_WORD_ERR .............48
345 ILL_MSG_BIT_IN_WRD_ERR ..........48
346 ILLEGAL_ENCODE_ERR_TYPE......48
347 ILLEGAL_GAP_TIME_ERROR.........48
348 ILLEGAL_GAP_WORD_ERROR ......49
349 ILL_MSG_EN_BEGIN_WRD.............49
350 ILL_MSG_EN_WIDTH_ERR .............49
351 ILLEGAL_MESSAGE_BUS ...............49
353 ILLEGAL_FIRST_MSG_IMR.............49
354 ILLEGAL_SECOND_MSG_IMR........49
356 ILLEGAL_SUBADDRESS..................49
382 ERROR_IN_COMMAND....................49
383 COMMAND_DID_NOT_START .......49
384 COMMAND_DID_NOT_END............50
413 CARD_SELF_TEST_FAILED ............50
431 ILLEGAL_BCST..................................50
441 ILLEGAL_AMPLITUDE.....................50
442 ILLEGAL_AMPLITUDE_PCI ............50

Data Device Corporation

79

BU-69065 Manual

INDEX
BLOCK_ DATA_RT .................................. 72
INTERRUPT AFTER ACCESSING TX/RX
DATA TABLE ........................................ 66
INTERRUPT AFTER MODE COMMAND
TEMPLATE MATCH ............................. 67
INTERRUPT AFTER MODE COMMANDS66
INTERRUPT AFTER TX/RX COMMAND
TEMPLATE MATCH ............................. 66
INTERRUPT ON END OF MESSAGE...... 65
INTERRUPT ON FRAME SYMBOL ........ 65
NO OPERATION........................................ 64
NO RESPONSE ON BOTH BUSES .......... 69
RESET DISCRETE 0 .................................. 71
RESET DISCRETE 1 .................................. 71
RESET DISCRETE 2 .................................. 71
RESET DISCRETE 3 .................................. 72
RESET OUTPUT TRIGGER ...................... 68
RESET STATUS BIT IN STATUS ............ 68
RESET THE BUSY BIT IN STATUS ........ 69
RESET THE SERVICE REQUEST BIT IN
STATUS .................................................. 66
RETRY CURRENT MESSAGE AND
REMAIN ON ALTERNATE BUS ......... 64
RETRY CURRENT MESSAGE ON
ALTERNATE BUS ................................. 64
RETRY ON SAME BUS............................. 65
RETRY ON SAME BUS AND THEN ON
ALTERNATE BUS ................................. 67
SET BUSY BIT AND RESET SRQ BIT IN
STATUS .................................................. 69
SET DISCRETE 0 ....................................... 70
SET DISCRETE 1 ....................................... 70
SET DISCRETE 2 ....................................... 70
SET DISCRETE 3 ....................................... 71
SET OUTPUT TRIGGER ........................... 68
SET SRQ BIT AND RESET BUSY BIT IN
STATUS .................................................. 70
SET STATUS BIT IN STATUS ................. 68
SET THE BUSY BIT IN STATUS ............. 69
SET THE SERVICE REQUEST BIT IN
STATUS .................................................. 65
SKIP NEXT MESSAGE ............................. 70
SKIP NEXT MESSAGE ONCE ................. 72
TIME-TAG.................................................. 67
WAIT FOR INPUT TRIGGER ................... 69
Interrupt ............................................... 51, 65, 66
Invalid Word.................................................... 75

683 ILLEGAL_BUS_STATE......................55
742 STP_CANNOT_OPEN_FILE ..............56
800 WRONG_RBF_VERSION...................56
801 WRONG_EMBEDDED_VERSION ....56
802 WRONG_DRIVER_VERSION ...........56
803 CANNOT_ENABLE_CARD ...............56
804 CANNOT_REGISTER_CARD............56
805 LOG_DEV_NOT_FOUND ..................56
806 LOG_DEV_NOT_TESTSIM ...............56
807 NO_NT40_MULTIPLE_CARDS ........56
808 DMA_NOT_SUPPORTED ..................56
809 DMA_TOO_SMALL ...........................57
810 AMPLITUDE_NOT_SUPPORTED ....57
811 IRIG_NOT_SUPPORTED ...................57
812 COUPLING_NOT_SUPPORTED .......57
813 INVALID_COUPLING........................57
814 INVALID_TERMINATION ................57
815 INVALID_BUS_CONFIG ...................57
816 INVALID_IRIG_TIME ........................57
817 IRIG_ALREADY_PRESENT ..............57
818 VXI_LIBRARY_NOT_INSTALLED..57
819
VXI_REG_COMMUNICATION_ERRO
R...............................................................58
820
VXI_MEM_COMMUNICATION_ERRO
R...............................................................58
824 IRQ_INSTALL_FAILED.....................58
900 ILLEGAL_DAT_POS_MAG ............61
901 ILLEGAL_DAT_POS ..........................61
902 WARNING_COUNT_READ...............61
Exception .........................................................53
F
FLS (Fixed Length Stack)................................34
H
headquarters ................................................... viii
I
Icon
Caution..........................................................ix
Disk ................................................................x
Idea/Tip .........................................................ix
Note...............................................................ix
Reference .......................................................x
Warning.........................................................ix
Intermessage Routines .....................................62
BLOCK_ DATA_BC...................................72

Data Device Corporation

L
Legality............................................................ 47

80

BU-69065 Manual

INDEX
Lock .................................................................44

Replay Mode ..................................................... 14


STK.................................................................. 35

M
T

Message .....................................................48, 73
Message Header ...............................................73
Monitor Message Header
BUS..............................................................74
CAP..............................................................74
CMODE .......................................................74
ERROR CODE ............................................75
FLS FLG ......................................................75
ILL ...............................................................74
INVALID COMMAND...............................74
IRIG FLG.....................................................74
LW ...............................................................75
MODE COMMAND ...................................74
P .................................................................75
RECEIVE.....................................................74
RECEIVE STATUS.....................................74
RTC HIGH...................................................74
RTC LOW....................................................75
SW ...............................................................75
SYSTEM DATE ..........................................74
TRANSMIT .................................................74
TRANSMIT STATUS .................................74
V .................................................................75
WORD COUNT...........................................74

technical support.............................................viii
Tester/Simulator Menu ................................ 1, 15
Bus Controller.............................................. 18
Conventions ................................................. 16
Data Tables .................................................. 27
Error Injection.............................................. 41
Encoding Error ........................................ 42
Error Types .............................................. 41
Gap Error ................................................. 42
Response Error ........................................ 42
Generate C Code.......................................... 40
Monitor ........................................................ 29
Capture..................................................... 30
Cmd Mask................................................ 32
Filtering ................................................... 30
Hard Disk Storage ................................... 32
Legality.................................................... 31
Response Timeout ................................... 30
Status Mask.............................................. 30
Remote Terminal ......................................... 25
Replay.......................................................... 39
Replay Start ............................................. 39
RT Response Timeout ............................. 39
Run .............................................................. 33
Stack Viewer................................................ 34
Command................................................. 36
Data.......................................................... 37
Data Radix ............................................... 38
Exception ................................................. 38
Searching ................................................. 36
Status ....................................................... 36
Zero Time ................................................ 38
Transmit..................................................... 48, 50

R
Receive.......................................................48, 50
RT_RT .............................................................48
S
SelectBus .........................................................55
SKIP.................................................................65
Software Installation
Windows 95/98/NT/2000...............................2
Software License and Policies ..........................vi
Software Operations
BC Mode......................................................14
Monitor Mode ....................................................14

Data Device Corporation

W
Web site ..........................................................viii

81

BU-69065 Manual