Ahanix Dvine5 HTPC w/iMon IR receiver

len · Post by **len** » Sat Aug 07, 2004 12:20 am

I recently purchased a multi media kit for an Ahanix Dvine5 HTPC case(http://www.ahanix.com/dvine5.html) which includes an iMon IR receiver built into a VFD. I have a working lirc config file for the remote that came with the IR receiver. I downloaded IR.exe 5.09, IRdecode.dll(latest version) and Remote Master 1.02(I don't have Excel) hoping to be able to reprogram my URC-8910. Here is what I did...

o I had the URC-8910 learn several keys from the iMon remote control

o Uploaded the URC content to the IR program to see what protocol was being used. A few keys came up as indicating they used the NEC protocol but most indicated they used the NEC1 protocol.

o I created a new SAT device(setup code 2000) on Remote Master based on the NEC1 protocol. Based on the information about "Learned Signals" in IR. I entered the EFC code of each "Learned Signal" under the "Functions" tab of Remote Master

o I mapped the functions to the 8910 buttons in the "Layout" tab of Remote master.

o Cut-n-Pasted the output for the Device Upgrade Code into IR.exe. into a new Device in IR.

o Uploaded the information to my URC-8910 and tested it in lirc with no luck.

What am I doing wrong here? If anyone can help I'd greatly appreciate it.

Below is information from my lirc config and information in IR..

Code: Select all

begin remote

  name  Ahanix_IMON
  bits           16
  flags SPACE_ENC|CONST_LENGTH
  eps            30
  aeps          130

  header       9000  4500
  one           625  1625
  zero          625   375
  ptrail        625
  repeat       8875  2125
  pre_data_bits   16
  pre_data       0x609F
  gap          12000
  toggle_bit      0

  frequency    38000
  duty_cycle   33

      begin codes
          App.Exit                 0x00000000000000FF
          Power                    0x000000000000807F
          1                        0x00000000000040BF
          2                        0x000000000000C03F
          3                        0x00000000000020DF
          4                        0x000000000000A05F
          5                        0x000000000000609F
          6                        0x000000000000E01F
          7                        0x00000000000010EF
          8                        0x000000000000906F
          9                        0x00000000000050AF
          0                        0x000000000000D02F
          Windows                  0x00000000000030CF
          Menu                     0x000000000000B04F
          App.Launcher             0x000000000000708F
          Function                 0x000000000000F00F
          Task.Switcher            0x00000000000008F7
          Back                     0x0000000000008877
          Select                   0x00000000000048B7
          Eject                    0x0000000000009867
          Delete                   0x00000000000018E7
          Up                       0x000000000000C837
          Right                    0x0000000000006897
          Down                     0x000000000000E817
          Left                     0x00000000000028D7
          Enter                    0x000000000000A857
          Vol-                     0x00000000000058A7
          Vol+                     0x000000000000D827
          Mute                     0x00000000000038C7
          Play                     0x000000000000B847
          Pause                    0x0000000000007887
          Prev                     0x000000000000F807
          Next                     0x00000000000002FD
          Rew                      0x000000000000827D
          Fwd                      0x00000000000042BD
          Stop                     0x000000000000C23D
          Open                     0x00000000000022DD
          Rec                      0x000000000000A25D
          Bookmark                 0x000000000000629D
          Thumbnail                0x000000000000E21D
          Aspect                   0x00000000000012ED
          DVD.Menu                 0x000000000000926D
          DVD.Caption              0x00000000000052AD
          DVD.Language             0x000000000000D22D
          Full.Screen              0x00000000000032CD
      end codes

end remote

Information about learned signals

Code: Select all

LEARNED SIGNALS:
#            Bound Device  Bound Key  Protocol  Device    SubDevice   OBC	Hex Cmd  EFC Misc
1            CD            L1         NEC       6  		             2     BF       183	
                                      NEC1      6  		             2     BF       183	
2            CD  	       L2         NEC1	   6  	                3     3F	    187

Sample Information about the new "SAT" in IR.exe

Code: Select all

Protocol ID: 5A
Fixed Data: 00 FF FF
Max Var Size: Empty Field

Keyname                 Hex Command          EFC
0                       2F                   059
1                       BF                   183
2                       3F                   187

Mark Pierson · Post by **Mark Pierson** » Sat Aug 07, 2004 4:05 am

It looks like you forgot to enter the Device (6) on the Setup tab in the RM upgrade.

jon_armstrong · Post by **jon_armstrong** » Sat Aug 07, 2004 6:00 am

If you don't want to learn all those commands you can translate the data in the "begin codes" section. Use numeral 1 for example, take the last byte "BF" and put in the hex command column in RM. The OBC (2)and EFC will be calculated for you.

This technique will only work in RM.

johnsfine · Post by **johnsfine** » Sat Aug 07, 2004 6:23 am

jon_armstrong wrote: This technique will only work in RM.

There is a way to enter hex commands in KM as well, which is mentioned in a few other threads on this topic. But since "len" said he doesn't have Excel, we can skip those details.

I wanted to warn that this method only works with some LIRC files. Jon is correct that it would work with this LIRC file. There are many other IR protocols and in many of them this method can't work. Additionally LIRC has more than one way to represent the same set of signals. I'm not sure what drives those decisions, but it can take a set of signals in this same (NEC1) protocol and represent it in other ways, that require other methods of extracting the hex command from the LIRC codes.

len · Post by **len** » Sat Aug 07, 2004 3:52 pm

thanks for the help, once I specified my device it worked just fine! As far as the conversion of the lirc info to RM layout I noticed that late last night after I had already "learned" the IR signals!

-Len

jon_armstrong · Post by **jon_armstrong** » Sat Aug 07, 2004 6:05 pm

len wrote:As far as the conversion of the lirc info to RM layout I noticed that late last night after I had already "learned" the IR signals!

Thats usually the way it works

BTW, that was one of the most thorough posts that I have seen in describing the issues.

Welcome to JP1

pjigar · Post by **pjigar** » Thu May 05, 2005 9:53 am

Please, upload your iMon device upgrade on JP1 yahoo group under misclelenious devices folder. I have also bought an HTPC case that comes with the iMon remote. I could benifit from your hard work.

Thanks,
pjigar

Post by **The Robman** » Sun Sep 25, 2005 4:20 pm

I built an upgrade file based on the info previously posted...
https://www.hifi-remote.com/forums/dload ... le_id=2217

hansdegit · Post by **hansdegit** » Tue Sep 27, 2005 7:14 am

I tried Rob's upgrade yesterday, assuming this iMon device also works for my Silverstone, see:

https://www.hifi-remote.com/forums/viewt ... 6&start=30

I always thought those iMon receivers were exactly the same....What am I overlooking?

Regards,
Hans

Post by **The Robman** » Tue Sep 27, 2005 8:51 am

If you look at the lirc config files, you'll see that they're completely different. The system described in this thread uses the common NEC1 protocol with a device code of 6. The button entries from the config file reveal the OBCs used, hence I was able to create an upgrade.

The system described in the other thread uses a totally unique protocol that I've never seen before. If you look at the data in the config file you'll see that it uses 3 or 4 bytes of data per button, and when I look at the signal itself, I can't see (yet) how to get it down to that few number of bytes.

You said that you tried my upgrade, but you didn't say whether it worked or not.

hansdegit · Post by **hansdegit** » Wed Sep 28, 2005 7:47 am

Rob said:
>You said that you tried my upgrade, but you didn't say whether it worked or not.

I tried this upgrade on my iMon vfd en it did not work, despite Rob's efforts.

Keep up the good work Rob! Your work is very much appreciated.

Post by **The Robman** » Wed Sep 28, 2005 8:51 am

What does your lirc config file look like? If it looks like the one in this thread, the upgrade should work, if it looks like the one in the other thread, it shouldn't work.

pjigar · Post by **pjigar** » Wed Sep 28, 2005 9:31 am

I think hansdigit has no idea about lirce config file. But I bet he has a IR receiver and iMon-PAD remote that uses the new remote.

handsdigit, Does your remote look like this? If yes then you are using the newer (mysterious!) protocol.

hansdegit · Post by **hansdegit** » Wed Sep 28, 2005 12:14 pm

Hi,

I have no clue whatsoever about lirc or winlirc. I do want to dig in to it, but for now, I'll stick to getting my URC 7562 to work with the iMon Pad. I hope some guru knows how to decode the protocol, otherwise I can't use the extender; I have almost the same problem as you do, pjigar.

Yes, my remote looks very, very similar to the one you mentioned in the previous post.

Again, thanks for all efforts.

JP1 Remotes

Ahanix Dvine5 HTPC w/iMon IR receiver

Ahanix Dvine5 HTPC w/iMon IR receiver

Can you post the upgrade at yahoo groups?