1’J/’5I’ · 1.3 Purpose and Objectives of Document 1 1.4 Document Status and Schedule 1 1.5...

1’J/’5I’National Aeronauticsand 11/12/92

SQaceAdministration

GeorgeC. Marshall SpaceRight CenterMarshall SpaceFlight Center.Alabama35812

LIGHTNING IMAGING SENSOR

SOFTWARE REQUIRENENTS SPECIFICATION

MSFC.Form4S4(Rev. October1976)

MSFC—SPEC-2026

11/12/92

LIGHTNING IMAGING SENSORSOFTWARE REQUIREMENTS SPECIFICATION

PreparedBy: Approved By:

C

_______

Louis C. Simeone Js’ph L. RandallSystem Software Branch D’1rector, Information and

Electronic SystemsLab.

Ap ved Approved By:

______

Z3

Hugh Christian PrestonLiHasslerRemote SensingBranch ScienceP yload

Project Engineering

Approved By:

Dinah B. HigginsEarth ScienceandApplications Office

1

NOTEMwreviswt ment.file shee doamierecei&x Tableof Connts

ii

ReleaseDate Marshall Space Flight Canter Page 1 ofSPECIFICATION/DOCUMENT

CHANGE INSTRUCTiONSCopy No.:

Spec.JDoc. No. MSFC-SPEC-2026

Change SCN/DCN CCBD ReplacementPageNcJ Date No.JDate No./Date— Instructions

CHG 1 SCN 001

A3—02—00011—12—92

MA3—02-O0114—22—93

BaselineRelease

Replacepages 4, 5, 11, 12, 27, and 28 with newpages 4, 5, 11, 12, 27, and 28

FC-.vrm 4140(RevSecemLer1990)

MSFC-SPEC—202611/12/92

TABLE OF CONTENTSPage

1.0 INTRODUCTION 1

1.1 Identification of Document 1

1.2 Scope of Document 1

1.3 Purposeand Objectives of Document 1

1.4 Document Status and Schedule 1

1.5 DocumentationOrganization 1

2.0 RELATED DOCUMENTATION 2

2.1 Applicable Documents 2

2.2 Informational Material 3

3.0 FLIGHT SOFTWARE REQUIREMENTS 4

3.1 Hardware and Exception GeneratedRoutines 4

3.1.1 Initialization Software 4

3.1.2 Filter TemperatureMonitoring 4

3.2 Hardware Configuration 4

3.2.1 Primary Configuration 43.2.1.1 Operation Environment 43.2.1.2 Interfaces 5

3.2.1.2.1Command And ControlInterfaces 5

3.2.1.2.2 Time Mark Interface3.2.2 Watchdog Timer 5

3.3 Commands 5

3.3.1 Instrument Command List 6

3.3.2 Command Constraints 6

3.3.3 Timing Constraints 6

3.4 OperationalModes 6

3.4.1 System Test Mode 6

3.4.2 Background Send On Mode 6

3.4.3 BackgroundSend Of f Mode 7

3.5 Interrupts 7

3.5.1 Real Time Event ProcessorInterrupt 7

3.5.2 Command and Control Interrupt 73.5.3 Time Mark Interrupt 7

3.6 Data Formats 8

3.6.1 LIS Data Formats 83.6.1.1 ScienceData 83.6.1.2 HousekeepingData 83.6.1.3 Packet Structure 83.6.1.4 Packet Formation Format 9

3.6.2 Time Data Format 9

iii

TABLE OF CONTENTS

MSFC-SPEC-202611/12/92

Page

9

9

10

101010

101010111111111112

121212

14141414

4.5 Interrupts 14

3.7 Displays 9

3.8 EngineeringDevelopmentand AnalysisSoftware

3.9 Implementation

4.0 ELECTRICAL GROUND SUPPORT EQUIPMENTSOFTWARE REQUIREMENTS

4.1 Hardware and Exception GeneratedRoutines

4.1.1 Initialization Software4.1.2 Filter TemperatureMonitor

4.2 Hardware Configuration4.2.1 MSFC TRI Simulator Configuration

4.2.1.1 MIL—STD—1773 Interface4.2.1.2 Time Mark Interface4.2.1.3 PassiveAnalog Iritefface4.2.1.4 Power Distribution Interface

4.2.2 GSFC TR Simulator Configuration

4.2.3 Calibration Configuration4.2.4 Post-IntegrationConfiguration

4.3 Commands4.3.1 LIS Instrument Command Simulation

4.3.1.1 Command List4.3.1.2 Command Constraints4.3.1.3 Timing Constraints

4.3.2 Platform Simulation Commands4.3.2.1 Command List4.3.2.2 Command Constraints4.3.2.3 Timing Constraints

4.3.3 EGSE Commands4.3.3.1 Command List4.3.3.2 Command Constraints4.3.3.3 Timing Constraints

4.4 OperationalModes4.4.1 Self—Test Mode4.4.2 TRI4 Software Simulation4.4.3 Analysis Mode

12121313131313131313

Mode

iv

MSFC-SPEC—202611/12/92


4.6 Data Formats 15

4.6.1 LIS Data Formats 15

4.6.2 EGSE Internal Data Formats 15

4.6.3 Calibration Facility Data Formats 15

4.6.4 SGSE/GSFCSimulator Data Formats 15

4.7 Displays 15

4.7.1 EGSE Command Status 16

4.7.2 EngineeringData Display 16

4.7.3 Lightning Image Display 16

4.8 EngineeringDevelopmentand AnalysisSoftware 16

4.8.1 Focal Plane Simulator Software 16

4.8.2 1773 Test Routines 16

4.8.3 EGSE Diagnostic Mode 16

4.9 Implemention 17

4.9.1 Developed Software 17

4.9.2 Commercial Software 17

4.9.3 ReusableSoftware 17

5.0 CALIBRATION FACILITY SOFTWARE REQUIREMENTS 18

5.1 Hardware and Exception GeneratedRoutines 18

5.1.1 Initialization Software 18

5.1.2 Exception Monitoring 18

5.2 Hardware Configuration 18

5.2.1 Optical Stimulation EquipmentInterface 18

5.2.2 TFI24 Simulation EquipmentInterface 19

5.2.3 Raw LIS Pixel Data 19

5.2.4 High SpeedPhotometer 19

5.3 Coxrmtands 19

5.4 OperationalModes 19

5.5 Interrups 19

5.6 Data Analysis 19

5.6.1 Detailed Analysis 19

