Drucegrove DragonFly TFT20 Series, DragonFly TFT022, DragonFly TFT500, DragonFly TFT024, Firefly TFT300 Series User Manual
...
User Manual
Document Version 1.4
23/11/2015
Drucegrove DragonFly User Manual 1.4 Page 2
Contents
Introduction ........................................................................................................................................................ 5
Drucegrove TFT Feature Comparison .................................................................................................................... 8
DragonFly Driver Hardware and Operating System ............................................................................................... 9
DragonFly Display Settings ................................................................................................................................... 9
DragonFly Core Software and Configuration ....................................................................................................... 10
DragonFly Boot Sequence .................................................................................................................................. 10
Micro SD Card .................................................................................................................................................... 11
DragonFly System Installation ............................................................................................................................ 12
Connecting to a Single Elevator .................................................................................................................................. 12
Connecting to Multiple Elevators ............................................................................................................................... 14
RS485 Network ........................................................................................................................................................... 15
Ethernet Network ....................................................................................................................................................... 16
DFX Layout and XML Configuration Files ............................................................................................................. 18
DFX Files ...................................................................................................................................................................... 18
XML Files ..................................................................................................................................................................... 18
Manually Creating and Editing XML Files .................................................................................................................... 19
Settings XML File ................................................................................................................................................ 21
Indicator Settings ........................................................................................................................................................ 21
Network Settings ......................................................................................................................................................... 23
Date and Time Settings ............................................................................................................................................... 23
Video Settings ............................................................................................................................................................. 24
Identity XML File ................................................................................................................................................ 25
Identity Settings .......................................................................................................................................................... 25
Network Settings ......................................................................................................................................................... 25
Groups ......................................................................................................................................................................... 26
DragonFly Designer Software ............................................................................................................................. 27
DragonFly Layouts (DFX Files) ............................................................................................................................. 28
Static Background Image Layer ................................................................................................................................... 29
‘Element Canvas’ Root Element Layers ....................................................................................................................... 30
‘Dynamic Ticker Text’ Root Element ........................................................................................................................... 30
‘Video’ Root Element .................................................................................................................................................. 30
Dynamic Sub Elements ................................................................................................................................................ 31
Element Conditions ..................................................................................................................................................... 32
Video Element ................................................................................................................................................... 35
Supported Video Formats ........................................................................................................................................... 37
Supported Audio Formats for Video ........................................................................................................................... 38
Supported Containers for Video ................................................................................................................................. 38
Supported Network Protocols for Video..................................................................................................................... 39
Live Network Video Overview ................................................................................................................................. 39
Configuring the DragonFly for Live Network Video ................................................................................................ 40
DragonFly Variables ........................................................................................................................................... 41
Drucegrove DragonFly User Manual 1.4 Page 3
Live Data Feeds .................................................................................................................................................. 45
RSS (XML) Feeds .......................................................................................................................................................... 45
Text Feeds ................................................................................................................................................................... 45
Parser Arguments ....................................................................................................................................................... 47
Variables...................................................................................................................................................................... 47
Source URL .................................................................................................................................................................. 49
Read Actions ............................................................................................................................................................... 49
XML Read Actions ....................................................................................................................................................... 50
Text Read Actions........................................................................................................................................................ 51
Using the DragonFly Designer ............................................................................................................................. 52
Tutorial 1: Opening and Editing a Template Layout ................................................................................................... 52
Tutorial 2: Previewing the Layout ............................................................................................................................... 56
Tutorial 3: Creating an SD Card ................................................................................................................................... 59
Tutorial 4: Creating an Automatic Update USB Drive ................................................................................................. 61
Tutorial 5: Broadcasting a Layout over a LAN ............................................................................................................. 62
Tutorial 6: Creating a New Layout .............................................................................................................................. 63
Tutorial 7: Setting a Background Image ...................................................................................................................... 68
Tutorial 8: Drawing on the Background Layer ............................................................................................................ 70
Tutorial 9: Adding and Configuring Screen Elements ................................................................................................. 74
Tutorial 10: Adding a Dynamic Text Element .............................................................................................................. 77
Tutorial 11: Configuring a Dynamic Text Element to update based on Conditions .................................................... 80
Tutorial 12: Configuring a Dynamic Text Element to act as a timed Text Slideshow ................................................. 84
Tutorial 13: Adding a Dynamic Image Element that updates based on Conditions ................................................... 88
Tutorial 14: Adding Weather Elements ....................................................................................................................... 95
Tutorial 15: Animating Elements based on Conditions ............................................................................................. 104
Tutorial 16: Adding a Video Element ........................................................................................................................ 110
Message Library ............................................................................................................................................... 116
Drucegrove DragonFly User Manual 1.4 Page 4
Important Note
This document is a work in progress, and may not fully explain all aspects of the DragonFly
hardware or software. For any technical questions that are not addressed in this manual, please
contact Drucegrove directly:
Email: technicalsupport@drucegrove.com
Phone: +44 (0)1992 650 486 (Select Option 3)
This document explains the basics of the DragonFly hardware, how the DragonFly core software
operates, and describes how the DragonFly can be set up and configured using the DragonFly
Designer software.
Drucegrove DragonFly User Manual 1.4 Page 5
Introduction
The Drucegrove DragonFly™ range of TFT displays are capable of showing elevator position, direction and emergency
messages in addition to other text, images and rich media. This allows the displays to be branded and customised
match the building they are installed in. The additional text and images can be static (ie building name, company
logo, etc), or dynamic based on the position of the elevator (ie individual floor tenancy information).
The TFT20 Series displays are self contained units with the display and driving electronics integrated into one
package. The screen sizes available are 4.3”, 5.7” and 7.0”, and they have the same built in message image library as
the FireFly™ TFT300 Series indicators.
For larger DragonFly™ displays, the TFT500 Omni Driver can be used. This is based on the same driving electronics as
the TFT20 series but boasts a more powerful processor with graphics accelerating and video decoding hardware, and
a DVI / HDMI output. Drucegrove supply a separate open frame TFT screen and a HDMI to DVI cable for connecting
the screen to the TFT500 Omni Driver. The screen sizes available range from 10.4” to 42”, in 4:3 standard, 16:9 wide
or 4:1 panoramic aspect ratios
The TFT20 Series and TFT500 can be networked via Ethernet, which opens up the possibility of streaming live news
headlines, weather, finance information, transport information (TfL, Nation Rail, bus times etc) and more from RSS
feeds.
Live video can also be displayed on displays driven from the TFT500 Omni Driver. The video is streamed digitally to
the display over Ethernet from either an IPTV source or an IP CCTV camera - either of which can be located anywhere
in the building. Being digital, a single video feed can be streamed to an unlimited number of displays without loss of
quality or the need for boosters or amplifiers.
DragonFly TFT20 Series TFT Position Indicators
Drucegrove’s DragonFly™ TFT20 Series Indicators are available in
three standard sizes: 4.3", 5.7" and 7.0". The displays are fully
customisable, and at their simplest level offer a wide choice of
colours, images, character fonts and arrow styles. They are available
with a choice of two different integrated drivers, the RE1 or the RE2.
The RE1 offers basic drawing options with no animation or video. The
RE2 has hardware accelerated graphics allowing smooth animation,
alpha blending and live video playback.
The position indicators may be configured for elevator car or landing displays, and are capable of showing up to
three character floor designations, car direction arrows, hall lantern arrows, full screen messages and pictograms.
They are fully compatible with the Drucegrove 2-Wire™ System and OTIS® Serial Data, and may also be used as
stand-alone position indicators with binary, Gray or discrete wire-per-floor inputs.
Every aspect of the display can be configured, and special display content can be configured to show or change at
certain floors, for certain message responses, or even for a specific time of day or date.
The position indicators can be configured over a LAN via a standard web browser, or alternatively the on-board
micro SD card can be removed and reconfigured freely from any computer.
Drucegrove DragonFly User Manual 1.4 Page 6
DragonFly TFT500 TFT Screen Driver
The DragonFly™ TFT500 Omni Driver works with any readily available
DVI or HDMI display, so if our standard range of sizes is not enough,
choose another! For interfacing to your elevator, the Omni Driver
connects to either the Drucegrove 2-Wire™ System, OTIS ® Serial Data,
or with the addition of an IND059 input mode, non-proprietary binary /
Gray / discrete signals. The unit can be networked via RS485 and
Ethernet for live data feeds and live network video streams.
Take advantage of their most sophisticated features. Use the latest technology in processing graphics to combine
elevator information with scrolling text feeds, rich media and video content. Our in-house team will take your
concept, images and logos to produce a result that suits your building. And with the open connectivity that we have
provided you will never be out of date.
We can supply any size of open-frame TFT display, with a lens and any mountings and faceplates needed for fitting
inside your elevator cars, and all necessary networking peripherals for connecting together a system of displays.
Our in-house metalwork facilities allow us to mount any display in almost any location with a professional finish and
minimal hassle.
For basic operation, the TFT500 simply needs a 2-Wire input for power and elevator data, and a screen connected to
the HDMI / DVI output. For data synchronisation and live data or video feeds, the Ethernet Network would need to
be connected:
TFT500
2-Wire Supply Input
Two pairs of + and - terminals are
present for Loop In / Loop Out
2-Wire connectivity
Ethernet Network
HDMI / DVI Output
Connect HDMI-to-DVI cable
Drucegrove DragonFly User Manual 1.4 Page 7
DragonFly Open Frame TFT Screens for use with the TFT500 Screen Driver
Drucegrove offer a standard range of three open frame industrial grade TFT
displays to run from the TFT500 Omni Driver - a 10.4”, 15” or 19” screen with
suitable mountings and either toughened glass or polycarbonate protection.
The screens have a DVI or HDMI input, allowing them to be driven directly from
the TFT500 output.
The standard three screen sizes have the following technical specifications:
10.4”
15”
19”
Resolution (pixels)
1024 × 768
1024 × 768
1280 × 1024
Luminance (cd/m2)
500
350
600
Contrast Ratio
1200:1
1000:1
2000:1
Viewing Angle
88 / 88 / 88 / 88
85 / 85 / 85 / 85
89 / 89 / 89 / 89
Backlight Half Life
50000 Hours
50000 Hours
50000 Hours
A wide range of other non-standard screen sizes are also available in an open frame mounting with a HDMI or DVI
input, ranging from 7” to 70” in diagonal size and in 4:3 standard, 16:9 wide or 4:1 panoramic aspect ratio. Refer to
screen specific documentation or contact Drucegrove for more information.
Note: External TFT screens require their own power supply, and are not powered from the 2-Wire bus.
DVI Input
Connect HDMI-to-DVI cable
Display Power Supply
from local 12V 4A DC PSU
Screen Power Button
The state of this button is remembered
after power down, and this button leaves
the factory in the ’on’ state, so it should
not need to be pushed again
Drucegrove DragonFly User Manual 1.4 Page 8
Drucegrove TFT Feature Comparison
The following comparison table shows the feature differences between the TFT300 series FireFly, TFT20 Series
DragonFly and the TFT500 DragonFly Omni Driver:
TFT300 Series (4.3”, 5.7” & 7.0”)
TFT20 Series (4.3”, 5.7” & 7.0”)
TFT500 Omni Driver (from 10.4”)
Integrated TFT display (4.3”, 5.7” or 7.0”)
Yes
Yes
No
DVI / HDMI output for external TFT display (10.4” to 42”)
No
No
Yes
Drucegrove 2-Wire™ input compatible
Yes
Yes
Yes
OTIS® Serial Data input compatible
Yes (at additional cost)
Yes (at additional cost)
Yes (at additional cost)
Stand Alone (binary/Gray/discrete) input compatible
No
Yes (with addition of IND59)
Yes (with addition of IND59)
Ethernet network connectivity (wired)
No
Yes
Yes
RS485 network connectivity
No
No
Yes
Display elevator position and direction
Yes
Yes
Yes
Display elevator status and emergency messages
Yes
Yes
Yes
Display elevator floor tenancy information per floor
No
Yes
Yes
Display time and / or date
No
Yes
Yes
Display static text, logos and images
No
Yes
Yes
Display live RSS feeds (eg news, weather, TfL, etc)
No
Yes
Yes
Display Video from local file on micro SD card
No
Yes (RE2 version only)
Yes
Display Video from remote live network source (IPTV)
No
Yes (RE2 version only)
Yes
Display Video from remote network camera (IP CCTV)
No
Yes (RE2 version only)
Yes
Built in library of over 150 full screen elevator message images
Yes
Yes
No
Standard range of themes available to choose from
Yes
Yes
No
Background can be configured as any colour or image
No
Yes
Yes
Text and arrows can be configured as any colour
No
Yes
Yes
Text can be configured as any font
No
Yes
Yes
Arrows can be configured as any shape
No
Yes
Yes
Screen elements can be shown / hidden on elevator events
No
Yes
Yes
Screen elements can be shown / hidden at specific times / dates
No
Yes
Yes
Display options configured via dipswitches
Yes
No
No
Display options stored in XML files on micro SD card
No
Yes
Yes
Display options can be remotely changed via network
No
Yes
Yes
Built in audio amplifier for speech and/or video audio
No
No
Yes
Built in gong
Yes (at additional cost)
Yes (with addition of GNG24)
Yes (with addition of GNG24)
Supplied with purpose designed mountings
Yes
Yes
Yes
Supplied with lens
Yes
Yes
Yes
Supplied with faceplate
Yes (at additional cost)
Yes (at additional cost)
Yes (at additional cost)
Supplied in surface mount fixture
Yes (at additional cost)
Yes (at additional cost)
Yes (at additional cost)
Low Profile, with option of remote TFT display
Yes (at additional cost)
No
Yes
Vandal Resistant to EN81-71 Category 2
Yes (at additional cost)
Yes
Yes (at additional cost)
Meets elevated temperature requirement of EN81-72
Yes
No
No
Runs on Windows CE operating system
No
Yes
Yes
Battery backed, network synchronisable real time clock
No
Yes
Yes
2 discrete outputs for driving external LED arrows
Yes
No
Yes
2 addition general purpose outputs
No
No
Yes
4 general purpose inputs for triggering screen events
No
No
Yes
Drucegrove DragonFly User Manual 1.4 Page 9
DragonFly Driver Hardware and Operating System
The DragonFly hardware is based around an ARM Cortex processor, and runs the Microsoft Windows CE 6.0
operating system. The hardware and operating system were specifically designed for embedded industrial
applications. There are no mechanical drives – all storage is flash based. The hardware does not require active
cooling, and is not damaged by power loss or cycling – even if the boot sequence is interrupted. If power is lost and
restored, the DragonFly will automatically reboot and recover without issue.
Internally, the DragonFly has a non-volatile flash drive which contains basic boot loader software. This boot loader
runs the main DragonFly software automatically on power up. The main DragonFly software and all relevant layout
and configuration files are stored on a removable micro SD card (refer to individual product wiring diagrams for
micro SD card location).
The TFT20 series DragonFly driving hardware can either be built around the RE1 or the RE2 engine. The RE1 offers
basic drawing options with no animation or video. The RE2 has hardware accelerated graphics allowing smooth
animation, alpha blending and live video playback.
There are no engine options with the TFT500, and hardware accelerated graphics is available in this unit by default.
DragonFly Display Settings
The TFT022, TFT023 and TFT024 have an integrated screen with the following resolutions
TFT022 has a 4.3” screen with a resolution of 480×272 pixels
TFT023 has a 5.7” screen with a resolution of 640×480 pixels
TFT024 has a 7.0” screen with a resolution of 800×480 pixels
The TFT500 Omni Driver can be configured to output any resolution on its DVI output. The resolutions of the
standard screen sizes are as follows:
10.4” screen has a resolution of 1024×768 pixels
15” screen also has a resolution of 1024×768 pixels
19” screen has a resolution of 1280×1024 pixels
Note: All DragonFly screens are driven at 16 bit colour depth (RGB 5-6-5) by default.
Drucegrove DragonFly User Manual 1.4 Page 10
DragonFly Core Software and Configuration
All software configuration, fonts, images, data files, etc are stored on the micro SD card:
The core software itself is stored under the “\Storage Card\Bin\” directory.
All of the software and layout settings are stored in XML files under the “\Storage Card\Config\” directory.
Layouts are stored in DFX files under the “\Storage Card\Config\Theme\” directory.
Other data is stored under “\Storage Card\Data\”. This includes fonts, and the message image library files.
The software and configuration are automatically set up on the micro SD card by the DragonFly Designer software.
The same DragonFly core software works on all TFT20 Series and TFT500 hardware, regardless of the processor
engine or screen type.
DragonFly Boot Sequence
The RE1 based DragonFly has no internal flash, so its boot sequence is as follows:
1. A registry key is present to automatically run “\SD Card\Startup\Startup.exe”
2. Startup.exe sets up the desktop environment, installs any default fonts, configures the Ethernet network,
initialises the data receiver firmware, and finally runs “\SD Card\Bin\DragonFly.exe”
3. DragonFly.exe shows a white splash screen with a DragonFly logo as it loads, before finally displaying the
screen layout selected in the Settings.xml file.
If the Startup.exe software does not automatically run after creating a new SD card, it will need to be manually run
the for the first time using a USB mouse/keyboard and the Windows CE file explorer. Double click on Device,
followed by SD Card and then Startup. Then double click on Startup.exe. The software will automatically create the
auto-run registry key for the next time the device boots up.
The RE2 and RM2 based DragonFly has the Startup.exe software pre-installed in internal flash, so its boot sequence
is as follows:
1. Startup.exe is run from the internal flash, and installs any default fonts, configures the Ethernet network,
initialises the data receiver firmware, and finally runs “\Storage Card\Bin\DragonFly.exe”
2. DragonFly.exe shows a white splash screen with a DragonFly logo as it loads, before finally displaying the
screen layout selected in the Settings.xml file.
As a failsafe, The Windows CE image on the RE2 and RM2 will also launch “\Storage Card\Startup\Startup.exe”
automatically. This instance of the software will check the internal flash instance and replace it if it is not fully
present or has not executed in a timely manner.
If there is no micro SD card inserted, the Startup.exe software on the internal flash will not find “\Storage
Card\Bin\DragonFly.exe”, and will show an error message on the screen. The unit will then automatically reboot
itself after 2 minutes.
Drucegrove DragonFly User Manual 1.4 Page 11
Micro SD Card
The micro SD card must be present at all times in order for the DragonFly to operate. If the micro SD card is ever
changed, then it is recommended that the DragonFly be rebooted.
The micro SD card must be formatted to FAT, and the maximum capacity is 4GB. Note that SDHC and SDXC micro SD
cards are not supported.
On the TFT20 Series the micro SD card socket is on the smaller PCB raised off the main PCB (there is a cut out in the
back plate to access the socket), and there is a pair of reset pins between behind the input terminals. The reset pins
are labelled RST, and should be shorted to each other to perform a reboot:
On the TFT500 the micro SD card socket is on the side, and there is a reset button between the RS485 terminal and
the input terminals, which should be pressed to perform a reboot:
Reset Button
micro SD Card
Reset Pins (RST)
micro SD Card
Drucegrove DragonFly User Manual 1.4 Page 12
DragonFly System Installation
Connecting to a Single Elevator
For the most basic operation of displaying the elevator car position and direction, a DragonFly only needs to be
connected to a Drucegrove 2-Wire bus. The 2-Wire bus will provide both power and data to the DragonFly driving
circuitry. For a TFT20 series position indicator, this 2-Wire bus will also power the TFT screen. For the TFT500 Omni
Driver, a separate external screen will be provided and this will have a 12V DC power supply which will need mains
110-230V AC input.
The following diagram shows how a TFT024 positioned inside the elevator car should be connected back to a
Drucegrove IND055 2-Wire controller:
Additional 2-Wire equipment may be connected to the 2-Wire bus, including other FireFly and DragonFly TFTs (of
mixed sizes), LED segment and dot matrix PIs, gongs and speech announcer units.
Elevator Car
TFT024
DragonFly
7.0” TFT PI
Machine Room
110-230V
AC Input
}
Inputs from
Elevator Controller
2 Wires for
Power and Data
IND055
Controller
Interface
24V DC
PSU
Drucegrove DragonFly User Manual 1.4 Page 13
The following diagram shows how a TFT500 with an external TFT screen positioned inside the elevator car should be
connected back to a Drucegrove IND055 2-Wire controller.
Note that a local 12V DC power supply requires a 110-230V AC input inside the elevator car:
12V DC
PSU
TFT Screen
with DVI Input
TFT500
DragonFly
Omni Driver
110-230V
AC Input
Machine Room
110-230V
AC Input
}
Inputs from
Elevator Controller
2 Wires for
Power and Data
IND055
Controller
Interface
24V DC
PSU
Elevator Car
Drucegrove DragonFly User Manual 1.4 Page 14
Connecting to Multiple Elevators
It is possible to connect the TFT500 to the 2-Wire bus of multiple elevators. This is done using IND079 2-Wire to
RS485 transcoders. The IND079s each take in a single 2-Wire feed, and communicate back to single TFT500 via an
RS485 network.
It is possible to have up to 63 IND079s on an RS485 network back to a single TFT500. The DragonFly Designer
software can be used to configure screen elements to look at specific elevator position and status data on the RS485
bus rather than the local 2-Wire input on the DragonFly itself.
The following diagram shows how two elevators in a duplex could be connected to a single TFT500 to show the
position and status of each elevator car on one screen:
For more elevators, additional IND079s would be required (up to a maximum of 63 units), and their RS485 networks
would be “daisy chained” together. The maximum transmission distance of the RS485 is 4000 feet, but it is
recommended that all IND079s be kept local to the TFT500, and any long distance runs be on the 2-Wire bus.
ON
110-230V AC
Mains Input
24V DC
Power
Supply
DVI to HDMI
UTP
IND079
2-Wire Supply (Left) Loop In/Out
Provides both power and elevator data
Connect IND055 output from left elevator
and ensure that the address is set to 1
(dipswitch 8 on only)
2-Wire Supply (Right) Loop In/Out
Provides both power and elevator data
Connect IND055 output from right elevator
and ensure that the address is set to 2
(dipswitch 7 on only)
TFT500
CAT5
Ethernet Connection
to network for live data
feeds and time / date
synchronisation
ON
ON
IND079
2-Wire supply looped from one IND079 input to
TFT500 input, to provide TFT500 with power
Ensure that the network address is
set to 3 (dipswitches 7 and 8 on),
and the adjacent RS485 Master
jumper is set to the ON position
Drucegrove DragonFly User Manual 1.4 Page 15
RS485 Network
The TFT500 Omni Driver has an on board RS485 port. This can currently be used for multi-elevator based TFT
displays using a network of IND079 transcoders.
The RS485 network should be connected together in a “daisy chain” using unscreened twisted pair.
All units on the RS485 network should have a unique network address, which is selected via the on board Network
Address dipswitch on the TFT500 and IND079. The network address is linked to the least significant byte of the IP
address of a TFT500 by default (this can be changed in the DragonFly settings).
There needs to be one TFT500 on the RS485 network acting as an RS485 master. This master mode function can be
selected via a jumper next to the Network Address dipswitch.
Note: The RS485 wires are polarised so should be connected to each terminal block in the same orientation.
Note: All RS485 wiring needs to be twisted pair. If there are untwisted sections, the network will not work.
Drucegrove DragonFly User Manual 1.4 Page 16
Ethernet Network
The Ethernet Network can be used to connect one or more DragonFly units back to a PC / Laptop for remote
simultaneous configuration, real time clock synchronisation, live data feeds from Ethernet based sensors or internet
based RSS feeds, and live multicast IPTV based video or an IP camera feed.
The Ethernet network uses standard IP based protocols, and so standard CAT5 cabling and Ethernet switches may be
used. For certain features, managed Ethernet switches are recommended, and may need to be specially configured
for IGMP traffic (see information on the Video Canvas for more information, or contact Drucegrove directly).
The following diagram shows how a TFT024 should be networked from an elevator car back via a machine room to a
central building management room:
Note that the maximum distance of an Ethernet run is 100 meters (328 feet), and if the trailer run from the TFT
screen back to an Ethernet switch is over this distance, Ethernet Extenders need to be used (as shown in the above
diagram). If the distance is less than 300 feet, a CAT5 trailer may be used without Ethernet Extenders.
Note: All Ethernet wiring needs to be twisted pair. If there are untwisted sections, the network will not work.
Elevator Car
TFT024
DragonFly
7.0” TFT PI
Machine Room
110-230V
AC Input
}
Inputs from
Elevator Controller
2 Wires for
Power and Data
IND055
Controller
Interface
24V DC
PSU
110-230V
AC Input
110-230V
AC Input
Ethernet
Extender
4 × UTP on Trailer
Max length 300 feet, or 2500 feet if
Ethernet Extenders are used
CAT5
Building Management Room
CAT5 Ethernet connections
to other machine rooms
CAT5
Ethernet
Extender
110-230V
AC Input
Ethernet
Switch
PC / Laptop
Unscreened Twisted Pair for network
2× AWG14 cables for 24V power and data
CAT5 for network (max length 300 feet)
HDMI (HDCP encryption not supported)
110V - 230V Mains power cable
Drucegrove DragonFly User Manual 1.4 Page 17
The following diagram shows how to network a TFT500 Omni Driver inside an elevator car:
Unscreened Twisted Pair for network
2× AWG14 cables for 24V power and data
CAT5 for network (max length 300 feet)
HDMI (HDCP encryption not supported)
110V - 230V Mains power cable
12V DC
PSU
TFT Screen
with DVI Input
TFT500
DragonFly
Omni Driver
110-230V
AC Input
Elevator Car
Machine Room
110-230V
AC Input
}
Inputs from
Elevator Controller
2 Wires for
Power and Data
IND055
Controller
Interface
24V DC
PSU
110-230V
AC Input
110-230V
AC Input
Ethernet
Extender
4 × UTP on Trailer
Max length 300 feet, or 2500 feet if
Ethernet Extenders are used
CAT5
Building Management Room
CAT5 Ethernet connections
to other machine rooms
CAT5
Ethernet
Extender
110-230V
AC Input
Ethernet
Switch
PC / Laptop
Drucegrove DragonFly User Manual 1.4 Page 18
DFX Layout and XML Configuration Files
DFX Files
The DragonFly uses a proprietary file format for its screen layouts, with the file extension *.dfx. These files can be
loaded and saved directly from the DragonFly Designer software, and will be loaded directly by the DragonFly core
software. The DFX file contains position and appearance settings for all screen elements, a full size static background
image, and any embedded images and fonts for dynamic screen elements.
XML Files
All device settings are stored in XML (Extensible Markup Language) files on the micro SD card on the DragonFly.
These files are standard text files which can be created and edited using any text editor (ie, Notepad). The DragonFly
Designer software will create all necessary XML files by default when an SD card is created. It should not be
necessary to create or modify XML files manually. There are two main XML files stored under the Config directory on
the micro SD Card:
1. Settings.xml is situated in “\Storage Card\Config\”. This file always has this name, and must be in this
location. It is not an optional file, and the software will fail to load without it. It contains top level settings,
and references the Theme DFX file and an optional Input XML file.
2. Identity.xml is situated in “\Storage Card\Config\”. This file always has this name, and must be in this
location. It is not an optional file, and the software will fail to load without it. It contains several fields for the
sole purpose of identifying the location of the DragonFly unit within a site over a LAN (site name, building
name, elevator group, elevator number, etc). The floor position address is stored in the Identity.xml file,
which is used for car/lantern behaviour. LAN settings are also stored in Identity.xml, including the DHCP
setting and manual IP address settings.
There is one further optional XML file:
3. The Input XML file is situated in “\Storage Card\Config\Input\”. Multiple data files can be stored in this
directory with different names. The Settings.xml file references the input file to use, and it is an optional file;
it is not required for the core software to function. The input file contains settings for IND21 2-Wire
compatibility (floor designation and message table), or input configuration for use with an IND059
binary/Gray/discrete input module.
Drucegrove DragonFly User Manual 1.4 Page 19
Manually Creating and Editing XML Files
Under normal circumstances, the XML files on the micro SD Card should not need to be edited. When creating a
micro SD Card from the DragonFly Designer software, the XML files will be created and configured automatically.
Updates via USB or a LAN will automatically modify relevant XML files accordingly.
Under special circumstances XML files can be created and edited using any basic text editing software. Microsoft
Notepad can be used, but the free GNU text editor Notepad++ (http://notepad-plus-plus.org) is recommended as it has
syntax highlighting for XML files.
Note: XML Files should be in UTF-8 format.
If Microsoft Notepad is used, ensure that the encoding is set to UTF-8 (8 bit Unicode Transformation Format) when
the file is saved (this setting is next to the Save button on the Save As dialog). If UTF-8 is not used, the DragonFly
software will fail to load the XML file.
Drucegrove DragonFly User Manual 1.4 Page 20
The following is an example of an XML file, which has been colour coded to highlight different elements:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Comment -->
<Root>
<SettingGroup>
<Setting>Value</Setting>
</SettingGroup>
<ElementGroup>
<Element> <!-- Comment -->
<Setting>Value</Setting>
</Element>
<Element AttributeName="AttributeValue">
<Setting>Value</Setting>
<Setting>Value</Setting>
</Element>
</ElementGroup>
</Root>
The first line (shown in orange) should always be present; it defines the XML version and encoding, and the
DragonFly software will not load the XML file without this.
Comments (shown in green) can be added to an XML file between <!-- and --> tags.
The XML structure consists of nodes (shown in black) and settings (shown in blue). The names of these nodes and
settings vary depending on the type of XML file (ie, the nodes and settings in the Settings.xml file are different to a
layout XML file).
All nodes and settings must have a matching closing tag, which is the same as the opening tag but with a forward
slash after the < character. If a closing tag is not present or misspelled, the DragonFly software will fail to load the
XML file.
Some elements and settings may have attribute settings (shown in red). The attribute name is followed by an equals
character, and then the attribute value is placed inside quotation mark characters. Multiple attributes can be defined
if necessary, separated by a space. Attributes do not require a closing tag.
Drucegrove DragonFly User Manual 1.4 Page 21
Settings XML File
The general software settings are stored in the Settings.xml file, which can be found under “\Storage Card\Config\”.
This file must always be present for the software to load. The Settings.xml file consists of four main setting groups;
IndicatorSettings, NetworkSettings, DateTimeSettings and VideoSettings.
Indicator Settings
The following settings can be defined in the Settings.xml file, under IndicatorSettings:
Program
Optional free text string value.
Used for administration to identify the SD Card program.
DeviceType
Optional free text string value, “TFT2X” by default.
Used for administration to identify the device type over network.
DeviceName
Optional string value, “DGINDICATOR” by default.
Sets the device name on network and USB device connection.
Theme
Required string value.
Determines the theme DFX file name to use.
The file should be stored under “\Storage Card\Config\Theme\”.
The file name does not include the “.dfx” file extension.
Input
Optional string value.
Determines the input XML file name to use.
The file should be stored under “\Storage Card\Config\Input\”.
The file name does not include the “.xml” file extension.
StorageDivisionKB
Integer value, 15360 by default.
Determines the amount of RAM to use for volatile storage. Volatile storage is
used by Windows CE and the DragonFly software.
Decreasing this value will increase available RAM, but setting too low could
cause system failure. A value of 15360 is recommended.
DisableMessages
Boolean value, false by default.
Used to disable elevator status/emergency messages.
EnableHallLanternArrows
Boolean value, true by default.
Used to disable hall lantern arrows on the display (outputs for external
lanterns will still work, if present).
EnableFloorScroll
Boolean value, true by default.
When true, the floor designation characters will scroll when they change.
The rate of scroll is determined by the FloorScrollTime setting, or if
FloorScrollTime is -1 the scroll rate dipswitches on the IND055 2-Wire
Controller will be used.
EnableFloorFade
Boolean value, true by default.
When true, the floor designation characters will fade when they change.
Fading effects are only available on the RE2. The rate of fade is determined by
the FloorScrollTime setting, or if FloorScrollTime is -1 the scroll rate
dipswitches on the IND055 2-Wire Controller will be used.
FloorScrollTime
Integer value, -1 by default.
When zero, floor designation character scrolling and fading will be disabled.
When set to a positive value, this setting determines the duration of the
scrolling and/or fading effect in milliseconds.
When set to -1 (or any negative value), the duration of the scroll and/or fade
effect is determined by the scroll rate dipswitches on the IND055 2-Wire
Controller.
EnableWatchdog
Boolean value, true by default.
When true, the system will automatically reboot after two minutes if the
software becomes unresponsive. It is recommended that this setting be left
enabled.
ValidFloorDesignations
Comma separated string values, empty by default.
When specified, this setting will limit the floor designation characters that can
be displayed. If a floor designation is received, it will only be displayed if it
exists in the comma separated list, or if this list is empty.
Drucegrove DragonFly User Manual 1.4 Page 22
FloorPriorityActiveTime
Integer value, zero by default.
When a floor designation changes, the system makes screen redrawing its top
priority and disables non-critical events and routines to ensure scrolling
and/or fading effects are smooth. After the scrolling and/or fading, the system
will catch up with missed events and routines. This can delay the next floor
change on very fast moving elevators. This setting will keep screen redrawing
as top priority for a specified number of milliseconds after a floor has
changed. For fast elevators, this setting can be set to a value between 2000
and 5000 to improve responsiveness.
VerifyReceivedAllFloorChars
Boolean value, false by default.
The IND055 2-Wire controller sends out four floor characters at a time (but
typically only 2 or 3 are actually used). This setting instructs the software to
wait for all four characters before updating the display. It is not generally
required, and can be left set to false.
BaseScrollDirectionOnCarDirection
Boolean value, false by default.
Floor levels have an integer address in the IND055 2-Wire Controller, and this
is sent out over the 2-Wire bus. The scroll direction of floor designation
characters is determined by the change in floor level address. If this setting is
set to true, the scroll direction will be determined by the elevator car
direction.
UpdateTimerInterval
Integer value, zero by default.
If a positive non-zero value is used, this sets the interval (in milliseconds) of
the screen update timer. This setting should not have to be changed.
EnableBroadcastLiftInfo
Boolean value, false by default.
When true, the elevator floor designation characters, floor level, direction, etc
will be sent out as UDP packets over the LAN. This can be used for displays
that aggregate the status of multiple elevators. The amount of information
that is sent out is determined by the BroadcastLiftInfoMode setting.
BroadcastLiftInfoMode
Integer value, zero by default.
Can be set to one of the following values to determine the elevator
information that should be broadcast when the EnableBroadcastLiftInfo
setting is true:
0 = Floor, Direction, Door Status and Message
1 = Floor, Direction and Door Status
2 = Floor and Direction
3 = Floor Only
ForceTouchScreenMenu
Boolean value, false by default.
When the mouse is clicked on the screen, the space bar is pressed, or (where
touch screens are fitted) the screen is touched, a menu appears on the screen.
By default, the 4.3”, 5.7” and 7” displays have touch screen capability. As
these screens are primarily used with the RE1, if the RE1 is detected then a
menu is used which is optimised for touch. If an RE2 is detected, a menu is
used which is more comprehensive and intended for use with a mouse and
keyboard. Setting this value to true forces the software to use the touch
friendly menu, for cases where the RE2 is fitted to a 4.3”, 5.7” or 7” screen.
Drucegrove DragonFly User Manual 1.4 Page 23
Network Settings
The following settings can be defined in the Settings.xml file, under NetworkSettings:
UDPPort
Integer value, 3683 by default.
Sets the port for the UDP receiver and transmitter, which is used to
communicate with other DragonFly units and remote administration and
configuration software over the Ethernet network. All units and software on
the network should be configured to use the same port, and 3683 is
recommended as a standard Drucegrove default.
EnableUDP
Boolean value, true by default.
Enables or disables the UDP receiver and transmitter, which is used to
communicate with other DragonFly units and remote administration and
configuration software over the Ethernet network.
EnableHTTP
Boolean value, true by default.
Enables or disables the HTTP web server, which is used for the HTTP control
panel and remote access to files and screenshots.
Date and Time Settings
The following settings can be defined in the Settings.xml file, under DateTimeSettings:
TimeZone
String value, “GMT Standard Time” by default.
Defines the system time zone.
AutoDaylightSaving
Boolean value, true by default.
Enable or disable automatic daylight saving time adjustment.
AutoSyncInternetTime
Boolean value, true by default.
Enable or disable automatic synchronisation of time and date to an internet
based time server.
InternetTimeServer
String value, “time-nw.nist.gov” by default.
Defines the URL of the internet time server to use for synchronisation.
AutoSyncInternetInterval
Defines the interval between internet time synchronisation events.
The setting can be set to one of the following values (EveryDay is default):
Every15Mins
EveryHour
Every6Hours
Every12Hours
EveryDay
EveryWeek
AutoSyncLANTime
Boolean value, true by default.
If enabled, all DragonFly units will synchronise their clocks between
themselves locally over the Ethernet network every day at 02:00.
Drucegrove DragonFly User Manual 1.4 Page 24
Video Settings
The following settings can be defined in the Settings.xml file, under VideoSettings:
OverrideSettings
Boolean value, false by default.
If True, the video settings inside the loaded DFX will be ignored, and the video
settings in the Settings.xml file will be used instead.
VideoURL
String value, empty by default.
The local file location and name, or the URL of a live network video stream.
(Note: This setting will only be used if OverrideSettings is True)
VideoSizeMode
This defines how the video is sized in the video canvas.
Valid options are:
0 = Automatic
1 = Fill Window (stretch)
2 = Fill Window (4:3 aspect ratio)
3 = Fill Window (16:9 aspect ratio)
4 = Do Not Resize
(Note: This setting will only be used if OverrideSettings is True)
VideoThreadPriority
This defines the CPU priority of the video thread. This should not have to be
adjusted, but valid values are:
Highest
AboveNormal
Normal
BelowNormal
Lowest
(Note: This setting will only be used if OverrideSettings is True)
HideWhenNoVideo
Boolean value, false by default.
If True, the video canvas will be hidden when no video is present (ie, live
network video stream is disconnected). Alternative screen content can be
positioned behind the video window, to be shown when the video is not
present.
(Note: This setting will only be used if OverrideSettings is True)
Loop
Boolean value, true by default.
This is only available for a local video file. If set to False, the video file will only
play once, and then stop.
(Note: This setting will only be used if OverrideSettings is True)
AudioVolume
Integer value between 0 and 10000.
Zero will mute the audio, and 10000 is full volume.
(Note: This setting will only be used if OverrideSettings is True)
AudioBalance
Integer value between -5000 and 5000 for left/right audio balance.
Negative values are for left balance, positive values are for right balance.
(Note: This setting will only be used if OverrideSettings is True)
Drucegrove DragonFly User Manual 1.4 Page 25
Identity XML File
The DragonFly Ethernet network settings, including tags to identify the unit position within a building over the
network, are stored in the Identity.xml file, which can be found under “\Storage Card\Config\”. This file must always
be present for the software to load. The Identity.xml file consists of three main setting groups; IdentitySettings,
NetworkSettings and Groups.
Identity Settings
The following settings can be defined in the Settings.xml file, under IndcatorSettings:
IndicatorType
Optional free text string value, empty by default.
Used to identify the DragonFly device type over the Ethernet network.
ScreenType
Optional free text string value, empty by default.
Used to identify the screen type and/or size over the Ethernet network.
FloorPositionAddress
Integer value, 0 by default.
Sets the floor position address, which is used to display lantern arrows and
activate gong outputs at the correct floor. The floor position address equates
to the floor address given out by the IND055 2-Wire Controller (represented
in hexadecimal on the IND055 LCD display). A value of zero represents
elevator car position.
IndicatorFloorDesignation
Optional free text string value, empty by default.
Used to identify the landing floor level over the Ethernet network.
IndicatorId
Optional free text string value, “0” by default.
Used to identify the unit over the Ethernet network.
IndicatorLiftNumber
Optional free text string value, empty by default.
Used to identify the elevator number over the Ethernet network.
IndicatorLiftGroup
Optional free text string value, empty by default.
Used to identify the elevator group over the Ethernet network.
IndicatorBuildingName
Optional free text string value, empty by default.
Used to identify the building name over the Ethernet network.
This setting is intended for use with future internet connectivity.
IndicatorSiteName
Optional free text string value, empty by default.
Used to identify the site name over the Ethernet network.
This setting is intended for use with future internet connectivity.
Network Settings
The following settings can be defined in the Settings.xml file, under NetworkSettings:
NetworkEnableDHCP
Boolean value, false by default.
Enables the Dynamic Host Configuration Protocol (DHCP) for automatically
assigning the IP Address and settings over the Ethernet network with a DHCP
server. If no DHCP server is present, or the IP Address is configured manually,
this setting should be set to false.
NetworkIPAddress
The IP Address of the unit on the Ethernet network.
This setting is ignored if DHCP is enabled.
NetworkSubnetMask
The Subnet Mask of the unit on the Ethernet network.
This setting is ignored if DHCP is enabled.
NetworkDefaultGateway
The Default Gateway of the unit on the Ethernet network.
This setting is ignored if DHCP is enabled.
NetworkDNSServer
The DNS Server of the unit on the Ethernet network.
This setting is ignored if DHCP is enabled.
Drucegrove DragonFly User Manual 1.4 Page 26
Groups
Groups can be defined for identification of units on an Ethernet network. Network commands can also be sent to all
units belonging to a certain group. Groups are defined under the Groups section of the Identity XML file. Group
names can be any alpha numeric value, and can contain spaces and special characters.
If we consider the following identity file:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Drucegrove DragonFly Identity File -->
<!-- Copyright (C) 2015 Drucegrove Ltd -->
<Identity>
<IdentitySettings>
<IndicatorType>TFT20</IndicatorType>
<IndicatorScreenType>10.4"</IndicatorScreenType>
<FloorPositionAddress>0</FloorPositionAddress>
<IndicatorID>Left</IndicatorID>
<IndicatorLiftNumber>1</IndicatorLiftNumber>
<IndicatorLiftGroup>Group A</IndicatorLiftGroup>
<IndicatorBuildingName>DragonFly HQ</IndicatorBuildingName>
<IndicatorSiteName>123 DragonFly Street</IndicatorSiteName>
</IdentitySettings>
<NetworkSettings>
<NetworkIPAddress>194.0.1.100</NetworkIPAddress>
<NetworkSubnetMask>255.255.0.0</NetworkSubnetMask>
<NetworkDefaultGateway>194.0.1.254</NetworkDefaultGateway>
<NetworkDNSServer>194.0.1.201</NetworkDNSServer>
</NetworkSettings>
<Groups>
<GroupItem>Group A</GroupItem>
<GroupItem>Left Hand Screens</GroupItem>
</Groups>
</ Identity >
Here, two groups have been defined; “Group A” and “Left Hand Screens”.
Drucegrove DragonFly User Manual 1.4 Page 27
DragonFly Designer Software
The DragonFly Designer software can be used to create and edit screen layouts for any DragonFly display. The
Designer saves and loads *.dfx files directly, and has the ability to create micro SD cards for use with a DragonFly.
The Designer can also create USB update drives for updating an existing DragonFly screen, and can broadcast layouts
over a LAN to multiple screens simultaneously.
The DragonFly Designer is a free utility, and does not require a licence or registration. It requires a PC with Microsoft
Windows XP or later installed (Windows 7 or later is recommended), and the Microsoft .NET Framework 4.0.
Drucegrove DragonFly User Manual 1.4 Page 28
DragonFly Layouts (DFX Files)
A DragonFly screen layout consists of three layers:
1. The background layer, which is a full size static image
2. ‘Root Elements’ on top of the background layer
3. Dynamic ‘Sub Elements’ drawn onto the canvas layers
The ‘Root Elements’ include:
Element Canvas
Dynamic Text Ticker
Video
Dynamic ‘Sub Elements’ include:
Elevator Floor Designation
Elevator Direction Arrow (travelling or intended next direction, up or down)
Dynamic Text (embedded or conditional)
Dynamic Image (slideshow or conditional)
Dynamic Pictogram
Dynamic Time/Date Text
Analogue Clock
Scrolling Ticker Text
Dynamic Rectangle
Weather Temperature (from Ethernet based sensor, or internet based RSS feed)
Weather Symbol (from internet based RSS feed)
Transport for London (TfL) Feed
These elements are all designed into the Designer and DragonFly core software. Additional elements may be added
in future software updates. Please contact Drucegrove to request a new element.
Note: Dynamic elements cannot be drawn directly on to the background; they must be drawn onto a canvas.
Drucegrove DragonFly User Manual 1.4 Page 29
Static Background Image Layer
Every layout has a static background layer that covers the whole area of the layout. If nothing is drawn on to this
layer, the background will be a solid colour. The background is drawn by the DragonFly core software as a static flat
image, so anything drawn on the background is “static” and cannot be dynamically changed, shown, hidden or
moved. Nothing can sit behind the background, and all dynamic elements are drawn on top of the background.
The following static Background Drawing Tools are available:
Static Line
A basic line, with a configurable thickness and colour.
Static Rectangle
A basic rectangle or square, with a configurable fill colour, border colour and
border thickness. The corners of the rectangle can be given a rounded
radius.
Static Ellipse
A basic ellipse or circle, with a configurable fill colour, border colour and
border thickness.
Static Path / Polygon
Any solid shape, with configurable points, fill colour, border colour and
border thickness.
Static Text
Static text, with configurable font, weight, style and fill colour. This text
cannot be changed dynamically by the DragonFly (use the Dynamic Text sub
element for text that needs to change).
Static Image
A static image. This element supports most common formats (BMP, JPEG,
GIF and PNG), and the alpha channel of a 32bit PNG is supported. This image
cannot be changed dynamically by the DragonFly (use the Dynamic Image /
Slide Show sub element for an image that needs to change).
If a full screen background image is required, draw a Static Image over the entire layout. It will be placed on the
background layer automatically behind any dynamic screen elements.
Note: Static background shapes filled with a gradient will be dithered automatically for improved appearance.
Drucegrove DragonFly User Manual 1.4 Page 30
‘Element Canvas’ Root Element Layers
All dynamic ‘Sub Elements’ that are drawn by the DragonFly must be placed in an Element Canvas. When an
individual Sub Element needs to be redrawn, the whole canvas has to be redrawn, so it is advisable to split the layout
into multiple canvases where possible, for best performance on fast updating or animated elements.
Element Canvas backgrounds are “transparent” by default (although they can be given individual solid colour
backgrounds). The transparency only works for the background of a canvas, so if two canvases overlap, sub elements
will only be seen on the canvas that is in front.
Canvases are drawn by the PowerVR graphics hardware in the ARM Cortex processor using OpenGLES. This allows
for animated scrolling, fading and alpha blending effects.
‘Dynamic Ticker Text’ Root Element
The DragonFly can render a smooth horizontally scrolling ‘ticker’ text. The text can either be embedded into the DFX
file, or be configured from a remote source.
Dynamic Ticket Text backgrounds are a solid colour by default, or can be configured to be “transparent”. The
transparency only works for the background of the element, so if two ticker or canvas elements overlap, text or sub
elements will only be seen on the canvas that is in front.
The ticker is drawn by the PowerVR graphics hardware in the ARM Cortex processor using OpenGLES. It is
automatically redrawn asynchronously to all other screen elements. This allows for smooth scrolling, but restricts
the conditional capabilities of the element (ie, it cannot be dynamically moved around the screen based on
conditional events).
‘Video’ Root Element
The DragonFly is capable of supporting a single video element. This is rendered using the hardware DSP in the ARM
Cortex processor. It is automatically rendered asynchronously to all other screen elements. This allows for smooth
playback, but restricts the conditional capabilities of the element (ie, it cannot be dynamically moved around the
screen based on conditional events). Dynamic ‘Sub Elements’ cannot be drawn onto a video element. The video
element should be the same size or larger than the video source. The video element is not recommended for rotated
displays, as performance is poor for rotated H264 playback (rotated MPEG2 performance is not affected). The video
element should not be overlapped by any other root element.
For more information on using the Video element, refer to the Video Element section of this manual (page 35)
Loading...