Weird problem learning IR codes from Pronto

[Ron]

Sadly this is not something Girder controls, you might want to ask the guys at evation about this, or try the IRserver just to be sure.

[SteveV]

Ron,

I've discovered some weird behaviour with Girder and Irman--at this point I'm not quite sure which is causing the error. The problem is that Girder occasionally recognizes 2 different Pronto RC5 Codes as identical strings. In all cases, the ir codes are adjacent.

For example: if I teach Girder Pronto IR Codes "RC5 0 28" and "RC5 0 29" Girder thinks they are the same IR string, in this case "54FC9781B844". Pronto indicates the hex values as:

RC5 0 28 => 5000 0000 0000 0002 0000 001c 0000 0000
RC5 0 29 => 5000 0000 0000 0002 0000 001d 0000 0000

Any thoughts?

Thanks -- Steve

[SteveV]

As a follow up, I have the same problem with Pronto Codes "RC5 12 51" and "RC5 12 52" which girder reconizes both as "66F89781B844". Again, these codes a quite close but should be recognized as unique.

Pronto indicates their hex equivalents to be:

RC5 12 51 => 5000 0000 0000 0001 000c 0033
RC5 12 52 => 5000 0000 0000 0001 000c 0034

I think that this is a fairly recent problem as my Girder file is now quite large and uses MANY adjacent codes which have and continue to work properly. I don't recall seeing this problem up until several releases ago. I guess it's possible that my Irman is screwy but that doesn't explain why the older adjacent codes still work.

Regards -- Steve

[Edited by SteveV on 04-06-2001 at 10:04 AM GMT]

[SteveV]

Thanks for the reply and sorry for implicating Girder as a possible source of the problem ;)

I've sent evation an email--hopefully they'll respond as quickly as you do.

Thanks -- Steve

[ccclapp]

Steve

Did you solve the problem of the RC5 codes? I am dealing with a similar issue.

Thanks

--Caleb

[SteveV]

Hi Caleb,

Despite the "posted" date of "13 Oct 2002", IIRC, this thread is over 2 years old.

I never did it solved--I switched over to a Slink-e shortly after running into this problem.

Sorry I couldn't be of more help :(

Good luck -- Steve

[ccclapp]

Hi Caleb,

Despite the "posted" date of "13 Oct 2002", IIRC, this thread is over 2 years old.

I never did it solved--I switched over to a Slink-e shortly after running into this problem.

Sorry I couldn't be of more help :(

Good luck -- Steve


...better late than never :D

Thanks