Hi Guys,
I have the Ethernet protocol document so I can write a Crestron module to talk to the unit. The document explains the commands going to the unit, but not the responses back from the unit. I don't have a unit here at present to test with. Is there a more complete protocol document please?
Cheers
Phil.
Digitool MX32 ethernet protocol
-
- New Member
- Posts: 1
- Joined: Mon May 18, 2015 11:14 pm
-
- Member
- Posts: 123
- Joined: Thu Feb 07, 2013 8:40 am
Re: Digitool MX32 ethernet protocol
Hi Phil,
The MX32 will not respond to most messages. In fact, the only way to get a response to an Ethernet message with the MX16/32/Live is by using the UPDATE command, no other command will have a response. But, you can use the UPDATE command to confirm that a message was received because the response from the UPDATE command will contain a copy of all of the messages that the Digitool received since the last time it received an UPDATE command.
For example, let's say I send the command BLINK (this command is not in the document; it will blink the screen, it's a good way to test that the Ethernet communication is working). I can then send the UPDATE command and here is the response I will get:
{55}{50}{44}{41}{54}{45}{25}{00}{00}{00}{01}{FF}{02}{00}{03}{FF}{04}{00}{05}{FF}{06}{00}{07}{FF}{08}{00}{11}{FF}{12}{00}{13}{FF}{14}{00}{15}{FF}{16}{00}{17}{FF}{18}{00}{FE}{00}{00}{00}{01}{FF}{02}{00}{03}{FF}{04}{00}{05}{FF}{06}{00}{07}{FF}{08}{00}{11}{FF}{12}{00}{13}{FF}{14}{00}{15}{FF}{16}{00}{17}{FF}{18}{00}{FE}
{42}{4C}{49}{4E}{4B}{25}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}
The top portion is the 79 byte response from the UPDATE command, but you'll notice an extra 32 bytes that contain "BLINK%" (42, 4C, 49, 4E, 4B, 25 is the ASCII representation of "BLINK%"). Now I have just confirmed that the Digitool received the previous BLINK command correctly.
- Scott D.
The MX32 will not respond to most messages. In fact, the only way to get a response to an Ethernet message with the MX16/32/Live is by using the UPDATE command, no other command will have a response. But, you can use the UPDATE command to confirm that a message was received because the response from the UPDATE command will contain a copy of all of the messages that the Digitool received since the last time it received an UPDATE command.
For example, let's say I send the command BLINK (this command is not in the document; it will blink the screen, it's a good way to test that the Ethernet communication is working). I can then send the UPDATE command and here is the response I will get:
{55}{50}{44}{41}{54}{45}{25}{00}{00}{00}{01}{FF}{02}{00}{03}{FF}{04}{00}{05}{FF}{06}{00}{07}{FF}{08}{00}{11}{FF}{12}{00}{13}{FF}{14}{00}{15}{FF}{16}{00}{17}{FF}{18}{00}{FE}{00}{00}{00}{01}{FF}{02}{00}{03}{FF}{04}{00}{05}{FF}{06}{00}{07}{FF}{08}{00}{11}{FF}{12}{00}{13}{FF}{14}{00}{15}{FF}{16}{00}{17}{FF}{18}{00}{FE}
{42}{4C}{49}{4E}{4B}{25}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}{00}
The top portion is the 79 byte response from the UPDATE command, but you'll notice an extra 32 bytes that contain "BLINK%" (42, 4C, 49, 4E, 4B, 25 is the ASCII representation of "BLINK%"). Now I have just confirmed that the Digitool received the previous BLINK command correctly.
- Scott D.
Scott Dickey
Peavey Embedded Software Engineer
Peavey Embedded Software Engineer