User Manual: Command Console Application

USER MANUAL
Command Console Application
DMV d.o.o, Kraljevića Marka bb, 18000 Niš, Serbia, tel/fax: +381 18 4591 556, 4591 552, e-mail: info@dmv.rs, www.dmv.rs
UP856 Command Console User Manual
Table of content
1 INTRODUCTION.........................................................................................................................4
1.1 About the Manual..............................................................................................................4
1.2 About the app....................................................................................................................4
1.2.1 Supported Devices and Operating Systems..........................................................................4
2 DOWNLOADING THE APPLICATION............................................................................................5
2.1 Download from the site.....................................................................................................5
2.2 Downloads via android app: DMV App Store......................................................................5
3 CONNECTING TO THE DEVICE FOR THE FIRST TIME....................................................................6
3.1 Logging in..........................................................................................................................6
3.2 Initial interface...................................................................................................................6
3.3 Discovering and adding devices..........................................................................................7
3.3.1 Discovering device over LAN (Local Area Network)..............................................................8
3.3.2 Discovering devices via Wi-Fi................................................................................................8
3.3.3 Discovering devices via Bluetooth........................................................................................8
3.3.4 Discovering devices by cable (serial RS232 communication)...............................................9
3.3.5 Discovering devices via SMS.................................................................................................9
3.3.6 Downloading data from the Internet before going to the device location........................10
3.3.7 Downloading data from the internet after discovering the device....................................10
3.4 List of discovered devices.................................................................................................10
3.5 Techniques.......................................................................................................................11
4 WORKING WITH DEVICES........................................................................................................11
4.1 Adjusting device display...................................................................................................11
4.1.1 Scenarios and panels in DMV devices................................................................................11
4.1.2 Manual activation of scenario............................................................................................12
4.1.3 Scenario activation by scheduler........................................................................................13
4.1.3.1 Scheduler activation.......................................................................................................13
4.1.3.2 Scheduler modes............................................................................................................14
4.1.3.3 Setting up a scheduler program.....................................................................................16
4.1.4 Scenario activation by vehicle.............................................................................................17
4.1.4.1 Scenario plans................................................................................................................17
4.1.5 Activate scenarios via digital inputs....................................................................................18
4.1.6 Editing scenarios.................................................................................................................18
4.1.6.1 Changing panels and scenarios......................................................................................18
4.1.7 Working with media............................................................................................................22
4.1.7.1 Managing media files.....................................................................................................22
4.2 Setting up cloud connection.............................................................................................23
4.2.1 Setting up the cloud connection.........................................................................................23
4.2.2 GPRS modem setup............................................................................................................24
4.2.2.1 GSM info and SMS settings............................................................................................25
4.2.2.2 Telephone number and privileges.................................................................................25
2 od 48
4.3 Brightness settings...........................................................................................................26

4.3.1 Setting the minimal brightness...........................................................................................26
4.3.2 Brightness regulation according to light sensors................................................................27
4.3.2.1 Principle of operation....................................................................................................27
4.3.2.2 Brightness regulation curve...........................................................................................27
4.3.3 Setting the fixed brightness................................................................................................27
4.3.4 Brightness regulation according the daytime.....................................................................28
4.3.5 External brightness control.................................................................................................29
4.4 Device information...........................................................................................................29
4.4.1 Basic device information.....................................................................................................29
4.4.1.1 Reset sign.......................................................................................................................29
4.4.1.2 Refresh all variable parameters.....................................................................................29
4.4.2 Hardware maintenance......................................................................................................29
4.4.2.1 Checking current hardware status.................................................................................30
4.4.3 Information given by LED error technique..........................................................................31
4.5 Events and logs................................................................................................................32
4.5.1 Events..................................................................................................................................32
4.5.2 Event logs stored in device’s memory.................................................................................33
4.5.3 Actions on events................................................................................................................33
4.5.3.1 Setting actions on Events...............................................................................................33
4.5.4 Battery voltage monitoring.................................................................................................34
4.5.5 Internal temperature monitoring.......................................................................................35
4.5.6 General measurement logs.................................................................................................36
4.6 Traffic statistics................................................................................................................36
4.6.1 Review of traffic statistics...................................................................................................37
4.6.1.1 Hourly statistics (HBH)...................................................................................................37
4.6.1.2 Vehicle by vehicle statistics (VBV)..................................................................................37
4.6.1.3 Graphical representation of the statistics......................................................................38
4.6.1.4 Current hour data..........................................................................................................38
4.6.2 Export traffic statistics to a file............................................................................................38
4.6.3 Radar settings......................................................................................................................38
4.6.4 Demonstration working mode of radar sign.......................................................................39
4.7 Setting the time of the internal clock................................................................................39
4.8 Firmware update..............................................................................................................40
4.9 GPS setting.......................................................................................................................41
4.10 Push button for quick settings........................................................................................41
4.10.1 Adjusting the parameters by using of push button..........................................................41
4.10.1.1 Adjustment parameters on Speed signs......................................................................41
4.10.2 Push button settings.........................................................................................................42
4.11 Adjusting Police Blinkers................................................................................................43
4.12 Operate the vehicle roof-top sign lifter...........................................................................44
4.12.1 Lifting and lowering the device.........................................................................................44
4.13 Device parameters structure..........................................................................................45
5 COMMAND CONSOLE SETTINGS..............................................................................................45
3 od 48
5.1 Cloud...............................................................................................................................45
5.2 Techniques.......................................................................................................................45
5.2.1 Manual updating of techniques..........................................................................................45
5.2.2 Automatic updating of techniques.....................................................................................45
5.3 My devices.......................................................................................................................45
5.3.1 Settings................................................................................................................................45
5.3.1.1 Set default technique.....................................................................................................45
5.3.1.2 Baud rate........................................................................................................................46
5.3.2 Download from Cloud.........................................................................................................46
5.3.3 Register on cloud................................................................................................................46
5.3.4 Set device location..............................................................................................................46
5.3.5 Remove...............................................................................................................................46
5.4 Communication................................................................................................................46
5.5 Language..........................................................................................................................46
5.6 Licence.............................................................................................................................46
5.7 About...............................................................................................................................46
5.8 Developer tools................................................................................................................46
5.9 Log out.............................................................................................................................46
5.10 Clear Cache....................................................................................................................46
6 ANNEXES.................................................................................................................................46
6.1 Annex 1............................................................................................................................46
6.2 Annex 2............................................................................................................................48
Document Control Date

Author Nikola Stojanović, Milan Radenković 30-04-2020
Approved by Nikola Stojanović 08-05-2020
Version Description
5 New visual identity, new techniques: Police blinkers, Rooftop,
Scenarios, Users and privileges
1 INTRODUCTION
1.1 About the Manual
The purpose of this User manual is to show the user how to control and operate a DMV device using the
free Command Console app.
1.2 About the app

DMV Command Console is an application for controlling and managing a DMV device.
The application communicates directly with the device, so the user must be at the location of the device.
Currently, supported platforms are Android and Windows. Download the Android Command Console from
the DMV App Store located on the Google Play Store.
1.2.1 Supported Devices and Operating Systems

Devices running Android and Windows operating systems are currently supported.
4 od 48
2 DOWNLOADING THE APPLICATION

Downloading an application can be done in many ways. To download via official channels you need a DMV
account. The DMV account is also used for the Cloud Control application. The order is obtained when
purchasing a DMV and if you need support, contact your dealer.
2.1 Download from the site

The latest version of Command Console (for Windows and Android) can be downloaded from www.dmv-
cloud.com. A DMV account is required to access the portal. Available installations can be downloaded in the
Download section.
2.2 Downloads via android app: DMV App Store

The Command Console can also be downloaded through the DMV App Store. The DMV App Store is an
application that needs to be downloaded from the Google Store. You must have a DMV account to access
the application. After logging in, the application will offer you the latest version of Command Console.
5 od 48
3 CONNECTING TO THE DEVICE FOR THE FIRST TIME

The DMV Command Console can be run on a PC, tablet or smartphone.
After launching the application, the logo, version and date of creation of the application will be displayed.
3.1 Logging in
In order to use the application, it is necessary to log in using a DMV account. Different accounts may have
different roles with different access privileges. Before using the console, you must request the order
information from the manufacturer or distributor.
3.2 Initial interface

During launching the Command Console for the first time, there should be internet connectivity available in
order to download techniques and other files from the Cloud Server that are necessary for device
operation.
6 od 48
Three sections are available in the main menu:

 Devices
 Add device
 Settings
For the first time, the console launched has an empty Devices section, or no devices added.
3.3 Discovering and adding devices

If the device we want to operate is not in the Devices section, that is, when working with the device for the
first time, it is necessary to add the device first, the Add device section.
Possible interfaces for connecting to the device are LAN, Direct Wi-Fi, Bluetooth, Serial Communication and
SMS (SMS is only available on the Android platform).
The device may have a number of interfaces available, but it is always equipped with the basic RS232 serial
interface.
If the device has more than one connection method, e.g. you need to connect to the device via BLE and
previously used Ethernet, in the Add device section, select the Bluetooth connection method, then select
the Bluetooth device and connect to it. In the Devices section, the method of connecting to the device will
be changed, the name of the Bluetooth will appear instead of the IP address of the device at the point of
connection.
The Cloud option is used when the Internet is not available at the point of installation of the device in order
to pre-download from the cloud the data needed to work with the device, icons and layouts (described in
detail in the section 3.3.6)
In order for the Command Console to be ready to operate the device, the following steps are required:
1. Open Add Device window
2. Select connection type
3. Select a device address or identify the device
7 od 48
4. Wait for confirmation
3.3.1 Discovering device over LAN (Local Area Network)