5.7 Displays 19

5.8 EngineeringDevelopmentand AnalysisSoftware 20

5.9 Implementation 20

5.9.1 Commercial Software 205.9.1.1 Assemblers/Compilers 205.9.1.2 Commercial Hardware Drivers 20

5.9.2 ReusableSoftware 20

5.9.3 Functional Partition 20

V

MSFC—SPEC—202611/12/92


6.0 ABBREVIATIONS AND ACRONYMS 21

7.0 VERIFICATION MATRIX 23

8.0 DATA FLOWS 26

Appendix A LIS Instrument Commands 37

Appendix B Simulated FDS TR!vI Interface Commands 39

Appendix C EGSE Commands 40

Appendix D Calibration Facility/EGSE Data ExchangeFormats 41

Appendix E LIS InstrumentDevelopmentalTestRoutines 42

Appendix F 1773 Mode Control Commands 43

vi

MSFC-SPEC—2026

11/12/92

LIST OF FIGURES

Figure Page

8-1 LIS Hardware Configuration 27

8-2 CoarseTime Update 28

8-3 Time Mark Reception 29

8—4 SciencePacket Formation 30

8—5 HousekeepingPacketFormation 31

8-6 Time Data Formation 32

8—7 Discrete Telemetry Acquistion 33

8—8 MSFC Interface Simulator 34

8—9 GSFC Interface Simulator 35

8—10 Post—IntegrationConfiguatiori 36

vii

MSFC-SPEC-202611/12/92

1.0 INTRODUCTION

1.1 Identification of Document

This is the Software RequirementsSpecification

for the Lightning Imaging Sensor (LIS) Experiment.

1.2 Scope of Document

This specificationestablishesrequirements

for the LIS software. This document applies to the Flight

Software, Electrical Ground Support Equipment (EGSE) Software

and Calibration Software to be developedby Marshall Space

Flight Center (MSFC) for the LIS Experiment.

Flight software will be developedand testedas

specified in the LIS Software Management,Developmentand

Test Plan (Reference1) for the Tropical Rainfall Measuring

Mission (TPMM).

1.3 Purposeand Objectives of Document

The use of this specificationwill help promote

efficient design and verification of the LIS software.

1.4 Document Statusand Schedule

This documentwill be baselinedat the Software

RequirementsReview (SRR), as specified in the LIS Software

Management,Developmentand Test Plan (Reference1), and will

be used throughout the software life—cycle of the LIS

experiment.

1.5 DocumentationOrganization

This documentcontains five sections. Section 1.0

is the introduction, section 2.0 contains related

documentation,section 3.0 contains Flight Softwarerequirements,section 4.0 containsElectrical Ground Support

Equipment Software requirementsand section 5.0 contains

Calibration Facility Software requirements.

1

MSFC-SPEC-202611/12/92

2.0 RELATED DOCUMENTATION

2.1 Applicable Documents

The latest version of the documents listedwill be used as referencedwhere applicable:

Reference1 - Lightning Imaging SensorSoftwareManagement,Developmentand TestPlan, MSFC-PLAN—2025

Reference2 Tropical Rainfall MeasuringMissionSpacecraftto Lightning ImagingSensor Instrument Interface ControlDocument, TRMM-490-022

Reference3 Military StandardFiber OpticsMechanizationof an AircraftInternal Time Division CommandResponseMultiplex Data BusSpecification, MIL—STD-1773

Reference4 - TMS32O AssemblerGuide forthe TI TMS320C25

Reference5 - Tropical Rainfall MeasuringMissionSGSE/IGSE Interface ControlDocument, TRMM-490-TBD

2

MSFC-SPEC—2026

11/12/92

2.2 Informational Material

The latest version of the documentslisted

will be used for information where applicable:

Info 1 — Tropical Rainfall MeasuringMissionCommand and Data Handling SubsystemHardware Interface Control Document,TRMM-490-TBD

Info 2 — Tropical Rainfall MeasuringMissionElectrical System Specification,TRMM-4 9 O—TBD

Info 3 — Tropical Rainfall MeasuringMissionSpecification, TRMM-490—OO1

Info 4 — LIS SystemRequirementsPerformance, MSFC-SPEC-TBD

3

MSFC-SPEC—20264/22/93

3.0 FLIGHT SOFTWARE REQUIREMENTS

The LIS flight software is the Read Only Memory(ROM) residentcode and data designedto run the onboardoperationof the Texas InstrumentsTMS320C25 microprocessorcontroller. The LIS flight software shall interpret commandsto the LIS instrument, receive and store digital data fromboth the Real Time Event Processor(RTEP) and the Housekeeping Data Acquisition System (DAS) and also packagedatafor transmissionto the TR1 spacecraft’sFlight Data System(FDS).

3.1 Hardware And Exception GeneratedRoutines

3.1.1 Initialization Software

The LIS flight software shall be automaticallyexecutedupon system power-up or when the microprocessorisresetby the watchdog timer. The watchdog timeT will causeasystemreset if a software failure is detected.Theinitialization software will initialize the TMS320C25, theBus Controller Remote Terminal (BCRT) and also the RTEP foroperationof the LIS instrument.

3.1.2 Filter TemperatureMonitoring

The LIS flight software shall exceptionmonitorthree filter temperatureswhen commanded. In the event thetemperatureexceedsnominally defined parametersthe LISflight software will resetboth heatercontrollers and alsoenable the controller not operatingduring generationof thelast exception.

3.2 Hardware Configuration

3.2.1 Primary Configuration

The primary configuration of the LIS flightsoftware is the firmware that directs the orbital operationsof the TMS320C25 microprocessor.

3.2.1.1 Operation Environment

The LIS software shall operatein the followingenvironment:

SCNOO1TMS320C25 microprocessor8k x 16 bits of external EPROM16k x 16 bits of external SRAM

4

MSFC—SPEC—20264/22/93

3 . 2. 1. 2 Interfaces

The LIS flight software will be written to controlthe hardware interfacesbetween the LIS instrument and theTP1 spacecraft.These interfacesshall conform to the TR21Spacecraftto LIS Instrument lCD (Reference2).

3.2.1.2.1 Command And Control Interfaces

