SMA Developer sert de lieu de stockage centralisé de toute la documentation relative aux interfaces utilisées dans les produits SMA. Par le biais de la documentation publiée ici, SMA mise en premier lieu sur des interfaces ouvertes et standardisées facilitant l’intégration de produits SMA dans les applications photovoltaïques les plus diverses.
SMA vous permet d’accéder facilement et confortablement à nos produits sans avoir à signer de déclaration de confidentialité supplémentaire (NDA). La plupart des documents peuvent être téléchargés gratuitement. Pour certains téléchargements, il vous faut d’abord vous enregistrer.
Intégration des onduleurs SMA
Les présentes informations mettent l’accent sur l’application de standards qui facilitent l’intégration des onduleurs. Le premier pas dans ce sens a été d’équiper les onduleurs d’une interface SMA Modbus® et d’une interface SunSpec® Modbus®. Ainsi, aucun composant supplémentaire n’est requis pour avoir directement accès aux données des appareils. Cela réduit considérablement les coûts de système pour vous et vos clients.
Pour la surveillance et la commande centralisées d’onduleurs string, la connexion des onduleurs SMA peut également avoir lieu via une interface SMA Modbus® standardisée et un appareil de communication supérieur.
Avec ces solutions, SMA offre entre autres un moyen universel de surveillance, une solution de commercialisation directe de l’énergie ainsi que des interfaces pour la consigne de puissance active et réactive.
En matière de gestion de l’énergie, SMA propose d’ores et déjà une solution. D’ici à ce que cette solution soit standardisée, vous pouvez déjà utiliser sans restriction le protocole d’échange de données existant SEMP (Simple Energy Management Protokoll) du Sunny Home Manager.
Ici, vous pouvez télécharger gratuitement nos documents de développement :
Pour accéder aux téléchargements suivants, vous devez vous enregistrer et accepter les conditions d’utilisation :
Interface protocole SEMP
Interface de compteur
pour SMA ENERGY METER
Source code example for integration of SMA Energy Meter
Interface SPEEDWIRE DEVICE DISCOVERY
Speedwire Device Discovery permet de détecter les appareils présents dans le réseau local.
pour tous les appareils SMA avec Speedwire ou Speedwire/Webconnect
Veuillez noter que, en dehors des informations fournies ici, nous ne pouvons pas proposer d’assistance supplémentaire pour l’intégration de nos produits.
Question:
Why is the Modbus interface reaction time defined as only five to ten seconds in the technical documentation?
Answer:
The reaction time given is based on the worst-case reaction time analysis. This is with the intention of providing a reliable estimate for customers to minimize planning risks.
However, the reaction time of the SMA Modbus interface depends on many factors and is normally significantly less.
Question:
How do I read the number of MPP trackers?
Answer:
The number of MPPs cannot be read directly. However, if values relating to DC voltage (30771, 30957, 30963) are available in the case of solar irradiation, the number of MPPs can be determined using them.
Question:
Why does Modbus crash after a few days?
Answer:
This is not a crash, but instead a reaction to when more than the maximum of four TCP/Modbus connections is made.
If an attempt is made to do so, the system waits for precisely two hours. Once this time has elapsed and an existing connection has been inactive for that period, this connection is removed from our inverter bridge.
The same applies to all devices making requests to Modbus that establish a Modbus/TCP connection to the inverter but are not removed properly under fault conditions, for example.
Because we do not have any appropriate criteria for this, the inverter or the data module installed in the inverter as a TCP server cannot actively terminate the connection.
Question:
Why do I receive a NaN instead of a value for some registers at night?
Answer:
SMA inverters are controlled by two processors:
a central processing unit (CPU; usually a DSP) for controlling the power electronics and measuring PV and grid variables, and a communications processor (CP; ARM or similar) for the outward-facing interfaces.
The following apply in this respect:
If the CPU is not active, “NaN” is shown for registers with CPU data. In most cases, this can be interpreted as “0” for the power fed in, as feeding in does not take place without the CPU.
Below a particular PV voltage (much less than 80 V), it is expected that the CPU supply voltage is no longer stable and that the measured values are therefore no longer sufficiently precise. In this case, “0” is output for some devices instead of the actual measured value. This applies in particular to the measured value for PV voltage. However, this is not relevant to the grid variables, as feeding in no longer takes place below this PV voltage.
In summary, NaN can be interpreted as “0” in practically all relevant cases for the power fed in.
Question:
Why is the register's current value not displayed and only is -1 or the maximum value showing up?
Answer:
It may be a NaN answer (Not a Number). Check in the device-specific Modbus list whether the requested device has this register address.
Question:
Why were only 9 requests (polls) out of 270 answered with OK, for example, and how can these connection problems be resolved?
Answer:
Depending on the IP stack used, it may be the case that the responses are not always sent in a package. Some IP stacks fragment responses.
The standard Modbus specification expects the following in such a case:
Before the actual Modbus data, the TCP Modbus response includes a seven-byte header, known as an MBAP header, which includes length information.
With TCP reception of a Modbus response, please check that the number of databytes received matches the length information. This is how a fragmented Modbus response can be recognized and completed with further TCP receive calls.
Source: Modbus Organization, “MODBUS Messaging on TCP/IP Implementation Guide V1.0b”, January 29, 2018
Source: Modbus Organization, “MODBUS Messaging on TCP/IP Implementation Guide V1.0b”, January 29, 2018
Question:
Why are two answers occasionally sent via Modbus upon request?
Answer:
Depending on the IP stack used, it may be the case that the responses are not always sent in a package. Some IP stacks fragment responses.
The standard Modbus specification expects the following in such a case:
Before the actual Modbus data, the TCP Modbus response includes a seven-byte header, known as an MBAP header, which includes length information.
With TCP reception of a Modbus response, please check that the number of databytes received matches the length information. This is how a fragmented Modbus response can be recognized and completed with further TCP receive calls.
Source: Modbus Organization, “MODBUS Messaging on TCP/IP Implementation Guide V1.0b”, January 29, 2018
Question:
What does error code 11 mean when requesting some Modbus registers?
Answer:
Error code 11 is sent in response when the Modbus request contains a unit ID that is different from the one set for the inverter.
Example:
If the inverter is set to unit ID = 5 and the Modbus request is made for unit ID = 3 (SMA Modbus) or unit ID = 126 (SunSpec Modbus), error code 11 is sent.
If the inverter is set to unit ID = 5, the correct Modbus request would also be for unit ID = 5 (SMA-Modbus) or unit ID = 128 (SunSpec Modbus). The unit ID in the SunSpec Modbus profile for SMA inverters derives from the preset unit ID in the SMA Modbus profile + 123.
Please check the setting of the unit ID on the inverter.
The following information is sorted by register number
Question:
Why do registers 30797, 30799 and 30801 no longer work in the SMA Cluster Controller?
Answer:
The registers referred to represent the line conductor grid current (AC phase currents). There has been a new definition in the SMA Data2+ object model for the AC phase currents. The old objects were unsigned by the data type.
These objects are obsolete, and new signed objects have been defined accordingly. The new SMA Data2+ objects are represented in the SMA Modbus profile on new, separate register addresses. The benefit of this adjustment for SMA and customers is that an additional SunSpec requirement (signed current) can be fulfilled.
The old objects are gradually being replaced by these new objects in every CPU at SMA (e.g., in case of new developments). This means that at the same time there is an effect on the Modbus register addresses. There is currently still some overlap in terms of SMA devices, equipped with a certain communications processor (KP-COM30), that support both old and new addresses. A general switchover is planned in the future for new development projects and forthcoming product lifecycle support products.
Old SMA addresses:
| 30797 | MB_TYPE_U32 | /* GridMs.A.phsA */ |
|---|---|---|
| 30799 | MB_TYPE_U32 | /* GridMs.A.phsB */ |
| 30801 | MB_TYPE_U32 | /* GridMs.A.phsC */ |
New SMA addresses:
| 30977 | 166 | MB_TYPE_S32 | /* GridMs.A.phsA */ |
|---|---|---|---|
| 30979 | 167 | MB_TYPE_S32 | /* GridMs.A.phsB */ |
| 30981 | 168 | MB_TYPE_S32 | /* GridMs.A.phsC */ |
Question:
Why do registers 30797, 30799 and 30801 no longer work in the SMA Cluster Controller?
Answer:
The registers referred to represent the line conductor grid current (AC phase currents). There has been a new definition in the SMA Data2+ object model for the AC phase currents. The old objects were unsigned by the data type.
These objects are obsolete, and new signed objects have been defined accordingly. The new SMA Data2+ objects are represented in the SMA Modbus profile on new, separate register addresses. The benefit of this adjustment for SMA and customers is that an additional SunSpec requirement (signed current) can be fulfilled.
The old objects are gradually being replaced by these new objects in every CPU at SMA (e.g., in case of new developments). This means that at the same time there is an effect on the Modbus register addresses. There is currently still some overlap in terms of SMA devices, equipped with a certain communications processor (KP-COM30), that support both old and new addresses. A general switchover is planned in the future for new development projects and forthcoming product lifecycle support products.
Old SMA addresses:
| 30797 | MB_TYPE_U32 | /* GridMs.A.phsA */ |
|---|---|---|
| 30799 | MB_TYPE_U32 | /* GridMs.A.phsB */ |
| 30801 | MB_TYPE_U32 | /* GridMs.A.phsC */ |
New SMA addresses:
| 30977 | 166 | MB_TYPE_S32 | /* GridMs.A.phsA */ |
|---|---|---|---|
| 30979 | 167 | MB_TYPE_S32 | /* GridMs.A.phsB */ |
| 30981 | 168 | MB_TYPE_S32 | /* GridMs.A.phsC */ |
Question:
Why do registers 30797, 30799 and 30801 no longer work in the SMA Cluster Controller?
Answer:
The registers referred to represent the line conductor grid current (AC phase currents). There has been a new definition in the SMA Data2+ object model for the AC phase currents. The old objects were unsigned by the data type.
These objects are obsolete, and new signed objects have been defined accordingly. The new SMA Data2+ objects are represented in the SMA Modbus profile on new, separate register addresses. The benefit of this adjustment for SMA and customers is that an additional SunSpec requirement (signed current) can be fulfilled.
The old objects are gradually being replaced by these new objects in every CPU at SMA (e.g., in case of new developments). This means that at the same time there is an effect on the Modbus register addresses. There is currently still some overlap in terms of SMA devices, equipped with a certain communications processor (KP-COM30), that support both old and new addresses. A general switchover is planned in the future for new development projects and forthcoming product lifecycle support products.
Old SMA addresses:
| 30797 | MB_TYPE_U32 | /* GridMs.A.phsA */ |
|---|---|---|
| 30799 | MB_TYPE_U32 | /* GridMs.A.phsB */ |
| 30801 | MB_TYPE_U32 | /* GridMs.A.phsC */ |
New SMA addresses:
| 30977 | 166 | MB_TYPE_S32 | /* GridMs.A.phsA */ |
|---|---|---|---|
| 30979 | 167 | MB_TYPE_S32 | /* GridMs.A.phsB */ |
| 30981 | 168 | MB_TYPE_S32 | /* GridMs.A.phsC */ |
Question:
Does the active power set point need to be changed in small or specific increments?
Answer:
If, for example, you want to change the active power set point from 70% to 10%, it is not required to do it in small or specific increments. Just transmit the new value. The inverter accepts this command and generates the curve in both directions.
Question:
If active power limitation by the system controls is absent and the inverter no longer receives any control commands (e.g., due to an interruption in communication), does it return to a default value?
What is this default value and how long is the timeout?
Answer:
The action that the inverter is to perform in the event of an interruption in communication can be set via Modbus.
Register 41193 is used for the operating mode for absent active power limitation. The time for the timeout, during which the previously defined action is to be performed, must also be set in register 41195. If you have opted for a fallback power, the power level must be set as a % in register 41197.
Question:
Why are multiple registers (40155/40497) available for MAC addresses?
Answer:
SMA register 40155 for the MAC address is incorrect, obsolete and marked as not to be used. Use the newer register, 40497.
Question:
Why are multiple registers (40155/40497) available for MAC addresses?
Answer:
SMA register 40155 for the MAC address is incorrect, obsolete and marked as not to be used. Use the newer register, 40497.
Question:
Which registers may be cyclically written for system control without destroying the device’s flash memory?
Answer:
Please observe the relevant safety information in the documentation (safety information section). Registers for cyclical changes are marked with the addition „Parameters for system control.“
The following information is sorted by register number
Question:
Why is a value of 325 returned instead of the expected ID:101 for a single-phase inverter in the case of the SB nn00TL-21, PKG 2.60 and SB nn00TLST-21, PKG 2.60 inverters?
Answer:
This is an error in SMA mapping that no longer occurs in this way with other inverters. The aim is to eliminate this error in future versions. The value of 325 can be set as equal to 101.
Question:
Why is the value not available for the SMA inverters?
Answer:
The DC power is not available as a cumulative value. It must be added up individually in SunSpec model 160 in consideration of the existing MPP-Trackers (see registers 40632 et seq.).
Question:
Why is the value not available for the SMA inverters?
Answer:
The internal temperature value is currently available only for certain inverters.
Question:
Why is the value not available for the SMA inverters?
Answer:
Register 40224 with information on the operating status was introduced at SMA only in July 2016 for the SB n000TL-US-22 device series. It may be that it cannot be offered in all inverters for this reason.
Question:
Why can I not activate the value?
Answer:
This value must be activated within the inverter’s first ten operating hours. After that, an SMA Grid Guard password is required.
Question:
Why can I not deactivate this control element by using the value “0”?
Answer:
Deactivation would not make sense for ensuring faultless operation. The inverter would ideally have to be set to default; however, SunSpec does not allow this setting. SMA therefore does not offer deactivation via SunSpec.
Question:
Why can I not activate the value?
Answer:
This value must be activated within the inverter’s first ten operating hours. After that, an SMA Grid Guard password is required.
Question:
Why can I not deactivate this control element by using the value “0”?
Answer:
Deactivation would not make sense for ensuring faultless operation. The inverter would ideally have to be set to default; however, SunSpec does not allow this setting. SMA therefore does not offer deactivation via SunSpec.
Question:
Why can I not activate the value?
Answer:
This value must be activated within the inverter’s first ten operating hours. After that, an SMA Grid Guard password is required.
Question:
Why can I not deactivate this control element by using the value “0”?
Answer:
Deactivation would not make sense for ensuring faultless operation. The inverter would ideally have to be set to default; however, SunSpec does not allow this setting. SMA therefore does not offer deactivation via SunSpec.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.
Question:
Why is the value not available for the STP nn000TL-10, PKG 2.65 inverters?
Answer:
The register is present in the inverter. For technical reasons with the STP nn000TL-10, this register cannot currently be documented in the device-specific list. There is no reason not to use the register.