RAD-Galaxy User’s Guide
67
© 2016 Intrepid Control Systems, Inc.
Version 1.2 - November 28, 2017
Now we will repeat this same basic process for the server response on channel 2.
15. Select RAD-Galaxy Channel 2 Network:
Select “OP (BR) ETH02” from the
on
Network
drop-down box.
16. Create a Receive Message:
To the right of the drop-down box click the button.
17. Rename the Message:
Double-click the default message name and change it to
“Server Response”.
18. Change the EtherType and Protocol:
Check the
EtherType
setting from “Raw” to
“IPv4”. Then change the
Protocol
field from “Raw” to “UDP”.
We want to define the Server Response message so that it will decode any reply from the
server’s address and port. So we will use the IP address and port that the server node is using
for the
Source
fields, but set the
Destination
fields to wildcards.
19. Change the Source and Destination Address and Port Fields:
Change
Source
to
“10.0.0.2”,
Source Port
to “60002”,
Destination
to “X.X.X.X”, and
Destination Port
to
blank (delete the “60002” value in the field).
20. Add a Signal:
Click the arrow next to the
button and select “Add 16 Bit Signal”.
21. Rename the Signal:
Rename signal to “Response Value”.
The server receive message is now done. Let’s take a look at the results of our message
definitions.
22. Switch to Messages View.
23. Go Online.
The result will be a display similar to Figure 73. Notice how the decoding allows us to more
clearly see the client/server nature of the exchange.
The server only transmits when it is responds to client requests it receives. The fact that this
continues to happen with the RAD-Galaxy tap in place demonstrates that messages are still
being sent between the two nodes even as they are copied over to Vehicle Spy.
24.
Go Offline.
