Re: IR Blaster - what I send isn't received

[<pa...@pl...>]

>> Context
>> - the receiver has been working, I decided to upgrade to a
>> transceiver so
>> as to control set top box
>> - the transceiver seems to be sending commands, but not recognised
>> by any
>> of my devices
>> - if I use two different PCs, and use the transceiver to send IR to
>> the
>> receiver, with both having the same config file, the receiver doesn't
>> recognise them (but mode2 shows it is receiving something)

>> Summary view is:
>> - I have an mce usb receiver, and a separate mce_usb transceiver
> Hint: you can have a transceiver just loop back to itself. 
Interesting - I couldn't work this out, I'll have to try harder.  Since I
have two devices I'll stick to sending from one to the other for now - one
less thing to go wrong at the moment.

> You might post a copy of your
> config too (trimmed down to just a few buttons), maybe someone will
> see something that looks off in it. Receiving tends to be more
> forgiving than transmitting sometimes.

CONFIG FILE:
# brand: creek
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote

name creek
bits 5
flags RC5|CONST_LENGTH
eps 30
aeps 100

one 934 861
zero 934 861
plead 944
pre_data_bits 8
pre_data 0xA0
gap 115876
toggle_bit_mask 0x800

begin codes
KEY_MUTE 0x0D
KEY_POWER 0x10
end codes

end remote


>> The trick here is that the transceiver isn't recognised out of the
>> box by
>> LIRC, although it is an MCE device.

>Definitely want to know the device ID then, so it can be added to cvs.

The relevant bit of the code patch from my first e-mail:
CODE PATCH
*** ../../../lirc-0.8.5/drivers/lirc_mceusb2/lirc_mceusb2.c 2009-04-16
00:20:26.000000000 +1000
--- lirc_mceusb2.c 2009-08-07 21:46:09.000000000 +1000
***************
*** 179,184 ****
--- 179,188 ----
/* Formosa eHome Infrared Transceiver */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe015) },
/* Formosa21 / eHome Infrared Receiver */
+ { USB_DEVICE(VENDOR_FORMOSA, 0xe03a) },
+ /* Formosa21 / eHome Infrared Transceiver */
+ { USB_DEVICE(VENDOR_FORMOSA, 0xe03c) },
+ /* Formosa21 / eHome Infrared Transceiver */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe016) },
/* Formosa aim / Trust MCE Infrared Receiver */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe017) },
***************


>> I made a code change in irc_mceusb2.c
>> so as to enable it. This code change I made in both mceusb_dev_table
>> and
>> transmitter_mask_list.

>Have you tried *not* adding it to the transmitter_mask_list? This is
>(iirc) a list of transceivers that have inverted transmit masks vs.
>the rest of the transceivers. If you've got it listed as inverted,
>when it isn't, that would definitely screw with things.

Ah, this is a really critical piece of information.  I almost blinded
myself when the lightbulb went on above my head!!  I've modified the code
so that it doesn't appear in the transmitter mask, and I think I'm much
closer now.

The mode2 output is attached below.  The first column is the output I get
from the transmitter being received by my other receiver.  It still isn't
recognised as the keypress I sent (KEY_POWER in the remote file above). 
But it is a lot closer than it was before.

The second and third columns are output from the remote control itself, to
the same receiver.  I pressed the button once, but I think it repeated
twice, so I cut the output off at the point that looked like the start of
the repeat, and put it into the third column.  If I did that all correctly,
then the first column is the transmitter, and columns 2 and 3 are the
remote control itself.

I'm not entirely sure how to read this output, but the clear differences
are the pulses in line 4, line 8, lines 13 and 14.  And clearly the remote
itself is sending more pulses, although I'm not certain that they're
material.  Interestingly the transmitter is longer on some pulses and
shorter on others, so it isn't as clear cut as I might have hoped. 
Nonetheless, it looks better than it did.  I'm at work now, so I'll have
another crack at this tonight - given that it's closer I might run through
everything from start to finish, and do each step again to make sure I have
it right.

Transmit	  -  	Remote	  -  	Second repeat?
space 100000	  -  	space 100000	  -  	space 89700
pulse 1000	  -  	pulse 1000	  -  	pulse 950
space 700	  -  	space 750	  -  	space 800
pulse 1900	  -  	pulse 1000	  -  	pulse 950
space 750	  -  	space 750	  -  	space 800
pulse 1000	  -  	pulse 1000	  -  	pulse 950
space 700	  -  	space 800	  -  	space 800
pulse 1000	  -  	pulse 1800	  -  	pulse 1850
space 750	  -  	space 800	  -  	space 800
pulse 950	  -  	pulse 1000	  -  	pulse 950
space 750	  -  	space 800	  -  	space 800
pulse 950	  -  	pulse 950	  -  	pulse 950
space 1600	  -  	space 800	  -  	space 850
pulse 1900	  -  	pulse 950	  -  	pulse 900
space 750	  -  	space 800	  -  	space 850
pulse 950	  -  	pulse 950	  -  	pulse 900
space 750	  -  	space 1700	  -  	space 1750
pulse 950	  -  	pulse 1800	  -  	pulse 1800
space 800	  -  	space 850	  -  	space 800
pulse 900	  -  	pulse 900	  -  	pulse 950
         	  -  	space 850	  -  	space 850
         	  -  	pulse 900	  -  	pulse 900
         	  -  	space 1750	  -  	space 1700
         	  -  	pulse 900	  -  	pulse 950

Thanks for all the assistance, I think this is taking me somewhere closer. 
If the mode2 output tells anyone something that indicates an error, then
I'd love to know about it, otherwise I'll work on it tonight as I said
above.

Thanks,

Paul