Data transfersbetween the LIS instrument and theTR1 spacecraftwill be accomplishedvia a 1773 fiber opticdata bus conforming to the protocol defined br MIL—STD-1773(Reference3). The LIS flight software shall initialize thebus controller remote terminal (BCRT) hardware to send dataand housekeepingpacketsand receive command and data packetson the 1773 layer, as a remote terminal, in accordancewiththe protocol defined in the TP121 Spacecraftto LIS InstrumentlCD (Reference2). LIS flight software constructsthe data SCNOO1packetsfor transmission.

In responseto a data transfercommand from the TRfliht data system (FDS), the BCRT can operateby performinga direct memory access(DM.A) and/or interrupting themicroprocessor.When in the DMA mode, the microprocessorisplaced on hold, and cannot accessmemory or data. Instrumentcommandsand time updateswill produce a BCRT interrupt of themicroprocessor.All other transferswill be accomplishedbythe BCRT, via DMA.

3.2.1.2.2 Time Mark Interface

The LIS flight software shall receive the coarsetime from the TR1 spacecraftvia the MIL-STD-l773 fiberoptic bus in conformance withthe TRNM Spacecraftto LISInstrument lCD (Reference2). A 1 Hz time mark signal will bereceivedover a RS-422 interface and will generateaninterrupt to the LIS microprocessor.The LIS flight softwarewill replacecurrent time with the new coarsetime uponreceipt of the time mark signal.

3.2.2 Watchdog Timer

In the event the LIS flight software tries toexecuteout of program memory or the LIS flight softwarebecomeslocked in an endlessloop the watchdog timer willreset the TMS320C25. The LIS software shall resetthewatchdogtimer every 1.2 secondsto indicate successfulcodeexecution.

3.3 Commands

The LIS software shall recognizeand decodetheCCSDS packetssent to command the LIS instrument. The formatof thesepacketsis describedin section 2.3 of FDS Appendixof the TRNN Spacecraftto LIS Instrument lCD (Reference2).

5

MSFC-SPEC—2026

11/12/92

3.3.1 Instrument Command List

The LIS flight software shall recognizeand

implement the LIS instrument commands. A list of commandsand

a descriptionof the action required are in Appendix A.

3.3.2 Command Constraints

Constructionof LIS instrumentcommandsshall be

subject to the constraintsof the TR Spacecraftto LIS

Instrument lCD (Reference2), section 8.2 and the FDSAppendix of the TR1 Spacecraftto LIS Instrument lCD(Reference2), section 2.3.1.

3.3.3 Timing Constraints

The following timing constraintsshall be observed:

a. 1773 commandswill be read within 32milliseconds to prevent over writing of thecommand buffer.

b. The BCRT requiresDMA control within 1.9microsecondsafter command receipt. Thesoftware will not executeany code thatpreventsthe microprocessorfrom relinquishingcontrol of the memory to BCRT DMA.

3 .4 OperationalModes

The LIS instrumentwill operate in three modes and

have differing bandwidth allocations. These modes are defined

by the TR1 Spacecraftto LIS Instrument lCD (Reference2).

3.4.1 System Test Mode

The system test mode will consistsof an instrument

self—test that determinesthe operationalhealth of the LIS.

The LIS data output during the systemtest mode shall be

within the bandwidth allocation as assignedby the FDS

Appendix of the TRI Spacecraftto LIS Instrument lCD(Reference2). -

3.4.2 Background Send On Mode

In the Background Send On Mode backgrounddata

shall be appendedto the event data in the sciencedata

packets. The LIS data output shall be within the bandwidth

allocation as assignedby the FDS Appendix of the TRMNSpacecraftto LIS Instrument lCD (Reference2), sections

2.2.4 and 2.2.5.

6

MSFC-SPEC—202611/12/92

3.4.3 Background Send Of f Mode

In the Background Send Off Mode no backgrounddata

shall be included in the sciencedata packets. The LIS data

output shall be within the bandwidth allocation as assigned

by the FDS Appendix of the TRr1 Spacecraftto LIS Instrument

lCD (Reference2), sections2.2.4 and 2.2.5.

3.5 Interrupts

The TMS320C25 has three external maskableuser

interrupts available for external devices.

3.5.1 Real Time Event ProcessorInterrupt

The RTEP will set a flag to interrupt the TMS320C25

at the end of each video frame lightning occuranceor when

the 512th video frame occurs. Video frames are processedby

the RTEP at a rate of one video frame every 2 milliseconds.

The LIS flight software shall acknowledgethe interrupt and

initiate the sciencepacket formation algorithm.

3.5.2 Command and Control Interrupt

The command and control interrupt is generatedby

the BCRT in responseto a valid LIS command requiring

microprocessorinteraction. The LIS flight software shall

respondto the command and control interrupt by acknowledging

the interrupt, reading the command buffer and also executing

the receivedLIS command.

3.5.3 Time Mark Interrupt

The time mark interrupt is generatedby the LIS

hardwareupon receptionof the 1 Hz RS-422 time mark. The LIS

flight software shall respondto the time mark interrupt by

acknowledgingthe interrupt and swapping the ‘new’ and ‘old’

coarsetime memory pointers.

7

MSFC-SPEC—202611/12/92

3.6 Data Formats

3.6.1 LIS Data Formats

The LIS flight software collects, packetizesand

also storesLIS instrumentdata for transmissionover the

TR1 1773 bus. The time stampedLIS instrumentdata utilizes

multiple 1773 subaddressreads as defined in the TRNM FDS

Appendix of the TRI Spacecraftto LIS Instrument lCD(Reference2).

LIS data shall be formed into CCSDS packets. Each

packet includes a primary and a secondarypacket headersas

defined in the FDS Appendix of the TRMM Spacecraftto LISInstrument lCD (Reference2) and also a time stamp to a

resolution of 16 microseconds.

3.6.1.1 ScienceData

The LIS sciencedata consistsof lightning event

data (pixel location, intensity and time stamp to aresolution of 2 milliseconds). Backgrounddata will be added

to the sciencepacket if the number of events is low. LIS

sciencedata shall be compressed(by suppressingsuperfluous

row, pixel, and time information) to maximize data within the

allocatedbandwidth. This compressionalgorithm will allow

for recovery of backgroundand event data on the ground.

3.6.1.2 HousekeepingData

A LIS instrumenthousekeepingdata packet shall

consistsof 16 housekeepingwords from the housekeepingDAS

and statusword(s). The statusword(s) show(s) error status

and command verification returned from the LIS hardware.

3.6.1.3 Packet Structure

All LIS data transferredin FDS data readsshall be

transmittedas CCSDS telemetry packetsas defined in the FDS

