RM bug(?) with Panasonic (old) protocol

Capn Trips · Post by **Capn Trips** » Mon Mar 21, 2005 4:27 am

When trying to create an RM 1.20 upgrade for my Scientific Atlanta Satellite receiver, I enter the protocol (Panasonic (old)) on the setup page, and then the correct device number (27) for device 1. Since my IR learns (all very clean ) showed multiple EFCs and Hex decodes, I opted to enter OBC (which I usually do, anyways), but on the functions tab the only function for which I can successfully add an OBC is number 0, as soon as I enter any subsequent OBC for any other function, the program hangs up.

I've looked at the Scientific Atlanta upgrade HERE which is an RM fiile with the same basic parameters, and it looks fine, but exhibits the same behaviour when I try to enter (or change) any OBC other than the one in line 1.

I also did a cross-check using KM, and a similar problem occurs

I can enter the OBC for the entry for the first function, and the corresponding EFC and Hex are filled in by KM, but any subsequent OBC entry for other functions is ignored. It doesn't hang up the program, but yields no auto-filling in of the remaining fields.

Is there a problem with Panasonic (old) and KM/RM? or is it just me? Should I be using a different protocol deaspite the clean learn/decode?

Edit: Upon further experimentation I found this odd behavior repeated in multiple protocols, so I re-installed both RM and KM. I'm not 100% certain, but it appears that in RM, the OBC column presumes/requires entries in base 6, as any imported numbers never display a digit greater than 5 in them - not sure whether this is true for all protocols, or just a glitch with the Panasonic (old). Still looking at KM to see if I've "fixed" it.

gfb107 · Post by **gfb107** » Mon Mar 21, 2005 7:50 am

You've definitely found a bug in RM. Expect a fix later today.

Capn Trips · Post by **Capn Trips** » Mon Mar 21, 2005 7:59 am

For what it's worth, I've been farting around with this for a bit and have discovered the following specific symptoms:

RM will not display OBCs in decimal for a select group of protocols, in particular, the ones I have found include:
Acer Keyboard - maximum character OBC column will display = 6
Akai - 6
DISH Network - 5
NRC 17 - 7
Panasonic (old) - 5

I just sort of did a spot check of random protocols, in which the majority worked, but those above popped out at me - base 7 for Akai? Base 6 for DISH and Panasonic (old)? Base 8 for NRC17?

Also, whenver I change the RM protocol to Panasonic (old), I can no longer change protocols - the program will not update and I have to open a new instance of RM.

Hope this helps.

The Capn

gfb107 · Post by **gfb107** » Mon Mar 21, 2005 8:08 am

The bug you found is not specific to any single protocol.

Post by **The Robman** » Mon Mar 21, 2005 9:50 am

I seem to remember also that there's a bug in KM for the Panasonic (Old) protocol where the numbers that you enter in the byte2 column to select the device code aren't correct. I don't recall if this bug was ever fixed. I don't think the bug was propergated over to RM but I'm not positive.

gfb107 · Post by **gfb107** » Mon Mar 21, 2005 11:00 am

The fix for this is now available.