search

bitfocus / companion-module-shure-wireless

MIT License
4 stars 9 forks source link

Shure SLX-D lock status #9

Closed jorblad closed 1 year ago

jorblad commented 3 years ago

According to SLX-D Command Strings there is a way to get lock status even from SLX-D but it does it with another command < GET LOCK_STATUS > < REP LOCK_STATUS ALL > instead < GET 1 TX_PWR_LOCK > so it would be nice to have that in the Channel Status Display

krocheck commented 3 years ago

Hi @sjobergsson, According to the manual and control spec as best as I can tell, the report you're referring to is for the receiver's lock status, not the transmitter(s). This is since there is the dual channel receiver and they would have a channel number if it were channel based.

If you'd like, you can telnet to the receiver on port 2022 and report back if you see any REP strings as you change the lock on the transmitter. It's always possible they implemented it but didn't show it in the control spec. I had to implement that model blind based on the spec since I didn't have one available. Keith

jorblad commented 3 years ago

Hi @sjobergsson, According to the manual and control spec as best as I can tell, the report you're referring to is for the receiver's lock status, not the transmitter(s). This is since there is the dual channel receiver and they would have a channel number if it were channel based.

If you'd like, you can telnet to the receiver on port 2022 and report back if you see any REP strings as you change the lock on the transmitter. It's always possible they implemented it but didn't show it in the control spec. I had to implement that model blind based on the spec since I didn't have one available. Keith

Sadly I don't have any slxd yet either, and now when I look at the spec you might be right but when I get slxd I will test if I can get out something unless someone else already has seen that then. Samuel

krocheck commented 3 years ago

Sounds good. Yeah, if I have the REP command and the different strings sent it can be easily added.

jeffmpelletier commented 3 years ago

I think you mean port 2202...

On Thu, Apr 1, 2021 at 3:34 PM Keith Rocheck @.***> wrote:

Sounds good. Yeah, if I have the REP command and the different strings sent it can be easily added.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-shure-wireless/issues/9#issuecomment-812185059, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMK7FPTD7K6XWTWFUVRMM3TTGTRHBANCNFSM4ZUTRXJA .

krocheck commented 3 years ago

Accurate ... did that from memory. My bad!

jmrowe504 commented 2 years ago

Hey, maybe I am missing something, but no matter what I do I can not communicate with any of my receivers. Please advise.

krocheck commented 2 years ago

From the same computer does Wireless Workbench see them?

jmrowe504 commented 2 years ago

As it would turn out I have to turn off the blocked access on the receiver. I did notice that not all of the receivers have the option for muting, which I will check again now that I’ve updated the firmware.

krocheck commented 1 year ago

I checked with Shure engineering ... the LOCK_STATUS is for the receiver. The transmitters don't send their lock status in the side channel data stream.

jeffmpelletier commented 1 year ago

Ha. Weird… that was me…

On Mon, Feb 20, 2023 at 5:34 PM Keith Rocheck @.***> wrote:

I checked with Shure engineering ... the LOCK_STATUS is for the receiver. The transmitters don't send their lock status in the side channel data stream.

— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-shure-wireless/issues/9#issuecomment-1437701762, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMK7FPTXRNYRFOKPHZMUUYLWYQESTANCNFSM4ZUTRXJA . You are receiving this because you commented.Message ID: @.***>

krocheck commented 1 year ago

I was simplifying the chain ... lol. Yes, I checked with @jeffmpelletier who checked with engineering :)

jeffmpelletier commented 1 year ago

And I’ll reply here for all, I did just get confirmation that adding < SET LOCK_STATUS > would require a firmware update. Not sure how high prioritizing that could be convinced to the powers that be, but I’ll put in a good word.

Best,

Jeff

On Mon, Feb 20, 2023 at 6:15 PM Keith Rocheck @.***> wrote:

I was simplifying the chain ... lol. Yes, I checked with @jeffmpelletier https://github.com/jeffmpelletier who checked with engineering :)

— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-shure-wireless/issues/9#issuecomment-1437727470, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMK7FPXRD3VA6KXX6UZUO6DWYQJJLANCNFSM4ZUTRXJA . You are receiving this because you were mentioned.Message ID: @.***>

jeffmpelletier commented 1 year ago

and just another update. I convinced the powers to include < SET LOCK_STATUS > in the next FW build; it's in an official ticket . Crossing fingers...

On Mon, Feb 20, 2023 at 6:54 PM Jeff Pelletier @.***> wrote:

And I’ll reply here for all, I did just get confirmation that adding < SET LOCK_STATUS > would require a firmware update. Not sure how high prioritizing that could be convinced to the powers that be, but I’ll put in a good word.

Best,

Jeff

On Mon, Feb 20, 2023 at 6:15 PM Keith Rocheck @.***> wrote:

I was simplifying the chain ... lol. Yes, I checked with @jeffmpelletier https://github.com/jeffmpelletier who checked with engineering :)

— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-shure-wireless/issues/9#issuecomment-1437727470, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMK7FPXRD3VA6KXX6UZUO6DWYQJJLANCNFSM4ZUTRXJA . You are receiving this because you were mentioned.Message ID: @.***>

krocheck commented 1 year ago

Sweet! Thanks Jeff!