Older RPM help.

[TDR-94]

I still stand by my comment that a team of chimps coded all this software.

Well,at about this point with having "all" the Flash and DSP files and Programmer R18B02 AND RPM14C05, a "chimp" could have already created a personality and successfully loaded into all these radios by now!

There is obviously something you're missing or not understanding.

 

[merlin]

Not when all you deal with is errors.
Yea, an example of what I deal with--I have 2 LPE200s cloned, 3 edacs systems- 47 groups--5 conventional systems-
37 conventional channels. both radios work just fine, save for one tiny difference. One of those 37 channels on one of those radios doesn't transmit. It does receive. Now have one of those expert chimps explain that one.
Now I do have 2 channels set for digital, one aegis and one provoice, but they transmit plain analog. 'That' may be something overlooked but consider,, I have the big book here in front of me, made a full checklist, reprogrammed a dozen times and just doesnt do what the book says it should. It isn't about understanding, it isn't that hard or complicated. That is just one example of hundreds I deal with.
All the flash and DSP files short of an Orion that just won't talk to a computer etc. so about 22 sets.
DSP is easy, if need be, I can write my own DSP firmware in having the needed development package.
(thinking sending one of these off with D-star for the ham world)
Thanks for the input though.

 

[TDR-94]

Do any of those radios have both Aegis and ProVoice enabled in the features menu? If you are copying a personality from a radio, editing it, and then programming it back into other radios,it could quite possibly be replicant error. That's a bad practice. Create a new master personality file from scratch and use that to program the radios.

 

[merlin]

Yes they have aegis and provoice. some of the original channels talk digital, a couple I added with the same settings don't. only difference is frequency.
You are going to have to detail what replicant error is. I have yet to encounter any errors that were not the fault of the programmer and usually a wrong setting.
I just got done building up another P7100ip, used the LPE200 personality as a template and it works.
A difference is using RPM 14 for the 7100, but everything was verbatim. 14 doesn't like the 200s.
Still haven't solve the no TX on one channel, one radio of 4. ?????
Key down, backlight lights, no beep, no icon, no RF out. the RX works fine.

 

[TDR-94]

RPM14 doesn't support LPE-200's, only Programmer.

I'm still leaning towards end user errors and not the software.

 

[merlin]

Guess I should have worded " 14 doesn't like the 200s. " differently.
I DO have complete lists of radios each of these softwares do and don't support.
I did discover the 200s are doing digital, seems they are fixed in narrow band and the deviation is way down.
I tried changing the feature data, but they revert when power cycled. Hardware issue no doubt.
They don't do G-star or T99 either so there goes a repeater notion. Been busy making PTT fixes for the P7100s and 700Ps. A few nice faceplates in the lot. Next is a break to work on my spectrum analyzer, Calibration is slipping but still self calibrates, just have to know what it is telling you.

 

[TDR-94]

Unless you are referring to changing the "tracking data",you can't modify the "feature data" to work with other radios or enable features in the existing radio. Each feature string is generated specific to each radio.

 

[TDR-94]

Still haven't solve the no TX on one channel, one radio of 4. ?????Key down, backlight lights, no beep, no icon, no RF out. the RX works fine.

The Flash or DSP could be corrupted in that particular radio.Try loading the correct "P" series Flash and "I" series DSP version, for the LPE-200, into that particular LPE-200 again.Don't use a copy of the Flash or DSP that was pulled from another radio.

 

[merlin]

The Flash or DSP could be corrupted in that particular radio.Try loading the correct "P" series Flash and "I" series DSP version, for the LPE-200, into that particular LPE-200 again.Don't use a copy of the Flash or DSP that was pulled from another radio.

That doesnt have any effect. one notion is a bad memory cell in the eeprom, but the self tests pass.
Same thing with a wiped radio and a virgin DIY codeplug.
Getting to be a lot of work for old radios I can't license. Some hardware work, I can put these on 33 Cm.
Chop out the 800 Mhz parts and use IFs with transverters for anything. no longer an easy task with only one poor eye left.
If I can reach a goal of getting all the functions hex codes, an SDR is still in mind.

 

[TDR-94]

Well,it was worth a shot.I've had 700P/Pi's that would power-up with no display, other's with just a battery icon along with other functional weirdness. Turned out to be either corrupt Flash and DSP or personality files in the radios.

It's quite possible that it's the eeprom,given the age of the radio.

 

[merlin]

Those jaguar 700Ps are really the only radios I fave bad problems with. If not picky program versions it is hardware issues.
I have one that worked, my own personality. went to change that with another and get wrong version errors and won't re program. Odd part is using the same RPM, now wrong version ??? Go figure.

 

[TDR-94]

If the personality was created with RPM and you tried loading it into a radio that was last programmed with Programmer, it will give you an incompatibility error. You can take a personality that was created with Programmer and load it into a radio that was programmed with RPM,but not the other way around.

 

[TDR-94]

I didn't word that the correct way.

If you create a personality in RPM and then try to open it with Programmer it will give you a newer version/incompatibility error. If you take a personality that was created with Programmer and then open it with RPM then there usually isn't any issue. You will also get the same error if you try to open a personality that was created on a newer version of RPM and try to open it with an older version of RPM.

 

[merlin]

Yea, I have that all figured out. There still has to be comparability with the firmware files though.
8 files make up the software in the radio and they all have to play well together.
I used a personality from an LPE200, put it in jaguar 700P and it worked, but doesn't always go that way.
Took a break and built an MRKII UHF, had to recover and that worked but get an error 'wrong radio type' with a bare personality I made up for it. Radio type 46, it works, type 50, it doesn't. (same files for the recovery)
Oh well, a quick faceplate change and I will have another working Jag 700P.
Hey, personality files for RPM have a different extension than programmer, you have to read it from the radio.

 

[merlin]

Well,it was worth a shot.I've had 700P/Pi's that would power-up with no display, other's with just a battery icon along with other functional weirdness. Turned out to be either corrupt Flash and DSP or personality files in the radios.

It's quite possible that it's the eeprom,given the age of the radio.

I get that with a missing or corrupt personality. One of my jag's is nuked, any attempt to read/write to the radio, it reverts to radio startup. All but the brain board is now in parts box.