FIMER PVS-100/120-TL

Commercial PV inverter

FIMER documents SunSpec Modbus RTU and TCP for PVS-100/120-TL. Use the exact rating and wiring-box suffix because AC voltage, MPPT count and string monitoring differ. This guide is read-only. Plant control, protection and grid settings stay with the commissioned system.

  • Modbus TCP
  • Modbus RTU
  • SunSpec Modbus

Commercial PV inverter

Compatibility

Compatible through documented SunSpec Modbus

The exact-family product manual documents SunSpec-compliant Modbus RTU and TCP, and FIMER publishes a PICS workbook for the PVS-100/120-TL.

PVS-100-TL and PVS-120-TL only, with the full model suffix, firmware and commissioned interface recorded. Read monitoring data only. Do not change active-power, reactive-power, protection or grid settings.

Connect it with

Route into Edge

For a permitted read-only connection on the inverter LAN

  • Modbus
  • Edge
  • Platforms
Commercial PV inverter
Interface
Gateway
Edge
Output
PVS-100/120-TLPVS-100/120-TL Ethernet port
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Modbus TCP client
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Poll only the SunSpec models returned by the installed inverter. Preserve any existing plant controller and the configured network topology. The customer-platform output is optional; Edge remains the local system of record.

When the commissioned RS-485 interface is available for a read-only client

  • Modbus
  • Edge
  • Platforms
Commercial PV inverter
Interface
Gateway
Edge
Output
PVS-100/120-TLPVS-100/120-TL RS-485 port
Isolated serial interfaceApproved RS-485-to-host adapter
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Modbus RTU client
Customer platformMQTT · API · files
Modbus RTU · RS-485
Isolated serial
Runs locally
Optional onward data
Confirm the inverter is configured as a Modbus slave and record its address, baud rate, parity and bus termination before polling. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
PVS-100-TL100 kW at 400 Vac; 2 MPPT or 6 MPPT by suffixUse the installed suffix and discovered SunSpec models.
PVS-120-TL120 kW at 480 Vac; 2 MPPT or 6 MPPT by suffixDo not reuse the PVS-100 electrical limits.
SX, SX2, SY and SY2 wiring boxesSix MPPT variants with differing string-input equipmentRecord the full nameplate before assigning points.

Specifications

PVS-100-TL is rated 100 kW at 400 Vac and PVS-120-TL is rated 120 kW at 480 Vac. The product family has two- and six-MPPT wiring-box variants, so the family name alone is insufficient for array or point design.13

Ratings
PVS-100-TL: 100 kW at 400 Vac; PVS-120-TL: 120 kW at 480 Vac3
PV input
1000 V maximum DC; two or six MPPT depending on the wiring-box suffix13
Interfaces
One RS-485 port, two Ethernet ports and WLAN service access1
Protocol
SunSpec-compliant Modbus RTU and Modbus TCP12
Enclosure
IP663

Interface

Documented measurements and integration boundaries for PVS-100/120-TL.

  • Inverter identity and firmware from the implemented SunSpec common model.
  • AC power, voltage, current, frequency and energy where returned by the installed SunSpec model set.
  • DC power and operating state where the installed variant and firmware expose them.

Assessment

Exact PVS-100/120-TL suffix and firmware, using documented SunSpec Modbus only.

InteroperabilitySupported with conditions
Exact-family SunSpec RTU and TCP plus a PICS are published; model and firmware discovery remain required.12
AccuracySupported with conditions
Electrical measurements and identity models are documented, while available points depend on the installed suffix and firmware.12
SecurityLimited
The local Modbus paths do not provide transport encryption or peer authentication, so network isolation and read-only enforcement are required.1
ReliabilitySupported with conditions
Environmental limits and communications hardware are published; polling recovery and coexistence need site testing.13
RuggednessSupported with conditions
IP66 and installation limits are published for the family, subject to the exact variant and installation method.3
ScalabilitySupported with conditions
Ethernet daisy-chain and addressed serial operation are documented, but client roles and segment loading need an engineered site plan.1
LifecycleSupported with conditions
FIMER publishes an exact-family manual, datasheet and PICS with revisions; deployed firmware and retained configuration still need recording.123

