Ihse Draco MultiView 4K 60 User manual

Document MV42-API_REV01.00_en
Edition: 2023-04-05
USER MANUAL
Draco
MultiView API
Application Programming
Interface for
Draco MultiView 4K60

Introduction
This manual contains important safety instructions as well as instructions for setting up the product and
operating it.
Please read the general safety instructions (see chapter 2, page 7) and additional notice in the
respective chapters.
Read carefully through the User Manual before you switch on the product.
Trademarks and Trade Names
All trademark and trade names mentioned in this document are acknowledged to be the property of their respective
owners.
Validity of this Manual
This manual applies to the Draco MultiView 4K60. Please note the change log for this manual in the chapter 12,
page 52).
The manufacturer reserves the right to change specifications, functions or circuitry of the series described here
without notice. Information in this manual can be changed, expanded, or deleted without notice. You can find the
current version of the manual in the download area of our website.
Copyright
© 2023. All rights reserved. This manual may not be reproduced in any manner without the prior written consent of
the manufacturer.
Available Documentation
Name
Format
Description
Provision
User Manual PDF Contains instructions required to operate the product. Download from
website
Contact
IHSE GmbH
Benzstraße 1
88094 Oberteuringen
Germany
phone: [phone]
fax: [phone]
e-mail: [e-mail]
website: https://www.ihse.com

Draco MultiView 4K60 API Table of Contents
3
Table of Contents
Table of Contents .......................................................................................................................................................... 3
1 Important Information ........................................................................................................................................... 5
1.1 Symbols for Warnings and Helpful Information........................................................................................... 5
1.2 Terms and Spellings.................................................................................................................................... 5
1.3 Intended Use ............................................................................................................................................... 6
2 Safety Instructions ................................................................................................................................................ 7
3 Description ............................................................................................................................................................. 8
3.1 System Overview ........................................................................................................................................ 8
3.1.1 Application ................................................................................................................................... 8
3.1.2 Draco MV System with External Controls.................................................................................... 8
3.2 Telegram Structure...................................................................................................................................... 9
3.2.1 GET Request ............................................................................................................................... 9
3.2.2 SET Command .......................................................................................................................... 10
3.2.3 Size of Telegram........................................................................................................................11
3.3 Data Communication.................................................................................................................................11
3.4 API Telegram Command Structure with different Applications ................................................................. 11
4 Installation of External Control ..........................................................................................................................12
5 Configuration for Communication via API........................................................................................................13
5.1 Enabling Network Connection as API ....................................................................................................... 13
5.1.1 Enabling API Telegram Commands .......................................................................................... 13
5.1.2 Enabling of Sending Echoes for Switching Processes ..............................................................14
5.1.3 Keeping IP Socket Connection ..................................................................................................14
6 Operation via API Interface................................................................................................................................. 15
6.1 API Telegram Overview ............................................................................................................................15
6.2 API Telegram Byte Overview ....................................................................................................................16
6.2.1 Focusing on one Input and Selecting other Inputs ....................................................................17
6.2.2 Focusing on two Inputs in Individual Fullscreen Mode ..............................................................18
6.2.3 Selecting an Output in Individual Fullscreen Mode ...................................................................20
6.2.4 Changing the Display Mode.......................................................................................................20
6.3 7-Byte API Telegram SET_CPU ................................................................................................................ 21
6.3.1 Focusing on one Input................................................................................................................ 21
6.3.2 Focusing on two Inputs .............................................................................................................. 22
6.4 9-Byte API Telegram SET_CPU_EX ..........................................................................................................23
6.4.1 Focusing on/Selecting one Input per Board with Asynchronous Switching Mode ....................24
6.4.2 Focusing on/Selecting two Inputs per Board with Asynchronous Switching Mode ...................24
6.5 9-Byte API Telegram SET_DISPLAYMODE ..............................................................................................25
6.5.1 Selecting the Display Mode and Fousing on one Input...............................................................26
6.5.2 Selecting the Display Mode and Focusing on two Inputs........................................................... 26
6.6 9-Byte API Telegram SET_CPUCON .........................................................................................................27
6.6.1 Routing an Input to an Output in Fullscreen Mode ....................................................................28
6.6.2 Routing two Inputs to two Outputs in Fullscreen Mode .............................................................29
6.7 13-Byte API Telegram SET_DISPLAYMODE_EX ......................................................................................30
6.7.1 Selecting the Display Mode and Focusing on one Input per Board ..........................................31