Connecting to a device over a local area network (LAN) is possible if the device has an Ethernet interface
available via the RJ45 port.
In order to connect to the device, the device must be on the same LAN as the computer / tablet.
Regardless of whether the connection is via Ethernet cable or wireless, the network parameters of the
devices and computers (IP addresses, Subnet Mask and Gateway addresses) must be set. DMV software
Network Device Toolkit can be used to set the network parameters of the device (instructions are provided
by the DMV).
Steps to Connect:
1. Connect your device to the LAN of your computer / tablet.
2. After connecting to the Internet, select Add device → LAN from the main menu, the IP and MAC
addresses of the devices connected to the local network will appear. The requested device can be
found by scrolling or filtering by IP / MAC address. By dialling the IP / MAC address, we connect to
the device and if the connection is successful, a message will appear that the device has been
detected.
3. Access the Devices section and connect to the device by selecting Connect.
The Internet is only required when connecting to the device for the first time. Every subsequent connection
does not require Internet access.
3.3.2 Discovering devices via Wi-Fi

Connecting to a device via Direct Wi-Fi is possible if the device has a built-in Wi-Fi module.
Steps to connect:
1. Select Add device → Direct Wi-Fi, the available Wi-Fi will be displayed (the Wi-Fi module of the
device has a name / access point, which is the same as the serial number of the device).
2. Select Wi-Fi by serial number (SN, device serial number is on the device label), if the connection is
successful a message will appear that the device has been detected. Not all data needed to work
with the device (device icon and layouts) have been pulled from the cloud yet. The next step is the
Internet.
3. The PC / tablet / smartphone should be connected to the Internet to pull data (device icons and
layouts) from the cloud. This step is only required when connecting to the device for the first time.
Every subsequent connection to the same device does not require this step.
4. Access the Devices section and connect to the device by selecting Connect. While connecting to a
device, the data necessary to continue working with the device is pulled from the cloud at the same
time.
NOTE: The Internet is only required when connecting to the device for the first time via Direct Wi-Fi. Every
subsequent connection to the same device does not require Internet access.
3.3.3 Discovering devices via Bluetooth

Connecting to a device using Bluetooth is possible if the device has a Bluetooth module installed.
Steps to connect:
1. Select Add device → Bluetooth, the available Bluetooth devices will be displayed (the Bluetoot
device module has a name / ID that is the same as the serial number of the device).
2. Select Bluetooth by serial number (the serial number of the device is on the label of the device), if
the connection is successful a message indicating that the device has been detected. At the same
time, the data required to work with the device (device icon and layouts) were withdrawn from the
server.
8 od 48
3. Access the Devices section and connect to the device by selecting Connect. While connecting to the
device, the data necessary to continue working with the device is being pulled from the cloud at the
same time.
NOTE: When working with Windows PC or a laptop, VMS‘s Bluetooth should be added to device list of
Windows as a new device, before discovering device from Command Console.
NOTE: The Internet is only required when connecting to the device via Bluetooth for the first time. Every
subsequent connection to the same device does not require Internet access.
3.3.4 Discovering devices by cable (serial RS232 communication)

Connecting to the device via serial communication is possible if the device has an RS232 serial interface
available (serial / USB converter is required to connect to the computer).
Steps to connect:
1. Connect the device and computer with a serial cable (for computers that do not have an RS232
interface, use a USB to 232 converter). Use a mini USB cable when connecting to a tablet /
smartphone.
2. Connect your PC or Android device to the Internet.
3. Select Cable (serial communication), select the bit rate (number of bits per second) 19200 or 9600,
and then select the serial interface port. If the connection is successful, a message will be displayed
indicating that the device has been detected and at the same time data (device icon and layouts)
have been pulled from the server.
NOTE: The Internet is only required when connecting to the device for the first time via serial
communication. Every subsequent connection to the same device does not require Internet access.
NOTE: When a device is detected via a specific serial COM port, use the same COM port the next time it is
connected, the device will need to be rediscovered.
3.3.5 Discovering devices via SMS

Allows you to control your device via mobile SMS. This is the only communication supported in the
Command Console that has no local character.
Connection via SMS is possible if the device has a GSM / GPRS modem (SIM card must have a prepaid credit
or a postpaid package that includes SMS messages).
This option is only enabled on the Android platform (smartphones and tablets that support SIM card).
The steps for connecting are as follows:
1. Configure GSM / GPRS modem. Modem adjustment can be done via the Command Console if the
device is detected via another available interface) or with the Display Studio application (by setting
the GSM working mode and Connection interval parameters). Set the GPRS modem mode to
"Always on". See section 4.2.2 for more details.
2. Connect your tablet / smartphone to the Internet. With this step, we ensure that the parameters
and device layouts are pulled from the server. To work with your device via SMS, you need constant
Internet access.
3. Select SMS, enter the SIM card number contained in the device in the provided field. Number
format is + CCSCN.
CC country code
SC mobile network code
N phone number
9 od 48
4. After several messages have been exchanged, you will be notified that the device has been
discovered.
3.3.6 Downloading data from the Internet before going to the device location
If there is no Internet at the installation site, it is possible to pre-download device data (device icon and
layouts) via the Cloud option.
The steps are as follows:
1. Connect your PC or Android device to the Internet.
2. Select the Cloud option and enter the device serial number in the Enter serial number field. By
entering the first five digits of the serial number, it is possible to add all the devices in the series. By
marking the serial numbers, the devices have been detected and are in the device list in the Devices
section.
3. At the device location, you need to rediscover the device through a local connection.
3.3.7 Downloading data from the internet after discovering the device
If there is no Internet at the device location, the device may be detected and partial operation of the device
may be possible. Device data for full device operation can be retrieved from the cloud later by connecting
your computer / tablet / smartphone to the Internet (when available) and accessing Settings → My Devices
→ Download from Cloud.
3.4 List of discovered devices

When the Command Console is first launched, the Devices section is blank.
After successfully detecting the device through some of the available communications, it will appear in the
Devices list in the main window.
Each discovered device will be displayed in its field in the Devices section. The device field contains the
following information:
 Device icon,
 Device serial number,
 Type of connection and address
 Field for a free description of the device
 Connect button (connecting to device and accessing device techniques)
 Remove button (deleting a device from the list).
The user can enter a description, reference or text specific to each device (eg installation location, street,
city, installation country, reference, etc.). This option helps to identify more easily among similar devices.
Activated by longer clicking on a darker field, below the serial number and connection method.
NOTE: Discovered device does not mean that it is connected immediately. The next step is to connect the
Command Console to the device by selecting Connect.
NOTE: Ways to connect your device to your computer / tablet / smartphone via Command Console are
described in Chapter 3.3.
10 od 48
3.5 Techniques
DMVs are monitored and controlled by Techniques. Techniques are a set of functionalities, parameters, and
tables grouped together to make device management easier and more transparent.
After selecting the device, a panel with techniques will appear. Which techniques will be displayed or
available depends on the type of device, which means that different types of device have different
techniques. Some techniques are standard for all types of devices: Info, Brightness, Firmware (software)
Loader, Maintenance, Parameters, RTC, and Temperature.
Available sections in the techniques panel:

1. Back (My Devices) button - step back or disconnect from the device;
2. Techniques panel - techniques available for the device;
3. Status button - displays the Online / Offline connection status, followed by IP address / Wi-Fi /
Bluetooth and device serial number. In case you are offline (Offline), selecting this button offers the
option of reconnecting.
4 WORKING WITH DEVICES

4.1 Adjusting device display
4.1.1 Scenarios and panels in DMV devices
The scenario is display visual message which suits the real situation on the road or street. The scenario may
refer to road works, vehicle column, accident, etc.
One or more scenarios can be defined in the device, each scenario can have one or more panels. The panels
should be viewed as a single static display on the device display. Panels can be included or excluded from
the script. Only activated panels are displayed in the activated scenario.
The panels of the selected scenario are displayed cyclically, one after the other. The panel layout by
scenario, number of panels and scenario can also be adjusted locally through the DMV Display Studio
application or through the Cloud Control client application.
11 od 48
Depending on the type of device, the panel can be consisted of image, animation, traffic symbol, text, date
and / or time.
In the Display technique you can see the scenarios and the layout and number of panels in each scenario.
Display technique helps pre-save scenarios that can be easily activated later when needed.
4.1.2 Manual activation of scenario

The Scenarios technique is used to activate the scenario. The Scenarios technique shows the available
scenarios for activation.
Depending on the actual situation on the road, such as road works, vehicle column, accident… one of the
existing scenarios previously defined in Display may be activated.
12 od 48
To show the scenario on your device, select one of the scenarios offered and press the Activate scenario
button. When the command is executed, the activated scenario is displayed.
4.1.3 Scenario activation by scheduler

For devices that support the scheduler functionality, it is possible to predefine the showing according to a
specific schedule. Showings or scenarios are activated according to the set time sequence without the need
for the operator to manually change them.
It is possible to define the device showing up to five years in advance. This is done by defining five different
types of days (programs), so some of the day types are assigned to each day.
The Scheduler technique is used to create a display plan (which scenarios will be displayed at what time
interval). The scenarios themselves are edited in the Display technique.
There are multiple modes for schedulers and one or more programs within each mode.
4.1.3.1 Scheduler activation
The steps to activate the scheduler are as follows:
1. Select the desired operating mode.
2. Click Activate mode.
3. In the appropriate program, adjust the intervals, select the desired scenarios and other settings.
4. For calendar mode, you need to set the calendar first.
5. Write the calendar by clicking the Set calendar button.
6. Load settings into your device by clicking Set program settings.
13 od 48
NOTE: Only one mode can be active.

