Allocation schematic from spring terminal to Easy2Install interface |
31
Allocation schematic from spring terminal to Easy2Install interface
For mixed data cabling connections using E2I interfaces as well as spring terminals within one group installation, the
below allocation schematic must be followed. For each length of cable between these two interface systems, one un-
braided RJ45 to individual strand Ethernet/patch cable (1 pc) is required.
The following allocations are then made:
Controller/Extender with spring terminal to Extender with Easy2Install interface
In this configuration, the individual wire strands of an Ethernet cable (CAT5e or above), which has been unbraided
at one end, are connected to one of the spring terminals (
R
) of the Controller or Extender charging station, while
the RJ45 plug of the Ethernet cable is inserted into the left hand side Easy2Install interface of the next Extender
charging station.
Controller/Extender with Easy2Install interface to Extender with spring terminal
In this configuration, the RJ45 plug of the Ethernet cable is inserted into the right hand side Easy2Install interface
of the Controller or Extender charging station, while the unbraided wire strands of the Ethernet cable are connect-
ed to the other spring terminal (
L
) of the next Extender charging station.
In both cases, the individual wire strands of the Ethernet cable must be allocated as illustrated below.
Spring terminal
Energy meter
RJ45 plug
Top view of
terminal
ABL bus
allocation
Connection
terminal
PIN allocation
Top view of RJ45 plug
8
1
1
2
3
4
5
6
7
8
B M A
METER
B M A
CONTROL
CONTROL A
–
1
8
1
1
2
3
4
5
6
7
8
B M A
METER
B M A
CONTROL
CONTROL M
–
3 & 6
CONTROL B
–
2
METER A
(
7
METER M
)
4 & 5
METER B
&
8
WARNING!
Identical allocation of wire strands
Please note:
As no standard exists for the allocation of wire strands colours to the contacts of an RJ45 plug, the above
illustration only shows the allocation of the RJ45 contact to the spring terminal contact.
These allocations must be followed consistently, otherwise faultless communication within the system is
impossible.
Trademarks
All trademarks mentioned in this manual, including those that may be protected by third parties are, without restric-
tion, subject to the regulations of the respectively applicable trademark law and the property rights of the respective
registered owners. All trademarks, trading names or company names marked here as such are, or may be, trademarks
or registered trademarks of their respective owners. All rights not explicitly granted here are reserved.
The absence of explicit identification of trademarks used in this manual must not lead to the conclusion that a name
is free from the rights of third parties.
