Black Box DKM FX Interface Manual
  1. Manuals
  2. Brands
  3. Black Box Manuals
  4. Switch
  5. DKM FX
  6. Interface manual
Black Box DKM FX Interface Manual

Black Box DKM FX Interface Manual

Application programming interface (api) manual
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
DKM FX and DKM FX Compact
Application Programming Interface (API) Manual
Order toll-free in the U.S.: Call 877-877-BBOX (outside U.S. call 724-746-5500)
Customer
FREE technical support 24 hours a day, 7 days a week: Call 724-746-5500 or fax
Support
724-746-0746 • Mailing address: Black Box Corporation, 1000 Park Drive, Lawrence,
Information
PA 15055-1018 • Web site: www.blackbox.com • E-mail: info@blackbox.com
ACX048
ACXC8
ACX080
ACXC16
ACX160
ACXC32
ACX288
ACXC48
BLACK BOX
ACXC64
ACXC80
ACXC48F16
ACXC48F32
®

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DKM FX and is the answer not in the manual?

Questions and answers

Related Manuals for Black Box DKM FX

Summary of Contents for Black Box DKM FX

  • Page 1 Order toll-free in the U.S.: Call 877-877-BBOX (outside U.S. call 724-746-5500) Customer FREE technical support 24 hours a day, 7 days a week: Call 724-746-5500 or fax Support 724-746-0746 • Mailing address: Black Box Corporation, 1000 Park Drive, Lawrence, Information PA 15055-1018 • Web site: www.blackbox.com • E-mail: info@blackbox.com...
  • Page 2 Trademarks Used in this Manual Trademarks Used in this Manual Black Box and the Double Diamond logo are registered trademarks of BB Technologies, Inc. TOSLINK is a registered trademark of Kabushiki Kaisha Toshiba dba Toshiba Corporation. Any other trademarks mentioned in this manual are acknowledged to be the property of the trademark owners.
  • Page 3 FCC and IC RFI Statements and NOM Statement FEDERAL COMMUNICATIONS COMMISSION AND INDUSTRY CANADA RADIO FREQUENCY INTERFERENCE STATEMENTS This equipment generates, uses, and can radiate radio-frequency energy, and if not installed and used properly, that is, in strict accordance with the manufacturer’s instructions, may cause inter ference to radio communication.
  • Page 4 NOM Statement 4. Todas las instrucciones de operación y uso deben ser seguidas. 5. El aparato eléctrico no deberá ser usado cerca del agua—por ejemplo, cerca de la tina de baño, lavabo, sótano mojado o cerca de una alberca, etc. 6.
  • Page 5 NOM Statement 16. El cable de corriente deberá ser desconectado del cuando el equipo no sea usado por un largo periodo de tiempo. 17. Cuidado debe ser tomado de tal manera que objectos liquidos no sean derramados sobre la cubierta u orificios de ventilación. 18.

  • Page 6: Table Of Contents

    4. Installation ....................20 4.1 What’s Included ................20 4.2 System Setup ...................20 5. Configuration ..................21 5.1 General Remarks ................21 5.2 DKM FX or DKM FX Compact Configuration ........21 5.2.1 System Data ................21 5.2.2 Network.................23 5.3 Communication Setup ..............26 5.4 Telegram Structure ................27 5.4.1 Request ..................27...
  • Page 7 Table of Contents 6. Operation ....................28 6.1 System Requests ................28 6.2 Switch Commands ................29 6.2.1 Switch Off All Ports .............29 6.2.2 Get CPU Device Connected to CON Device......29 6.2.3 Set CPU Device Connection to CON Device ......30 6.2.4 Get CPU Devices Connected to CON Devices ......30 6.2.5 Set Connections of CPU Devices to CON Devices ....31 6.2.6...
  • Page 8 Table of Contents 7.2.4 Get CPU Devices Connected to CON Devices ......52 7.2.5 Set Connections of CPU Devices to CON Devices ....54 7.2.6 Get CON Device Connected to CPU Device......55 7.2.7 Set CON Device Connection to CPU Device ......56 7.2.8 Get CON Devices Connected to CPU Devices ......57 7.2.9 Set Connection of CON Devices to CPU Devices ....58...

  • Page 9: About This Manual

    Chapter 1: About this Manual 1. About This Manual 1.1 Scope This manual describes how to install your DKM FX API, how to operate it, and how to perform troubleshooting. 1.2 Validity This manual is valid for all devices listed on the front page. The product code is printed on the base of the devices.

  • Page 10: Safety Instructions

    For reliable and safe long-term operation of your DKM FX, follow these guidelines: Installation • Only use in dry, indoor environments. • The DKM FX and the power supply units can get warm. Don’t put them in an enclosed space without any airflow. • Do not obscure ventilation holes.

  • Page 11: Overview

    Chapter 3: Overview 3. Overview 3.1 Description The DKM FX API is used to control the matrix externally by serial commands via serial (RS-232) or network (TCP/IP) connection. The DKM FX API provides the full scope of switching functionality. It does not support the configuration of a DKM FX system.

  • Page 12: Product Range

    Network connection cable (CATx) External serial control (TCP/IP, Option 2) 3.4 Product Range Table 3-3. Available products. Number Description DKM FX and DKM FXC-API ACX-API DKM FX matrix application programming interface (API) Page 12 724-746-5500 | blackbox.com ACX048 API manual...

  • Page 13: Device Views

    Chapter 3: Overview 3.5 Device Views In Sections 3.5.1 through 3.5.7, Figures 3-2 through 3-8 illustrate the DKM FX and DKM FX Compact chassis serial and TCP/IP connectors. Tables 3-4 through 3-10 describe these components. 3.5.1 DKM FX 288-Port Figure 3-2. Front view, ACX288.

  • Page 14: Dkm Fx 160-Port

    Chapter 3: Overview 3.5.2 DKM FX 160-Port Figure 3-3. Front view, ACX160. Table 3-5. ACX160 components. Number Component Serial connector (DB9) TCP/IP connector (RJ-45) Page 14 724-746-5500 | blackbox.com ACX048 API manual...

  • Page 15: Dkm Fx 80-Port

    Chapter 3: Overview 3.5.3 DKM FX 80-Port Figure 3-4. Front view, ACX080. Table 3-6. ACX080 components. Number Component Serial connector (DB9) TCP/IP connector (RJ-45) 3.5.4 DKM FX 48-Port Figure 3-5. Front view, ACX048. Table 3-7. ACX048 components. Number Component Serial connector (DB9)

  • Page 16: Dkm Fx Compact 48-Port

    Chapter 3: Overview 3.5.5 DKM FX Compact 48-Port Figure 3-6. Front view, ACXC48. Table 3-8. ACXC48 components. Number Component Serial connector (RJ-45) TCP/IP connector (RJ-45) 3.5.6 DKM FX Compact 32-Port Figure 3-7. Front view, ACXC32. Table 3-9. ACXC32 components. Number...

  • Page 17: Dkm Fx Compact 16-Port

    Chapter 3: Overview 3.5.7 DKM FX Compact 16-Port Figure 3-8. Front view, ACXC16. Table 3-10. ACXC16 components. Number Component Serial connector (RJ-45) TCP/IP connector (RJ-45) Page 17 724-746-5500 | blackbox.com ACX048 API manual...

  • Page 18: Status Leds

    Chapter 3: Overview 3.6 Status LEDs The DKM FX and DKM FX Compact Status LED indicators are shown in Figure 3-9 and described in Table 3-11. Figure 3-9. CPU board, front view. Page 18 724-746-5500 | blackbox.com ACX048 API manual...
  • Page 19 Chapter 3: Overview Table 3-11. Status LEDs on the CPU board. Number Status Description White CPU board is in registration process Blue flashing Registration at the matrix is started Status 1 Red flashing Registration is in progess Green flashing Operating condition Green CPU board de-registered Operating condition...

  • Page 20: Installation

    Setup of the external control 1. Install the CPU and I/O boards. 2. Connect the keyboard, mouse, and monitor to the CPU board of the DKM FX. 3. Connect the matrix to the power supply. 4. Open OSD via hotkey and log in with administrator rights in the main menu.

  • Page 21: Configuration

    Chapter 5: Configuration 5. Configuration 5.1 General Remarks The DKM FX API provides all commands that are necessary to switch the DKM FX matrix. 5.2 DKM FX Configuration To operate the DKM FX or DKM FX Compact matrix, it has to be configured appropriately.
  • Page 22 Chapter 5: Configuration Select Configuration > System in the main menu. NOTE: The serial interface can be blocked while the OSD is open. Figure 5-2. Menu Configuration—System. You can select between the following buttons: Table 5-2. Button functions. Number Component Cancel Reject changes Save...

  • Page 23: Network

    Select System > System Data in the main menu. Figure 5-3. Menu System—System Data. 5.2.2 Network The DKM FX API relevant network configuration is set in this menu. You can access the menu via OSD or Java: Figure 5-4. OSD and Java icons.
  • Page 24 Input of the subnet mask in the form “255.255.255.0”, if DHCP is not active. mask Gateway Byte Input of the IP address in the form “192.168.1.1”, if DHCP is not active. LAN interface at the DKM FX activated for access via Java tool (TCP/IP port activated Tech 5555). Support deactivated Function not active.
  • Page 25 Chapter 5: Configuration Figure 5-5. Menu Configuration—Network. You can select between the following buttons: Table 5-4. Button functions. Number Component Cancel Reject changes Save Save changes Java Tool Select System > Network in the task area. Figure 5-6. Menu System – Network Page 25 724-746-5500 | blackbox.com ACX048 API manual...

  • Page 26: Communication Setup

    5.3 Communication Setup TCP/IP socket connection To control the DKM FX via TCP/IP socket connection, the Service has to be activat- ed. See Chapter 2.6.4, Network Status and Chapter 4.4.5, Network in the DKM FX and DKM FX Compact manual for more information.

  • Page 27: Telegram Structure

    Chapter 5: Configuration Serial connection To establish the serial communication to the DKM FX, set the format for serial data transmission to the following parameters:. 115.2K, 8, 1, NO (115.2 KBAUD, 8 data bits, 1 stop bit, no parity) 5.4 Telegram Structure 5.4.1 Request...

  • Page 28: Operation

    Chapter 6: Operation 6. Operation The DKM FX API can be addressed in two different ways: 1. Telegrams via serial connection. 2. Telegrams via TCP/IP socket connection. Both connections accept the same telegrams. Available telegrams support system requests, switch commands, and assignments.

  • Page 29: Switch Commands

    Chapter 6: Operation 6.2 Switch Commands 6.2.1 Switch Off All Ports Request Telegram: ESC [ A Description: Switch off all ports. Example: Switch off all ports 0x1B 0x5B 0x41 Response <ACK> [<ECHO>] or <NAK> [ ] = Optional elements 6.2.2 Get CPU Device Connected to CON Device Request Telegram ESC [ H Size ConId...

  • Page 30: Set Cpu Device Connection To Con Device

    Chapter 6: Operation Example: Return CPU device (CpuId = 1012) connected to CON device (ConId = 3017). 0x1B 0x5D 0x48 0x09 0x00 0xC9 0x0B 0xF3 0x03 or <NAK> 6.2.3 Set CPU Device Connection to CON Device Request Telegram ESC [ I Size ConId CpuId Description Set CPU device connection (input) to CON device (output).

  • Page 31: Set Connections Of Cpu Devices To Con Devices

    Chapter 6: Operation Example Return CPU devices connected to CON devices. (ConId = 3017, 3028, 3040) 0x1B 0x5B 0x4A 0x0D 0x00 0x03 0x00 0xC9 0x0B 0xD4 0x0B 0xE0 0x0B Response Telegram ESC ] J Size ConCnt <ConId, CpuId>[1] … <ConId, CpuId>[ConCnt] Description Get CPU devices (input) connected to CON devices (output).

  • Page 32: Get Con Device Connected To Cpu Device

    Chapter 6: Operation ConCnt Number of CON devices <ConId, CpuId>[ ] List of IDs (ConID, CpuID) Example: Set connections of CPU devices to CON devices. ConId[1] = 3017, CpuId[1] = 1012; ConId[2] = 3028, CpuId[2] = 3013; ConId[3] = 3040, CpuId[3] = 1020; 0x1B 0x5B 0x4B 0x13 0x00 0x03 0x00 0xC9 0x0B 0xF4 0x03 0xD4 0x0B 0xF5 0x03 0x0E 0x0B 0xFC 0x03 Response...

  • Page 33: Set Con Device Connection To Cpu Device

    Chapter 6: Operation Example Return CON device (ConId = 3017) connected to CPU device (CpuId = 1012). 0x1B 0x5D 0x4C 0x09 0x00 0xF4 0x03 0xC9 0x0B or <NAK> 6.2.7 Set CON Device Connection to CPU Device Request Telegram ESC [ M Size CpuId ConId Description Set CON device (input) connection to CPU device (output).

  • Page 34: Set Connection Of Con Devices To Cpu Devices

    Chapter 6: Operation Example Get CON devices connected to CPU devices (CpuId = 1012, 1013, 1020. 0x1B 0x5B 0x4E 0x0D 0x00 0x03 0x00 0xF4 0x03 0xF5 0x03 0xFC 0x03 Response Telegram ESC ] N Size CpuCnt <CpuId, ConId>[1] … <CpuId, ConId>[CpuCnt] Description Return CON devices (input) connected to CPU devices (output).

  • Page 35: Set Con Device Connection To Cpu Device (Single Bidirectional Connection-Kvm Full Access)

    Chapter 6: Operation Example Set connection of CON devices to CPU devices. CpuId[1] = 1012, ConId[1] = 3017; CpuId[2] = 1013, ConId[2] = 3028; CpuId[3] = 1020, ConId[3] = 3040; 0x1B 0x5B 0x4F 0x13 0x00 0x03 0x00 0xF4 0x03 0xC9 0x0B 0xF5 0x03 0xD4 0x0B 0xFC 0x03 0x0E 0x0B Response <ACK>...

  • Page 36: Set Connection Of Con Devices To Cpu Devices (Multiple Bidirectional Connections-Full Access)

    Chapter 6: Operation 6.2.11 Set Connection of CON Devices to CPU Devices (Multiple Bidirectional Connections—Full Access) Request Telegram ESC [ Q Size Cnt <CpuId, ConId>[1] … <CpuId, ConId>[Cnt] Description Set connection of CON devices (input) to CPU devices (output) and CPU devices (input) to CON devices (output).
  • Page 37 Chapter 6: Operation Example Get all CPU device – CON device connections. 0x1B 0x5B 0x52 Response Telegram ESC ] R Size CpuCnt ConCnt <CpuId, ConId>[1] … <CpuId, ConId>[ CpuCnt] <ConId, CpuId>[1] … <ConId, CpuId>[ ConCnt] Description Return all CPU device–CON device connections in pairs. For each defined CPU device, the ConId of the connected CON device will be added, or 0 if the CPU device is disconnected.

  • Page 38: Set Connection For All Con Devices And Cpu Devices

    Chapter 6: Operation 6.2.13 Set Connection for All CON Devices and CPU Devices Request Telegram ESC [ S Size CpuCnt ConCnt <CpuId, ConId>[1] … <CpuId, ConId>[ CpuCnt] <ConId, CpuId>[1] … <ConId, CpuId>[ ConCnt] Description Set a connection for all defined CON devices and CPU devices. For each defined CPU device, add the ConId, or 0 if the CPU device is disconnected.

  • Page 39: Set Extended Connection

    Chapter 6: Operation 6.2.14 Set Extended Connection Request Telegram ESC [ b Size CpuId ConId Mode Description Set CON device (input) connection to CPU device (output) and CPU device (input) connection to CON device (output). Data of CON device (USB, audio, …) is transmitted to a CPU device. Data of CPU device (video, USB, audio, …) is transmitted to a CON device.

  • Page 40: Set Virtual Con Device To A Real Con Device

    Chapter 6: Operation 0x1B 0x5B 0x54 0x07 0x00 0xC9 0x0B Response Telegram ESC ] T Size RConId VConId Description Return virtual CON device of a real CON device. RConId ID of real CON device VConId ID of virtual CON device Example Return virtual CON device (VConId = 4034) of a real CON device (RConId = 3017).

  • Page 41: Get Real Cpu Device

    Chapter 6: Operation 6.3.3 Get Real CPU Device Request Telegram ESC [ V Size VcpuId Description Get real CPU device of a virtual CPU device. VCpuId ID of virtual CPU device Example Get real CPU device of a virtual CPU device (VCpuId = 2018). 0x1B 0x5B 0x56 0x07 0x00 0xE2 0x07 Response Telegram...

  • Page 42: Get Virtual Con Devices

    Chapter 6: Operation Example Set real CPU device (RCpuId = 1012) to a virtual CPU device (VCpuId = 2018). 0x1B 0x5B 0x57 0x09 0x00 0xE2 0x07 0xF4 0x03 Response <ACK> [<ECHO>] or <NAK> [ ] = Optional elements 6.3.5 Get Virtual CON Devices Request Telegram ESC [ X Size ConCnt RConId[1] …...

  • Page 43: Set Virtual Con Devices To Real Con Devices

    Chapter 6: Operation RConID[1] = 3017, VConID[1] = 4034; RConID[2] = 3028, VConID[2] = 4042; RConID[3] = 3040, VConID[3] = 4045; 0x1B 0x5D 0x58 0x13 0x00 0xC9 0x0B 0xC2 0x0F 0xD4 0x0B 0xCA 0x0F 0xE0 0x0B 0xCD 0x0F 6.3.6 Set Virtual CON Devices to Real CON Devices Request Telegram ESC [ Y Size ConCnt <RConId, VConId>[1] …...

  • Page 44: Set Real Cpu Devices

    Chapter 6: Operation Description Get real CPU devices of virtual CPU devices. For CpuCnt = 0, all virtual CPU devices with assignments to virtual CPU devices will be returned. CpuCnt Number of CPU device VCpuId[ ] List of IDs of virtual CPU devices Example Get real CPU devices of virtual CPU devices (VCpuId = 2018, 2030, 2035).

  • Page 45: Best Practice

    Chapter 6: Operation Description Set real CPU devices to virtual CPU devices. CpuCnt Number of CPU devices <VCpuId, RCpuId>[ ] List of Pairs of VCpuId and RCpuId Example Set real CPU devices to virtual CPU devices. VCpuId[1] = 2018, RCpuId[1] = 1012; VCpuId[2] = 2030, RCpuId[2] = 1013;...

  • Page 46: Private Access (Establishing An Exclusive Kvm Session)

    Chapter 6: Operation 6.4.3 Private Access (Establishing an Exclusive KVM Session) Set CON device connection to CPU device and CPU device connection to CON device, CpuId = 1012 and ConId = 3017: 0x1B 0x5B 0x62 0x0B 0x00 0xF4 0x03 0xC9 0x0B 0x02 0x00 Disconnect: 0x1B 0x5B 0x62 0x0B 0x00 0xF4 0x03 0x00 0x00 0x02 0x00 6.4.4 USB 2.0 Access (Establishing a USB 2.0 Data Connection)

  • Page 47: Specifications

    Chapter 7: Specifications 7. Specifications The DKM FX can be controlled via RS-232 serial interface or TCP/IP socket (Port 5555). Table 7-1. Telegram structure. Type Bytes Description Control character Always: ESC (0x1B) Server identification Identification of service Command A special command...

  • Page 48: System Requests

    Chapter 7: Specifications Table 7-2. Sequence of a data communication. DKM FX Matrix Control CPU — Sending a command Acquiring a command, processing — a command, blocking of further commands a) Errors occurred: <NAK> b) No errors <ACK> — c) Optional: <ECHO>...

  • Page 49: Switch Commands

    Chapter 7: Specifications Table 7-4. Get system time. Type Bytes Description Hex Coding Control character 0x1B Server identification 0x28 Command 0x53 Size Total length of telegram (12 bytes) 0x0C 0x00 Seconds Seconds (0–59) 0x00 - 0x59 Minutes Minutes (0–59) 0x00 - 0x59 Hours Hours (0–23) 0x00 - 0x23...

  • Page 50: Get Cpu Device Connected To Con Device

    Chapter 7: Specifications 7.2.2 Get CPU Device Connected to CON Device Request: Telegram ESC [ H Size ConId General description: Get CPU device (input) connected to CON device (output). Table 7-6. Get system time. Type Bytes Description Hex Coding Control character 0x1B Server identification 0x28...

  • Page 51: Set Cpu Device Connection To Con Device

    Chapter 7: Specifications 7.2.3 Set CPU Device Connection to CON Device Request: Telegram ESC [ I Size ConId CpuId General description: Set CPU device connection (input) to CON device (output). Input data of CPU device (video, USB, audio, …) will be transmitted to CON device.

  • Page 52: Get Cpu Devices Connected To Con Devices

    Chapter 7: Specifications 7.2.4 Get CPU Devices Connected to CON Devices Request: Telegram ESC [ J Size ConCnt ConId[1] … ConId[ConCnt] General description: Get CPU devices (input) connected to CON device (output). For ConCnt = 0, all CON devices will be returned. Table 7-9.
  • Page 53 Chapter 7: Specifications Table 7-10. Get CPU devices (input) connected to CON devices (output). Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5D Command 0x4A e.g. for ConCnt = 3 Size Total length of telegram (7 Bytes + data) 0x13 0x00 ConCnt Number of CON devices...

  • Page 54: Set Connections Of Cpu Devices To Con Devices

    Chapter 7: Specifications 7.2.5 Set Connections of CPU Devices to CON Devices Request: Telegram ESC [ K Size ConCnt <ConId, CpuId>[1] … <ConId, CpuId>[ConCnt] General description: Set connections of CPU devices (input) to CON devices (output). Data of CPU (video, USB, audio, …) will be transmitted to CON device. Table 7-11.

  • Page 55: Get Con Device Connected To Cpu Device

    Chapter 7: Specifications 7.2.6 Get CON Device Connected to CPU Device Request: Telegram ESC [ L Size CpuId General description: Get CON device (input) connected to CPU device (output). Table 7-12. Get CON device connected to CPU device. Type Bytes Description Hex Coding Control character...

  • Page 56: Set Con Device Connection To Cpu Device

    Chapter 7: Specifications Example: Return CON device (ConId = 3017) connected to CPU device (CpuId = 1012). 0x1B 0x5D 0x4C 0x09 0x00 0xF4 0x03 0xC9 0x0B or <NAK> 7.2.7 Set CON Device Connection to CPU Device Request: Telegram ESC [ M Size CpuId ConId General description: Set CON device (input) connection to CPU device (output).

  • Page 57: Get Con Devices Connected To Cpu Devices

    Chapter 7: Specifications 7.2.8 Get CON Devices Connected to CPU Devices Request: Telegram ESC [ N Size CpuCnt CpuId[1] … CpuId[CpuCnt] General description: Get CON devices (input) connected to CPU devices (output). For CpuCnt = 0, all CPU devices will be returned. Table 7-15.

  • Page 58: Set Connection Of Con Devices To Cpu Devices

    Chapter 7: Specifications Table 7-16. Return CON devices (input) connected to CPU devices (output). Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5B Command 0x4E e.g. for CpuCnt = 3 Size Total length of telegram (7 Bytes + data) 0x13 0x00 CpuCnt Number of CPU devices...

  • Page 59: Set Con Device Connection To Cpu Device (Bidirectional)

    Chapter 7: Specifications Table 7-17. Set connection CON devices (input) to CPU devices (output). Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5B Command 0x4F e.g. for CpuCnt = 3 Size Total length of telegram (7 Bytes + data) 0x13 0x00 CpuCnt Number of CPU devices...

  • Page 60: Set Connection Of Con Devices To Cpu Devices (Bidirectional)

    Chapter 7: Specifications Table 7-18. Set CON device (input) connection to CPU device (output) and CPU device (input) connection to CON device (output). Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5B Command 0x50 Size Total length of telegram (9 bytes) 0x09 0x00 CpuId ID of CPU device...

  • Page 61: Get All Connections

    Chapter 7: Specifications Table 7-19. Set connection of CON devices to CPU devices (bidirectional). Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5B Command 0x51 Size Total length of telegram (7 bytes + data) 0x09 0x00 e.g. for Cnt = 3 Size of list 0x13 0x00 CpuId...
  • Page 62 Chapter 7: Specifications Example: Get all CPU device–CON device connections 0x1B 0x5B 0x52 Response: Telegram ESC ] R Size CpuCnt ConCnt <CpuId, ConId>[1] … <CpuId, ConId>[ CpuCnt] <ConId, CpuId>[1] … <ConId, CpuId>[ ConCnt] General description: Return all CPU device–CON device connections in pairs. For each defined CPU device, the ConId of the connected CON device will be added, or 0 if the CPU device is disconnected.

  • Page 63: Set Connection For All Con Devices And Cpu Devices

    Chapter 7: Specifications Example: Return all CPU device – CON device connections in pairs. CpuId[1] = 1012, ConId[1] = 3017; CpuId[2] = 1013, ConId[2] = 3028; CpuId[3] = 1020, ConId[3] = 3040; ConId[1] = 3017, CpuId[1] = 1012; ConId[2] = 3028, CpuId[2] = 0; 0x1B 0x5D 0x52 0x15 0x00 0x03 0x00 0x02 0x00 0xF4 0x03 0xC9 0x0B 0xF5 0x03 0xD4 0x0B 0xFC 0x03 0x0E 0x0B 0xC9 0x0B 0xF4 0x03 0xD4 0x0B 0x00 0x00...
  • Page 64 Chapter 7: Specifications Table 7-22. Set a connection for all defined CON devices and CPU devices. Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5B Command 0x53 e.g. for CpuCnt = 3 Size Total length of telegram (9 bytes + data) ConCnt = 2 0x15 0x00 e.g.

  • Page 65: Set Extended Connection

    Chapter 7: Specifications 7.2.14 Set Extended Connection Request: Telegram ESC [ b Size CpuId ConId Mode General description: Set CON device (input) connection to CPU device (output) and CPU device (input) connection to CON device (output). Data of CON device (USB, audio, …) is transmitted to a CPU device. Data of CPU device (video, USB, audio, …) is transmitted to a CON device.

  • Page 66: Assignments

    Chapter 7: Specifications 7.3 Assignments 7.3.1 Get Virtual CON Device Request: Telegram ESC [ T Size RConId General description: Get virtual CON device of a real CON device. Table 7-24. Get virtual CON device of a real CON device. Type Bytes Description Hex Coding...

  • Page 67: Set Virtual Con Device To A Real Con Device

    Chapter 7: Specifications Example: Return virtual CON device (VConId = 4034) of a real CON device (RConId = 3017). 0x1B 0x5B 0x54 0x09 0x00 0xC9 0x0B 0xC2 0x0F or <NAK> 7.3.2 Set Virtual CON Device to a Real CON Device Request: Telegram ESC [ U Size RConId VConId General description:...

  • Page 68: Get Real Cpu Device

    Chapter 7: Specifications 7.3.3 Get Real CPU Device Request: Telegram ESC [ V Size VCpuId General description: Get real CPU device of a virtual CPU device. Table 7-27. Get real CPU device of a virtual CPU device. Type Bytes Description Hex Coding Control character 0x1B...

  • Page 69: Set Real Cpu To A Virtual Cpu

    Chapter 7: Specifications Example: Return real CPU device (RCpuId = 1012) of a virtual CPU device (VCpuId = 2018). 0x1B 0x5D 0x56 0x09 0x00 0xE2 0x07 0xF4 0x03 or <NAK> 7.3.4 Set Real CPU to a Virtual CPU Request: Telegram ESC [ W Size VCpuId RCpuId General description: Set real CPU device to a virtual CPU device.

  • Page 70: Get Virtual Con Devices

    Chapter 7: Specifications 7.3.5 Get Virtual CON Devices Request: Telegram ESC [ X Size ConCnt RConId[1] … RConId[ConCnt] General description: Get virtual CON devices of a real CON device. For ConCnt = 0, all real CON devices with assignments to virtual CON devices will be returned.
  • Page 71 Chapter 7: Specifications Table 7-31. Return virtual CON devices of a real CON device as pairs. Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5D Command 0x58 e.g. for ConCnt = 3 Size Total length of telegram (7 bytes) + data 0x13 0x00 ConId Number of CON device...

  • Page 72: Set Virtual Con Devices To Real Con Devices

    Chapter 7: Specifications 7.3.6 Set Virtual CON Devices to Real CON Devices Request: Telegram ESC [ Y Size ConCnt <RConId, VConId>[1] … <RConId, VConId>[ConCnt] General description: Set virtual CON devices to real CON devices. Table 7-32. Set virtual CON devices to real CON devices. Type Bytes Description...

  • Page 73: Get Real Cpu Device

    Chapter 7: Specifications 7.3.7 Get Real CPU Device Request: Telegram ESC [ Z Size CpuCnt VCpuId[1] … VCpuId[CpuCnt] General description: Get real CPU devices of virtual CPU devices. For CpuCnt = 0, all virtual CPU devices with assignments to virtual CPU devices will be returned.
  • Page 74 Chapter 7: Specifications Table 7-34. Return real CPU devices of virtual CPU devices as pairs. Type Bytes Description Hex Coding Control character 0x1B Server identification 0X5D Command 0x5A e.g. for CpuCnt = 3 Size Total length of telegram (7 bytes + data) 0x13 0x00 CpuCnt Number of CPU devices...

  • Page 75: Set Real Cpu Devices

    Chapter 7: Specifications 7.3.8 Set Real CPU Devices Request: Telegram ESC [ a Size CpuCnt <VCpuId, RCpuId>[1] … <VCpuId, RCpuId>[CpuCnt] General description: Set real CPU devices to virtual CPU devices. Table 7-35. Set real CPU devices to virtual CPU devices. Type Bytes Description...

  • Page 76: Connector Pinouts

    Chapter 7: Specifications 7.4 Connector Pinouts Table 7-36. DB9 connector. Picture Signal Color Signal Not connected Not connected — — Table 7-37. RJ-45 connector. Picture Signal Color Signal Not connected Not connected Not connected Not connected Table 7-38. RJ-45 connector (serial). Picture Signal Color...

  • Page 77: Troubleshooting

    Chapter 8: Troubleshooting 8. Troubleshooting In Chapters 8–9, support for problems with the DKM FX API is provided. If you have problems with the involved devices, especially the DKM matrix, refer to the respective device manuals. 8.1 Network Error Diagnosis: Network settings are not accepted after editing.

  • Page 78: Technical Support

    Chapter 9: Technical Support 9. Technical Support Before contacting technical support, please ensure you have read this manual, and then installed and set up your DKM FX as recommended. Contact Black Box Technical Support at 724-746-5500 or info@blackbox.com. Support Checklist To efficiently handle your request it is necessary to provide us with complete information for support and problem cases.

  • Page 79: Glossary

    Composite Video: The Composite Video is also called CVBS and it is part of the PAL TV standard. CON Unit: Component of a DKM FX or Media Extender to connect to the con- sole (monitor(s), keyboard and mouse; optionally also with USB 2.0 devices).
  • Page 80 Chapter 10: Glossary DVI-I: A combined signal (digital and analog) that allows running a VGA monitor at a DVI-I port – in contrast to DVI-D (see DVI). EGA: The Enhanced Graphics Adapter (EGA) is an old analog graphic standard, introduced by IBM in 1984. A D-Sub 9 connector is used for connection. Fiber: Single-mode or multimode fiber cables.
  • Page 81 An API may include specifications for routines, data structures, object classes, and variables. Echo: The response of the DKM FX matrix to an external command (optional). NACK: A transmission control character sent by a station as a negative response to the station with which the connection has been set up.
  • Page 82 NOTES Page 82 724-746-5500 | blackbox.com ACX048 API manual...
  • Page 83 NOTES Page 83 724-746-5500 | blackbox.com ACX048 API manual...
  • Page 84 724-746-5500 or blackbox.com. About Black Box Black Box provides an extensive range of networking and infrastructure products. You’ll find everything from cabinets and racks and power and surge protection products to media converters and Ethernet switches all supported by free, live 24/7 Tech support available in 30 seconds or less.

This manual is also suitable for:

Dkm fx compact

Table of Contents