Hi Adrian,
I just finished re-reading your post made a couple of weeks ago when I first brought up "How to create an 8 byte integer". Your thoughts/comments have become clearer now that I have tried to implement this and have seen (some) of the issues it presents!
The problem I have (had) with sending a string of bytes is that they are being decoded by existing software that is already in the field. It is decoded as 4 bytes then set/saved/processed as an Long Integer:
[code:1:d41d5ae7a0]
Remote_Response_Data = (Add1 * 256 * 256 * 256) + (Add2 * 256 * 256) + (Add3 * 256) + Add4
[/code:1:d41d5ae7a0]
I wanted to continue to use that same process, but it seems that is not going to work. Further consideration of your suggestion and deeper thought says that your argument is the best solution. In this case as well, we *can* control both ends. So even with the (windows) software in the field, we can either force before use or set this as a new feature with an enable switch - we I have as well....
More consideration reveals that by utilizing your suggestion, we could also make the code an alpha, or alpha-numeric code.
Again, thank you all for your suggestions and pointing out what should have been obvious....
Tim
↧