Joined: 06 May 2007
|Posted: Sun Apr 27, 2008 1:54 pm Post subject:
|Ok, so it looks like the proper adx to reference is "6E_160baud.adx", since what I see as a pattern is what I thought I saw yesterday, but then it didn't seem to crossreference between Scanner Pro and Tuner Pro RT for the same application.
The pattern I see is that the "byte" used by Tuner Pro RT, is converted to hexidecimal, and used in the "Packet Offset (Hex)" location in the adx editor.
Is that correct mark?
I compared the "6E_160baud.adx", to A059 file that I downloaded from file man, and this is where I figured out this pattern.
If what I see is correct, why do the same applications seem to use different bytes of the datastream between the .ads used by TP RT and the .adx used by Scanner Pro. I compared $59 .ads and .adx files, and I believe a few others, and none seem to match between the two programs.
BTW, the "import" function doesn't seem to really do anything, as that was my first attempt, to create a new .adx. I'm sure you know this, but just wanted to point that out if it was supposed to work.
Well I figured it out....
Yesterday when I was comparing .ads and .adx files for code $59, I forgot that hexidecimal starts at 0 (0x00 or $00), and that numerical starts 1 (I remembered the latter ), so I didn't offset the byte number by -1 when I was comparing them. Now it all makes sense.
I'm still curious about the "unique ID" box and it's function in the program.