Over The Air Programming (OTAP) Part 5

This is the fifth part in a five part series of posts on Radio Management. This allows system managers to remotely configure radio units without the need of physically touching the radio. Via the Radio Management CPS, configuration updates can simply and quickly pushed to radio units.

This post discusses how Over The Air Programming (OTAP) is managed whilst the radio unit is roaming between sites.

Radio users may unknowingly change between channels, or the Radios themselves can also roam between sites of an IP Site Connect system during an active over-the-air session. If for whatever reason, a radio moves to a channel not monitored by a control station, or moves out of the coverage area of the system, any over-the-air (OTAP) operation stops. When the radio returns to the monitored channel, and registers its presence, the over-the-air operation will start once again.

Currently, to communicate with single site repeaters that are not within RF coverage of each other, multiple PCs with control stations must be set up in those areas. Depending on RF coverage, one PC  - perhaps installed at a high site - may be within RF coverage of multiple sites. In such cases, more control stations can be connected to a single device programmer.

Note that it is important that a radios profile must not be present in more than one CPS Server!

On IP Site Connect systems that have local area channels at some of the sites, there are a couple of configuration options available. If the radios usually operate on the wide area channels (i.e. a slot which is linked), and infrequently change to the local channels (i.e. a slot which is not linked), it may be easiest to have the CPS and control stations at one site monitoring the wide area channels only.

In this case, radios can only be programmed over-the-air when they become present on the wide area channel, monitored by the Control Station(s). When they are on the local channels, they are considered absent.

If some of the radios always remain on the local channels, then it is necessary to have control stations monitoring these channels (slots) in order for the CPS to contact the radios there. Depending on the RF coverage of each site; the location of the RM Server and Control Stations, all sites may not be reachable via RF from one location. Therefore a second PC with control stations must be set up within RF coverage of the local channels of other sites.

1 comment:

  1. Wayne, Thank you for all of the work that you put in to these posts.

    I have a fleet of DP4801e's and I'm managing them using WiFi, which is wonderfully quick!

    My question concerns the preservation of distinctive, per-radio, settings such as sign-on logo and - more importantly - the security PIN. As my radios are personally issued to each user, they are protected by a PIN known only to that user (and me, of course!).

    If I apply a template from the CPS, the radio ID remains unmodified - just as it would with the wired CPS with the "Clone identity" box unchecked. The PIN, however is replaced with the one in the template, meaning that all radios that are updated in a batch end-up with the same PIN.

    Can you think of a way around this - to preserve the PIN - or am I doomed to having one template per radio? Perhaps the concept of configuration sets can be pressed into service here?

    Oh, and the OTA battery management. Is that a paid-for product? It looks very useful, as one problem that we have always had is "wandering" batteries, which magically move between radios.

    Again, Thank you.



Spam comments will be removed and the poster reported to Google.