@ Dennis,
The "info tab" has the lion's share of what I've determined and have recorded outside of today's unsure memory. Even that *may* have some "unforseen at the time" errors.
The post I made earlier regarding PL/MPL data storage and managment is the result of recently re-affirming the function/process before posting erroneous /mis-remembered information.
I started down that rabbit hole just before I paused research, so I had to re-create and refresh my memory of the process before I posted anything.
The finished/presentable .xls PL calc you see is the great granchild of the scratchpad tab? I thru some formulas in to translate what I viewed in raw data into what the RSS displayed for that mode slaved PL/MPL location.
Read references I make in post referencing zero page values as "I remember it was there, but dont recall the exact memory location" As of yet, I havent gone back and re-affirmed any of that non specific information.
I will need to perform some up to date re-evaluation of the codeplug structure to refresh my memory and post what those variables are and where they are stored.
For example, from memory, and because I "used" them repeatedly I can correctly say (as viewed in HexWorkshop):
bytes 02h and 03h store the size (last byte location) of the codeplug.? I remember those clearly because that is how I confirmed what size codeplug I was exploring/mapping.
The RSS created codeplug files are all ~9k bytes. Data above the point referenced here is ignored when writing the codeplug to the radio.
bytes 03h and 04h are the checksum values. I remember those clearly because those are the locations I had to write corrected CS values to in order for the RSS to accept the edited codeplug. It wont even load a file that has a bad CS much less write it to the radio.
Anything beyond that I will need to confirm exact function(s)/location(s) in order to provide verified correct information.
I've spent recent time available on the PL data management as it is more complex and more critical to the project to manipulate these parameters
As is the fequency calculation, location(s) in the codeplug for a given mode, and method of storing the 10 bit, 6 bit, reference freq bit, V0/V1 bits, and C0/C1 bits I have already posted or presented in the .xls files.
Currently it is possible to:
import a standard RSS generated codeplug file to a hex editor,
edit any/all frequency values for a given mode (using the .xls frequency to byte calculator to determine the values)
edit any PL value for a given mode (using the .xls PL calculator to determine the values)
edit the NP scan list for a given mode (I suspect sorting info for P1/P2 manipulation is relatively easy but was not high on the priority list)
correct the checksum
save the file
and re-open it in RSS to write to the radio.
I believe with more research, it is possible to manipulate all the X9000 features, eventually.
As I said the verified/documented structure data appears to have been on a long dead now HDD. Anything I have posted I have verified. Anything left I havent posted is yet to be re-verified.
