- Joined
- Jan 24, 2010
- Messages
- 480
- Reaction score
- 83
Is there a way to clone personalities between radios without overwriting P25 and MDC IDs?
Well, you could just program the current personality into a different radio, but then you'd have duplicate ID'S on the system which is never a good thing.
We always save a pers file for every radio with the name starting with the last 5 of the serial. We update the IP, ID & OTAR ID, then save. That way, we always have a pers file that we can quickly blow into a radio when it comes back from maint.
I use “override and program” all of the time in RPM14, but I haven’t commented because I don’t use this feature in RPM2. I don’t have enough RPM2 compatible radios! In 14, when you hit override and program, you get an additional window with all of the programmable IDs listed. From there, you can edit the IDs without actually modifying the plan. There’s even an increment button that moves the IDs by one, which works well when you are running a small system (like my personal P25C system), but not so much if your one of several shops programming for a statewide network…
-B
I use “override and program” all of the time in RPM14, but I haven’t commented because I don’t use this feature in RPM2. I don’t have enough RPM2 compatible radios! In 14, when you hit override and program, you get an additional window with all of the programmable IDs listed. From there, you can edit the IDs without actually modifying the plan. There’s even an increment button that moves the IDs by one, which works well when you are running a small system (like my personal P25C system), but not so much if your one of several shops programming for a statewide network…
Rpm2 can use a csv file for programming IDs and IP addresses too. No need for more than one personality.It's the same with RPM2, just looks different.
Makes senseWe have multiple systems in each radio, so that would become a nightmare with the multiple IDs per radio. Also, not every radio is programmed the same, talkgroups, zones, etc. Having a pers for each serial number makes things very easy and no need to figure anything out.
Yep that makes sense. Did you look into Vida ID at all? It'll provision all the personalities over the air like OpenSky. You can change them on the fly in the field also.Edit:
None of the IDs or IPs are real or valid and are only used as examples.
Example:
Radio 1 might have the following:
4 systems
6 zones
3 TRS IDs: 280032, 3610345, 1451764
1 IP: 192.168.32.192
1 OTAR ID: 280032
Radio 2 might have:
2 systems
2 zones
2 TRS IDs: 345041, 3615003
1 IP: 192.168.61.47
1 OTAR ID: 345041
Radio 3:
1 system
1 TRS ID: 190007
1 IP: 192.168.9.2
1 OTAR ID: 190007
The police department might have a large number of different programming templates that cover all of their individual units, so a hostage negotiation radio will have different programming than a school RSO and on down the line. Each unit defined what they wanted programmed. With countless templates and IDs from a lot of different systems, it can become overwhelming very quickly and it is very easy to make a mistake. My coworker and I check each others work well in advance of programming, so there is no question that it is right when we issue out radios. We also send out a lot of radios for RMA and when they come back, 9 times out of 10 they are unprogrammed. It is extremely easy to look up the pers file based off of the serial number and program. No need to look up several databases for the correct IDs for that particular radio.