Monitor & Control Your TX

There are actually 5 different ways you can monitor and control your equipment. Knowing, and choosing the right method could make monitoring and controlling your broadcast equipment a breeze!

OPTION 1: Use the BW’s Web Remote User Interface.

This is the classic and most used way that TXV2 users can seamlessly connect to their transmitter to control and monitor at any time of the day from anywhere in the world.

All you need is an internet connection at the location of your device and on your personal remote device.

Here is an example of how one might setup their Transmitter to be remotely accessed by a web browser or smart phone browser.

First, make sure you have a fixed line Internet connection and a network router setup at your transmitter’s location. Test the connection to the internet with a laptop to make sure you can connect to a test webpage such as

Next, give the transmitter a static IP address that is within the same subnet as the router’s IP address.

This means that if your Router (also known as default gateway) has an IP address of and a subnet mask of, then you must set an IP address on your transmitter of anywhere from through to More information on basic network configuration can be found here.

Once you have given your Transmitter an IP address, let’s say it is, make sure that under the HTTP settings menu on the front panel are set to default (HTTP Enabled on Port 80)

If your internet provider has issued your transmitter site internet connection with a public static IP address, then you will need to use Port Forwarding on your router that will point Port 80 to the local IP address of the transmitter.

If your Internet provider uses a Dynamic IP address for connection to the internet, then you will need to use a service such as DynDNS that will allow the remote connection to work effectively.

Once you have the port forwarding set, then all you need to do is enter the public IP address into your internet connected web browser or smart phone browser and the remote interface will appear!


See for yourself how easy it is to control your transmitter using the V2 Remote Control App try it here.

TOP TIP:  Send commands to your transmitter using web URL’s.

Using the HTTP connection, users are able to issue commands to the transmitter in the address bar of their browser of choice. These are known as HTTP API commands. These also allow users to issue HTTP commands from custom software that they may developed.

This gives great flexibility, especially if you want to initiate commands by simply launching a URL shortcut icon on your computer.

