@ RFI-EMI-GUY
16 MPL limit....no, but I'll need to qualify that.
First, as has been mentioned by others, I too have an acute case of CRS as in "Why did I walk in this room, or What did I have for breakfast....sometimes I truely cant remember. Would be funny if it wasnt so sad.
So,? boilerplate disclaimer....it's been at least 3 maybe 4 years ago since I even? took a poke at any of this.
Back on topic...MPL count is set by a byte on zero page of the memory, somewhere before 0Fh.
Change that and it sets the MPL count the RSS will let you enter.
Two caveats
1- Checksum...that can be delt with. If not the RSS will complain and will NOT save or fix it. If the CP is hex edited and the CS is not corrected the RSS will not open the file.
2- What function owns the memory that the RSS will now allow you to write PL data in?
In a bare bones operation, no encryption, no siren, VRS control, MDC and DTMF etc it would likely be fine. I have not mapped those functions so I cant say if they use that space or not, or if anything does.
Also, the PC's screen goes wonky (that's a technical term) when you enter MPL data > than about 20. Keep up with where you are and it will enter the data as expeted. The RSS display routine wasnt written to handle the extra fields and the NL/CR functions are out of sync with the data fields. No biggy, pay attention, it will work.
The other issue is the CH side. The memory space for the "alpha tags" gets screwy too. Like programming more modes (240?) than the CH has space to store the alpha tags. It works, but looks like crap on the CH.
There is a means to bump mode count to 255. Same deal. A byte on zero page controls the number of modes the RSS will let you enter in setup. Again same deal with the original owner of the memory space and the CH alpha tag issue.
Ever done the "increase the scan member limit" hex edit in Spectra/MCS/MTS etc RSS? Same thing only in the codeplug not the RSS. BTW the scan limit is a hard 64 on a mode by mode basis, unless you get the 128/255 RSS and FW. But that a totally different dog to kick.
So, 255 modes w/32 (or more) MPL in a 2k 2816 is possible, if the original owners (if any) of the memory real estate arent using it.
The ability to edit EEPROM memory locations "on the fly" is the cat's a$$ here. We know where the data resides in/for each mode (at least the tx,rx,alt tx freqs, the mode slaved tx/rx PL data, the 8 bytes per mode that are bit mapped to enable/disable the 1st 64 modes that can be scanned when that mode is selected, and the actual MPL data location.)
We know how to calculate the hex values needed for these values, and we know where and how to calculate and correct the checksum so the radio doesnt throw a codeplug checksum fault on the next bootup.
There are other? functions in the per mode byteset like TOT and Priority scan, I've not set out to find so far.
I agree, all I/O functions seem to be via SB9600 and done in or thru the CH and VIP ports.
Finding a siren cable may be as hard as finding an actual drawer/CH cable.
A thought about dual drawer operation.
I *think* I remember...lol that the radio1/radio2 was programmed in the CH with certain CH RSS. Again in the 1st line of the CP zero page a byte? or bit was set or cleared telling the radio if it was radio1 or 2. I think I have the CH RSS "somewhere" that sets up the radio1 or 2 button.
There was SP RSS and FW for this as well but I want to say the guy I learned this from said there was a work around. I'll have to scour my emails to see if I still have that exchange.
I agree, hardware hacks are not the desired path, but it's the only way to wedge ourselves in to the places needed to manipulate the system to our liking.
Or, it's possible Casey and I are just batsh*t crazy mad scientists....lol
