Skip to content

Sungrow

Supported models
  • Logger1000
  • Logger1000A/B
  • Logger3000
  • Logger3000B
  • Logger4000
  • COM100A
  • COM100D/E
  • WiNet-S
  • SG10KTL
  • SG10KTL
  • SG12KTL
  • SG15KTL
  • SG20KTL
  • SG30KU
  • SG36KTL
  • SG36KU
  • SG40KTL
  • SG40KTL-M
  • SG50KTL-M
  • SG60KTL-M
  • SG60KU
  • SG30KTL-M
  • SG30KTL-M-V31
  • SG33KTL-M
  • SG36KTL-M
  • SG33K3J
  • SG49K5J
  • SG34KJ
  • LP_P34KSG
  • SG50KTL-M-20
  • SG60KTL
  • SG80KTL
  • SG80KTL-20
  • SG60KU-M
  • SG5KTL-MT
  • SG6KTL-MT
  • SG8KTL-M
  • SG10KTL-M
  • SG10KTL-MT
  • SG12KTL-M
  • SG15KTL-M
  • SG17KTL-M
  • SG20KTL-M
  • SG80KTL-M
  • SG111HV
  • SG125HV
  • SG125HV-20
  • SG30CX
  • SG33CX
  • SG36CX-US
  • SG40CX
  • SG50CX
  • SG60CX-US
  • SG49.5CX-JP
  • SG110CX
  • SG250HX
  • SG250HX-US
  • SG100CX
  • SG100CX-JP
  • SG250HX-IN
  • SG25CX-SA
  • SG75CX
  • SG3.0RT
  • SG4.0RT
  • SG5.0RT
  • SG6.0RT
  • SG7.0RT
  • SG8.0RT
  • SG12RT
  • SG15RT
  • SG17RT
  • SG20RT
  • SG5.5RS-JP
  • SG125HX-JP
  • SG320HX
  • SG350HX
  • SG125CX-P2
  • SG25CX-P2
  • SG30CX-P2
  • SG33CX-P2
  • SG36CX-P2
  • SG40CX-P2
  • SG50CX-P2

Modbus TCP over ethernet

  1. Connect the ethernet cable between the ETH1 port of the Teleport and the LAN port of the Sungrow Logger. If the LAN port of the logger is already occupied (e.g. connected to a router), navigate to our appendix for instructions on how to integrate with a router.

  2. Log in to the Logger web UI as explained in the commissioning process and go to System and then choose Port Parameter.

    1. If no router is present, go to Ethernet and set the Automatically obtain IP settings (DHCP) parameter to Close. Configure the following settings, with values as described in Static IPs for a direct asset connection.

      • IP Address
      • Subnet Mask
      • Gateway
    2. Go to Power Control and select Active Power to enter the active power interface. Set the Active Control Mode to Remote Power Control and verify these settings:

      • Control Method: Open-loop Control
      • Query recovery time(0~60)s: 0
      • Frame delay (4~70)ms: 18
      • Target Value Filter: Identical Values
      • Filter Time(0~60)s: 0
      • Northbound Communication Abnormal Protection: Modbus-TCP/IEC104
    3. To enable optional fallback configuration, available on the Logger1000 and Logger3000 models, configure the following settings.

      For the Logger1000 this can be found under the System, Transfer Configuration, menu in the Modbus, Server, Communication Interrupted Protection tab. For the Logger3000 this can be found under Power Control, Active Power menu.

      • Protection switch: Enable
      • Peer IP Address: IP address of the Teleport
      • Port: 502
      • Communication Error Tripping Time(s): 60
      • Communication Abnormality Output (%): Target Percentage (the fallback value set on the inverters when a connection between the Teleport and the Logger is lost)
      • Communication Error Auto Recovery Times(s): 5
      • Communication Output Recovered: Boot
      • Maximum Output Trigger Switch: Disable
    4. Click save

Detection of faulty inverters

Teleport can detect faulty inverters behind the Sungrow Logger. In order to unlock this functionality, the Forwarding Modbus IDs of the inverters must be configured. The Forwarding Modbus IDs can be found as follows:

  1. Log in to the Logger web UI

  2. Navigate to Devices and select Device List

  3. Note and share the Forwarding Modbus ID for each inverter