# UDP message issue

**URL:** <https://forum.inductiveautomation.com/t/udp-message-issue/76180>\
**Category:** Ignition\
**Created:** [July 11, 2023, 9:32am UTC](https://forum.inductiveautomation.com/t/udp-message-issue/76180 "2023-07-11T09:32:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Giske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/richard_giske/32/41906_2.png) [@Richard\_Giske](https://forum.inductiveautomation.com/u/Richard_Giske)\
**Post date:** [July 11, 2023, 9:32am UTC](https://forum.inductiveautomation.com/t/udp-message-issue/76180/1 "2023-07-11T09:32:47Z")

</div>

I'm reading some data forwarded through a Moxa nport 5150a via UDP.

I'm having some issues however, the data is showing mostly as "diamonds" with questionmarks in them.  
So it's most likely some encoding issue, but I've not encountered this before.

Can this be rectified with scripting in ignition, or does the data have to be encoded in a different format from the Moxa box? (I don't have access to the moxa config so I'm not entirely sure how it's set up).

Anyone got experience with this Ignition/Moxa combo or has run into this problem before?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 11, 2023, 11:59am UTC](https://forum.inductiveautomation.com/t/udp-message-issue/76180/2 "2023-07-11T11:59:13Z")

</div>

That is normal for getting bytes. You will need to use the `MessageBytes` tag instead of the `Message` tag, then do your own decoding.

[https://docs.inductiveautomation.com/display/DOC81/UDP+and+TCP+Driver#UDPandTCPDriver-UDPTags](https://docs.inductiveautomation.com/display/DOC81/UDP+and+TCP+Driver#UDPandTCPDriver-UDPTags)