Page 1 of 1
Special function messes up IR code
Posted: Thu Jan 12, 2012 8:35 pm
by picree
RMIR file is
uploaded here. I am trying to include the discrete on/off functionality into a macro that relies on the extender protocols. I am using IR Scope to check my work. The problem device is the Lumagen (CD Video 0900). I have Discrete ON from the OEM remote mapped to the Sleep key on my 15-2117 (and Discrete OFF mapped to Shift-Sleep). That key works fine and properly turns on/off the device. IR Scope says the key decodes to:
Protocol Lumagen, Device 2, OBC 7, Hex 07
The IRP form is:
{37.8k,415,msb}<1,-6|1,-12>(A:12,1,-11.1m)+{A=$207}; Alt leadout form: ^56m
HOWEVER, when I include the key in any sort of Special Protocol (like ToadTog) and try to access that function from another key to just toggle it (like the Power key) then the IR signal changes to:
Protocol Thomson7, Device 4, OBC 112, Hex F0
The IRP form is:
{38.0k,415,msb}<1,-6|1,-12>(A:12,1,-174.3m)+{A=$207}; Alt leadout form: ^220m
WHAT THE HECK????

Can someone take a look at my RMIR file to see what gives? Ive tried all different options I can think of. Thanks.
EDIT: In fact, when I check all my other devices Power button functionality with IR Scope it seems like the extender somehow messes with the ditto/repeat sequence of the IR signal. In the case of my other devices the result is close enough apparently to toggle the device. Any thoughts?
Re: Special function messes up IR code
Posted: Thu Jan 12, 2012 11:30 pm
by eferz
picree wrote:WHAT THE HECK????

Can someone take a look at my RMIR file to see what gives? Ive tried all different options I can think of. Thanks.
EDIT: In fact, when I check all my other devices Power button functionality with IR Scope it seems like the extender somehow messes with the ditto/repeat sequence of the IR signal. In the case of my other devices the result is close enough apparently to toggle the device. Any thoughts?
You're actually not the only one that has this issue. Jledwell has a similar problem discussed in this thread (
https://www.hifi-remote.com/forums/viewtopic.php?t=13742). He is also using a extender with his 9910 and apparently isn't behaving well with his macros. Although, he doesn't have an IR widget to further analyze it. I'm starting to wonder if a bug crept in on one of the recent updates.
Posted: Fri Jan 13, 2012 5:12 am
by picree
Well, it certainly seems buggy. I've looked at the waveforms (direct key access vs calling through a ToadTog (or DSM) macro) and they are identical except for the leadout and the ditto/repeat pattern. In most of my equipment that changes the NEC1 protocol to decode to NEC2 but everything else matches so I guess it works (most of the time...it's always been a little flaky with power on/off but I just thought that was my equipment). In this case the different leadout must be enough to confuse the Lumagen.
@Jledwell's problem does sound very similar.
Can anyone using an extender test their power on/off codes with an IR Widget with/without passing them through a macro to see if there are any differences?
Posted: Fri Jan 13, 2012 6:29 am
by vickyg2003
It would appear that you've already diagnosed the problem. You are having a duration problem. The device is only sending out 1 frame when in a macro and the special protocols are for all practical purposes a macro. So the button doesn't work because you need a repeat frame or two. This should be an easy tweak, but I can't tweak this until Saturday. Maybe someone else will help you out before then.
Posted: Fri Jan 13, 2012 9:00 am
by picree
@vickyg-well the behavior isn't necessarily consistent across protocols. So it's more than a matter of adding a frame or two. For example, on my DVD power (NEC1) instead of two ditto frames the extender converts that to one repeat frame with a long lead out between (NEC2ish). For the Lumagen instead of two repeat frames the extender converts that to one repeat frame with a long lead out between (Thomson7 I guess).
Posted: Fri Jan 13, 2012 12:02 pm
by vickyg2003
picree wrote:@vickyg-well the behavior isn't necessarily consistent across protocols.
Well yes, each protocol is different. We need to tweak the protocol for Lumagen to send out two frames. Some protocols already force extra frames, this one doesn't.
Posted: Fri Jan 13, 2012 4:54 pm
by picree
I uploaded an IR Scope file to the
diagnostic forum if it will help in troubleshooting. It includes two waveforms. The first is the properly executed Lumagen Power On and the second waveform is that same key but passed to the 15-2117 Power button via a ToadTog toggle.
Posted: Fri Jan 13, 2012 6:00 pm
by vickyg2003
Posted: Fri Jan 13, 2012 10:24 pm
by picree
Sorry for the late reply but we were down watching a movie. In any case, WORKS GREAT! Checked all the buttons I had. Thanks so much for the fast reply Vicky! Wonderful!
I'll see if I cant add the mem A, mem B, and the aspect ratio buttons and upload it as complete.
Thanks again...great!
