EasyManua.ls Logo

4Links Diagnostic SpaceWire Interface - Spwio Event Waveform Defaults; Spwio Event Waveform Examples

Default Icon
47 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Page 30
therSpaceLink_EW_enable_reporting() C-language API function. See the respective SpWIO or C-
language Application Programming Interface manual for details.
Each SpaceWire port generates an event when one or more of the following have been enabled and subsequently
occur:
11.1.1 SpWIO Event Waveform Defaults
The default for SpWIO is to cause events when SpaceWire errors are seen (i.e. incorrect token sequences, parity
errors or flow-control errors), and to generate event waveform triggers just for the SpaceWire port on which an
error was seen. No SMA pulses are generated on J5-J6 by default.
11.1.2 SpWIO Event Waveform Examples
In addition to the default Error Waveform triggering, it is possible to supply the /es and /ew command-line
parameters to SpWIO, which apply to all ports, or the inline versions of these commands can be supplied after
selecting a particular port to affect just that port. Remember that the flags for /es and /ew are supplied
directly, over-writing the previous setting, or as delta-adjustments (using + and -).
The command-line parameters have the following effects:
/ew t
Create event triggers when SpaceWire time-codes are seen on SpaceWire ports 1 - 8, and
delete any previous events.
/ew +t
Create additional event triggers when SpaceWire time-codes are seen on SpaceWire ports 1 - 8,
leaving any previous event triggers unchanged.
/ew -t
Remove event triggers when SpaceWire time-codes are seen on SpaceWire ports 1 - 8, if they
were enabled previously.
/es 14
Trigger waveforms on all eight SpaceWire ports when an event is seen on port 1 or port 4.
SpWIO /ew flag
DSI option
Description
none
An event flag is embedded in the transmit data stream - i.e. the user can
trigger an event at some specified point in a transmitted data stream.
s
The first byte of a packet is received.
m
Intermediate bytes of received packets arrive.
e
The end-of-packet marker, EOP, is received.
g
The error-end-of-packet marker, EEP, is received.
t
Time codes are received.
a
ER
The ECSS error ESC-ESC is observed.
b
ER
The ECSS error ESC-EOP is observed.
c
ER
The ECSS error ESC-EEP is observed.
f
ER
Flow-control tokens are received.
p
ER
The ECSS Parity error is observed.
v
ER
More data is received than flow-control credit permits.
w
ER
Too many flow-control tokens are received.
x
ER
The ECSS Timeout (disconnect) error is observed.

Table of Contents