Re: irsend with raw codes?

[Richard F. <si...@bi...>]

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