First Timer Needs Help w/ Power All Off Macro

[mifronte]

Hello.

Just received my cable yesterday. I have been reading and playing with the JP1 software tools the last two weeks waiting for the cable. I have a OFA 9910 remote using extender 1.1.

Please help debug my Power All Off feature. The goal is to power off the current device on a short key press of the Power button and on a long key press, to power off all devices.

The short key press is working, but the long key press has no impact other then the remote LCD changes and the IR light flashes with the remote LCD ending in the TV mode with Code 0000 regardless of what the current device associated with the power button.

Other then that everything works as anticipated.

Here is the URL to my IR file:
http://www.hifi-remote.com/forums/dload ... le_id=4579

Everything appears to work except the Power All off macro on XShift Phantom 3, which is activated by a LKP on the Power button in TV, DVD, AUX and VCR mode.

My current devices:
Sony Grand Wega KDF-E50A10 Rear Projection TV
Denon 2910 DVD Player
Tosibia SD-2109 DVD Player
JVC HR-VP638U VCR

The LKP keymove is as follows: LKP(2) [Short]:Phantom 3 [Long]:XShift Phantom 3.

Phantom 3 is defined to be discrete off for each device.

XShift Phantom 3 has a global macro defined to turn all devices off by calling the respective Phantom 3 (except for TV).

TV uses ToadTog to control power, Shift Phantom 3 to power off, XShift Power to power on.

I have experimented with different LKP timing with no results.

Also,

1. How can my code be more efficient?

2. Based on my IR file, does it look like that I have a correct comprehension of the JP1 framework?

Thank you for your help.

[mifronte]

I was able to get the all devices to power off by directly inserting the global macro on XShift Phantom 3 into the [Long] part of the LKP on the power button for each device mode.

The downside is that I waste a lot of memory because this long macro to power off all devices has to be repeated in each of the LKP on the power button for each device mode. Also it is not too scalable if I have to add a future device, I would exceed the 14 buttons maximum and I would have to modify the code in multiple places.

Any ideas why the global macro on XShift Phantom 3 would not work?

I will try putting the power all off macro on a real button like M3 and try calling that from the LKP on the power button for each device mode.

[Capn Trips]

I will try putting the power all off macro on a real button like M3 and try calling that from the LKP on the power button for each device mode.

I was going to suggest exactly that. Your IR file seems to be OK and "should" work as you describe/intend. I use the 8910/9910 Extender and have no such problems, but perhaps xshift-Phantom 3 is the problem. Another thing to try is to create a keymove placing your x-shift Phantom 3 on a real button (In the NEWEST version of IR, you can keymove a BUTTON rather than just a FUNCTION) and see if the macro runs properly off of x-shift Phantom 3.

[mifronte]

I am tracking the TV power status using ToadTog. I have a Force On and a Force Off as follows:

ToadTog(0, ForceOn) [Already On]:Discrete On [Off->On]:Discrete On; Pause

ToadTog(0, ForceOff) [On->Off]:Discrete Off [Already Off]: Discrete Off

So what is the status of ToadTog immediately after an upload? I suspect it is set to Null because I noticed it behaves erratically initially until it is properly synchronized with the actual TV status.

Can someone confirm? Just trying to identify if this is the expected behavior or I need to track down another bug.

[mifronte]

Moved the global macro to power all devices off from XShift Phantom 3 to L4 (a real button) and everything works as anticipated!

Capn Trips,

I am using IR V7.0. To keymove a button instead of a function, do I just type in the button name (Key Name) instead of the EFC?

[Capn Trips]

Moved the global macro to power all devices off from XShift Phantom 3 to L4 (a real button) and everything works as anticipated!

Capn Trips,

I am using IR V7.0. To keymove a button instead of a function, do I just type in the button name (Key Name) instead of the EFC?

I must be losing my mind, because I distincly recall opening a version of IR recently in which on the Keymove Tab, when you go to "ADD" a keymove, in addition to the "EFC" and "HEX" options, I saw a third - "Button" - option, but it seems to have disappeared.

