JP1 Remotes Forum Index JP1 Remotes


FAQFAQ SearchSearch 7 days of topics7 Days MemberlistMemberlist UsergroupsUsergroups RegisterRegister
ProfileProfile Log in to check your private messagesLog in to check your private messages Log inLog in

RM/RMIR v2.09 available

 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> JP1 - Software
View previous topic :: View next topic  
Author Message
mathdon
Expert


Joined: 22 Jul 2008
Posts: 3249
Location: Cambridge, UK

PostPosted: Sun Oct 20, 2019 11:46 am    Post subject: RM/RMIR v2.09 available Reply with quote

RM/RMIR v2.09 is now officially released.. This first release is build 6 as the first five builds were for development purposes. This is a major new version, incorporating IrpTransmogrifier by Bengt Martensson (Barf), and results from a cooperative effort with Bengt to whom I am very grateful. IrpTransmogrifier is now the default decoder for learned signals, though DecodeIR is still available through the menu item Options > Set IR Decoder. There is a new menu item Help > IrpTransmogrifier Protocols that provides documentation for IrpTransmogrifier that is equivalent to that for DecodeIR at Help > Interpreting Decoded IR Signals, which is still retained. Command files irptransmogrifier.bat (for Windows) and irptransmogrifier.sh (for Linux and Mac OS X) are provided for command-line access to IrpTransmogrifier itself from the RMIR installation folder, equivalent to those of the same names in a stand-alone installation of IrpTransmogrifier.

As a result of this change, a set of learned signals can now be converted to a device upgrade at the push of a button. There is a button Convert to Device Upgrade on the Learned Signals tab that does this. The intention is that almost all conversions of learned signals to device upgrade that can be performed manually can now be done through this automated process. This has become possible through entries in the protocol database of IrpTransmogrifier that link to entries in the RMIR file protocols.ini.

The supported platforms are 32-bit and 64-bit Windows, Linux and Mac OS X, together with experimental support for Raspberry Pi. This version now requires Java 8 or later, as that is the minimum Java requirement for support of IrpTransmogrifier. It supports all currently known types of UEI remotes, including XSight and Simpleset remotes. UEI has recently closed down the EZ-RC.com website that provided support for XSight and similar remotes. RM/RMIR provides complete replacement support for these remotes, including the ability to upgrade the firmware to the last version that UEI issued. XSight users new to RMIR, especially ones who have been directed here from the legacy page at EZ-RC.com, should read the Wiki article Getting started with XSight and Nevo for further information.

No special action is needed to perform a firmware upgrade on an XSight remote. Just do a download in the usual way. If a firmware upgrade is available it will be offered. You may install it or not, at your choice, and if you choose not to install it, you are given the opportunity not to be offered the upgrade again in future.

The XSight and Simpleset remotes are supported by RMIR directly via their USB interface, without the need for any cable other than the USB lead supplied with the remotes. Other remotes are supported through their JP1 6-pin connector with JP1.x interface cables that use an FTDI chip. These cables are also available with a Prolific chip instead of the FTDI one, but many remotes will not work with these cables. More information on this is given below. It is strongly advised that you use a cable with a genuine FTDI chip - there are also cables with counterfeit FTDI chips on the market and these too will often not work.

Remotes that support the Bluetooth UEI phone app can access RMIR through their Bluetooth interface, in several ways. All supported OS platforms can use the BLED112 Bluetooth dongle, currently available for $10.45 in the US or for GBP8.52 (UK 8 pounds 52 pence) in Europe. Windows users have two additional access methods. One uses the Bluetooth stack that is built in to Windows 10, but the remote needs v2.00 of the Bluetooth extender installed and this installation requires a one-off use of a JP1.x cable. The other is available both for Windows 10 and some earlier Windows versions (but so far only tested on Windows 8.1) and does not require this use of a JP1.x cable, but needs the installation of the BlueSoleil Bluetooth stack. See the Bluetooth thread Bluetooth is coming to RMIR for more details.