Table of Contents Draco MultiView 4K60 API
4
6.7.2 Selecting the Display Mode and Focusing on two Inputs per Board .........................................31
7 Maintenance ......................................................................................................................................................... 33
7.1 Querying the System Status via API Interface .......................................................................................... 33
7.1.1 Status Request Response - Custom Layouts............................................................................33
7.1.2 Status Request Response - Display Mode ................................................................................34
7.1.3 Status Request Response - Power Status and Hardware......................................................... 34
7.1.4 Status Request Response - Video Signal Presence at Input X.................................................35
7.1.5 Status Request Response - USB Routing/Monitor Connected to Output X ..............................38
7.1.6 Status Request Response - Associated Window from Input X displayed on Output X ...............40
7.2 API Echo for System Changes and Activities triggered without Media Control ........................................41
7.2.1 Echo Example for Real Time Clock ...........................................................................................41
7.2.2 Echo of Focused Inputs with a Single Head Device..................................................................42
7.2.3 Echo of Focused Inputs with a Dual Head Device ....................................................................43
7.2.4 Echo of Routed Inputs to Outputs..............................................................................................44
7.2.5 Echo of Changed Display Mode with Single Head Devices ......................................................46
7.2.6 Echo of Changed Display Mode with Dual Head Devices.........................................................47
8 Technical Support ...............................................................................................................................................48
8.1 Support Checklist ...................................................................................................................................... 48
9 Glossary ............................................................................................................................................................... 49
10 Index .....................................................................................................................................................................50
11 Table of Figures...................................................................................................................................................51
12 Change log ...........................................................................................................................................................52

Draco MultiView 4K60 API Important Information
5
1 Important Information
1.1 Symbols for Warnings and Helpful Information
The meaning of the symbols used for warnings and helpful information in this manual is described below:
NOTICE
NOTICE identifies information, if not observed, endangers the functionality of your device or the security of your
data.
This symbol indicates information about special features on the device or when using device and function
variants.
This symbol indicates instructions for procedures recommended by the manufacturer for an effective utilization of
the device potential.
1.2 Terms and Spellings
Uniform terms are used in this manual for better readability or easier assignment.
The following terms are used for products and descriptions:
Term Description
Draco MV Draco MultiView 4K60
Web UI Draco MV Web User Interface to configure, monitor and operate the device (see
Draco MV user manual)
Source Computer, graphics card (USB, video, audio, data)
Sink Console (monitor, keyboard, mouse; optionally also video, audio, data sources)
Main output Output OUT1/OUT1.1
Main monitor Monitor connected to output OUT1/OUT1.1
Window Window on the monitor to stream the video signal of an associated input (referred to as
“window” below).
Main window Window with to stream the video signal of the focused input displayed on the main
monitor, in the foreground or in the background depending on the selected display mode.
Window arrangement Depending on the selected display mode, the windows are arranged on one monitor, on
two monitors and with some display modes also via levels on one monitor.
The following spellings are used for keyboard commands:
Keyboard command Description
key Key on the keyboard.
key + key Press keys simultaneously.
key, key Press keys successively.
2x key Press key quickly, twice in a row (like a mouse double-click).
Number/number on the
keyboard
Numeric key at the top end of the alphanumeric keyboard usually used for described
operations.
Number on the
numerical pad
Numeric key on the numeric pad. If the use of the numeric pad is required, it is explicitly
described.

Important Information Draco MultiView 4K60 API
6
The following spelling is used for, e.g., descriptions of editing files or updating firmware:
Keyboard command Description
Config.txt
For instance, file name.
#CFG
For instance, file content.
The following spellings are used for software descriptions:
Spelling Description
Bold print Description of terms that are used in the device firmware or the Web UI
Bold print > Bold print Selection of a menu item in the working area of OSD, e.g., Configuration > System
Mouse button Description
Left mouse button Primary mouse button* (default in most operating systems)
Right mouse button Secondary mouse button*
* Unless you have customized your mouse settings in the used operating system.
Descriptions containing "click...", "mouse click" or "double-click" each means a click with the primary (left) mouse
button. If the right mouse button has to be used, this is explicitly declared in the description.
1.3 Intended Use
The Draco MV API (application programming interface) is used to control a Draco MV externally by network (TCP/IP)
connection. The Draco MV API has been successfully implemented with various common media control systems.
The Draco MV API provides the full scope of switching functionality. It does not support the configuration of a
Draco MV.

