From various Maint Manuals for the LPE200, I can see the following commands:
First, enter test mode by entering
cmd 0 radio responds by displaying TESTMODE (remembering all the below are from LPE200 documents only, so I don't know if they'll work on others)
cmd 2 = display RSSI values, live updating, on one line of your PC terminal program (press enter to quit)
cmd 2 0 = display the Weak RSSI value, as per above updates live on on line of PC terminal program, valid ranges from 35 to 100
cmd 2 1 = display the Strong RSSI value, as per above updates live on on line of PC terminal program, valid ranges from 139 to 204
cmd 30 = display tracking data
cmd 43 0 nn vv = alter tracking data values, where nn is the the field to change (numbering starts from field 0) and vv is the new value. This doesn't write the changes to E2PROM, only sets the changes. For example if you wanted to change the very first value of the tracking data as displayed (which happens to be a value for Tracking Version Number) you would enter cmd 43 0 0 x. To change the 33rd value (which happens to be the 'strong' -40dBm RSSI value) you would enter 43 0 32 x.
cmd 29 = write changes to tracking data made with above command.
cmd 71 aa bb cc = sets tracking data segment (I don't know how this differs to cmd 43 above)
where aa is the power level setting; 0=very low, 1=low, 2=high
where bb is the TX band; 0=normal, 1=talkaround
where cc is the freq band location; 0=low, 1=mid, 2=high
apparently for 800 MHz, some frequency examples break down as:
806 MHz is aa 0 0
815 MHz is aa 0 1
824 MHz is aa 0 2
851 MHz is aa 1 0
860 MHz is aa 1 1
869 MHz is aa 1 2
cmd 74 1 = turn on RF PA; cmd 74 0 = turn off RF PA
cmd 85 0 = sets PA power control loop into open loop mode
cmd 81 = display current power adjustment value for the specific band-split and band-segment selected (in cmd 71 above, I presume)
cmd 80 x = increase or decrease output power using same scale values as given in cmd 81 above.
cmd 82 1 = reads current power output level as a value that the radio power control loop is currently sensing, and places the value to the TX_PWR_SENSE location in tracking data. (again, cmd 29 needs to be issued to actually write this data)
cmd 9 = display current AFC value for master reference oscillator
cmd 9 x = alter AFC by one step, where x is 0 for decrement one step, 1 for increment by one step.
cmd 50 nnnnnnnnn = set RX frequency, where nnnnnnnnn is freq in MHz ie 815212500 is 815.2125 MHz
cmd 70 nnnnnnnnn = set TX frequency, where nnnnnnnnn is freq in MHz ie 815212500 is 815.2125 MHz
cmd 3 x = set radio to wide or narrowband operation, where x is 0 for wideband, 1 for narrowband
cmd 52 2 = check squelch status, if ?PASS 1 is given then squelch is open, if ?PASS 0 then squelch is closed.
cmd 52 1 vv = set squelch value where vv is 1 for tight (high RF threshold) and up to 159 for loose (low RF threshold). Settings above 159 are not recommended.
cmd 54 0 = unmute RX audio (and I presume cmd 54 1 mutes again)
I got these commands from the AE/LZB 119 1641/3 rev E and AE/LZB 119 3520/1 Rev 3 documents. No doubt there's plenty more commands. In fact, I wonder if programmer 'talks' in this cmd language to send just about everything it needs to: tracking data, feature encryption information, personality information, hardware version queries etc etc.
More than that, I wonder if this HDT language, and the cmd's are 'universal' across the range ie MRK, LPE, Jag, M7100 etc.
Just for interests sake, I connected two laptops together with a null modem cable and ran a terminal program on one, and programmer on the other, just to see if I could capture anything readable... at 9600_8N1, all I could see was the same string of 5 symbols (probably a 'radio, are you awake?' query).
I've got a 'sacrificial' MRK that I can & would like to experiment on, but don't know how to get it into HDT mode. How is that done for the MRK?
|
Linear Mode
