Its a small standalone exe, I have made a copy of it trying to reverse engineer it. I don't care if it breaks that program since I have copies. I own the software and controller, finding out how it works to use for myself, and use that knowledge to be able to data-log is the whole reason I have this device. I don't see any ethical issues with what I am trying to achieve with this.Reverse engineering anything is akine to trying to break a code.
Im not certain were able to help with reverse engineering what is evidently not your code !
In a general way
You need to understand the "data" you see in any program, as to what it means
e.g. asic is a 7 bit code, represented in a 8 bit field,
or it could be a pure hex number
if your seeing W3039
is that write 09 ?
or write 3039 ?
or what ?
the same 8 bits at different times could be a control code, a number , a letter dependent upon the protocol.
The data might even be little endian / big endian swapped,
might have a CRC , could even be encrypted
you need first to get a good look at the real data on the line,
1 and 0.
then you can start deciding what it is,
Once you have the above,
then look for patterns,
is there a regular set of data ,
is there correlation between wind going up and a set of data going up
It can be done,
look at things like SAMBA for file access , that was reverse engineered
But its not easy, and takes lots of pain staking logging / recording, and a fair amount of luck,
once you have one bit, you can generally build on that
some times down a false path, but persistance.
Have you looked here
I have tried several serial analyzers and the data keeps coming up like the screen shot I posted before. the hex doesn't match up with visual data shown in the pc program. Which is why it might not be possible to use that serial data without either some type of register map or finding out what register data the program is using.