Draco MultiView 4K60 API Safety Instructions
7
2 Safety Instructions
To ensure reliable and safe long-term operation of your device, please note the following guidelines:
Read this user manual carefully.
Only use API telegram commands according to this user manual. Failure to follow the instructions described can
endanger the security of your data.
Observe instructions of the Draco MV user manual, available via download from the manufacturer’s website.

Description Draco MultiView 4K60 API
8
3 Description
3.1 System Overview
3.1.1 Application
The Draco MV operating system offers various functions for an operation via Draco MV API. The API telegram
commands are mainly intended to stream video signals to specified outputs, to change display modes, and to query
several status information of the Draco MV.
Via API a telegram response is automatically sent to confirm the preservation of the telegram commands.
To receive the API echo via TCP/IP, the sockets have to be kept open continuously (see chapter 5.1.3, page 14).
3.1.2 Draco MV System with External Controls
The Draco MV system can be connected to an external control via TCP/IP, using a Cat X network cable via API
interface.
Fig. 1 System overview (example = dual head installation with external controls)
1 Sources (computer, graphic card)
2
Draco Multiview 4K60
3
External switching solution with GPIO interface
(optional)
4 Console (monitors, keyboard, mouse with optional
audio devices and USB devices)
5 Network connection cable (Cat X)
6 External control, TCP/IP (optional)

Draco MultiView 4K60 API Description
9
3.2 Telegram Structure
Constraints
•Minimum telegram length is 3 bytes
•Maximum buffer size for data transfer is 10240 bytes.
•16 sockets for TCP/IP communication over port 7055 (7065 for SSL) are available. Ensure that there will be at
least one socket left for the communication with the Web UI.
•Wait for a response before sending another request to the Draco MV.
Definition
The Little Endian format is used as byte order (valid for all commands larger than 1 byte).
3.2.1 GET Request
For detailed information about querying a status via Get request, please refer to chapter 7, page 33.
Description Control
Character
Server
identification
Command
Hex coding 0x1B 1 Byte 1 Byte
Request
Type Bytes Description
Control character 1 Start byte always: ESC (
0x1B
)
Server identification 1 Identification of service = request: [ (
0x5B
)
Command 1 A special command (
0x7A
)
Example
Telegram: 0x1B 0x5B 0x7A
Response
Type Bytes Description
Control character 1 Start byte always: ESC (
0x1B
)
Server identification 1 Identification of service = response: ] (
0x5D
)
Command 1 A special command (
0x7A
)
Size 2 Optional, if telegram size > 3 bytes
Data n Optional, n bytes of data
Example
Telegram: 0x1B 0x5D 0x7A 0x0D 0x00 0x0B 0x00 0x03 0x90 0x08 0x0F 0x13 0xFF