Appendix of the TRMN Spacecraftto LIS Instrument lCD(Reference2), section 2.2.2, “Packet Communications”.

The referencedsection specifiesthe CCSDS options

to be used, the protocol governing transmit requests,packet

acknowledgeand also error handling.

8

MSFC—SPEC—202611/12/92

3.6.1.4 PacketFormation Format

The LIS flight software shall maintain two memory

location pointers for sciencepacketsand also two memory

location pointers for housekeepingpackets. A completeddata

packet ready for transmissionto the TRMM FDS will be stored

in one area of memory. A secondarea of memory will contain

the new packet information. Once the confirmation of the data

packet transmissionhas occurred the LIS flight software will

swap the pointer and form a new packet in the same location

of the packet that has been confirmed.

3.6.2 Time Data Format

Coarsetime data shall be transmittedby the FDS

over the 1773 bus as describedin the FDS Appendix of the

TRMM Spacecraftto LIS Instrument lCD (Reference2),

section 2.2.6.

The LIS flight software will maintain pointers to

two memory locations. One pointer will reflect the location

of the current coarsetime and the other pointer will reflect

the location of the new coarsetime.

3.7 Displays

None.

3.8 EngineeringDevelopmentand Analysis Software

The LIS engineeringdevelopmentand analysis

software shall support hardwaredevelopmentand testing. This

software will be written on an as neededbasis.

3.9 Implementation

The LIS flight software shall be written in

assemblylanguagefor the Texas InstrumentsTMS320C25

microprocessor.This languageis written as specified

in the TMS23O AssemblerGuide for the TI TMS320C25(Reference4).

The TMS320C25 has the following resources

available:

1. 533 16—bit word on-chip PAM2. 100 nanosecondinstruction cycle3. 10 MIPS4. 16x16 I/O space

9

MSFC—SPEC—2026

11/12/92

4.0 ELECTRICAL GROUND SUPPORT EQUIPMENTSOFTWARE REQUIREMENTS

The Electrical Ground Support Equipment (EGSE) is a

design and test tool used to simulate the electrical

interfacesand software activity of the TR1 space—craft.The

EGSE software will operatethe EGSE equipmentand command the

LIS instrument. The EGSE software shall have a user friendly

interfaceto automatethe control of the EGSE hardware and

will also provide the ability to store, display and analyze

LIS data.

4.1 Hardware And Exception GeneratedRoutines


The EGSE software shall begin execution following a

run command from the operatingsystem. Further executionwill

be driven by menus or sequencesloaded from floppy disk.

4.1.2 Filter TemperatureMonitor

None.


The EGSE software will support a variety of

simulation hardwareconfigurations. In each configuration the

EGSE software shall provide command and control capability

that makes the hardwareconfiguration transparentto the

user. See Data Flow figures in Section 8.0.

4.2.1 MSFC TR2! Simulator Configuration

The EGSE software shall operatethe TR?1 interface

simulators. The software shall control the interfacesof the

MSFC TR4 simulator and also provide command and monitoring

functions defined in section 4.4.2, utilizing the data format

defined in section 4.6.4.

4.2.1.1 MIL—STD—1773 Interface

The EGSE software will implement the EGSE

computer as bus controller to the LIS instrumentusing the

MIL-STD—1773 command and control interface. The EGSE software

shall drive a MIL-STD—l553 card used by the EGSE and

implement the same command/responseprotocol (Reference3).

10

MSFC-SPEC-20264/22/93

4.2.1.2 Time Mark Interface

The EGSE software will control the time markinterface. The EGSE software shall have the capability toenableor disable the primary and redundantinterface and

also have the capability to enable or disable the interruptgeneratedby the time mark hardware.

4.2.1.3 PassiveAnalog Interface

The EGSE software will drive the passiveanaloginterfaceduring the simulation of the TRt’2’I spacecraft.TheEGSE software shall be able to excite any erie of 4 SCNCOI(redundant) thermistors, convert the analog voltage to a 12-bit digital word and also pass the data to the EGSE ADPequipment.

The EGSE software will drive the passiveanaloginterfaceduring the simulation of the TP2’! spacecraft.The

EGSE software shall be able to excite any one of 8(redundant) thermistors, convert the analog voltage to a 12—bit digital word and also pass the data to the EGSE ADPequipment.

4.2.1.4 Power Distribution Interface

The EGSE softwarewill drive the power distributionsimulator. The EGSE software shall activate the control linesthat open and close the four distribution relays and alsoread the statusof the contact closures.

4.2.2 GSFC TRMM Simulator Configuration

The EGSE softwarewill provide TR!! interfacesimulation by the GSFC simulator hardware. The EGSE softwareshall control the ethernetinterface to the TRM simulatorand also provide command and monitoring functions.

4.2.3 Calibration Configuration

The calibration configurationwill have either the

MSFC TR1 simulator configuration or the GSFC TR12! simulatorconfigurationwith the addition of an interface to thecalibration facility computers.

The EGSE software shall control the interfacebetweenthe calibration facility and the EGSE computersandalso control the exchangeof data betweenthe two systems.

11

MSFC-SPEC—20264/22/93

4 . 2 . 4 Post-IntegrationConfiguration

The post integration configuration is used afterthe LIS instrument has been integratedto the TRI spacecraftand also is used to interface the TR SpacecraftGroundSupport Euipment (SGSE) for LIS checkout. The interface tothe SGSE is accomplishedvia a thin wire (lOBase 2) ethernet. f SCNOO

The EGSE software shall control the interfacebetweenthe EGSE and the SGSE and also provide command andmonitoring functions.

4.3 Commands

EGSE commands shall be issuedby the operatororsequencesstored on disk. All other information supplied tothe EGSE will be classifiedas data.

4.3.1 LIS Instrument Command Simulation

4.3.1.1 Command List

The EGSE software will simulate the FDS by issuingcommandsto the LIS instrument. A list of instrumentcommandsand 1773 mode control commandsare in Appendix Aand Appendix F. The block data transferprotocol is describedin the FDS Appendix of the TR! Spacecraftto LIS Instr’entlCD (Reference2), section 2.2 “Telemetry PacketDescriptions.” The mode control commandsare given inAppendix F.

4.3.1.2 Command Constraints

In addition to constructingall valid LIS commandsthe EGSE software shall test the LIS responsefor generatinginvalid LIS commands.

4.3.1.3 Timing Constraints

