Joined: 01 Aug 2003
Location: Chicago, IL
|Posted: Sun Jan 14, 2018 8:25 pm Post subject:
|The hex that you are finding is the OBC in hexadecimal form, so you need to do a hex-to-decimal conversion on it. There are various tools you can use to do that, including Excel (which has the =HEX2DEC function) and the scientific calculator that comes with Windows.
The hex codes used in RM are *not* just a hexadecimal representation of the OBC, they are the hex codes used by the protocol executor. This is a bit technical, but the NEC executor uses hex codes in an LSB-COMP format (LSB means Least Significant Bit first). So, if you wanted to manually calculate the RM hex code, you would first convert your OBC to binary, then you would reverse the order of the binary, then you would complement it (ie, change all the 1s to 0s, and all the 0s to 1s). So yeah, a bit complicated, so just enter the OBCs.
So, going back to your first post, you gave us this...
11 ee 16 CH+
11 ee 0F CH -
converting hex to decimal
11 = 17
ee = 238
16 = 22
0F = 15
So, the OBC for CH+ is 22. For the RMDU file, I just took all the hex codes that you entered and converted them to decimal and re-entered them as OBCs. You must have entered the wrong hex code for CH+ as I see the OBC in the file is 34. If you change that to 22 it will start working.
Please don't PM me with remote questions, post them in the forums so all the experts can help!