# Serial in node not working in node-red 0.20.5

**URL:** <https://discourse.nodered.org/t/serial-in-node-not-working-in-node-red-0-20-5/10141>\
**Category:** General\
**Created:** [14 April 2019 20:20 UTC](https://discourse.nodered.org/t/serial-in-node-not-working-in-node-red-0-20-5/10141 "2019-04-14T20:20:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dennishvo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dennishvo/32/2896_2.png) [@dennishvo](https://discourse.nodered.org/u/dennishvo)\
**Post date:** [14 April 2019 20:20 UTC](https://discourse.nodered.org/t/serial-in-node-not-working-in-node-red-0-20-5/10141/1 "2019-04-14T20:20:51Z")

</div>

I'm running node-red 0.20.5 on an RPi 3 B+ with Raspbian GNU/Linux 9.8 (stretch) and node-red-serial-port 0.8.1. Since upgrading from node-red 0.19.5, the serial in node has started behaving strangely.

Messages are being transmitted from another PCB to the RPi every second, but mostly I get no data. Every few minutes I get either a "-1" message or garbage such as this: "�~�����~��?���~���~?���~��~?~��~?�~��~���~���~�~�~����~�� ~~��~��~?�~��~���~�����~��?���~���~?���~��~?~��~?�~��~���~���~�~�~����~��~~ ��~��~?�~��~���~�����~��?���~���~?���~��~?~��~?�~���~���~���~�~�~����~�� ~~��~��~?�~��~���~�����~��?���~���~?���~��~?~��~?�~��~���~���~�~�~����~��~~ ��~��~?�~��~���~�����~��?���~���~?���~��~?~��~?�~��~���~���~�~�~����~�� ~~��~��~?�~��~���~�����~��?���~���~?���~��~?~��~?�~��~���~���~�~�~����~��~~ ��~��~?�~��~���~�����~��?���~���~?���~��~?~��~?�~��~���~���~�~�~����~��~~��~��~?�~��~���~�����~��?���~���~?���~��~?~��~?�~��~���~���~�~�~����~��~..."

I should be receiving a short string every second about 16 bytes long and terminated with '\r' (CR, ASCII character 13).

Any clues as to what has changed between 0.19.5 and 0.20.5 that could cause this?

---

<div class="post-metadata">

**Author:** ![dennishvo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dennishvo/32/2896_2.png) [@dennishvo](https://discourse.nodered.org/u/dennishvo)\
**Post date:** [14 April 2019 22:25 UTC](https://discourse.nodered.org/t/serial-in-node-not-working-in-node-red-0-20-5/10141/2 "2019-04-14T22:25:23Z")

</div>

Issue resolved. For some reason the configuration for ttyS0 was changed so that the baud rate became 57600 instead of 9600. This never occurred in previous upgrades of node-red, so I'm still a little confused as to how this happened. Any thoughts?

---

<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:** [15 April 2019 08:39 UTC](https://discourse.nodered.org/t/serial-in-node-not-working-in-node-red-0-20-5/10141/3 "2019-04-15T08:39:07Z")

</div>

How did you upgrade?

---

<div class="post-metadata">

**Author:** ![dennishvo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dennishvo/32/2896_2.png) [@dennishvo](https://discourse.nodered.org/u/dennishvo)\
**Post date:** [15 April 2019 14:36 UTC](https://discourse.nodered.org/t/serial-in-node-not-working-in-node-red-0-20-5/10141/4 "2019-04-15T14:36:48Z")

</div>

Typically I use the update-nodejs-and-nodered script. However, I've traced this issue to (shockingly) an error on my part. I started working with a new serial device that runs at a higher baud rate and that configuration got copied into the wrong flow. Sorry to waste your time.

---

<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:** [15 April 2019 15:17 UTC](https://discourse.nodered.org/t/serial-in-node-not-working-in-node-red-0-20-5/10141/5 "2019-04-15T15:17:53Z")

</div>

No problem.