Results 1 to 6 of 6

Thread: Major problem with IR passthrough of RC5 codes...

  1. #1
    Join Date
    Mar 2003
    Location
    Arizona
    Posts
    519

    Default Major problem with IR passthrough of RC5 codes...

    Ben,
    I cannot get ANY of the stock Marantz/Philips RC5 (and extended RC5) codes to work. It looks (not sure since the NRIRserv logging is not working) like the codes never even get to the USB-UIRT to be transmitted.

    Have you done any testing with RC5 codes?

  2. #2
    Join Date
    Mar 2003
    Location
    Arizona
    Posts
    519

    Default

    Ben, you around?

  3. #3
    Join Date
    May 2002
    Location
    CT
    Posts
    6,559

    Default

    Hi Aaron,
    I am now. I was away from the forum for a few days.

    Unfortunately RC5 codes are not supported at all via passthrough right now. This is something Jon and I were going to work on. It only supports learned codes, which is why you don't see it blip on the USB-UIRT.

    This is something I'll look into (RC5 to IR data) and hopefully Jon can present some insight.

  4. #4
    Join Date
    Mar 2003
    Location
    Arizona
    Posts
    519

    Default

    Cool... at least I know you know about it :lol:

    When do you think you might have the IR Learning features ready in NR? Since I have Marantz equip (RC5 codes!) I need to learn the codes... but alas... nothing to learn them with. :cry:

  5. #5
    Join Date
    May 2002
    Location
    CT
    Posts
    6,559

    Default

    Learning is one of the items on my next TODO list, now that 0.99 appears to be ready to go out the door.

  6. #6
    Join Date
    Jun 2003
    Posts
    11

    Default

    Quote Originally Posted by WickedEwok
    Hi Aaron,
    Unfortunately RC5 codes are not supported at all via passthrough right now. This is something Jon and I were going to work on. It only supports learned codes, which is why you don't see it blip on the USB-UIRT.

    This is something I'll look into (RC5 to IR data) and hopefully Jon can present some insight.
    The way the NRIRServ interface talks to IR hardware drivers is that it passes raw IR timing data. Because of this, the current architecture will only handle RC5 if an RC5->Raw interpreter is placed *inside* the NRIRServ program. If we want to do this another way, the NRIRServ API is going to need to change.

    -Jon

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •