Menu
▾
▴
lirc-list
|
From: Jason L. <jas...@gm...> - 2013-09-05 12:29:39
Attachments:
test.conf
Screenshot from 2013-09-05 21:43:26.png
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I have an HP MediaSmart RC2285201/01 ( the left one in this image http://www.flickr.com/photos/bleblanc/2587106736/) remote that I'm trying to get the codes for. I've tried out irrecord which does detect something but once I try the conf file it produces, lirc fails to read anything. I've been looking at the signal using xmode2. It seems odd to me as though the codes for any particular key cycle or are not the same for each repeated send. In the screenshot I've attached, I was only pressing the 1 key. Any ideas what sort of protocol it might be so I can try and get it working? I'm using lirc in debian: 0.9.0~pre1-1 I'm attempting to record with: irrecord -f --device=/dev/lirc0 test.conf test.conf included here in case its of use. I only recorded a few keys for testing purposes. Thanks, Jason -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSKHkpAAoJEPpXHsdQXnZOlWMP/1apUl3Niq5ZFh5TJkP4frIy YVhQYt1qyAQyJfBqz7QuhVSeR6hSTrWHLOVvuVN5SuaHQazV0rgoO9MAsEXvwHGh D7gPR4TZWVpDtUvub+6xEWvUptrfZSoCaXXU1hBhYknMA5MDuPgAkDBCOBsqTlto 8OsUBMklmqu5Jy58AQsiJRHNd2nxub4NuRVniAwR0XyeB8vGFH9Bi+6FRiKIyJTM 95lh2EhbvimhxQvwMUpuGSTku08rtC7X+QSNRqcMKqfMboJsZz1dQHOrZl4Hwscb K65odBVuY/msEd7QUgEBJi/4a2FyfFSTF2fCodVbQjfDC3ULdRm76HmG0KRn+ym6 lJ/hT/zpuTM1rdOPdlsQRR6cIDIKfCeUz2O2lVC+hIQ9zqwyXv4KVKaApetCFBYK J4Q+/MiSLXD/8GmXHvUcNcQq9J+NqUqnW971RkErS1SRMSH9/g7Cj4cDgtlnggjG dei7mZicg0aYawRk+3/jm9Ha6bPMauQKYQAgrtVRr7nGvm71olvE7rtufgxmNjOu PfD5UDnxHbafJi/W97gZFbXoihxLNHCz0dRsJ3VW+Et6Hm41+xI++56+dbc/G8ns 39eObNDs9WyGPfZFImvk6r5iUA2YVmzfh2Nxgd5glu0hnCA6yUUPWuwPkCUDKsBu HPS9FGV01OKh7uM6AaoV =w0j1 -----END PGP SIGNATURE----- |
|
From: Martin T. J. <ma...@br...> - 2013-09-12 20:03:09
|
Hello Jason, Your signals look like snippets of RC6, see http://www.sbprojects.com/knowledge/ir/rc6.php and http://www.pcbheaven.com/userpages/The_Philips_RC6_Protocol/. In any RC6 mode the signals should be the same length you were correct in your suspicions of the signals displayed by xmode2, you need to get a consistent signal before proceeding. You don't give details of your receiver but all times in your .conf file are multiples of 50 microseconds, irrecord is not good at determining the timing data with this resolution it may be worth trying to start with a template .conf file with the timing data provided.. Martin |
|
From: Jason L. <jas...@gm...> - 2013-09-17 04:36:24
|
Martin Tharby Jones wrote, On 13/09/2013 5:02 AM: > Hello Jason, > > Your signals look like snippets of RC6, see > http://www.sbprojects.com/knowledge/ir/rc6.php > and http://www.pcbheaven.com/userpages/The_Philips_RC6_Protocol/. > In any RC6 mode the signals should be the same length you were correct > in your suspicions > of the signals displayed by xmode2, you need to get a consistent signal > before proceeding. > > You don't give details of your receiver but all times in your .conf file > are multiples of 50 microseconds, > irrecord is not good at determining the timing data with this resolution > it may be worth trying to start > with a template .conf file with the timing data provided.. > Hi Martin, Thanks for your thoughts on this. The receiver is an HP model TSGI-IR01 HP P/N 5070-2584. It's a usb device that looks like this: http://main.jmah.net/wp-content/uploads/2013/03/xbmc-htpc-hp-infrared-receiver.jpg I'm having not much luck finding out about this but I'm starting to wonder if this receiver is not RC6 capable. Tonight I'll try and get some captures from a USB IR Toy, which will hopefully give me a clearer idea what code its transmitting. Jason -- Jason Lewis http://emacstragic.net |
|
From: Jason L. <jas...@gm...> - 2013-09-17 12:28:23
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 17/09/13 2:36 PM, Jason Lewis wrote: > Martin Tharby Jones wrote, On 13/09/2013 5:02 AM: >> Hello Jason, >> >> Your signals look like snippets of RC6, see >> http://www.sbprojects.com/knowledge/ir/rc6.php >> and http://www.pcbheaven.com/userpages/The_Philips_RC6_Protocol/. >> In any RC6 mode the signals should be the same length you were correct >> in your suspicions >> of the signals displayed by xmode2, you need to get a consistent signal >> before proceeding. >> >> You don't give details of your receiver but all times in your .conf file >> are multiples of 50 microseconds, >> irrecord is not good at determining the timing data with this resolution >> it may be worth trying to start >> with a template .conf file with the timing data provided.. >> > > Hi Martin, > > Thanks for your thoughts on this. > > The receiver is an HP model TSGI-IR01 HP P/N 5070-2584. It's a usb > device that looks like this: > http://main.jmah.net/wp-content/uploads/2013/03/xbmc-htpc-hp-infrared-receiver.jpg > > I'm having not much luck finding out about this but I'm starting to > wonder if this receiver is not RC6 capable. Tonight I'll try and get > some captures from a USB IR Toy, which will hopefully give me a clearer > idea what code its transmitting. > > Jason > > I saved some traces in a google doc. You can see them here: http://goo.gl/sHAAHc To me it looks like a modified RC6 protocol. The Toggle bit seems to be moved to about 2/3 of the way through the trace. Any thoughts? Jason -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSOErjAAoJEPpXHsdQXnZOBoMP/1HqOgrVh7U5qF3TEqz+v7nM wQYf2KF9G9xdZXVxrVYGLkrO8hgpn4uHSKNgC66hVsnttkl2ySpWi/PrrIDEHHEf L42dj4zQiBQuWcWsOkJiCjn17gb8OhedTQXYAwY5JCcnJt7rzDXH6YJoJE+jVyOZ eetuMk3yoP0C8pzhDhoO09ZMDu/SSkiilWKlitlw5sMnSEy81Fu92OV0D/iti7Ff 5jTHXVClhXRqXTrV6aKUYsZj+DTm+4vgXcPeEHdBHFN5CVs5IPZXUUpiT2gf4pXl TjbpOOp8/Tl3WOi39NevkHfAEj/SzpDxoNqcJ+lhDGmVB53QlX3RDwMGArPnDXIR DXHXE1QaxCcVx4AKOakG/yKKAMLO6P8euJBxMHT8i11Z1Ek3L5R9Rb+7w0usfndX Nx+j8BZPbnWtSvJr4tnkMXT82JW1APoIPIwFnOvdsoWIjZXD2h7w3/pllHp8J230 k4qOXUlOkfLRfwNe2vARaLOh4o0ZcHFbqyjm/8SY2KtdbpgFcxZ/oN68octxKauV 2JlB/CSQVH86EIZLKNtVuHub5rnIWBs5whkTVdL77CPHg+BryCV+r9kGJG2dY3xD 9Ddq2hbzBI/fTmIVW5j9e0IzKs9t5xR58iaNERXm859xjiDin/dnEZDhZyO+6Pyq /K0P+nJRBzgy3mITWhQR =w1CG -----END PGP SIGNATURE----- |
|
From: Martin T. J. <ma...@br...> - 2013-09-19 19:46:27
|
On 17/09/13 13:28, Jason Lewis wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 17/09/13 2:36 PM, Jason Lewis wrote: >> Martin Tharby Jones wrote, On 13/09/2013 5:02 AM: >>> Hello Jason, >>> >>> Your signals look like snippets of RC6, see >>> http://www.sbprojects.com/knowledge/ir/rc6.php >>> and http://www.pcbheaven.com/userpages/The_Philips_RC6_Protocol/. >>> In any RC6 mode the signals should be the same length you were correct >>> in your suspicions >>> of the signals displayed by xmode2, you need to get a consistent signal >>> before proceeding. >>> >>> You don't give details of your receiver but all times in your .conf file >>> are multiples of 50 microseconds, >>> irrecord is not good at determining the timing data with this resolution >>> it may be worth trying to start >>> with a template .conf file with the timing data provided.. >>> >> Hi Martin, >> >> Thanks for your thoughts on this. >> >> The receiver is an HP model TSGI-IR01 HP P/N 5070-2584. It's a usb >> device that looks like this: >> > http://main.jmah.net/wp-content/uploads/2013/03/xbmc-htpc-hp-infrared-receiver.jpg >> I'm having not much luck finding out about this but I'm starting to >> wonder if this receiver is not RC6 capable. Tonight I'll try and get >> some captures from a USB IR Toy, which will hopefully give me a clearer >> idea what code its transmitting. >> >> Jason >> >> > I saved some traces in a google doc. You can see them here: > > http://goo.gl/sHAAHc > > To me it looks like a modified RC6 protocol. The Toggle bit seems to be > moved to about 2/3 of the way through the trace. Any thoughts? > > Jason Hello Jason, Your receiver provides mark and space timing data as shown by the ability of irrecord to create raw_codes data and the fact that xmode2 and mode2 work therefore all the protocol decoding is performed by the lirc daemon or kernel depending on your configuration (it should handle all supported protocols). The problem is that it is missing chunks of the data. The logic analyser traces look good, they won't be the same as described in my links above they are using a different RC6 mode (6) which provides 32 bits, see my annotated trace. https://docs.google.com/document/d/1hVKuJWsqa-BlIfGUBE-1h7NCG49XLBoVm_QEbJX_qDs/pub The header and bit timing look to be standard but there is no trace showing the gap so you will have to provide a value in the template configuration file attached. Details of the configuration file are given in: http://winlirc.sourceforge.net/technicaldetails.html Martin |
|
From: Jason L. <jas...@gm...> - 2013-09-28 14:26:55
|
# Please make this file available to others
# by sending it to <li...@ba...>
#
# this config file was automatically generated
# using lirc-0.9.0-pre1(default) on Sun Sep 29 00:00:48 2013
#
# contributed by
#
# brand: HP
# model no. of remote control: MediaSmart HP-RC2285201/01
# devices being controlled by this remote: HP MediaSmart Connect x280n
#
begin remote
name HP-RC2285201-01
bits 21
flags RC6|CONST_LENGTH
eps 30
aeps 100
header 2686 860
one 453 433
zero 453 433
pre_data_bits 16
pre_data 0x1BFF
gap 106201
min_repeat 2
# suppress_repeat 2
# uncomment to suppress unwanted repeats
toggle_bit_mask 0x8000
rc6_mask 0x100000000
begin codes
KEY_POWER 0x0E2DF3
KEY_SOURCE 0x0E2D74
KEY_MENU-SETTINGS 0x0E2DAB
KEY_RED 0x0E2D1B
KEY_GREEN 0x0E2D1A
KEY_YELLOW 0x0E2D19
KEY_BLUE 0x0E2D18
KEY_SEARCH 0x0E2D6C
KEY_MEDIA 0x0E2DF4
KEY_LIVETV 0x0E2D6D
KEY_UP 0x0E2DA7
KEY_FAVOURITES 0x0E2D54
KEY_LEFT 0x0E2DA5
KEY_OK 0x0E2DA3
KEY_RIGHT 0x0E2DA4
KEY_GUIDE 0x0E2D33
KEY_BACK 0x0E2DAA
KEY_INFO 0x0E2D7E
KEY_RECORDEDTV 0x0E2D5F
KEY_DOWN 0x0E2DA6
KEY_VOLUMEUP 0x0E6DEF
KEY_WINDOWSKEY 0x0E2D5E
KEY_CHANNELUP 0x0E2DE1
KEY_VOLUMEDOWN 0x0E6DEE
KEY_MUTE 0x0E6DF2
KEY_CHANNELDOWN 0x0E2DE0
KEY_MENU 0x0E2D2A
KEY_RECORD 0x0E2DC8
KEY_REWIND 0x0E2DD6
KEY_PLAY 0x0E2DD3
KEY_PAUSE 0x0E2DCF
KEY_FASTFORWARD 0x0E2DD7
KEY_SKIPBACK 0x0E2DDE
KEY_STOP 0x0E2DCE
KEY_SKIPFORWARD 0x0E2DDF
KEY_1 0x0E2DFE
KEY_2 0x0E2DFD
KEY_3 0x0E2DFC
KEY_4 0x0E2DFB
KEY_5 0x0E2DFA
KEY_6 0x0E2DF9
KEY_7 0x0E2DF8
KEY_8 0x0E2DF7
KEY_9 0x0E2DF6
KEY_* 0X0E2D53
KEY_0 0x0E2DFF
KEY_# 0X0E2D5D
KEY_CLEAR 0x0E2DA9
KEY_LAST 0x0E2DF5
KEY_ENTER 0x0E2D1E
end codes
end remote
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X