# Modbus TCP previews correct output, but receiving end gets garbage

**URL:** <https://discourse.nodered.org/t/modbus-tcp-previews-correct-output-but-receiving-end-gets-garbage/78322>\
**Category:** General\
**Tags:** modbus, docker\
**Created:** [10 May 2023 15:22 UTC](https://discourse.nodered.org/t/modbus-tcp-previews-correct-output-but-receiving-end-gets-garbage/78322 "2023-05-10T15:22:11Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![Darren](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/darren/32/92202_2.png) [@Darren](https://discourse.nodered.org/u/Darren)\
**Post date:** [6 June 2023 14:29 UTC](https://discourse.nodered.org/t/modbus-tcp-previews-correct-output-but-receiving-end-gets-garbage/78322/26 "2023-06-06T14:29:59Z")

</div>

Some the weirdness my end was caused by Modbus broadcasting single-number arrays, rather than single numbers. Fixed with simple functions. [Solution to that issue here](https://discourse.nodered.org/t/modbus-server-with-node-red-docker-port-forwarding-required/78096/12)

Issue still remains with byte-swapping on my colleague's end.

---

_[View the full topic](https://discourse.nodered.org/t/modbus-tcp-previews-correct-output-but-receiving-end-gets-garbage/78322)._