This first release build of RM/RMIR v2.09 is available only as a full installation package but subsequent builds will be issued both as a full package containing everything required and as an update package that contains only those files changed since this initial release. To upgrade from v2.08 without losing your settings, delete everything in your installation folder other than the RemoteMaster.properties file that contains your settings. Then unzip the new installation package into that folder and you are done. Alternatively, if you wish to keep your v2.08 installation and port your settings to v2.09, follow the full installation instructions below and then copy the RemoteMaster.properties file from your v2.08 installation to this new one.

The RMIR menu item Help > Check for updates checks for new builds as well as new versions. If a new build or version is available then this menu item displays a message containing a hyperlink that will take you straight to the available downloads for the update. To upgrade to a new build, just unzip the upgrade package into the installation folder for any earlier build of the same version, overwriting any files of the same name. Upgrade packages are cumulative, so it is not necessary to install each upgrade in turn.

To install the full package afresh, for any OS first unzip it to a new folder that is not read-only. For a Windows OS this means, in particular, that it should not be unzipped into a subfolder of the Program Files folder. After unzipping the package, do the appropriate one of the following:

  • If your OS is Windows then run Setup.vbs by double-clicking or otherwise. This will create three shortcuts, one each for RMIR and RMPB and the third (named Remote Master) for RM. They will be created in your installation folder, but they are also copied to Start > All Programs > Remote Master if you are running a Windows version that has a Start menu. You may copy them to your desktop, or any other location, as you wish. Setup.vbs also creates file associations to open .rmir files in RMIR, .rmdu files in RM and .rmpb files in RMPB.

  • If your OS is Linux then run Setup.sh from Terminal as a shell script. If the current directory in Terminal is the RemoteMaster installation directory then the command "sh Setup.sh" will run the script. It creates three .desktop shortcuts, one each for RMIR and RMPB and the third (named RemoteMaster) for RM. They will be created in your installation folder, but they are also copied to your $HOME/.local/share/applications folder to ensure that they appear on your Dash. Setup.sh will also add you to the dialout group of users, if you are not already in it. If you need to be added, then it will ask you for your sudo password as this step needs to be run with root privileges. This step is needed to enable RMIR to access USB serial ports without RMIR itself being run as root.

    The distribution also contains a text file linux_xsight.rules. If you have an XSight or Nevo remote, you may need to copy this to the directory "/etc/udev/rules.d/". It may be re-named if desired, provided the extension .rules is kept. This file provides a user-friendly name for the XSight as a USB device. Some users have found that Linux systems cannot find the XSight/Nevo remote unless RM/RMIR is run as root, even after running Setup.sh, unless this file is present.

  • If your OS is Mac OS X then there is as yet no special installation procedure.
With all three OS's, RMIR can be opened without using a shortcut by double-clicking or otherwise running the Java file RemoteMaster.jar. RM can be opened from RMIR with the menu item File > New > Device Upgrade and RMPB with the menu item File > New > Protocol. The instances of RM or RMPB so opened are independent of the RMIR instance from which they are opened, so you can then close RMIR and leave RM or RMPB open if you wish. RM can also be opened from a command line by running RemoteMaster.jar with an argument -rm and RMPB with an argument -pb. Please note that although it is optional to run Setup.vbs in Windows as RMIR, RM and RMPB can always be opened in these ways, in Linux you need either to run Setup.sh or to use some other means to add your user id to the dialup group of users. This need only be done once ever, however, as it is a system setting that is not specific to the RemoteMaster program.

