- Joined
- Jul 12, 2003
- Messages
- 251
- Reaction score
- 10
Received a surplus P7350 in the original box, P25T/PV, all documentation and still has the protective film over the display. Has a LID on the casting and was programmed for a six site P25 system and some analog 700mhz simplex freqs. Last programmed with RPM10B (PERS VER 69.00) and FE still has the 40 bit string, hasn't been converted to 80 bits and the radio is running the following code;
BURN: R11A04
BOOT: R12A00
ECP: R16D07
AES: R03A06
DES: R02B08
Based on this information once I got it on the bench I read it with RPM R14C05 and when I try to save the file I get an error I've not previously encountered. "Security Key not present, file will not be saved".
Now this is curious because AAC began with RPM11, it was not a feature in R10B sooooooo whats going on? I begin perusing through the personality file and all the trunking data has been stripped out, like the radio was read with the conventional only version of RPM or when ESK/Personality lock is used except the security menu on the RPM toolbar was still grayed out and this radio does not have the feature 21 status bit enabled. When I expanded the P25 Trunked tree I found something else I've not previously seen, lock icons next to all the trunked systems.
It would seem that not all of the trunked data was stripped out. There was an IDEN table listed for the first six sites on the Alabama Interoperable Radio System (AIRS) which it seems is a hybryd Harris - /\/\ system. Also one of the trunked frequency sets is still listed and it's the Wilmer (6,6) site. No TG data is present but the radio contains all TG's not listed in the RR datatbase based on TG ID's shown on the display. Additionally, This radio does have status bit 47 enabled nor does the IDEN table in the radio have any phase II entries and that is a phase II system.
I do know that RPM has the TxWARN system hard-coded to require some additional security requirements in order to be programmed, I'm assuming that AIRS is also one of those hard-coded flagged systems? Prior to the implementation of AAC what was necessary to write/read those systems? Perhaps the same smart cards used for ESK implementation and keyloading the radios with Key Admin prior to the deployment of Key Manager? Is there any way to get around it to see what information the radio contains? I suspect the answer is no, like in the case of an ESK enabled radio.
BURN: R11A04
BOOT: R12A00
ECP: R16D07
AES: R03A06
DES: R02B08
Based on this information once I got it on the bench I read it with RPM R14C05 and when I try to save the file I get an error I've not previously encountered. "Security Key not present, file will not be saved".
Now this is curious because AAC began with RPM11, it was not a feature in R10B sooooooo whats going on? I begin perusing through the personality file and all the trunking data has been stripped out, like the radio was read with the conventional only version of RPM or when ESK/Personality lock is used except the security menu on the RPM toolbar was still grayed out and this radio does not have the feature 21 status bit enabled. When I expanded the P25 Trunked tree I found something else I've not previously seen, lock icons next to all the trunked systems.
It would seem that not all of the trunked data was stripped out. There was an IDEN table listed for the first six sites on the Alabama Interoperable Radio System (AIRS) which it seems is a hybryd Harris - /\/\ system. Also one of the trunked frequency sets is still listed and it's the Wilmer (6,6) site. No TG data is present but the radio contains all TG's not listed in the RR datatbase based on TG ID's shown on the display. Additionally, This radio does have status bit 47 enabled nor does the IDEN table in the radio have any phase II entries and that is a phase II system.
I do know that RPM has the TxWARN system hard-coded to require some additional security requirements in order to be programmed, I'm assuming that AIRS is also one of those hard-coded flagged systems? Prior to the implementation of AAC what was necessary to write/read those systems? Perhaps the same smart cards used for ESK implementation and keyloading the radios with Key Admin prior to the deployment of Key Manager? Is there any way to get around it to see what information the radio contains? I suspect the answer is no, like in the case of an ESK enabled radio.
