¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

IR control thru DM RMC Weirdness


 

Hi All,
In all my years, I don't remember seeing this issue, anyone seen this and have a fix?
I have an LG TV IR driver (I've actually tried a few) that need to control (3) little/cheapo LG panels in secondary bedrooms.
They are connected to the standard DM-RMC-100-C room boxes. DM8x8 and RMCs are all 1080p level video and have latest FW for their capabilities.
when firing any command, the command is latched for ~2 seconds (esp. bad for Vol +/-). I can tell by the function as well as my Xantech emitters having the talk-back LEDs flasshing for 2 sec.
When I try the same IR driver(s) on the CP3 ports they just pulse for ~ 0.05 sec like you'd expect.
I have tried applying the 'pulse IR' filter via the Device Learner tool, with identical results...

It seems that the RMCs 'don't like' this IR driver (I didn't have time to test another driver on the RMC).

Anyone seen this behavior, and have a fix for it??? TIA!


 





Get
On Feb 20, 2023, at 6:34 PM, Steve Kuehn <steve@...> wrote:

Wow!? I am shock that this is the first time you have ever seen this issue.? Yes this is a well known problem with the DM-RMC-100-C and I don't believe Crestron has ever come up with a fix for it.

The issue is the DM-RMC-100-C does not handle an IR codes properly that has both at header and a repeat section.??? LG uses header length of 34 and then a very short repeat section of length two.? Yamaha is similar.

Basically what you need to do is generate 2 IR codes each for functions like vol+, vol-, up, down, left, and right.? For example, for up you will have a Up-Pulse and a Up-Hold. For the Up-Pulse, you will remove the repeat section of the code so it? just sends out a single 34 length header IR pulse.? For the Up_Hold, you will take the 34 length header and replace the repeat section with it -- so in the end you have a 0 length header and a 34 length repeat section which used to be the header. Then in your SIMPL program send the header pulse when the client pushes a button.? If the client holds the button, then send out the repeat code.

Probably be best to use a program like VERT to convert Crestron codes into standard hex codes.? Then manually edit the hex codes and then import them back into Crestron.

Good luck,
Steve


 

Geoff Reynolds wrote an IR utility several years ago, that could easily swap the one-time and repeat codes, in addition to a few other useful functions.

I no longer have the link, but maybe he'll chime in with it.

--- On Monday, February 20, 2023 at 6:35 PM, Steve Kuehn wrote:

Yes this is a well known problem with the DM-RMC-100-C and I don't believe
Crestron has ever come up with a fix for it.

The issue is the DM-RMC-100-C does not handle an IR codes properly that has
both at header and a repeat section. LG uses header length of 34 and then a
very short repeat section of length two. Yamaha is similar.

Basically what you need to do is generate 2 IR codes each for functions like
vol+, vol-, up, down, left, and right. For example, for up you will have a Up-
Pulse and a Up-Hold. For the Up-Pulse, you will remove the repeat section of
the code so it just sends out a single 34 length header IR pulse. For the
Up_Hold, you will take the 34 length header and replace the repeat section with
it -- so in the end you have a 0 length header and a 34 length repeat section
which used to be the header. Then in your SIMPL program send the header pulse
when the client pushes a button. If the client holds the button, then send out
the repeat code.

Probably be best to use a program like VERT to convert Crestron codes into
standard hex codes. Then manually edit the hex codes and then import them back
into Crestron.

Good luck,
Steve


 

A trial version can be obtained here:


Geoff

On Tue, Feb 21, 2023 at 7:27 PM Tony Golden <mrgolden@...> wrote:
Geoff Reynolds wrote an IR utility several years ago, that could easily swap the one-time and repeat codes, in addition to a few other useful functions.

I no longer have the link, but maybe he'll chime in with it.



> --- On Monday, February 20, 2023 at 6:35 PM, Steve Kuehn wrote:
>
> Yes this is a well known problem with the DM-RMC-100-C and I don't believe
> Crestron has ever come up with a fix for it.
>
> The issue is the DM-RMC-100-C does not handle an IR codes properly that has
> both at header and a repeat section.? LG uses header length of 34 and then a
> very short repeat section of length two.? Yamaha is similar.
>
> Basically what you need to do is generate 2 IR codes each for functions like
> vol+, vol-, up, down, left, and right.? For example, for up you will have a Up-
> Pulse and a Up-Hold. For the Up-Pulse, you will remove the repeat section of
> the code so it? just sends out a single 34 length header IR pulse.? For the
> Up_Hold, you will take the 34 length header and replace the repeat section with
> it -- so in the end you have a 0 length header and a 34 length repeat section
> which used to be the header. Then in your SIMPL program send the header pulse
> when the client pushes a button.? If the client holds the button, then send out
> the repeat code.
>
> Probably be best to use a program like VERT to convert Crestron codes into
> standard hex codes.? Then manually edit the hex codes and then import them back
> into Crestron.
>
> Good luck,
> Steve







 

I don't think that the issue is the IR driver, per se, as I've tried a version with the Pulse IR filter applied.
We did some more testing and multiple LG files behaved basically the same way, BUT the tried and true Samsung UN series driver worked fine.
It appears to be something about the LG drivers being processed thru the RMC IR output...
Granted, I haven't dealt with LG at all more than 2-3 times in the last 5-7 years, but its weird to me that no one seems to have see this issue. there has to be at least 10% of the DM installs that have LG TVs on their RMCs, wouldn't you think??


 
Edited

Maybe because serial is more widely used to control LG's vs IR? Perhaps the OP could use serial vs IR with better results.


 

Thru further testing, I found that my 'PulseIR' version of the driver did not have the pulse ir filter properly applied - could be that I didn't click SAVE hard enough, or something stupid like that...
Once I fixed this, the driver started only pulsing for 1/2 sec. like it should.

I still concur that this is some sort of bug with the LG drivers and the RMCs, but this is good enough for the application...

Thanks for everyone's input...!


 

I have just sent you by email an IR driver file for LG TV. This has been in use on one of our installations since 2016 using DM16x16 with DM-RMC-4K-C endpoint. It is connected to just some basic LG TV from around 2015. It is currently, and has always worked without issue. KR David


 

Thank you, David! I will look to try and report back...
Unfortunately if you already emailed it, I haven't received it. I checked all spam/junk filters and no sign of it...

If possible, you could post in the files section for all, or if you want to just send it to me you could use the Wormhole file transfer system and email me the link...


TIA!!