Serial UDP and OSC not working together

Hello MacTommy , thank you for sending the showfile.  It was very helpful.

The issue you are running into is that your Send String macros (and maybe other Strings you might send Executed by a Cue) are formatted like OSC.  So they look like this:

/thing/all/1>1/

When Eos encounters a string like that to send, it assumes you want that to be sent as OSC since it is following OSC norms, so Eon sends it down the "OSC Pipe" (in your case, sending to Port 53000).  Eos v3.1.1 Operations Manual - Explicit OSC Output

To force a string to use the "String" pipe (in your case, Port 8001), preface it with "udp:"

Send_String udp:/thing/all/1>1/

I do not see this documented in the User Manual, so I will see about getting it into a future version.

EDIT: This option was added in v2.3.2: [EOS-32588] Serial strings with "udp:" prefix should never be sent as OSC - Jira

I did find this forum post from many years ago that describes this feature: sending Strings over Ethernet, Bug, Question - Eos Family Show Control Support (MIDI, SMPTE, OSC, RTC, etc) - Eos Family Consoles - ETC - Community 

Hi and thanks for that clearifaction Matt. 

I rebuild my script so it filter out all non "OSC IDK"-commands, because EOS send out "fire"-command every GO. I also change networkport so it´s same as our QLab-machine and added my Arduino-IP on the OSC-setup so I have multiple IP on OSC-output. So now it works fine when I tested it whitout serial UDP enabled... 

Hi and thanks for that clearifaction Matt. 

I rebuild my script so it filter out all non "OSC IDK"-commands, because EOS send out "fire"-command every GO. I also change networkport so it´s same as our QLab-machine and added my Arduino-IP on the OSC-setup so I have multiple IP on OSC-output. So now it works fine when I tested it whitout serial UDP enabled...