®
Data Device Corporation
105 Wilbur Place
Bohemia, New York 11716
631-567-5600 Fax: 631-567-7358
www.ddc-web.com
FOR MORE INFORMATION CONTACT:
Technical Support:
1-800-DDC-5757 ext. 7771
FEATURES
•Type II PCMCIA 2.10 Compatible
PC Card
•Simulation and Test of
MIL-STD-1553 Systems
•64K Words of Shared RAM
•Simultaneous Emulation of BC,
Up to 31 RT’s, and an MT
•Selective Message Monitor
•32-Bit Time Tag with 1 µsec
resolution
• User-Friendly Menu Software for
Windows®9x/2000/XP and
Windows NT®
•Compatibility with Previous DDC
Tester/Simulator Cards
•Replay of Previously Recorded
Bus Traffic via Menu and
Runtime Library
•Source Code Generation Wizard via
Menu Software
DESCRIPTION
DDC's BU-65570M is a versatile, Type II PCMCIA Card designed for the
test and simulation of MIL-STD-1553 systems. It provides full, intelligent
interfacing between the serial dual redundant MIL-STD-1553 data bus
and an IBM PC. User-friendly software allows the BU-65570M to con-
currently simulate a Bus Controller (BC), and up to 31 Remote Terminals
(RT), and provides a selectable, triggerable Bus Monitor (MT).
The BC and RT’s evaluate each 1553 message in real time to deter-
mine if any format errors have occurred. Separate registers are main-
tained for the last command word and the last status word of each
emulated RT. In addition, the user may inject errors into any 1553
message issued by the emulated BC or RT’s. These errors include
word count, bit count, zero crossing, parity, and, in the case of emu-
lated RT’s, response errors.
The intelligent MT captures the 1553 bus traffic. The user can define
when MT operation is to begin and which messages (based on the
RT address, T/R bit, and subaddress) are to be captured. Monitored
information can be displayed on a message by message basis.
User friendly menu software for Windows 9x, Windows NT, and Windows
2000/XP are supplied with ‘C’, Visual Basic, and LabVIEW programming
libraries. The Windows Menu structure allows instant access to the data
bus BC, RT, MT and playback functions via an Intuitive Graphical Interface
(IGI). The libraries provide complete compatibility with previous versions of
DDC Tester/Simulator software. This allows software developed for these
cards to be quickly ported to the BU-65570M with minimal conversion over-
head performed by the user. These software features, combined with the
portability of the PC Card format, make the BU-65570M the best choice for
portable dynamic test and simulation of MIL-STD-1553 systems.
BU-65570M
PCMCIA FORMAT MIL-STD-1553B
TESTER/SIMULATOR CARD
Make sure the next
Card you purchase
has...
© 2002 Data Device Corporation
All trademarks are the property of their respective owners.
2
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
FIGURE 1. BU-65570M BLOCK DIAGRAM
DATA
ADDRESS
ADDRESS
DATA
Dual Port
Shared RAM
64K Words
CH A
CH B
Protocol
Unit
PCMCIA
INTERFACE
ADAPTER 64K Words
Program RAM
Card
Configuration
Register
Attribute
Memory
(Tuples)
CPU
3
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
TABLE 2. BU-65570M HARDWARE SPECIFICATIONS
PARAMETER MIN TYP MAX UNITS
ABSOLUTE MAXIMUM RATING
Supply Voltage
• +5 V -0.3 7.0 V
RECEIVER
Threshold Voltage
• Transformer Coupled,
Measured on Stub
0.56 Vp-p
TRANSMITTER
Differential Output Voltage
• Transformer Coupled,
Measured on Stub
18 20 27 Vp-p
POWER SUPPLY REQUIREMENTS
Voltages/Tolerances
• +5V
Current Drain @ +5.0V
• Idle
• 50% Duty Cycle
• 100% Duty Cycle
4.5
220
720
870
5.5
240
800
1000
V
mA
mA
mA
TABLE 1. BU-65570M REQUIREMENTS AND
CAPABILITIES
HARDWARE REQUIREMENTS
• Pentium or compatible computer with PCMCIA Adapter
• DDC’s BU-65570M1 MIL-STD-1553 Simulator and Tester Card
SOFTWARE REQUIREMENTS
• DOS, Windows 9x, Windows NT, or Windows 2000/XP
• DDC’s software CD-ROM
AVAILABLE OPERATIONS
• Tests and simulates MIL-STD-1553 BC and up to 31 RT’s
• Provides independent MT mode operation
• Error injection and detection capabilities
1553 MESSAGE TIMING
RT Response Time
(See Note 1)
BC Intermessage Gap
(See Note 2)
BC/RT/MT Response Timeout
(See Note 3)
Transmitter Watchdog Timeout
MT Minimum gap for capture
2
4
10
25
700
29
µsec
µsec
µsec
µsec
µsec
THERMAL
BU-65570M
Operating Temperature (See Note 4)
Storage Temperature
0
-20
+55
+65
°C
°C
PHYSICAL CHARACTERISTICS
Size
Weight
3.370 X 2.126 X 0.197
(85.6 X 54.0 X 5.0)
2.8
(80)
in
(mm)
oz
(g)
Notes for TABLE 2:
1. This time assumes that this card is not emulating BC.
2. This hardware time is enforced by the firmware. If an attempt to reduce
this time is made, the time will be stretched to 25 µsec.
3. This time is programmable from 2 µsec to 29 µsec in 1 µsec increments.
4. Air temperature in the card’s immediate vicinity.
GENERAL
The BU-65570M allows a PC to concurrently simulate a MIL-
STD-1553 BC, and multiple (up to 31) RT’s, and provide an intel-
ligent MT. The BU-65570M requires transformer coupling to the
bus.
The BU-65570M supports “Plug and Play” installation, using a
dynamically mapped base address and interrupt vector supplied
by the operating system, for easy installation and setup.
Full error detection features are provided in all modes of opera-
tion. In addition, user specified errors – including bit count,
Manchester II errors – may be injected in both BC and any of the
emulated RT modes.
Operation of the BU-65570M is controlled through the use of
Windows 9x, Windows NT, or Windows 2000/XP based user-
friendly menus. The Windows menu provides a flexible multitask-
ing, multi-document interface. The menu provides an interactive
software interface which allows for full control of the features and
functionality of the BU-65570M.
BUS CONTROLLER MODE
The BU-65570M Bus Controller supports all MIL-STD-1553B
message formats. Up to 1000 unique receive, transmit, mode
code, and RT to RT messages may be defined at one time.
Programmable attributes within a message are time to next mes-
sage, bus (channel A or channel B), intermessage routines, and
injected error. The time to next message defines the time from
the start of the present message to the start of the next mes-
sage. The time to next message is programmable up to 65,535
µsec in 1 µsec increments.
MINOR AND MAJOR FRAMES
The execution of messages is controlled by a message list
referred to as a frame. The frame specifies the contents and tim-
ing of complete communication runs by the BC. Each entry in the
frame is either a reference to a message or a special symbol.
The entire frame is referred to as a major frame. The major frame
is divided into minor frames of equal time duration.
The major frame time is based on a programmable 32-bit counter
with 1 µsec resolution. The BU-65570M supports major frames
of up to 1000 messages for single buffered mode or up to 100
messages for double buffered mode, and the period is up to 143
minutes.
BC ERROR INJECTION
Error conditions may be injected on a message-by-message
basis. The BU-65570M supports three categories of injected BC
errors: length errors, encoding errors, and gap errors. Length
errors include both word count errors and bit count errors. Word
counts of -32 to +1 words may be programmed. Bit counts of +3,
+2, +1, -3, -2, or -1 bit may be programmed on any word within
the message.
4
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
Encoding errors are implemented through the use of two simple
yet powerful mechanisms for modifying the output of the BU-
65570M's Manchester encoder. The two modifying functions are
glitch and inverse. A glitch will force the output of the encoder to
an idle bus condition for the specified period of time. An inverse
will invert the output of the encoder for the specified period of
time. The placement of the error is specified by the word number,
starting time, and width. The error may be placed in any word
within the message. The starting time is programmed in 500 ns
increments from the beginning of the specified word. The width
of the error is specified in 50 ns increments up to 3 µsec. This
error injection scheme lends itself to generating a host of errors
including invalid sync patterns, parity errors, and Manchester bi-
phase errors.
A gap of 3, 4, or 5 µsec (measured mid-parity crossing to mid-
sync crossing) may be inserted between any two words in a
message. This allows for a “dead time” gap between words of 1,
2, or 3 µsec.
INSERTING ASYNCHRONOUS MESSAGES
The BU-65570M allows an asynchronous message to be insert-
ed while the card is running. This inserted message will be exe-
cuted upon completion of the current message.
BC INTERMESSAGE ROUTINES
Upon completion of a BC message, the BU-65570M's on-board
processor executes 2 intermessage routines. Intermessage rou-
tines are used to implement automatic retries on failed mes-
sages as well as other “end of message” functions. TABLE 3 pro-
vides a summary of the BU-65570M's intermessage routines.
RESPONSE TIMEOUT
The BU-65570M BC, RT’s and MT support programmable
response timeout values ranging from 2 to 29 µsec in 1 µsec
increments.
RT MODE
The BU-65570M can concurrently simulate the operation of 31
unique remote terminals (RT’s) plus a broadcast address. The
BU-65570M maintains 31 independent “last status” and “last
command” words allowing for full support of transmit last com-
mand and transmit status mode commands. The BU-65570M
supports full RT command illegalization for each transmit or
receive message based on RT address AND subaddress. In
addition, individual mode commands may be illegalized.
RT ERROR INJECTION
Error conditions may be injected on an individual RT basis. The
BU-65570M supports five categories of injected RT errors:
length errors, encoding errors, gap errors, status address errors,
and response errors. Length errors include both word count
errors and bit count errors. Word counts of -32 to +1 words may
be programmed. Bit counts of +3, +2, +1, -3, -2, or -1 bit may be
programmed on any word within the message.
Encoding errors are implemented through the use of two simple
yet powerful mechanisms for modifying the output of the BU-
65570M's Manchester encoder. The two modifying functions are
glitch and inverse. A glitch will force the output of the encoder to
an idle bus condition for the specified period of time. An inverse
will invert the output of the encoder for the specified period of
time. The placement of the error is specified by the word number,
starting time, and width. The error may be placed in any word
within the message. The starting time is programmed in 500 ns
increments from the beginning of the specified word. The width
of the error is specified in 50 ns increments up to 3 µsec. This
error injection scheme lends itself to generating a host of errors
including invalid sync patterns, parity errors, and Manchester bi-
phase errors.
A gap of 3, 4, or 5 µsec (measured mid parity crossing to mid-
sync crossing) may be inserted between any two words in a
message. This allows for a “dead time” gap between words of 1,
2, or 3 µsec. A status address error may be injected in which the
RT responds with a status word containing an RT address which
does not match the terminal's RT address. The RT may be pro-
grammed to respond with any value from zero to 31 in its status
response.
TABLE 3. BC/RT INTERMESSAGE ROUTINES
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)
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
BLOCK_DATA_RT
5
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
The BU-65570M supports three types of response errors: no
response, a late response, or a response on the wrong bus. No
response errors may be programmed for a single channel (Bus
A or Bus B) or for both buses. Injecting a no response error on
one bus provides a simple mechanism for testing bus controller
retry conditions. A late response may be programmed in the
range of 12 to 30 µsec in 1 µsec increments.
RT INTERMESSAGE ROUTINES
The RT section of the BU-65570M also supports intermessage
routines. Upon completion of an RT message the BU-65570M's
on-board processor executes two intermessage routines. The
intermessage routine is specified by the data table that was used
by the RT for a given message. Refer to TABLE 3 for a summa-
ry of the BU-65570M's intermessage routines.
BC/RT DATA TABLES
The BU-65570M maintains 1000 data tables within the shared
RAM on the card. Each data table may be up to 32 words in
length. These data tables are common to both BC and RT.
Internal lookup tables map each RT address, T/R, subaddress
combination (RT mode) and message number (BC mode) to a
given data table. Data tables may be read or written to in real
time. Data tables may be either single or double buffered. Double
buffering can be used to avoid contention when the PC's appli-
cation and the 1553 bus access data tables simultaneously.
The BU-65570M provides an optional block data mode in which
the data table number associated with a given BC or RT mes-
sage is incremented after completion of the message. The block
data mode is implemented as a circular data structure. Each BC
message and RT command (RT address, T/R, and subaddress)
has three data table numbers associated with it: first, last, and
current. The current data table number will be incremented after
completion of message until the value of last is reached, at which
point the current table number will rollover to the value of first.
The incrementing of the current data table is accomplished
through the use of an intermessage routine.
MONITOR MODE
The BU-65570M contains an independent message monitor with
the ability to filter messages in real time. Monitor selection or fil-
tering is performed through the use of a lookup table based on
the RT address, T/R, and subaddress of command words.
Monitored messages are stored in the shared RAM on the BU-
65570M. Each entry in the monitor buffer contains a header fol-
lowed by a variable number of data words. Contained with the
message header are the receive/transmit command(s),
receive/transmit status(es), message format, Bus (A or B), a cap-
ture flag, word count (actual number of words in the message),
a detected error field, and a 32-bit time tag (1 µsec resolution).
The transfer of the messages from the card’s circular buffer to
the host memory/disk is determined by the capture flag which is
set upon detection of a predefined event. Capture events include
immediate, command template match, exception, or trigger. The
command template event is based on a 16-bit command word
with a 16-bit mask. Exception events may be programmed for
any exception: invalid command, invalid data, invalid status, gap
preceding data, response time error, wrong RT address error,
status set condition or an illegal command. The trigger event
uses one of the eight monitor input pins on the 9-pin D-type con-
nector as a trigger input.
INTERRUPTS
Interrupts to the PC are requested by both the BC/RT and the
Monitor on a common output. The hardware interrupt level used
by the BU-65570M is software programmable via an I/O mapped
register on the card. The interrupt level may be programmed to
any available interrupt value.
BC INTERRUPT GENERATION
BC interrupts may be enabled by a global interrupt mask for suc-
cessful messages, communication errors, status set conditions,
or on selected frame symbols (skip, break point, major frame,
and minor frame symbols). The criteria for a status set condition
is programmed globally through the use of a status mask. The
status mask allows any of the 16 bits within an RT status word to
be ignored. The status mask affects the generation of interrupts
as well as the detected error field which is stored in the message
structure.
BC interrupts are issued by intermessage routines associated
with messages allowing for selective interrupt generation on a
message by message basis. Each interrupt request is accompa-
nied by a two word vector pushed onto a circular queue which is
transparent to the user. The queue can hold up to 64 interrupt
vectors; thus, the host computer is not required to immediately
acknowledge the interrupt request.
RT INTERRUPT GENERATION
RT interrupts may be enabled by a global interrupt mask for
transmit/receive messages with no message error, mode com-
mands with no message error, transmit/receive messages with
the message error bit set, or mode commands with the message
error bit set.
RT interrupts are issued by intermessage routines associated
with data tables allowing for selective interrupt generation on a
message by message basis. Each interrupt request is accompa-
nied by a two word vector pushed onto a circular queue which is
transparent to the user. The queue can hold up to 64 interrupt
vectors; thus, the host computer is not required to immediately
acknowledge the interrupt request.
MONITOR INTERRUPTS
Monitor interrupts may be generated after each message is
received or after one third of the monitor's circular buffer has
been filled (approximately 4K words). This allows for either real-
time analysis or mass collection/storage of monitored data.
6
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
The following code is a modified version of the DDCSAMPLE.C sample program that is supplied with the BU-65570M hardware, and
represents the simplicity of writing code for the BU-65570M PCMCIA card.
#include "TS_drv.h"
#include <time.h>
MESSAGE Message;
Device_p pCrd;
CMD Cmd1, Cmd2;
INJ_ERR InjErr;
U16BIT i, Frame[10], data[32];
RT_DEFS rt;
DRV_CONFIG cfg;
S32BIT Err;
time_t time_start;
int main ()
{
printf("Resetting card...\n");
if(Err = ddcResetCard(&pCrd,&cfg,0)){
ddcPrintErrorMessage(pCrd,Err, "reset_card");
exit(1);
}
printf("Card reset successful!\n");
/* Define Message 1 */
Cmd1.wcnt = 5;
Cmd1.subadr = 1;
Cmd1.t_r = 0; // should be 0 for a RECEIVE command
Cmd1.tadr = 1;
Cmd2.wcnt = 31;
Cmd2.subadr = 1;
Cmd2.t_r = 1;
Cmd2.tadr = 1;
InjErr.error = E_NONE;
InjErr.sub_error_1 = 0;
InjErr.sub_error_2 = 0;
InjErr.sub_error_3 = 0;
Message.bus = BUS_A;
Message.comm_type = RECEIVE;
Message.cmd_1 = Cmd1;
Message.cmd_2 = Cmd2;
Message.time_to_next_message = 1000;
TESTER/SIMULATOR SOFTWARE
The BU-65570M is supplied with software Runtime Libraries for
DOS, Windows 9x, Windows NT, and Windows 2000 and Menu
programs for Windows 9x, Windows NT, and Windows 2000.This
software is provided with the card at no extra cost.
TESTER/SIMULATOR RUNTIME LIBRARIES
The Runtime Libraries (RTL) come in both 16-bit and 32-bit ver-
sions to support DOS and Windows. For a detailed description of
the Tester/Simulator RTL, please refer to the Tester/Simulator
Runtime Library Programmers Manual (Document # MN-
69068XX-001). Using the Runtime Library, applications may be
created that are capable of controlling the BU-65570M card as
BC, RT and MT modes simultaneously. The Runtime Library sup-
ports “C” programming, LabVIEW and Visual Basic interfaces.
Existing programs written for the previous versions of the DDC
Tester/Simulator cards may be recompiled with the new RTL and
used with the BU-65570M. Included with the Tester/Simulator
Runtime Library are sample programs that can be used as a
starting point for a custom application. Please visit the DDC Web
site for updates to the RTL and program examples.
7
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
Message.data_table_no = 1;
Message.first_intermessage_routine = NO_OPERATION;
Message.second_intermessage_routine = NO_OPERATION;
Message.inj_error_ptr = &InjErr;
if(Err = ddcDef_message (pCrd, 1, &Message )){
ddcPrintErrorMessage(pCrd,Err, "def_message");
exit(1);
}
/* Define Message 2. Only changed values are listed */
Cmd1.wcnt = 1;
Cmd1.t_r = 1; // should be 0 for a RECEIVE command
Cmd1.tadr = 2;
Message.comm_type = TRANSMIT;
Message.cmd_1 = Cmd1;
Message.data_table_no = 2;
if(Err = ddcDef_message (pCrd, 2, &Message )){
ddcPrintErrorMessage(pCrd,Err, "def_message");
exit(1);
}
/* Set up BC Frame using messages defined above */
Frame[0] = 1;
Frame[1] = 2;
Frame[2] = END_OF_MINOR;
Frame[3] = 1;
Frame[4] = 2;
Frame[5] = END_OF_MAJOR;
if(Err = ddcDef_frame (pCrd, 6, Frame )){
ddcPrintErrorMessage(pCrd,Err, "def_frame");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
if(Err = ddcDef_minor_frame_time (pCrd, 1000 )){
ddcPrintErrorMessage(pCrd,Err, "def_minor_frame_time");
exit(1);
}
/* Set up RT1 */
InjErr.error = E_NONE;
InjErr.sub_error_1 = 0;
InjErr.sub_error_2 = 0;
InjErr.sub_error_3 = 0;
rt.inj_error = &InjErr;
rt.basic_status = 0x0000;
if(Err = ddcDef_emulate_rt(pCrd,1, YES)){
ddcPrintErrorMessage(pCrd,Err, "def_emulate_rt");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
if(Err = ddcDef_rt(pCrd,1, &rt)){
ddcPrintErrorMessage(pCrd,Err, "def_rt");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
8
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
if(Err = ddcDef_rt_map(pCrd,1, 0, 1, 3)){
ddcPrintErrorMessage(pCrd,Err, "def_rt_map");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
/* Set up RT2 */
if(Err = ddcDef_emulate_rt(pCrd, 2, YES)){
ddcPrintErrorMessage(pCrd,Err, "def_emulate_rt");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
if(Err = ddcDef_rt(pCrd, 2, &rt)){
ddcPrintErrorMessage(pCrd,Err, "def_rt");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
if(Err = ddcDef_rt_map(pCrd, 2, 1, 1, 4)){
ddcPrintErrorMessage(pCrd,Err, "def_rt_map");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
/* Set up Data Tables */
for(i=1; i<5; i++){
if(Err = ddcDef_table_size (pCrd, i, 32)){
ddcPrintErrorMessage(pCrd,Err, "def_table_size");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
}
for(i=0; i<32; i++) data[i] = 0x1111;
ddcWrite_data(pCrd,1, data, 32, 1);
for(i=0; i<32; i++) data[i] = 0x2222;
ddcWrite_data(pCrd,2, data, 32, 1);
for(i=0; i<32; i++) data[i] = 0x3333;
ddcWrite_data(pCrd,3, data, 32, 1);
for(i=0; i<32; i++) data[i] = 0x4444;
ddcWrite_data(pCrd,4, data, 32, 1);
/* Run BC Frame twice */
if(Err = ddcRun_bc(pCrd,1, 1)){
ddcPrintErrorMessage(pCrd,Err, "run_bc");
Err = ddcShutDownIdea(&pCrd);
exit(1);
}
/* delay until BC finishes */
while((clock() - time_start)/CLK_TCK < 2.5);
if(Err = ddcShutDownIdea(&pCrd)){
ddcPrintErrorMessage(pCrd,Err, "shut_down_idea");
exit(1);
}
printf("Card shut down successful, terminating program.\n");
return 0;
}
9
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
TESTER/SIMULATOR MENU INTRODUCTION
The Tester/Simulator Menu provides an interface for DDC PCM-
CIA Tester/Simulator cards. For detailed information about the
Tester/Simulator Menu, please refer to the Tester/Simulator
Menu User's Guide (Document # MN-69065S0-001).
Each of the MIL-STD-1553 operating modes, Bus Controller
(BC), Remote Terminals (RT), and Monitor Terminal (MT) are
setup independently with all parameters being saved to a
Tester/Simulator setup file (*.stp). The card is capable of running
in any combination of modes simultaneously. A green indicator
on the run page will indicate which modes are running. Replay is
an additional mode that has been added to the Menu. In this
mode, it is possible to replay a previously captured stack file.
Subsequent to configuring the operational parameters and mes-
saging of the BU-65570M via the Menu software, the source
code generation wizard can be invoked.
The source code generation wizard allows the user to selective-
ly enable BC/RT/MT activity, with interrupt processing callback
routines, and a “.C” output file will be created. The generated C
file is based on the API set of the Runtime Library (RTL).
The Tester/Simulator Menu provides all the functions necessary
to control the BU-65570M operating modes. The BC mode is pre-
pared for operation by creating messages and assembling the
messages into a frame. The parameters for each message,
including the command word, data words, and Bus selection can
be modified from the Tester/Simulator Menu. Setup screens are
available for setting operational parameters such as Response
Timeout, Retries and Stop-On criteria. A BC frame is created by
adding the defined messages to a frame structure. The
Tester/Simulator Menu allows a frame to be a composition of
many minor frames, where each minor frame will represent the
same amount of time. The minor frame time usage is displayed
in an indicator bar at the bottom of the BC setup page. This indi-
FIGURE 3. REMOTE TERMINAL SETUP DOCUMENTFIGURE 2. BC SETUP DOCUMENT
cator gives a quick display of the time used by the messages in
the minor frame. If the time usage is greater than 75% then the
indicator bar will change to yellow. If the time usage is 100% or
more, then the indicator will change to red. The minor frame time
usage can be reduced by removing messages from the minor
frame or by changing the minor frame time.The minor frame time
is operator programmable. The number of minor frames, times
the minor frame time represents the total time needed for the
Major Frame. Once the frame setup is complete, the BC setup
screen can also be used to control the processing of the BC
Frame. The controls for setting the minor frame time, the number
of frames to send, and the RT response timeout may be config-
ured from this setup screen.
The Remote Terminal mode setup document allows setting the
hardware to respond to any combination of legal RT addresses.
The setup for each RT specifies the data table(s), data, error
injection, status response, and message legality for each emu-
lated RT. The data edit screen provides controls to select the
sub-address and enter the data. Once all of the sub-address
responses have been determined for each RT, the ‘RT Run’ but-
ton may be clicked to activate the RT processing.
Monitor operation is also provided. The BU-65570M
Tester/Simulator Menu monitor is a message monitor that will
monitor the 1553 bus traffic, decode the messages (command
and data) and save the information to a Stack File. The monitor
is capable of filtering the message information based on Remote
Terminal address, Sub-address, and Transmit/Receive for each
message. When all of the appropriate filtering has been estab-
lished, the Response Timeout option may be set. The timeout
option instructs the Monitor as to how long it must wait before
declaring a no response message. The Run Monitor screen has
controls that allow setting the Stack File requirements, and the
Monitor Trigger parameters. The Monitor trigger function allows
the operator to select from trigger immediate, trigger on external
input via the mini-D connector, or trigger on command word.
10
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
FIGURE 5. STACK VIEW
Communication information is saved in stack files (*.stk). The
stack file parameters for stack file size and name are modified on
the Monitor setup screen (as shown in FIGURE 4). The monitor
does not have to be explicitly run to capture a stack file. BC and
RT modes also provide stack file generation. After running the
card, the generated stack file can be viewed by opening the
stack viewer. From the Run screen, the Stack View button allows
quick access to the stack file open dialog. Once opened, the
stack file can be searched for any type of message or error.
The Replay button presents the functions and controls to setup
the BU-65570M to replay MIL-STD-1553 bus traffic recorded as
a *.stk file. This stack file may be either a file generated by the
BU-65570M, or a converted stack file from the previous versions
of the DDC Tester/Simulator boards. The setup for Replay
includes selecting which remote terminals will be emulated by
the Tester/Simulator and which ones will be represented as actu-
al remote terminals on the bus. The BU-65570M will replay only
those responses, as read from the stack file, that it is emulating.
All responses for remote terminals that are not being emulated
will be provided by actual hardware on the bus.
The BU-65570M has the capability of operating as a message
monitor at the same time that it is reconstructing the bus traffic.
When Replay and Monitor are running simultaneously, the
Replay function will read previously recorded data from a stack
file on disk, and recreate it on the bus. At the same time the
Monitor will be reading the data from the bus and saving it to a
new stack file on disk. This provides a powerful system-debug-
ging tool that will allow viewing of data on the bus as it was orig-
inally recorded from an actual system, and the data that was
recorded when the bus traffic was replayed in the lab.
FIGURE 4. MONITOR SETUP DOCUMENT
FIGURE 6. REPLAY SETUP DOCUMENT
The stack file contains information pertaining to the date, time
and number of messages. It also contains the data portion of the
messages, all pertinent status information, and text describing
the error type.
The stack file can be searched by message command word, any
data word, or any MIL-STD-1553 error. Each of the search crite-
ria may be combined with a mask to allow searching for a family
of command or data words. The search direction is selectable
between up and down.
11
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
INTERFACE TO A MIL-STD-1553 BUS
The BU-65570M permits only transformer coupling to a MIL-
STD-1553 bus. FIGURE 7 illustrates the interface from the BU-
65570M Card to a MIL-STD-1553 bus. Transformer coupling is
implemented using triax connectors. In accordance with MIL-
BU-65570M
DATA
BUS
Z0
1:1.4
0.75 Z0
BUS COUPLER
BUS A
BUS B
TRANSFORMER COUPLED
STUB
Z0
0.75 Z0
(Transformer coupling)
Triax Connector
1:1.79
1:1.79
FIGURE 7. BU-65570M INTERFACE TO A MIL-STD-1553 BUS
STD-1553, a transformer coupled connection to a 1553 bus
requires the use of a bus coupler. In addition, the 1553 bus must
be properly terminated. A bus coupler contains an impedance
matching transformer as well as a pair of fault isolation resistors.
12
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
1.969
(50.3)
P1
1.193
(30.3)
18.00 ± 1.0
A
B
P2
P3
P4
1
2
3
4
5
6
7
8
9
A1 A15 P1 P2 B1 B15
FIGURE 8. BU-65570M MECHANICAL OUTLINE, SHOWN WITH TRANSFORMER
COUPLED CABLE ASSEMBLY
0.197 MAX
(5.00 MAX)
PIN 34 PIN 1
PIN 35
P1
PIN 68
B
NOTE: Dimensions in inches(mm) unless otherwise noted.
3.370 ±0.008
(85.59 ±0.20)
2.126 ±0.004
(54.00 ±0.10)
B
A
2.126 ±0.004
(54.00 ±0.10)
A
13
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
TABLE 4. BU-65570M1 PINOUT
FROM TO
TX/RX A B13, B14 Center
SIGNAL NAME P1 P2 P3 P4
TX/RX A B11, B12 Outer
SHIELD Shield Housing
TX/RX B B7, B8 Center
TX/RX BB5, B6 Outer
SHIELD Shield Housing
MON TRIG IN A15 7
MON TRIG OUT A14 8
BC TRIG IN A13 9
BC TRIG OUT A12 2
GND A10 1
RESERVED A B3 3
RESERVED B B2 4
RESERVED C B1 5
RESERVED D A11 6
14
Data Device Corporation
www.ddc-web.com
BU-65570M
D-09/05-0
ORDERING INFORMATION
BU-65570M1 - X00
Test Criteria:
0 = Standard Testing
Process Requirements:
0 = Standard DDC Processing
Temperature Range:
3 = 0°C to +55°C (BU-65570M1-300)
Number of 1553 Channels:
1 = 1 Dual Redundant Channel
Card Type:
M = PCMCIA
Base Model Number:
BU-65570 = MIL-STD-1553B Simulator and Tester Card
Note: The above products contain tin-lead solder.
—DDC ATPELECTRICAL TEST
Class 3IPC-A-610INSPECTION / WORKMANSHIP
CONDITION(S)METHOD(S)TEST
STANDARD DDC PROCESSING
FOR DISCRETE MODULES/PC BOARD ASSEMBLIES
INCLUDED SOFTWARE
BU-69065S0
Windows 9x/NT/2000 32-bit Tester/Simulator Menu
BU-69067S0
DOS/Win 3.x 16-bit Tester/Simulator Runtime Library
BU-69068S0
Windows 9x/NT/2000 32-bit Tester/Simulator Runtime Library
OPTIONAL SOFTWARE
BU-69404DM-64VM
32-bit
dataMARS
, Data Monitoring, Analysis, and Replay; with Virtual Panels and Multiplex
BU-69404DS-64VM
32-bit
dataSIMS
, Data Simulation, Analysis, and Replay; with Virtual Panels and Multiplex
15
D-09/05-0 PRINTED IN THE U.S.A.
DATA DEVICE CORPORATION
REGISTERED TO ISO 9001:2000
FILE NO. A5976
R
E
G
I
S
T
E
R
E
D
F
I
R
M
®
U
The information in this data sheet 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.
105 Wilbur Place, Bohemia, New York, U.S.A. 11716-2482
For Technical Support - 1-800-DDC-5757 ext. 7771
Headquarters, N.Y., U.S.A. - Tel: (631) 567-5600, Fax: (631) 567-7358
Southeast, U.S.A. - Tel: (703) 450-7900, Fax: (703) 450-6610
West Coast, U.S.A. - Tel: (714) 895-9777, Fax: (714) 895-4988
United Kingdom - Tel: +44-(0)1635-811140, Fax: +44-(0)1635-32264
Ireland - Tel: +353-21-341065, Fax: +353-21-341568
France - Tel: +33-(0)1-41-16-3424, Fax: +33-(0)1-41-16-3425
Germany - Tel: +49-(0)89-15 00 11-12, Fax: +49-(0)89-15 00 11-22
Japan - Tel: +81-(0)3-3814-7688, Fax: +81-(0)3-3814-7689
World Wide Web - http://www.ddc-web.com