All of the parameters in the TX V2 can be read or set using standard HTTP requests in the fashion of, for example, (this will return the current power value of the transmitter with IP address

You can view all of the instructions of how to do this in the TX V2 user manual here on pages 43 – 46.



Telnet is a very powerful connection protocol for remotely controlling and monitoring the V2. By default, Telnet is enabled on port 23. By connecting to the units IP on port 23 using a Telnet client, you can issue text commands for any parameter on the V2.

Some popular windows based Telnet clients that people use are Putty.exe, which can be downloaded here for free or there is a telnet client built into windows, which you can learn to activate on your windows machine here.

TOP TIP:  Automate and schedule ANY V2 parameter.

You can schedule any parameter on your V2 to activate using Telnet and a Windows PC! Simple windows Batch files can be written to launch the windows Telnet client and a vbs script file can be run to set any parameter on your device. You can launch them from icons on the PC or have them automatically run when you are not at your PC. The commands can be launched automatically at any time of day using the windows task scheduler.

The below example demonstrates how you could schedule your transmitter to mute its RF output between 12 and 3am each day.

Step 1. Enable the Windows Telnet Client (Instructions here)

Step 2. Create 2 batch files by entering the below text into notepad and saving them with the .bat file extension. The first file will contain the below. The IP address shown on the second line should be replaced with the IP address of your transmitter.

: Open a Telnet window
start telnet.exe
:: Run the script
cscript C:\rfmuteon.vbs
Save this file as RFMUTE-ONBATCH.bat and then create another file called RFMUTE-OFFBATCH.bat with the below text.
: Open a Telnet window
start telnet.exe
:: Run the script
cscript C:\rfmuteoff.vbs

Step 3. Create 2 VBScript files by entering the below text into notepad and saving them with the .vbs file extension. The first vbs file will switch RF Mute on and should look like the below. (See descriptions of line beginning with :: )

:: Start the shell object
set OBJECT=WScript.CreateObject(“WScript.Shell”)
:: Wait 500ms
WScript.sleep 500
:: Send password keys and enter key (pass[Enter])
OBJECT.SendKeys “pass{ENTER}”
:: Wait 500ms
WScript.sleep 500
:: Send command keys to RF Mute
OBJECT.SendKeys “set transmitter.rf_mute.manual_enable on{ENTER}”
:: Wait 500ms, then enter a space and wait another 500ms to give the action time to take effect
WScript.sleep 500
OBJECT.SendKeys ” “
WScript.sleep 500 
:: Exit the telnet window
OBJECT.SendKeys “exit{ENTER}” 
WScript.sleep 500
OBJECT.SendKeys ” “ 

Step 4. Save this file onto the C drive as rfmuteon.vbs (so that your batch file knows what to run) Now create the second vbs file and save it as rfmuteoff.vbs. It should contain the below text and does exactly as above, but only this time it issues an “off” command.

set OBJECT=WScript.CreateObject(“WScript.Shell”)
WScript.sleep 500
OBJECT.SendKeys “pass{ENTER}”
WScript.sleep 500
OBJECT.SendKeys “set transmitter.rf_mute.manual_enable off{ENTER}”
WScript.sleep 500
OBJECT.SendKeys ” “
WScript.sleep 500
OBJECT.SendKeys “exit{ENTER}”
WScript.sleep 500
OBJECT.SendKeys ” “
Step 5. You should now see 4 files that look like the below. You should be able to launch each batch file to test them by double clicking the icon. You will then see a telnet window appear, commands entered and window close within a matter of seconds!


Step 6. You can now go to the Windows task Scheduler and schedule the RF Mute ON batch file to run at midnight, and then you can schedule the RF Mute OFF batch file to run at 3am. You should see the tasks in the scheduler look something like this.




SNMP is a great feature of the V2 and allows you to monitor the parameters of your BW V2 in real time.

Watch this short video that takes you step by step through setting up SNMP

Then, depending on your SNMP client, you can perform tasks that allow you to plot graphs of parameters over time. There are many programs on the market that can monitor SNMP data, and many of them can be complex and extremely powerful.

All SNMP information of devices are held on whats known as MIB files. The MIB file on the V2 transmitter can be found by entering

http://(UNIT’S IP ADDRESS)/api/BWB-TX-V2-MIB.mib into your web browser. Please also note that SNMP must be enabled in the Front Panel in System->SNMP->Enable.

The SNMP-> “Read Only” must be set to “off” in order to modify parameters though SNMP.

Each parameter is represented with an ID number called an OID. These OIDs can be discovered by using software known as a MIB Browser. There are free Mib browsers that can be found online and are great tools for browsing through MIB files and locating OIDs that are associated to particular parameters.

TOP TIP:  Be on top of your transmitters performance by plotting SNMP data on a graph.

SNMP data can be plotted onto a graph to represent values over time. Let’s take the forward power, reverse power and peak deviation as an example. All you need is the OIDs for these parameters, and you can use a free program called Getif to visually represent these values live over a period of time. Handy if you need to go back in time to see how your transmitter was performing.


This graph is from an open source application called Zabbix. It represents the transmitter deviation over a 2hr period.


User Datagram Protocol (UDP) is a data communications protocol that uses your IP connection to send limited messages to another device on your network.

UDP is used on the V2 to send log file messages. Logs are kept on the V2 transmitter for 1 month however using UDP enables you to send the log files to a PC and keep them for as long as your hard drive can store them.

There are some very sophisticated third party applications that can collect log file data and present the data visually. One popular application that can do this is Splunk. Splunk allows you to extract values from particular lines of the log files and represent these visually on a dashboard.

Below is a visual representation of the V2 internal power amplifier temperature – taken from the Splunk dashboard. You can also create visual alarms for when certain values meet particular criteria of your choosing. It has taken information from the V2 log file and presented it in a live thermometer style.

Splunk can also create visual graphs on power readings and any other value you can extract from the log file.

The sending of log files over UDP can be used in so many ways and this is only one. There are hundreds of third party applications that can give you in-depth representations of your transmitter’s past and present performance.



Remote control via RS232 is a great option if you do not have an Ethernet or IP connection present.

You can use terminal software to connect with a serial cable to the RS232 port on the back of your unit.

One of the best free terminal applications for serial and telnet connections is Putty, available here.

To connect to the unit via RS232 connection, connect a standard serial cable between the transmitter and the PC, and use the following settings for the COM port:

  • Baud rate – Selected Baud rate set in the Unit (default: 19200bps)
  • Data Bits – 8
  • Parity – None
  • Stop Bits – 1
  •  Flow Control – Hardware

Any text based command can be read or set using the RS232 connection. All information on text based access can be found on page 42 of the V2 manual.

Log file data can also be collected via the RS232 connection and exported to a text file. This is another great way to keep log files older than the transmitter’s internal memory can store (31 days).


If you require any assistance on setting up any of the above methods of remote control on your V2 transmitter, please contact the Technical Support Team


Thanks for sigining up

Your email has been added to our mailing list.

Close window 


Coming Soon

Close window 

Logged out

You have now logged out

Close window 

Thank You

We will contact you shortly

Close window