Services

  1. MORSE Guide 2
  2. Services
https//www.racom.eu/eng/support/morse-m2/services.html
10. Services
Prev   

Print version

10. Services

10.1. Service 0x18 Echo

The Echo packet (! command) goes throught the network to the destination address and back. On each addresses is attached 8 bytes describing the way in the node and out of it.

Request format:

| serNo/16 | type/16 |

Response format:

| serNo/16 |
| prefix/3 | par1/5 | par2/8 |      |
| addr/32  |                        | added for each address
| prefix/3 | par1/5 | par2/8 |      |

Items meaning:

serNo/16

E018 – service number

type/16

This item is added in the version 9.0.28.0 and higher. It distinguishes the echo packet from statistical test and from the exclamation mark command. Allows the concurrent aplication of both this commands.

0001 – Echo paket generated from the statistical test
0002 – Echo paket generated by the exclamation command “!”

addr/32

MORSE address of the visited node

prefix/3
valuevisiblemeaning
 on 4 bites 
00obsolete
12direction in the node
24direction out of node
36,7packet incomming via RFC
48serd (service dispatcher, turning point of the route)
6Cuser (beginning/end of the route)

Meaning of next two items depends up the prefix value:

For prefix = 1, 2, 6 :

par1/5
valuemeaning
1SCC
2RFC
3ETH
4NAG
Finterconnection (direct connection between nodes)
par2/8

number 0 to 4 – CNI id (e.g. SCC can have id from 0 to 3)

par2/8 has no significancy for the case when par1/5 = F

For prefix = 3 :

par1/5

DQ of the incomming RF signal

par2/8

RSS of the incomming RF signal

For prefix = 4 :

par1/5

has no significancy

par2/8

has no significancy

Items format overview:

prefix/3par1/5par2/8
0 obsolete  
 1 SCC 
1 into node2 RFCchannel No.
2 out of node3 ETH 
6 user4 NAG 
 F interno significancy
3 rfDQRSS
4 serdno significancy 


The packet types

  • Echo with trace, secured packet

    Request:

    0x98

    Response:

    0x9A

  • Echo with trace, unsecured

    Request:

    0x18

    Response:

    0x1A

  • Echo without trace, unsecured

    Request:

    0x10

    Response:

    0x12

Examples:

The examples are valid for Setr 9.0.28.0 and higher. The previous versions use a shorter packets where the item type/16 = 0x0002 is missing.

Echo packet as result of the ! command:

packet type 0x98, data sent 0xE018 0002 …

>>!h22

690F0022h>!

690F0022h>
u S00   690F0011    R01 
25/ 84  690F0022   serd 

 serd   690F0022    R01 
31/ 82  690F0011  u S00 
690F0022h>
13:22:05.050|690F0022 690F0011|690F0022 690F0011|14F  RFTX    12 98 4dat 0
E018 0002 C100 690F 0011 4201
13:22:05.096|690F0011 690F0022|                 |14F*31~ 82    0*06  ack
13:22:05.164|690F0011 690F0022|690F0011 690F0022|153*31* 82   28*9A 4dat 0
E018 0002 C100 690F 0011 4201 7954 690F 0022 8000 8000 690F 0022 4201
13:22:05.164|690F0022 690F0011|                 |153  RFTX     0 06  ack

Echo packet generated using the Send packet test:

packet type 0x98, data sent 0xE018 0002

Send packet: (N):1   (d):690F0022h
(t)ype:0098h
s(o)urce:690F0011h
d(a)ta:....                        ...0xE018 0002
random data (l)ength:0byte
(r)epeat period:0ms + (j)itter:0ms
IP (P)ing
(s)tart r(e)port sto(p)
(q)uit
>>s

>>O.K.
>>

 test   690F0011    R01 
26/ 72  690F0022   serd 

 serd   690F0022    R01 
30/ 71  690F0011  u S00 
>>
13:40:46.367|690F0022 690F0011|690F0022 690F0011|15E  RFTX    12 98 4dat 0
E018 0002 A000 690F 0011 4201
13:40:46.414|690F0011 690F0022|                 |15E*31~ 71    0*06  ack
13:40:46.497|690F0011 690F0022|690F0011 690F0022|160*30* 71   28*9A 4dat 0
E018 0002 A000 690F 0011 4201 7A48 690F 0022 8000 8000 690F 0022 4201
13:40:46.498|690F0022 690F0011|                 |160  RFTX     0 06  ack

Echo packet generated using the Send packet test:

packet type 0x10, data sent 0xE018 0002

Send packet: (N):1   (d):690F0022h
(t)ype:0010h
s(o)urce:690F0011h
d(a)ta:....                        ...0xE018 0002
random data (l)ength:0byte
(r)epeat period:0ms + (j)itter:0ms
IP (P)ing
(s)tart r(e)port sto(p)
(q)uit
>>s

>>O.K.
>>
13:50:32.623|690F0022 690F0011|690F0022 690F0011|163  RFTX    4 10 5dat 0
E018 0002
13:50:32.749|690F0011 690F0022|690F0011 690F0022|167*31* 73   4*12 5dat 0
E018 0002

