JP1 Remotes

mathdon wrote: Fri May 08, 2026 4:18 am I have posted RMIR v3.2.16 as a new official release on SourceForge.

Many thanks for all your effort, Graham!

Especially since this is an official release, can you please tag the code associated with this release when you have a moment? Thanks!

This odd behavior of the RCA RCRP05B remote's "POWER" button with regard to macros was noticed and described (albeit not with any extender involved) in a thread I began over 16 years ago, back when those remotes were new:

Observations on the RCA RCRP05B Remote's Behavior

There's other ...

Can you tell the difference between a genuine FTDI chip and a clone by looking at it?
Probably not with any real confidence.

I bought my 1st FTDI cable, a genuine one, from Mouser, back in 2009. Over the years since then, I recall a lot of back-and-forth in this cat-and-mouse game of "genuine ...

JP1.4 and JP2 remotes don't use the "break" mechanism to initate programming mode. Doh! Thanks for the education, 3FG. I should have delved into the 'jp12serial.cpp' source code a bit before commenting. Sorry for the noise, folks.

Aside: The situation was complicated enough back in 2009 ...

I have been doing some tests with RealTerm on a URC3680, which is also JP1.4, viewing the signals with a logic analyzer and don't understand what I find even with that remote. I can see with the analyzer exactly what RMIR sends when starting a raw download and what the responses are, and can send ...

The behavior of various HID devices with regard to wake-ability could be dependent on, among other things, the operating system. So it might help if you mention the operating system(s) on which you're interested in having this work.

Having said that, I'll report some of my experience testing this ...

Does anyone actually use CDE/Motif? Not much anymore and not with RMIR, but extensively in the past.
It looks like an old Unix style from pre-history. Ugly as sin. This is highly off-topic, but I cringe when I read people complaining about how "ugly" Motif is/was. It's like people complaining that ...

I have now posted RMIR v3.0.4 in the RMIR Development folder for testing. Graham, there's a minor typo in the "Set Progress Bar Text Colors" dialog's explanatory text, where an 'f' should be a 't' in the word "the". It's in 'RemoteMaster.java', on the 1st word of this line: + "fhe following one ...

davecs wrote:Can you tell me the location and name of the CSS files? It might be different in a different distro, but at least it might help me find it.

On Slackware 15.0, the top-level Gtk3 CSS file (from which you can '@import' other files or just add your CSS rules) is here:

I'm a little late to this (and I had to install Java on my Slackware 15.0 PC just now to run RMIR in order to be sure of what I'm saying), but I think I might have some helpful input...

When the "Gtk" look-and-feel option of RMIR is selected, it appears as though Gtk version 3 (not anything older ...

Delighted to hear that you're on the road to recovery, Graham! :D

I figured that your absence from the forum was probably because you were too busy improving the hospital's TV setup by building several programming cables and AIRWidgets, all after having ordered a batch of JP1-compatible remote ...

So very sorry to hear of your misfortune, Graham.

I have nothing but respect for and admiration of your intelligence, dedication, perseverance, and overall good-natured way of dealing with things.

Wishing you all the best in your surgery and recovery!

But the absence of the udev rules file in the regular (non-Debian) archive is really bad. I found FLIRC 'udev' rules under the "Trouble Shooting [sic]", "Linux" section on this site: https://flirc.gitbooks.io/flirc-instructions/content/title-page.html Had I not found them (or had they not worked ...

[...] So I was able to get it running. Glad to hear this!

I'd have mentioned more in my earlier post about the various issues (udev, libreadline, etc), but I wasn't sure how much of it would apply unless you were also running Slackware.

In my case, for 'libreadline', the problematic (for FLIRC ...

Thanks! I think I'll get one. I don't think you'll be disappointed. There's a lot yet to be tested with my FLIRC device, but so far, it's been mostly a positive impression.

The company behind FLIRC seems a bit under-staffed and sometimes even a bit unprofessional on their forum, but (so far) the ...