NOTE: If Manual mode is active, it means that the scheduler is off.
4.1.3.2 Scheduler modes
The following scheduler modes are available:
 Every day
 Weekdays + Weekend
 Calendar
 Manual (Scheduler off)
4.1.3.2.1 Every day mode
The device is programmed to work the same way every day (in a week / month / year). The calendar is
inactive and the device behaves independently of the day of the month, weekdays, weekends, etc. The only
program under this regime is:
 Ordinary day
4.1.3.2.2 Working Day + Weekend Mode
The days are divided into weekdays and weekends, according to which there are two Programs:
 Working day
 Weekend.
During weekdays, the device behaves in accordance with the settings of the Workday program. On
weekends, the device behaves according to the settings of the Weekend program. The weekend includes
Saturday and Sunday.
4.1.3.2.3 Calendar mode
The device follows the settings in the calendar. There are five programs in this mode:
 Ordinary day,
 Working day,
 Weekend,
 Program 1 i
 Program 2.
14 od 48
Programs are consisted of scenarios, intervals at which scenarios are triggered, and speed thresholds that
activate scenarios.
Any of the programs can be assigned to one or a group of dates in the calendar.
The calendar can be programmed for the next five years.
NOTE: The month and year on the calendar are factory preset for January 2000. In order for the calendar to
be set from the current month and year, it is necessary to reset the calendar to the Reset calendar button
or to load the calendar from the file (Import calendar button).
The calendar days of the current month will appear after the calendar has been reset.
The arrows on the right (>) and left (<) sides serve to change the moon and the arrows (>>) above the right
arrow change the year.
The program bar above the calendar contains five program settings: Ordinary day, Working day, Weekend,
Program 1, and Program 2. Each program is presented by different colour for easy distinguishing.
The steps for configuring your calendar are:
1. Activate mode by selecting Activate mode.
2. Configure programs as desired using program windows...
3. Set calendar days
◦ In the Program Bar, select the program you want.
◦ After selecting a program, select the start and end date of the period you want the selected
program to use. Clicking once on the first day and then on the last day of the desired period and
all days in this period will be highlighted with the colour of the selected program from the
Ribbon.
◦ To set a program for only one specific date, double-click the day in the calendar and the day will
be coloured by the selected program from the Program bar. This way, a program is assigned to
the day and the device behaves according to the settings in the program.
4. When program is assigned to each day of each month, write a calendar to device by selecting the
Set calendar button.
4.1.3.2.3.1 Available options for working with calendar

Load calendar file - Load a calendar file.
15 od 48
Save calendar file - save settings to a file in the memory of your computer / tablet / smartphone. When
saving, you can select the location where the appropriate file will be stored. The saved settings can later be
loaded into the same or different device.
Reset Calendar - All settings are reset and reset to the current month and year.
4.1.3.2.4 Manual mode
Manual mode means that the scheduler is off.
In this mode, the device behaves independently of the time of day and calendar. Manual mode has no
programs offered, no ability to divide the day into intervals, but offers the ability to set scenarios that will
run continuously in the future.
4.1.3.3 Setting up a scheduler program
Up to 10 intervals can be defined within the program (factory-set, at user request the number of intervals
can be changed), each interval can be assigned a scenario i.e. behaviour of the sign. The default start / end
time for the interval is between 00:00 and 23:59.
4.1.3.3.1 Available options for working with programs
Import settings - Load program file.
Export settings - Save the program settings to the computer / tablet / smartphone memory. When saving,
you can select the location where the appropriate file will be stored. The saved setting can later be loaded
into the same or different device.
Reset settings - The setup program returns to the original / factory settings.
4.1.3.3.2 Setting the interval
4.1.3.3.2.1 The default interval
The settings made here will apply unless an additional interval is defined. It will also apply at intervals not
covered by user-added intervals. In this way, the predefined (last) interval covers all time periods not
covered by predefined intervals.
4.1.3.3.2.2 Interval
Click "+" to add a new interval.
Set the time in the selected interval field. The intervals should be arranged in chronological order while the
last interval in the sequence is a predefined interval. The new interval will become active 1 minute after the
previous interval ends. If two or more intervals cover the same period of the day, the top priority will have
the highest execution priority. The priority decreases by going down.
NOTE: Intervals should be arranged in chronological order of execution. If the interval exceeds the next day,
it is necessary to divide the same interval into two intervals. Example: The interval from 9:00 PM to 9:00 AM
should be divided into two intervals, one from 9:00 PM to 11:59 PM and the other from 00:00 AM to 9:00
AM.
NOTE: In order for the program to become active immediately upon loading into the device, the device
must be reset.
16 od 48
4.1.3.3.3 Scenario settings

Select the Scenario button. Select the desired scenario, pictogram, flasher mode, threshold speeds and
others. What will be offered for setting (Scenario, Pictogram or Blinkers) depends on the type of device.
Once the program is set up, confirm by clicking the button Set program settings.
4.1.4 Scenario activation by vehicle

DMV device that have built in radar as a vehicle detector, can activate scenarios automatically when a
vehicle arrives. Scenarios are activated based on the speed of the oncoming vehicle and the predefined
plan.
The technique dedicated for adjusting the scenario plan is the VAS (Vehicle Activated Sign) technique. The
VAS technique allows you to adjust the scenario i.e. sign behaviour based on the speed of the oncoming
vehicle.
If the device has the scheduler functionality the Scheduler technique is used for the settings, where the
Manual mode of this technique mode is used instead of VAS technique.
4.1.4.1 Scenario plans

Select the Edit button. Select the desired scenario or flasher mode (if available). The maximum number of
speed thresholds is defined by device software. It is necessary to define the speed thresholds and the
behaviour (scenario and flashers) of the sign for each threshold.
 Default - the scenario is active until either a vehicle is detected or the speed of an oncoming vehicle
is greater than Threshold1.
 Threshold1 - the scenario is activated when the speed of the oncoming vehicle exceeds the speed
of Threshold1 and does not exceed the speed of Threshold2.
 Threshold2 - the scenario is activated when the speed of the oncoming vehicle exceeds the speed
of Threshold2 and does not exceed the speed of Threshold3.
 Threshold3 - ...
Once the scenario plan is set, confirm by clicking the OK button.
NOTE: The speed of the next threshold must be greater than the speed of the previous one. The values of
all Thresholds must be greater than 0. Thresholds with a higher index have a higher priority.
NOTE: Scenarios are set up in the Display technique.
17 od 48
4.1.5 Activate scenarios via digital inputs

Devices can have one or more digital inputs through which the device display can be activated. The setting
of the device is similar to the vehicle activated signs, when a vehicle arrives. In the case of digital inputs,
instead of setting the thresholds, we have the setting of a specific digital input, i.e. the behaviour of a device
if a specific digital input is activated. Devices that are activated via digital inputs are shipped with factory-set
priorities.
In addition to digital inputs, devices can have radar at the same time. In this case scenario activation is
possible in two ways: by triggering the digital input and / or by approaching vehicle.
The Scheduler technique shows which of the thresholds are activated by digital input and which are by
vehicle. Thresholds triggered by digital input are inactive (Threshold field is disabled) while thresholds
triggered by vehicle are active and the speed threshold that will activate the scenario can be adjusted.
4.1.6 Editing scenarios

Scenario preparation i.e. selecting a pictogram, animation, or text message is done in the Display technique.
It is possible to make various changes related to panels within the scenario, changes in position, content,
messages, duration, etc.
After making changes, changes need to be sent to the device and this is done by clicking on Set button
4.1.6.1 Changing panels and scenarios
Panels can be enabled or disabled via the Panel activation button. The panel duration is set in seconds. The
panel is edited via the Edit button. On the left side of the interface there is the current panel settings. There
are commands for adding and deleting media at the bottom right of the screen.
Buttons for entering text, pictures, animations, date / time and deleting media are:
Add animation - adds animation
Add bitmap - adds pictograms
18 od 48
Add text line - adds a line of text
Add date and time - adds a date and time on the screen
Delete selected media - deletes the selected image, text message, date, time, or animation. In order
for the delete option to be active, the desired media must be selected.
Delete all panel’s content
Confirmation of panel changes.

