JP1 Remotes

Another approach I've seen (and even used) is to simply leave the Satellite or Cable box on all of the time. You should check, but in most cases, particularly if it's a DVR box, the box does not actually turn "Off" but goes into "Standby" and the power consumption in "Standby" is virtually the same as when the box is "On" so you gain nothing by turning it "Off".

It goes against any ideas of being ecologically prudent, but it may in fact make no difference.

What a great group you are! If I could take all of the hints, suggestions, and tips found on this JP1 site, I could fill a "JP1 for Dummies" book. Thanks again.

Richard

greenrl,
I had some time on my hands this morning, and took a look at your setup.
This is the one from 4 days ago, so you may have changed this some since then.

One thing that struck me right off the bat is you are hardly using any punch through either with keymoves or with your setup macros.

One of the best features with these remotes is the ability to add punchthrough so that you don't have to be constantly changing back and forth between modes.

For example
I see that your TV is a wide screen, I just got one myself, and I know that I couldn't function without having the aspect mode available in all modes.
I do this by adding keymoves to the various modes.

Also for volume punch through, do you really have that many items that use their own volume selectors?

1 AUD V_AUD
2 AUX1 V_AUX
3 AUX2 V_AUX2
4 CD V_TV
5 SAT V_SAT
6 CBL V_TV
7 DVD V_AUD
8 PVR V_TV
9 TV V_TV
10 VCR uses last selected

Does your TV really have its own Transport keys, or should thouse be left to use last selected too.

But on to your problem with the discrete on/off not working right for CBL

Here is your discrete on for Cbl

8
CBL SHIFT-Up ToadTog(0,ForceOn)
[Already On]:X_CBL;Phantom1
[Off->On]:
X_CBL;
Phantom1;
X_CANCEL;
X_CBL;
Phantom1

I don't have a clue as to why there is a x_cancel, X_cable in the middle of the off side, but that is not going to buy you any time. If you are trying to deal with a duration problem, you might want this side to be Phantom1,phantom1, phantom1, phantom1 because x_cancel,x_cbl is a very tiny delay, probably not enough to do anything for you.

However, I think if this were my problem macro that I'd switch things around so that the CBL on was the very last thing that was going on so that the CBL-Phantom1 on would be the last thing in the macro so that you can use the actual button hold to control the duration, but with that 15 seconds you need for your TV to accept the input, this doesn't seem reasonable.

vickyg2003 wrote:greenrl,

One thing that struck me right off the bat is you are hardly using any punch through either with keymoves or with your setup macros.

One of the best features with these remotes is the ability to add punchthrough so that you don't have to be constantly changing back and forth between modes.

I don't use a punch through because your Readme.htm states that "There is no VPT".

vickyg2003 wrote: For example
I see that your TV is a wide screen, I just got one myself, and I know that I couldn't function without having the aspect mode available in all modes.
I do this by adding keymoves to the various modes.

Thankfully the Sammy remembers the last aspect ratio used for a given input.

vickyg2003 wrote: Also for volume punch through, do you really have that many items that use their own volume selectors?

1 AUD V_AUD
2 AUX1 V_AUX
3 AUX2 V_AUX2
4 CD V_TV
5 SAT V_SAT
6 CBL V_TV
7 DVD V_AUD
8 PVR V_TV
9 TV V_TV
10 VCR uses last selected

Some of these are in the default key macros that the extender adds when merged with the upgrade. I have just not bothered to remove the ones not used. The AUD, CD, CBL, DVD, PVR, and TV are what I need for my setup.

vickyg2003 wrote:But on to your problem with the discrete on/off not working right for CBL

Here is your discrete on for Cbl

8
CBL SHIFT-Up ToadTog(0,ForceOn)
[Already On]:X_CBL;Phantom1
[Off->On]:
X_CBL;
Phantom1;
X_CANCEL;
X_CBL;
Phantom1

I don't have a clue as to why there is a x_cancel, X_cable in the middle of the off side, but that is not going to buy you any time. If you are trying to deal with a duration problem, you might want this side to be Phantom1,phantom1, phantom1, phantom1 because x_cancel,x_cbl is a very tiny delay, probably not enough to do anything for you.

OK I understand what you are saying...but many tests have demonstrated to me that the way I have it is the only way I can get the Dish508 to turn on reliably every time. I have tried the 4 Phantom1 discretes in a row and it did not work.

I know that the discrete codes work outside of the extender by entering shift 00xxx codes as does the normal power button.

vickyg2003 wrote: However, I think if this were my problem macro that I'd switch things around so that the CBL on was the very last thing that was going on so that the CBL-Phantom1 on would be the last thing in the macro so that you can use the actual button hold to control the duration, but with that 15 seconds you need for your TV to accept the input, this doesn't seem reasonable.

