So why don't you and Mike and MCH combine all your information and write up an article to be posted on Repeater-Builder? This seems like an interesting topic. As long as you put a disclaimer at the top about not being responsible for any problems that may occur with the operation of the user's radio as a result of modifications made with this information, etc, you should cover your a$$ fairly easily.
Bob M. ====== --- On Sat, 2/14/09, W. H. Phinizy <[email protected]> wrote: > From: W. H. Phinizy <[email protected]> > Subject: [Repeater-Builder] Re: Motorola RSS File Structure > To: [email protected] > Date: Saturday, February 14, 2009, 8:27 AM > Mike, MCH, et al, > > Thank you for your comments and particularly the > "Rosetta Stone" for > the channel lines of an MT1000 codeplug. Several > observations, which > may be of interest: > > (1) The first 14 lines (which appear to be 11 > lines for my 16-channel MT1000) are not > entirely sacred grounds. It is possible > to "hack" that data to some degree, although > at this point, I haven't really investigated > it thoroughly and the RSS might just as well > provide one enough access...so why bother. > > By the way, I refer to them as the "header" > data and the channel lines as "detail" data. > > (2) I suspect one of the reasons that modifying > the header data -- or using a pedestrian editor > like Notepad -- doesn't work out is because > it/they might truncate the three blank lines > between the top of the header data and the > part that precedes the detail data. Below, > modified to not wrap, is a snippet from a > codeplug header. Notice that the line containing > the recurring "1234566789+" literals is the > first of these three blank lines. The remaining > two are polulated woth periods. > > These were modified (filled with non blanks) > adulterated, saved, and re-read without incident. > I have not written the codeplug to the radio, so > be careful. The point is that so long as there are > 48 blanks terminated by a CR/LF (0x0DOA) the code > plug seems fine. > > (3) Of possible interest to hack would be the big > long, line of "308NONENONENONENONENONE.." > which > appears to be the PL table. The format belowis > separated into significant tokens for clarity: > > 308 D023 D023 0693 2336 0719 2418 0744 2503 0719 2541 > > where: > > 308 = constant value > D023 = Digital 023 (TX & RX) for entry one > 0693 = TPL 69.3 (TX) for entry two > 2336 = TPL 233.6 (RX) for entry two > ..etc. > > Header of 16-channel MT1000: > ---------------------------- > 00F604782YYYYYYYYYYYYYYYABCDEFGHIJ XYZ1ARU0909H445S > EEEEENDEEEEDD01030840003003030000000000000000016070... > 042NONE NONE 042NONE NONE EEEDXXXXXXX > 308D023D02306932336071924180744250307192541NONENONE... > 123456789+123456789+123456789+123456789+12345678 > ................................................ > ................................................ > > 020007007DDEEEEEE0001DDDEDEED1501500500DDDDDEK > EEDDDNDDDDPDE0150050250000770000750790101800080 > > 01562EE100110011001100110011001100110011001100110011001000 > D015DD0821649 > ---------------------------- > > (4) I use an editor called UltraEdit; it is by far > the best product available for software developers. > It has a built-in hex editor that can be toggled > on or off. By the way, no pecuniary interest here, > just a satisfied customer. It is cheap, however, > and offers a 45-day trial period. > > (5) By the way, if one is interested in methodology, > it is possible to run the RSS in a DOS window > (remember, the radio is NOT being programmed), > edit the code plug, read a code plug with RSS, > make changes using the RSS, and instantly have > the editor alert you that a change has been made > so can see the net effects. > > I tried this on my friend's computer with his RSS > and my code plugs. > > I have not gotten into the HT600 code plugs yet, but I > suspect that > some of the data blocks are pretty much the same -- or, at > least > similar. > > Again, Mike, I am grateful for your insights and the > wonderful > contributions you and the others have made to the Repeater > Builder's > site. These areicles have fueled my excitement for these > radios. > > They are great bargains, can be fixed up, and offer > reliable and > sturdy alternative to the more fragile, higher-priced > alternatives. > > Besides, as a ham, I just like to take things apart and see > what > makes them tick. > > 73s, > > Bill, k6whp > > > > > Funny you should ask about the Genesis radios. They > are the > > only code plugs that I've really looked closely > at. > > > > The HT600 and P200 (except low band) are the same > radio. > > The HT600E, MT1000 and low band P200 are the same > radio. > > > > I have no knowledge of the HT600 code plug, but the > MT1000 > > code plug is straight ASCII text characters that are > positioned > > at specific byte locations in the code plug. > > > > My interest in cracking the code plug is because I > have > > several MT1000s - a 16 channel UHF on GMRS, a > 99-channel > > UHF on mixed use, > ..etc.
