KRAMER: SIMPLE CREATIVE TECHNOLOGY
Communication Protocol 3000
12
General Commands
Command Syntax Response
Protocol Handshaking #DEV_ID@ ~ DEV_ID@ OK
Parameters:
DEV_ID – Each device has its own K-Net ID that matches to a specific device in K-Config configur ation tree.
K-Net Auxiliary Device must react only to commands which are preceded by its o wn ID.
Example:
WebAccess: #03@
Device Application: ~03@ OK
Note:
Every device (or application that emulates a device) shoul d reply to this request if preceded by its K-Net ID.
Room controllers commands
Emulate button action #01@BTN BTN,[KEYPAD_ID,[ACTION ]]CR ~01@BTN BTN,KEYPAD_ID,ACTION
RESULTCRLF
Device needs to send this command to the master device when it wants to emulate button action
BTN – Button ID according to the configuration in K-Config
KEYPAD_ID – The KNET ID of the device that the emulated button belongs to according to the configu ration in K-Config
ACTION - P=Button Pressing / H= Button Holding / R=Button Releas e.
Valid button operations sequence will be P->H(->H…)->R or P->R or only R.
Pressing and Holding will activate “Activate while pres sed” trigger if defined in K-Config, Releasing wil l activate “Activate on Release” and “Toggle ”
triggers.
RESULT – OK
User can supply 1, 2 or 3 arguments.
The default arguments are :
KEYPAD_ID - the first ID on the list (in the file portdef.ini)
ACTION – P=Button Pressing / R=Button Release.
Example (device application emulate releasing of button 1 i n keypad 3):
Device Application: #01@BTN 1,3,RCR
Master response: ~01@BTN 1,3,R OKCRLF
Note: Master response may be followed by other commands or rep lies according to the Action list for the button t rigger from configuration in K-Config.
Config RGB button leds #DEV_ID@RGB BTN, RED , GREEN, BLUE, STATE CR ~DEV_ID@RGB BTN, RED, GREEN , BLUE,
STATE RESULT CRLF
Device that implements lit buttons should react to this c ommand and set its button.
Device can support full color buttons or just plain on/off l ights.