Sennheiser Media Control Protocol for ew300/500 receivers
Hans Schouten
Posts: 5
Hi,
Has anyone experience using the Sennheiser Media Control Protocol for readout settings ie. battery level etc for a Sennheiser ew300 series receiver?
I have the protocol from the sennheiser site but I won't get any response.
I make a connection using UDP (type 3 in IP_CLIENT_OPEN) over port 53212.
Regards,
Hans Schouten.
Has anyone experience using the Sennheiser Media Control Protocol for readout settings ie. battery level etc for a Sennheiser ew300 series receiver?
I have the protocol from the sennheiser site but I won't get any response.
I make a connection using UDP (type 3 in IP_CLIENT_OPEN) over port 53212.
Regards,
Hans Schouten.
0
Comments
Please do not cross-post threads.
You also posted this here: http://www.amxforums.com/showthread.php?9286-Sennheiser-Media-Control-Protocol-for-ew300-500-receivers.
As Auser once put it:
Thanks for responding to my question.
I have attached the Sennheiser protocol.
A small part of my code:
DEFINE_DEVICE
dvSENNHEISER_1 = 0:7:3
DEFINE_VARIABLE
VOLATILE INTEGER iSENNHEISER_1_BAT_LEVEL
DEFINE_EVENT
DATA_EVENT[dvSENNHEISER_1]
{
ONLINE:
{
SEND_COMMAND Data.Device,"'RXON'"
}
STRING:
{
STACK_VAR CHAR cSENNHEISER_1_MSG[50]
cSENNHEISER_1_MSG = Data.Text
send_string 0,"cSENNHEISER_1_MSG"
IF (FIND_STRING (cSENNHEISER_1_MSG,"$0D",1))
{
IF (FIND_STRING (cSENNHEISER_1_MSG,'Bat ',1))
{
REMOVE_STRING (cSENNHEISER_1_MSG,'Bat ',1)
iSENNHEISER_1_BAT_LEVEL = ATOI(REMOVE_STRING (cSENNHEISER_1_MSG,"$0D",1))
}
}
}
}
DEFINE_PROGRAM
(*========================================*)
(* GET SENNHEISER BAT LEVEL *)
(*========================================*)
WAIT 50 // for testing
{
IP_CLIENT_OPEN(dvSENNHEISER_1.Port, '192.168.40.160', 53212, 3) // UDP CONNECTION ! 3 = UDP WITH RECEIVE
WAIT 10
{
SEND_STRING dvSENNHEISER_1,"'Bat',$0D"
}
}
(*
*)
You can get the BAT level as a part of the cyclic attributes.
Use the Push command to get the cyclic attributes.
To get a single status of this cyclic attributes use:
(first open the ip connection)
Push 0 100 0<CR>
(the ip connection will close due a timeout mechanism included in the protocol)
So you should get all cyclic parameters back once.
You can find the cyclic attributes response on page 9 of the protocol.
Regards,
Markus