NOTE: If the maximum number of lines of text, images, symbols, or animations (maximum number is
software-defined) has been added to the panel, the addition buttons will be inactive. After deleting one line
of text, image, symbol or animation, these commands will be active again.
4.1.6.1.1 Working with bitmaps
By selecting the Add bitmap button or selecting the bitmap which is already on the panel, options for
working with the bitmaps will appear to the right. A new image can be selected and its position can be
changed using the arrows and align buttons provided.
After editing, confirm the settings with the OK button.
Load new settings into the device by selecting the Set button.
The number of pictograms in one panel is limited by the device‘s software. The Add bitmap button
becomes inactive after adding the maximum number of images. If there are no images in the device, the
button will be disabled.
4.1.6.1.2 Editing text messages
To add new text, select the Add text button.
By selecting existing text, the current text can be edited or deleted.
Depending on the device type, it is possible to change the colour of the text. The upper right part shows
one, two or six colours (depending on whether it is a monochrome, two-colour or full colour display).
The text section also allows you to change fonts, adjust character spacing, and position text.
4.1.6.1.2.1 Entering text
The text of the message is entered in this field. The maximum number of characters depends on the
resolution of the display, font selected and the space between the letters.
The number of lines of text in one panel is limited by the device software. The Add text button becomes
inactive after adding the maximum number of text lines.
4.1.6.1.2.2 Font
This option selects one of the fonts stored in the device memory. If multiple lines of text are set, any of the
fonts offered can be selected for each line.
4.1.6.1.2.3 Max. Spacing
This option is used to adjust character spacing. The maximum distance is defined by the device software
and the Command Console will not allow a distance greater than the maximum. After entering the value
you need to confirm by pressing Enter.
4.1.6.1.2.4 Text positioning
Use the arrows to position the lines of text. It is possible to make vertical and horizontal centering as well as
alignment against the edge of the display
After setting the text, confirm the new settings by clicking the OK button.
Load the new settings into the device by selecting the Set button.
19 od 48
4.1.6.1.3 Display date, time and temperature

Select Add Date and time to set the date, time, or temperature. HH: mm will be displayed as a text line.
With its selection, options will appear on the right to select what to display, format, font, and maximum
distance between characters.
Time / Date / Temp - Choose between time, date and temperature.

Format - allows you to change the time or date format.
Font - allows you to choose one of the fonts offered.
Max. Spacing - character spacing, after entering the value, press Enter.
Use the arrows to position the line of text.
4.1.6.1.4 Working with animations
Adding animation to the panel is done by selecting the Add animation button. This opens a window with
available animations. Selecting one will bring up an animation to the panel.
Selecting an animation will display the options for adjusting the display: animation selection, animation
speed and positioning on the right.
Animation speed allows you to adjust the animation speed in the range 0-9, 0 being the lowest speed.
Click the OK button to confirm the animation settings
Select Set to send changes to device.
4.1.6.1.4.1 Loop - Number of animation repetitions
In the main panel window, it is possible to adjust the number of repetitions of animation within the panel. If
this value is set to "0", the animation will be executed only once and will last as long as the frames and the
animation speed is set. Displaying the next panel of the scenario will happen after all repetitions of the
animation in the current panel are completed and after the duration of the current panel.
4.1.6.1.5 Working with predefined pictograms
Select the scenario and then the panel. Selecting the Edit button opens a panel window.
Selecting the pictograms on the panel opens the possibility to choose Symbol. A window on the right will
offer available predefined pictograms.
20 od 48
Select the OK button to confirm the setting, and select the Set button to send settings to device.
4.1.6.1.6 Working with DC (digit and character) fields
Select the scenario and then the panel. By clicking to Edit opens a panel window where CK fields are set.
There are two ways to adjust the view:
 By editing the DC field
 By selecting the element on panel
21 od 48
Select the OK button to confirm the setting, and select the Set button to send changes to device.
4.1.7 Working with media

The Media Browser technique is for working with media like fonts, images, animations. Media which are
already in the device memory will be shown grouped.
There are tools for adding new media or deleting existing media from the device.
Which media type are supported is defined by the device software. In this technique, the Command
Console application only recognizes supported media types. For example, media type for bitmaps depend
on whether the devices are monochrome, dual-colour, or full-colour matrix devices.
For each media following information is available: index, resolution, name.
Depending on the size, DMV device can display character of different heights, all standard traffic sign
symbols as well as animations. A large number of available bitmaps, fonts and animations can initially be
stored in the device memory.
There is an option for creating and uploading fonts, bitmaps and animations that were created by the user.
4.1.7.1 Managing media files
A user should select a specific group of media to work with by clicking on their type.
The technique enables the following media work:
 Change file’s position - use the <> arrows for changing the file index
 Delete selected - deletes one selected media
 Delete type - deletes all media from the selected group
 Add files - Adds new media from your computer / tablet / smartphone memory. Before adding new
files they can be created or edited in Display studio or could be provided by the manufacturer.
Write changes to the device by selecting the Set button.
All media read from device are stored locally and they are available to other techniques like Display
technique.
22 od 48
NOTE: Reading the media from the device is performed only once and then only the checksum is checked.
Application looks for changes between local media and media into device.
4.2 Setting up cloud connection

In order for devices to communicate with the server, they must have Ethernet or GPRS communication
interface.
4.2.1 Setting up the cloud connection

The Cloud technique allows user to set parameters related to the communication with the cloud.
Devices with Ethernet communication interface will have Cloud technique, while devices with GPRS/3G
modem will have additional GPRS technique (section 4.2.2).
Server IP address – IP address of the cloud server.

Server port – communication port of the cloud server.
23 od 48
Enable edit via the Cloud - the ability to change parameters via the cloud server, turning on allows control
of the device via the Cloud.
Enable Cloud connection – by turning on allows device to connect via the Cloud.
Connection interval - connecting interval to the Cloud server.
Establish connection timeout - waiting time to connect to cloud Server (in seconds, set minimum 5
seconds).
Reply from Cloud timeout - response timeout from cloud server (in seconds, set a minimum of 5 seconds).
Maximum session duration - the maximum duration of a connection to the cloud server (in seconds,
minimum 10 seconds). For parameter value = 0, the started connection is constantly maintained (this must
be supported in embedded software).
Cloud Connection keep alive interval - keep alive interval in case that connection is being maintained.
Minimum interval between sessions - minimum time (pause) between two connections (in seconds, set a
minimum of 5 seconds). It cannot be changed, the value can only be read.
Refresh - read the current parameter values from the device.
Set - Writes new values into the device.
NOTE: For devices that have a GPRS or 3G modem, setting the Connection interval to too low value may
cause interruption of other communication interfaces (Bluetooth, Wi-Fi, RS232 ...). GPRS modem,
Bluetooth, Wi-Fi, RS232 share the same serial communication channel. GPRS communication has the
highest priority, so if the interval for connecting to the Cloud is set to a short time interval, this type of
communication may "occupy" the channel, since in that case the channel will not be free for other
communications. If device supports Bluetooth or Wi-Fi, it is recommended that the connection interval not
be shorter than 15 minutes.
4.2.2 GPRS modem setup

The GSM or 3G modem make possible remote control of the device via the mobile network by using the
network operator's SIM card. The DMV device connects to the Internet via GPRS or 3G modem and reach
cloud server.
The GPRS technique is used to configure the GPRS modem. The most important parameters which are
needed to be set are APN, User and Password (settings are obtained from your network operator). After
entering, save the parameters to the device by selecting the Set option.
24 od 48
4.2.2.1 GSM info and SMS settings

Allow calls from anybody - any phone number will be registered if sign is called; If set No - the ability to be
called only from contacts in the Telephone numbers & privileges list. In order to call the device, the GPRS
modem must be supplied with power constantly, so it is necessary, before calling the sign, to set the GSM
Working Mode parameter to Always on.
Allow edit via SMS, Yes - parameters in the device can be changed via SMS, No - no parameters in the
device can be changed via SMS.
Allow SMS from anybody, Yes - the ability to receive SMS from any user; No - the ability to receive SMS only
from contacts in the privilege list (Telephone numbers & privileges).
GSM working mode – defines whether the GPRS modem will only be active during the event of connection
or will always be active.
NOTE: GSM working mode should be set to Always on if there is intention for using of SMS communication
or if user intend to call the sign.
4.2.2.2 Telephone number and privileges
Up to 9 customer phone numbers can be defined that can have different levels of control and notification.
Phone format is + 38164…
+CCSCN
CC country code
SC mobile network code
N phone number
4.2.2.2.1 Calls and SMSs
Privileged numbers should be entered from position two to position nine.
The first position automatically records the number of users who last called the device.
If the device is being called by a non-privileged number and anybody is allowed to call (and if the GPRS
modem is always on), then its number will be entered in the first position. Since the first user is factory-set
to receive SMS from the device, the user will receive an SMS notification each time the device takes action
on the selected events (see Logs and Actions on events).
All privileged users receive messages from the device if Send SMS on event is checked.
25 od 48
Table of telephone numbers and privileges:

 Column Telephone number, enter phone numbers in the format described above. A telephone
number can be entered in any field except the field in the first position.
 Column Send SMS on event column, mark the phone numbers to which the device will send a
message after the event.
 Column Allowed to change parameter, mark the phone numbers that allow it to change
parameters in the device.
4.3 Brightness settings

DMV devices have built-in precise brightness control with 1% resolution and support four brightness control
regulation methods:
 Automatic, based on informations provided from light sensors (depending on measured external
illuminance)
 Automatic, depending on time of day (day-time and geo-location algorithm)
 Fixed brightness
 External brightness control
It is necessary to choose which of the offered brightness control method will be active. This is done by
setting the priority. Brightness control method with a larger number I.e. having a higher position takes
higher priority.
Changing the priority is done by using the arrows next to the selected brightness control method.
The brightness control method priorities change automatically if the highest priority control mode is no
longer operational. This means that control method with next lower priority takes the first place and it
begins to control the brightness. For example, if the light sensor fails, the daylight control is automatically
activated by default.
4.3.1 Setting the minimal brightness

Devices come with a preset minimal display brightness.
The value of Minimum brightness can be increased if needed.
26 od 48
4.3.2 Brightness regulation according to light sensors

