The remote on a phone line, finally on your dashboard.
Plenty of sites still answer only a phone — a Sine RFC-1/B sitting on a bare copper line with no IP and no SNMP. BNM dials it on a schedule, keys in the security code, walks every channel, reads back each value, logs every reading, and calls you the moment one drifts out of range. No VPN, no new box at the site — the 1980s remote alarms and dials out like any modern device.
Dialed: (615) •••-4417
Channels read: 18 / 18
A clipboard and a handset isn’t monitoring.
Thousands of transmitter sites run a Sine RFC-1/B or a Burke on nothing but a phone line. To check the rig, someone dials in with a handset, punches a security code, and copies the readings onto paper by hand — once a shift if you’re lucky. Between those calls, nobody’s watching.
BNM makes that call for you, on a schedule, and never forgets. The reading that used to live on a clipboard becomes a trended channel with a threshold and a phone number behind it.
- ✓No IP, no SNMP, no hardware change at the site
- ✓Works on the copper line that’s already there
- ✓Every call logged — an audit trail you never had
Dial, authenticate, read — then call you.
The same checks you’d run by hand with a handset — the dial, the security code, the channel-by-channel readout — automated end to end.
Reads any channel, 00–63
Whatever you’ve wired to the remote, BNM can read — forward / reflected power, SWR and percent of power, plate / PA / screen / grid current, plate and filament voltage, modulation, audio L/R.
Temperatures & environment
Building, outside and TX-exhaust temperature, plus humidity — the room conditions a phone remote already meters but nobody was watching between manual calls.
Status channels
Generator, AC power, transmitter selected, door, tower lights and tower beacon — on/off conditions logged every call, with an alert the moment one flips.
A log that writes itself
Every dial-up appends a timestamped reading for each channel — the transmitter log you used to keep by hand, built automatically and trended like any IP device.
On your schedule
Set how often it dials — every 30 minutes for tight history, a few times a day for a quiet line. BNM kicks the call when one is due and stays out of the way otherwise.
It calls you, not a screen
When a reading crosses your limit or a status flips, the same engine that placed the dial-up turns around and calls your phone — AMD, call-down list, escalation, just like every IP device.
The dial-up still wakes you up.
You set the high/low limit on any numeric channel and tell BNM which status channels matter. Critical conditions ring a phone; warnings can email or text. See how alerting routes them →
- Phone unreachable — no answer, busy, or the line is dead
- Authentication failed — the unit rejected the security code
- Channel out of range — a reading crossed your high or low limit
- Status channel changed — generator, AC power, door, tower lights flipped
- Reading parse failure — the unit’s answer couldn’t be read cleanly
The quirks of dialing a 40-year-old box, handled.
Its own phone number
BNM dials from a line dedicated to readings, separate from your voice-alert number — a poll in progress never collides with an alarm trying to reach you.
Lockout-safe authentication
The unit locks out after a few bad codes. BNM authenticates carefully and backs off rather than hammering it, so polling never bricks your access to the remote.
Stuck-channel recovery
Phone lines drop out and inactive channels come back as noise. If a channel doesn’t return a clean value within ~14 seconds, BNM skips it, logs the skip, and moves on — the call never hangs.
Test Connect, before you trust it
One button dials the unit, authenticates, and hangs up — a ~30-second proof that the line, the number and the code all work before you arm a single channel.
Put a phone number on your blind site.
We’ll dial your RFC-1/B on a test call, prove the code and the line, map your channels, and wire a dial-out so an out-of-range reading reaches your phone — not a clipboard nobody checks until morning.