Description Draco MultiView 4K60 API
10
3.2.2 SET Command
Description
Control
Character
Server
identification
Command Total length of telegram Data
Hex coding 0x1B 1 Byte 1 Byte 1 Byte 1 Byte n Bytes
Request
Type Bytes Description
Control character 1 Start byte always: ESC (
0x1B
)
Server identification 1 Identification of service = request: [ (
0x5B
)
Command 1 A special command
Size 2 Optional, if telegram size > 3 bytes (see example in chapter 3.2.3, page 11)
Data n Optional, n bytes of data
Example
Example for the API telegram command SET_CPU:
Telegram: 0x1B 0x5B 0x47 0x07 0x00 0x04 0x00
Focus on input 4.
Response
Type Bytes Description
<ACK> 1 Acknowledge (0x06), no error.
The Draco MV will send a confirmation if the SET command has been
received and the Draco MV settings have been successfully changed.
<NAK> 1 Negative Acknowledge (
0x15
), error occurred.
The Draco MV will send an error message if the SET command has been
received but the Draco MV settings have not been successfully changed.
<BEL> 1 Busy (0x07), no time.
The Draco MV will send a busy message if the Draco MV is busy and
receiving of the SET command is not possible.
[ECHO] n Reports the Draco MV sequences solicited by a command and thus the new
switching status of the Draco MV. The echo can be used to update user
applications and to operate several Draco MV in parallel. To activate the
Echo Mode, see chapter 5.1.2, page 14 (for network interface).
Example
<ACK>[ECHO]
[ ] = Optional elements
Use the [ECHO] reports to verify that the switch commands have been executed as requested. Update the
external switch status according to the [ECHO] reports rather than according to your commands.
Optional elements

Draco MultiView 4K60 API Description
11
3.2.3 Size of Telegram
The size of the telegram contains all bytes of the request or the response, see the following example:
Ctrl Char Server Ident Command
Total length of
telegram CpuID1 CpuID2
0x1B 0x5B 0x49 0x0D 0x00 0x01 0x000x04 0x00
Byte count 1 2 3 4 5 6 7 8 9
Hex coding 0x1B 0x5B 0x49 0x09 0x00 0x01 0x00 0x04 0x00
3.3 Data Communication
Fig. 2 Process sequence of a data communication
3.4 API Telegram Command Structure with different Applications
Here are some examples for sending API telegram commands with different applications.
API Switch Telegram Command
ESC SRV CMD Size CPU ID
High-, Low-Byte
CON ID
High-, Low-Byte
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
Byte 9
0x1B
0x5B
0x49
0x09
0x00
0x01
0x00
0x04
0x00
API Switch Telegram Command for use in Packet Sender App (www.Packet Sender.com)
1B 5B 49 09 00 01 00 04 00
API Switch Telegram Command for use with Linux (with netcat, Nmap.org)
Installing nmap in debian linux: "apt-get install nmap"
•Not encrypted API
echo -ne "\x1B\x5B\x49\x09\x00\x01\x00\x04\x00 | ncat 192.168.100.200 7055 -d 0.1
•Encrypted (SSL) API
echo -ne "\x1B\x5B\x49\x09\x00\x01\x00\x04\x00 | ncat -C --ssl 192.168.100.200 7065 -d 0.1
Sending response:
a) Busy <BEL>
b) Errors occurred: <NAK>
b) No errors: <ACK>
c) Optional: <ECHO>
d) Optional: Response telegram with data.
3.
Receiving and processing response
telegram.
4.
Sending of an API telegram command.
Acquiring and processin
g of a command,
blocking of further commands.
2.
1.

Installation of External Control Draco MultiView 4K60 API
12
4 Installation of External Control
First-time users are recommended to set up the system in a test environment that is limited to a single room. This
makes it easier to identify and solve any cabling problems, and experiment with your system more conveniently.
Requirements
The Draco MV system has been connected and basically configured according to the Draco MV user manual:
•The hardware of the Draco MV system has been physically connected (Draco MV, sources, and sinks, etc.).
•The initial configuration has been set (system settings, e.g., network settings).
•A status of the Draco MV configuration has been stored as backup file.
Setting up an External Control
Connect the external control via TCP/IP to the Draco MV.
If using a TCP/IP connection, the IP address of the Draco MV and the IP address of the external controller must
be in the same subnet, or a corresponding gateway must be configured