A few remotes have an external 5-hole connector rather than the 6-pin connector in the battery compartment that is common in UEI remotes. These need an adapter to convert the 5-hole connector to the standard 6-pin one. Detailed instructions for making such an adapter are given here. Remotes that use a Maxim processor can all be connected with a standard JP1.2/3 interface cable but only one that uses the FTDI chip. Cables with chips of other manufacturers such as Prolific have difficulty communicating with the Maxim processors. This is discussed in some detail in this thread. The most recent processor used by UEI is from Texas Instruments. These can certainly be connected by JP1.2/3 cables with the FTDI chip. The situation with other chips is not yet known. These remotes can also be connected through their Bluetooth interface as described above.

When using XSight remotes (and similar ones such as Nevo) with Windows 8.1 and Windows 10, Enhanced Power Management needs to be disabled for the USB port concerned. RMIR v2.09 checks for this and displays a message saying exactly what Windows registry setting needs to be changed if it finds that this setting is still enabled. There is also an item "Enhanced Power Management info" under the RMIR Help menu that provides further information on this.

RMIR is available only as a Java file. Version 2.09 requires a Java 8 or later runtime environment, either 32-bit or 64-bit. Versions from 2.04 through 2.08 required Java 7 or later, version 2.03 and earlier only required Java 6. The release package includes the following support files:

  • DecodeIR v2.45 as library files for Windows (32-bit and 64-bit), Linux and Mac OS X.
  • jp12serial v0.24 as library files for Windows (32-bit and 64-bit), Linux, Mac OS X and Raspberry Pi.
  • digitmaps.bin with digit maps up to number 729.
  • protocols.ini which is a database of protocol executor data.
  • RMIR.sys that contains the data needed by RMIR to perform firmware upgrades of the XSight remotes.
  • The RDF File Specification, Version 4.
  • The RDF File Specification, Version 5 as revision 12 of an Addendum to Version 4.
An update to any of these files will result in a new build being released, so there is no need for separate updating of any of them. Version 4 of the RDF File Specification covers RDF files for remotes with interfaces up to JP1.3. Version 5 is required to support remotes with interfaces from JP1.4 onward. Version 5 is under continuous review as UEI remotes with new features are discovered, with revisions of the Addendum being issued as required.

Please visit the JP1 Community Wiki for information about how to use RMIR. A link to the Tutorial in the Wiki is also included in the Help menu. Please note that as this project is supported solely by volunteers, the Wiki may not be up to date. This version of RM/RMIR contains many new features required to support the newer types of remote. At the time of its release, these are not covered by the help files contained in the Wiki. RM/RMIR itself, however, shows notes and tooltips (the text shown when you hover the mouse pointer over a button or table entry) designed to make its use as self-explanatory as possible.

The download package is available in the following folder. Just click on it to start the download. The corresponding folder for future builds will contain both the full and upgrade packages.
Please see above for installation instructions.

Links:
The RemoteMaster project home page.
IrpTransmogrifier manual.
JP1 Community Wiki
Tutorial (part of the Wiki)
Getting started with XSight and Nevo (also part of the Wiki)
Nevo and XSight Remotes (thread specific to these remotes)
Bluetooth is coming to RMIR (announcement thread for the new Bluetooth interface)
RMIR XSight Support (development thread)
RMIR Simpleset Support (development thread)
RemoteMaster on Raspberry Pi with Raspian (development thread)
RMIR: Prototype IR function in RM (development thread)
IrpTransmogrifier: new program/library for IRP protocols (development thread for IrpTransmogrifier)
RM/RMIR v2.08 available (announcement thread for last official version)
ChangeLog.txt (also included in the installation package)
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


Joined: 22 Jul 2008
Posts: 3249
Location: Cambridge, UK

PostPosted: Mon Nov 04, 2019 9:12 am    Post subject: Reply with quote

I have now posted development build 7 of RMIR v2.09 in the RMIR Development folder on SourceForge. It is only available as an update to build 6.

Build 7 adds features needed to support the URC-2125BC0. It also makes a few improvements to the user interface and adds one new feature that affects all remotes with segments. This is the addition to the Device Buttons table of the General tab of a Setup Lock column. The flag in a device segment that sets a setup code lock was identified some time ago but not previously represented in that table.

