The data are floating point encoded on 32 bits Little_endian
byte 0 to 3: 00 00 00 00 = 0 channel number
byte 4 to 7: 1f 85 a3 41 = 0x41a3851f = 20.4400005341
This one's actually pretty simple.
I think how I did this one was noticing the lack of punctuation in the initial string. From there I believe I just used the magic operation to get the next 2 ...
Since you are dealing with a dot Net application, this will be super easy.
As dot Net application are 'compiled' using an Intermediate Language (IL), you may be able to recover something very close to the original source code. If the binary is not obfuscated/protected, you just have to open-up your application in a .NET editor.
DnSpy is the one that I find ...
Without reverse engineering, it may be difficult to guess what are these data. However, you can harvest many packets then diff/observe them to determine the size of data filed, which data remain, which data changes...
Here's my go to in Python3: bytes.fromhex('020a0d')
From there you can interpret how you'd like.
Python 3.7.6 (default, Dec 30 2019, 19:38:26)
>>> hex_str = '020a0d'
As an aside, I've found that storing things as ASCII Hex is one of the better RE habits I've gotten into. You can share ...