VHF P7100 P25 fault

[Syncopations]

Okay, this is weird. Last night, my P7100 was working fine. P25 was coming in as clear as digital can be. Well, this morning, I reprogrammed the radio with an updated personality. When the radio rebooted, I get a FEAT ERR ERR=0553. Now, neither RPM or Radio Maintenance can read the radio. Oddly enough, it appears the radio can still decode P25. However, I can no longer see the feature options and the SYS, TRK, and CNV all show as 0.

Does anyone have any idea as to what might have happened?

 

[Radioman96p71]

Looks like you need to recover the radio with a good backup of the tracking and feature data. Here is the definition from the service manual:

PIFEAT_TRACK_ERROR SOFTWARE 553:
Tracking data failure. Radio will revert
to the default tracking data set. Tracking
data needs to be re-loaded, or (if a copy
of tracking data not available) radio
needs to be re-calibrated.

 

[DisasterGuy]

A lesson to ALWAYS backup tracking and feature data.

 

[Syncopations]

A lesson to ALWAYS backup tracking and feature data.

Unfortunately, I don't have the tracking and feature data on this computer. It was lost when my other computer crashed. I never backed it up on the new computer. Am I screwed?. I do have the FEATDATA 1-3.

 

[Radioman96p71]

You'll have to manually enter the feature data and the tracking will need to be reset. For RX its not as critical but you'll probably want to get that re-aligned to allow it to track properly.

 

[Syncopations]

You'll have to manually enter the feature data and the tracking will need to be reset. For RX its not as critical but you'll probably want to get that re-aligned to allow it to track properly.

How can I have the tracking and reset?

 

[Radioman96p71]

To properly align the radio you'll need access to a service monitor and some other test gear. Probably not something you have laying around. There are some default tracking files that come with ProGrammer that can get you CLOSE but it's not going to be ideal.

 

[Syncopations]

To properly align the radio you'll need access to a service monitor and some other test gear. Probably not something you have laying around. There are some default tracking files that come with ProGrammer that can get you CLOSE but it's not going to be ideal.

I tried the default tracking from ProGrammer. Didn't work. I'm bummed out about this. I liked that radio.

 

[Radioman96p71]

There is a listing on eBay right now to service/align those radios. You might give that a shot.

 

[Syncopations]

Okay, I was able to get the tracking data from another P25 radio. As a matter of fact, the other radio came from the same agency my radio came from, and the new owner of it is a friend of mine. Using the tracking from his radio, and DSP from my radio and the feature data from my radio, I was able to partially recover the radio. I'm now able to program the radio, however I still get the FEAT ERR ERR=0551. The radio still decodes P25 and analog. Now, whenever I transmit to the VCALL stuff, analog works as intended. When I programmed a VCALL channel in P25 and transmitted, I got a DIGV ERR error, but the radio still transmitted in P25 and the scanner was able to successfully hear the P25.

A few things:

1) Can anyone spare the FLSH VER file J2R16D01 and the DSP file F4R06K02 for P7100(system) VHF? If you can't, please don't answer. If you can, or if you have comments regarding this particular question, please send me a private message.

2) I read the feature data from my friends radio. His set has 16 sets(octets?), mine has 18. I noticed that some of octets(??) repeat from FEATDATA 2 and 3. Is that normal? I can send images of the feature set from the radio taken before the radio screwed up. If you can help, private message please.

Thank you to everyone who has helped me and those to may be able to help.

 

[nucleaireqc]

not add four zero for the end (00 00) exemple FEATDATA 1 01B******F98 FEATDATA 2 F7E0F**C492F FEATDATA 3 294**07D0000 (THE END ZERO NOT ADD FEATURE ENCRYPTION DATA)

 

[DisasterGuy]

Why are.you messing with the feature string? Did purchase a new.feature and it was provided by TAC?

 

[Syncopations]

The whole radio freaked out on its own. I had to do a recovery and had to put the feature string back in. Unfortunately, I didn't have a backup of it. I did, however have pictures of FEATDATA 1-3 that I took before the radio went out. I put those in, and got the radio to work....somewhat.

I'm able to power up the radio and program it again. I do get a 0551 error on power up, but everything works. I can TX on analog just fine. I can TX on digital(P25 and ProVoice), but I get an error which I assume means "Digital Version" error, but a scanner tuned to the digital frequency receives the digital voice with no issues either. The radio can decode digital traffic with no problem we well.

Why are.you messing with the feature string? Did purchase a new.feature and it was provided by TAC?

 

[nucleaireqc]

The whole radio freaked out on its own. I had to do a recovery and had to put the feature string back in. Unfortunately, I didn't have a backup of it. I did, however have pictures of FEATDATA 1-3 that I took before the radio went out. I put those in, and got the radio to work....somewhat.

I'm able to power up the radio and program it again. I do get a 0551 error on power up, but everything works. I can TX on analog just fine. I can TX on digital(P25 and ProVoice), but I get an error which I assume means "Digital Version" error, but a scanner tuned to the digital frequency receives the digital voice with no issues either. The radio can decode digital traffic with no problem we well.

Everything works? you speak in digital and it does not give you an error (DIGV_error)?

I could perhaps give you remote assistance.