This build includes RDF, map and image files for the URC-2125BC0 and URC62440, and also a replacement RDF for the URC2020B0-B1 that adds a note about its unusual connector. It also includes RDF4Spec_Addendum_rev13.pdf in the Docs folder, which has been updated from rev12 to include additions needed to support the URC-2125BC0.
_________________
Graham
Back to top
View user's profile Send private message
danich



Joined: 07 Oct 2019
Posts: 2

PostPosted: Tue Nov 05, 2019 5:17 am    Post subject: Memory leak Reply with quote

I faced bug with memory leak. Each file saving consume free memory and after few saving file be can't be loaded.

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=25705

1) Open 'my.rmir'. Memory usage: 3224 free
2) Save
3) Open 'my.rmir'. Memory usage: 3000 free
4) Save
5) Open 'my.rmir'. Memory usage: 2552 free
6) Save
7) Open 'my.rmir'. Memory usage: 1656 free
8) Save
9) Open 'my.rmir'. Error loading file.

Same problem also happened with 'blank' file (downloaded from remote after factory resetting)

I tried v2.08build7, v2.09build6, v2.09build7.
System Properties:
java.version = "1.8.0_201"
java.vendor = "Oracle Corporation"
os.name = "Linux"
os.arch = "amd64"

PS: Same problem on Windows
Back to top
View user's profile Send private message Send e-mail
mathdon
Expert


Joined: 22 Jul 2008
Posts: 3249
Location: Cambridge, UK

PostPosted: Tue Nov 05, 2019 10:11 am    Post subject: Reply with quote

Sorry for that, danich. As you discovered, the bug has been present in all recent builds. It is fixed in development build 8 , posted as before in the RMIR Development folder on SourceForge. Build 8 is only available as an update to build 6 of RMIR v2.09 or to development build 7 which was posted yesterday.
_________________
Graham
Back to top
View user's profile Send private message
danich



Joined: 07 Oct 2019
Posts: 2

PostPosted: Wed Nov 06, 2019 2:58 am    Post subject: Reply with quote

mathdon
Now it's working fine.
Thank you!
Back to top
View user's profile Send private message Send e-mail
Barf
Expert


Joined: 24 Oct 2008
Posts: 968

PostPosted: Sat Nov 30, 2019 6:57 am    Post subject: Reply with quote

I finally discovered the "Save" button on the "Learned Signal Timing Summary"! However, the csv thus generated is slightly flawed: If there is a repeat portion, a separate line is created, so importing breaks. Also the literal words "Once:" and "Repeat" are not really meaningful on every line in the table; they belong (possibly) in the header.

The following patch to LearnedSignalTimingSummaryDialog.java makes the csv import more usable.

Code:

Index: com/hifiremote/jp1/LearnedSignalTimingSummaryDialog.java
===================================================================
--- com/hifiremote/jp1/LearnedSignalTimingSummaryDialog.java    (revision 1667)
+++ com/hifiremote/jp1/LearnedSignalTimingSummaryDialog.java    (working copy)
@@ -593,6 +593,8 @@
     {
       out = new PrintWriter( new BufferedWriter( new FileWriter( file ) ) );
       String temp = summaryText.substring( summaryText.indexOf( '#' ) );
+      temp = temp.replaceAll("Once:\t", "");
+      temp = temp.replaceAll("\n\t\t\t\t\t\tRepeat:\t", "\t");
       temp = temp.replaceAll( "\"", "\"\"" );
       temp = temp.replaceAll( "\t", "\",\"" );
       temp = temp.replaceAll( "\n", "\"\n\"" );



PS. Consider using StringBuilder instead of String for such things.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mathdon
Expert


Joined: 22 Jul 2008
Posts: 3249
Location: Cambridge, UK

PostPosted: Sat Nov 30, 2019 6:41 pm    Post subject: Reply with quote

The Learned Signal Timing Summary code was written by Vyrolan, not me. I am happy to apply your fix, but I am not responsible for the issue.
_________________
Graham
Back to top
View user's profile Send private message
R2-M0



Joined: 14 Aug 2009
Posts: 81

PostPosted: Tue Dec 03, 2019 7:54 pm    Post subject: Reply with quote

Is there any chance that protocols.ini (or some related file) was corrupted in this build?

I ask because I updated RMIR this past weekend when prepping an upgrade for a new AVR I'd just purchased. After setting up the new receiver, I uploaded the new config to my RCRP05B... but the AVR refused to respond to a single command.

I'd upgraded from an older Denon to a newer model, and a second JP1 remote I had (which I hadn't yet updated) still worked to control the new AVR. When I downloaded the programming off that other remote to compare, however, the upgrade was identified as (I think) some Panasonic protocol and not Denon-K.

