Situation – connection of AAA application in Windows through MAS with CU (Communication Unit) MR400 and to the MORSE network. The AAA application is replaced here by Setr.
MC100, MG100, MR900, MR25ET, MCM302ET or sw Walrus and Morce work in the same way as MR400.
Configuration consists of the following steps:
Entering IP addresses – into PC and through service cable to CU
Ping testing – ping PC -> CU along Ethernet link
Starting Setr – CU connected via Ethernet link, ping PC <- CU
Setting routing – configuration for a single PC or for more users
Setting MAS – select range of PC addresses, filling Art table
Test from mtu menu – sending UDP datagram from Setr via MAS to remote CU, sending MORSE packet from CU via MAS to PC
Starting application – after this activation simply replace Setr with another AAA application and the connection is ready
The numbered steps are described below in detail, with a brief summary given at the end.
1. Local connection via Ethernet
First set a suitable IP address and mask in a PC running Windows98 or WindowsXP, for example:
IP adresa - 10.0.0.1 maska - 255.255.255.0
The MORSE CU of the MR400 is in its default state. Connect to the CU using the service cable and set the IP address and mask, e.g.:
EPe 0i0A000002 ... to je 10.0.0.2
0nFFFFFF00 ... to je 255.255.255.0Insert the MORSE address in CU (since version 9.32 this address can stay zero):
Ne 1a690F5600 ... MORSE address
2. Ping
Now we can remove the service cable and connect the PC and CU using the crossed Ethernet cable. Test the connection by sending a ping from the command line in the PC to the MR400:
ping 10.0.0.2
3. Setr
If the ping works we can start Setr in the PC running Windows:
setr -pIP10.0.0.2
We can test this PC – CU connection in local mode by calling certain services, e.g.:
sts ... which replies with the number of seconds
since starting the CU, e.g.:
>>312Now it is possible to test a ping from the CU to the PC:
EPe 0tP t0A000001 ... IP address of PC 10.0.0.1
s ... (s)tart
e ... r(e)port gives the result
p ... sto(p)If no reply returns we should search for the error in the steps carried out so far.
Setr connected in such a way is only able to communicate with the local CU. Connection with other MORSE network CUs is possible after configuring MAS, see below.
![[Note]](/images/radost/images/icons/note.png){kind=icon} | Note |
|---|---|
In the PC (WindowsXP especially) can be active the firewall, which prevents the ping receiving. Switch it off for the test purposes. If we are working in LAN with the name server in which the CU address is defined we can enter the name of the computer instead of the IP address when starting Setr, e.g.: setr -pIPradiomodem.racom.cz setr -pIPradiomodem |
4. Routing
Now we have to decide if we will use only one single MORSE address and one single application, or a group of 256 addresses and more applications (on more computers).
4A. Single address.
Add the connection to ETH channel in the Node menu:
Ne 1uE0 ... routing the user output from the node to the AAA app.
1sE0 ... routing service packets to SetrSet the EIe menu to the default condition:
EIe f ... routing the user output of the Ethernet channel to node 1
5A. MAS configuration
Setting the EPe menu for MAS mode:
EPe 0t s1 ... link to Art table number 1
B690F5600 ... Base - required PC MORSE address
M00000000 ... zero mask requires an absolute match
for the Base and PC addressesNow it is necessary to fill in Art table number 1. We have the possibility of doing this automatically or manually using Setr. For automatic filling switch off Setr (Alt+X) and then start it again using command:
setr -pIP10.0.0.2 -pm8000 -pw690F5600
where the meaning of parameters is:
-pIP10.0.0.2 ... IP address of CU
-pm8000 ... number of UDP port of application (Setr), in decimal
-pw690F5600 ... MORSE address, under which the application will be
known in the MORSE network, in hexadecimalAfter starting Setr read the contents of the Art table:
ART No 1: items: 1 default gw: 00000000 (0.0.0.0 ) dest: gw: 690F5600 1F400001 (105.15.86.0 31.64.0.1 )
The Art table contains:
in the
destcolumn the MORSE address, under which application AAA is known in the MORSE networkin the
gwcolumn there is a composite expression – let´s note that 0x1F40 is 8000 in decimal, which is the UDP port of our AAA application and furthermore 0x0001 is the lower part of the IP address of the computer running windows, from which only the lower 14 bits are valid and the upper 2 bits are zero.
We can fill the Art table in this manually for the necessary combination of addresses. It is useful to block automatic filling with the command:
EPe 0t ef ... (e)nable:OFF
Appearance of the respective part of the menu:
MAS: (s)Art:1; write (e)nable:OFF (B)ase:690F5600 (M)ask:00000000
Now MAS is ready to transfer UDP datagrams from the AAA application, operating at the IP address 10.0.0.1 and at port 8000, which appears as address 690F5600 in the MORSE network.
We can check functionality using Setr. Switch Setr off and start with the parameters:
setr -pIP10.0.0.2 -pm8000 -pw690F5600 or setr -pI0A000002 -pm0x1F40 -pw690F5600 >>!h 690F5600>sts 690F5600>1245 ... example of a reply
If no reply arrives search for the error in the steps according to points 4. and 5.
4B. More addresses, connecting Setr via LAN
Situation – The MR400 and several PCs are connected to the LAN network. Through the common MR400, on which MAS is running, it is possible to connect these PCs to the MORSE network. Each PC in the MORSE network is represented by a different MORSE address. Other applications may also be connected via the LAN network in this way.
Configuration:
MR400 has for example the address 690F5600
The PCs use addresses 690F5701, 690F5702, 690F5703, ….
In the Ne menu we set the wide table, which will route
packets for the PC to the Link output. Switch on address multiplication,
which sends packets originally routed to Link to the User output, and
connect the User and Service output to E00:
Nodes:
retab
Nid|address |M | u s | L N |l w n g H|sTO Err Cent vTO hTO
(0) 0048E62D - S00| - R00|0 0 0 0 -| 15 SERV OFF 304 30
(1) 690F5600 L E00 E00| - R01|0 1 0 0 -| 15 SERV OFF 304 30
(2) 00000000 S01 S00| - R02|0 0 0 0 -| 15 SERV OFF 304 30
(3) 00000000 S02 S00| - R03|0 0 0 0 -| 15 SERV OFF 304 30
(4) 00000000 S03 S00| - R04|0 0 0 0 -| 15 SERV OFF 304 30The routing wide table sends packets which have the PC destination address to the actual address of the node:
>> Wide retab. No 1 57to:5600
The EIe menu remains in the default condition:
Channel to Node Interface:
retranslation | user+service lim
id N A t m | N A t Base m sec brc S e
(0) 0 NO AR | 1 NO AR usr OFF NONEIf we are working in the LAN network, the selection of the IP addresses of the application (PC with Setr) must also suit this network, for example:
IP adresa - 192.168.2.1 maska - 255.255.255.0
In the EPe menu we select the IP address in accordance with the LAN network:
Internet Protocol: Eid| ip address | net mask | gw | (0) C0A80205 192.168.2.5 FFFFFF00 255.255.255.0 00000000 0.0.0.0
5B. MAS configuration
Choose EPe 0ts. By selecting (s)Art in the
parameters we activate MAS, (B)ase and (M)ask
determine the area in which MORSE addresses of connected Setr´s can
be selected:
MAS: (s)Art:1; write (e)nable:ON (B)ase:690F5700 (M)ask:000000FF
Start setr in windows using the command:
setr -pIP192.168.2.5 -pm8000 -pw690F5701
where is:
-pIP192.168.2.5 ... IP address of CU
-pm8000 ... is the application port number, decimal
-pw690F5701 ... is the MORSE address, under which the PC with Setr
will be known in the MORSE networkOther Setr may also be started at the same time on other PCs, however it is necessary that they all use a different MORSE address. After starting Setr we can look at how the Art table was automatically filled, here 2 Setr were started:
ART No 1: items: 2 default gw: 00000000 (0.0.0.0 ) dest: gw: 690F5702 1F40020C (105.15.87.2 31.64.2.12 ) 690F5701 1F400201 (105.15.87.1 31.64.2.1 )
6. Packet transfer to the MORSE network
Routing, which ensures the sending of packets for the PC (here 690F57xx) to the MR400 address (here 690F5600), must be set in the destination CU. In the CU 690F5609 it is table wide:
690F5609h> Wide retab. No 1 57to:5600
Connection example and the RFC monitoring in CU 690F5600:
690F5609h>! 690F5609h> u E00 690F5600 R01 29/ 65 690F5609 serd serd 690F5609 R01 28/ 64 690F5600 u E00 690F5609h> Monitoring: source 690F5600|1. RF mon |toa frm |dst src |lNo!DQ!RSS size|TT N 15:37:23.058|690F5609 690F5600|690F5609 690F5701|012 RFTX 10 98 1dat 15:37:23.105|690F5600 690F5609| |012*29~ 64 0*06 ack 15:37:23.155|690F5600 690F5609|690F5701 690F5609|012*28* 64 26*9A 1dat 15:37:23.155|690F5609 690F5600| |012 RFTX 0 06 ack
In the remote CU 690F5609 we can set the Async link protocol and
direct it to the address of our application. The two lower bytes of IP
application address, here 5701, are set in the protocol parameter. The 16
bit mask is set by the command SIe 2um16. Start monitoring of
the port with Async link in the remote CU, route it to the address of our
application.
Test the connection from Windows to the remote Async link. Use the
function mtU for creating the necessary IP test frame. It
sends the AAAA characters to the address choosen by command
!h690F5609.
690F5609h>mtU Send type :09 690F5609h> 07:53:31.393 tx 2 | S02 AAAA
Test the connection from the remote link to the application:
690F5609>in ... use the function Channel data send 690F5609>dc ... choose the data input in SCC2 690F5609>ah0123456789ABCDEF ... insert some data (here hex) 690F5609>s ... start
690F5609h>O.K. 690F5609h>SETR: Packet type 09. 690F5701 690F5609 0889 8 0123 4567 89AB CDEF ... application Setr received and printed the data 08:01:48.087 rxsim 8 | S02 0123 4567 89AB CDEF ... monitoring input of data to the remote CU
| Note |
|---|---|
This is the connection with the Async. link in the remote CU. There may be a lot of CUs connected via MORSE network in this way and each can use a different protocol if necessary. Their data is then processed by the central application AAA connected through MAS, which distinguishes protocols best according to the respective MORSE addresses. This system integration is thus already contained in the MORSE system. |
UDP packet
If we want to view the format of the UDP packet we can start Setr
with the parameter -mh and Setr will print data in the UDP datagrams. It
is a good idea to switch off remote monitoring for this activity so that
Setr does not monitor monitoring packets. On the contrary local monitoring
in the CU, which contains MAS is switched on here. Again function
mtu, which generates 4 characters AAAA in the Setr application is
used:
690F5609h>mtU Send type :09 07:39:18.437 tx 10 to:192.168.2.5, 8888 0000 8982 690F 5609 AAAA
… application Setr is started with parameter -mh. It sends a UDP datagram containing the MORSE pseudoframe 0000 8986 690F 5609 AAAA with destination MORSE address and data AAAA to IP address 192.168.2.5 and to port 8888.
08:39:30.663 rsi:52 rx|0002A94B108E |00C09F63CFAB | IP/UDP/MOR/USR/DATA 0002 A94B 108E 00C0 9F63 CFAB 0800 4500 0026 00F2 0000 8011 B47E C0A8 0201 C0A8 0205 1F40 22B8 0012 4535 0000 8982 690F 5609 AAAA
… monitoring of the datagram entering the Ethernet channel contains, amongst others:
source IP address C0A8 0201 destination IP address C0A8 0205 source port 1F40 hex = 8000 dec destination port 22B8 hex = 8888 dec MORSE pseudoframe 0000 8982 690F 5609 AAAA
RF mon |toa frm |dst src |lNo!DQ!RSS size|TT N 08:39:30.664|690F5609 690F5600|690F5609 690F5701|036 RFTX 2 89 2dat AAAA
… monitoring of data sent through the MORSE radio channel
Monitoring through MAS
When routing monitoring from the remote CU to the Setr connected
through MAS it is necessary to insert the MORSE address of the PC with
Setr into the ise menu. In the above example of the single
application (A) it was address 690F5600, in the case of (B) it is, for
example, address 690F5701. Use option L to insert it into the
remote CU:
690F5609>
ise 0N1
0aL (type 'L' for local address)The resulting menu ise contains the PC destination address (MORSE):
690F5609h> System channels: (Service 'iMo' works for s0 and s1 only) id|--Node--addr------timeout---size---s(e)c-- (0) 1 690F5701 888 400 ON (1) 0 00000000 888 400 ON (2) 0 00000000 888 400 ON (3) 0 00000000 888 400 ON (4) 0 00000000 888 400 ON (5) 0 00000000 888 400 ON
We then route monitoring to system channel 0.
7. Running the application
Using Setr switch off remote and local monitoring, switch off Setr, start application AAA and now only observe how everything operates. The application runs on UDP port 8000 and communicates against UDP port 8888, which is used by the CU. The format of data is described in another document (Format of UDP datagram IPGW for MORSE).
SUMMARY
Brief summary of the steps described above for connecting the application through the MORSE Application Server (MAS):
| 1. | IP address in PC: IP address - 10.0.0.1
mask - 255.255.255.0IP and MORSE address in CU: EPe 0i0A000002 ... i.e. 10.0.0.2
0nFFFFFF00 ... i.e. 255.255.255.0
Ne 1a690F5600 ... MORSE address |
| 2. | Ping from PC to CU: ping 10.0.0.2 |
| 3. | setr -pIP10.0.0.2 ping from CU to PC: EPe 0tP t0A000001 s e p |
| 4A. | Connection through MAS with one address: Ne 1uE0
1sE0
EIe f |
| 5A. | Setting MAS: EPe 0t s1
B690F5600
M00000000
setr -pIP10.0.0.2 -pm8000 -pw690F5600Content of Art: dest: gw:
690F5600 1F400001 (105.15.86.0 31.64.0.1 ) |
| 4B. | More addresses, connection of Setr through LAN: Ne 1a690F5600
1MLn
1uE0
1sE0
1w1
Tw1
57to:5600
EIef
EPe 0 iC0A80205
nFFFFFF00 |
| 5B. | Setting MAS: EPe 0 t
s1
B690F5700
M000000FF
setr -pIP192.168.2.5 -pm8000 -pw690F5701Content of Art: dest: gw:
690F5702 1F40020C (105.15.87.2 31.64.2.12 )
690F5701 1F400201 (105.15.87.1 31.64.2.1 ) |
| 6. | Packet transfer through the net: destination CU 690F5609: Tw1
57to:5600
u E00 690F5600 R01
30/ 70 690F5609 serd
serd 690F5609 R01
29/ 68 690F5600 u E00Test connection from Setr through MAS to the remote async link: 690F5609h>mtU Send type :09 690F5609h> 07:53:31.393 tx 2 | S02 AAAA |