Introduction
1
1 Introduction
Kramer Electronics offers a wide variety of control products that meet numerous different AV
requirements. These solutions make up the Kramer control system and offer seamless compatibility
with Kramer signal management and scaling products, as well as interfacing with display devices
and other third party products for complete room control solutions.
The control action lists (macros), associated in the K-Config configuration application with various
physical (keypad controllers) and software triggers, can also be initiated by sending the Kramer
Protocol 3000 commands over IP.
This document serves as a guideline for building an application (referred to as the "Virtual Device"
in K-Config and in this document) that will serve as a User Interface dev ice in a Kramer based
room control system.
The application can run on any platform (mobile, PC, and so on) and under any OS (Windows®,
Linux®, Android™, iOS®, and so on) - according to the competence of the developer, and end-user
preference.
The developer can use "Virtual Device" development guidelines to create the application for the
Virtual Device without any limitation of platform, design, and so on.
This document is intended for competent developers under the relevant OS and for the relevant
devices.
1.1 Definitions (within the context of this document)
K-NETsetup – A Kramer control setup, made from at least two units (one of them, the User
Interface device, can be a Virtual Device). The K-NET units communicate between them using the
Kramer Protocol 3000. Each unit on the K-NET setup has its own unique K-NET ID number.
Master Room Controller (Master RC) – A Kramer room control device; used as the Master in a
K-NET room control installation.
The Master RC will have a K-NET ID of 1 and will run the relevant configuration file created in the
K-Config application.
As of February 2011, Kramer's applicable Master RCs for Virtual Device setups are SV-551,
SV-552, SL-1, SL-10, SL-12 and SL-14RC.
K-NET auxiliary deviceA Kramer K-NET device, which is part of a Kramer room control setup
and is connected with a K-NET cable to the Master RC.
The auxiliary device K-NET ID will always be greater than 1.
Virtual DeviceAn application simulating a User Interface device that communicates over IP,
with a single Kramer Master RC as part of the K-NET setup.
The Virtual Device will use one of two reserved K-NET ID numbers – 11 or 12.
K-Config Virtual Device triggers layer – A functional duplication of the Virtual Device active
buttons and text fields in the K-Config application. Used to link the Virtual Device screens to the
control action lists (macros) written under K-Config.
2 The Communication Layer
The Virtual Device uses Ethernet connection (wired or wireless) and Protocol 3000 (see section 4),
for communication with the associated Master RC.