Skip to main content
Skip table of contents

Networking Discover Lithium Batteries with LYNK II

NOTE

  • Turn OFF all devices before connecting cables.

  • Do not plug an AEbus RJ45 network cable or terminator into the 10/100 Ethernet port of the LYNK II.

  • Do not connect a CAT5 or higher cable from the LYNK port of the LYNK II to a WAN or MODEM port of a network router.

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

NOTE

Unless specified by Discover Energy Systems, power electronics must not be connected directly to the LYNK network.

Refer to the LYNK II Installation and Operation Manual (805-0033) for detailed instructions on network layouts, connections, and terminations for compatible Discover Lithium battery models. Some key reminders are provided in this manual.

  • At least one battery must be connected to the LYNK Port on LYNK II.

  • A network of batteries will communicate as one battery.

  • No more than one network of batteries may be connected to LYNK II.

  • LYNK II requires power. There are three possible sources: a 13-90 Vdc power supply, LYNK Port-enabled Discover Lithium battery, or a USB device.

  • Discover Lithium batteries must be set to ON to supply power and communicate data with LYNK II.

AES RACKMOUNT

image-20250422-212617.png

Both LYNK II and AES RACKMOUNT Battery Modules are internally terminated. No extra termination is required.

HELIOS ESS

image-20250422-212748.png

Both LYNK II and HELIOS batteries are internally terminated. No extra termination is required.

NOTICE

TERMINATION REQUIREMENT

HELIOS ESS Batteries prior to serial number DLPHD48B251080001 are supplied with a termination resistor. When setting up closed-loop communication with these HELIOS ESS Batteries, plug the termination resistor into the COM3/COM4 port on the last battery in the LYNK network.

Failure to follow these instructions may result in equipment damage.

JavaScript errors detected

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

If this problem persists, please contact our support.