4.3.2.1 Principle of operation
The illumination of the display adapts to the ambience based on the measurement of the light sensor. The
device may have one or two built-in light sensors (usually one on the front and one on the back of the
device case). External illumination measured ranges from 0 to 64,000 Lux.
In the case of two light sensors, the mean value from two sensors is used. To prevent sudden changes in the
illumination of the device, a mean measurement is taken for an interval of the last 10 seconds.
In the event of a failure of one light sensor, the other will continue to operate and the automatic control
method will still be active. In the event of a failure of both light sensors, the sign will automatically switch to
the next highest priority brightness control method.
If the sensor does not change the value for a long time (24h by default), the device will declare it dirty and
its measurement will not be used for regulation.
4.3.2.2 Brightness regulation curve
The brightness control curve can be adjusted by changing the parameters Darkness illumination and Bright
day illumination. If the external illumination is less than that defined by the Darkness illumination
parameter then the brightness on the display will be at the defined minimum brightness level and if it is
greater than the one defined by the Bright day illumination parameter the illumination will be 100%.
4.3.3 Setting the fixed brightness

The selected brightness value is constant until a new value is set. Fixed brightness can be adjusted in values
from 1 to 100. The brightness is adjusted by moving the slider left or right and after adjusting the value it is
necessary to confirm the changes by clicking the Set button.
27 od 48
The fixed brightness value is stored in flash memory and can be changed 100,000 times over the life of the
device, which would correspond to the average change in illumination value once per hour. For systems
where there is a need to regulate brightness more frequently, the external control method should be used.
4.3.4 Brightness regulation according the daytime

The brightens is regulated based on the time and date of the internal clock and defined geographical
location of the device. Monthly changes in sunlight during the year are taken into account. The regulation
mode is accurate enough for all locations within a 500km radius of a defined location.
This type of regulation works based on a table of defined dawn and dusk moments. The times of the
beginning and ending of dawn and dusk are defined for each month (X1-X4).
Each day is divided into four intervals:
 Night, between X4 and X1 – brightness is equal to Minimum brightness.
 Sunrise, between X1 and X2 - brightnes rises from Minimum brightness to the maximum (100%).
 Day, between X2 and X3 - the brightness is constant and maximum (100%).
 Twilight, between X3 and X4 – the brightness decreases from maximum (100%) to minimum
brightness.
Table of Sunrise/Sunset moments:
NOTE: Geographic location where device will be installed and the information about the sunrise / sunset
moments for that location are defined by manufacturer in the firmware. This data cannot be edited by
users.
28 od 48
4.3.5 External brightness control

This control method is used when the device is part of a system in which the brightness is controlled
independently of the individual device.
There is no limit to the frequency of changes, the new lighting level can be adjusted every second.
The Time to Live (TTL) parameter specifies the duration of set brightness. After the time has expired, the
brightness set-point is no longer valid, and the display switches to the next brightness control method
according to priority. If TTL is set to 0, it means "live forever" (permanently active), I.e active until the next
device reset (on).
4.4 Device information

All relevant device information can be viewed and tracked in the Info and Maintenance techniques.
4.4.1 Basic device information

The Info technique allows you to view different device parameters such as:
 Software number
 Software configuration number
 Display resolution
 Layout number
 Operating hours of the device
 The date the software was created
 Date and time of the last reset of the device
The technique has two buttons Reset Device and Refresh.
4.4.1.1 Reset sign
In the Info technique, Reset device button reset the device. The number of resets is limited to 65535, no
need to reset the device unnecessarily.
4.4.1.2 Refresh all variable parameters
In the Info technique, Refresh button allows to read all the variable parameters and tables of the device.
4.4.2 Hardware maintenance

The Maintenance technique recognizes all installed hardware components (battery monitor, light sensor,
clock, etc.) and allows user to quickly check the current status of the hardware.
Three statuses are used for each of the installed hardware components:
 OK -
 Warning -
 Not OK -
29 od 48
4.4.2.1 Checking current hardware status

4.4.2.1.1 Checking the time of internal real time clock
The RTC time shows the accuracy of the built-in clock and displays the time in the device and time
difference in seconds relative to the time of the computer or tablet.
NOTE: Accuracy of clock time in the device is essential for proper scheduler operation as well as proper
event logging within the device
4.4.2.1.2 Checking the battery voltage
Batt. state monitors and displays the current battery voltage in Volts and indicates whether it is low, normal
or high. There are four states:
 Over-voltage
 Normal
 Low
 Display is off (because of battery status).
NOTE: Battery status can seriously affect the display of the device. In low battery condition, device
brightness will automatically drop by 50% over the currently defined brightness. When the battery is empty,
the display will turn off to save energy. The sign is then in a so-called hibernation state.
4.4.2.1.3 Checking the device temperature
Temp alarm state shows the temperature of the device and whether the current temperature is low, normal
or high. If the temperature is higher than warning threshold, a warning will be triggered, and if the current
temperature is higher than alarm threshold, a temperature alarm will appear.
The temperature is checked every minute, while logging of its values is done every 10 minutes.
4.4.2.1.4 Checking light sensors
The Light sensor 1 and 2 show the external illumination value measured by each sensor, whether the
sensors are working properly or if there is a problem, e.g. whether they are dirty or not working.
The light sensors are checked every second.
30 od 48
4.4.2.1.5 Checking the detection of the radar

The Radar shows the date and time of the last detected vehicle, warning status if there is no vehicle
detection for a long time (in the last 12 hours), it might be that there is a problem with the radar, the status
Not OK will be displayed.
4.4.2.1.6 Checking controller memory
Disc Error Code shows if there is an error in the device memory. Error codes are 1,2,3 and 4. Codes greater
than 4 are for debugging purposes and mean there is no error.
4.4.2.1.7 LED error detection
Led Error detection shows the number of defective LEDs.
The LED is checked every 10 minutes by default. A valid requirement for LED fault detection is that the
current illumination on the device is greater than 80%. These two values can be adjusted via advanced
settings.
Device reset will cause clearing information about current LED errors and scanning should be done again.
Type of LED error detected depends on device type.
4.4.2.1.8 Reset watchdog
Reset and watchdog monitors and shows the total number of hardware and software resets of the device
and shows the number of allowed resets. The number of allowed resets is factory-set and cannot be
changed.
4.4.2.1.9 LED board error detection
LED Boards displays which groups and how many of them are defective. Within this section, there is a visual
representation of the faulty LED board chain. If there is an LED board error, it can be displayed graphically at
its position within the sign.
The LED boards are checked every 8 minutes. This interval can be adjusted via advanced parameters. Device
reset will cause clearing information about current LED errors and check should be done again.
4.4.3 Information given by LED error technique

DMV VMS do self-check of the LEDs and drivers. At certain intervals, the device performs self-testing and
stores the results in memory.
The devices detect three types of LED errors:
 Short circuit - exists when a diode short circuit is detected on the LED drivers. Battery powered
devices do not have a stable voltage and short circuits cannot be detected.
 Open Circuit - the open circuit is detected by the LED drivers.
 Overheating error - LED driver temperature higher than 150 C.
Information about the LED errors in LED error technique.
31 od 48
Available settings are:

Error check interval - the interval between two self-tests (in seconds). The picture above is an example
where the self-test interval is set to 600 seconds (10 min). The blue line indicates the time remaining until
the next self-test.
Alarm threshold - the number of LED errors that need to occur for the device to detect an event. Chapter
4.5 describe events in detail.
Maximum number of errors per day - maximum number of errors per day.
Allowed thermal faults - determines whether thermal faults will be checked. If parameter is set to 1 -
thermal faults will be checked, 0 - thermal faults will not be checked
Minimum illumination for LED checking (%) - to detect LED errors, the illumination must be above 80% by
default.
4.5 Events and logs

4.5.1 Events
Events are certain situations that occur during the operation of a device. For example, when turned on, the
device will detect an "on" event; when the temperature of the device exceeds the temperature thresholds,
device will detect the "temperature alarm" event; when the temperature of the device returns within the
allowed temperature thresholds, the device will detect a "temperature alarm deactivation" event; when the
battery voltage drops below the minimum voltage threshold, the device will detect a "battery low" event,
etc.
Events can be:
 Alarms
 Warnings
 Information i.e. ordinary events
 Deactivation events
Example, within a battery event there is a "Battery Alarm too low" event that occurs when the battery
voltage drops below the threshold value, and a "Battery Alarm Deactivation too low" event that happens
when the battery voltage rises again above the required value (these two trigger voltages are usually not
equal, there is a "hysteresis" difference between them).
After event is detected, the device usually takes some "action". The device will first take emergency actions
(if on), such as switching on the fan when high temperature is detected or entering the power save mode
32 od 48
when it detects low battery... Emergency actions depend on the event that occurs and the specific
installation conditions of the device.
A list of possible events in DMV sign is given in Chapter 6.1 Annex 1.
4.5.2 Event logs stored in device’s memory

All events can be stored in the device memory. Which events will be stored in the device memory is set in
the Maintenance technique, in Actions on events section.
The event logs can be downloaded in the Maintenance technique, by using the Logs button.
4.5.3 Actions on events

The device responds when it detects an event and takes action.
NOTE: When working with the device, it is necessary to set what actions device takes on which events. It is
necessary to enable one or more actions per event.
After responding, the device can perform the following actions:
 An event can be recorded in the device memory
 DMV device can send cloud event information (if the device is connected to a cloud server)
 DMV device can send event information to the SCADA server (if the device is connected to the
SCADA server)
 DMV device can send event information via SMS (if this feature is available)