Sorry about adding to your confusion.

[Capn Trips]

I am tracking the TV power status using ToadTog. I have a Force On and a Force Off as follows:

ToadTog(0, ForceOn) [Already On]:Discrete On [Off->On]:Discrete On; Pause

ToadTog(0, ForceOff) [On->Off]:Discrete Off [Already Off]: Discrete Off

So what is the status of ToadTog immediately after an upload? I suspect it is set to Null because I noticed it behaves erratically initially until it is properly synchronized with the actual TV status.

Can someone confirm? Just trying to identify if this is the expected behavior or I need to track down another bug.

Immediately after upoad, all ToadTog flags are NOT set (or set to 0).

[Mark Pierson]

I must be losing my mind, because I distincly recall opening a version of IR recently in which on the Keymove Tab, when you go to "ADD" a keymove, in addition to the "EFC" and "HEX" options, I saw a third - "Button" - option, but it seems to have disappeared.

You're not losing your mind (at least not yet)... the "Key" option is available in the key move dialog on many of the newer remotes (i.e. those that use 5-digit EFC's).

[Capn Trips]

I must be losing my mind, because I distincly recall opening a version of IR recently in which on the Keymove Tab, when you go to "ADD" a keymove, in addition to the "EFC" and "HEX" options, I saw a third - "Button" - option, but it seems to have disappeared.

You're not losing your mind (at least not yet)... the "Key" option is available in the key move dialog on many of the newer remotes (i.e. those that use 5-digit EFC's).

Why does IR discriminate against us 3-digit EFC remote users?

[Mark Pierson]

Why does IR discriminate against us 3-digit EFC remote users?

It doesn't really... the key move formats are slightly different in the newer models.

[Capn Trips]

Well, back to the original thread:

Moved the global macro to power all devices off from XShift Phantom 3 to L4 (a real button) and everything works as anticipated!

In the interest of research, how about if you now take the xsihft-Phantom 3 button and assign to it a 1-button macro consisting of L4 and see if xshift-Phantom 3 works in your LKPs?

Now if you want to preserve the "real" L4 button for some other "real" use, try putting that macro sequence on OTHER imaginary buttons (like xshift-L4) and see if it works.

If it does, then I suspect that you have likely uncovered a bug in the 9910 extender rdf which presumes that xshift-Phantom 3 is available when in fact it is not, or something like that. An expert, or the extender writer would likely have to get involved at that point, but as a minimum, perhaps one could identify a range of buttons that although seemingly available, do not work in the extender.

[ElizabethD]

If it does, then I suspect that you have likely uncovered a bug in the 9910 extender rdf which presumes that xshift-Phantom 3 is available when in fact it is not, or something like that.

I thought this sounded vaguely familiar but couldn't remember ...
So start about here:
http://www.hifi-remote.com/forums/viewt ... 9013#39013

[Capn Trips]

WOW Liz!

Good memory to dig that one up from a year and a half ago!

So, mifronte, obviously xshift-Phantom 3 cannot be used in the 8910/9910 extender as I myself discovered over a year ago . Obviously you should have done a better job reading the forums before posting such a silly question

[ElizabethD]

Obviously you should have done a better job reading the forums before posting such a silly question

... and besides that cool advice you'd have to imagine it just might be inside a 6131 thread
LOL

I just tacked on a note in the extender files section

[mifronte]

Thanks ElizabethD for that thread. It explains the weird behavior that I was getting. I guess I just missed it since the subject of that thread would not have alerted me to the problem given I was using the OFA 9910 instead of the 6131.

Capn Trips,

Would you know what the duration/threshold values in the LDKP translates to in milliseconds for the OFA 8910/9910 remote? I am using the threshold value of 2, but feel that it may be a little to long.

Also can someone explain what is the purpose of holding down a button in relation to the last step of a macro? I noticed it mentioned a few times on this forum, but was too much of a newbie for any of the information to register.