Setup

Read three-phase inverter power

Use FIMER’s PVS-100/120 PICS Rev 005 as a best-effort starting map. Its model 103 describes signed AC power and a separate scale factor. Discover the installed model headers once, then compare the first reading with the inverter’s own monitoring.

Connection and identity
Use the commissioned TCP endpoint/unit ID or RS-485 slave address and framing. Read FC03 at wire address 40000, quantity 2: PDU 03 9C 40 00 02. SunS is 53 75 6E 53. Read common model 1 at 40002 to check manufacturer, model, version and serial. All addresses here are zero-based PDU addresses; translate any one-based client display before sending requests.
Locate model 103
Read two-register headers: model ID and data length L. Next header = current header + L + 2; stop at ID 65535. Rev 005 places model 103 at H = 40070 with L = 50, after common model 1. Confirm that header on the device. If H differs, use discovered H rather than retaining the workbook’s absolute addresses.
Read power and scale together
W is signed S16 at H+14; W_SF is signed sunssf at H+15. For the published H = 40070, read wire 40084, quantity 2: PDU 03 9C 94 00 02. The first returned word is power, the second its scale. Rev 005 declares both read-only and W_SF = 1; read the live factor rather than hard-coding it.
Decode a synthetic response
AC power in W = signed raw × 10^W_SF. Synthetic data 27 10 00 01 gives raw 10000 and factor 1: 100000 W = 100 kW. FF 9C 00 01 gives -100 × 10 = -1000 W; preserve signed decoding. These bytes demonstrate the decoder, not measured production. Convert W to kW once, and compare timestamps and power with the inverter display or logger.
Check quality before expanding
For S16 and sunssf, 0x8000 means unavailable, not zero. If the signature, model ID/length or scale fails, check client address convention and selected interface first. Add voltage, current, frequency and energy using their own model-103 types and scale factors. Keep RTU Device Acquisition/master mode distinct from Modbus SunSpec Server/slave mode; do not replace an existing bus master.

Acceptance: The manufacturer map gives a concrete first AC power reading. Record the document revision once and verify discovery and values on site; power-control, protection and grid writes remain with the commissioned plant system.

  1. Identify the exact inverter

    Record PVS-100 or PVS-120, the complete wiring-box suffix, serial number and firmware. Confirm the site AC voltage and MPPT count against the nameplate.

  2. Preserve plant control

    Record the existing logger, plant controller and grid settings. Use a read-only client and do not enable or exercise power-control functions.

  3. Choose one documented interface

    For TCP, use a permitted protected LAN endpoint. For RTU, confirm slave mode, address, serial framing and termination without displacing the current bus master.

  4. Discover before decoding

    Read two-register headers: model ID and data length L. Next header = current header + L + 2; stop at ID 65535. Rev 005 places model 103 at H = 40070 with L = 50, after common model 1. Confirm that header on the device. If H differs, use discovered H rather than retaining the workbook’s absolute addresses.

  5. Validate measurements

    W is signed S16 at H+14; W_SF is signed sunssf at H+15. For the published H = 40070, read wire 40084, quantity 2: PDU 03 9C 94 00 02. The first returned word is power, the second its scale. Rev 005 declares both read-only and W_SF = 1; read the live factor rather than hard-coding it.

Common questions

Does every PVS-100/120-TL have six MPPTs?
No. FIMER publishes both two- and six-MPPT wiring-box variants. The complete suffix determines the input topology.13
Does this guide permit inverter control?
No. It covers read-only SunSpec monitoring. Active and reactive power commands, protection and grid settings remain outside this integration.1
Can an RS-485 connector alone justify an Edge path?
No. The path here is supported by the exact-family manual and PICS, and still requires the commissioned slave settings and an available bus role.12

Sources

  1. PVS-100/120-TL product manual, Rev G (opens in a new tab) (PDF) FIMER
  2. PVS-100/120 SunSpec PICS, Rev 005 (opens in a new tab) FIMER
  3. PVS-100/120-TL Datasheet, Rev D (opens in a new tab) (PDF) FIMER

Further reading

Product names and trademarks belong to their owners. Publication does not imply endorsement or a commercial relationship.