Echo response contained in the MARS-A packet:

13:53:45.244 tx     14 | S03
F00A 1200 690F 0022 E018 0002 6B3D

Echo packet generated using the Statistical test:

packet type 0x10 also RSS (m)easure:OFF, sec(u)rity:OFF
data sent 0xE018 0001 …

>>
14:02:52.399|690F0022 690F0011|690F0022 690F0011|17B  RFTX    10 10 2dat 0
E018 0001 0004 FFFB AAAA
14:02:52.474|690F0011 690F0022|690F0011 690F0022|17B*31* 72   10*12 2dat 0
E018 0001 0004 FFFB AAAA

Format description valid for fw 9.0.28.0.


10.2. Packet type

The packet type is a parameter length 1 byte characterizing the packet. It influences the packet processing in the node.

The packet type presented are valid for the communication protocols (MARS-A, MARS-U, MAS, slip, ppp, ethernet). The packet type used in the MORSE retranslations channels is slightly different, e.g. in the broadcast bit.

User packet types:

|S/1|B/1|H/1|NT/5|

Meaning of items:

S/1

security

B/1

broadcast

H/1

handicap/priority

0high priority
1low priority
NT/5

network type

meaning of item NT:

0x00reserved
0x01reserved
0x02reserved
0x03reserved
0x04reserved
0x05reserved
0x06reserved
0x07reserved
0x08reserved
0x09USER DATA C1 (CHANNEL 1)
0x0AUSER DATA C2 (CHANNEL 2)
0x0Breserved
0x0CNetwork message (former PACK ERROR)
0x0Dreserved
0x0Ereserved
0x0FMONITORING
0x10SERVICE REQUEST
0x11reserved
0x12SERVICE REPORT
0x13reserved
0x14reserved
0x15PATH – packet having predefined trace
0x16reserved
0x17reserved
0x18SERVICE REQUEST+TRACE; (see 0x10)
0x19reserved
0x1ASERVICE REPORT+TRACE; (see 0x12)
0x1Breserved
0x1Creserved
0x1DPATH+TRACE; (see 0x15)
0x1Ereserved
0x1Freserved

TRACE is a compilation of trace passed by the packet

Examples

The packets incomming from SCC0 to Setr via MARS-A protocol are monitored. The 3rd byte contains the packet type.

Packet type 0x09 USER DATA

The packet of type 0x09 received from address 690F0003:

2007-06-11 06:44:20.933  rx1 12
C008 0902 690F 0003 AAAA 0AAC

Packet type 0x90 SERVICE REQUEST, secured

Packet type 0x92 SERVICE REPORT, secured

Service request sts of type 0x90 is sent to address 690F0002, the report of type 0x92 came:

690F0002h>sts

690F0002h>
2007-06-11 06:42:56.762  tx1 14
E00A 9081 690F 0002 E00A 7300 8A8C 

2007-06-11 06:42:56.882  rx1 16
C00C 9201 690F 0002 A00A 3436 3633 990F

Packet type 0x98 SERVICE REQUEST+TRACE, secured

Packet type 0x9A SERVICE REPORT+TRACE , secured

Echo packet ! is sent to address 690F0002:

690F0002h>!

690F0002h>
2007-09-05 11:03:55.60  tx1 14
F00A 9886 690F 0002 E018 0002 
E19B 

2007-09-05 11:03:55.220  rx1 46
C02A 9A06 690F 0002 E018 0002 
C100 690F 0001 4201 7E50 690F 0002 8000 
8000 690F 0002 4201 7C52 690F 0001 C100 
D139 

u S00   690F0001    R01 
30/ 80  690F0002   serd 

 serd   690F0002    R01 
28/ 82  690F0001  u S00 
690F0002h>

Setr version 9.0.27.0 and lower uses for Echo the word E018 instead of newer E018 0002.

Packet type 0x15 PATH

Service request sts is sent using path packet to address 690F0002:

path  690F0002h>sts

2007-06-11 06:43:49.778  tx1 26
C016 1580 690F 0001 8200 690F 0001 690F 0002 0010 E00A 7300 AD81 

2007-06-11 06:43:49.919  rx1 28
E018 1500 690F 0001 8201 690F 0002 690F 0001 0012 A00A 3437 3136 BB0D

Packet type 0x1D PATH+TRACE

Echo packet ! is sent using path packet to address 690F0002:

2007-09-05 11:43:24.504  tx1 26
F016 1D80 690F 0001 8200 690F 0001 690F 0002 0018 E018 0002 
E699 

2007-09-05 11:43:24.270  rx1 58
C036 1D00 690F 0001 8201 690F 0002 690F 0001 001A E018 0002 
C100 690F 0001 4201 7E4E 690F 0002 8000 
8000 690F 0002 4201 7D4F 690F 0001 C100 
D53B 

u S00   690F0001    R01 
30/ 78  690F0002   serd 

 serd   690F0002    R01 
29/ 79  690F0001  u S00 
path  690F0002h>
Prev   
9. Protocols Contents 

©  2024 RACOM s.r.o. All Rights Reserved.