Common JP1.3 Extender V3

[unclemiltie]

Macros look fine to me. Should work. I'd report this to Bill. You may be the first to try this version on the Insignia.

He has, I'm trying to figure it out. I've asked him to try a few things (including replacing the call to scan the keypad with something else)

The thing is that the code in the extender hasn't changed since I ported the pre-combined code to the 3147 remote and released the first version of that extender. (other than trying to do the interruptible pause)

Tranx

In the case of the interrupt the key has to be a "real" keypress not one that is the next key in a macro. The mechanism uses the interrupt generated by a key press to decide if one was pressed and no such hardware interrupt is generated when processing the "keys" in a macro. Perhaps I need to clarify the read me on this?

[unclemiltie]

However concluded that the 'pause problem' was a red herring. That was because two stage macros (without pause) give the same outcomes: in an un-extended configuration both commands in a macro working normally, but in the similar extended configuration the first command not working and the second command was only working if the physical button was held down for an extra moment.

What do you mean by "two stage" macros?

let's say you have a macro defined on a button as

Exit = 1, 2, 3, 4, 5, 6, 7

are you saying that the "1" command is not being sent but the rest are? That would be a definite bug in the extender


It's often prudent to build a test version that simplifies what you are trying to do and prove that the remote is doing what it is supposed to, then making the more and more complicated parts.

So for example, if you wanted

Exit = 1, 2, 3, pause, 4, 5,, 6, 7

make info = 1, 2, 3
guide = 4, 5, 6 , 7

press info and then guide with a pause in the middle. If that's the case, then add the pause and the 4,5,6,7 to the end of info and see if it works.

[tranx]

(Follow up email also sent) - one of my original test commands, which works ok when sent by physically pressing its own button and in a non-extended macro, does not work when it is put in a macro in the extender
i.e.
Dev_dev2, 'problem button', pause on a phantom, 'some other button'
or
Dev_dev2, 'problem button', 'some other button'

or
Dev_dev2, 'some other button', pause on a phantom, 'problem button'
or
Dev_dev2, 'some other button', 'problem button'

I am not clear about the following or if it might be relevant?

In the case of the interrupt the key has to be a "real" keypress not one that is the next key in a macro. The mechanism uses the interrupt generated by a key press to decide if one was pressed and no such hardware interrupt is generated when processing the "keys" in a macro. Perhaps I need to clarify the read me on this?

[mdavej]

Macros look fine to me. Should work. I'd report this to Bill. You may be the first to try this version on the Insignia.

He has, I'm trying to figure it out...

Great to see you back in the saddle again. I'd offer to do some testing, but when I dug through my JP1 box, I couldn't find my Insignias. I guess I sold them or gave them away. My daily drivers are all Nevos. Much easier for the family to use something with a display than remember all my cryptic macros. Still think the Insignia is the next best thing.

Like you, I love the quality feel of the Simpleset with its dome contacts. Hope it finds its way to future OFA remotes. Just wish the Simpleset had a few more buttons.

Sorry to get off topic. Back to debugging...

[unclemiltie]

I got a chance to get out my IR widget and IR scope and did some testing with your IR file in my 422-1 (the key labels don't match but who cares)

Anyway, with the delay set at 1.0 second I see both the first and the last key of the macro being sensed by the Ir widget. specifically I see:

Frequency 36857
Protocol Panasonic

First Key Device 176.0, key 75, Hex 2D (which checks with your kermove)
Second key Device 160.28, key 61, Hex 43 (which checks with your device upgrade)


So the extender is playing the macro as you have defined it:

Dev_Dev2,Shift-Power, Phantom 1, Power

I only tested Macro #17 and tested and got the same results with the interruptible pause enabled and disabled.


Something else is going on in your system since the remote is sending the commands specified in the macro. It may be the repeat count or something else so the device is not seeing the commands. Try doubling up the commands (i.e. do Shift-Power twice and Power twice) to see if that makes a difference.

[tranx]

Thanks very much. Have things to do for a couple of days but will come back.

mdavej,
me too. The extra buttons on Insignia/422-2 would make a nice change from OARUSB04/URC6440 and have been looking forward to trying again to get the Extender's pause working with 422-2 because of its backlight

[tranx]

With the trial Common Extender and Inteset-422-2, Pause in those macros is working - doubling the problem command did it. Thanks again.

Haven't done anything to the interruptible pause details or configuration (which is enabled)

[greeno]

is there a way to tell physically if the inteset 422 remote is a 422-1 or 422-2? or does it not matter from the perspective of the common extender?

also where are folks buying them for good prices?

Thanks,
jeff

[unclemiltie]

The signature is the determining factor.

In general, the same signature means the remote has the same firmware in it so the extender will activate and work. The extender has some protection in it to ensure that it is activating on the remote that it expects, although it's minimal.

There is sometimes a difference in the remote models that changes the labels printed on the keys (the best example is the 30853085 remote that comes in the flavor of the Radio Shack 15-133, -134 and -135. Many of the keys have been renamed so there are different RDF's with different tex for key values)

IIRC the Inteset remotes are 3494 and 3565. I don't have one of the 3494 remotes so the support is "in there" but has never been debugged to ensure that it works properly.

[greeno]

thanks unclemiltie.

[sweh]

Please excuse me if I'm being dumb or missed this... I can't seem to get SHIFT keys working.

I have a Time Warner branded 1056B01.
I'm using RMIR 2.06build 2

I did a 981 reset on the remote to clear it.
Downloaded this to RMIR
Then did File->Install Extender -> 3X33-notes.hex
This seemed to go fine.

So now I created a quick'n'simple upgrade for my Sony DVD player. This is a minimum setup as proof of concept.

DVD/1073
Aiwa Protocol 00 5E
Protocol Params 102 0
(resulting in FixedData 66 00)

This had just 3 functions:
Power EFC5=00070
Stop EFC5=00232
Open EFC5=00139

I bound Power to "Power"; "stop" to "stop"
I then bound Open to "Shift+Stop"
For testing, I also bound Open to "Pause"

That's the whole upgrade; nice and simple.

Uploaded, seemed to go fine.
Selected DVD, pressed Power. The player turns on.
Press "pause" and the door opens. This shows the upgrade codes appear to be fine.

But Setup+stop does not close the door.

I tried other shift values (e.g. 53 "On Demand") and these don't seem to work either.

Am I doing something wrong?

[gfb107]

It’s not like a keyboard. There are 2 separate button presses. First press and release setup, then press and release stop.

[mdavej]

I’m not seeing where you activated the extender either.

[sweh]

I’m not seeing where you activated the extender either.

Doh! It's been a long time since I've done this stuff and I forgot that step. Which is silly 'cos I'm used to pressing POWER on my 8811 to active it. Thats why I detailed every step I did. I'll check that tonight when I get home.

Thanks!

[unclemiltie]

I’m not seeing where you activated the extender either.

I'll bet that this is it.

The extender moves the area where key moves are contained and all of the shift-x keys are done as key moves.

So the remote is finding the stuff that is in the upgrade (since that has not moved) but isn't finding anything in the keymove area since it's looking in the wrong place