From: Brian J. M. <br...@in...> - 2012-04-15 15:02:44
Attachments:
signature.asc
|
Hi, I have a new set-top box I need to use irsend to control. For the record, it's a HUAWEI DC730. It comes with it's own remote. I also have an mceusb receiver/transmitter unit (an acer mceir-210 to be exact) which I have verified as being working by affixing the transmitter diode to the receiver diode and choosing a configuration file for a motorola dct2000 and then using irsend and irw to verify I can receive what I am sending. i.e.: $ irsend SEND_ONCE DCT2000 POWER and an irw running at the same time reports: 000000000000aff9 00 POWER DCT2000 So hardware-wise everything is working. Now trying to use irrecord to try to learn from this STB's remote I unfortunately end up getting: $ sudo irrecord -d /dev/lirc0 /tmp/remote.conf irrecord - application for recording IR-codes for usage with lirc [ standard irrecord boilerplate ] Press RETURN to continue. Now start pressing buttons on your remote control. It is very important that you press many different buttons and hold them down for approximately one second. Each button should generate at least one dot but in no case more than ten dots of output. Don't stop pressing buttons until two lines of dots (2x80) have been generated. Press RETURN now to start recording. ................................................................................ Found gap: 81484 Please keep on pressing buttons like described above. ................................................................................ Space/pulse encoded remote control found. Signal length is 35. Found possible header: 322 771 Found trail pulse: 292 No repeat code found. Signals are space encoded. Removed header. Signal length is 17 Now enter the names for the buttons. Please enter the name for the next button (press <ENTER> to finish recording) KEY_1 Now hold down button "KEY_1". Something went wrong. Please try again. (9 retries left) Something went wrong. Please try again. (8 retries left) Something went wrong. Please try again. (7 retries left) Something went wrong. Please try again. (6 retries left) Something went wrong. Please try again. (5 retries left) Something went wrong. Please try again. (4 retries left) Something went wrong. Please try again. (3 retries left) Something went wrong. Please try again. (2 retries left) Something went wrong. Please try again. (1 retries left) Something went wrong. Try using the -f option. So I tried using the -f option to force raw mode and did get a configuration file that works with some amount of reliability receiving from the remote however that same file seems to have absolutely no ability to send the appropriate IR codes as tested with directly with the STB as well as using my above loopback configuration with the mceusb receiver/transmitter that I have. I'm not quite sure where to go from here. Any ideas? Cheers, b. |
From: Richard F. <si...@bi...> - 2012-04-16 23:55:02
|
Hi Brian, It depends on a few factors. 1. Minimise IR interference (try a dark room and make sure the transmitter is as close as possible to the receiver), 2. Do some research and check what protocol that remote is using, I had a hell of a time attempting to record my Austar Flinders Satellite STB... It uses the RC-MM protocol. You can tell irrecord to use a specific protocol by specifying from the examples. 3. The pronto remotes have an awesome database and you may be able to get the pronto hex codes and convert to lirc configuration using the python script. Hope this gives you some more avenues to try :) -rF On 16/04/2012, at 1:02 AM, Brian J. Murrell wrote: > Hi, > > I have a new set-top box I need to use irsend to control. For the > record, it's a HUAWEI DC730. It comes with it's own remote. > > I also have an mceusb receiver/transmitter unit (an acer mceir-210 to > be exact) which I have verified as being working by affixing the > transmitter diode to the receiver diode and choosing a configuration > file for a motorola dct2000 and then using irsend and irw to verify I > can receive what I am sending. i.e.: > > $ irsend SEND_ONCE DCT2000 POWER > > and an irw running at the same time reports: > > 000000000000aff9 00 POWER DCT2000 > > So hardware-wise everything is working. > > Now trying to use irrecord to try to learn from this STB's remote I > unfortunately end up getting: > > $ sudo irrecord -d /dev/lirc0 /tmp/remote.conf > > irrecord - application for recording IR-codes for usage with lirc > > [ standard irrecord boilerplate ] > > Press RETURN to continue. > > > Now start pressing buttons on your remote control. > > It is very important that you press many different buttons and hold them > down for approximately one second. Each button should generate at least one > dot but in no case more than ten dots of output. > Don't stop pressing buttons until two lines of dots (2x80) have been > generated. > > Press RETURN now to start recording. > ................................................................................ > Found gap: 81484 > Please keep on pressing buttons like described above. > ................................................................................ > Space/pulse encoded remote control found. > Signal length is 35. > Found possible header: 322 771 > Found trail pulse: 292 > No repeat code found. > Signals are space encoded. > Removed header. > Signal length is 17 > Now enter the names for the buttons. > > Please enter the name for the next button (press <ENTER> to finish recording) > KEY_1 > > Now hold down button "KEY_1". > Something went wrong. Please try again. (9 retries left) > Something went wrong. Please try again. (8 retries left) > Something went wrong. Please try again. (7 retries left) > Something went wrong. Please try again. (6 retries left) > Something went wrong. Please try again. (5 retries left) > Something went wrong. Please try again. (4 retries left) > Something went wrong. Please try again. (3 retries left) > Something went wrong. Please try again. (2 retries left) > Something went wrong. Please try again. (1 retries left) > Something went wrong. > Try using the -f option. > > So I tried using the -f option to force raw mode and did get a > configuration file that works with some amount of reliability receiving > from the remote however that same file seems to have absolutely no > ability to send the appropriate IR codes as tested with directly with > the STB as well as using my above loopback configuration with the > mceusb receiver/transmitter that I have. > > I'm not quite sure where to go from here. > > Any ideas? > > Cheers, > b. > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 |
From: Brian J. M. <br...@in...> - 2012-04-17 03:21:15
Attachments:
signature.asc
Huawei DC730.rmdu
|
On 12-04-16 07:54 PM, Richard Ferrara wrote: > Hi Brian, Hi Richard, Many thanks for the response. > 1. Minimise IR interference (try a dark room and make sure the transmitter is as close as possible to the receiver), When trying to use irrecord or when trying to blast the resulting raw codes? > 2. Do some research and check what protocol that remote is using, Yeah, I couldn't find anything. This STB seems to be fairly "niche". I did find an "RMDU" file for it though. I will attach it in case it's useful. > You can tell irrecord to use a specific protocol by specifying from the examples. If you can figure out which protocol it's using. I don't think I am there yet. I did try the RCMM-32.conf, RC-5.conf and RC-6.conf files. No luck with any of them. > 3. The pronto remotes have an awesome database and you may be able to get the pronto hex codes From where? Do you mean this: http://www.remotecentral.com/cgi-bin/codes/? If so, unfortunately I don't even see HUAEI as a recognized brand. > Hope this gives you some more avenues to try :) Thanks again. Cheers, b. |
From: Brian J. M. <br...@in...> - 2012-04-17 13:45:53
Attachments:
signature.asc
|
As a followup, I took this remote apart and other than a couple of capacitors, this remote is being entirely driven from a chip with the following markings: 54973 64133 1014 02 I couldn't manage to find anything out about it though. :-( b. |
From: Richard F. <si...@bi...> - 2012-04-17 22:57:38
|
If you don't care about the remote you could wire up a hardware solution. Not as elegant but would be the path of least resistance. -rF On 17/04/2012, at 11:45 PM, Brian J. Murrell wrote: > As a followup, I took this remote apart and other than a couple of > capacitors, this remote is being entirely driven from a chip with the > following markings: > > 54973 > 64133 > 1014 02 > > I couldn't manage to find anything out about it though. :-( > > b. > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev |
From: Brian J. M. <br...@in...> - 2012-04-17 23:00:58
Attachments:
signature.asc
|
On 12-04-17 06:57 PM, Richard Ferrara wrote: > If you don't care about the remote you could wire up a hardware solution. I'm not sure I'm following. > Not as elegant but would be the path of least resistance. Perhaps which is why I am showing interest. :-) b. |
From: Richard F. <si...@bi...> - 2012-04-18 00:17:11
|
Similar to this. http://forums.oztivo.net/showthread.php?1977-Success-with-IR-translator-for-Austar-Flinders On 18/04/2012, at 9:00 AM, Brian J. Murrell wrote: > On 12-04-17 06:57 PM, Richard Ferrara wrote: >> If you don't care about the remote you could wire up a hardware solution. > > I'm not sure I'm following. > >> Not as elegant but would be the path of least resistance. > > Perhaps which is why I am showing interest. :-) > > b. > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev |
From: Richard F. <ri...@fe...> - 2012-04-18 00:15:32
|
Similar to this.. http://forums.oztivo.net/showthread.php?1977-Success-with-IR-translator-for-Austar-Flinders On 18/04/2012, at 9:00 AM, Brian J. Murrell wrote: > On 12-04-17 06:57 PM, Richard Ferrara wrote: >> If you don't care about the remote you could wire up a hardware solution. > > I'm not sure I'm following. > >> Not as elegant but would be the path of least resistance. > > Perhaps which is why I am showing interest. :-) > > b. > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev |
From: Richard F. <ri...@fe...> - 2012-04-17 00:11:05
|
Hi Brian, It depends on a few factors. 1. Minimise IR interference (try a dark room and make sure the transmitter is as close as possible to the receiver), 2. Do some research and check what protocol that remote is using, I had a hell of a time attempting to record my Austar Flinders Satellite STB... It uses the RC-MM protocol. You can tell irrecord to use a specific protocol by specifying from the examples. 3. The pronto remotes have an awesome database and you may be able to get the pronto hex codes and convert to lirc configuration using the python script. Hope this gives you some more avenues to try :) -rF On 16/04/2012, at 1:02 AM, Brian J. Murrell wrote: > Hi, > > I have a new set-top box I need to use irsend to control. For the > record, it's a HUAWEI DC730. It comes with it's own remote. > > I also have an mceusb receiver/transmitter unit (an acer mceir-210 to > be exact) which I have verified as being working by affixing the > transmitter diode to the receiver diode and choosing a configuration > file for a motorola dct2000 and then using irsend and irw to verify I > can receive what I am sending. i.e.: > > $ irsend SEND_ONCE DCT2000 POWER > > and an irw running at the same time reports: > > 000000000000aff9 00 POWER DCT2000 > > So hardware-wise everything is working. > > Now trying to use irrecord to try to learn from this STB's remote I > unfortunately end up getting: > > $ sudo irrecord -d /dev/lirc0 /tmp/remote.conf > > irrecord - application for recording IR-codes for usage with lirc > > [ standard irrecord boilerplate ] > > Press RETURN to continue. > > > Now start pressing buttons on your remote control. > > It is very important that you press many different buttons and hold them > down for approximately one second. Each button should generate at least one > dot but in no case more than ten dots of output. > Don't stop pressing buttons until two lines of dots (2x80) have been > generated. > > Press RETURN now to start recording. > ................................................................................ > Found gap: 81484 > Please keep on pressing buttons like described above. > ................................................................................ > Space/pulse encoded remote control found. > Signal length is 35. > Found possible header: 322 771 > Found trail pulse: 292 > No repeat code found. > Signals are space encoded. > Removed header. > Signal length is 17 > Now enter the names for the buttons. > > Please enter the name for the next button (press <ENTER> to finish recording) > KEY_1 > > Now hold down button "KEY_1". > Something went wrong. Please try again. (9 retries left) > Something went wrong. Please try again. (8 retries left) > Something went wrong. Please try again. (7 retries left) > Something went wrong. Please try again. (6 retries left) > Something went wrong. Please try again. (5 retries left) > Something went wrong. Please try again. (4 retries left) > Something went wrong. Please try again. (3 retries left) > Something went wrong. Please try again. (2 retries left) > Something went wrong. Please try again. (1 retries left) > Something went wrong. > Try using the -f option. > > So I tried using the -f option to force raw mode and did get a > configuration file that works with some amount of reliability receiving > from the remote however that same file seems to have absolutely no > ability to send the appropriate IR codes as tested with directly with > the STB as well as using my above loopback configuration with the > mceusb receiver/transmitter that I have. > > I'm not quite sure where to go from here. > > Any ideas? > > Cheers, > b. > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 |
From: Brian J. M. <br...@in...> - 2012-04-23 05:02:38
Attachments:
signature.asc
|
On 12-04-16 07:54 PM, Richard Ferrara wrote: > Hi Brian, Hi Richard, > 1. Minimise IR interference (try a dark room and make sure the transmitter is as close as possible to the receiver), Recorded from the remote to raw in a very dark room. Had the transmitter LED taped right to the front of the receiver and while the receiver's light blinks when I use irsend, irw is still not seeing a thing. > 2. Do some research and check what protocol that remote is using, I had a hell of a time attempting to record my Austar Flinders Satellite STB... It uses the RC-MM protocol. You can tell irrecord to use a specific protocol by specifying from the examples. Still haven't been able to determine this. I don't think this device (manufacturer) is too popular/prevalent. I've tried contacting Huawei directly but (to no surprise) they failed to respond. > 3. The pronto remotes have an awesome database and you may be able to get the pronto hex codes and convert to lirc configuration using the python script. Is this http://www.remotecentral.com/cgi-bin/codes/ you mean? There was nothing at all there for Huawei. I even did a site search for Huawei and it returned a few hits but nothing about my device. Please? Anyone? Any ideas? I mean other than hacking the hardware. I don't own it, the cableco does. b. |
From: Richard F. <si...@bi...> - 2012-04-23 05:28:21
|
Hi Brian, I was in the same position as you, I ended up with two options, hack the hardware or change the STB. Hacking the hardware would have been easy, spend $30 on a replacement remote and some time wiring and programming it up. However in that scenario I was still stuck with the crappy provider STB which a max of S-Video out. Ended up replacing the STB which had component out, a remote I could record and HD video :D HD-PVRs are a godsend. -rF On 23/04/2012, at 3:02 PM, Brian J. Murrell wrote: > On 12-04-16 07:54 PM, Richard Ferrara wrote: >> Hi Brian, > > Hi Richard, > >> 1. Minimise IR interference (try a dark room and make sure the transmitter is as close as possible to the receiver), > > Recorded from the remote to raw in a very dark room. Had the > transmitter LED taped right to the front of the receiver and while the > receiver's light blinks when I use irsend, irw is still not seeing a thing. > >> 2. Do some research and check what protocol that remote is using, I had a hell of a time attempting to record my Austar Flinders Satellite STB... It uses the RC-MM protocol. You can tell irrecord to use a specific protocol by specifying from the examples. > > Still haven't been able to determine this. I don't think this device > (manufacturer) is too popular/prevalent. I've tried contacting Huawei > directly but (to no surprise) they failed to respond. > >> 3. The pronto remotes have an awesome database and you may be able to get the pronto hex codes and convert to lirc configuration using the python script. > > Is this http://www.remotecentral.com/cgi-bin/codes/ you mean? There was > nothing at all there for Huawei. I even did a site search for Huawei > and it returned a few hits but nothing about my device. > > Please? Anyone? Any ideas? > > I mean other than hacking the hardware. I don't own it, the cableco does. > > b. > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 |
From: StephenG <st...@ph...> - 2012-04-27 04:01:50
|
Hi Brian. I was in the same situation as you. My cable co went digital and sent me a dc730 which castrated my mythtv box. I didn't have any luck with "irrecord -f" either. So, I took the remote into work and scoped it up with an photodiode to get all the timings and carrier frequency. Long story short, I now have a working lirc.conf file that I can use with irsend. I won't guarantee it'll work with your box but you're welcome to give it a try. http://www.physics.queensu.ca/~steve/DC730_lirc.conf NOTE that I was only interested in sending the numbers so that my mythtv box could change the channels so it only has keys 0-9. If you need the other keys, let me know and I'll finish the job. -steve Brian J. Murrell wrote: > > Hi, > > I have a new set-top box I need to use irsend to control. For the > record, it's a HUAWEI DC730. It comes with it's own remote. > > --SNIP---- > > Any ideas? > > Cheers, > b. > > -- View this message in context: http://old.nabble.com/irsend-with-raw-codes--tp33690522p33756843.html Sent from the LIRC mailing list archive at Nabble.com. |
From: Brian J. M. <br...@in...> - 2012-04-27 17:10:12
Attachments:
signature.asc
|
On 12-04-27 12:01 AM, StephenG wrote: > > Hi Brian. I was in the same situation as you. My cable co went digital > and sent me a dc730 which castrated my mythtv box. If you are talking about the cableco that serviced you when you are/were at queensu.ca, then we are talking about one and the same cableco. Queens is "just down the street" (relatively speaking) from me here. :-) > http://www.physics.queensu.ca/~steve/DC730_lirc.conf Ahhh. Great. Thanks! Did you notice that somebody else provided a similar config based on the RMDU file that I had dug up and sent to the list? It's working wonderfully for me also. > NOTE that I was only interested in sending the numbers so that my mythtv > box could change the channels so it only has keys 0-9. If you need the > other > keys, let me know and I'll finish the job. Indeed. Mythtv is my use-case also. Thanks so much for responding though, I do appreciate it. Cheers, b. |
From: StephenG <st...@ph...> - 2012-04-27 19:37:01
|
Glad you got a working one. I got mine all up and running at around 2am this morning (WHY do I stay up that late!?) I confess I'm relatively new to LIRC setup and didn't know what an RMDU is used, and whether it had worked for you. Some days, I just hit the brute force button and attack things at the lowest level (maybe I've done to much assembly language programming). It did help me nail the carrier frequency though. Can you do me a favour and test mine to see if it works on your box too? Richard wants to give me a shot with his remote so he's planning on mailing it to me. It would be nice to know that what I did is universally applicable. Brian J. Murrell wrote: > > > Did you notice that somebody else provided a similar config based on the > RMDU file that I had dug up and sent to the list? It's working > wonderfully for me also. > -- View this message in context: http://old.nabble.com/irsend-with-raw-codes--tp33690522p33760469.html Sent from the LIRC mailing list archive at Nabble.com. |