If I place the CBL-Phantom1 last in the macro, the Dish 508 will not turn on.

The really befuddling characteristic is that if the CBL macro is run first from a cold start, the Dish508 turns on every time. If the very same macro is run after the TV macro, the Dish508 does not turn on. This must indicate a complete misunderstanding on my part of how the extender works.

Taking jimdunn's advice, I have posted a "baby steps" IR file with only the TV and CBL macros. It operates the same way as the full file.
http://www.hifi-remote.com/forums/dload ... le_id=9470

This has just about evolved into an academic exercise. I am about ready to toss in the towel and use Capn Trips "always on" philosophy since the WAF factor is dropping.

The really befuddling characteristic is that if the CBL macro is run first from a cold start, the Dish508 turns on every time. If the very same macro is run after the TV macro, the Dish508 does not turn on. This must indicate a complete misunderstanding on my part of how the extender works.

Hmmmm I've played the macro from a cold start and from a cold start after the TV button was played, and both times it sends out

Dish_Network 0.7 1 07
Dish_Network 0.7 1 07

Which should be two power on commands.

Are you sure dishnetwok is not turning on? It could be that the TV isn't switching to the input?

I may be confused here, but it still seems to me you have an unnecessary set of ToadTogs for the CBL device.

You are tracking the TV power state in a ToadTog, so that you can conditionally pause if the TV is starting from cold - fair enough...

But for the CBL, you are using a ToadTog, and sending a discrete on command (Phantom1) from within the ForceOn.

You don't seem to be making any "decisions" based on the power state of CBL, so why are you tracking its power state at all ?

Just sending Discrete On/Off power commands seems to be all you need to do for CBL - that's the point of Discretes - if its already On, discrete On will have no effect, but if its off, Discrete on will turn it on (and vice versa for Discrete Offs) - all without any ToadTogs.

I don't know if that's going to solve your problem - probably not, since Vicky has looked at the actual output, and the Phantom1 seems to get sent OK in both cases, but it does seem to be an unnecessary, potentially error prone layer of confusion/complication - unless I'm missing the reason you need to track CBL power state.

Yes, I know the Dish does not turn on because there is a power LED on the front panel and the TV is on the s-video input.

I have no way to tell what the remote is sending out.

As I say, it is befuddling. And YMMV.

jimdunn,

At this point, the only reason I am using the TT for the Dish force on is because after many many tries to use only the discrete on in this scenario have failed and only the TT turns it on in the extender. Go figure!

Gotta run, be back later.

Richard

In that case, I don't know what is going on, sorry.

Vicky has determined that the remote is sending the signal - so it should be working.

Confusingly, if I'm reading it right, it seems to be that this signal just doesn't work when the TV is already on?

If that's not right - don't even read the probable nonsense below...


If that is so, and because this is starting to look so odd and unpredictable,
Here's a really off the wall suggestion:
Physically unplug the TV power so that it can't power on - then try both scenarios of running the macros again.

There was a situation in Australia where one of the Satellite providers released a box which had endless remote control problems for some buttons for some users - turned out in the end that some models of flat screen TVs were interfering with some of the infra red signals.

This is so unlikely to be related to your problem that I hesitate even to mention it - but at least this test would be quick and easy.

Well I do have a way to see what you are sending. I have the widget preAND your remote.

I was looking at the previous IR file you posted.

I can see that the power command is being sent two times.

My one question would be if this long LED hold for the 30 second pause might be depleating your battery, givng you a low-voltage reset. You might want to check to see if the IR is being emitted when you press the CBL key. Check through the view finder of a digital camera and see if you are getting a flash. (the phone camera will do)

Oh and I really like Jim Dunn's idea! We've seen that before on certain models of TV's

vickyg2003 wrote: Oh and I really like Jim Dunn's idea! We've seen that before on certain models of TV's

No - mine is very speculative and unlikely.

Of the 2, my money would be on your theory, because if TV is resetting the remote due to the long pause, then presumably that could drop it out of the extender too - hence the CBL macro wouldn't work. Much more likely - but not something that would have occurred to me, especially since I haven't played the macros and watched the 30 second LED glare at me

jimdunn wrote:No - mine is very speculative and unlikely.

Not really, if you google "tv interferes with remote" you'll get pages and pages of complaints. and the first few are about Samsungs and DishTV, so my money is on your idea!

Hmmm, veddy interesting....
I will have to run the experiment with TV unplugged.

Yippee! Problem solved. Works perfectly with the TV unplugged.

Now the question is "What to do about it"? Who wouldda thunk?:lol:

Richard

Solutions include masking tape over the Dish IR window (acts like a filter), changing backlight setting on your TV or relocating your Dish box so it isn't awash with IR noise from your screen.