Are you sending the strings as native bytes or ASCII equivalents?

Most of what you have listed are just different forms of notation for the same thing.

e.g. cd is equivalent to 205 or 11001101 in binary.

Assuming your strings are correct, pasting \xCD\x00\x0e\xaa\x01\x0b\x0A\x09\x08\x0C\x10\xff\x01\x18\x01\x20\x01 into an SIO should work on TCP port 23 (according to the documentation). It does not matter if it is lower or upper case as the Hex notation is just a human readable form of single byte binary and the SIO symbol will interpret it, though it is better to decide what you prefer to use and stay with it, the string you pasted are mixed. (If you are just going to use preset strings then an SIO is the easiest way to do it. If you are planning to do something more adventurous then S+ should be easy enough, but you need to build your strings correctly.

 

From the vendor website

"Once the Protocol Buffer message has been serialised it must be sent in the following format by prepending the eDIDIO Series 10 specific "wrapper". [Start Byte, Length MSB, Length LSB, ...PB message bytes...]

• The Startbyte is 0xCD.
• Length is the total length of the protocol buffer message."

Thanks Lindsay.

To follow up on this, I had to reflash the eDidio DMX controller with their native firmware, as the unit I had was flavored for Control4, which left TCP port 23 disabled, as well as other things.

Once back to non-TLS, and using port 23 with a TCP client, I was able to connect my MC3 to the eDidio S10 and send the commands in the following format:

 

\xCD\x00\x0e\xaa\x01\x0b\x0A\x09\x08\x0C\x10\xff\x01\x18\x02\x20\x01

 

No line feed or carriage return.  This is a string to start "Sequence 2", as created in the Spektra app for eDidio DMX controller.