Separate names with a comma.
Discussion in 'TiVo Underground' started by Omikron, Apr 30, 2008.
Anyone know if there is a code for closed captioning?
So this doesnt void the warranty or anything?
Not a direct code, no.
I don't see how since you're not even opening the box...
I tried copy and pasting
to toggle CC, however once it gets to the menu screen, it ignores the rest of the commands. i suppose they just get dropped.
i suppose if a program was written, it could be delayed pretty easily.
Yeah, it's definitely a timing issue.
I'd try simpler things, such as "KEYBOARD T", "KEYBOARD 84" (ASCII base10), "KEYBOARD 54" (ASCII hex), "KEYBOARD 0x54"
I made all the commands into a txt file and can just mark/copy from notepad and then right-click in the telnet window from XP to paste. Works faster than I can type.
Cool stuff. Great discovery, Omikron.
So wierd. I wonder why 'nc' isn't working.
edit: oh, btw, it doesnt lock up my UI, though
It doesn't lock up using telnet app, only when I tried it using NetTerm.
On the CH_STATUS <CHANNEL> <STATUS> message...
Rather than <STATUS> indicating the type of tuner, it would appear that <STATUS> indicates the "who done it". (<REASON>?)
REMOTE = because of an IR code received (either through the IRCODE command or from actual IR)
LOCAL = because of something local inside the device itself (First connect, SETCH, switch from any of the Tivo screens to LiveTV)
RECORDING = because we're recording something
If this is true, there's still no decent status indication of which tuner is actually doing what. Having a "STATUS" command to send to Tivo would be REALLY nice
That doesn't seem to be supported by what I've seen. If I monitor the status screen and change channels via the TiVo remote the status remains LOCAL. What have you seen that leads you in this direction?
The SETCH always returns LOCAL. IRCODE always returns REMOTE. Both seem to always change the tuner that I'm watching.
Edit: OK, scratch that. SETCH just returned REMOTE.
I was watching the primary tuner and recording something on it. SETCH switched the tuners and returned REMOTE. So now I'm watching the remote tuner. Hmmm...
Edit2: SETCH again still returns REMOTE now. IRCODE CHANNELUP returns LOCAL, but I'm still watching the same tuner. Uhhhh?
Then perhaps there is still no clear-cut definition. :-/
Regardless of what the second parameter in the response means, what's clear is that this is an absolutely EXCELLENT find!!
This is going to make my Pronto 9600 soooo much better!
Here's my first stab at a simulated remote... a Python app that requires GTK. Currently, you have to edit it to set TIVO_ADDRESS manually, and only IRCODE commands are supported.
This still needs a lot of work, but if people are cutting and pasting into a telnet app, I figure this is an improvement.
[See sig for the latest version.]
I seem to have an issue on my HD; The commands seem to work and I get feedback from SETCH and IRCODE that seem appropriate, but that is followed about 2 seconds later by a "command timeout" message.
I do an "open" and immediately see "CH_STATUS 0841 LOCAL"
I then enter SETCH 0840 I first see "CH_STATUS 0840 REMOTE", then that is overwritten by "COMMAND_TIMEOUT".
I've tried both the Vista Telnet client and PuTTY. With PuTTY I tried both raw mode and TelNet.
I'm presuming the ENTER key is the appropriate key to send a command, yes?
You have to type fast. If you get COMMAND_TIMEOUT you need to start over typing your command again.
I am pasting the copmmands into the telnet client window and hitting enter. The commands are executing, for example, I get the ch_status if I do an up or down channel ircode command. It is after that acknowledgment that I am getting the timeout.