Are three DC input groups three MPPTs?

No. The Eco 100 technical table specifies one MPP controller. Its D-variant input groups have their own current and fuse limits, but they are not three independently tracked arrays.

Does TCP monitoring require enabling inverter control?

The interface and inverter-control settings are separate in the operating instructions. Keep the control option and existing control priorities unchanged for a monitoring-only connection.

Can I use the meter endpoint for inverter production?

No. The manual fixes the inverter TCP identity at 1 and separately shows meter identity 200 by default. Verify which device and measurement location a value represents.

Can float and integer maps share the same offsets?

No. Select the decoder using the actual discovered SunSpec model. Preserve the commissioned representation so existing clients keep using their intended map.

Fronius Tauro Eco 100-3-D Modbus setup

Compatibility

Compatible through Modbus TCP

The manufacturer documents a local SunSpec Modbus interface. Discover the installed model list and verify the exact inverter identity before selecting measurement offsets.

Fronius Tauro Eco 100-3-D, direct-string 100 kW variant on a 380/400 V three-phase grid. The current Tauro operating instructions cover its local Modbus interface. Eco 100-3-P pre-combined inputs, Eco 99 and Tauro 50 are separate variants. No minimum firmware version is established by the retained interface instructions; record the installed version and discovered SunSpec models.

Connect it with

Gateway ZGW-20
From €899 ex VAT Configure Gateway

For read-only measurements from the individual inverter

Modbus
Edge
Platforms

Read the inverter directly using the configured network endpoint. Preserve any existing logger or plant controller; this monitoring path does not take ownership of dispatch, protection or grid settings. The customer-platform output is optional; Edge remains the local system of record.

Models

Download

Models	Interface	Route into Edge
Eco 100-3-D	100 kW, direct-string, one MPPT	Use the exact D-variant manual and discovered SunSpec models.
Eco 100-3-P	Pre-combined DC inputs	Different input limits and array topology; not the direct-string variant.
Tauro 50 / Eco 99	Different rating and PV topology	Do not substitute their technical tables for Eco 100-3-D.

Specifications

Each Tauro needs its own direct LAN connection to use Modbus TCP. The communication settings expose the selected SunSpec model type, the configured TCP port and distinct inverter and meter identities. The inverter endpoint uses unit ID 1, while the attached meter is separate. Reading the inverter therefore does not automatically give the site’s import, export or net consumption; those require the correct meter endpoint and measurement location.¹

Exact variant: Tauro Eco 100-3-D; direct string connection, 100 kW AC¹
PV topology: One MPP controller; three DC input groups do not mean three independent MPPTs¹
PV limits: 1000 V maximum DC; 580–930 V MPP range; 150 kWp maximum total PV field power¹
Grid: Three-phase 380/220 V or 400/230 V; regional grid settings remain installer-controlled¹
Connection: Direct LAN connection for each inverter; use the configured Modbus TCP port¹
Inverter identity: TCP inverter unit ID fixed at 1; meter default 200 is a different endpoint¹
SunSpec selection: float or int + SF changes the measurement model; discover before decoding¹
Environment: IP65; -40 to +65 °C, or -30 to +65 °C with the built-in AC disconnector option¹

Interface

Documented measurements and integration boundaries for Tauro Eco 100-3-D.

Inverter AC power, voltage and current from supported SunSpec measurement models.
Generation energy and operating state where implemented by the installed firmware.
Common-model identity used to bind the point schedule to the exact inverter.

Assessment

Fronius Tauro Eco 100-3-D, direct-string 100 kW variant on a 380/400 V three-phase grid. The current Tauro operating instructions cover its local Modbus interface. Eco 100-3-P pre-combined inputs, Eco 99 and Tauro 50 are separate variants. No minimum firmware version is established by the retained interface instructions; record the installed version and discovered SunSpec models.

InteroperabilitySupported with conditions: The exact model documentation establishes the local interface and identity checks. The installed configuration and existing site controller must be preserved.¹
AccuracySupported with conditions: The measurement representation and units are documented, but inverter telemetry does not establish revenue-meter accuracy.¹
SecurityNot yet assessed: The proposed local monitoring path does not establish authenticated or encrypted measurements. Restrict access to the approved site network.¹
ReliabilityNot yet assessed: No measured availability or guaranteed historical backfill is established for this direct monitoring connection.¹
RuggednessSupported with conditions: The exact manual specifies the enclosure rating and temperature limits, with option or derating conditions that must be retained.¹
ScalabilitySupported with conditions: Each Tauro requires its own direct LAN endpoint and identity. Preserve the existing representation and control configuration.¹
LifecycleNot yet assessed: Versioned documentation is available, but a guaranteed support term or replacement lifetime is not established by the retained sources.¹