The EGSE software shall issue commands subject tothe FDS timing constraintslisted in the FOS Appendix of theTR Spacecraftto LIS Instrument lCD (Reference2), sections2.2.2, 2.3.2, and 2.4. This will provide simulation of theTR FDS while operation in the MSFC TR interfacesimulatorconfiguration-

12

MSFC--SPEC—202611/12/92

4.3.2 Platform Simulation Commands

The EGSE softwarewill support platform simulation

commands in each of the hardware configurations.These

commandsare issued by the FDS to exerciseand test the LIS

hardwarevia the TR1 interfaces.


The EGSE software shall support insuring of the

simulated FDS commands listed in Appendix B in order to fully

exercisethe LIS hardware.


None.

4.3.2.3 Timing Constaints

None.

4.3.3 EGSE Commands

EGSE commandsare defined as:

1. a command that issuesto LIS and/or the

interface simulator, a sequenceof commands

designedto perform a check of LIS response.

2. a command issued to the EGSE that performs some

internal checking function, processesdata, or

controls i/o devices such as printers, disks,

etc.

3. A command issued to control the data exchange

betweenthe EGSE and the calibration facility

equipment.


The EGSE shall provide commandsto perform all the

functions listed in Appendix C.


None

4.3.3.3 Timing Constaints

None.

13

MSFC—SPEC—2026

11/12/92

4.4 OperationalModes

4.4.1 Self—Test Mode

The self-testmode shall be executedupon command,

or immediately upon execution of the EGSE program, unless

this feature is disabledby the user. The default operation

will have a self-testperformed. This default may be disabled

by pressingthe ‘ESC’ key within 1 secondof program

execution. Exiting the program re—enablesthe default. During

self-testmode, there is no requirementfor maintaining the

TRI simulation mode or the analysismode.

4.4.2 TF1 Software Simulation Mode

The EGSE software shall support both the TR!

software simulation mode and the analysis mode (4.4.3)

simultaneously.During the TR1 software simulation mode the

EGSE software will support any one of the three hardware

configurationsand provide also simulation of the activity of

the TR1 FDS software.

4.4.3 Analysis Mode

The EGSE software will display, store and process

LIS and GSE data. Data processingwill verify command

responsesand also data format.

4.5 Interrupts

The time update interrupt routine is only required

in the MSFC TR Interface simulator configuration. The EGSE

software shall processthe time update interrupt generatedby

the time-mark simulator. In responseto the interrupt the

EGSE software updatesthe coarsetime code to the LIS via the

1773 bus. The time of updatewill conform to the timing

constraintsof the FDS.

14

MSFC-SPEC—202611./12/92

4.6 Data Formats

4.6.1 LIS Data Formats

The EGSE software shall be able to check LIS data

for format validity and correctnessand also extract the

following information:

a. Row, column, intensity, and time—stamp of

lightning events.

b. Approximate scenebackgroundand timegenerated.

C. Analog value of each DAS housekeepingchannel.

d. Condition indicated by each bit of the status

word(s)

4.6.2 EGSE Internal Data Formats

The EGSE software developerswill define and

document internal data formats for manipulation of LIS data

as needed.

4.6.3 Calibration Facility Data Formats

All data exchangedbetween the EGSE and the

calibration facility shall be compliant with the format in

Appendix D.

4.6.4 SGSE/GSFCSimulator Data Formats

The EGSE software will support the exchangeof

commandsto and data from the LIS instrumentwhile utilizing

the formats and constraintsrequired by the TR1 IGSE/SGSE

InterfacesDocument (Reference5).

4.7 Displays

The EGSE software will display all LIS data, the

statusof EGSE command settingsand also utilize the dual

display capability of the EGSE. The GSE display will provide

sciencedata and other data.

The MSFC configurationwill include data collected

from the 1773 bus and also data collected from discrete

interfaces.Other configurationswill include data passedto

the EGSE by the ethernetinterface.

15

MSFC—SPEC—202611/12/92

4.7.1 EGSE Command Status

The EGSE software shall allow the user the ability

to view the command statusof the LIS instrument.

4.7.2 EngineeringData Display

The EGSE software shall provide monitoring

capability of LIS housekeepingdata, discretetelemetry and

also simulated TRI’1 interface status.

4.7.3 Lightning Image Display

The EGSE software shall display sciencedata with

the ability to view individual frames of data (in non-real

time) and during active calibration real-time sciencedata.

4.8 EngineeringDevelopment and Analysis Software

The EGSE software will support the developmentarid

testing of the EGSE hardwareand also the LIS instrument.

This software will be written on an as-neededbasis.

4.8.1 Focal Plane Simulator Software

The EGSE software shall control the focal plane

simulator board. This software will be used as a development

and test tool for the RTEP and also provide control of the

output of simulated CCD patternsand simulated lightning

events. The EGSE software should provide the ability to vary

the number, location, and intensity of simulated lightning

events againstvariable backgrounds.

4.8.2 1773 Test Routines

The EGSE software shall meet the developmental

testing of the LIS 1773 command and control interface. The

test routines to be provided are listed in Appendix E.

4.8.3 EGSE Diagnostic Mode

The EGSE software shall provide detaileddiagnostic

tests for the EGSE ADP and simulation equipment. This

softwarewill provide full exerciseof the hardware

capabilities.

16

MSFC-SPEC—2026

11/12/92

4.9 Implementation

Documentationand testing of all software,

including commercial software and reusablesoftware, will be

treatedas if they are a new development.

4.9.1 Developed Software

The EGSE software shall be implementedin a

programming languagecompatiblewith the family of computers

selectedas ADP equipment. The selectedcomputer is an Intel

80486 based IBM compatiblewith an ISA bus structure.

4.9.2 Commercial Software

The EGSE software shall utilize commercially

available software environmentsfor developing software and

as drivers for commercially purchasedhardware interfacesor

peripherals.

4.9.3 ReusableSoftware

The EGSE software will utilize softarewritten for

other NASA projects.

17

MSFC-SPEC—202S

11/12/92

5.0 CALIBRATION FACILITY SOFTWARE REQUIREMENTS

Calibration Facility Software is defined as that

software controlling the generationof simulated lightning

events (through optical stimulation of the LIS instrument)and the software required to analyze the correlation of the

input simulation to the output LIS sciencedata.

5.1 Hardware and Exception GeneratedRoutines


The initialization software shall be a menu driven

setup procedureto select the conditions for the differenttests that will be apart of the calibration. The list of test

options are listed in Table 5.1.

Table 5.1 Test Menu Options

