# Problem with continuous high digital output signal from contrib-S7 node

**URL:** <https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819>\
**Category:** General\
**Created:** [22 April 2026 15:42 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819 "2026-04-22T15:42:30Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johannesje](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@Johannesje](https://discourse.nodered.org/u/Johannesje)\
**Post date:** [22 April 2026 15:42 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/1 "2026-04-22T15:42:30Z")

</div>

Hi all,

I am using a Siemens Logo for my home automation.  
I have connected a dimmer on my Siemens Logo, when I give a pulse, the light goen "on" and with the second pulse the light goes "off". For dimming the lights I have a continuous signal.  
I am using "node-red-contrib-s7" including "Dashboard 2.0", so I can send a pulse or continuous signal to the Siemens logo.  
Sometimes (once in a mounth) the output goes to "high", so the light is continuous dimming. the only possibility to stop this, is reload the software in the Siemens Logo.  
Is there some one who has experience with thid issue?

---

<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:** [22 April 2026 15:56 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/2 "2026-04-22T15:56:47Z")

</div>

> [@Johannesje](#):
>
> Sometimes (once in a mounth) the output goes to "high"

What output goes high?

---

<div class="post-metadata">

**Author:** ![Johannesje](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@Johannesje](https://discourse.nodered.org/u/Johannesje)\
**Post date:** [22 April 2026 16:03 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/3 "2026-04-22T16:03:51Z")

</div>

Output node-red to input Siemens Logo. When I set the output from Node-red to low, the input to Siemens Logo stay "High"  
It happens with different outputs

---

<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:** [22 April 2026 16:05 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/4 "2026-04-22T16:05:54Z")

</div>

I don't know that node in detail, does it normally show a 'connected' status? If so does it stay connected?

Are there any messages in the node red log when the problem happens?

Does restarting node-red fix it?

---

<div class="post-metadata">

**Author:** ![Johannesje](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@Johannesje](https://discourse.nodered.org/u/Johannesje)\
**Post date:** [22 April 2026 16:24 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/5 "2026-04-22T16:24:46Z")

</div>

I read normally "Online" near the node  
Can I find afterwards a message in a log file?  
Restarting Node-Red has no effect, only reload the Logo software.

---

<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:** [22 April 2026 16:41 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/6 "2026-04-22T16:41:05Z")

</div>

> [@Johannesje](#):
>
> I read normally "Online" near the node

So the node thinks it is still connected.

> [@Johannesje](#):
>
> Can I find afterwards a message in a log file?

That depends on what OS you are running and how you installed node-red.

> [@Johannesje](#):
>
> Restarting Node-Red has no effect, only reload the Logo software.

That makes it almost certain that it is a problem at the Logo end. Can you still control/read other things on the Logo?

---

<div class="post-metadata">

**Author:** ![Johannesje](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@Johannesje](https://discourse.nodered.org/u/Johannesje)\
**Post date:** [22 April 2026 17:21 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/7 "2026-04-22T17:21:04Z")

</div>

I run continue more IO on the Logo together with node-red, this is fourth Logo DI where it happens....

---

<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:** [21 July 2026 17:22 UTC](https://discourse.nodered.org/t/problem-with-continuous-high-digital-output-signal-from-contrib-s7-node/100819/8 "2026-07-21T17:22:03Z")

</div>

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