rs422 communication protocol standardisation

12
ESA UNCLASSIFIED – For Official Use RS422 Communication Protocol Standardisation Torbjörn Hult

Upload: others

Post on 27-Dec-2021

12 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

RS422 Communication Protocol Standardisation

Torbjörn Hult

Page 2: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 2

UART protocol study

Objective to define physical and data link layer requirements as input to an update of the ECSS-E-ST-50-14C standard

Study performed by RUAG and TERMA

Started Feb 2013, end May 2014

Tasks performed:

Survey of existing protocols and collection of user requirements

Preparation of physical and data link layer requirements, including test bench definition

Test bench manufacturing and requirements verifications

User needs survey performed and user requirements and draft physical and data link layer requirements distributed to the survey responders interested in following the work.

Page 3: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 3

UART physical layer

Based on ECSS-E-ST-50-14C terms and clause 8.8 physical layer: Relaxed impedance matching and

ground displacement voltage requirements (±1 V)

Drive current characteristics more detailed

Up to 16 m cable

Recommend to use a 9-pin connector at PE side

Optional cross-strapping at CE side to simplify sensor/actuator design

CE = Core Element PE = Peripheral Element ASDI = Asynchronous Serial Digital Interface

TxRLOAD

VOUT

IOUT (mA)

VOUT (V)

IOUT

50

1

2

3

4

5

0

ISC

VL2

VL1

ZOUT

VOC

Page 4: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 4

UART character layer (part of data link layer)

Characters and BREAK defined.

Even parity recommended

Baud rates of 19,2k, 115,2k and 460,8k recommended. 9,6k, 38,4k, 57,6k and 230,4k allowed

Baud rate tolerances, start bit transients, skew, signal transition oscillations and receiver margins defined in detail

D0(LSB) D1 D7

(MSB)PAR(opt.) STOP

11 (or 10) bits

START

tBtiming reference

Next Character START bit

> 13 · tB – tSKEW > 1 · tB – tSKEW

BREAK

START bit

(N+0.5) ∙ (tB + ΔtB)

timing reference

tRM

11 (10) ∙ (tB + ΔtB)

Next Character START bit

0.5 ∙ (tB + ΔtB)

tRM tRM tRM tRM

Page 5: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 5

UART frame layer (part of data link layer)

Master/slave communication

Delimited by header and end flag (FEH)

BREAK used as communication synchronisation

Break

RSP link:

CMD link: CMD header Flag

RSP header

Cargo

Cargo

2 Bytes 0-4095 Bytes 1 Byte

2 Bytes 0-4095 Bytes 1 Byte

Flag

1 Byte

AB

CMD message

RSP message

I T Len(11:8) Len(7:0)First header byte Second header byte

CMD RSPI = Instruction/information code 00: Command Normal response

01: Not used Error response10: Reserved Reserved11: Reserved Reserved

T = Transaction ID, copied from CMD to RSP

Page 6: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 6

Master/Slave protocol

Note that the protocol is a Master/Slave protocol, and in the SAVOIR context it will be managed by the RTU

SAVOIR | Jean-Loup TERRAILLON | Malta | DASIA2011 | 18/05/2011 | Pag. 6

Figure 4-1 from ECSS-E-ST-50-14C

Page 7: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 7

UART frame layer - upper layer interface

The CE Frame Layer interface to upper layer includes the following:

Cargo of CMD messages for transmission

Transaction ID for transmission

Cargo of RSP messages received

Received Transaction ID

Frame Layer RSP error events

Command communication synchronisation (BREAK)

Command AB Sequence (including BREAK)

Command AB Character only

The PE Frame Layer interface to upper layer includes the following:

Cargo of CMD messages received

Cargo of RSP messages for transmission

Frame Layer CMD error events

Page 8: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 8

UART frame layer options

Pipe-lining allows full bandwidth utilisation with relaxed timing constraints for instance when loading or dumping PE memory

Future protocol extensions using the reserved I-field values 10B and 11B are e.g.:

Addressing multiple PEs on a single RS-485 link

Adding data field headers

Auto-baud function using BREAK + 55H character allows for simple oscillators in the PE

AB Sequence

BREAK AB Character< 100 ms

AB Byte = 5516

CMD:

RSP:

Load memory:

Dump memory:

CMD:

RSP:

Page 9: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 9

Verification

Performed by analysis and test

By analysis:

Failure propagation

Interface Timing margins

Baud rate, BREAK, Autobaud, bit jitter, FPGA utilisation

By test:

Tx electrical characteristics (voltages, currents, rise/fall time)

Rx electrical characteristics (voltages, currents)

Tx bit skew at different baud rates (9600 – 460800)

Rx bit skew tolerance at different baud rates

Autobaud timing skew

Character and Frame layer protocols incl. error injection

Page 10: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 10

Test bench

Labview(FPGA Module)

PC

PCI Express

USB

USB

PXI ChassisFlexRio Module

RS-422 Rx/Tx

RS-422 Rx/Tx

UART (Test)

FPGA

UART (CE/PE)UUT

Arbitrary Generator

OscilloscopeTrigger

NI PXIe-1073FlexRio Adaptor Module

: COTS

: CUSTOM

: INSTRUMENT

CableZo=120Ω

NI PXI-7962R

Page 11: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 11

Test bench

Page 12: RS422 Communication Protocol Standardisation

ESA UNCLASSIFIED – For Official Use

Who | What | Where | When | Pag. 12

Contact

Feedback: [email protected]