Join 136,327 Programmers for FREE! Get instant access to thousands of experts, tutorials, code snippets, and more! There are 2,821 people online right now. Registration is fast and FREE... Join Now!
You'll want to find a specification as to what the communications format is. Just taking a wild guess, it appears to be a heterogeneous structure with little endian words, double words, and probably some 32-bit IEEE-754 floating point numbers. But that's just a wild guess (as in, without seriously looking at it).
This post has been edited by perfectly.insane: 6 Sep, 2008 - 08:25 PM
You'll want to find a specification as to what the communications format is. Just taking a wild guess, it appears to be a heterogeneous structure with little endian words, double words, and probably some 32-bit IEEE-754 floating point numbers. But that's just a wild guess (as in, without seriously looking at it).
Well, looking that the range of the output, it's definitely not text (lots of FF bytes). As far as whether or not it's little endian or big endian, it's hard to say either way. But it looks like there's a large array of short ints in the middle (the 0x15, 0xFF combinations, but a few combinations in the beginning are different, and they're different wordwise). I suspected that it was little endian because it's probably less likely to have two words that end with exactly 0xFF but have differing initial bytes, whereas if it were little endian, then that 0xFF would probably indicate a negative number (if it's being interpreted as signed). It looks like there may be a few 4-byte integral values and a few floating point ones, looking at the patterns (especially for 4-byte blocks of not-so-nice (meaning, not 0x00, 0xFF, 0x7F, etc)). But again, that's just from experience. The original poster hasn't given us any further details. If we knew what this was supposed to represent (at least any information at all), it would be much easier to reverse engineer.
Well, looking that the range of the output, it's definitely not text (lots of FF bytes). As far as whether or not it's little endian or big endian, it's hard to say either way. But it looks like there's a large array of short ints in the middle (the 0x15, 0xFF combinations, but a few combinations in the beginning are different, and they're different wordwise). I suspected that it was little endian because it's probably less likely to have two words that end with exactly 0xFF but have differing initial bytes, whereas if it were little endian, then that 0xFF would probably indicate a negative number (if it's being interpreted as signed). It looks like there may be a few 4-byte integral values and a few floating point ones, looking at the patterns (especially for 4-byte blocks of not-so-nice (meaning, not 0x00, 0xFF, 0x7F, etc)). But again, that's just from experience. The original poster hasn't given us any further details. If we knew what this was supposed to represent (at least any information at all), it would be much easier to reverse engineer.
if that is hex then i found this great site but it still does not translate right ARE YOU SURE ITS HEX? because it seems it might not be hex because here it the site i used and here is the translation
3 Sep, 2008 - 12:44 PM
| 