FYIthere is a program out there that "fell" out of a Motorola LAB that allows you to read and edit the GP300 codeplug directly. We do not know where it is, just that it does exist. It is generally called GP Utility or GP Tools or something like that. It looks similar to RSS but its only function is bit banging.
If you have one of the GP300 5-tone models with a display, it shows an error something like 053, and it doesn't want to accept a codeplug, you can try turning on the radio with all the side buttons pressed including PTT. This will put the the unit radio into test mode and it will accept the codeplug, if its the right model.
Yes these radios have a fuse. To access it, first pull off the top knobs. Turn the radio so that you are looking at the battery connection side. At the bottom of the metal chassis, gently insert a flat-blade screwdriver between it and the housing, and pry up.
After you have the chassis out of the housing, carefully remove the speaker/microphone header plug. Note that there are four retainer clips holding the chassis together. With your screwdriver, gently pry off the clips. Hold your finger down on them as you do this so you don't shoot them across the room.
Once you've done this, you should have the main circuit board, the metal chassis and a large shield apart. On the metal chassis, on the opposite side of the battery contacts, you will see a small circuit board. On this board is the fuse, it's usually a square white fuse. Sometimes it's round. The Motorola part number is 6580561D02, four amps.
If you are not a technician and are not experienced at disassembling radios, you must exercise caution, people have been known to wreck the housing, RF board or both just trying to get it apart, believe me it's easy to do if not careful.
You will want to check out the pages below for some very important hacking information on the GP300. Some of the codeplug structure, disabling the encryption, cloning, etc., it can all be found in these two pages.Check out page 1.
In order to program out of band frequencies into the first two bandsplits (to facillitate use in the Ham Band), follow any of the out of band instructions listed above. The software is set up all the same way and the existing modifications will work.
You will need to take some brass slugs from UHF VCO coils and replace the VHF ferrite slugs with them. Tweak them down all the way inside the coils, and they will lock on 220. Change the 3 low pass filter coils near the antenna from 7 turns to 3 turns and the 4 capacitors to 12pF. At this point you will have 1 watt output.
You will also need to modify the front end module (still working on that - as of 1/21, it's down to 1 microvolt.) You will also need to jumper around or modify the VCO low pass filter on the receive side. Deviation and power set do NOT work outside the original calibration points, and may need to be set manually with component changes. You will need to either buy or cut an antenna for 220.
03/07/02 - Update: I have removed all passive components from the input/output Chebyshev filters in the RF module and replaced them with single tuned circuits. Sensitivity is now about 0.4 microvolts, but front end noise is lower than it should be, and the squelch is still tight even at a setting of 1. Deviation is weird - about 7kHz with no encode tone, and 5kHz with PL encode.
In the GP300.MDF file make a Checksum-16 of thewhole file (the F12 option in Hex Workshop), in our case we ended up with0xF2D3 (RSS V 05.00), write this down, you might need it later.Look starting at about offset 0x402, you should see something like:00000402 02 00 94 11 5C 12 94 11 5C 12 9411 5C 12 05 00 50 05 ....\...\...\...P.05 00 = Bandsplit identifier (Note:it is at the end of the frequency assignments)94 11 = 4500 in decimal, ie 450.0000 MHz5C 12 = 4700 in decimal, ie 470.0000 MHzNote there are 3 occurances of the strings 9411 and 5C 12, the first set is the limits displayed in the Radio Wide menu(F4-F2). The second set are the TX limits for the radio. The third setare the RX limits for the radio (note that if the TX and RX limits arenot set the same the RX limits are screwed up).To figure out what hex to enter for your bandsplits you can either use the Base Convertor (in Hex Workshop), or use a calculator with a HEX --> DECIMAL conversion function. If you are using a calculator enter your limit (ie 1440 for 144.000 MHz) and convert it to hex, you should get 0x05A0. When you enter the data into the .mdf file you have to reverse the bits such that you would actually enter 0xA005 in the field you are changing.Some of the RSS packages (We don't have codeplugsfor everything, so We can't check them all) check the checksum of the .mdffile when you try and load a codeplug and return an error if the checksumof the .mdf file doesn't match the one stored in the program. If you don'tget an error when you run the RSS with the new .mdf and try and load acodeplug then you don't have to worry about the next step.If you get a corrupt .mdf file error then you will have to go back and correct the checksum in youredited .mdf file. Load the file back in your hex editor and make a Checksum-16 of the file. If you compare the new checksum with the original one for the file they probably will be different.The only way we have to correct the checksum of the file at this time is to keep editing bits and making Checksum-16 calculations until the edited file's checksum and the original match. You can either edit the Copyright statement or some of the model descriptions in the file. Just take one or a few of these insignificant bytes (some experimentation may be required depending on by how much the cheksum is out) and add or subtract a few bits of the numbers make a Checksum-16 of the file. You should notice the checksum has changed by the number of bits you added or subtracted. Keep going until the checksum's match.Once the checksum's of the files match you should be able to run the RSS, load the codeplug, and enter the frequencies within your new bandsplits with ease.Out of Band Information, Alternate Method 2First, make a backup copy of the GP300.MDF file.
That's it. Now, when you run the RSS and read the radio via the RIB, the program thinks you have the 465-495 model and you can input the frequencies in this range with out any limitation, and still have the extra out of band with the shift key. BUT, remember, you haven't changed the RF section in the radio, so you will only be able to get the radio to work up to +/-10MHz outside of its original split, if you are lucky.
Expand the radio to 16 channelsThere are several ways you can add channels to a 2 or 8 channel GP300/P110 radio. The easiest is to use a program called TK (Took Kit). This programs plugs into the normal cables and RIB and does all the work for you. TK won't work with the GP350 so don't try it. The hex method may work but has not been tested.NOTE: Ido not have any sources for TK, so don't bother asking, you're on your own.Expand the radio to 16 channels,Alternate MethodA much slower but just as effective way of doing it is to use Hex Workshop to edit the saved file. The saved file from the GP300/P110 uses some form of encryption that changes the look of the file each time it is saved in RSS. This can sometimes make the below process long and boring.First, make a backup of the codeplug file you want to edit (copy it to a .bak or something). In the event you loose track of which bit you are editing and get a Error 58, its easy to start over again.Next, load your codeplug file into your hex editor. You want to edit the byte right after the end of the serial number. Make a note of it's original value and increment it or decrement it by one and save the file.Exit the hex editor and start up the GP300 RSS.Try loading the file you just edited, you will either get an Error 21 (Radionot supported) or the codeplug will load okay (once in a while you mayget an Error 58, but this isn't very common).Note the model number that the codeplug has loaded as, and compare it to the original model number of the radio. If the nineth character of the model number is a "C" (ie. P93YPC20C1__) you have a 16 channel codeplug. Also, make sure that the rest of the model number is the same, otherwise you may have made a 16 channel codeplug on some other band!If the RSS won't load the codeplug, go back to the hex editor and change the bit again, save the file in the hex editor and try loading it again. Keep repeating this until a) you get tired and give up, b) you are successfull, or c) you edit that byte all 255 times. If you have come to point c), edit the byte to something you know that works, load it in RSS and re-save it in RSS. This will re-encrypt the file and you can continue editing.If you want to do this faster, you should check out the Hoffis pages (above) and disable the encryption for the codeplug. Heck, if you can manage to do that, you should be able to make the 16 channel modification easily then. :)
Tips:run the RSS in one DOS window of Windows 3.1x andthe hex editor in another to make swapping between the programs less painfulltry editing the byte up and down a ways and see howmany "good" loads you get, you will probably find that the "good" loadswill be somewhat grouped togetherif you aren't having much success finding many combinations which will load, re-save a good codeplug in RSS to scramble the codeplug and keep trying.Note: Sometime in 1994 Motorola changed the 2 channel radios such that if you were to hack the radio into an 8 channel model, you still get 2 channels. The change was the microprocessor to a new unit that only recognizes the common and 1 line of the channel selector. The channel switch is the same regardless of which radio you have. Only by changing the CPU can you then change the number of channels to more than 2. To tell if you can convert your radio, pop the knob off and turn the selector. If the 2 channels programmed inthe radio come up in the order 1,2,2,2,2,2... it will work. If they come up 1,2,1,2,1,2,1,2... forget it, you'd probably have to change the microprocessorto get it to work.Expand the radio to 16 channels,Alternate Method 2Depending on which firmware is in your radio, this may or may not work (see Note above).Open the GP300.MDF in your Hex editor and make a Checksum-16 of the whole file. You will need this later, so write it down. For RSS version 5.00 I got a checksum of 0xF2D3.Search for your model number in the file, you probably will come accross more than one entry so you can either change them all or change them one by one until it works.Once you find your model entry you should see something like this:0000086C 50 39 34 59 50 43 32 30 43 33 5F5F 06 1F 1004 27 40 14 20 19 50 P94YPC20C3__....'@..PIf you look at this model entry, the third byte after the model number (offset 0x87A) is a 10. This is the hex representation for the number of channels in the radio, in this case 16ch. Most of the time you will see a 0x02 or 0x08 in this position for 2 or 8 channel radios respectively. Try changing the field to 0x10 to make a 16 channel radio and see what happens. Also note the 06 at offset 0x878, this is the bandsplit for this model number and corresponds with the bandsplit entry in the table at the top of the .mdf file.The .mdf file for these radios is checksum protected and every time the RSS loads it calculates the checksum for the file and compares it to an internal reference to see if it matches. If the checksums do not match you will get an error message.The only way we have to correct the checksum of the file at this time is to keep editing bits and making Checksum-16 calculations until the edited file's checksum and the original match. You can either edit the Copyright statement or some of the model descriptions in the file. Just take one or a few of these insignificant bytes (some experimentation may be required depending on by how much the cheksum is out) and add or subtract a few bits of the numbers make a Checksum-16 of the file. You should notice the checksum has changed by the number of bits you added or subtracted. Keep going until the checksum's match.To find out if you picked the correct model number to edit, save the .mdf file and load your radio's codeplug into the RSS. Try adding channels with the Mode Utility and see what happens.Some other RSS modification tips for the GP300GP300 RSS ver.R07.00.00 31-Oct-94.If you would like to program any GP300 radio with the codeplug information previously got from another GP300 (serial number, model, freq. range etc. doesn't matter), do the following:In the file gp_2.ovl. look for signature C6 46 FC 00 9A E3 08 at offset 10949 (2AC5h) and modify three bytes from ** into 90h:Old string = C6-46-FC-00-9A-E3-08-XX-XX-**-**-**New one = C6-46-FC-00-9A-E3-08-XX-XX-90-90-90XX means the value doesn't matter, leave old values (these bytes contain segment address and may vary).Run gp300.exe and load archive file with the codeplug info previously saved on disc.Press (F8) and program any target GP300. Model number, serial and features will be copied into it.
If you want to disable frequency checking for entering out of band frequencies in RSS, try doing the following modifications:Search for 77 10 around location 3E80 and replace with 90 90
Search for 77 03 around location 3E8D and replace with 90 90One disables frequency checking on tx, the other on rx. Note that the locations will vary depending on the version of RSS.Out of band for 5-tone radiosThis seems to work on 5-tone version 2 RSS. Program your out of band frequency into either the TX or RX field, then use [shift]-F2 to leave the field. This only seems to work for +/-2MHz or so.Another thing to try is using the shift key to enter the frequencies into the field remembering to release it for the decimal point, ie. 146.9400 would be !$^.($)) just make just you are using a standard English keyboard layout.
3a8082e126