Broadcast Messages; Transport Protocols - Siemens RUGGEDCOM ROS User Manual

Hide thumbs Also See for RUGGEDCOM ROS:
Table of Contents

Advertisement

Chapter 5
Setup and Configuration
Section 5.4.3.5

Broadcast Messages

DNP Broadcast Messages
Addresses 65521 through 65535 are DNP 3.0 broadcast addresses. ROS supports broadcasts sending messages
with those destination addresses received from serial ports to all IP Addresses found in the Device Address Table
(either learned or statically configured). When a DNP broadcast message is received from the IP network, it will be
distributed to all ports configured to support the DNP protocol.
TIN Broadcast Messages
TIN broadcast messages can be received only from devices connected to the serial ports.
TIN Mode 1 Broadcast Messages
These messages will be sent to all TIN Address/Ports found in the Dynamic Address Table.
TIN Mode 2 Broadcast Messages
These messages will be sent according to the configuration: to all TIN addresses on every IP address found in the
Dynamic Address Table and/or to all Wayside Data Radio IP addresses found in the Static Device Address Table.
Section 5.4.3.6

Transport Protocols

For supported protocols, with exception of Modbus, either UDP datagram or TCP connection packets can be used
to transport protocol data over the IP network. The Modbus data can be transported only using TCP connection,
following Modbus TCP protocol. UDP supports all the addressing modes of IP – unicast, multicast and broadcast.
Therefore, if address learning is enabled, UDP broadcasts will be sent across the network.
Transport for Raw Socket
The TCP transport for RawSocket requires configuration of connection request direction, remote IP address, and
IP port for listening or requesting outgoing TCP connections. Only one outgoing connection can be requested,
but up to 64 connections can be accepted if the port is configured to listen to incoming connection requests. For
ports configured to request connections and to listen to incoming connection requests, only one connection can
become active.
ROS will attempt to connect periodically if the first attempt fails and after a connection is broken.
ROS can be used to connect to any device supporting TCP (e.g. a host computer's TCP stack or a serial application
on a host using port redirection software).
If Raw Socket ports are configured to use UDP for transport, up to 64 remote hosts can communicate with
devices connected to local serial ports. Data in UDP packets from remote hosts configured to communicate with
a particular serial port will be forwarded to that port, as long as the serial port is configured to listen on the UDP
port to which the remote hosts are transmitting. Data received from the serial port will be forwarded to all remote
hosts configured to communicate with that serial port.
138
RUGGEDCOM ROS
User Guide
Broadcast Messages

Advertisement

Table of Contents
loading

Table of Contents