4.5.3.1 Setting actions on Events
The adjustments are made in the Maintenance technique, the table Actions on events.
Possible actions:
 Log Enable - logs an event in the device memory
 Send2Cloud Enable - sends the event to the cloud server
 Send2SCADA Enable - sends the event to the SCADA server
 SMS Enable - sends a text message to a privileged user
The setup table is the same for all device types, but only events that the device is capable of detecting will
be tracked and activated. Example, unless the device has radar installed, events in the radar group cannot
be used for actions.
Events are classified into the following groups:
4.5.3.1.1.1 General events „GEN“
Still in development.
4.5.3.1.1.2 Activation events „RST“
For example, when the device is turned on ("reset"), when it is "ordered" to be turned off. The device can
detect the reason for the reset and perform some action accordingly.
4.5.3.1.1.3 Scenario events „Chg Scenario“
The moment when the content of the display changes for some reason. This may be because of a time-
dependent operation or because of a command received through some communication channel, or because
of another event ...
4.5.3.1.1.4 Temperature events „Temp“
The moment when the temperature inside the device goes through certain threshold values. Meaning it
gets too hot, gets too cold, the moment the fan is switched on, the moment the heater is switched off, etc.
4.5.3.1.1.5 LED events „LED“
The moment a LED error is detected or the number of faults exceeds critical values.
33 od 48
4.5.3.1.1.6 Battery events „Batt“

Tthe moment when the battery voltage reach some thresholds - becomes low or becomes normal again. It
can alert the user to replace the battery or check the solar panel.
4.5.3.1.1.7 Hardware events „Hardware“
The moment when something happened to the hardware components. There are constant checks on some
of the hardware components inside the device such as light sensors, temperature sensors, LED, flash
memory, etc. In the case of a malfunction, the event will be triggered.
4.5.3.1.1.8 Time events „Timer“
The moment when the specified timer has expired (the time when the device has responded to the cloud),
etc.
4.5.3.1.1.9 GPRS call events „GPRS Call“
Events such as when a call or SMS to the sign occur.
4.5.3.1.1.10 Communication events „Comm Err“
The moment when a communication problem occurs, e.g. the device cannot connect to the cloud server ...
or a similar communication problem.
4.5.3.1.1.11 Memory events „Mem full“
Data Acquisition Events (warning that storage memory is almost full). The device collects some data during
operation, such as battery voltage, internal temperature, traffic statistics... and stores it in tables that need
to be read (SCADA server, cloud server, computer, tablet) before being filled.
4.5.3.1.1.12 Geo location events „GPS“
The moment when GPS position of the device is changed in relation to a given radius.
4.5.3.1.1.13 Radar events „Radar“
For example. When a violent driver is detected, street congestion or radar is simply inactive for a long time.
4.5.3.1.1.14 Measurements events „Samples“
The moment when defined threshold was reached during measuring some value (humidity, lighting,
voltage…).
The completed Action on events table should be sent to the device by clicking the Set button.
4.5.4 Battery voltage monitoring

DMVs have a built-in battery monitoring A/D converter as well as reporting when voltage thresholds are
exceeded. Constant and correct operation of the device requires a constant voltage, i.e. to move within the
permitted limits. There are four voltage states:
When the battery voltage is between certain thresholds, the device sends the battery status information:
 normal
 over-voltage
 low voltage
 display is off because of battery
The moment when the battery voltage reach one of the thresholds (becomes very high or very low or
returns to defined limits) is an event that will be stored in the device. Some events are treated as "alarms",
some as "warnings" and some as "deactivation events" (for a more detailed explanation of events, see
section 4.5).
After an event is detected, device will usually perform one of the "actions". When the battery goes in e.g. to
"low voltage" state, the device's Power safe mode is activated. In power safe state, display brightness is
reduced by 50% and sign turns off all peripheral components that affect power consumption: GPRS module,
fan, heaters, etc. These emergency actions depend on the event itself and are configurable. At night, the
device operates with minimal illumination (the value set to Minimal brightness, the Brightness technique).
34 od 48
Battery technique is used to view the history and status of battery voltage. According to the information
available, it can be concluded whether to charge the battery, replace the battery, check the solar panel, etc.
Voltage log Chart - x-axis shows time intervals for the selected time period: hour / day / 7 days / 30 days /
All data. The Y-axis shows the battery voltage in Volts.
The graph shows three voltage thresholds:
 Over-voltage (red) - the upper battery voltage threshold.
 Low voltage - indicates the battery voltage threshold.
 Display off (yellow) - voltage threshold below which the device display goes off.
Voltage threshold values can be changed within Battery setting. To send new threshold values to the device,
click the Set button.
Refresh - an option to read the current state of battery voltage from the device.
4.5.5 Internal temperature monitoring

DMV devices have a built-in sensor for internal temperature measuring and some events are reported when
the temperature inside of device is above the thresholds.
The moment when the temperature level reach threshold (it gets too hot, it gets too cold, the moment the
fan switches on, the moment when the heater is switched off, etc.) is an event that is logged in device
memory.
In general, events are treated as "alarms", "alerts" or "deactivation".
Example, the "Temperature warning" event occurs when the temperature exceeds the "Warning Point"
value = 50 oC or the "Temperature Alarm" event occurs when the temperature exceeds the "Alarm Point"
value = 70 oC. After announcing the event, the device takes some "action" (e.g., "Action due to high
temperature"). The unit will first take immediate action, such as dimming the LEDs or switching on the fan
(if the temperature is high) or the heater (if the temperature is low)...
High temperature actions are:
 Do nothing
 When "Warning Point" is exceeded, the illumination decreases linearly, if the temperature
continues to rise and exceeds the "Alarm Point", the brightness immediately drops to the minimum
value.
35 od 48
 When "Warning Point" is exceeded, the brightness dims linearly, if the temperature continues to
rise and the "Alarm Point" is exceeded, the device switches off the display.
 When "Warning Point" is exceeded, the device switches off immediately. (This action is set by
default)
After the critical temperature has decreased, the device's display is switched on.
The Temperature technique is used for setting thresholds and for monitoring internal temperature.
On the temperature graph, x-axis shows the time intervals in the selected time period: hour / day / 7 days /
30 days / All days. The Y-axis shows the temperature in Celsius (°C).
The graph shows three different temperature thresholds:
 Alarm threshold (red) – upper temperature limit. An alarm is triggered if this threshold is exceeded.
 Fan threshold (green) – if this threshold is exceeded, fan in the device turns on.
 Warning threshold (yellow colour) - threshold of the temperature warning.
Edit threshold - threshold values are factory set, but can be changed.
New threshold values can be sent to the device by clicking the Set button.
Refresh - option to read the current temperature state and logs from the device.
4.5.6 General measurement logs

This is currently in development stage.
4.6 Traffic statistics

DMV devices with built-in radar can measure vehicle speed and collect different traffic data.
The Radar technique is used to display and archive traffic statistics, as well as to change radar settings.
36 od 48
4.6.1 Review of traffic statistics

Traffic data is stored in the memory of a certain sign, i.e. a limited time period (the time period may be
shorter or longer, depending on the device or its software), can be saved in an excel spreadsheet. The data
are intended for traffic analysis, recognition of the period when the largest number of traffic violations,
detection of violent drivers...
4.6.1.1 Hourly statistics (HBH)
Hourly statistics is traffic data of every hour. Statistics are collected during the hour and at the end of the
full hour, new data is written to memory.
The statistics contain the following data for each hour:
 Number of vehicles detected.
 Number of speeding vehicles.
 The time when the maximum vehicle speed was detected.
 Distribution of the number of vehicles by speed ranges (eg 0-24km / h, 25-35km / h…> 125km / h).
Speed ranges can be defined according to the location of the sign installation.
 Average vehicle speed.
 Maximum vehicle speed.
 Street occupancy (in%).
 Sign activity (in%).
NOTE: Hourly statistics are logged into the device's permanent memory, done every full hour. Meanwhile,
the collected data is stored in temporary memory (RAM). Disconnecting the device or resetting the device
before writing this data to permanent memory will cause a loss of traffic statistics for the period from the
last write to the time when the reset or loss of power occurred.
4.6.1.2 Vehicle by vehicle statistics (VBV)
This is a statistic by which every vehicle detected is recorded. The exact time and speed of each vehicle at
the time of its detection are recorded *. The device collects data continuously and every ten minutes or to a
certain (100 fossils factory) number of detected vehicles, stores collected data to the VBV log.
VBV statistics is not included in every radar device but are enabled on demand.
37 od 48
* NOTE: The moment when radar detects a vehicle and the moment when a device recognizes a new
vehicle based on received data may be different. The sign will adjust the display based on the detected
speed of the object moving toward the sign, and this occurs independently of statistical "recognition" of
vehicle.
4.6.1.3 Graphical representation of the statistics
There are histograms which are graphical representations of traffic statistics.
4.6.1.3.1 Distribution of the number of vehicles by speed range - graphical representation
The number of vehicles is divided into 12 speed ranges (0-25km / h, 25-35km / h… 125 + km / h). Speed
ranges can be defined according to the location of the sign (Chapter 4.6.3).
4.6.1.3.2 Number of vehicles per hour - graphical representation
For each hour, the number of vehicles and the number of vehicles that exceeded the speed limit are
displayed.
4.6.1.4 Current hour data
The collected data of the current hour are displayed: current speed, how many vehicles have passed, how
many vehicles have exceeded speed, what is the maximum speed of the vehicle, and so on…
4.6.2 Export traffic statistics to a file

Traffic statistic can be saved in an excel spreadsheet (csv format).
Steps:
1. Choose Radar technique
2. Choose Hour by Hour Statistic or VBV logs button
3. Export the selected table by clicking Export button
4. Select a location and save the file
4.6.3 Radar settings

The "Settings" button opens a number of parameters for setting traffic statistics:
 Radar – enables or disables radar. If the radar is off, the device will not detect vehicles.
 Speed limit – Speed limit at the location where a sign is installed. Essential for statistics, used to
sort a vehicles as "correct" or "speeding".
 Minimum speed to detect - the lowest speed that the controller accounts. It is usually set to
5km/h. All detected objects with lower speed will not be treated. For example, to ignore
pedestrians and cyclists, this parameter can be set to 15km/h.
 Maximum speed to display - the maximum speed that device can show on its display. If the vehicle
is moving at a higher speed than defined, the actual speed of the vehicle will not be displayed –
speed defined by this parameter will be displayed instead. In this way, it can also prevent
inappropriate behaviour such as car racing. For example, on a road where the limit is 50km/h, this
parameter can be set to 79km/h, so that all cars moving above this speed will be shown 79km/h.
 The street is counted as occupied after the vehicle - refers to the time that the last detected
vehicle "occupies" the street, expressed in 1/10sec. It is factory set to 20, which means that the
vehicle behind when there are no more vehicles, takes the street for another 2 seconds (after
passing the sign, i.e. after the radar has stopped detecting it). This is used to calculate street
occupancy.
 Speed unit - speed unit: km/h (kilometres per hour) or mph (miles per hour).
 Reckless driver threshold - violent driving threshold. Every time when radar detects a vehicle going
above this speed, an event is generated. Depending on the event handling (Maintenance
technique, Actions on events) the event will be recorded in the memory log or will activate sending
a message to the cloud, SCADA server or sending an SMS).
38 od 48
 Crowd threshold - the number of vehicles that need to be detected in a given period in order to be
