1. Crestron
  2. Теми

Shure MXA910 protocol details

 

Anybody talked to this ceiling array mic yet?  Has a protocol document, but it's a little... underspecified.  Is the < > and spacing literal?  Are there delimiters?

http://www.shure.com/americas/products/microphones/microflex-advance/mxa910-ceiling-array-microphone#support
 

Yep, very easy to talk to and I believe the <> were literal and no delimiter that I remember.


Mark

On Tue, Jan 17, 2017 at 11:14 AM, Jeremy Weatherford jweather@... [Crestron] <Crestron@...> wrote:
 

Anybody talked to this ceiling array mic yet?  Has a protocol document, but it's a little... underspecified.  Is the < > and spacing literal?  Are there delimiters?

http://www.shure.com/americas/products/microphones/microflex-advance/mxa910-ceiling-array-microphone#support
Andrew Welker
 

What Mark said. It's easy to control and pretty much anything you can do on the web interface, you can do from the API. To check your protocol, just connect using a terminal program and send the commands you want. If I remember correctly, you'll get lots of unsolicited feedback, so be prepared for that.


On Tue, Jan 17, 2017 at 11:19 AM Mark Delzer mdelzer@... [Crestron] <Crestron@...> wrote:

Yep, very easy to talk to and I believe the <> were literal and no delimiter that I remember.


Mark


On Tue, Jan 17, 2017 at 11:14 AM, Jeremy Weatherford jweather@... [Crestron] <Crestron@...> wrote:
 

Anybody talked to this ceiling array mic yet?  Has a protocol document, but it's a little... underspecified.  Is the < > and spacing literal?  Are there delimiters?

http://www.shure.com/americas/products/microphones/microflex-advance/mxa910-ceiling-array-microphone#support
 

"Is the < > and spacing literal?  Are there delimiters?"

Yes, and the greater-than *is* your delimiter...  :)

  - Chip
 

Great, thanks for all the helpful responses.

On Tue, Jan 17, 2017 at 11:57 AM, chipmoody@... [Crestron] <Crestron@...> wrote:
 

"Is the < > and spacing literal?  Are there delimiters?"

Yes, and the greater-than *is* your delimiter...  :)

  - Chip
 

I'm controlling a bunch of these all over at a large site I'm working on and they are pretty easy to talk to.  I haven't found any issues or mistakes with the protocol manual.

The < and > are literal, and there is no extra delimiter after the ">" char.  A sample command should look like:
"< SET LED_COLOR_MUTED RED >"

Just open a TCP/IP client port to them on port #2202 and you should be good to go.  Another note, is that for control, you need to connect to the "control IP address".  I believe these things get 2 different IP addresses when setting them up, one is a Dante IP, and the other is a Control IP.  The Dante IP is specifically for passing audio between other Dante endpoints, and the Control-IP is for setup and controlling them with the API commands.  Pretty straight forward.

-jason
nikita10@hotmail.com
 

Hi Jason,
Would you happen to have a module for this?

-Lou
 

Just use an sio.  Commands are easy to find in the Shure manual. 

Ephrain

On Jul 23, 2018, at 9:01 PM, nikita10@... [Crestron] <Crestron@...> wrote:

 

Hi Jason,

Would you happen to have a module for this?

-Lou
 

I've got a module;

Needs some testing though...
nikita10@hotmail.com
 

Thanks for the quick response guys.

-Lou
nikita10@hotmail.com
 

Are there Mic gain controls through sliders?
 

I don't have a module, I usually only control the LED color through them rather than anything else like volume or actual muting.  Most of that type of control I prefer to do directly on the DSP system, but clients like the LED to track red/green when muting it, so I mute on the DSP and then just send the command to turn the LED color to red/green to match the mute state on the DSP.

I only use simple SIO for this, as there is nothing more to it than the commands.
 

"Would you happen to have a module for this?"

No module, but I've got a program with an SIO loaded with most of the commands/responses for this mic if you want it.

It's set up so that if you tap it, it starts cycling through all the ring colors - a second tap turns off ALL the indicators.  (Which - IIRC - had to be done through presets, they oddly enough didn't include commands to turn the white "mic muted" indicators on and off)

  - Chip
 

That would be great. I could build off of there. Thanks again

-Lou
 

Hey Chip,  I've had to control the LED color and LED on/off before, and I was able to do it without presets.  I had to use the "brightness" command and set it either to 0 or 2?  (full off or full on) to make the led go off.  Not sure if this is similar to what you were doing, but using the brightness wasn't exactly my first instinct to use.

My use case, was that the client wanted to have the mic to track the VoIP phone.  If the phone was not in use, the LED would be OFF.  If the VoIP was off-hook, the LED would track Red/Green with privacy mute.  The awesome part is that you can change the colors still while the brightness is OFF.  So you can have simple code track red/green, and another peice of simple code track hook on/off and change the brightness to off/full and it works great.

No Presets required.

-jason
 

"The awesome part is that you can change the colors still while the brightness is OFF"

I *think* we're talking about different LEDs.  I can control the *ring* no problem - it's the "mic mute" LEDs I'm talking about.

  - Chip
 

Use the Brightness command to turn the LED off. I usually don’t even mute it since I am already muting the DSP. I just send commands for changing the unmuted color from green to red or from a color to no light. I have a module that I can’t share unfortunately that does parse out the preset names. Nothing difficult about parsing the feedback if needed. They would be the perfect product if they provided a second LAN port for control, IMO.

-Davis
 

I do the same.

0 = Off
1 = Dim
2 = Bright (default)

On Tue, Jul 24, 2018 at 9:20 PM jasonmussetter@... [Crestron] <Crestron@...> wrote:
 

Hey Chip,  I've had to control the LED color and LED on/off before, and I was able to do it without presets.  I had to use the "brightness" command and set it either to 0 or 2?  (full off or full on) to make the led go off.  Not sure if this is similar to what you were doing, but using the brightness wasn't exactly my first instinct to use.

My use case, was that the client wanted to have the mic to track the VoIP phone.  If the phone was not in use, the LED would be OFF.  If the VoIP was off-hook, the LED would track Red/Green with privacy mute.  The awesome part is that you can change the colors still while the brightness is OFF.  So you can have simple code track red/green, and another peice of simple code track hook on/off and change the brightness to off/full and it works great.

No Presets required.

-jason
brian.erch@yahoo.com
 

Same basic idea here. I've found that if I'm muting in a DSP or codec, it is better to just change the LED brightness or unmuted color in the mic so AEC doesn't have to reconverge when the mic unmutes again. Also, after looking at the module, I love that we have come to nearly the same conclusion development-wise, albeit separately.

Since we're talking Shure products, I have fairly lightweight modules for the Shure ULX-D and QLX-D wireless mics—mostly channel volume/mute and transmitter type. I have been using tx type status responses from the units to automatically recall handheld/lav transmitter presets in DSPs without having to expose buttons for these functions on a UI. I can post them if anyone is interested.
 

Chip, we must be talking about different mics?  I'm referring to the MXA910 Ceiling mic (only has 1 LED on it), it sounds like you may be referring to the tabletop version that has the color ring (MXA310?).  Sorry for any confusion, I haven't used the tabletop ones yet, so don't know if those are different.

1 - 20 з 24