Draco MultiView 4K60 API Configuration for Communication via API
13
5 Configuration for Communication via API
In the following section, all relevant settings via OSD or Web UI are described. For a detailed explanation about OSD
or Web UI, please refer to the Draco MV user manual.
Enabling Network Connection as API
To enable sending API telegram commands and sending echoes via network interface, some settings are to be
configured first:
•Enabling sending API telegram commands (see chapter 5.1.1, page 13).
•Enabling sending echoes (see chapter 5.1.2, page 14).
•Keeping the IP socket open (see chapter 5.1.3, page 14).
NOTICE
Loss of configuration changes
By clicking or Okay (OSD) or Apply (Web UI), changes are applied to the active configuration and saved in the
volatile memory of the Draco MV. In the event of a sudden power failure, these changes are lost. To save changes
permanently:
save the configuration changes into the active configuration (Remote Save, only Web UI), or perform a restart
(Restart MV (OSD) or Restart (Web UI)). For more information, please refer to the Draco MV user manual.
After changing the configuration of the system, we recommend to de-register the primary controller board and to
boot the secondary controller board until the boot process is finished.
Configurations can be saved as a file that can be stored independent of the Draco MV.
We recommend saving a Draco MV status every time when a configuration has been changed.
5.1 Enabling Network Connection as API
5.1.1 Enabling API Telegram Commands
To operate the Draco MV via API telegram commands, the Draco MV have first to be configured via Web UI settings.
The serial interface can be blocked while OSD has been opened.
To enable the operation via API telegram commands, proceed as follows:
1. Login to the Draco MV via Web UI.
2. Click System Settings in the toolbar to display the tasks of the system settings.
3. Tick the API Service checkbox to enable the network interface at the Draco MV for accessing via API telegram
commands (7055/TCP (7065 for SSL)).
4. Click Apply to confirm your entries.
Fig. 3 Web UI menu System Settings - Network - General (Working area 2)

Configuration for Communication via API Draco MultiView 4K60 API
14
5.1.2 Enabling of Sending Echoes for Switching Processes
To send all performed switching commands in the Draco MV as an echo, the following option has to be enabled:
1. Login to the Draco MV via Web UI.
2. Select Configuration > System in the main menu.
3. Tick the LAN Echo checkbox to enable sending echoes via network interface.
4. Click Apply to confirm your entries.
Fig. 4 Web UI menu System Settings - System (Working area 2)
5.1.3 Keeping IP Socket Connection
Communication
IP Sockets
Non-encrypted Draco MV IP address with TCP Port 7055.
SSL-encrypted Draco MV IP address with TCP Port 7065.
Keeping IP Sockets open for Sending Echo for Switching Processes without API Telegram Commands
The Draco MV includes 16 network sockets. The socket connection is normally terminated after about 60 sec
inactivity. If there is no keep alive signal in between this period, the socket will be closed again. To send echoes for
all affected Draco MV processes that are executed without API telegram commands, e.g., switching via function keys
as an echo, the IP socket connection have to be kept open.
To keep the IP socket connection to the Draco MV open, it is necessary to send a cyclic polling of the API telegram
command Get System Status every 55 sec to guarantee to receive API Echo (see chapter 3.2.1, page 9).

Draco MultiView 4K60 API Operation via API Interface
15
6 Operation via API Interface
6.1 API Telegram Overview
TCP/IP Socket connections to the Draco MV can be used via TCP/IP port 7055 (SSL: 7065).
When sending commands via the API interface, the Draco MV echoes the same command with a leading
acknowledgement byte 0x06 (ACK) in front.
Internal Hot Key switching commands are echoed without a leading acknowledgement byte 0x06.
Example for an API Telegram Request with Response
E.g., to focus on input 4 and maximize the associated window in the window arrangement of output OUT1/1.1, enter
the API telegram of line 1. See line 2 for the API Echo.
01 = Maximizing the associated window of the focused input
4.1 in the
window arrangement of output OUT1.1 (ConID)
04 = Focusing on input 4.1 (CpuID)
06 = Leading acknowledgment
Fig. 5
Example - SET_CPUCON API telegram and response
There are telegrams with a different number of bytes available:
Telegram command Bytes
01 02 03 04 05 06 07 08 09 10 11 12 13
SET_CPU
1B 5B 47 07 00 CpuID 00
SET_CPU_EX
1B 5B 4A 09 00 CpuID1 00 CpuID2 00
SET_CPUCON
1B 5B 50 09 00 CpuID 00 ConID 00
SET_DISPLAYMODE
1B 5B 46 09 00 ModeID ModeID CpuID 00
SET_DISPLAYMODE_EX
1B 5B 49 0D 00 ModeID1 ModeID1 ModeID2 ModeID2 CpuID1 00 CpuID2 00
Size of the API telegram
API Telegrams for Single Head or Dual Head Devices in Synchronous Switching Mode
Telegram command Description
SET_CPU
•Focuses on one input (see chapter 6.3.1, page 21).
•Focuses on two inputs in individual Fullscreen Mode (see chapter 6.3.2, page 22).
SET_DISPLAYMODE
•Changes the display mode (see chapter 6.5.1, page 26).
•Keeps or changes the focused input (see chapter 6.5.2, page 26).
API Telegrams for Dual Head Devices with Synchronous or Asynchronous Switching Mode
Telegram command
Description
SET_CPUCON
Selects outputs to maximize associated windows of selected inputs in the individual
Fullscreen Mode (see chapter 6.6.1, page 28).
SET_DISPLAYMODE_EX
Keeps or changes the display mode, keeps, or changes the focused input, selects up to
three inputs to be displayed in individual Fullscreen Mode (see chapter 6.6.2, page 29).
SET_CPU_EX
•Focuses on two inputs with asynchronous switching mode (see chapter 6.4.1, page 24).
•Focuses two inputs in individual Fullscreen Mode with asynchronous switching mode
(see chapter 6.4.2, page 24).