considered that there is traffic congestion. Depending on the event handling (Maintenance
technique, Action on events), the event will be logged into the memory log or will activate sending
a message to the cloud, SCADA server or sending SMS).
 Crowd hysteresis - entered value ± Crowd threshold, defines the number of vehicles above which
the crowd is considered to have occurred, or below which the crowd ceased.
 Crowd averaging - the number of vehicles that represent the average congestion on the street.
 Maximal time without vehicles (hours) - maximum time without detected vehicles. After the time
has elapsed, it is suspected that there is a possible problem with the radar. Monitor radar
information and status in Maintenance technique.
 Low speed and high speed for Speed Statistics – “Hour by hour Statistic“ gives the distribution of
vehicle speed for each hour. The vehicles are arranged in 12 ranges, the first range is for vehicles
moving below the lower speed threshold (LST), the last range is for vehicles moving at a speed
higher than the upper speed threshold (HST). The interval between LST and HST is than divided into
10 ranges. For example, for default configuration: LST = 25 and HST = 125, number of vehicles will
be distributed to the following ranges: 0-24km/h, 25-35km/h, 36-45km/h ... 116-125km/h and >
125+ km/h.
 Allow review prolongation - Enabling this option allows the last panel duration of the activated
scenario to be extended until the end of vehicle detection.
 Show one speed per vehicle - when switched on, the device shows only one or the first vehicle
speed detected.
4.6.4 Demonstration working mode of radar sign

The demo mode simulates vehicle arrival at different speeds and is used for presentations and testing of
devices. Demo mode is generally a supported function of a radar device, it is not supplied as needed.
Settings:
 Demo mode - activate or deactivate demo mode.
 Demo stat logging - enable or disable the logging of radar statistics in demo mode.
 Demo speeds and delays table - a table in which the values of the simulated vehicle speed and the
simulated time between two vehicles are set. The table is changeable, so the column values can be
changed. When demo mode is activated, the sign will be working according each simulated speed.
If speed is set to 255, that means that demo mode simulation will start from beginning, simulating
first speed of the table.
 Current demo table index - indicates the row number of the Demo table whose speed is currently
displayed on the device.
4.7 Setting the time of the internal clock

There is high precision digital clock built into DMV devices. That is an integral circuit that keeps track of the
current time and date. Information about the correct time and date is extremely important for the proper
operation of the scheduler, as well as for the correct entry of information about events that have occurred
in the device. The integrated circuit comes with a battery, which serves to power the clock in the event of a
power failure. The precision of the clock is 2 ppm, i.e. the difference with the exact time on an annual basis
can vary up to 1 minute.
The RTC technique can be used to:
 display the time/date of the internal clock,
 synchronize the time/date of the device with the time/date of the computer or tablet,
or
 to manually adjust the time and date.
39 od 48
Available commands:
Refresh – download the current time from the device.
Set system time – sync device time with computer/tablet/smartphone time.
Set manual time – manual time setting. After entering the time and date in the "Manual time" fields, write
it to device by clicking this button.
Set daylight saving time – setting DLS (Daylight saving time) region to the device.
4.8 Firmware update

The Firmware Loader technique is used for loading firmware (device software) into the device.
The software needs to be stored on a computer/tablet/smartphone.
Choose HEX file – allows browsing and choosing hex file

Update Firmware – loading of firmware is beginning by clicking on this button.
40 od 48
4.9 GPS setting

Devices with a built-in GPS receiver have information about their location. Location information can be used
in many ways. It is possible to generate an event if a device location changes out from given radius: device
location can be monitored from remote location on the map by using the DMV Cloud Control application or
DMV web portal.
The GPS technique in Command Console allows you to check and adjust following GPS parameters:
 Current Location - shows the current coordinates of the device
 Geofencing radius – the circle in which location change of device is ignored. If the device moves out
of a radius, the device generates an alarm.
 Arm device – if this this option is enabled, current location of device is locked and device will be
armed. The movement of the device is calculated relative to the locked location.
 Last armed location - shows the coordinates of the last locked location.
4.10 Push button for quick settings

Some types of devices that have the ability to display numbers and characters have a built-in button on the
case, which is used to quickly change some parameters. The parameter setting is monitored on the display
of the device itself.
4.10.1 Adjusting the parameters by using of push button

To change the parameters with the push button, do the following:
 Hold down the key until the first parameter indicator appears. The parameter indicator should blink.
 Navigating to the next parameter indicator is done by pressing a push button.
 If the push button was not touched while the parameter indicator is blinking, the first digit of the
parameter value will flash after a few seconds.
 Pressing the push button again changes the value of the first digit. If we do not press a push button
for a few seconds, the next digit will flash, and so on.
 After the last digit of the parameter value was set, the parameter indicator will blink again.
NOTE: The push button must be held for about 10 seconds to restore the initial settings.
4.10.1.1 Adjustment parameters on Speed signs
Parameter indicators available:
Triggering speed 1 (TS1)
41 od 48
Triggering speed 2 (TS2)

“Default” pictogram - working mode without vehicles
Pictogram 1 - working mode when there is vehicle with speed greater then TS1
Pictogram 2 - working mode when there is vehicle with speed greater then TS2
4.10.2 Push button settings

The Push-button Adjust technique allows user to adjust the operation of the button. It is possible to toggle
some of the parameters on or off in the setup list, set the initial value of a parameter, etc.
The following settings are available in the technique window:

 Active - This option activates or deactivates push button operation.
 Time out for next digit (1/10s) - the time for the digit or parameter indicator to blink before moving
to the next digit or to the next parameter indicator. The recommended value is 30 (3 seconds).
 Passivity timeout (1/10s) - time of push button inactivity, after which the device exits the
parameter setting and the traffic sign resumes normal operation. The recommended value is 250
(25 seconds).
 Hold to initialize all parameters (1/10s) - Hold time to initialize all parameters. The recommended
value is 100 (10 seconds).
 Reset - When the reset is enabled, the device is reset after the parameter settings are completed.
The settings are confirmed by pressing the Set button.
Table parameters offers the following settings:

 Name - parameter name. It depends on the type of device and the user cannot change it.
 Name on the display - these are the parameter indicators that appear on the display of the device.
They can be changed in the table itself.
 Edit - by checking, a parameter is added to the adjusting list, while all unselected ones remain
invisible for adjusting with the push-button. The setup process is shortened because unselected
parameters will not be displayed on the device display.
 Init - selecting this allows initialization of a parameter in the initialization process.
42 od 48
 Initial value - the value of a parameter that is reverted to during the initialization process.
4.11 Adjusting Police Blinkers

The Police Blinkers technique allows to adjust the parameters of so-called police blinkers. There are three
police flashers in the unit. One white blinker working independently and two blinkers red / blue or blue /
blue working in pairs (alternating).
The setting of the blinkers is separated by separately adjusting the operation of the white blinker and
separately adjusting the blinkers that work in pairs.
The following settings are available:
 T1 - the time (ms) of the blinker is on or the blinker is off. It is the same time that the blinker is on
and off.
 N - number of times the blinker will light up (pulse number) before taking a break T2.
 T2 - the duration (ms) of the blinking off before the N is lit.
When the blinkers are paired, they alternate between each other. One turns on N times in a row, followed
by pause T2, and then another blinks N times in a row, and so on.
The default values are (N = 3, T1 = 7, T2 = 15).
43 od 48
4.12 Operate the vehicle roof-top sign lifter

