| Author |
Message |
|
poflynn
|
 Posted: Wed Oct 31, 2007 1:03 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
|
Interesting thread. Note that everyone everywhere has trouble learning this remote. Unfortunately I know nothing about this stuff other than the basics but surely someone could translate these working codes from other apps to lirc...
_________________
Paul O'Flynn
|
|
| Top |
|
 |
|
resmaker
|
Posted: Thu Nov 01, 2007 2:48 pm |
|
|
Joined: Wed Jul 04, 2007 4:21 pm
Posts: 8
|
|
I guess my question is what do the # values need to represent
So if I have 123 frequecy do we need to convert to 456 inside LIRC to get it to work.
What # system does LIRC use. Hex / Binary(doubtful) / Proprietary?
I too will be very stuck soon if I don't come up with a solution for the IR codes.
I really wish that stupid USB port on the front did something.
OR
They put a Firewire(IEEE-1394) port on this stupid box. DAMN THEM.
I also wonder if their would be a way to tap into the ethernet(cat-5) to send channel switching data. I guess I could port sniff to see what happens but once I got the information I don't have enough experience to do anything with it.
ARRRRGH - I love the cost and channel selection. I am starting to hate AT&T with my MythTV box.
|
|
| Top |
|
|
|
poflynn
|
Posted: Thu Nov 01, 2007 4:08 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
resmaker wrote: I guess my question is what do the # values need to represent
So if I have 123 frequecy do we need to convert to 456 inside LIRC to get it to work.
What # system does LIRC use. Hex / Binary(doubtful) / Proprietary?
This is essentially the question I posed to the thread above. I doubt I'll get an answer. I googled around a bit and there's no easy way to convert the #s between these apps.. resmaker wrote: I also wonder if their would be a way to tap into the ethernet(cat-5) to send channel switching data. I guess I could port sniff to see what happens but once I got the information I don't have enough experience to do anything with it. Don't bother - it's all encrypted/DRM'ed data. resmaker wrote: ARRRRGH - I love the cost and channel selection. I am starting to hate AT&T with my MythTV box.
There's no question that AT&T (and all other cos going fwd) are going to do their best to not make this easy, so get used to it. How frustrating that the biggest problem everyone has with this service is the damn remote, esp. ironic as the box is Windoze-based and thus the remote is already learned by some app somewhere... I also surprised that these Pronto, Tivo & other users have all managed to crack it but no one has yet, or even tried much, for lirc.
Grrrr
_________________
Paul O'Flynn
|
|
| Top |
|
|
|
resmaker
|
Posted: Fri Nov 02, 2007 1:02 pm |
|
|
Joined: Wed Jul 04, 2007 4:21 pm
Posts: 8
|
|
If they have the codes then someone must make a conversion utility to make it LIRC.
If I get a chance I will do some research in that direction.
Thanks for the Ethernet info - I have an HDHomerun so I know all about encrypted channels. I wasn't trying to splice into the stream but instead send a change channel message similar to the IR remote. The IR remote send the command then the box sends the command back to AT&T and the stream changes.
I need to order my USB IR blaster soon. Once I get that I will try to do some testing as well. This will stink if I can not get the IR codes to work.
I still love my MythTV especially when I use the AT&T Uverse as a comparison. I watch recorded and live TV now remotely on my PC from my MythTV. Good Luck getting any big corp to give up that much control.
|
|
| Top |
|
|
|
poflynn
|
Posted: Tue Nov 06, 2007 11:25 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
So, it seems it can be done using the Hauppauge 150 & its blaster.
http://www.uverseusers.com/component/op ... ic,3867.0/
Unfortunately I have a 150MCE, arrgh! Still, I guess I'll just have to buy yet another card....
Still looking for a 'normal' lirc solution...
Paul
_________________
Paul O'Flynn
|
|
| Top |
|
|
|
resmaker
|
Posted: Wed Nov 07, 2007 2:35 pm |
|
|
Joined: Wed Jul 04, 2007 4:21 pm
Posts: 8
|
|
So I am having issues with my AT&T supplied DVR - usually 3 reboots a week and yesterday I had to reboot 3 times to watch the last 10 minutes of a show.
So I decided to call AT&T tech support and ask them for help on this IR code issue.
Me -'What are the IR codes for this remote'
Them - 'Use 955'
Me - 'Oh sorry, I meant what are the frequencies the remote is sending out my DVR is having a hard time learning the buttons'
Them - 'Why would the DVR not work with your remote maybe you need another remote'
Me - 'Not your DVR, my Tivo(like) DVR so I can turn or change channels with that'
Them - 'Wait I will need to get you to level 2'
At level 2 I had almost the same conversation and it ended with 'I don't know'
So that is that.
This was way funnier in person and I was much more frustrated by the end of the call with the first tech. The first tech relayed the information to the second so well that he started with you should use 955 for your remote. I said,'I don't think they explained my problem correctly'
What options are their for changing the channel from MythTV via the IR blaster, I know that I could use LIRC. What other ways can I do it? I have a PVR-350 could that help?
I am getting a USB IR Blaster soon, hopefully it will learn the codes or I can find a person that has learned the AT&T codes for it.
|
|
| Top |
|
|
|
poflynn
|
Posted: Thu Nov 08, 2007 1:29 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
resmaker wrote: So I am having issues with my AT&T supplied DVR - usually 3 reboots a week and yesterday I had to reboot 3 times to watch the last 10 minutes of a show.
I have heard stories like this, mine isn't near this bad. resmaker wrote: What options are their for changing the channel from MythTV via the IR blaster, I know that I could use LIRC. For this STB? None, and no, lirc is not an option, at the moment, due to the lack of a config file for this remote/STB. That was the whole point of this thread. resmaker wrote: What other ways can I do it? I have a PVR-350 could that help?
Does it come with an IR Blaster? I don't think so, if not, then it is of no use in controlling this STB. resmaker wrote: I am getting a USB IR Blaster soon, hopefully it will learn the codes or I can find a person that has learned the AT&T codes for it.
No & no, sorry.
_________________
Paul O'Flynn
|
|
| Top |
|
|
|
bobmyth
|
Posted: Thu Nov 08, 2007 7:42 pm |
|
|
Joined: Wed Jan 18, 2006 8:36 pm
Posts: 199
|
|
| Top |
|
|
|
poflynn
|
Posted: Thu Nov 08, 2007 10:46 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
bobmyth wrote: This article will show you how to convert from pronto to lirc: http://www.n8gray.org/blog/2007/01/28/pronto-to-lirc/Thanks for the link. That article seems to assume that you can capture at least one code from the remote in non-raw format using irrecord, which I can't  Interestingly it did cause me to search remotecentral.com (again) and just less than a week ago someone posted a ccf file for this remote on there! http://www.remotecentral.com/cgi-bin/fi ... ip1200.zip
Still, it's a bit frustrating that I have these 'other' config files but still can't get an lirc file from them. Also a bit surprising to me that lirc seems to be the last app to get a config file.
BTW I did install Tonto etc and below is my screenshot, note that it doesn't even have a hex value. There sure does seem to be something special about this remote
_________________
Paul O'Flynn
|
|
| Top |
|
|
|
poflynn
|
Posted: Thu Nov 15, 2007 6:24 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
poflynn wrote: So, it seems it can be done using the Hauppauge 150 & its blaster.
Paul Just wanted to confirm to everyone that I got this working using the 150 & its built-in blaster, lircd.conf below. Shame I needed to buy a new card for this. Paul Quote: # # this config file was automatically generated # using lirc-0.5.5pre8 on Sun Apr 18 11:43:45 1999 # # contributed by Jens Leuschner <leuschner@gmx.net> # # brand: Hauppauge # model: # supported devices: WinTV primo; WinTV pci; WinTV radio # # This config file will work with both homebrew receivers and # original Hauppauge TV cards !!! # begin remote name blaster bits 32 flags RAW_CODES eps 0 aeps 0 plead 0 gap 333333 repeat_bit 0 begin raw_codes name 0 8519680 name 1 8519681 name 2 8519682 name 3 8519683 name 4 8519684 name 5 8519685 name 6 8519686 name 7 8519687 name 8 8519688 name 9 8519689 name POWER 8519690 name CH_UP 8519695 name CH_DOWN 8519696 name KEY_MUTE 8519697 name VOL_DOWN 8519698 name CH_PREVIOUS 8519699 name VOL_UP 8519700 name DISPLAY 8519701 name MNSELECT 8519703 name EXIT 8519704 name GUIDE 8519707 name ENTER 8519723 name MENU 8519727 name MUP 8519728 name MDOWN 8519729 name MLEFT 8519730 name MRIGHT 8519731 name FF 8519732 name PLAY 8519733 name REW 8519734 name REC 8519735 name PAUSE 8519736 name STOP 8519737 end raw_codes end remote begin remote name Hauppauge bits 13 flags SHIFT_ENC eps 30 aeps 100 one 950 830 zero 950 830 plead 960 gap 89584 repeat_bit 2 begin codes TV 0x000000000000100F RADIO 0x000000000000100C FULL_SCREEN 0x000000000000102E CH+ 0x0000000000001020 CH- 0x0000000000001021 VOL- 0x0000000000001011 VOL+ 0x0000000000001010 MUTE 0x000000000000100D SOURCE 0x0000000000001022 1 0x0000000000001001 2 0x0000000000001002 3 0x0000000000001003 4 0x0000000000001004 5 0x0000000000001005 6 0x0000000000001006 7 0x0000000000001007 8 0x0000000000001008 9 0x0000000000001009 0 0x0000000000001000 RESERVED 0x000000000000101E MINIMIZE 0x0000000000001026 end codes end remote # # this config file was automatically generated # using lirc-0.6.6(animax) on Tue Apr 15 19:50:27 2003 # # contributed by # # brand: Hauppauge # model no. of remote control: # devices being controlled by this remote: PVR 2/350 # begin remote name hauppauge_pvr bits 13 flags RC5|CONST_LENGTH eps 30 aeps 100 one 969 811 zero 969 811 plead 1097 gap 114605 toggle_bit 2 begin codes Power 0x00000000000017FD Go 0x00000000000017FB 1 0x00000000000017C1 2 0x00000000000017C2 3 0x00000000000017C3 4 0x00000000000017C4 5 0x00000000000017C5 6 0x00000000000017C6 7 0x00000000000017C7 8 0x00000000000017C8 9 0x00000000000017C9 Back/Exit 0x00000000000017DF 0 0x00000000000017C0 Menu 0x00000000000017CD Red 0x00000000000017CB Green 0x00000000000017EE Yellow 0x00000000000017F8 Blue 0x00000000000017E9 Ch+ 0x00000000000017E0 Ch- 0x00000000000017E1 Vol- 0x00000000000017D1 Vol+ 0x00000000000017D0 Ok 0x00000000000017E5 Mute 0x00000000000017CF Blank 0x00000000000017CC Full 0x00000000000017FC Rewind 0x00000000000017F2 Play 0x00000000000017F5 Forward 0x00000000000017F4 Record 0x00000000000017F7 Stop 0x00000000000017F6 Pause 0x00000000000017F0 Replay 0x00000000000017E4 Skip 0x00000000000017DE end codes end remote # # this config file was automatically generated # using lirc-0.7.0(any) on Sun Nov 28 20:25:09 2004 # # contributed by # # brand: Hauppauge 350 # Created: G.J. Werler (The Netherlands) # Project: Mythtv Fedora Pundit-R www.mythtvportal.com# Date: 2004/11/28 # model no. of remote control: Hauppauge A415-HPG # devices being controlled by this remote: PVR-350 # begin remote name Hauppauge_350 bits 13 flags RC5|CONST_LENGTH eps 30 aeps 100 one 969 811 zero 969 811 plead 1097 gap 114605 # gap 200000 toggle_bit 2 begin codes Go 0x00000000000017BB Power 0x00000000000017BD TV 0x000000000000179C Videos 0x0000000000001798 Music 0x0000000000001799 Pictures 0x000000000000179A Guide 0x000000000000179B Radio 0x000000000000178C Up 0x0000000000001794 Left 0x0000000000001796 Right 0x0000000000001797 Down 0x0000000000001795 OK 0x00000000000017A5 Back/Exit 0x000000000000179F Menu/i 0x000000000000178D Vol+ 0x0000000000001790 Vol- 0x0000000000001791 Prev.Ch 0x0000000000001792 Mute 0x000000000000178F Ch+ 0x00000000000017A0 Ch- 0x00000000000017A1 Record 0x00000000000017B7 Stop 0x00000000000017B6 Rewind 0x00000000000017B2 Play 0x00000000000017B5 Forward 0x00000000000017B4 Replay/SkipBackward 0x00000000000017A4 Pause 0x00000000000017B0 SkipForward 0x000000000000179E 1 0x0000000000001781 2 0x0000000000001782 3 0x0000000000001783 4 0x0000000000001784 5 0x0000000000001785 6 0x0000000000001786 7 0x0000000000001787 8 0x0000000000001788 9 0x0000000000001789 Asterix 0x000000000000178A 0 0x0000000000001780 # 0x000000000000178E Red 0x000000000000178B Green 0x00000000000017AE Yellow 0x00000000000017B8 Blue 0x00000000000017A9 end codes end remote
_________________
Paul O'Flynn
|
|
| Top |
|
|
|
poflynn
|
Posted: Mon Nov 26, 2007 3:06 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
Good news folks,
A user on the Nabble/lirc mailing list has cracked this difficult remote. Below is the lircd.conf, should work with the serial blaster from irblaster.info. Shame I was just a wee bit too early, could have saved me hours of work & $60 on a card which I now no longer need. Still, shan't complain, I still have an FE to get running on this....
All credit goes to "Greg P" on Nabble!
Paul
Code: begin remote
name vip1200
bits 32
flags RCMM|CONST_LENGTH
eps 2
aeps 100
header 417 278
three 167 778
two 167 611
one 167 444
zero 167 278
ptrail 167
gap 99817
toggle_bit_mask 0x8000
begin codes
ZERO 0x23402600
0 0x23402600
ONE 0x2340A601
1 0x2340A601
TWO 0x23402602
2 0x23402602
THREE 0x2340A603
3 0x2340A603
FOUR 0x23402604
4 0x23402604
FIVE 0x2340A605
5 0x2340A605
SIX 0x2340A606
6 0x2340A606
SEVEN 0x2340A607
7 0x2340A607
EIGHT 0x23402608
8 0x23402608
NINE 0x2340A609
9 0x2340A609
LAST 0x2340260A
POWER 0x2340A60C
INFO 0x2340260F
CHPG+ 0x2340A620
CHPG- 0x2340A621
FF 0x23402628
REW 0x2340A629
PLAY 0x2340262C
PAUSE 0x23402630
STOP 0x2340A631
RECORD 0x23402637
A 0x2340A638
B 0x2340A639
RECORDEDTV 0x23402644
FWD 0x2340A64C
REPLAY 0x2340264D
MENU 0x2340A654
EXIT 0x2340A655
UP 0x2340A658
DOWN 0x23402659
LEFT 0x2340A65A
RIGHT 0x2340A65B
OK 0x2340A65C
BACK 0x2340A683
C 0x2340A686
DELETE 0x2340A69E
TVVIDEO 0x234026A8
GUIDE 0x234026CC
ENTER 0x234026E1
VIDEOONDEMAND 0x2340A6F0
gointeractive 0x2340A6FD
end codes
end remote
_________________
Paul O'Flynn
|
|
| Top |
|
|
|
kingtj
|
Posted: Thu Apr 03, 2008 9:50 am |
|
|
Joined: Mon Sep 20, 2004 4:49 pm
Posts: 26
Location:
St. Louis, MO (USA)
|
|
I just signed up for AT&T U-Verse last weekend at my house, and have been working on making my MythTV (R5F27) work properly with it.
I have a PVR-250 card working with the configuration for the grey/silver Hauppage remote on its IR receiver (actually using a Logitech Harmony remote control set to emulate the Hauppage remote though, since the original remote has been lost).
That part works great. But after setting up the irblaster (2nd. copy of lircd) to use the codes provided in this message thread, and configuring it to use COM1 with a home-brew IR sender cable, I'm having some problems.
Data is definitely being sent to the U-Verse VIP1200 box, but it seems like it always misses digits. I've tried moving the LED further away from the box, and right up against it on the front, right-hand side (isn't that where its IR receiver is located?).
Typically, if I send a channel change to a 2 or 3 digit channel starting with 1, it immediately goes to channel 1 - the "on demand video" screen, and is stuck there until I use the U-Verse remote to bail it back out to "live TV" mode again!
With a shorter delay in the channel_change.sh script, it seemed like it started ignoring the first digit sent in any channel change request, but captured the remaining digits properly.
What delay value are people using who have this working properly?
|
|
| Top |
|
|
|
poflynn
|
Posted: Sat Apr 05, 2008 9:00 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
My script is below. I have two VIP1200s hooked to my MBE, one is changed using the built-in IR blaster of the 150 & the other is being changed using a serial blaster. Both work fine using the same delay as below.
My blasters are taped directly on to the RHS of the STB, just to he right of the 'Record' LED & label.
Best of luck,
Paul
Quote: #!/bin/sh
REMOTE_NAME=VIP1200
cmd="$1"
case $cmd in
[0-9]*)
for digit in $(echo $1 | sed -e 's/./& /g'); do
irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME $digit
sleep 0.3
# If things work OK with sleep 1, try this for faster channel changes:
# sleep 0.3
done
;;
*)
irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME $cmd
;;
esac
irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME ENTER
_________________
Paul O'Flynn
|
|
| Top |
|
|
|
kingtj
|
Posted: Sun Apr 06, 2008 2:25 pm |
|
|
Joined: Mon Sep 20, 2004 4:49 pm
Posts: 26
Location:
St. Louis, MO (USA)
|
Thanks for the response!
I discovered I was wrong about where the IR receiver was located on the VIP 1200 box. Like you said, it's more towards the front, middle of the unit than all the way over on the right-hand side. I also had to put my LED right up against the box to get good results. It was always missing digits when I moved it a few inches away.
It's good to know the sleep 0.3 statement is working for you though. That's what I went with too. I also added an irsend command to my script to send the "ENTER" button after a channel change is sent, to make sure it knows the sequence of digits is finished.
All is working well now!
poflynn wrote: My script is below. I have two VIP1200s hooked to my MBE, one is changed using the built-in IR blaster of the 150 & the other is being changed using a serial blaster. Both work fine using the same delay as below. My blasters are taped directly on to the RHS of the STB, just to he right of the 'Record' LED & label. Best of luck, Paul Quote: #!/bin/sh
REMOTE_NAME=VIP1200
cmd="$1"
case $cmd in
[0-9]*)
for digit in $(echo $1 | sed -e 's/./& /g'); do
irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME $digit
sleep 0.3
# If things work OK with sleep 1, try this for faster channel changes:
# sleep 0.3
done
;;
*)
irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME $cmd
;;
esac
irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME ENTER
|
|
| Top |
|
|
|
poflynn
|
Posted: Mon May 26, 2008 10:51 pm |
|
|
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location:
CA,USA
|
I'm sure any AT&T uverse users out there will have noticed by now that there's a new 'feature' - namely the STB will turn itself off after a period of inactivity (defined by lack of keypresses). This is bad for us of course. Well, using the serial port 'home brew' IR blaster I got it to work by modifying the /usr/local/bin/change-channel-lirc.sh script file as follows:
Quote: REMOTE_NAME=VIP1200
cmd="$1"
# POF Added to turn on STB in case it is off.
irsend --device=/dev/irblasterd SEND_ONCE $REMOTE_NAME OK
sleep 1.3
# POF End
case $cmd in
[0-9]*)
........... etc etc etc
Note the two new lines. I tried 'sleep 0.3' & it didn't work, neither did 'sleep 1' but 1.3 did seem to work.
So, basically now it presses 'ok' before it begins to change the channel, seems to work. Slows down the channel changing but honestly it was very slow already, too slow for channel surfing, but I never watch live TV anyway so that's not a problem for me.
However I still have a problem: I have two STBs connected to my BE. One gets its channels changed as above but the other uses the built-in IR blaster of the 150 card. Unfortunately the lircd.conf file I have for that (as retrieved from this famous blog posting http://www.blushingpenguin.com/mark/blog/?p=24&cp=13) does not include a code for the 'ok' button so I cannot send such a cmd. I'm sure others out there use this IR blaster, maybe you have an idea... Sending 'power' is risky as if it's already on it will now turn off, 'ok' will have no affect on its own if the STB is on...
Suggestions?
_________________
Paul O'Flynn
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