Operation via API Interface Draco MultiView 4K60 API
16
6.2 API Telegram Byte Overview
Selection
Description
CpuID Focuses on one input of the primary board.
For dual head devices with activated Async Switch function via API telegram
SET_CPUCON, the inputs can be selected separately for the primary and secondary board.
CpuID1 Focuses on one or two inputs of the primary board.
CpuID2 Selects one or two inputs of the secondary board.
ConID Selects the output the focused/selected input should be routed.
With dual head devices and activated Async Switch function, the outputs can be selected
separately for the primary and secondary board.
ModeID Selects the display mode of the primary and secondary board.
ModeID1 Selects the display mode of the primary board with activated Async Switch function.
ModeID2 Selects the display mode of the secondary board activated Async Switch function.
Selection Single head devices Dual head devices with
synchronous switching
Dual head devices with
asynchronous switching
CpuID Focuses on one input of the
primary board.
Focuses on one input of the
primary board and selects
one input of the secondary
board.
Focuses on one input for the
primary or secondary board
when using the API telegram
SET_CPUCON.
CpuID1 n/a
Focuses on one or two inputs
of the primary board and
selects one or two inputs of
the secondary board.
Focuses on one or two inputs
of the primary board.
CpuID2 n/a n/a Selects one or two inputs of
the secondary board.
ConID Selects the output the
focused/selected input should
be routed.
Selects the output the
focused/selected input should
be routed.
Selects the output the
focused/selected input should
be routed.
ModeID Selects the display mode of
the primary board.
Selects the display mode of
the primary and secondary
board.
n/a
ModeID1 n/a Selects the display mode of
the primary and secondary
board.
Selects the display mode of
the primary board.
ModeID2 n/a n/a Selects the display mode of
the secondary board

Draco MultiView 4K60 API Operation via API Interface
17
6.2.1 Focusing on one Input and Selecting other Inputs
Single Head Devices
CpuID
Function with single head devices
00 Keeps the current focused input.
01 Focuses on input 1.
02 Focuses on input 2.
03 Focuses on input 3.
04 Focuses on input 4.
Synchronous Switching with Dual Head Devices
CpuID Function with dual head devices
00 Keeps the current focused input.
01 Focuses input 1.1 of the primary board.
02 Focuses input 2.1 of the primary board.
03 Focuses input 3.1 of the primary board.
04 Focuses input 4.1 of the primary board.
Asynchronous Switching with Dual Head Devices
CpuID
Function with dual head devices
00 Keeps the current focused input.
01 Focuses input 1.1 of the primary board.
02 Focuses input 2.1 of the primary board.
03 Focuses input 3.1 of the primary board.
04 Focuses input 4.1 of the primary board.
05 Selects input 1.2 of the secondary board.
06 Selects input 2.2 of the secondary board.
07 Selects input 3.2 of the secondary board.
08 Selects input 4.2 of the secondary board.
Synchronous/Asynchronous Switching of Dual Head Devices
CpuID1 Function
00 Keeps the current focused input.
01 Focuses on input 1.1 of the primary board.
02 Focuses on input 2.1 of the primary board.
03 Focuses on input 3.1 of the primary board.
04 Focuses on input 4.1 of the primary board.

