The raw message format is pretty easy to understand.  So how do we use this to find and fix problems with our device?

If your device isn't working right, you can look at the raw message traffic with mtDebug and see if data is missing, or malformed, or if the values being reported are outside of the range that you would expect.

For example, if your device always reports a value of 0 for a pot, no matter how you turn it, then you can focus your attention on the pot circuitry or the specific parts of the software that are supposed to read it and report its value.

If the value of the variable for your pot is never sent at all, then perhaps you forgot to add something important to the code that TCPmaker generated for you.

Suppose your device has problems only under some specific circumstances: for example, when you push a certain button. You can run your device under the control of mtDebug with logging off until just before you trigger the problem.  Then, turn on logging, push the button to trigger the problem, and you'll capture just the message traffic you need.