JP1 Remotes

If you have a typical interaction between a protocol variant and the remote model, such as Thomson protocol for a 7560, you need to select the protocol AFTER you select the remote model in order to get correct results.

The "7" variant of Thomson is in the 8060 and is available as a protocol upgrade for the many S3C80 models that lack Thomson entirely.

The base variant of Thomson is available only in a few of the older S3C80 models (and for some non S3C80 remotes).

If you select 7560 then Thomson, you correctly get the base version and don't need a protocol upgrade. If you select Thomson and then select 7560, you usually get the "7" variant and need a protocol upgrade which you shouldn't need and which would break Thomson device upgrades you may build the other way (Thomson protocol devices are rare in JP1, but if you have one, there's a greater chance that you have another).

Edit: Rereading my own post, I decided it was unclear whether this is a usage warning or an enhancement request. The answer is Yes. When Greg reads it, it should be an enhancement request. When others read it prior to that enhancement, it's a usage warning.

I noticed the same thing when I was fooling around with the various Dish network $0002 variants. I had to switch to an unrelated protocol after changing remote types and then back to $0002.

I didn't mean to imply this is just a Thomson issue. You should get this problem whenever you select protocol name and later switch from a model requiring a protocol upgrade to a model in which that same protocol upgrade could work but protocols.ini says to use a built-in version instead. RM fails to switch to the built-in version.

I'll include a fix for this in v1.01. Should be available soon.

All you had to do was ask: RemoteMaster v1.01 is now available!