JP1 Remotes

RMIR v3.2.7 is now officially released. This is the first official release since v3.2.0, as builds 1 through 6 were for development purposes.

Here are the changes since v3.2.0. It makes a substantial update to the import of built-in setups for JP1.4 and JP2 remotes as setups have been found that were missing in v3.2.0, it adds support for UEI's manufacturer-specific TV Replacement Remotes that have not previously been supported and it fixes a few bugs.

The distinctive feature of UEI's manufacturer-specific TV Replacement Remotes is that the TV setup does not use setup codes. Setup is instead only by a search process. They appear to RMIR as an Activity with three button groups. The first group consists of the digits, volume and channel buttons together with the Power button, the other two groups containing all the other buttons. The setups for all three groups can be set independently, but the first group is restricted to a subset of the setups available for the second and third groups. There appear to be three generations of these remotes, each having significantly more facilities than the previous one. This build of RMIR supports all three generations, but as with all new remotes the support for each remote needs to be added by an expert.

The first generation, which uses a MAXQ610 processor, is simply as just described. It appears to RMIR as a fixed Activity with the ability to set the device for each of the three button groups by a search process, but that is all. The second and third generations are JP1.4 remotes that use a Samsung S3F80 processor. The second generation adds an internal (so non-selectable) device button that has no internal setup codes available. However, these remotes support device upgrades that can be selected as the device for this internal device button. It is not mentioned in the documentation for the remote, but the remote has two modes of operation. The Activity mode can be turned off and then all buttons use the device upgrade selected for the internal device button. These also support learning.

The third generation has significant extra features. These remotes have three internal device buttons which I have chosen to call TV, Cable and Audio. The Cable device is still a mystery but the Audio device serves as volume punch-thru both in Activity mode and when this mode is turned off. The Audio device IS set with setup codes, listed in the manual. These remotes support learning and also support macros, including three real-time macros on dedicated App keys.

The supported remotes of this sort, listed by generation, are:

First generation:
URC-1910 R00 for Samsung TVs (signature 257302)
Second generation:
URC-1910 R01 for Samsung TVs (signature 361302)
Insignia NS-RMTSNY17 for Sony TVs (signature 361701)
Third generation:
URC-4910 for Samsung TVs (signature 369302)
URC-4911 for LG TVs (signature 369401)
URC-4912 for Sony TVs (signature 369502)
URC-4913 for Philips TVs (signature 369602)
URC-4914 for Panasonic TVs (signature 369702)

To complicate the situation, however, there are exceptions. This build also supports two further TV Replacement Remotes that are set up differently. These are:

URC-4922 for TCL TVs (signature 371604)
URC-4923 for Roku TVs (signature 371503)

The URC-4922 does use setup codes. The TV model can be selected either by a Simpleset method or by direct code entry, with the manual containing a substantial list of codes. Like generation 3 it supports learning and macros, again with real-time macros on three dedicated App keys.

The URC-4923 differs again in that it supports nine setup codes but these are set with a single digit 1-9. It supports learning but not macros. It has eight dedicated App keys but these can only be set to specific apps from a list of 25, set by this app number.

Graham I never notice this before now
I think Starting from version 3.2.2 to the current version if I select
File>New>Remote Image and select the URC-3660 or Related ones
The Activity Tab does some odd behavior or can not be selected at all depending on the Version of RMIR it also writes a over 20Mb size rmaster.err file
I don't know if this is crucial or not but I thought you should be notified of this behavior

Randy, many thanks for pointing this out. It is a recurrence of an issue that I thought I had fixed. I think I have done so now, so after some more testing I will post a development version for you to test. Before I post another official release I will wait to see if any other bugs rear their heads.

Randy, I have now posted development build RMIR v3.2.8 in the usual place. Please let me know if this resolves the issue you identified.

I am very grateful for all the testing work you do for me. Many features would be missing and bugs remain if it wasn't for you. Thank you again.

Your Welcome
It is my pleasure testing RMIR
So far RMIR v3.2.8 performs as expected and my issue is now fixed
So time will tell if any other bugs appear

Needs More Testing But v3.2.8 is slower at upload and downloads compared to v3.2.7
Not sure if caused by interface set to Auto-Detect or not.
Will retry another time

HamburgerHelper1 wrote:Needs More Testing But v3.2.8 is slower at upload and downloads compared to v3.2.7

I can't see anything in the changes for v3.2.8 which might cause this, so if it is consistent, is it with any particular remote?

It's an issue running it in Linux
Tested jp1.3 and jp1,4 Remotes
Seems fine in windows but on Linux can take up to 30 seconds to find remote
I thought possible computer failure but tested on a different machine dual booting windows/Linux
So somehow v3.2.8 is different for linux
I am in the process of moving so not all of my Jp1 equipment is available to me as it is packed away

More Info
Even if I select dev/USB0 instead of auto it still takes 30 seconds to find remote
dev/USB0 works fine in v 3,2 7

I too have a dual-boot machine, Windows 11 and Ubuntu 20.0.4. I have just booted into Ubuntu, opened RMIR v3.2.8 and then downloaded and uploaded my URC-3660. It took just a few seconds for each, as normal. I can try a different remote or v3.2.7 if you like, or with files of yours if you send me some, but this first test suggests to me that the issue may be specific to particular Linux implementations. I cannot even speculate on why you get this issue in Linux and I do not.

I am Running Xubuntu 22.0.4 and 24.0.4
with every new version Linux seems to tighten up security
I logged into 24.0.4 as root and ran RMIR 3.2.8 and it performed very well
I logged out of root and logged in as a normal user and again RMIR 3.2.8 performed very well however it did not work on a 2nd computer with 24.0.4
and This method did not work for 22.0.4
I assume it is something like permissions or belonging to certain groups that is the problem

Thank you for these latest updates. It seems clear now that this is a Linux issue rather than something that needs fixing in RMIR, so I will regard v3.2.8 as OK, pending any further bugs coming to light.

HamburgerHelper1 wrote: I logged out of root and logged in as a normal user and again RMIR 3.2.8 performed very well however it did not work on a 2nd computer with 24.0.4
and This method did not work for 22.0.4
I assume it is something like permissions or belonging to certain groups that is the problem

Did you run setup.sh? What do you have in /etc/udev/rules.d? Directly after pluging in the "cable" do and

Here is results unfortunately with moving i do not have the time to pursue this
and it still puzzles me why RMIRV 3.2.7 works fine but not V3,2,8


RMIR WORKING COMPUTER=
ls -l /dev/tty????
groups
crw-rw---- 1 root dialout 188, 0 Jun 17 08:03 /dev/ttyUSB0
test adm tty disk dialout fax cdrom floppy tape sudo audio dip video plugdev users netdev lpadmin scanner

RMIR SLOW DOWNLOAD COMPUTER

ls -l /dev/tty????
groups
crw-rw----+ 1 root dialout 188, 0 Jun 17 07:55 /dev/ttyUSB0
test adm tty disk dialout fax cdrom floppy tape sudo audio dip video plugdev users netdev lpadmin scanner

Problem Solved
RMIR v 3.2.8 working fine now, no more slow downloads
What I did find though is that i had to have my FTDI cable plugged into the computer
before running setup.sh.
I was working on 3 computers the first time installing so i did not always have the FTDI Cable plugged in when I ran setup.sh
as long as the cable is plugged in when I ran setup.sh RMIR works as expected