<div class="gmail_quote">On Tue, May 4, 2010 at 8:01 PM, M.A.E.M. Hanson <span dir="ltr"><<a href="mailto:hansonorders@verizon.net" target="_blank">hansonorders@verizon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Interesting theory. If true though (that is, if there is video of a<br>
screen saver being output), how come my HD-PVR records a 0-length<br>
file when the box is pseudo-off? I don't have my box hooked directly<br>
to a tv, so I can't test to see if this is true for my STB. Hm, I<br>
wonder if this is a setup/configuration option?<br>
<br>
Can you point me at info about how to send a MENU command? I'd be<br>
happy to mod 6200ch if I understood the protocol.<br>
</blockquote>
<br></div>
I'm at a loss for why your HD-PVR records zero bytes. Maybe I'm way off<br>
in my line of thinking? I tested my QIP-6200 (remotely via ssh and VNC)<br>
a little while ago and I found that if the menu is on (that is, the box<br>
is "off"), the channel change via 6200ch fails, but recordings via the<br>
HD-PVR still record--they just record the screen saver. I put together<br>
a quick and dirty patch for 6200ch that adds support for the "-q" switch<br>
that sends the ROOT_MENU command to the QIP-6200. You can find it here:<br>
<br>
<a href="http://tinyurl.com/27q42v8" target="_blank">http://tinyurl.com/27q42v8</a><br>
<br>
This is against the 6200ch.c posted on the wiki. Apply and recompile.<br>
I tested it and it does indeed send the correct MENU command to the STB.<br>
However, I have not worked out a way to have it detect that the MENU<br>
command needs to be sent.</blockquote><div><br></div><div>I guess it would have to be either different firmware (is your STB from Verizon?) or differently configured setup options. Unfortunately I don't have a tv near the STB where it is now, so it's a little difficult to check the options or the firmware version. The good news is, the ROOT_MENU command does indeed turn "power" on, as opposed to toggling it! Thanks for that, should solve most of the problem. Too bad I can't get a reliable status back.</div>
<div><br></div><div>So the subunit type of "panel" seems to be the way to invoke the remote or front-panel buttons. I tried playing around with some different subunit commands with the STB on the off mode, but I couldn't effect a change in the reported status.</div>
<div><br></div><div>-Jerry</div>
</div>