In desperation, I downgraded my RMIR back to 2.07 and tried again, and then my new upgrade worked like a champ.

Additional experimentation also showed that, when I open my .rmir file in 2.09, RMIR apparently changes something in it immediately -- because if I then try to open another file without saving the first one, I get a warning that the file contents changed even though I didn't touch a thing.

All of which makes me suspect that this latest version has its protocol wires crossed. All my other devices still seemed to operate fine, so the problem seems to be isolated to only certain protocols -- but Denon-K definitely seems to be affected.
Back to top
View user's profile Send private message
mathdon
Expert


Joined: 22 Jul 2008
Posts: 3249
Location: Cambridge, UK

PostPosted: Wed Dec 04, 2019 5:57 am    Post subject: Reply with quote

R2-M0 wrote:
Is there any chance that protocols.ini (or some related file) was corrupted in this build?

It is possible, since there was a substantial revision of protocols.ini for RMIR v2.08, in an attempt to remove many inconsistencies and inaccuracies that had crept in over the years. I am not aware of any corruption that was caused, but if you post the .rmir file that demonstrates this in the Diagnosis Area, with a link to it in this thread, then I will look into it.

The warning about file contents changed when you haven't deliberately changed anything does not necessarily mean an error. RMIR parses and interprets the setup file, then re-creates the setup data from its interpretation. This can result in changes that are of no significance, such as changing the order of data segments, but which still are flagged as changes.
_________________
Graham
Back to top
View user's profile Send private message
R2-M0



Joined: 14 Aug 2009
Posts: 81

PostPosted: Wed Dec 04, 2019 6:17 am    Post subject: Reply with quote

Much appreciated!

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=25750
Back to top
View user's profile Send private message
mathdon
Expert


Joined: 22 Jul 2008
Posts: 3249
Location: Cambridge, UK

PostPosted: Wed Dec 04, 2019 12:46 pm    Post subject: Reply with quote

Thank you for posting the file. Yes, there is an error in protocols.ini. One line has somehow got missed out. I will post a new RMIR build shortly with the correction and a few other minor amendments, but in the meantime you can fix this yourself. Open protocols.ini with a text editor and scroll down or search for the entry starting [Denon-K]. It will begin
Code:
[Denon-K]
PID=00 CD
DevParms=Device:4=4,OEM Dev1=84,OEM Dev2=50

It should begin
Code:
[Denon-K]
PID=00 CD
VariantName=2
DevParms=Device:4=4,OEM Dev1=84,OEM Dev2=50

so the VariantName line is missing. Just insert that line and all should be well.
_________________
Graham
Back to top
View user's profile Send private message
R2-M0



Joined: 14 Aug 2009
Posts: 81

PostPosted: Wed Dec 04, 2019 4:25 pm    Post subject: Reply with quote

Yep, that did it. All is now spiffy. Thanks, Graham!
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> JP1 - Software All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

Powered by phpBB © 2001, 2005 phpBB Group
Get Smart! the band's official homepage Rockabilly Central