DEVA Broadcast Ltd. is an international communications and high-technology manufacturing
organization, its corporate headquarters and facility located in Burgas, Bulgaria. The company
serves the broadcast and corporate markets worldwide – from consumers and small businesses to
the largest global organizations. It is dedicated to the research, design, development and provision
of advanced products, systems and services. DEVA launched its own brand back in 1997 and has
nowadays evolved to become known as a market leader and internationally reputed manufacturer
of user-friendly, cost-effective and innovative broadcast products.
Creativity and innovation are deeply woven into DEVA corporate culture. Through successful
engineering, marketing and management our team of dedicated professionals creates futureoriented solutions to improve customers’ performance. You may rely that all issues communicated
to our crew would be addressed accordingly. We pride ourselves on our pre and post-sales support
and purchase services, which along with the outstanding quality of our radio gear have won us due
respect and the market authority position.
DEVA best-of-breed solutions have become the best sellers for our partners. The strategic
partnerships which have been formed with industry leaders during all these years that we have been
operating on the broadcasting market, have proved us a reliable business partner and a valuable
asset, as our dealers worldwide would conrm. In constant pursuit of precision and long-term
satisfaction, DEVA enhances the reputation of our partners and clients alike. Furthermore, we have
already a proven merit as a credible partner provider.
Our portfolio offers complete line of high quality and competitive products for FM and Digital
Radio, Radio Networks, Telecommunication Operators and regulation authorities. For almost
two decades of intensive software and hardware development, we have achieved a unique priceperformance and endurance of our product lines. Our company’s multitude of equipment and
services is in line with the latest technologies and key trends. The most recognizable characteristics
attributed to DEVA products are their clear-cut, streamlined design, easiness of use and costeffectiveness: simplicity of forms but multiplicity of functions.
For us there is no stage when we deem that we have reached the most satisfactory level in our
work. Our engineers are in constant pursuit of new ideas and technologies to be captured in DEVA
solutions. Simultaneously, a strict control is being exercised at each step of any new development.
Experience and hard work are our fundament but the continuous improving process is what we
never leave aside. DEVA participates on a regular basis in all landmark broadcasting events, not
only to promote its products, but to exchange valuable know-how and experience. We are also
engaged in international large-scale projects involving radio and audio solutions which makes us
even more competitive on the global market.
All DEVA products are developed and produced in accordance with the latest ISO 9001 quality
control standards.
- 5 -
Page 6
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 is an advanced SNMP V.2 telemetry tool all in a class of its own. Specically developed
to guarantee easy and exible real-time monitoring and remote control options for RVR FM Radio
Transmitters, this product brings efciency and reliability coupled with a compact and practical
design. It provides IP-based broadcast control for exceptional scalability, gives you access to a large
number of devices and supports a variety of transmitter congurations: Modular, KPS, TEX, PTX,
and BARRACUDA as a single or dual drive, as well as a 1+1 and an N+1 conguration. A quick
intervention by the competent staff in the event of a fault has never been so easy, with adjustable
alarm thresholds for all important parameters and alarms dispatched via E-mail, SMS and SNMP.
Top product performance is also achieved thanks to the LAN port for full TCP/IP remote control
and monitoring and the extremely intuitive embedded WEB server for interactive supervision. What
is more, status report via SMS is available as well with the optional GSM Modem. DB2003 also
provides a number of great additional features, such as the Factory Parameters Restore option, SNTP
for automatic synchronization of the built-in clock, as well as date and time settings in various
formats. It allows for easy rmware upgrades to ensure that your remote control device is always up
to date.
Combined with a compact and robust aluminum case, this powerful product delivers dependable
round-the-clock operation with guaranteed quality.
Product Features
• IP-based broadcast control for exceptional scalability
• LAN port for full TCP/IP remote control and monitoring
• Very Intuitive Embedded WEB server for interactive supervision
• Advanced monitoring and full control by SNMP Ver.2C
• Adjustable alarms thresholds for all important parameters
• Firmware update for future-proof operation
• Parameters Factory Restore Option
• Alarm dispatch via E-mail, SMS, SNMP
• Proved and reliable hardware for 24/7/365 operating
• Status reporting via SMS with optional GSM Modem
• Attractive price and very good price-performance ratio
• SNTP for automatic synchronization of the built-in clock
• Date & Time Settings with various formats
• Compact and Robust Aluminum Case for high RF immunity
• Easy Installation and Setup
- 7 -
Page 8
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 has three logical Telemetry Ports – Telemetry Port 1, Telemetry Port 2 and Telemetry
Port 3. Each Telemetry Port can connect to the monitored device via one of several available physical
interfaces.
INTERFACES
DB2003 has two connectors to the monitored device - COM1 and COM2. The COM1 connector
2
supports RS232 interface only. The COM2 connector is multi-functional, supporting I
RS485 half-duplex interfaces, as well as GPO1, GPO2 and GPO3.
COM1 Connector
C, RS232,
+12V
GND
1k
RXTX
12345
6789
This is a DB9 connector.
Pin 1 – not used
Pin 2 – RS232 Rx line (DB2003 receiver)
Pin 3 – RS232 Tx line (DB2003 transmitter)
Pin 4 – output +12V – can be used to switch Plug-in Control Unit interface on front panel connector
Pin 5 – common ground
Pin 6 to 9 – not used
- 10 -
Page 11
COM2 Connector
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
C bus is independent – it only uses pins on the COM2 connector. Several monitored devices
(telemetry ports) can be connected, with different bus addresses assigned to them. This is 5V bus.
Ethernet
DB2003 comes with an RJ45 connector for an Ethernet Internet connection. The main interaction
between man and machine is through the WEB-based interface. Through a WEB browser, the device
can be accessed, monitored and set up from your computer, tablet or smartphone.
- 11 -
Page 12
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 can be used with the following RVR Elettronica devices:
• Transmitter/Exciter series: PTX_LCD, PTX_DDS, PTX_LCD_DSP, TEX_LCD and Blues;
• Power Ampliers: PJ, Plug-in KPS-CA and Barracuda;
• Change-over Units.
The monitored device must be connected through a cable to the DB2003, with the relevant
Telemetry Port set up as specied in the “Telemetry Port Settings” on page 24.
You will nd details on the cables for connecting the DB2003 to the monitored device in
“APPENDIX A” on page 49.
SETTING SCENARIO
DB2003 has several communication interfaces: 2х RS232, RS485 half duplex and I2C.
DB2003 has three Telemetry Ports. Each Telemetry Port can use any of the available interfaces to
connect to its corresponding monitored device. Multiple scenarios are possible, with the monitored
devices not exceeding 3 (the number of Telemetry Ports).
Some monitored devices can be connected via RS232 and/or I2C (PTX_LCD). Plug-in KPS-CA
can be connected via RS485 or RS232, but the preferred interface is RS485, so RS232 can be available
to service the transmitter.
In accordance with their installation, the client must make the necessary cables. Details on Cables
and connectors can be found in “APPENDIX A” on page 49.
DB2003 is able to send alarm notications via SMS using a GSM modem, which is purchased
additionally. The Modem is connected to communication port “COM1” and upon activating it, that
port cannot be used to connect to a monitored device.
Depending on the selected operation mode, the DB2003 can be used for:
• passive monitoring of the monitored device, without affecting it;
• remote control of the monitored device through commands sent by an operator;
• automatic control of the monitored device by a set schedule – change of power.
DAYPARTS
DB2003 allows users to set up a weekly schedule to manage the power of the monitored device.
Not all monitored device series can be managed. This functionality is available for PTX_LCD, PTX_
LCDDSP, PTX_DDS ,TEX_LCD, Blues, Plug-in KPS-CA and Barracuda.
Users can set two levels – Low Power and Full Power. When there is an active Daypart, a command
is sent to manage the power level to Low Power. When there is no active Daypart, a command is sent
to manage the power level to Full Power.
Further details on the setup and use of Dayparts are available in “Dayparting” on page 27.
- 12 -
Page 13
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 allows you to set a value threshold for some of the monitored signals. If a value stays
beyond that threshold for a certain amount of time, an alarm event notication is sent.
The notication can be made in one way or in a combination of ways: E-mail, SNMP trap, SMS
or GPO activation.
For some signals, it is possible to monitor high and low threshold, e.g. Forward Power and
Temperature. For other signals, such as Reected Power, only the upper threshold can be monitored.
A notication is sent both when the signal goes beyond the threshold (alarm activation), and when
normal values are restored (idle).
An alarm notication is also sent when there is an event such as loss of connection with the
monitored device. No threshold or time delay is set for this alarm type. For some events, a notication
is not necessary for a signal’s return to normal status, e.g. in the case of power change.
Depending on the monitored device series, the number and type of alarms available will also
change. Logging on as admin allows you to select which ones to activate and at what thresholds.
Further details on the setup and use of Alarms are available in “Alarms” on page 28.
- 13 -
Page 14
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
This chapter lists the settings inuencing the operation of the DB2003 but having no direct
inuence on the monitored device, as well as its selection and connection.
There are two levels of login rights to the DB2003: as admin or as user. These are default
usernames, which can be changed. Each of them has its own password for access. Admin has full
access to the device and can remotely manage the monitored devices. The session is maximum 10
minutes long (subject to setup) and can be renewed. The admin session can be interrupted by an
SNMP user for a set operation.
User has limited rights. It can monitor but can not edit. It has no access to settings and cannot
change the operation mode of the DB2003 or inuence monitored devices. Its session can be set to
no time limits but can be interrupted by admin or by an SNMP user for a set operation.
HARDWARE FACTORY DEFAULT
It is recommended that the device should have no cables and power supply connected. Press and
hold the RESET button (between COM1 and COM2). Then feed power to the device, with the button
held pressed for at least 5 seconds, until all LED’s on the lower row start blinking simultaneously.
Release the button and wait for a few seconds until the process is completed and the PWR LED is on.
This procedure restores all settings to their factory defaults, including the device’s IP address.
DHCP is on. Logs are not deleted.
- 14 -
Page 15
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
This section contains information about IP Address and assignment type, DHCP enable/disable,
network mask, gateway, primary and secondary DNS, MAC address.
SNMP AGENT
The SNMP Agent section allows you to Enable/Disable agent, change agent and manager ports
and set manager address (SNMP trap receiver). The DB2003 uses SNMP version 2 – the Read/Write
community is similar to a password for read/write access. Use the agent ID to distinguish between
multiple agents in one trap receiver.
You can download the MIB le as well as test the entire route from end to end.
- 16 -
Page 17
E-MAIL
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
To receive alarm event notications by email, you must specify the receiver’s address. You can set
one or two receiver addresses.
In order for the notications to be received, the DB2003 requires an email server to re-direct them.
There are two options here:
1. You can use the address of a server you are using;
2. You can use a server provided by DEVA for the purpose .
PLEASE NOTE that notications may be ltered as spam and may not reach the receiver.
HTTP SERVER AND FTP SERVER
When the HTTP server is disabled, access via WEB browser is no longer possible. However, users
can still have access via SNMP. It is possible to change the default port – when there are several
devices with the same external IP address.
Here, you can also set the duration of the admin session. When that time elapses, and the device
is not being actively used, the session is automatically terminated to allow access to user. It is
recommended that you log out.
When setting zero duration for the user session, it becomes unlimited. It may be interrupted upon
access request by admin or by an SNMP set operation.
- 17 -
Page 18
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
It is recommended that this service should remain enabled, so the DB2003 can automatically set
its time. That ensures that the time in the system and port logs is accurate.
You can also specify another time server.
GSM MODEM
To receive an SMS as an alarm notication, you must connect a GSM Modem to the DB2003. The
modem has to have an active SIM card, with the PIN code protection disabled. Set the GSM Modem
to COM1 to enable communication. If there are no issues, Status must become Active, as illustrated
above.
In the right-hand section, set the phone numbers of up to 5 message receivers. Use the [Test]
button to make sure all of them receive the notications.
When selector “GSM Modem” is set “to COM1”, even if there is no connected modem,
communication port COM1 is not available and cannot be used to connect to the monitored device.
- 18 -
Page 19
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 has three general purpose outputs: GPO1, GPO2 and GPO3. They have identical
functionality and are hereinafter to be referred to as GPO’s. Each GPO is the TLV817 optocoupler
photo transistor collector (NPN transistor, Vce = 30V max, Ic = 20mA max). Each of the three
emitters is connected to common ground. It may be seen as a normally open contact. A Pinout is
shown in “COM2 Connector” on page 11.
You can set an appropriate alias for each GPO as a reminder of what it controls.
In accordance with its function, each GPO can be controlled by an alarm event, by ping watchdog
or manually. You can select whether an alarm event will cause opening or closing of the contact.
PLEASE NOTE that without a power supply, the GPO is normally open, which can be interpreted
as a false alarm.
With manual control or ping watchdog, you can select a stable status change or a change for a
certain amount of time (Pulse Duration).
In order for a GPO to be used as an alarm event output, the following three conditions must be
fullled:
1. The Alarm Output function must be selected;
2. In the Telemetry Port/Alarms setting, the Enabled option must be selected for GPO;
3. The GPO must be indicated in Notications/GPO. Further details on alarms are available in
“Alarms” on page 28.
In order for the GPO to be used as a ping watchdog output, you must select the relevant output
function and specify in the ping watchdog setting which GPO must be used.
For manual control of the GPO, select the relevant function. Set the required output status. You
can select a pulse type and start a pulse with the set duration. PLEASE NOTE that without a power
supply, the GPO is normally open, which can be interpreted as a false activation.
- 19 -
Page 20
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
You must enter an address to which the DB2003 must send a ping at certain intervals. When the
set number of unsuccessful attempts is reached, the selected GPO is activated. A GPO is generally of
the pulse type and cuts the power supply to the controlled device, causing a reboot.
Startup Delay sets the time for the controlled device to reboot, during which no ping is sent.
With the [Test] button, users can check the routing to the specied address.
DEVICE MANAGEMENT
Reboot Device
[Reboot Device] causes the device (DB2003) to re-start. It does not change the settings or delete
the logs. If Dayparting has been activated for any Telemetry Port, a command will be sent to the
monitored device to determine the forward power in accordance with the current time.
Restore All Except IP
[Restore All Except IP] causes all settings to be restored to their default values. It does not affect
the IP address settings, so it is still possible to connect to the device. The Timezone setting is not
changed. Logs are not deleted.
No commands are sent to the monitored devices. All Telemetry Ports are disabled, selected models
and parameters for connecting to the monitored devices are canceled.
RECOMMENDATION: Prior to taking this action, make sure you have all the data required for
restoring the connection to the monitored devices – interface, speed, address, model, etc.
- 20 -
Page 21
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
Storage Format is where you can format the internal storage. All logs are deleted. It does not affect
the settings regarding the connection with monitored devices. No additional commands are sent to
the monitored devices.
When “Warning Level” is Enabled and Used exceeds the set level, a message is shown:
The message disappears when “Warning Level” is Disabled or when the set level exceeds the
used one:
• Warning Level increases;
• Memory is freed by removing old les – use FTP client;
• [Format] – deletes ALL les – System and Port LOGs.
Firmware Update
Firmware Update installs an updated DB2003 rmware version. Unless there are explicit
instructions accompanying the rmware, it does not cause or require change in any of the settings.
It does not delete the logs. If Dayparting has been activated for any Telemetry Port, a command will
be sent to the monitored device to determine the forward power in accordance with the current time.
Notify Power Up
If you Enable the respective notication channel (Email, SMS, SNMP trap), you will receive a
notication once DB2003 boots up. For that to happen, settings for the notication channel must be
applied.
- 21 -
Page 22
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 creates two types of logs – System Log and Port Logs. The System Log can be read via
the WEB interface.
Select the desired date, Month, Year and see the Log for the respective day. With “All”, you can
select for Day all the days of the Month; if a great deal of information has been stored, please allow
for a certain delay. To quickly switch back to today’s log, use the [Today] button.
Log can be sorted by column: Data/Time, Type or Message – in descending or ascending order.
There are lters to select only the required information – for a specic time, type of log, port or
certain events.
Recording data in the System Log cannot be disabled. The System Log does not record the values
of the signals read from the monitored devices. The les can also be accessed via FTP at “sys”.
To record data in the Port Logs, this must be allowed with the relevant Telemetry Port setting (see
“Telemetry Port Settings” on page 24). Users must set the required interval for recording the data read
from the monitored device. It is recommended that a short interval (in seconds) should be set at only
one port, for a limited time. Especially in the case of a monitored Plug-in, the size of Port Logs is
too large, which makes working with them more difcult. The Port Log data is extracted from the
DB2003 and visualized in the appropriate way through specialized software.
- 22 -
Page 23
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The settings for each port are identical. This Guide is to designate each port with the phrase
Telemetry Port. The Dayparting function is not available for all monitored device series and may
therefore not be displayed on the settings screen. The number and type of alarm events is different
for each series and may differ from the ones described below.
- 24 -
Page 25
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
In this group of settings, you have to specify the device the DB2003 is to monitor/control and how
to connect to it. Setting an Alias allows the user to recognize the different monitored devices. This is
where you enable/disable the port.
Select Model & Connect
The set interface must match the one which is physically connected. The address and speed of the
connection must correspond to the ones set in the monitored device. With the I
not taken into consideration.
With different interfaces, the address can be the same for several ports, but when the connection
is over I2C, different addresses must be set to differentiate between devices. If required, set another
address into the monitored device.
The models in the PTX_LCD, PTX_DDS, PTX_LCDDSP, TEX_LCD and Blues series have
different nominal forward power. If you select another model from the same series, which is different
from the one actually connected, the DB2003 will not be able to tell the difference. The power in
W when setting alarm and dayparts thresholds will be calculated against the nominal power of the
set model. For alarms, power is compared in W, while for Target Power command values are in
percent. That will lead to a difference between the transmitter’s power and the power expected by
the DB2003.
The models from the Plug-in KPS-CA and Barracuda series differ by the number of RF Units.
When a model is set, which is different from the one actually connected, the DB2003 will not display
the data from all RF units or will try to request and display data from non-existent RF units.
It is highly recommended that you set a model precisely as the one connected.
2
C interface, speed is
Dangerous Parameters
The change in some parameters is dangerous, e.g. the change in the transmitter’s frequency. The
DB2003 has a designated mechanism to limit such actions, therefore the default Edit Dangerous
Parameters value is Disable. In this case, the dangerous parameters are not available for telecontrol.
When the selected value is Enable, the dangerous parameters are displayed and can be edited. They
are marked by a warning sign.
When you have selected the value “For a limited time”, you see a ticker counting seconds down
- this is the time in which the new value must be entered and saved. This mechanism presupposes
awareness of whether the operator’s actions are necessary.
- 25 -
Page 26
Port Log
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
With this setting, you can disable or enable the recording of a log for the respective port, and
choose the required logger interval for recording data from the monitored device. The port logs data
is extracted from the DB2003 and visualized in an appropriate way via specialized software. In order
for the software to work, the FTP server of the DB2003 must be enabled.
It is recommended that a short interval (in seconds) should be set at only one port, for a limited
time. Especially in the case of a monitored Plug-in, the size of port logs is too large, which makes
working with them more difcult.
- 26 -
Page 27
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 allows users to create a weekly schedule to control the power of the monitored device.
Not all series of monitored devices can be managed in this way. The functionality is available for
PTX_LCD, PTX_DDS, PTX_LCDDSP, TEX_LCD, Blues, Plug-in KPS-CA and Barracuda.
Two levels are set, called Low Power and Full Power. When there is an active Daypart, a command
is sent to control the power to Low Power. When there is no active Daypart, a command is sent to
control the power to Full Power.
There are 8 Dayparts selectors with identical parameters. It is possible to set overlapping values;
it is sufcient for one Daypart to be active to set Low Power.
To set values for Low Power and Full Power, the relevant value is in percent. The value in W
is calculated against the nominal power for the selected monitored device model. The Plug-in and
Barracuda series allow you to set Target Power up to 105%, while PTX, TEX and Blues – up to
100%.
When Dayparts are enabled, the setting of Forward Power is controlled by the DB2003 and the
relevant parameters are not available for telecontrol – Target Power for PTX, TEX and Blues, and
Selected Power for Plug-in: Nominal/Lower and the Nominal and Lower values. For the PTX, TEX
and Blues models, the DB2003 monitors and controls the Target Power parameter. For the Plug-in
models, respectively Nominal or Lower Power is selected via Selected Power, while at the same time
the values of the two levels must match the ones set in Dayparts. The DB2003 sends commands to
control the power but does not change the On-Air status.
For each Daypart, users must set the day of the week when it must be active. Selecting Never
disables the respective Daypart. Selecting Every Day ensures Daypart is active for the specied time
frame, regardless of the current day.
The active time frame is dened by its Start time and Duration.
- 27 -
Page 28
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
DB2003 allows you to set a threshold for the values of some of the monitored signals. When the
threshold is passed and this continues for a certain amount of time, an alarm event notication is sent.
The notication can be made in one way or in a combination of ways: E-mail, SNMP trap, SMS or
GPO activation. You must Enable/Disable the respective notication method for all Telemetry Port
alarms. That way, you can disable all alarms for this particular Telemetry Port. For each alarm, the
notication method is selected individually.
Alarms List
Alarm NameNotication
Forward Power (FWD)Low, High, Idle
Reected Power (RFL)High, Idle
Unbalanced Power (UNB) High, Idle
Temperature (t°)Low, High, Idle
Total Modulation (MOD)Low, High, Idle
PLL Lock Loss (PLL)Active, Idle
Audio Loss (AUD)Active, Idle
SWR Alarm (SWR)Active, Idle
General Alarm (GEN)Active, Idle
Foldback (FOLD)Active, Idle
Local Control (LOC)Active, Idle
Log Changed (LOG)Active
PTXTEX BluesPlug-inPJSCMLHC
üüüüüüü
üüüüüüü
üüüüüüü
üüü
üüü
üüü
üüü
ü
üü
Series
ü
ü
ü
ü
Target Changed (TGT)Active
Front Panel Access (ACC) Active
Link Loss (LNK)Active, Idle
This table shows which levels are monitored for the respective signals, as well as the available
alarms depending on the model of the monitored device. Admin can choose which ones to enable
and at what thresholds. With the Reset button, you return the counter and the timer of the respective
alarm to zero.
üüü
üüüüüüü
ü
- 28 -
Page 29
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
For some signals, both high and low threshold are monitored (Forward Power, Temperature,
Modulation), while for others - only high threshold is (Reected and Unbalanced Power). A
notication is sent whenever the value passes the threshold (alarm activation) and upon its return to
normal status (Idle).
An alarm notication is also sent in the case of an event such as loss of connection with the
monitored device. For this type of alarm, no threshold or delay is set. For some events, it is not
necessary to send a notication for the return to normal values – for example that is the case with
power change.
To set up an email notication, the following must be fullled:
• the [E-mail] button in the Notications for the alarm must be enabled;
• e-mail notication must be enabled for the entire Telemetry Port;
• a receiver must be entered in Settings> Device> E-mail. (see “E-mail” on page 17)
To set up an SNMP trap notication, the following must be fullled:
• the [SNMP] button in the Notications for the alarm must be enabled;
• SNMP trap notication must be enabled for the entire Telemetry Port;
• a receiver must be entered in Settings> Device> SNMP Agent> Manager IP. (see “SNMP
Agent” on page 16)
- 29 -
Page 30
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
To set up an SMS notication, the following must be fullled:
• the [SMS] button in the Notications for the alarm must be enabled;
• SMS notication must be enabled for the entire Telemetry Port;
• GSM modem must be connected and enabled in Settings> Device> GSM Modem. (see “GSM
Modem” on page 18)
To set up a GPO notication, the following must be fullled:
• the output must be selected from the [GPO] button in Notications for the alarm;
• GPO notication must be enabled for the entire Telemetry Port;
• the Alarm Output function must be set for the respective output in Settings> Device> GPO.
(see “General-Purpose Outputs” on page 19)
The alarm thresholds are used to highlight signal values. If the alarm is not enabled, the threshold
pass is still registered with the highlighting of the signal.
The alarm can be enabled without any Notications being selected. In this case, the main screen will
show the abnormal signal in the alarm indicators eld but will not send any activation notications.
When both the alarm and the Notications are enabled, upon activation of the alarm a notication
will be sent and there will also be an indication on the main screen.
- 30 -
Page 31
Telemetry and Telecontrol
WEB INTERFACE – HOME
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The image above shows the main panel of the WEB interface for three allowed Telemetry Ports.
The upper section contains the bar showing the port status, as well as the Alias and model of the
monitored device. On the right-hand side of the bar are the button that displays/hides the read signal
values and the button that displays telecontrol parameters . When the user has no admin
rights, this button is not active. The middle section shows the blue bar, which indicates enabled
Dayparts, as well as the power currently set.
Next comes the eld with the ve main signals. They differ in accordance with the model of the
selected monitored device. The right-hand section of the eld shows the indicators for the enabled
alarms. If the status is different from Run, this section is not displayed, as illustrated by the lower
section of the image for Telemetry Port 3.
NOTE: Screenshots are taken from simulated devices, rather than monitored ones in actual
operation. The signal values in the images may therefore not be consistent.
The values of the main signals get highlighted in red when the set alarm thresholds are passed.
This happens even when the alarm is not Enabled – as illustrated by Unbalanced Power in the upper
section of the image. The value is in red but there is no Unbalanced Power alarm indicator on the
right. The value becomes highlighted as soon as the threshold is passed, while the alarm becomes
active once the Trigger Time elapses. The value returns to black as soon as the signal is restored to
normal, while the alarm will remain on until the Release Time elapses.
Alarm indicators
alarm. The pink ones indicate which alarms have been enabled, as well as the current Idle status.
The number below the line shows the number of times the alarm has been activated after the latest
resetting. The indicators in red show active alarms. The alarm abbreviations are shown in the Alarms
List table.
. The gray eld is a placeholder, with no Enabled
Click or tap on the Alarm indicator to reset single alarm counter. Click or tap on the
to reset all alarm counters on this telemetry port.
- 31 -
bell icon
Page 32
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The second way of displaying information shows it grouped in tabs. This method is used with
Plug-in and Barracuda monitored devices.
The image above shows the Status tab. Only one RF Unit is simulated, with its status Fault due to
high current at one of the end MOS transistors. The system is set to work in low power mode.
- 33 -
Page 34
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The next tab, Alarm Log, shows the contents of the log read from the monitored device. The
following recorded logs are demonstrated here, reecting the events involved in reaching a Fault
status of RF Unit 2.
These are the Alarm Log contents of the monitored device. It is not connected to the port or system
logs recorded by the DB2003.
Plug-in records in its Alarm Log in accordance with its conguration (more on which will be
discussed further on). These logs are not affected by the DB2003 settings. They are just displayed
here. The entire log can be deleted with a command by a DB2003 operator (see “Telecontrol” on
page 38).
Next comes the Release tab, displaying the Transmitter’s units, identication serial numbers of
the entire transmitter and the separate units, as well as the rmware version in use for each unit. (The
image above shows simulated information, any resemblance to a real device is unintentional.)
- 35 -
Page 36
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The information in the Conguration tab is again grouped into sub-tabs. Sub-tab Settings display
parameters which the Plug-in user can edit through the transmitter’s front panel and some of which
can be edited even remotely via the DB2003.
Sub-tab Control Unit shows the minimum power at the transmitter’s input, under which a
changeover of exciters will be carried out if the automatic Exciter changeover mode is selected.
The Action column shows the action the unit would undertake if the upper threshold of the
respective signal is passed. Action has one of three values: Wait, Retry or Fault. Wait means that no
- 36 -
Page 37
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
action is undertaken; the event is only recorded in the log. With Retry, the set number of attempts is
undertaken to return the signal to normal value. If the attempts are unsuccessful, the status switches
to Fault and the unit switches off. When the value is Fault, the unit immediately switches off.
These are the signal limits – passing them creates Alarm log entries. These values are set by the
manufacturer during production of the transmitter. Here, they are displayed in order to inform users
of the types of situations that would lead to Alarm log entries.
This table shows the signal values for all RF Units. As with Combiner, it displays the actions
which would be undertaken by the respective RF Unit if the signal limit is passed.
For the signals which do not have a DB2003 alarm, conguration thresholds are used to highlight
the signal value. This applies to all RF Units signals.
In the conguration table of the RF Units, the high threshold for MOS current is 36А, and the
action is Retry 8. The Alarm Log image shows the attempts to restore the respective parameter to
normal. Failure has led to a Fault status.
- 37 -
Page 38
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
Pressing this button shows the parameters subject to telecontrol. This is accessible only for
users with admin rights.
For telecontrol operations to be carried out, the required new values of the parameters must be set.
Commands will be carried out after the [Save] button is pressed.
In order for the respective action to be carried out immediately, the button marked with a lightning
sign () must be pressed. There is no need to press [Save].
Plug-in Telecontrol Parameters
The image above shows the telecontrol parameters for a Plug-in transmitter. All parameters subject
to telecontrol are displayed, due to the fact that Dayparts are Disabled.
- 38 -
Page 39
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
This image shows the telecontrol parameters for a Plug-in transmitter when Dayparts are Enabled.
The power control parameters are under the control of Dayparts and cannot be managed remotely by
an operator – the Nominal/Lower Power button and the values for the two thresholds.
The [Change Exciter] button causes an exciter changeover. For that action to be successful, the
exciter changeover mode must be “Manual” (that is not the case in the image above). Pressing this
button is equivalent to performing the same action through the Exciters menu on the transmitter’s
front panel.
The [Alarm Reset] button cancels the Fault status. It is equivalent to pressing the same button on
the transmitter’s front panel.
The [Clear Alarm Log] button deletes the transmitter’s log. WARNING: This action is irreversible
– once deleted, the Alarm log data cannot be restored.
The [Sync Time/Date] button synchronizes the transmitter’s time (used in the Alarm log) with that
of the DB2003. The DB2003 cannot be aware of the Plug-in time, so it is impossible to know what
the correction is when this action is performed.
The difference between Plug-in time and DB2003 time can be inferred from the System Log data
of the DB2003 when “Alarm Log” is Enabled:
The time shown in the Date/Time column is from the DB2003, while the time in the Message
column is from the Plug-in.
The time synchronization command for Plug-in is rounded off in whole minutes, without seconds.
This means that when the button is pressed, the DB2003 receives a synchronization request and in
fact sends a command to the Plug-in shortly before the start of a new minute.
- 39 -
Page 40
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The images below illustrate the effect of the Edit Dangerous Parameters setting for the PTX_LCD
models. In the rst image the value is ‘Disabled’ and the dangerous ‘Frequency’ parameter is not
available for telecontrol.
In the second image the value of the Edit Dangerous Parameters setting is ‘Enabled’, and the
dangerous ‘Frequency’ parameter is available for telecontrol. It is also marked by a warning sign.
In the image below the value of the Edit Dangerous Parameters settings is ‘For a limited time’ and
the dangerous ‘Frequency’ parameter can be edited in the remaining time indicated in the gray bar (in
this case 45 seconds). Once that time elapses, the new value will not be accepted.
It is recommended that the frequency change should be made separately, without any other
parameters being changed when the [Save] button is pressed.
- 40 -
Page 41
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
In all three images above, Dayparts are Enabled and Target Power is not available for telecontrol.
In the image below, Dayparts are Disabled and Target Power is available for telecontrol (there is no
blue bar).
Set the new values and press the [Save] button to send a command to the transmitter. There are no
buttons here with immediate action (marked by a lightning sign). All commands are sent when the
[Save] button is pressed. The more parameters are edited, the more time will be needed for sending
the commands to the transmitter. Once the process is completed, the current values of the transmitter
are displayed. Due to the large number of hardware varieties, some commands may not be carried
out in accordance with user expectations. Please make sure all settings are correct after the process
is completed. If necessary, repeat the action.
- 41 -
Page 42
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
SNMP is a convenient way of integrating the DB2003 into systems for automatic monitoring and
control of multiple transmitters. It can be used with the help of a free Android application to check
on the status or apply additional settings to the transmitter through a smartphone when the time or
location is inconvenient.
This Guide uses screenshoots from iReasoning MIB Browser Personal Edition – a free-of-charge
version of an excellent software tool of sufcient functionality.
SNMP AGENT
For SNMP to work, SNMP Agent must be Enabled and the respective ports must be routed. Go
to Settings> Device> SNMP Agent to set as Manager IP the IP address of the computer which is
running the trap receiver.
Set an appropriate value for Agent ID in order to be able to identify the sender in the case of
several DB2003’s sending traps to the same receiver.
With the [Test Trap] button, you can check the negotiability of the entire route.
DB2003 uses SNMP v.2, with Read/Write Community serving as a password for granting reading
and writing access respectively. Default values are shown. It is recommended those should be
changed for security reasons.
- 42 -
Page 43
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The latest version of the MIB le can be downloaded from the DB2003 with the press of the
[Download] button in the SNMP Agent section on Settings> Device. This will download the
DB2003-MIB.zip le containing DB2003-MIB.mib. Loading this le in the MIB browser will give
you the following tree:
In the “product” folder are OID’s which allow users to identify instances of DB2003 – each
manufactured device can be unambiguously identied by ‘sernum’ (it’s serial number).
The “settings” folder corresponds to Settings on the web page: under “device” are settings related
to the DB2003 itself, while the“telemetry Port” folders contain settings related to the monitored
devices connected on each port – General, Dayparts and Alarms.
Under the “telemetry” folder are OID for readings – this is information read from the monitored
device.
There are folders for every Series containing a Readings Table. The table has three columns – one
for each telemetry port.
For example, Telemetry port 2 monitors a PTX. The “port2” column shows readings from the
PTX. The other columns show “bad PID” – there are no PTX’s connected to these telemetry ports.
The table index starts from a zero value. The index for port1 is therefore 0, the one for port2 is 1,
and the one for port3 is 2.
- 43 -
Page 44
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
The table for PTX_LCD is indexed by OID ptxPortIdx, the one for TEX_LCD is indexed by
texPortIdx, etc., each with values 0, 1 and 2 for the respective port.
For access to a separate signal, add the port index to the OID. For example, OID ptxFreq has the
following value:.1.3.6.1.4.1.35833.2003.3.1.1.1.4
For access to the signal from port1, add .0 to the OID:
.1.3.6.1.4.1.35833.2003.3.1.1.1.4.0For access to the signal from port2, add .1 to the OID:
.1.3.6.1.4.1.35833.2003.3.1.1.1.4.1For access to the signal from port3, add .2 to the OID:
.1.3.6.1.4.1.35833.2003.3.1.1.1.4.2
The “kps” folder contains several tables. They allow users to work with transmitters from the
Plug-in and Barracuda series. The kpsTable contains information on Control Unit, Power Supply,
Combiner, etc., without RF Units. It is indexed by Telemetry Port – 0, 1 and 2. The parameters for
telecontrol of the transmitter are here.
There are three more tables here. These are for RF Units: tm1kpsRFUnitsTable,
tm2kpsRFUnitsTable and tm3kpsRFUnitsTable. Select the appropriate one in accordance with the
Telemetry Port where the transmitter is connected. These tables are indexed by RF Unit. The number
of columns is determined by the number of RF Units of the selected model. Their content is similar
to that of the WEB interface in the RF Units\All RF Units sub-tab.
The remaining three tables in the “kps” folder – tm1kpsAlarmLogTable, tm2kpsAlarmLogTable
and tm3kpsAlarmLogTable, allow users to read the transmitter’s Alarm Log. Select the appropriate
one in accordance with the Telemetry Port. These tables are indexed by the number of log entries.
There may also be no entries. The kpsTable provides a kpsALogAlter ag, indicating a new entry.
This table also provides kpsALogLines (number of log entries) but when the maximum length of
the log is reached, this value is saturated. The image above shows the Alarm Log of a transmitter at
Telemetry Port 1 – the index is arranged by rows for clarity. This is the same content as that shown
above from the WEB interface’s Alarm Log tab.
- 44 -
Page 45
SNMP GET & SNMP SET
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
Some of the signals have read-only Access. These are the values read from the monitored device
or the DB2003. In the MIB Browser read-only OID’s are marked with a green leaf. Other OID’s have
read-write Access. In the MIB Browser they are marked with a pen.
By entering an appropriate value, you can perform telecontrol of the transmitter or a DB2003
setting. The same parameters are available to edit here as the ones available for telecontrol through
the WEB interface.
By completing an SNMP set operation, a session is created in the DB2003. If another session has
been running at the same time by admin or user, it is terminated. The duration of the SNMP session
is selected in the SNMP Agent settings – Session Timeout. With a new recording operation, the
duration of the session is renewed. With SNMP reading, no new session is created and it not affect
the access of other users.
- 45 -
Page 46
SNMP TRAP
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
I. TERMS OF SALE: DEVA Broadcast Ltd. products are sold with an understanding of “full
satisfaction”; that is, full credit or refund will be issued for products sold as new if returned to the
point of purchase within 30 days following their receipt, provided that they are returned complete
and in an “as received” condition.
II. CONDITIONS OF WARRANTY: The following terms apply unless amended in writing
by DEVA Broadcast Ltd.
A. The Warranty Registration Card supplied with this product must be completed and returned
to DEVA Broadcast Ltd. within 10 days of delivery.
B. This Warranty applies only to products sold “as new.” It is extended only to the original enduser and may not be transferred or assigned without prior written approval by DEVA Broadcast Ltd.
C. This Warranty does not apply to damage caused by improper mains settings and/or power
supply.
D. This Warranty does not apply to damage caused by misuse, abuse, accident or neglect. This
Warranty is voided by unauthorized attempts at repair or modication, or if the serial identication
label has been removed or altered.
III. TERMS OF WARRANTY: DEVA Broadcast Ltd. products are warranted to be free from
defects in materials and workmanship.
A. Any discrepancies noted within TWO YEARS of the date of delivery will be repaired
free of charge, or the equipment will be replaced with a new or remanufactured product at
DEVA Broadcast Ltd. option.
B. Parts and labor for factory repair required after the two-year Warranty period will be billed
at prevailing prices and rates.
IV. RETURNING GOODS FOR FACTORY REPAIR:
A. Equipment will not be accepted for Warranty or other repair without a Return Material
Authorization (RMA) number issued by DEVA Broadcast Ltd. prior to its return. An RMA number
may be obtained by calling the factory. The number should be prominently marked on the outside
of the shipping carton.
B. Equipment must be shipped prepaid to DEVA Broadcast Ltd. Shipping charges will be
reimbursed for valid Warranty claims. Damage sustained as a result of improper packing for return
to the factory is not covered under terms of the Warranty and may occasion additional charges.
- 47 -
Page 48
PRODUCT REGISTRATION CARD
• All elds are required, or warranty registration is invalid and void
Your Company Name
Contact
Address Line 1
Address Line 2
City
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
Which DEVA Broadcast Ltd. product did you purchase?
Product Serial #
Purchase date / / Installation date / /
Your signature*
*Signing this warranty registration form you are stating that all the information provided to DEVA Broadcast Ltd. are truth and correct.
DEVA Broadcast Ltd. declines any responsibility for the provided information that could result in an immediate loss of warranty for
the above specied product(s).
Privacy statement: DEVA Broadcast Ltd. will not share the personal information you provide on this card with any other parties.
- 48 -
Page 49
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
Cables must be shielded with a metal braid. The screen is soldered to the connectors’ casing. The
conductors must have be at least 0,22 sq. mm (23 SWG) across. Install the DB2003 close to the
monitored device and make sure the cables are not unnecessarily long.
COM1 CONNECTOR
The COM1 Connector services only one RS232 interface of the point-to-point variety. The cable
has one connector on each end – Male and Female. The connections are direct – Pin 2 to Pin 2, Pin 3
to Pin 3, Pin 5 to Pin 5 and Screen to Casing.
DB2003 COM1 to RS232 on Monitored Device
COM2 CONNECTOR
The COM2 Connector services three interfaces and GPO. At the most, four cables will come out
of the connector:
• Cable 1 to RS232 connector on monitored device;
• Cable 2 to RS485 connector on Plug-in (only Plug-in series models use RS485);
• Cable 3 is for I2C bus;
• Cable 4 is for GPO, if used.
The gures below represent diagrams of the separate cables. When making your cable, please
keep in mind that in all gures, COM2 could designate the same connector. At the most, the four
cables will use four connections to the common ground. Only three pins are available, one of which
will have to be shared by two cables.
- 49 -
Page 50
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
Devices from the PTX_LCD series offer two interfaces to connect to DB2003 – I
RS232. The REMOTE connector, type DB15 must be used for an I2C connection. Use “Cable 3”(see
2
“APPENDIX A” on page 49). If you connect multiple devices on the I
C bus, each device must have
a unique address. In the device screen menu, under the “General Set” page, the parameter is named
“UART Adr.”. The same value is used for the I
2
C bus address. In the DB2003, it is designated “Bus
Address” and is valid for all interfaces.
The RS232 connection can be made in two ways. On the PTX_LCD side, you can use the RS232
connector, type DB9. On the DB2003 side, you can use the COM1 connector and a straight cable, as
described in “APPENDIX A” - “COM1 Connector”. The second way is to use the COM2 connector
and “Cable 1”. When 2 devices are connected via RS232 (on COM1 and COM2), they can use the
same address value. It is important to set in both DB2003 and PTX_LCD the same values for Bus
Address and for Bus Speed.
2
C bus and
PTX_DDS and PTX_LCDDSP
Devices from this series use only an RS232 connection and it can be made in two ways. On the
PTX_DDS/PTX_LCDDSP side, use the RS232 connector, type DB9. On the DB2003 side, you can
use the COM1 connector and a straight cable, as described in “APPENDIX A” - “COM1 Connector”.
The second way is to use DB2003 connector COM2 and “Cable 1”. When 2 devices are connected
via RS232 (on COM1 and COM2), they can use the same address value. It is important to set in both
DB2003 and PTX_DDS/PTX_LCDDSP the same values for Bus Address and for Bus Speed.
Devices from the PTX_DDS and PTX_LCDDSP series have a REMOTE connector but it cannot
be used with the DB2003.
TEX_LCD and Blues
Devices from the TEX_LCD and Blues series use only an I
2
C bus connection, using the REMOTE
connector, usually type DB15. Use “Cable 3”. If you connect multiple devises on the I2C bus, each
device must have an unique address.
Devices from the TEX_LCD and Blues series have an RS232 connector but it cannot be used with
the DB2003.
PJ Ampliers
Ampliers from the PJ series use only an I
2
C connection. Usually, the connector is of the DB9
type and is designated ‘I2C BUS’. Use “Cable 3” from “APPENDIX A”. If you connect multiple
devices on the I2C bus, each device must have an unique address.
PJ ampliers have an RS232 connector but it cannot be used with the DB2003.
- 51 -
Page 52
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria
Ampliers from the Plug-in series offer RS485 and RS232 connectivity. For the RS485 connection,
use “Cable 2”. The Plug-in connector is positioned on the rear panel of the Control Unit, type DB9
female, designated ‘RS485’.
On the front panel of the Control unit, there is a connector designated RS232. The Plug-in is
accessible from this connector, but this is not recommended. Leave this connector available to
service the transmitter. These two connectors share the same UART. When RS232 is used, the other
connector (RS485) is disabled internally. The DB2003 considers this as Link Loss and if the alarm is
enabled, notications are sent.
- 52 -
Page 53
65 Aleksandar Stamboliyski Str., 8000 Bourgas, Bulgaria