9. Programmer's Reference
UBEX series – Matrix Application Mode – User's Manual
105
9. Programmer's Reference
UBEX series – Matrix Application Mode – User's Manual
105
MA
TRIX APPLIC
A
TION MODE
Applied F-series endpoint firmware package: v1.4.1 | Applied R-series endpoint firmware package: v1.4.1 | Applied MMU firmware package: v1.2.1 | LDC software: v1.34.0b2
9.2.7. Signature
DEFINITION:
The signature is a four-digit-long hexadecimal value that can be optionally placed before
every command to keep a command and the corresponding responses together as a group.
Each line is terminated with a carriage return (Cr, ‘\r’) and line feed (Lf, ‘\n’) characters. In several cases the
number of the lines in the response cannot be determined in advance, e.g. the client intends to receive for the
whole response and also wants to be sure, that the received lines belong together and to the same command.
In these cases, a special feature the ‘signature’ can be used. The response to that particular command will
also be preceded by the signature, and the corresponding lines will be between brackets:
ç
1700#GET /MEDIA/EDID.*
æ
{1700
æ
m- /EDID:copy
æ
m- /EDID:delete
æ
m- /EDID:reset
æ
m- /EDID:switch
æ
m- /EDID:switchAll
æ
}
INFO:
The lines of the signature are also Cr and Lf terminated.
9.2.8. Subscription
DEFINITION:
Subscription to a node means that the user will get a notification if a property of the node
changes.
A user can subscribe to any node. These notifications are asynchronous messages and are useful to keep the
client application up to date, without having to periodically poll the node to detect a changed property. When
the user does not want to be informed about the changes anymore, he can simply unsubscribe from the node.
ATTENTION!
The subscriptions are handled separately for connections. Hence, if the connection is
terminated all registered subscriptions are deleted. After reopening a connection all subscribe commands
have to be sent in order to get the notifications of the changes on that connection.
Subscribe to a Node
ç
OPEN /MEDIA/XP/VIDEO
æ
o- /MEDIA/XP/VIDEO
Get the Active Subscriptions
ç
OPEN
æ
o- /MEDIA/XP/VIDEO
æ
o- /MEDIA/EDID
æ
o- /DISCOVERY
Subscribe to Multiple Nodes
ç
OPEN /MEDIA/XP/VIDEO/*
æ
o- /MEDIA/XP/VIDEO/*
Unsubscribe from a Node
ç
CLOSE /MEDIA/XP/VIDEO
æ
c- /MEDIA/XP/VIDEO
Unsubscribe from Multiple Nodes
ç
CLOSE /MEDIA/XP/VIDEO/*
æ
c- /MEDIA/XP/VIDEO/*
9.2.9. Notifications about the Changes of the Properties
When the value of a property is changed and the user is subscribed to the node, which the property belongs
to, an asynchronous notification is generated. This is notification is called as the ‘change message’. The
format of such a message is very similar to the response for the
GET
command:
æ
CHG /MEDIA/XP/VIDEO.SourcePortCount=10
A Short Example of How to Use the Subscription
There are two independent users controlling the device through two independent connections (
Connection #1
and
Connection #2
). The events in the rows occur after each other.
ç
OPEN /MANAGEMENT/LABEL
æ
o- /MANAGEMENT/LABEL
ç
GET /MANAGEMENT/LABEL.DeviceLabel
æ
pm /MANAGEMENT/LABEL.DeviceLabel=UBEX-MMU-X200
ç
GET /MANAGEMENT/LABEL.DeviceLabel
æ
pm /MANAGEMENT/LABEL.DeviceLabel=UBEX-MMU-X200
ç
SET /MANAGEMENT/LABEL.DeviceLabel=MMU_ServerRoom
æ
pw /MANAGEMENT/LABEL.DeviceLabel=MMU_ServerRoom
æ
CHG /MANAGEMENT/LABEL.DeviceLabel=MMU_ServerRoom
Explanation:
The first user (
Connection #1
) set a subscription to a node. Later the other user (
Connection #2
)
made a change, and thanks for the subscription, the first user got a notification about the change.
9.2.10. Legend for the Control Commands
Format
Description
<in>
Stream source ID
<out>
Output port ID
<port>
Interface port ID
<expression>
Batched argument: the underline means that more expressions or parameters can be
placed using a semicolon, e.g.
S101;S102;S401
or
S101:D301;S302:D201
<UBEX_EP>
UBEX endpoint ID, e.g. UBEXF254D9
<dev_ID>
Logical device ID of the UBEX endpoint
Sent command
Received response
•
Space character
|
Separator line ("or" character)
Connection #1
Connection #2
Connection #1
}
}
