# SMA Modbus TCP/IP warnings/fails

**URL:** <https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263>\
**Category:** General\
**Tags:** modbus\
**Created:** [16 December 2021 05:33 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263 "2021-12-16T05:33:07Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![SirPrice](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@SirPrice](https://discourse.nodered.org/u/SirPrice)\
**Post date:** [16 December 2021 05:33 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/1 "2021-12-16T05:33:07Z")

</div>

Dear all,  
I am reading from SMA via Modbus TCP/IP 3 values per 1 min every 4 min. It fails approx 4 - 6 times per 24 hours with the following errors:  
15 Dec 04:06:20 - [warn] [modbus-getter:modbusGetSolarkWh] FSM Reset On State QUEUEING  
15 Dec 04:06:44 - [warn] [modbus-getter:modbusGetSolarkWh] FSM Reset On State INIT

Anyone having any idea what to do, I do want too avoid loosing the data for the requested read as much as possible.

---

<div class="post-metadata">

**Author:** ![inGo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ingo/32/52953_2.png) [@inGo](https://discourse.nodered.org/u/inGo)\
**Post date:** [16 December 2021 09:08 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/2 "2021-12-16T09:08:58Z")

</div>

does it always concerns the same register?  
I see in the modbus spec from SMA that the Wh registers has a lenght of 4 instead of 2 like the others

---

<div class="post-metadata">

**Author:** ![SirPrice](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@SirPrice](https://discourse.nodered.org/u/SirPrice)\
**Post date:** [16 December 2021 09:31 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/3 "2021-12-16T09:31:00Z")

</div>

I am reading the following 3 items from SMA:

- Acccumulated kWh production
- Momentary W
- Time  
In almost all cases one or both of the first 2 are the items that fail, rare that the Time fails but has happen

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [16 December 2021 09:50 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/4 "2021-12-16T09:50:35Z")

</div>

Are you triggering multiple read requests at the same time, or doing them one after the other. If at the same time then try spacing them out so they do not overlap. Even better is to do them in one read, if the addresses are not far apart.

---

<div class="post-metadata">

**Author:** ![SirPrice](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@SirPrice](https://discourse.nodered.org/u/SirPrice)\
**Post date:** [16 December 2021 09:52 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/5 "2021-12-16T09:52:24Z")

</div>

The adress's are to far away, the spacing is 20 sec between each read in the minute when I am reading.

---

<div class="post-metadata">

**Author:** ![SirPrice](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@SirPrice](https://discourse.nodered.org/u/SirPrice)\
**Post date:** [16 December 2021 10:00 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/6 "2021-12-16T10:00:55Z")

</div>

Do you think 20 sec should be sufficent spacing, OR is the SMA Modbus Server so slow in reply that it could overlap even with 20 sec?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [16 December 2021 10:36 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/7 "2021-12-16T10:36:48Z")

</div>

Sorry, I don't know about that, presumably you can tell from when the messages are received whether that is the case.

---

<div class="post-metadata">

**Author:** ![inGo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ingo/32/52953_2.png) [@inGo](https://discourse.nodered.org/u/inGo)\
**Post date:** [16 December 2021 11:02 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/8 "2021-12-16T11:02:36Z")

</div>

SMA has a max. number of pollings per day or something... unfortunately I can't find the excat value now

not sure if is good to poll every 20sec a different register. Why not read every register in one step?

I use node-red-contrib-modbustcp  
poll every 25s 3 registers with modbustcp-read and it is working fine

edit:

from [SMA-Modbus-general](https://files.sma.de/downloads/SMA-Modbus-general-TI-en-10.pdf)

> **Data Transfer Interval via the Modbus protocol**  
> For system stability reasons, the time period between data transfers via the Modbus protocol must  
> be at least ten seconds. No more than five parameters and measured values should be transmitted  
> per SMA inverter.

sounds enought from SMA-side 🙄

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [16 December 2021 11:59 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/9 "2021-12-16T11:59:14Z")

</div>

Hi,  
i query every 5s my 4 SMA inverters since years without problem, In addition, a charging station (called openWB) query the 4 inverters via modbus every few seconds too.

I could query every 2s if I want.

You can check my flow(s): [10.12.2021 - Google Drive](https://drive.google.com/drive/folders/1oVJzBCnw3O7cKWE2wo1Qh1NKdFXjFBUV)

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/d/dd0ceb8f361193cb285d4547d77e90d356793cb2.png)

---

<div class="post-metadata">

**Author:** ![SirPrice](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@SirPrice](https://discourse.nodered.org/u/SirPrice)\
**Post date:** [6 January 2022 10:45 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/10 "2022-01-06T10:45:33Z")

</div>

![clk](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/6/762a53e722f0350caf52f62526452d49c927c297.png)  
 ![modbus](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/b/0bd5206ed18e15e274a7d06b03e84358a3ca0730.png)

This is my setup and the given alarms, Can I get help by someone to get explained the serial with alarms that I sometime get?  
The communication is over Internet and I get 4-5 errors a day (not including what I believe is errors that follows the initial error).  
I tried to move the requests to be 40 sec between and asking for one value at a time from the SMA Solar Inverter.  
Is there anything I could try out to change to improve and reduce the errors?  
I have also S7 communication to 2 different PLC's that hardly never fails or give errors.  
Also the S/ communication is spread out to not have a chance to conflict the time when the Modbus requests will occour.  
Would be very greateful for inputs, help

---

<div class="post-metadata">

**Author:** ![SirPrice](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@SirPrice](https://discourse.nodered.org/u/SirPrice)\
**Post date:** [6 January 2022 10:47 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/11 "2022-01-06T10:47:26Z")

</div>

![modbus_settings](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/0/0039480fe5589f6e9ee644cb48587860ada7e6d8.png)

This is the Modbus setup I am using as referense to support if someone could explain the behaviour of the errors, based on setup and error timestamps given in earlier attachments

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [7 March 2022 10:48 UTC](https://discourse.nodered.org/t/sma-modbus-tcp-ip-warnings-fails/55263/12 "2022-03-07T10:48:14Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.