The Icom IC-9700 is the transceiver most consistently listed with a built-in server function for RS-BA1 Version 2, alongside the IC-7610 and IC-7851, which also carry the function natively. The IC-7300, IC-7100, and IC-7000 do not include a built-in server; they need a PC running the RS-BA1 server software between the radio and the network. That single hardware fact determines whether you can operate remote without leaving a computer powered on at the station.
The keyword asks a narrow question, but the answer depends on how Icom documents remote capability across firmware generations. A radio that "supports RS-BA1" and a radio with a "built-in server" are not the same thing, and Icom's own product pages and manuals use both phrases. This explainer separates the two, shows why the distinction matters in practice, and gives you a checklist for verifying any specific transceiver before purchase. It stays on mechanisms and documented behavior rather than on dated price or availability claims, which change and which Icom does not publish as stable specifications.
What a "built-in server function" actually means in RS-BA1 V2
RS-BA1 Version 2 is client-server software. The client is the operator interface you install on a laptop or tablet. The server is the component that talks to the radio over its serial or USB control link and exposes audio plus CAT control across a network.
In the standard architecture, the server runs on a Windows PC physically cabled to the transceiver. The radio has no idea a network exists. The PC handles audio codec work, CI-V command translation, and the network socket. If that PC sleeps, updates, or loses power, remote operation stops even though the radio is fine.
A built-in server function moves that server process into the radio's own firmware and network stack. The transceiver becomes the network endpoint. You point the client at the radio's IP address, authenticate, and operate. No intermediary computer is required at the station.
The mechanism matters because it changes the failure domain. With a PC server, you maintain an operating system, drivers, and update cycles at the remote site. With an embedded server, you maintain a radio. The embedded path removes an entire class of remote-site failures, which is why the phrase appears prominently in marketing for the models that have it.
One professional caveat: "built-in server" describes where the server process executes, not whether every RS-BA1 feature is available. Feature parity between the PC server and embedded server varies by model and firmware. Verify the specific functions you need, such as dual receive or scope streaming, against the model's manual rather than assuming equivalence.
Which Icom transceivers carry the function, and which do not
Icom's remote-capable lineup splits into three groups. The first group has an embedded server. The second group supports RS-BA1 only through a PC server. The third group predates or sits outside the RS-BA1 V2 ecosystem entirely.
| Transceiver | Built-in server for RS-BA1 V2 | Typical remote path | Notes |
|---|---|---|---|
| IC-9700 | Yes | Direct network connection | VHF/UHF/SHF, scope streaming |
| IC-7610 | Yes | Direct network connection | HF/6 m, dual receive |
| IC-7851 | Yes | Direct network connection | Flagship HF/6 m |
| IC-7300 | No | PC running RS-BA1 server | Very common remote host via PC |
| IC-7100 | No | PC running RS-BA1 server | Mobile/portable form factor |
| IC-7000 | No | PC server, legacy support | Older platform, verify firmware |
| IC-705 | Yes, via its own network stack | Direct Wi-Fi or wired | Portable, RS-BA1-adjacent remote tools |
The IC-705 deserves a note because it blurs the categories. It offers direct network remote operation through its own networking, and Icom documents remote tools that overlap with the RS-BA1 workflow. Treat it as a separate implementation rather than a strict RS-BA1 V2 embedded-server equivalent unless the manual for your firmware revision says otherwise.
The practical reading of the table: if the keyword question is about which listed transceiver has the server inside the radio, the IC-9700 is the answer most often cited, with the IC-7610 and IC-7851 as the other native-server HF-capable options. The IC-7300 remains the most common radio people try to remote, and it always needs a PC in the middle.
Why the distinction changes your station design
The server location determines your power budget, your uptime strategy, and your attack surface. Each of those has concrete consequences.
Power budget: a PC left running at a remote site draws roughly 30 to 150 watts depending on the machine, plus monitor if attached. A radio with an embedded server draws only its receive or standby current. Over a month of continuous remote availability, the difference is large and shows up as heat, fan noise, and UPS runtime during outages.
Uptime strategy: a PC server needs operating system updates, which can reboot the machine unattended. Windows Update rebooting a remote host is one of the most common causes of a dead remote station. An embedded server has no operating system in that sense. Firmware updates are deliberate and infrequent, so the station stays reachable until you choose to change it.
Attack surface: every PC at a remote site is a general-purpose computer on a network. It needs patching, firewall rules, and account hygiene. An embedded server exposes a narrower service. Neither is automatically secure, but the embedded device presents far less to defend.
Counterintuitive detail: the embedded server is not always the lower-latency option. A well-tuned PC with a wired connection and a fast processor can deliver competitive audio and CAT responsiveness because it has more CPU headroom for codec work. The embedded server's advantage is reliability and simplicity, not raw performance. Choose it for uptime, not for milliseconds.
Where the documentation gets ambiguous
Icom's phrasing creates most of the confusion around this keyword. Product pages say a radio "supports RS-BA1 Version 2," which is true for radios that only work through a PC server. The phrase "built-in server" appears in manuals and feature lists for a narrower set. Searching for the support statement alone will mislead you.
Firmware revision matters. A model may gain or refine embedded server behavior across firmware releases. The manual for the specific firmware version is the authoritative source, not a retailer's bullet list or a forum post from an earlier revision.
Regional variants exist. Some model suffixes differ in included networking or regional feature sets. Verify the exact model number and region against the manual before assuming the embedded server is present.
The RS-BA1 V2 software itself is a separate purchase from the radio. Owning a radio with a built-in server does not include the client license. Budget for the software and confirm the client version you install matches the server behavior the radio documents.
Red flags when you research a specific model: A listing that says "remote capable" without naming RS-BA1, the server location, or the firmware version. A forum answer that describes the PC server workflow and implies it applies to every Icom radio. A retailer bundle that includes RS-BA1 without stating which server the radio uses. A manual page that references a different model's networking section. Any claim that a non-networked radio has an embedded server without a network port or Wi-Fi documented.
Plain-language version: "works with RS-BA1" and "has the server inside" are two different claims, and only the second one lets you leave the computer off.
Verifying a specific radio before you buy
The verification path is short and does not require trusting secondary sources. Work from the manual backward.
Step one: open the official product page for the exact model and region. Look for the networking or remote operation section, not the general feature list.
Step two: download the full manual for the current firmware. Search within the PDF for "server," "network," and "RS-BA1." Note whether the server is described as running on a PC or on the radio.
Step three: find the network port or Wi-Fi specification. A radio with an embedded server documents an IP configuration workflow in its own menu system. If the manual never assigns the radio an IP address, the server is not inside it.
Step four: check the RS-BA1 V2 client documentation for the model list and any server-location footnotes. Cross-reference against your manual finding.
Step five: confirm firmware version and regional suffix match between the manual and the unit you intend to buy.
Step six: confirm the software license is purchased separately and that your client version supports the radio's firmware.
Threshold guidance: if two of the first three steps disagree, stop and resolve the conflict before purchase. Documentation conflicts usually mean you are reading a manual for a different firmware revision or region, and the safest assumption is the more conservative claim.
Limitations and what this article cannot settle
This explainer describes stable architecture and documented feature categories. It does not assert current pricing, current availability, or current firmware behavior for any specific unit, because those change and Icom does not publish them as fixed specifications. Confirm them against the official manual and product page for your exact model, region, and firmware at the time of purchase.
Model lineups evolve. A transceiver added to or removed from the embedded-server list after publication would not appear here. Treat the comparison table as a map of the documented categories, not a live inventory.
The article also cannot tell you whether the embedded server meets your operational needs. Feature parity, audio quality, and CAT responsiveness vary by model and firmware, and only the manual plus your own testing settle that question. For any safety-critical or regulated use of remote station control, consult the applicable rules and a qualified professional rather than relying on a general explainer.