Operation via API Interface Draco MultiView 4K60 API
18
Asynchronous Switching of the Secondary Board of Dual Head Devices
When using the API telegram command SET_CPU_EX with dual head devices by synchronous switching, byte 08 has no
effect.
CpuID2 Function Available for API telegram
00 Keeps the current selected input. SET_DISPLAYMODE_EX and SET_CPU_EX
01 Selects input 1.1 of the secondary board. SET_DISPLAYMODE_EX
02 Selects input 2.1 of the secondary board. SET_DISPLAYMODE_EX
03 Selects input 3.1 of the secondary board. SET_DISPLAYMODE_EX
04 Selects input 4.1 of the secondary board. SET_DISPLAYMODE_EX
05 Selects input 1.2 of the secondary board. SET_CPU_EX
06 Selects input 2.2 of the secondary board. SET_CPU_EX
07 Selects input 3.2 of the secondary board. SET_CPU_EX
08 Selects input 4.2 of the secondary board. SET_CPU_EX
6.2.2 Focusing on two Inputs in Individual Fullscreen Mode
Byte for CpuID1 and CpuID2
Hexadecimal Decimal Focused input 1,
output via OUT1/OUT1.1
Selected input 2,
output via OUT2/OUT2.1
0B 11 1 1
0C 12 1 2
0D 13 1 3
0E 14 1 4
15 21 2 1
16 22 2 2
17 23 2 3
18 24 2 4
1F 31 3 1
20 32 3 2
21 33 3 3
22 34 3 4
29 41 4 1
2A 42 4 2
2B 43 4 3
2C 44 4 4

Draco MultiView 4K60 API Operation via API Interface
19
Examples
To focus on two other inputs in Fullscreen Mode, send the API telegram command
1B 5B 47 07 00 17 00.
The associated window of input 2 is maximized in the window arrangement on the main monitor connected to the
main output OUT1/OUT1.1. The USB HID control is switched to input 2 and the mouse can be used in the
associated window. The associated window of input 3 is maximized in the window arrangement on monitor 2
connected to output OUT2/OUT2.2.
Fig. 6 Individual Fullscreen Mode - Example for focusing and displaying two different inputs
API 7-byte telegram
Main output OUT1.x
Second output OUT2.x
01
02
03
04
05
06
07
1B 5B 47 07 00 0E 00 Focuses on input 1. Maximizes the associated window of input 4.
1B 5B 47 07 00 2A 00 Focuses on input 4. Maximizes the associated window of input 2.

Operation via API Interface Draco MultiView 4K60 API
20
6.2.3 Selecting an Output in Individual Fullscreen Mode
Single Head Devices
ConID
Function with single head devices
01 Selects the main output OUT1.1 to maximize the associated window of the focused input.
02 Selects output OUT2.1 to maximize the associated window of a selected input.
Synchronous Switching with Dual Head Devices
ConID Function with dual head devices
01 Selects the main output OUT1.1 and OUT1.2 to maximize the associated windows of the
focused input of the dual head device.
02 Selects output OUT2.1 and OUT2.2 to maximize the associated windows of the focused
input of the dual head device.
Asynchronous Switching with Dual Head Devices
ConID Function with dual head devices
01 Selects the main output OUT1.1 to maximize the associated window of the focused input.
02 Selects output OUT2.1 to maximize the associated window of a selected input.
03 Selects output OUT2.2 to maximize the associated window of a selected input.
04 Selects output OUT2.2 to maximize the associated window of a selected input.
6.2.4 Changing the Display Mode
Depending on the used API telegram, the display mode of the primary board and/or the secondary board is changed.
Bytes for ModeID,
ModeID1, ModeID2
Function
00 00 Changes the display mode to Fullscreen Mode.
01 00 n/a
02 00 Changes the display mode to PiP Mode.
03 00 Changes the display mode to Quad Mode.
04 00 n/a
05 00 n/a
06 00 Changes the display mode to Preview Mode.
07 00 Changes the display mode to True PiP Mode.
08 00 Changes the display mode to PbP Mode.
09 01 Changes the display mode to Custom Mode with layout 1.
09 02 Changes the display mode to Custom Mode with layout 2.
09 03 Changes the display mode to Custom Mode with layout 3.
09 04 Changes the display mode to Custom Mode with layout 4.
FF FF Keeps the current display mode.