Setup

Verify the SunSpec map before selecting power

This synthetic discovery example explains the wire request and model traversal. It does not claim a fixed power address for every Tauro firmware.

Endpoint: Use the configured TCP port and inverter unit ID 1. The meter endpoint is separate.
Signature request: FC03 PDU 03 9C 40 00 02 reads wire address 40000, quantity 2. SunSpec also defines alternate bases 0 and 50000; continue only at the base returning the signature.
Synthetic signature: 53 75 6E 53 spells SunS. A successful TCP connection alone does not prove the intended map.
Synthetic header: 00 01 00 42 means common model 1 with 66 following data registers. At wire header 40002, the next model begins at 40002 + 2 + 66 = 40070.
Representation check: 00 67 means model 103; 00 71 means model 113. Their layouts differ. Use the model actually returned, not the synthetic header as a fixed layout.

Acceptance: Accept only after the common identity matches this Tauro and the measurement model, unit and live reference agree. No dispatch or control write is part of this check.

Confirm the direct-string variant
Fronius Tauro Eco 100-3-D, direct-string 100 kW variant on a 380/400 V three-phase grid. The current Tauro operating instructions cover its local Modbus interface. Eco 100-3-P pre-combined inputs, Eco 99 and Tauro 50 are separate variants. No minimum firmware version is established by the retained interface instructions; record the installed version and discovered SunSpec models.
Keep the existing controls intact
Record the site controller and current inverter settings before adding a reader. Do not change feed-in limits, I/O priorities, power control or protection. The dedicated inverter-control option is separate from the TCP server configuration; do not enable control for this read-only procedure.
Connect to the individual inverter
Use the inverter’s direct LAN endpoint, configured TCP port and fixed inverter unit ID 1. The default meter identity 200 refers to a different device. Do not treat an RS-485 connector or the inverter’s downstream control wiring as an Ethernet monitoring path.
Record the SunSpec representation
The manual offers float and int + SF model types. Preserve the commissioned choice; changing it can invalidate another client’s point map. Discover the signature and model headers, then select only models actually returned by this inverter.
Verify identity before a measurement
Read the common model and compare manufacturer, model, serial number and firmware with the inverter. Traverse each model using its own length and stop at the end marker. Do not paste fixed power-register addresses from GEN24, Datamanager or a different Tauro setup.
Compare a correctly decoded read
Use the discovered model’s data type and units. Integer models require their associated signed scale factor; floating-point models require the corresponding complete float value. Keep unavailable values separate from zero and compare with the inverter’s live display before adding further points.

Common questions

Are three DC input groups three MPPTs?: No. The Eco 100 technical table specifies one MPP controller. Its D-variant input groups have their own current and fuse limits, but they are not three independently tracked arrays.¹
Does TCP monitoring require enabling inverter control?: The interface and inverter-control settings are separate in the operating instructions. Keep the control option and existing control priorities unchanged for a monitoring-only connection.¹
Can I use the meter endpoint for inverter production?: No. The manual fixes the inverter TCP identity at 1 and separately shows meter identity 200 by default. Verify which device and measurement location a value represents.¹
Can float and integer maps share the same offsets?: No. Select the decoder using the actual discovered SunSpec model. Preserve the commissioned representation so existing clients keep using their intended map.^1, 2

Related devices

Sources

Fronius Tauro and Tauro Eco operating instructions (opens in a new tab) Fronius
SunSpec Device Information Model Specification 1.1 (opens in a new tab) (PDF) SunSpec Alliance

Cookie	Kept for	What it does
`_ga`	13 months	Tells one browser apart from another across visits
`_ga_<id>`	13 months	Keeps the current visit together
`_clck`	1 year	Tells one browser apart from another across visits
`_clsk`	1 day	Joins the pages of one visit into one recording
`MUID`	1 year	Set by Microsoft on clarity.ms to recognise the browser

Cookie	Kept for	What it does
`li_fat_id`	30 days	Links a visit to the LinkedIn advert click that led to it
`bcookie`	1 year	Set by LinkedIn on linkedin.com to recognise the browser
`lidc`	1 day	Set by LinkedIn on linkedin.com to route requests
`UserMatchHistory`	30 days	Set by LinkedIn on linkedin.com to match visits for advertising
`AnalyticsSyncHistory`	30 days	Set by LinkedIn on linkedin.com to record when it last matched visits