Zennio Linecoupler
Technical Support:
http://zennioenglish.zendesk.com
8
Note
:
the individual address of a line coupler needs to be of the form
X.Y.0
(or
X.0.0
in
the case of working as a backbone coupler)
.
Regarding telegram filtering, the line coupler implements two complementary (and
optional) filters:
Group address filtering
: ETS automatically generates a group address table
for the project loaded. This table is transferred to the line coupler during
complete downloads. When a telegram containing a group address in the
“destination address” field arrives, the line coupler will look up if such address
exists in the group table, and eventually transmit the telegram to the other
side –if the address is found–or drop (block) it –if it is not–.
Note
:
making further changes to a project (addresses, etc.) requires
downloading the updated filter table to the line coupler
.
Example
:
if the line coupler has been parameterised to filter group
addresses from both lines, when it receives a telegram from the
mainline destined to a group address (e.g., 2/5/13) it will check that
there is a device in the sub-line with objects that have been assigned
such group address (or that such address has at least been marked in
ETS to pass through the line coupler; see Figure 5). If so, then the line
coupler will let it pass. Otherwise, it won’t be transferred to the sub-line.
The same would also apply to the inverse case (a telegram originating
in the sub-line).
Figure 5
ETS Option to Force Passing a Group Address through the Line Coupler
