View previous topic :: View next topic |
Author |
Message |
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Wed May 25, 2005 10:21 am Post subject: How to make upgrade from lirc conf file for iMON-PAD remote |
|
|
I have bought SilverStone LC10M HTPC case that comes with remote and IR rceiver. This remote is what they call iMON-PAD, this remote uses some kind of 'short' signal protocol as per manufacturer. I searched in this forum and noticed that someone created device upgrade for earlier version of remote that used NEC protocol. He used .conf file from lirc project. http://www.hifi-remote.com/forums/viewtopic.php?t=2627
The new version of iMon-PAD uses NEC-type protocol with different timings. I have .conf file from lirc project. I have no clue about how to use this file to create protocol upgrade and device upgrade. Pros, please help.
By the way, I have already tried to "learn" the IR commands from iMON-PAD remote to my 8910 but no luck. None of the learned commands have protocol information.
Code: |
# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.7.1pre2(imon) on Tue Mar 1 23:15:44 2005
#
# brand: iMON-New
# model no. of remote control: iMON-PAD
# devices being controlled by this remote:
#
begin remote
name iMON-PAD
bits 24
eps 30
aeps 100
one 0 0
zero 0 0
post_data_bits 8
post_data 0xB7
gap 235965
min_repeat 1
toggle_bit 29
begin codes
AppExit 0x288195
Power 0x289115
Record 0x298115
Play 0x2A8115
SlowMotion 0x29B195
Rewind 0x2A8195
Pause 0x2A9115
FastForward 0x2B8115
PrevChapter 0x2B9115
Stop 0x2B9715
NextChapter 0x298195
Esc 0x2BB715
Eject 0x299395
AppLauncher 0x29B715
MultiMon 0x2AB195
TaskSwitcher 0x2A9395
Mute 0x2B9595
Vol+ 0x28A395
Vol- 0x28A595
Ch+ 0x289395
Ch- 0x288795
Timer 0x2B8395
1 0x28B595
2 0x2BB195
3 0x28B195
4 0x2A8595
5 0x299595
6 0x2AA595
7 0x2B9395
8 0x2A8515
9 0x2AA115
0 0x2BA595
ShiftTab 0x28B515
Tab 0x29A115
MyMovie 0x2B8515
MyMusic 0x299195
MyPhoto 0x2BA115
MyTV 0x28A515
Bookmark 0x288515
Thumbnail 0x2AB715
AspectRatio 0x29A595
FullScreen 0x2AA395
MyDVD 0x29A295
Menu 0x2BA385
Caption 0x298595
Language 0x2B8595
MouseKeyboard 0x299115
SelectSpace 0x2A9315
MouseMenu 0x28B715
Enter 0x28A195
WindowsKey 0x2B8195
Backspace 0x28A115
MouseRightClick 0x688481
MouseLeftClick 0x688301
MouseNW 0x6B0281
MouseNW 0x6B02C1
MouseNW 0x6B0A89
MouseNW 0x6B0AC9
MouseNW 0x6B0AF1
MouseNW 0x6B1291
MouseNW 0x6B12D1
MouseNW 0x6B12E1
MouseNW 0x6B1A99
MouseNW 0x6B1AE9
MouseNW 0x6B22A1
MouseNW 0x6B22C1
MouseNW 0x6B22E1
MouseNW 0x6B2AA9
MouseNW 0x6B2AC9
MouseNW 0x6B2AE9
MouseNW 0x6B32B1
MouseNW 0x6B32D1
MouseNW 0x6B32F1
MouseNW 0x6B4281
MouseNW 0x6B42A1
MouseNW 0x6B42C1
MouseNW 0x6B4A89
MouseNW 0x6B4AA9
MouseNW 0x6B4AC9
MouseNW 0x6B5291
MouseNW 0x6B52B1
MouseNW 0x6B52D1
MouseNW 0x6B6291
MouseNW 0x6B62A1
MouseNW 0x6B62E1
MouseNW 0x6B6A99
MouseNW 0x6B6AA9
MouseNW 0x6B6AE9
MouseNW 0x6B7289
MouseNW 0x6B72B1
MouseNW 0x6B72F1
MouseN 0x690281
MouseN 0x690289
MouseN 0x690291
MouseN 0x690299
MouseN 0x6902A1
MouseN 0x6902A9
MouseN 0x6902B1
MouseN 0x6902B9
MouseN 0x6902C1
MouseN 0x6902C9
MouseN 0x6902D1
MouseN 0x6902D9
MouseN 0x6902E1
MouseN 0x6902E9
MouseN 0x6902F1
MouseN 0x6902F9
MouseN 0x694281
MouseN 0x694289
MouseN 0x694291
MouseN 0x6942A1
MouseN 0x6942B1
MouseN 0x6942C1
MouseN 0x6942D1
MouseN 0x6942E1
MouseN 0x6942F1
MouseN 0x6B7A81
MouseN 0x6B7A89
MouseN 0x6B7A91
MouseN 0x6B7AA1
MouseN 0x6B7AB1
MouseN 0x6B7AC1
MouseN 0x6B7AD1
MouseN 0x6B7AE1
MouseN 0x6B7AF1
MouseNE 0x690A89
MouseNE 0x690AC9
MouseNE 0x690AF1
MouseNE 0x691299
MouseNE 0x6912E9
MouseNE 0x691A91
MouseNE 0x691AD1
MouseNE 0x691AE1
MouseNE 0x692AB1
MouseNE 0x692AD1
MouseNE 0x692AF1
MouseNE 0x6932A9
MouseNE 0x6932C9
MouseNE 0x6932E9
MouseNE 0x693AA1
MouseNE 0x693AC1
MouseNE 0x693AE1
MouseNE 0x694A89
MouseNE 0x694AB1
MouseNE 0x694AF1
MouseNE 0x695299
MouseNE 0x6952A9
MouseNE 0x6952E9
MouseNE 0x695A91
MouseNE 0x695AA1
MouseNE 0x695AE1
MouseNE 0x696A91
MouseNE 0x696AB1
MouseNE 0x696AD1
MouseNE 0x697289
MouseNE 0x6972A9
MouseNE 0x6972C9
MouseNE 0x697A81
MouseNE 0x697AA1
MouseNE 0x697AC1
MouseE 0x688A81
MouseE 0x688AC1
MouseE 0x689281
MouseE 0x689A81
MouseE 0x689AC1
MouseE 0x68A281
MouseE 0x68AA81
MouseE 0x68AAC1
MouseE 0x68B281
MouseE 0x68BA81
MouseE 0x68BAC1
MouseE 0x68C281
MouseE 0x68CA81
MouseE 0x68CAC1
MouseE 0x68D281
MouseE 0x68DA81
MouseE 0x68DAC1
MouseE 0x68E281
MouseE 0x68EA81
MouseE 0x68EAC1
MouseE 0x68F281
MouseE 0x68FA81
MouseE 0x68FAC1
MouseE 0x690AF9
MouseE 0x691AF9
MouseE 0x692AF9
MouseE 0x693AF9
MouseE 0x694AF9
MouseE 0x695AF9
MouseE 0x696AF9
MouseE 0x697AF9
MouseSE 0x688A89
MouseSE 0x688AC9
MouseSE 0x688AF1
MouseSE 0x689291
MouseSE 0x6892D1
MouseSE 0x689A99
MouseSE 0x689AD9
MouseSE 0x689AE9
MouseSE 0x68AAA9
MouseSE 0x68AAC9
MouseSE 0x68AAE9
MouseSE 0x68B2B1
MouseSE 0x68B2D1
MouseSE 0x68B2F1
MouseSE 0x68BAB9
MouseSE 0x68BAD9
MouseSE 0x68BAF9
MouseSE 0x68CA89
MouseSE 0x68CAA9
MouseSE 0x68CAC9
MouseSE 0x68D291
MouseSE 0x68D2B1
MouseSE 0x68D2D1
MouseSE 0x68DA99
MouseSE 0x68DAB9
MouseSE 0x68DAD9
MouseSE 0x68EA99
MouseSE 0x68EAA9
MouseSE 0x68EAE9
MouseSE 0x68F289
MouseSE 0x68F2B1
MouseSE 0x68F2F1
MouseSE 0x68FAB9
MouseSE 0x68FAF9
MouseS 0x688289
MouseS 0x688291
MouseS 0x688299
MouseS 0x6882A1
MouseS 0x6882A9
MouseS 0x6882B1
MouseS 0x6882B9
MouseS 0x6882C1
MouseS 0x6882C9
MouseS 0x6882D1
MouseS 0x6882D9
MouseS 0x6882E1
MouseS 0x6882E9
MouseS 0x6882F1
MouseS 0x6882F9
MouseS 0x68C289
MouseS 0x68C299
MouseS 0x68C2A9
MouseS 0x68C2B9
MouseS 0x68C2C9
MouseS 0x68C2D9
MouseS 0x68C2E9
MouseS 0x68C2F9
MouseS 0x6AFA89
MouseS 0x6AFA99
MouseS 0x6AFAA9
MouseS 0x6AFAB9
MouseS 0x6AFAC9
MouseS 0x6AFAD9
MouseS 0x6AFAE9
MouseS 0x6AFAF9
MouseSW 0x6A82F9
MouseSW 0x6A8A89
MouseSW 0x6A8AC9
MouseSW 0x6A8AF1
MouseSW 0x6A9299
MouseSW 0x6A92D9
MouseSW 0x6A92E9
MouseSW 0x6A9A91
MouseSW 0x6A9AD1
MouseSW 0x6AA2B9
MouseSW 0x6AA2D9
MouseSW 0x6AA2F9
MouseSW 0x6AAAB1
MouseSW 0x6AAAD1
MouseSW 0x6AAAF1
MouseSW 0x6AB2A9
MouseSW 0x6AB2C9
MouseSW 0x6AB2E9
MouseSW 0x6AC2B9
MouseSW 0x6AC2F9
MouseSW 0x6ACA89
MouseSW 0x6ACAB1
MouseSW 0x6ACAF1
MouseSW 0x6AD299
MouseSW 0x6AD2A9
MouseSW 0x6AD2E9
MouseSW 0x6AE299
MouseSW 0x6AE2B9
MouseSW 0x6AE2D9
MouseSW 0x6AEA91
MouseSW 0x6AEAB1
MouseSW 0x6AEAD1
MouseSW 0x6AF289
MouseSW 0x6AF2A9
MouseSW 0x6AF2C9
MouseW 0x6A8281
MouseW 0x6A82C1
MouseW 0x6A8A81
MouseW 0x6A8AC1
MouseW 0x6A9281
MouseW 0x6A92C1
MouseW 0x6A9A81
MouseW 0x6AA281
MouseW 0x6AA2C1
MouseW 0x6AAA81
MouseW 0x6AB281
MouseW 0x6AB2C1
MouseW 0x6ABA81
MouseW 0x6AC281
MouseW 0x6AC2C1
MouseW 0x6ACA81
MouseW 0x6AD281
MouseW 0x6AD2C1
MouseW 0x6ADA81
MouseW 0x6AE281
MouseW 0x6AE2C1
MouseW 0x6AEA81
MouseW 0x6AF281
MouseW 0x6AF2C1
MouseW 0x6AFA81
MouseW 0x6B02F9
MouseW 0x6B0AF9
MouseW 0x6B12F9
MouseW 0x6B22F9
MouseW 0x6B32F9
MouseW 0x6B42F9
MouseW 0x6B52F9
MouseW 0x6B62F9
MouseW 0x6B72F9
end codes
end remote
|
|
|
Back to top |
|
|
gfb107 Expert
Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC |
|
Back to top |
|
|
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Wed May 25, 2005 12:00 pm Post subject: |
|
|
I will post the IR file tomorrow. Thanks. |
|
Back to top |
|
|
johnsfine Site Admin
Joined: 10 Aug 2003 Posts: 4766 Location: Bedford, MA |
Posted: Wed May 25, 2005 12:21 pm Post subject: Re: How to make upgrade from lirc conf file for iMON-PAD rem |
|
|
pjigar wrote: |
The new version of iMon-PAD uses NEC-type protocol with different timings. |
Not just different timings. To the extent I understand that Lirc file, it describes a protocol that is about as different from NEC as you could get and still be IR. If you actually meant something by "NEC-type", please explain.
I expect the actual protocol is related to RC6. It might even match the RC6 varient used in other HTPC remotes. But there are parts of that Lirc file that don't match my understanding of a how an RC6 varient would be represented in Lirc. Also, any fairly up-to-date version of DecodeIr would have identified any reasonable RC6 varient.
I'm especially confused by what those 0's mean.
and 29 is a surprising position for the toggle bit.
Hopefully, I'll have some time to look at the learned signals you said you'd post. |
|
Back to top |
|
|
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Wed May 25, 2005 12:37 pm Post subject: |
|
|
Quote: |
The new version of iMon-PAD uses NEC-type protocol with different timings.
|
Well actually this was said by someone in lirc forum. I was also confused about those 0's. I was trying to comare the .conf file of older iMon remote with this new .conf file. The older file didn't had 0's on one/zero lines.
Thanks for the prompt replies. As you may have noticed, this was my first post in the forum despite of the fact that I am using JP1 features extensively (Running extender on 8910) since last 1 year. I have found answers to just about every question using "search" button so far. |
|
Back to top |
|
|
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Thu May 26, 2005 10:41 am Post subject: |
|
|
I tried to upload file into "Diagnostic area" twice!! The uploaded file does not show up in th list some how. Does it take some time for it to b visible?
The file name is: Learned_keys_from_iMon-PAD.ir
Thanks,
pjigar |
|
Back to top |
|
|
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Thu May 26, 2005 10:46 am Post subject: |
|
|
I found the uploaded file!!
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1803
Experts, please take a look at this file and help me decode the protocol used by this remote. Once someone decodes the protocol, I would also like to learn how can I "create" the protocol upgrade using KM.
Thanks,
pjigar |
|
Back to top |
|
|
johnsfine Site Admin
Joined: 10 Aug 2003 Posts: 4766 Location: Bedford, MA |
Posted: Thu May 26, 2005 11:45 am Post subject: |
|
|
I don't expect to have any chunks of JP1 research time long enough to attack this in the near future. I don't know who else looks at such things. Assuming no one else does it and assuming I forget, please bump this in about a week to remind me. |
|
Back to top |
|
|
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Thu May 26, 2005 12:49 pm Post subject: |
|
|
Decoding the protocol is certainly uncharted waters for me, however, I am an EE and a hacker too. So if you can point me to some sites/deocumentation/etc where I can learn about how IR work, I can try to attack this from my side. I can also program as well.
If I am unccessfull then I will bump this thread up after a week, and every week there after |
|
Back to top |
|
|
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Thu May 26, 2005 1:45 pm Post subject: |
|
|
johnsfire,
I found some more information on the iMon-PAD remote and IR receiver. This is from forum which has developed iMon-PAD support for lirc.
venky has developed the driver for iMon-PAD in lirc project and he has also decodd the IR codees.
Apperently, iMon-PAD IR receiver is a special beast: It received the IR command, and decodes it in the firmware! Then it forwards the decoded command to OS via USB packets!!
But for JP1 purpose, all we are intereseted is the IR signal format, right?
Here is the thread which has more information on iMon-PAD remote and IR receiver.
http://venky.ws/forums/viewtopic.php?t=38
Hope this helps,
pjigar |
|
Back to top |
|
|
johnsfine Site Admin
Joined: 10 Aug 2003 Posts: 4766 Location: Bedford, MA |
Posted: Thu May 26, 2005 2:14 pm Post subject: |
|
|
I can't see anything in either of those links that looks even remotely related to the IR signals which were described by that Lirc file and learned into your .ir file.
That Format.txt file gives information details totally lacking in any context that could make it meaningful (I expect the intended audience is supposed to know the context).
As best I can guess, it isn't describing an IR signal at all. It is describing the OUTPUT from some IR to USB repeater and how that output is encoded when the input it receives is in NEC protocol.
But I still don't see any similarity between your Lirc file and NEC, and there is certainly no similarity between your learned signals and NEC. Whether the two are similar to each other is a harder question but they are at least similar to each other in the ways in which they are dissimilar to NEC. |
|
Back to top |
|
|
pjigar
Joined: 05 May 2005 Posts: 26
|
Posted: Fri May 27, 2005 9:30 am Post subject: |
|
|
I think I really confused everyone. As I understand, this iMon-PAD remote and IR are special pair.
1. iMon-PAD remote sends IR commands using 'some' protocol.
2. IR receiver decodes the raw IR command and then also converts the decoded command in to some "other" format before handing it to OS via USB interface.
What this means is lirc file describes th final format as seen by OS, not the raw decoded IR command. So lirc file is useless for our purpose.
You are right, the link I have provided was talking more about things "after" the command comes to OS. Not much helpful, I know, but I just wanted to point out this is not a normal rmote-IR receiver combo.
The only helpful this at this point is the learned IR file. I am also trying to get more information on th IR protocol format used from th comany who made this remote.
I will keep you posted. Thanks. |
|
Back to top |
|
|
johnsfine Site Admin
Joined: 10 Aug 2003 Posts: 4766 Location: Bedford, MA |
Posted: Fri May 27, 2005 9:44 am Post subject: |
|
|
johnsfine wrote: | It is describing the OUTPUT from some IR to USB repeater and how that output is encoded when the input it receives is in NEC protocol. |
So if I now understand you right, that OUTPUT is a USB encoding of an NEC IR signal, but that isn't the IR signal it actually received. It received some other IR signal and translated to NEC before encoding the IR waveform into a USB signal. |
|
Back to top |
|
|
gjarboni Expert
Joined: 20 Sep 2003 Posts: 294 Location: Columbia, MD |
Posted: Fri May 27, 2005 1:29 pm Post subject: |
|
|
Don't mean to jump in the middle here, but I've been following along and noticed some things.
1) The IR decoder doesn't send the on and off pulses to LIRC, only the decoded data (according to the person who wrote the special lirc driver for this receiver). That's why the one and zero times in the lirc file aren't needed (as in:
Basically the USB IR device does the decoding internally and passes the resulting 32 bit values over the USB bus. A special LIRC driver was needed to handle this new hardware and approach.
2) I don't remember the word to describe this, but the signals are the same time length. In other words all of the on and off times add up to the same value (57 time units). All of the on and off times are odd multiples (1,3,5,7). None of the signals have an off time of 1. All of the learned signals (except the mouse signals -- up, down, left, right) have each signal repeated twice with no toggle bit.
3) The learns for up,down,left,& right are bad (and take up a lot of the learned memory). pjigar, could you delete those signals and learn as many more buttons as you can (should be another 7 or 8 ). From reading the remote's web page (which claims a 30 millesecond response time), I'm guessing they are eliminating the leadout for the mouse commands. Either way, it looks like we'll have to deal with the directional arrows later. |
|
Back to top |
|
|
hansdegit
Joined: 06 Oct 2003 Posts: 39 Location: Schagen, Netherlands |
Posted: Mon May 30, 2005 2:26 pm Post subject: |
|
|
Bummer. I bought the Silverstone LC10M too, thinking "hey, what the heck, if it understands IR signals, then I can use my OFA6 to control the machine".
Apparently not. At least, not yet.
Does anybody have a clue? |
|
Back to top |
|
|
|