Skip to main content
Skip table of contents

LYNK Network Communication Cables

LYNK Network Communication Cables

NOTICE

EQUIPMENT DAMAGE

  • Do not connect a cable from an AEbus Port or LYNK Port to a WAN or MODEM Ethernet port.

  • Turn OFF all devices before connecting cables.

  • Mixing the LYNK Network with other networks may result in equipment malfunction and damage.

Failure to follow these instructions may result in equipment damage.

Networking Guidelines

  • Separate data and power cables allow for separation between data and power cables. Avoid interference and data corruption caused by running network cables bundled with power cables.

  • Allow for LYNK Network cable slack. Ensure that LYNK Network cables are slack and not in tension.

  • Isolate the LYNK Network. Do not mix other networks with the LYNK Network.

NOTE

The LYNK II Communication Gateway is internally terminated. A termination resistor is not required.

LYNK Network Installation and Layout for AES Cabinets (SLL03C2-D1P52S1R4-A01, SLL03C2-D1P52S1R5-A01, SLL03C2-D1P52S1R6-A01, SLL03C2-D1P52S1R7-A01, SLL03C2-D1P52S1R8-A01)

Each battery cabinet requires at least one LYNK II Communication Gateway.

  • Using a CAT5e or higher cable, insert one end into the LYNK Port (RJ45) on the LYNK II. Insert the other end of the cable into either J3 or J4 (LYNK Ports) in the HV Box of the AES Cabinet.

1-PCS_1-Cabinet.png
  • If you are connecting two power conversion systems (PCS) to the AES Cabinet, connect one PCS to the LYNK II and to the J3 port on the AES Cabinet, and connect the other PCS to another LYNK II device (purchased separately) and to the J4 port.

2-PCS_1-Cabinet.png
  • If you are connecting one PCS to two AES Cabinets, connect the PCS to the LYNK II and to either the J3 or J4 port of the first AES Cabinet, then connect the J3/J4 port of the second AES Cabinet to the open J3/J4 port of the first AES Cabinet.

1-PCS_2-Cabinet.png
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.