Hotel / hospital / campus radios always cross-talk?
No signal in garage or tunnel?
KINGTONE Solutions fixes it in one go

Interference in hotel radio systems usually has one root cause: too many departments sharing too few channels. When reception, housekeeping, security and valet all transmit on the same analog channel, every radio hears every other radio.

The fix is channel separation, not more power. JIMTOM digital repeaters with a grouping policy assign each department its own logical channel over shared infrastructure, so departments stop interfering with each other while the physical antenna and cable plant stay as they are.

What this does not do: channel grouping reduces interference between departments; it cannot remove interference originating inside a single department's own radio pool. If housekeeping has eight radios on one channel and they all key up together, no repeater setting fixes that — the department needs more channels.

An underground car park is a genuine signal dead zone — the structure blocks line-of-sight paths, and the concrete and steel in the structure absorb what little gets through. There is no antenna placement that solves this.

Two approaches cover it:

• Fibre-based coverage (BDA) — a donor antenna picks up the above-ground signal and a low-loss fibre distribution system carries it into the parking levels. Best when you own or control the base station and want full independence from the commercial network.
• Broadband wireless coverage — a small cell or pico base station inside the structure provides coverage directly. Simpler where the operator already has usable indoor coverage above ground.

Typical projects complete in 3-10 working days once the cable route is agreed, and coverage is verified per level rather than assumed.

What this does not do: neither approach makes radio coverage a substitute for a genuinely clean RF environment. If the structure already carries a high-power transmitter on the same frequency band, expect to design around interference rather than through it.

The distinction is whether the repeater uses one channel or two.

Same-frequency (the RS3100 approach) — transmit and receive on a single channel. No frequency coordination is needed between repeater and terminals, so existing terminals work unchanged and deployment does not wait on a frequency coordination exercise. The RS3100 forwards in 90ms, short enough for natural voice conversation. It also supports off-network passthrough: if the repeater loses power or backhaul, terminals in range still reach each other directly rather than losing all communication.

Different-frequency — separate uplink and downlink channels. This eliminates any possibility of the repeater hearing its own transmission, but every terminal must be tuned to the right frequency, so it costs you either frequency coordination or a fleet-wide terminal reprogramming exercise.

How to choose: same-frequency for temporary deployment and for fleets you cannot conveniently reprogram; different-frequency where you need the strongest possible isolation between the repeater and adjacent systems. Note that same-frequency shares one channel — high-density events with many simultaneous transmissions need a different-frequency or trunked design instead.

No, and the reason is physical rather than conventional. Our uplink extractor is the RF420 and the downlink extractor is the RF430. Three things differ:

• Port orientation — the two are keyed to opposite directions. Installing one where the other belongs connects the wrong ports.
• Isolation figures — each is specified for isolation in its own direction. Swapped, isolation drops and the base station transmitter sees energy reflected back.
• Frequency planning — the two are band-specific. Using the wrong one outside its intended band degrades insertion loss and return loss.

The practical consequence is signal leakage and, where isolation drops far enough, damage to the receiver. This is not a commissioning setting that can be tuned back.

A directional coupler is not a substitute either — couplers are built for power monitoring and signal sampling, not for extracting a clean signal path with defined isolation. The result is a degraded signal and, in a poorly designed installation, an overloaded receiver.

To identify what you have: read the model marking — RF420 is uplink, RF430 is downlink. Port labels alone are not reliable, because field rework and relabelling do happen.

Not as a rule, and the distinction matters when you are planning a mixed fleet.

Our S300 dispatch console is built against JIMTOM terminals and repeaters — that combination is what we test and support. We are not going to claim otherwise for a mixed-brand estate.

What we can do is separate the two problems, because they have different answers:

• Monitoring any brand — the S200 network management platform supports multi-brand device monitoring. It reports device state and alarms regardless of who made the hardware.
• Dispatching other brands — this depends entirely on whether the terminal exposes a control protocol we support. Nothing in the monitoring path can substitute for the absence of a control interface.

So if you already have a mixed fleet, start with S200 for monitoring and tell us the terminal models you need to dispatch — that list determines whether S300 can cover them, and we will say so plainly if it cannot.

We build this as two layers, because a mine does not have one coverage problem — it has a voice-coverage problem and a data-coverage problem, and one radio type cannot fix both.

• Voice (the baseline) — the RS3500 digital repeater series, built for permanent installation and continuous unattended operation. This is the difference from the portable RS3100: RS3500 is designed to run in a mine for years, not for a few days.
• Data (the added value) — the KT-B LTE/5G private network carries personnel positioning and video backhaul over the same infrastructure where the fibre is already run.
• Command — the S300 console gives a single unified view above ground.

This is the SOL900 converged wideband/narrowband architecture, and it is what we currently deploy in emergency command, event and campus projects.

What this does not do: LTE/5G coverage underground is only as good as the fibre or cable you can physically run. If the tunnel has no route for fibre, the broadband layer cannot be installed as designed, and we will tell you that at the survey stage rather than after installation.

With the RS3100 portable same-frequency repeater, 1-3 days is realistic for 1-10 square kilometres of temporary coverage. Equipment is set up and connected on arrival, and struck down when the event ends — there is no permanent site to build.

Two reasons the deployment is this fast:

• No frequency coordination — the RS3100 transmits and receives on one channel, so there is no coordination exercise to wait on. This is the single largest source of delay in a temporary network.
• No terminal fleet changes — it works with mainstream DMR terminals, so nothing has to be reprogrammed or replaced.

Conditions and limits: the 1-10 km² figure assumes reasonable antenna height and line of sight. Concrete and steel structures change the result, and any serious deployment needs a site survey first. Same-frequency operation also shares a single channel — if your event has high-density, many-simultaneous-transmission traffic, this is the wrong architecture and you need a different-frequency or trunked design. For a permanent site rather than a temporary one, the RS3500 is the correct product.

To size this properly, tell us three things: the area and terrain, the number of simultaneous users, and whether the deployment is temporary or permanent.

Yes for monitoring, and this is a real differentiator rather than a slogan. The S200 network management platform supports multi-brand device monitoring, so equipment from other vendors can sit in the same monitoring view as ours.

There is also a multi-site dimension worth knowing about. Our Pro+ series passive components — which includes the RF420 and RF430 signal extractors — connect to S200. That brings component status into the same view as the active equipment, which is how multi-site deployments catch a degraded or mis-installed extractor before users report it as a coverage problem. Most vendors without component-level monitoring only find out from the complaint.

The boundary: monitoring capability is not dispatch capability. Whether we can control a third-party repeater depends on whether it exposes a control protocol we support; its alarm and status reporting is a different matter from commanding it. If you have specific third-brand models in mind, send us the model list and we will confirm exactly what is covered rather than answering generically.