Ihse Draco MultiView 4K60 User Manual

Ihse Draco MultiView 4K60 User Manual

Hide thumbs Also See for Draco MultiView 4K60:
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Draco MultiView 4K60 and is the answer not in the manual?

Questions and answers

Summary of Contents for Ihse Draco MultiView 4K60

  • Page 1 USER MANUAL Draco MultiView API Application Programming Interface for Draco MultiView 4K Document MV42-API_REV01.00_en Edition: 2023-04-05...
  • Page 2 © 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 Contains instructions required to operate the product. Download from website Contact IHSE GmbH Benzstraße 1 88094 Oberteuringen Germany phone: +49 7546-9248-0 fax: +49 7546-9248-48 e-mail: info@ihse.com website: https://www.ihse.com...
  • Page 3: Table Of Contents

    Draco MultiView 4K Table of Contents Table of Contents Table of Contents ................................3 Important Information ............................5 Symbols for Warnings and Helpful Information ................... 5 Terms and Spellings............................ 5 Intended Use ............................... 6 Safety Instructions ..............................7 Description ................................8 System Overview ............................
  • Page 4 Table of Contents Draco MultiView 4K60 API 6.7.2 Selecting the Display Mode and Focusing on two Inputs per Board ......... 31 Maintenance ................................. 33 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 ................
  • Page 5: Important Information

    Draco MultiView 4K60 API Important Information Important Information 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.
  • Page 6: Intended Use

    Important Information Draco MultiView 4K60 API 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...
  • Page 7: Safety Instructions

    Draco MultiView 4K60 API Safety Instructions 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.
  • Page 8: Description

    Description Draco MultiView 4K60 API Description 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.
  • Page 9: Telegram Structure

    Draco MultiView 4K60 API Description 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 •...
  • Page 10: Set Command

    Description Draco MultiView 4K60 API 3.2.2 SET Command Optional elements Control Server Description Command Total length of telegram Data Character identification Hex coding 0x1B 1 Byte 1 Byte 1 Byte 1 Byte n Bytes Request Type Bytes Description Control character Start byte always: ESC ( 0x1B Server identification...
  • Page 11: Size Of Telegram

    Draco MultiView 4K60 API Description 3.2.3 Size of Telegram The size of the telegram contains all bytes of the request or the response, see the following example: Total length of Ctrl Char Server Ident Command CpuID1 CpuID2 telegram 0x1B 0x5B 0x49 0x0D 0x00 0x01...
  • Page 12: Installation Of External Control

    Installation of External Control Draco MultiView 4K60 API 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: •...
  • Page 13: Configuration For Communication Via Api

    Draco MultiView 4K60 API Configuration for Communication via API 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:...
  • Page 14: Enabling Of Sending Echoes For Switching Processes

    Configuration for Communication via API Draco MultiView 4K60 API 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.
  • Page 15: Operation Via Api Interface

    Draco MultiView 4K60 API Operation via API Interface Operation via API Interface 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.
  • Page 16: Api Telegram Byte Overview

    Operation via API Interface Draco MultiView 4K60 API 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.
  • Page 17: Focusing On One Input And Selecting Other Inputs

    Draco MultiView 4K60 API Operation via API Interface 6.2.1 Focusing on one Input and Selecting other Inputs Single Head Devices CpuID Function with single head devices Keeps the current focused input. Focuses on input 1. Focuses on input 2. Focuses on input 3. Focuses on input 4.
  • Page 18: Focusing On Two Inputs In Individual Fullscreen Mode

    Operation via API Interface Draco MultiView 4K60 API 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 Keeps the current selected input.
  • Page 19 Draco MultiView 4K60 API Operation via API Interface Examples  To focus on two other inputs in Fullscreen Mode, send the API telegram command 1B 5B 47 07 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.
  • Page 20: Selecting An Output In Individual Fullscreen Mode

    Operation via API Interface Draco MultiView 4K60 API 6.2.3 Selecting an Output in Individual Fullscreen Mode Single Head Devices ConID Function with single head devices Selects the main output OUT1.1 to maximize the associated window of the focused input. 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...
  • Page 21: 7-Byte Api Telegram Set_Cpu

    Draco MultiView 4K60 API Operation via API Interface 7-Byte API Telegram SET_CPU 6.3.1 Focusing on one Input For information about the CpuID, please see chapter 6.2, page 16, chapter 6.2.1, page 17 and chapter 6.2.2, page 18. To focus on one or two inputs, the API telegram command SET_CPU has to be sent: Size CpuID CpuID...
  • Page 22: Focusing On Two Inputs

    Operation via API Interface Draco MultiView 4K60 API 6.3.2 Focusing on two Inputs Example API 9-byte telegram Function 01 02 03 04 05 06 07 1B 5B 47 07 00 00 • Changes the display mode to the individual Fullscreen Mode. •...
  • Page 23: 9-Byte Api Telegram Set_Cpu_Ex

    Draco MultiView 4K60 API Operation via API Interface 9-Byte API Telegram SET_CPU_EX For information about the CpuID1 and CpuID2, please see chapter 6.2, page 16, chapter 6.2.1, page 17 and chapter 6.2.2, page 18. To focus on one or two inputs of the primary board and to select one or two inputs from the secondary board with dual head devices by asynchronous switching, the API telegram command SET_CPU_EX has to be sent: Size CpuID1...
  • Page 24: Focusing On/Selecting One Input Per Board With Asynchronous Switching Mode

    Operation via API Interface Draco MultiView 4K60 API 6.4.1 Focusing on/Selecting one Input per Board with Asynchronous Switching Mode Example API 9-byte telegram Function 01 02 03 04 05 06 07 08 09 1B 5B 4A 09 00 00 Primary board •...
  • Page 25: 9-Byte Api Telegram Set_Displaymode

    Draco MultiView 4K60 API Operation via API Interface 9-Byte API Telegram SET_DISPLAYMODE For information about the ModeID, please see chapter 6.2, page 16 and chapter 6.2.4, page 20. For information about the CpuID, please see chapter 6.2, page 16, chapter 6.2.1, page 17 and chapter 6.2.2, page 18.
  • Page 26: Selecting The Display Mode And Fousing On One Input

    Operation via API Interface Draco MultiView 4K60 API 6.5.1 Selecting the Display Mode and Fousing on one Input Examples API 9-byte telegram 01 02 03 04 05 06 07 08 09 Function 1B 5B 46 09 00 FF FF 00 Keeps the display mode and focuses on input 2. 1B 5B 46 09 00 03 00...
  • Page 27: 9-Byte Api Telegram Set_Cpucon

    Draco MultiView 4K60 API Operation via API Interface 9-Byte API Telegram SET_CPUCON For information about the CpuID, please see chapter 6.2, page 16, chapter 6.2.1, page 17 and chapter 6.2.2, page 18. For information about the ConID, please see chapter 6.2, page 16 and chapter 6.2.3, page 20. To select specific outputs when focusing on two inputs in the individual Fullscreen Mode, the API telegram command SET_CPUCON has to be sent: Size...
  • Page 28: Routing An Input To An Output In Fullscreen Mode

    Operation via API Interface Draco MultiView 4K60 API 6.6.1 Routing an Input to an Output in Fullscreen Mode Examples: Switching Single Head Devices To select two inputs in Fullscreen Mode with single head devices, use one of the following API telegrams: Bytes 01 02 03 04 05 06 07 08 09 Function 1B 5B 50...
  • Page 29: Routing Two Inputs To Two Outputs In Fullscreen Mode

    Draco MultiView 4K60 API Operation via API Interface 6.6.2 Routing two Inputs to two Outputs in Fullscreen Mode Example To display video signals of two different inputs in Fullscreen Mode, e.g., send two API telegram commands. 1. Step 1: send 1B 5B 50 09 00 The associated window of input 1 is maximized in the window arrangement on the main monitor connected to output OUT.
  • Page 30: 13-Byte Api Telegram Set_Displaymode_Ex

    Operation via API Interface Draco MultiView 4K60 API 13-Byte API Telegram SET_DISPLAYMODE_EX For information about the ModeID1 and ModeID2, please see chapter 6.2, page 16 and chapter 6.2.4, page 20. For information about the CpuID1 and CpuID2, please see chapter 6.2, page 16, chapter 6.2.1, page 17 and chapter 6.2.2, page 18.
  • Page 31: Selecting The Display Mode And Focusing On One Input Per Board

    Draco MultiView 4K60 API Operation via API Interface 6.7.1 Selecting the Display Mode and Focusing on one Input per Board Examples API 9-byte telegram Function 01 02 03 04 05 06 07 08 09 10 11 12 13 1B 5B 49 0D 00 08 00 FF FF 00 Primary board...
  • Page 32 Operation via API Interface Draco MultiView 4K60 API Primary board: The display mode is changed to Preview Mode and the USB HID control remains on input 1. Secondary board: The display mode is changed to PiP Mode and the video signal of the selected input 3 is streamed in the main window.
  • Page 33: Maintenance

    Draco MultiView 4K60 API Maintenance Maintenance Querying the System Status via API Interface The status request telegram may be used to keep the socket connection open. The socket connection is normally terminated after about 60 sec inactivity. Therefore, a cyclic polling of the status every 55 sec will guarantee to receive API Echo.
  • Page 34: Status Request Response - Display Mode

    Maintenance Draco MultiView 4K60 API 7.1.2 Status Request Response - Display Mode Display Mode Fullscreen Mode PiP Mode Quad Mode Preview Mode True PiP Mode PbP Mode Free Mode Hexadecimal Binary/Dual Bit 39 Bit 38 Bit 37 Bit 36 Bit 35 Bit 34 Bit 33 Bit 32...
  • Page 35: Status Request Response - Video Signal Presence At Input X

    Draco MultiView 4K60 API Maintenance Hexadecimal Binary/Dual Bit 39 Bit 38 Bit 37 Bit 36 Bit 35 Bit 34 Bit 33 Bit 32 Power 2 Power 1 Board Board DH (Y/N) type 2 type 1 00011001 00001111 00010111 00011111 7.1.4 Status Request Response - Video Signal Presence at Input X Primary video/audio board Secondary video/audio board...
  • Page 36 Maintenance Draco MultiView 4K60 API Primary video/audio board Secondary video/audio board Input 1.1 Input 1.2 Input 2.1 Input 2.2 Input 1.1 and 2.1 Input 1.2 and 2.2 Input 3.1 Input 3.2 Input 1.1 and 3.1 Input 1.2 and 3.2 Input 2.1 and 3.1 Input 2.2 and 3.2 Input 1.1, 2.1, and 3.1 Input 1.2, 2.2, and 3.2...
  • Page 37 Draco MultiView 4K60 API Maintenance Hexadecimal Binary/Dual Bit 47 Bit 46 Bit 45 Bit 44 Bit 43 Bit 42 Bit 41 Bit 40 IN4.2 IN3.2 IN2.2 IN1.2 IN4.1 IN3.1 IN2.1 IN1.1 10100000 10110000 11000000 11010000 11100000 11110000 00010001 00100010 00110011 01000100 01010101 01100110...
  • Page 38: Status Request Response - Usb Routing/Monitor Connected To Output X

    Maintenance Draco MultiView 4K60 API 7.1.5 Status Request Response - USB Routing/Monitor Connected to Output X USB HID control/USB 2.0 routed to Monitor connected to output X USB input X USB Input CPU1 No monitor connected USB Input CPU1 Monitor connected to OUT1.1 USB Input CPU1 Monitor connected to OUT2.1 USB Input CPU1...
  • Page 39 Draco MultiView 4K60 API Maintenance Hexadecimal Binary/Dual Bit 55 Bit 54 Bit 53 Bit 52 Bit 51 Bit 50 Bit 49 Bit 48 USB 4 USB 3 USB 2 USB 1 Monitor Monitor Monitor Monitor 00010000 00010001 00010010 00010011 00010100 00011000 00011111 00100000...
  • Page 40: Status Request Response - Associated Window From Input X Displayed On Output X

    Maintenance Draco MultiView 4K60 API 7.1.6 Status Request Response - Associated Window from Input X displayed on Output X Associated window of input X displayed on output X Display Mode Output OUT1.x Output OUT2.x Input 1 Input 1 Fullscreen (mirrored) Input 2 Input 1 Fullscreen (individual)
  • Page 41: Api Echo For System Changes And Activities Triggered Without Media Control

    Draco MultiView 4K60 API Maintenance API Echo for System Changes and Activities triggered without Media Control The API is not only feeding back acknowledge telegram commands sent from the media control, but the API also echoes internal system changes and activities (switching or disconnecting) triggered without media control such as: •...
  • Page 42: Echo Of Focused Inputs With A Single Head Device

    Maintenance Draco MultiView 4K60 API 7.2.2 Echo of Focused Inputs with a Single Head Device ESC [ G Size CpuID Echo: Echoes the focused input. Type Bytes Description Hex Coding 0x1B Control character 0x5B Server identification 0x47 Command 0x07 0x00 Size Total length of telegram (7 bytes) 0x03...
  • Page 43: Echo Of Focused Inputs With A Dual Head Device

    Draco MultiView 4K60 API Maintenance 7.2.3 Echo of Focused Inputs with a Dual Head Device ESC [ J Size CpuID1 CpuID2 Echo: Echoes the focused/selected input(s) of a dual head device. Type Bytes Description Hex Coding 0x1B Control character 0x5B Server identification 0x4A Command...
  • Page 44: Echo Of Routed Inputs To Outputs

    Maintenance Draco MultiView 4K60 API 7.2.4 Echo of Routed Inputs to Outputs ESC [ P Size CpuID ConID Echo: Echoes the input of the primary board or the secondary board that is routed to a selected output. Type Bytes Description Hex Coding 0x1B Control character...
  • Page 45 Draco MultiView 4K60 API Maintenance Echo Example for Connecting a CON Device to a CPU Device by Console Switching ESC [ c Size LogUserID LogConID CpuID ConID Mode Echo: Connection CON Devices (input) to CPU Devices (output) and CPU Devices (input) connection to CON Devices (output).
  • Page 46: Echo Of Changed Display Mode With Single Head Devices

    Maintenance Draco MultiView 4K60 API 7.2.5 Echo of Changed Display Mode with Single Head Devices Echo: ESC [ F Size ModeID CpuID Echoes the display mode and the focused input of single head devices and dual head devices in synchronous switching mode.
  • Page 47: Echo Of Changed Display Mode With Dual Head Devices

    Draco MultiView 4K60 API Maintenance 7.2.6 Echo of Changed Display Mode with Dual Head Devices Echo: ESC [ I Size ModeID1 ModeID2 CpuID1 CpuID2 Echoes display mode changes and switched input(s). Type Bytes Description Hex Coding 0x1B Control character 0x5B Server identification 0x49 Command...
  • Page 48: Technical Support

    Technical Support Draco MultiView 4K60 API Technical Support Prior to contacting support, please ensure you have read this manual, and then installed and set-up your device as recommended. Support Checklist To efficiently handle your request, it is necessary that you complete a support request checklist (Download). Please ensure that you have the following information available before you call: •...
  • Page 49: Glossary

    Draco MultiView 4K60 API Glossary Glossary The following terms are commonly used in this manual. Term Description Since packet transfer is not reliable, a technique known as positive acknowledgment with retransmission is used to guarantee reliability of packet transfers. An application programming interface (API) is a specification intended to be used as an interface by software components to communicate with each other.
  • Page 50: Index

    Index Draco MultiView 4K60 Index Echo via API ............. 41 Changed Display Mode Dual Head ............47 Single Head ............46 Focused Inputs Dual Head ............43 Single Head ............42 Real Time Clock ........... 41 Routed Input ............44...
  • Page 51: Table Of Figures

    Draco MultiView 4K60 API Table of Figures Table of Figures Fig. 1 System overview (example = dual head installation with external controls) ..........8 Fig. 2 Process sequence of a data communication ....................11 Web UI menu System Settings - Network - General (Working area 2) ........... 13 Fig.
  • Page 52: Change Log

    Change log Draco MultiView 4K60 API Change log This table offers an overview of the most important changes available through firmware updates, such as new functions, changed configuration or operation. Edition Date Chapter New functions/changes REV01.00 2023-04-05 - Initial user manual, existing manual completely reworked...

Table of Contents