OPTIONS DESCRIPTIONS

1. PIXEL SCAN A pixel by pixel scan ofthe LIS under differentconditions CW, pulsed, with

. or without backgrounds.

2. FLOOD FOV ‘ Full illumination of LIS atdifferent intensitiesandwavelengths.

3. LIGHTNING Providing a real time sceneSIMULATION for LIS with various back

grounds, lightning rates,lightning intensities, inmany locations at nearsimultaneousoccurrences.

5.1.2 Exception Monitoring

TBD


5.2.1 Optical Stimulation Equipment Interface

The acousticoptical scannerand modulator shall be

controlled by a slave digital signal processorthat will

generatethe lightning scenes.All the conditions for the

scenewill be transferredthrough the 486 PC selection

initialization software.

‘S

MSFC-SPEC—2026

11/12/92

5.2.2 TR1 Simulation Equipment Interface

The calibration software shall be capableof

controlling interfacesto the ground support equipment for

the purposeof passinginformation required to compare the

LIS sciencedata output to the input stimulus.

5.2.3 Raw LIS Pixel Data

This data shall be collected by the Matrox frame

grabberboards under the control of the 486 PC. The PC will

initialize the frame grabber boards which are intelligent and

controlled by the PC.

5.2.4 High Speed Photometer

This data shall be collected by the 486 Pc using a

high A/D from National Instruments.The photometerwill

monitor the temporal activity of the lightning simulation.

5.3 Commands

There is one command to indicate the start of the

test to all the processors.

5.4 OperationalModes

The operationmodes are indicated in the top level

menu selectedin Table 5.1.

5.5 Interrupts

There shall be one user interrupt to stop the test

and TBD software error interrupts to indicate problems.

5.6 Data Analysis

Software shall be capableof comparing the LIS

sciencedata to the input stimulus.

5.6.1 Detailed Analysis

This software shall provide the radiometric and

temporal transfer functions for all the pixels in LIS. This

is the results from all the data taken and reducedto a set

of coefficientsdescribingeach pixels performance.

5.7 Displays

The display of sceneby scenecomparisonsof the

generatedsceneand the LIS scenewill be comparedvisually

in near real-time. The 500 frame/secrate of LIS shall be

shown at the standardTV rate of 30 frames/secor less.

19

MSFC—SPEC—2026

1.1/12/92

5.8 EngineeringDevelopment and Analysis Software

Software will be written on an as neededto support

the developmentof the optical stimulation hardware.

5.9 Implementation

The calibration software shall be compatiblewith

the computer system selectedto control the calibration

facility optical stimulus equipment. The hardwarechosen for

this purpose is an IBM compatible, based on the Intel 80386

family of microprocessors.

5.9.1 Commercial Software

5.9.1.1 Assemblers/Compilers

Calibration facility software may make use of

commercially available software developmentenvironments.

5.9.1.2 Commercial Hardware Drivers

Calibration facility software may utilize, if

required, commercially available software for driving the

interfacesbetween the simulation computer and the TR1

simulation computer.

5.9.2 ReusableSoftware

N/A

5.9.3 Functional Partition

Optical Lightning Simulation software shall be

resident in a computer system interfacing to the stimulation

hardware. This machine is different from the computer system

controlling the TRflI simulation.

20

MSFC—SPEC—202611/12/92

6.0 ABBREVIATIONS AND ACRONYMS

ADP — Automatic Data Processing

BCRT — Bus Controller Remote Terminal

CRT - CathodeRay Tube

CCSDS - ConsultativeCommittee for Space Data Systems

DMA — Direct Memory Access

EGSE - Electrical Ground Support Equipment

FDS — Flight Data System (TR?1)

GSFC - Goddard Space Flight Center

Hz - Hertz

IBM — InternationalBusinessMachines

lCD - Interface Control Document

IGSE - Instrument Ground Support System

ISA - Industry StandardArchitecture

I/O - Input/Output

IP&CL — InstrumentProgram and Command List

LIS — Lightning Imaging Sensor

MIPS — Million Instructions Per Second

MS — Milliseconds

MSFC — Marshall SpaceFlight Center

NASA - National Aeronautics and SpaceAdministration

NS — Nanosecond

RAM - Random Access Memory -

ROM - Read Only Memory

RT - Remote Terminal

RTEP - Real Time Event Processor

SGSE — SpacecraftGSE

21

MSFC-SPEC—2026

1.1/12/92

ABBREVIATIONS AND ACRONYMS

SRR — Software RequirementsReview

TI - Texas Instrument

TBD - To Be Determined

TR1 - Tropical Rainfall Measuring Mission

22

MSFC—SPEC—2026

7.0 VERIFICATION MATRIX

Verification Methods: Verification Phases:

A = Analysis DP = Design Phase

I = Inspection IP = ImplementationPhase

T = Test VV = Verification and

X = Information Only Validation Testing

Requirement Verification Remarks

Reference Phase

DP IP VV

3.03.13.1.13.1.23.23.2.13.2.1.13.2.1.23.2.1.2.13.2.1.2.23.2.23.33.3.13.3.23.3.33.43.4.13.4.23.4.33.53.5.13.5.23.5.33.63.6.13.6.1.13.6.1.23.6.1.33.6.1.43.6.23.73.83.9

X

XX

I

I

XAAAX

x

XII

AAA

I

A.

ATIII

T

TT

I

IIIT

T

TTT

TTT

TT

Flight Software

LI! 12/92

23

VERIFICATION MATRIX

MSFC-SPEC-202611/12/92


A = Analysis DP = Design Phase

I = Inspection IP = ImplementationPhase



Requirement Verification Remarks

Reference Phase

DP IP VV

4.04.14.1.14.1.24.24.2.14.2.1.14.2.1.24.2.1.34.2.1.44.2.24.2.34.2.44.34.3.14.3.1.14.3.1.24.3.1.34.3.24.3.2.14.3.2.24.3.2.34.3.34.3.3.14.3.3.24.3.3.34.44.4.14.4.24.4.34.54.64.6.14.6.24.6.34.6.4

X

X

XX

X

XX

XXX

X

X

X

IIIII

A

A

I

T

TTTTT

II

I

II

TIII

I

I

EGSE Software

24

VERIFICATION MATRIX

MSFC-SPEC-202611/12/92


A = Analysis DP = Design PhaseI = Inspection IP = ImplementationPhase



Requirement Verification RemarksReference Phase

DP IP VV