In cases where the devices are mounted on the roof of the vehicle, a special device called the DMV
automatic lifter is used to change the position of the device to vertical or horizontal.
4.12.1 Lifting and lowering the device

Technique Rooftop is used to control the lifter.
 Up command - as long as the Up button is held, the unit is raised to a vertical position. As soon as
the button is released, the device stops.
 Down command - as long as the Down button is held down, the unit is lowered to a horizontal
position. As soon as the button is released, the device stops.
44 od 48
4.13 Device parameters structure

Each type of device has its own structure of parameters and tables. Parameters and tables are grouped into
sections / parameter groups. Some sections are common to all types of devices, while other sections and
parameters are included depending on the type of device.
The Parameters technique show all groups of device parameters. The technique is for advanced users while
other users are advised to use other techniques to manage the device.
5 COMMAND CONSOLE SETTINGS

The following categories are available in the Settings section:
5.1 Cloud
The Cloud option allows you to set the server address. The default address is www.dmv-cloud.com.
5.2 Techniques
Provides manual or automatic updating of techniques. Internet is required to update the techniques.
5.2.1 Manual updating of techniques

Under "Techniques" to manually update from the cloud, select the "Update techniques" button.
5.2.2 Automatic updating of techniques

In the "Techniques" section, select the "Enable technique auto-updates" button for enabling auto-update
from the cloud. The update is automatically done every time the application is launched if there is new
version of the technique.
5.3 My devices
The "Devices" option allows you to adjust the devices which are already in Device List.
5.3.1 Settings
5.3.1.1 Set default technique
Select the technique that will be displayed first when you enter the device.
45 od 48
5.3.1.2 Baud rate

Baud-rate for RS232 serial communication - 19200 or 9600;
5.3.2 Download from Cloud

Retrieve parameters, icons, layout and other necessary data from the cloud.
5.3.3 Register on cloud

Lets registering (send parameter structure) device to the cloud.
5.3.4 Set device location

Setting the location of the Tablet / Smart Phone/PC to be the location of the device on the cloud map. This
should be done when user is at sign location so it can update real location of the sign to the cloud.
5.3.5 Remove
Remove button deletes the device from the list.
NOTE: After this action, the device will be unavailable for on-site or offline work until it get discovered
again.
5.4 Communication
This section allows to select network interface. Other settings are: Device data transfer, UDP, TCP, Serial and
Bluetooth connection parameters. Do not change without consultation with manufacturer.
5.5 Language
Choosing the language of the application interface. List of supported languages are given in next 2 in section
6.2 Annex 2.
5.6 Licence
Under development.
5.7 About
Provides information on application version, application creation date, software number and configuration.
5.8 Developer tools

Tools for developers of the application.
5.9 Log out

Logs out current user.
5.10 Clear Cache

Clear Cache option, delete the local application folder (all devices and accounts).
NOTE: Deleting a local folder will remove all the techniques, files, and settings downloaded from the server.
Also, all discovered devices and all data downloaded from the device will be lost.
6 ANNEXES
6.1 Annex 1
46 od 48
Event group
Event group Events
code
1 TURN ON 0 – SOFTWARE ON
1 – POWER ON
129 – POWER OFF
2 DISPLAY SCENARIO 1 – DYNAMIC PANELS CHANGE IN RHYTHM
CHANGED 2 – DYNAMIC PANELS CHANGE OUT OF RHYTHM
3 – FLASHERS CHANGED
4 – ACTIVE SCENARIO CHANGED
5 – SST COMMAND HAPPENED
3 TEMPERATURE 0 – HEATER ON
128 – HEATER OFF
1 – FAN ON
129 – FAN OFF
2 – TEMPERATURE WARNING
130 – END OF TEMPERATURE WARNING
3 – TEMPERATURE ALARM
131 – END OF TEMPERATURE ALARM
4 LED ERROR 1 – OPEN LED ERROR STATUS CHANGED
2 – SHORT LED ERROR STATUS CHANGED
3 – LED ERROR STATUS CHANGED
4 – ALARM: NUMBER OF MAX LED ERRORS EXCEEDED
132 – END OF ALARM: NUMBER OF MAX LED ERRORS EXCEEDED
5 – THERMAL ERROR STATUS CHANGED
6 – THERMAL ALARM
134 – END OF THERMAL ALARM
5 BATTERY 0 – OVER-VOLTAGE
128 – END OF OVER-VOLTAGE
1 – LOW VOLTAGE
129 – END OF LOW VOLTAGE
2 – DISPLAY OFF
130 – DISPLAY ON
6 HARDWARE 0 – LIGHT SENSOR 1 ERROR
128 – END OF LIGHT SENSOR 1 ERROR
1 – LIGHT SENSOR 1 DIRTY
129 – LIGHT SENSOR 1 NOT DIRTY
2 – LIGHT SENSOR 2 ERROR
130 – END OF LIGHT SENSOR 2 ERROR
3 – LIGHT SENSOR 2 DIRTY
131 – LIGHT SENSOR 2 NOT DIRTY
4 – DOOR OPEN
132 – DOOR CLOSED
5 – DISK ERROR
133 – END OF DISK ERROR
7 TIMER 1 – MOMENT HAPPENED
2 – PERIODIC TIMER IS RAN OUT
3 – OBLAK KEEP ALIVE TIMER RAN OUT
4 – SCADA PERIODIC TIMER RAN OUT
8 GPRS CALL 1 – AUTHORIZED CALL
2 – AUTHORIZED SMS
3 – UNAUTHORIZED CALL
9 OBLAK 1 – CLOUD SERVER CONNECTION CAN NOT BE ESTABLISHED ERROR
COMMUNICATION 2 – REPLY FROM CLOUD SERVER TIMEOUT ERROR
3 – SESSION DURATION TOO LONG ERROR
4 – GPRS MODEM ERROR
5 – CAN NOT SEND TO CLOUD
6 – CAN NOT SEND SMS
7 – CAN NOT SEND TO SCADU
47 od 48
Event group
Event group Events
code
8 – COMMUNICATION TIMEOUT ERROR
9 – CLOUD CONNECTION TERMINATED BY CLOUD SERVER
10 MEMORY 1 – VEHICLE BY VEHICLE LOG BUFFER IS FULL
2 – EVENT LOG BUFFER IS FULL
3 – TEMPERATURE LOG BUFFER IS FULL
4 – VOLTAGE LOG BUFFER IS FULL
5 – INTERNAL TEMPERATURE LOG BUFFER IS FULL
11 GPS 1 – GPS COORDINATES GOT CHANGED
12 RADAR 1 – VIOLENT DRIVER
2 – STREET CONGESTION
130 – END OF STREET CONGESTION
3 – RADAR IS PASSIVE
131 – RADAR IS NO MORE PASSIVE
13 SAMPLES 1 – MEASUREMENT ALARM CHANGED
6.2 Annex 2
Language
1 English (UK)
2 English (US)
3 Serbian
4 Serbian (LAT SCRIPT)
5 Deutsch (DE)
6 Polish (PL)
48 od 48

User Manual: Command Console Application

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User Manual: Command Console Application

Uploaded by

Copyright:

Available Formats

USER MANUAL

Command Console Application

4.3 Brightness settings...........................................................................................................26

Document Control Date

1.2 About the app

1.2.1 Supported Devices and Operating Systems

2 DOWNLOADING THE APPLICATION

2.1 Download from the site

2.2 Downloads via android app: DMV App Store

3 CONNECTING TO THE DEVICE FOR THE FIRST TIME

3.2 Initial interface

Three sections are available in the main menu:

3.3 Discovering and adding devices

4. Wait for confirmation

3.3.1 Discovering device over LAN (Local Area Network)

3.3.2 Discovering devices via Wi-Fi

3.3.3 Discovering devices via Bluetooth

3.3.4 Discovering devices by cable (serial RS232 communication)

3.3.5 Discovering devices via SMS

3.4 List of discovered devices

Available sections in the techniques panel:

4 WORKING WITH DEVICES

4.1.2 Manual activation of scenario

4.1.3 Scenario activation by scheduler

NOTE: Only one mode can be active.

4.1.3.2.3.1 Available options for working with calendar

4.1.3.3.3 Scenario settings

4.1.4 Scenario activation by vehicle

4.1.4.1 Scenario plans

4.1.5 Activate scenarios via digital inputs

4.1.6 Editing scenarios

Add animation - adds animation

Add bitmap - adds pictograms

Add text line - adds a line of text

Confirmation of panel changes.

4.1.6.1.3 Display date, time and temperature

Time / Date / Temp - Choose between time, date and temperature.

 By selecting the element on panel

4.1.7 Working with media

4.2 Setting up cloud connection

4.2.1 Setting up the cloud connection

Server IP address – IP address of the cloud server.

4.2.2 GPRS modem setup

4.2.2.1 GSM info and SMS settings

Table of telephone numbers and privileges:

4.3 Brightness settings

4.3.1 Setting the minimal brightness

4.3.2 Brightness regulation according to light sensors

4.3.3 Setting the fixed brightness

4.3.4 Brightness regulation according the daytime

4.3.5 External brightness control

4.4 Device information

4.4.1 Basic device information

4.4.2 Hardware maintenance

4.4.2.1 Checking current hardware status

4.4.2.1.5 Checking the detection of the radar

4.4.3 Information given by LED error technique

Information about the LED errors in LED error technique.

Available settings are:

4.5 Events and logs

4.5.2 Event logs stored in device’s memory

4.5.3 Actions on events

4.5.3.1.1.6 Battery events „Batt“