User's Manual

Table Of Contents

The Bridge functionality is not affected, i.e. only frames whose recipients belong to the local LAN

are transmitted from the ETH interface.

It is possible to use more than one Repeater within a network. To eliminate the risk of creating a

loop, the “Number of repeaters” has to be set in all units in the network, including the Repeater units

themselves.

Warning: Should Repeater mode be enabled “Modulation rate” and “FEC” must be set to the same

value throughout the whole network to prevent frame collisions occurring.

• No of repeaters

Number {0 – 7}, default = 0

If there is a repeater (or more of them) in the network, the total number of repeaters within the network

MUST be set in all units in the network, including the Repeater units themselves. After transmitting

to or receiving from the Radio channel, further transmission (from this RipEX2) is blocked for a

period calculated to prevent collision with a frame transmitted by a Repeater. Furthermore, a copy

of every frame transmitted to or received from the Radio channel is stored (for a period). Whenever

a duplicate of a stored frame is received, it is discarded to avoid possible looping. These measures

are not taken when the parameter “Number of repeaters” is zero, i.e. in a network without repeaters.

• Tx delay [B]

Number {0 – 1600}, default = 0

This parameter should be used when all substations (RTU) reply to a broadcast query from the

master station. In such case massive collisions would ensue because all substations (RTU) would

reply at nearly the same time. To prevent such collision, TX delay should be set individually in each

slave RipEX2. The length of responding frame, the length of Radio protocol overhead, modulation

rate have to be taken into account.

7.1.2.3. Base driven protocol (Router mode)

Router mode with Base driven protocol (BDP) is suitable for a star network topology with up to 256

Remotes under one Base station. Each Remote can work as a Repeater for one or more additional

Remotes. This protocol is optimized for TCP/IP traffic and/or ‘hidden’ Remotes in report-by-exception

networks, when a Remote is not be heard by other Remotes and/or different Rx and Tx frequencies

are used.

Frame acknowledgement, retransmissions and CRC check guarantee data delivery and integrity even

under harsh interference conditions on the Radio channel.

Note

There is no need to set any routes in Routing table(s) for Remote stations located behind Re-

peater. Forwarding of frames from the Base station over the Repeater in either direction is

serviced transparently by the Base driven protocol.

Note

When Remote to Remote communication is required, respective routes via Base station have

to be set in Routing tables in Remotes.

Settings