EGSE Software(Continued)

4.7 X4.7.1 I4.7.2 I4.7.3 I4.8 X4.8.1 I4.8.2 A4.8.3 A4.9 X4.9.1 I4.9.2 A4.9.3 X

Calibration5.0 X Facility Software

5.1 X5.1.1 I5.1.2 X5.2 X5.2.1 A I5.2.2 A I5.2.3 X5.2.4 I5.3 X5.4 X5.5 A I5.6 T5.6.1 A I5.7 A5.8 X5.9 A I5.9.1 X5.9.1.1 X5.9.1.2 X5.9.2 X5.9.3 A I

25

MSFC—SPEC—2026

11/12/92

8.0 DATA FLOWS

The following figures make up the Flight and EGSEsoftware functional data flows. Figure 8-1 is a flighthardwareconfigurationchart. Figures 8-2 through 8-5 are

flight software functional data flow charts. Figures 8—6

through 8-7 are EGSE software functional data flow charts.

Figures 8-8 through 8-10 are ground hardwareconfiguration

charts.

26

—t

• I

(11C)z0C)

1.rj

(I)

JM

“ii

•-0

Flight 5oftara Functional Data

LiS Hacdh4aru Configuration

F 1 o

RTE P

V-..h.td 4.—..

g..%

11.1 d I.m.rl

I.), I..t

UjIt.aI t.-a’....,..

Fit,., Ii

F

Control lur

E a c t ro n I c s

Focal P1na

lb • II bit.

(FRUIt

C

I 1PillG2l

bIb • ii bib

L

C. ..d’Pi..d. Lull

ii, I I 4 - iiI

0.....

T PM H5/C Intarfocus

I I IIi i•,..(...

I I I Q.tb..I 1.1*.

L

I c I

I -1I I

It

I I

F D5

FIjura 8—1 L15 IIcircIi-,ijr Conficjiirttiui

C0

6L

C.

o C— 0L. u

C—

11

Lfl C—

— ‘O6 6

Co

— n ç)— LU —

C.—

6D

U CL irj

C— S

o — -

U, to

-o— 0.

—

— 6L

U’

CtO

C

U

MSFC-SPEC—20264/22/93

•5 .

-•.

CC

— •

—ca.

I

—

U C

, InCU

SCN001

Us

C

asS

H

Us

C00

U

c’1

UiC

LL

C—

•• C‘4• a

I.1

CU

C

zC’

0

28

F I I (.J I t 5 o U t j I c: I i u ii a I I) (1 I. i I I o

T in e II a r k P e c I L I o r-

(I)

()

C’)

-t11fl

Figure 8—3 Time Mark Reception

Sc I e n c e

ij

(I)‘ii

.1

F I cj Ii So F t ii ri r: o 1 Dci t ti

Packet Eorrncit I on

RTCPrI12oC2

Figure 8-4 SciencePacket Formation

MSFC-SPEC202611/12/92

_:Z

z

CC

t

VCC

— oJLiC uC

C

- CV

C.— cli

clio -

111U,

CC

0

0

ci

C4

.—

a)a)

a)u.i

0

—-

ELSE 5oftcnc Funczi i on(31 FDitc I1

I i n’ e [) ci I. d F o r in ci I. c ii

I. me ‘Mdrk iicktio-,I (‘cIg( lt€)€J (iI I Pikut

1 ii I U U’ U’ ci t 111 1 i r u -. —. ° -• I me I Iji U €3 I I oI 5’.i (:•d

(lu I urndl ecj Iuriiidl

3eqcier1ce [)dL€3Ia,e

[_15 Jr’s (r’urnenl CornhTidrlc.I 1’,cI Il ocz[ lr’irl% I(E?r’ [)it I 1

( 1

lfi)LJt

______

I US Icis ‘, Pic.I i-i I 1’ €1 (iS! (5 1 I (I)

(.orrmdi’sd Lf 5 (-,J

__________

I—

I I I ti in I

eqtience Q

(2 i. .pm,-i is U %,D

5)1 inc.) IUi I csI c) S C

Figure 8-6 Time Data Formation

flc:qu s i I ion

[1j)E 5o 1 1. vid1’1 F uric ( I 0 nd 1

[)iscr’ee elernelr’tj

[is er

1 ri j u tEu ud

}heririi S to,

x

[)E1 I d 1

I citchcl I C) U

C I ci Ii I I

x

flu t C) lflci L

U CI Li U) (iC U) S

Fo Iiad1I.ermi s t or

x

L sCo ii, c

i C) II ci I

1 0 11/1)

I’ljdcI/)t (i1(?

I (IOU)

I rn(jI: ‘. I o C k

I)li Ii-i c_I (.) 1

CL) liv U)1 S I (ill

I i CII?

I iii L I). ii e

1•i .I 1 Ii I I

I)ci I ci

¶3t 01 L Dci I ciIlio ii I i

S P 1I ci

iit

ii

(n

(11

1t1IF-’fl

(‘3

Figure 8-7 Discrete Telemetry Acquisition

1 NMM Si mu 1 t i on IIrcivir’e C o n l 1 ii ci o ii

( i13i ( [1 r I c: c i mu ‘I (1 c) r

IJ1)1 Cdl

I— I ll)Cr

_______________

—f) )--——. 5i a.

I — Co.ipl ci—

- ))-------. F--—-—

_____________

ei)M

f Di suit iiiiJj -—... joriuruI 1”..

1.19 ‘12

(Jr

I

II: 1

I (. 1 I

F I he r

IS A

\. )

5. ..S/ 1 /1’ — .. MIt.- 9(1) 1 9-i.i

IraiisIi1u, --

ci 1 ii J Prir.tci. ]

[

0 (Ti I 11 L (? 1-

1 I I..

I (.1,- ii ‘—.Ir

r:’ :‘:

1 (.01

I) I S (I I I

1 I’ I

hard(Ti k

f L?L,ouii ii]

Sequ I Ii 1 ii S

(Zci I hr I I ii

I

ci. I I ij

liii ci I ci.: C

I Ill)

C,)

C)

b.th1

1301

Figure 8—8 MSFC intertaceSimulator

TIRMM Si mu 1 E] on

(usrc

Ii E r’ (1 ‘-1 c3 i-

I n I. e r F c e

(.oniiçjur’Etior’i

i mu E 1 a

LI ::5 I 3[_

(

Of) t C d II ber

IiJ. I- — -

J

r c I [

1lUJ0ld I[Jt::i:csj

__________

Pr i er 1

CNI1)1 p I d .j

‘.1 (:RTDi spi )j

j Disk

L 5 F CSp c C P C

5 i mu 1 E1 t 0 C

C . I i I) I ,i I

I .ic I I a

I ‘ i Ii i’

I Flit) I

(I)I1C)

a—n—I

-0s-ct’)

Figure 8-9 GSFC Interface Simulator

9E

UuL

t 1< H H- F’

J’ ,‘_‘

IC 1D

a

1CD

D

Crn

r1CD

rr

C

I-)C

C

0

-J

a

0

C

D-j

12;

C

—

I-J

-

1D

WH

c-)

uj

-j

1

t J

Z6/ZI/II

9 O-DdS-DSW

MSFC-SPEC-202611/12/92

Appendix A

LIS Instrument Commands

1. Background Send ON

This command will causethe flight software to enter theBackgroundSend On Mode (section 3.4.2.1).

2. Background Send OFF

This command will causethe flight software to enter theBackgroundSend Of f Mode (section 3.4.2.2).

3. ThresholdAdjust

This command will include new thresholdvalues for the RTEP.

Flight softwarewill place the new values in the RTEPthresholdmemory.

4. Filter TemperatureSet Point

This command will include a value representinga set point

for the filter temperaturecontroller hardware. Flightsoftwarewill write this value to the temperaturecontroller

board.

5. Self Test

This command will causethe flight software to perform an

instrument level self-test. Software will executethe

following instructions:

TBD

6. Aperture Door OPEN

This command will causethe flight software to open the LIS

aperturedoor arid also check the aperturedoor status.

37

MSFC—SPEC—2026

11/12/92

7. Watchdog Timer Enable

This command will causethe flight software to enablethe

watchdog timer.

8. Watchdog Timer Disable

This command will causethe flight software to disable the

watchdog timer.

9. Heater A ON

This command will causethe flight software to resetboth

filter heatersand then enable heaterA.

10. Heater B ON

This command will causethe flight software to resetboth

filter heatersand then enable heaterB.

11. Enable Filter TemperatureException Monitoring

This command will enable software exceptionmonitoring of the

filter temperatureand automatic switching betweenthe A and

B heaters(section 3.1.2).

12. Disable Filter TemperatureException Monitoring

This command disablesthe automatic switching fuction enabled

by the Enable Filter TemperatureException Monitoring

command.

38

MSFC-SPEC—202611 / 12/ 92

Appendix B

Simulated FDS TR?1 Interface Commands

1. Read Thermistor #N

This command will causethe EGSE software to read the

temperatureof LIS thermistor #N, where N = 1 - 8.

2. Enable Primary Time-Mark

This command will causethe EGSE software to enable the

primary timemark.

3. Disable Primary Time-Mark

This command will causethe EGSE software to disable the

primary time-mark.

3. Enable RedundantTime-Mark

This command will causethe EGSE software to enable the

redundanttime—mark.

4. Disable RedundantTime-Mark

This command will causethe EGSE software to disable the

redundanttime—mark.

5. Assert Relay Control Line #N

This command will causethe EGSE software to assertthe relay

control line, energizingthe associatedcoil of the

magnetically latching relays distributing power to the LIS

instrument. This command will be labeled as the following

titles:

- Primary EssentialBus ON- Primary EssentialBus OFF- Primary Non—EssentialBus ON- Primary Non-EssentialBus OFF- RedundantEssentialBus ON- RedundantEssentialBus OFF- RedundantNon-EssentialBus ON- RedundantNon-EssentialBus OFF

39

Z6/ZI/!IgzOz—aS—DaSN

Q1

SpUtU1I0D 3S

D XTpUeddY

S

MSFC—SPEC—202611/12/92

Appendix D

Calibration Facility/EGSE Data ExchangeFormats

The EGSE software will remove all CCSDS overheadarid

protocol from LIS sciencedata. The EGSE software will also

provide the calibration facility with the compressdLIS

sciencedata packet. No header, parity, or other overhead

will be applied to the LIS sciencedata by the EGSE.

The EGSE will provide to the calibration facility each

LIS packet of sciencedata received. The data will be

provided within the timing constraintsof the EGSE. Should

multiple LIS packetsbe available, the latter packetswill be

appendedto the previous.

LIS backgrounddata that has been accumulatedcan be

sent upon command to the calibration facility as a full

128x128 frame of data. The format of this data will be as

follows:

<time stamp><rowl, pixell value><rowl, pixel2 value>

<rowl, pixell28 value><row2, pixell value><row2, pixel2 value>

<row2, pixell28 value>

No packet headersor flag will be applied. Hence, the

calibration facility computer must be in the proper mode to

receive this data prior to the EGSE command.

41

MSFC-SPEC—202611/12/92

Appendix E

LIS InstrumentDevelopmentalTest Routines

1. Send 1773 command word to LIS, subaddressN, requesting

the transmissionof 32 data words. N = (1,31). Verify proper

statusword received from LIS.

2. Send 1773 command word to LIS, subaddressN, requesting

the transmissionof X data words. N = (1,31); X = (1,32)

Verify proper statusword received from LIS.

3. Send 1773 command word to LIS, subaddressN, indicating

the transmissionof 32 data words. Send LIS 32 data words.

N = (1,31). Verify proper statusword received from LIS.

4. Send 1773 command word to LIS, subaddressN, indicating

the transmissionof 32 data words. Send LIS X data words.

N = (1,31); X = (1,32). Verify proper statusword received

from LIS.

5. Send LIS instrument comands (Appendix A) and verify

proper statusword received from LIS.

6. Send valid commandsto non-LIS RT addresses.Verify LIS

does not respond.

7. Send invalid commandsto LIS and non—LIS RT addresses.

Verify LIS does not respond.

8. Send mode commands (Appendix F) to LIS and/or as

broadcast.

9. Broadcasttime commands to LIS.

42

MSFC-SPEC—2026

11/12/92

Appendix F

1773 Mode Control Commands

The following 1773 mode codes, as required byMIL—STD—1553B, Notice 2, shall be implementedby EGSEsoftware:

Function Mode Code Transmit/ReceiveBit

Transmit StatusWord 00010 1

TransmitterShutdown 00100 1

Override Transmitter 00101 1Shutdown

Reset Remote Terminal 01000

These commandsshall be formed in compliancewith

Reference3.

43

Date post:	14-Jul-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times