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.08 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: 4515
Location: Cambridge, UK

                    
PostPosted: Tue Jun 25, 2019 7:19 am    Post subject: RM/RMIR v2.08 available Reply with quote

Edit: RM/RMIR v2.09 build 6 is now available.

RM/RMIR v2.08 is now officially released.. The supported platforms are 32-bit and 64-bit Windows, Linux and Mac OS X, together with experimental support for Raspberry Pi. It fixes a number of bugs in v2.07 build 2, includes a new version of the jp12serial library, a substantial overhaul of protocols.ini by The Robman, and an updated digitmaps.bin. Many RDF files have been updated to correspond to the revisions to protocols.ini. It adds support for the URC-7880 and URC-7935. It provides additional ways to access the Bluetooth interface that do not require the specific BLED112 dongle and adds the URC-7880 to the URC-7980 and URC-7955 as the third remote that supports this interface. For more information on the Bluetooth interface, see the thread Bluetooth is coming to RMIR. This version also improves the error file rmaster.err by eliminating many spurious messages and clarifying others. Some of these new features have been available in development builds of RMIR v2.07 but this is their first official appearance.

This version supports all currently known types of UEI remotes, including XSight and Simpleset remotes. XSight support includes the very similar Nevo remotes and the rather different Monster Revolution 200. UEI still supports the Simpleset remotes via the Simpleset.com website, but it has recently closed down the EZ-RC.com website that provided support for the XSight remotes. RM/RMIR v2.08 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.

The Bluetooth interface can now be accessed 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 mentioned above for full details of all of these methods.

This first release build of RM/RMIR v2.08 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.07 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.07 installation and port your settings to v2.08, follow the full installation instructions below and then copy the RemoteMaster.properties file from your v2.07 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.

The inclusion of the RDFs, Maps and Images in the package means that the distribution zip file is now about 20MB. The RDFs are in a subfolder of the installation folder named RDF and the Maps and Images in one named Images. The full list of supported remote interfaces is now JP1, JP1.1, JP1.2, JP1.3, JP1.4, JP1.4N, JP2, JP2N, JP2.1, JP3, JP3.1, XSight (all types, mini-USB with S3F80 or HCS08 processor and micro-USB with MAXQ622 processor) and Simpleset (also referred to as JPS and also with MAXQ622 processor). The JP2, JP2N, JP2.1 and JP3 interfaces refer to remotes that use a Maxim processor, the MAXQ610 for JP2, JP2N and JP2.1 and the MAXQ612 for JP3. The difference between JP2 and JP2.1 is that JP2.1 uses a 5-pin in-line connector external to the remote rather than the familiar 6-pin connector in the battery compartment. The latest interface, JP3.1, uses the Texas Instruments CC2541 processor.

JP2.1 remotes need an adapter to convert the 5-pin connector to the standard 6-pin one. Detailed instructions for making such an adapter are given here. The interfaces JP2, JP2N, JP2.1 and JP3 can all be connected with a standard JP1.2/3 interface cable (JP2.1, of course, by means of the adapter) 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 JP1.4 and JP1.4N interfaces use the Samsung S3F80 processor and should work correctly with any JP1.2/3 interface cable. The JP3.1 interface, with the Texas Instruments processor, can certainly be connected by JP1.2/3 cables with the FTDI chip. The situation with other chips is not yet known.

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.08 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.

This RMIR version is available only as a Java file. Support for the separate stand-alone Windows compilation produced from the Java code with Excelsior JET has now finished. This multi-platform Java version requires a Java 7 or later runtime environment, either 32-bit or 64-bit. Note that this is a change from v2.03, which required only Java 6 or later. 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 revised for this RMIR version, including support for remotes that use Maxim and Texas Instruments processors.
  • 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.
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)
RM/RMIR v2.07 available (announcement thread for last official version)
ChangeLog.txt (also included in the installation package)
_________________
Graham


Last edited by mathdon on Sun Oct 20, 2019 11:50 am; edited 3 times in total
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Sun Jul 07, 2019 9:06 am    Post subject: Reply with quote

I have now posted development build 2 of RMIR v2.08 in the RMIR Development folder on SourceForge. To update build 1 of RMIR v2.08 to build 2, unzip the file RMIR208build2.zip into the installation folder for build 1, replacing any files with the same names.

Vicky (vickyg2003) has posted excellent detailed instructions here on how to use legacy cables with Windows 10. This covers both JP1USB cables with a Delcom chip and JP1.2/3 serial interfaces with a serial to USB adapter with a Prolific chip. Testing of the Delcom cable with RMIR found that uploads to JP1 remotes could fail with modern fast PCs as the interface sent data faster than the EEPROM in the remote could accept. Build 2 of RMIR v2.08 includes both 32-bit and 64-bit Windows versions of v0.04 of jp1usb.dll to replace v0.031 that was included in build 1. This fixes the issue by adding in a short delay where necessary. Build 2 also fixes two long-standing minor bugs in RemoteMaster.jar that did not affect the operation of RMIR but which could display incorrect data in certain rare circumstances.
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Wed Jul 10, 2019 8:26 am    Post subject: Reply with quote

I have now posted development build 3 of RMIR v2.08 in the RMIR Development folder on SourceForge. To update either build 1 or 2 of RMIR v2.08 to build 3, unzip the file RMIR208build3.zip into the installation folder for the earlier build, replacing any files with the same names.

Build 3 fixes an issue with macros in XSight remotes when the same macro is used both as a macro on a key and also as an activity macro. See this thread for more details. I have left build 2 also available in case the fix in build 3 causes unforeseen issues elsewhere.
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Sat Jul 13, 2019 11:45 am    Post subject: Reply with quote

I have now posted development build 4 of RMIR v2.08 in the RMIR Development folder on SourceForge. To update any of builds 1 to 3 of RMIR v2.08 to build 4, unzip the file RMIR208build4.zip into the installation folder for the earlier build, replacing any files with the same names.

Build 3 was aimed at fixing an issue with macros in XSight remotes when the same macro is used both as a macro on a key and also as an activity macro. I have found that this fix was incomplete. It fixed the downloading of a setup with such a macro but if it was then saved as a .rmir file and reloaded, the use of the macro as an activity macro was missing. Build 4 should provide a complete fix for this issue but I have left build 2 also available in case the fixes in build 4 cause unforeseen issues elsewhere.
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Sat Jul 20, 2019 11:56 am    Post subject: Reply with quote

I have now posted development build 5 of RMIR v2.08 in the RMIR Development folder on SourceForge. To update any of builds 1 to 4 of RMIR v2.08 to build 5, unzip the file RMIR208build5.zip into the installation folder for the earlier build, replacing any files with the same names.

Build 5 fixes a long-standing bug concerning the installation of an extender for the OARUSB04G 4000 (signature 257604). It does not affect the version of that remote with signature 257601 or any version of the URC6440 that is the European equivalent. See this and following posts in the thread "URC-6440/OARUSB04G Extender 1.04 now available" for more details.
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Tue Aug 06, 2019 5:18 am    Post subject: Reply with quote

I have now officially released build 6 of RMIR v2.08, both as an upgrade to build 1 or later and as a full installation package. This incorporates the additions and bug fixes present in development builds 2 through 5 but also includes one major new feature. I have intended for a long time to add to RMIR the same support for modem upgrades of legacy remotes as is present in the now-obsolete IR.exe. I have now done this. For general information on modem upgrade capability, see the article Modem Upgrade Procedure in the JP1 Wiki. Specific information on the new support in RMIR is given below.

Build 6 of RMIR v2.08 has four new menu entries. On the File menu there are Import from Wav and Export to Wav, while on the Remote menu there are Upload using Wav and Cancel Wav Upload. These are the same entries as are present in IR.exe and they have the same functionality. In IR.exe, however, the export facility required you to install the stand-alone IRToWav program and link IR.exe to it. RMIR also uses IRToWav but it is incorporated into RMIR so no such linkage is required. The entries are used as follows:

    * Export to Wav is enabled only when a setup for a modem-enabled remote is loaded in RMIR. It creates a .wav audio file that may be played with any sound app. A sub-menu allows you to select either the whole or specific parts of the setup for inclusion in the Wav upgrade file.

    * Upload using Wav is an audio player built in to RMIR for playing Wav upgrade files. It gives you the duration of the playback before asking you to confirm that you wish to continue. Playback is asynchronous so that RMIR remains available during the upgrade. During playback it shows a progress bar and playback may be cancelled before completion by clicking on the Cancel Wav Upload menu item.

    * Import from Wav reads a Wav upgrade file into RMIR. A sub-menu lets you select between creating a new image or merging into the currently loaded setup. The merge option is only enabled when the current setup is for a remote with modem capability. The new image option is always enabled and is equivalent to merging the upgrade into a new image created with the New option on the File menu. A Wav upgrade file contains the signature of the remote for which it is intended. The new image option uses a new image for this remote. The merge option allows you to merge into a different modem-capable remote but warns you in advance and requires you to confirm that you want to continue.

_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Sun Aug 18, 2019 8:50 am    Post subject: Reply with quote

I have now posted development build 7 of RMIR v2.08 in the RMIR Development folder on SourceForge. This is an update to build 6, which is the most recent public release. The update package contains only one file, a replacement RemoteMaster.jar file for that in build 6. To install the update, unzip the package into the installation folder for build 6, replacing any files of the same name. As the update contains only one file, you may however instead simply copy the new file into the installation folder to replace the existing RemoteMaster.jar file.

Build 7 adds the facility to create an HTML file, summary.html, that contains all the tabular data in the setup that is open in RMIR. There is a new item, Create Summary, on the File menu. Selecting this creates the summary file in your RMIR installation folder and then opens this with your default web browser.

Please see the separate announcement, New Summary feature in RMIR, for more details of this new feature. Please also post any comments on the Summary feature in that thread, not this one. Any bug reports or other comments unrelated to the Summary feature should continue to be posted here.
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Sun Sep 08, 2019 8:51 am    Post subject: Reply with quote

I have now officially released build 7 of RMIR v2.08, both as an upgrade to build 1 or later and as a full installation package. It is unchanged from its issue as a development version but is repackaged for official release. Please see the preceding post on the development issue for more details.

Please note that this is the final build of RMIR v2.08 and the final build of any version that will be compatible with Java 7. The next release will be RMIR v2.09 and will require Java 8 or later. For more information on the reasons for this change, and on what is to come in v2.09, please see the thread RMIR: The Next Generation.
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Wed Sep 11, 2019 4:50 am    Post subject: Reply with quote

I have now posted RMIR v2.09 build 1 in the RMIR Development folder on SourceForge. It incorporates Barf's IrpTransmogrifier so the RemoteMaster.jar file has more than doubled in size since RMIR v2.08. See the thread RMIR: The Next Generation for details of its new features.
_________________
Graham
Back to top
View user's profile Send private message
mathdon
Expert


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

                    
PostPosted: Sun Oct 20, 2019 11:57 am    Post subject: Reply with quote

RMIR v2.09 is now officially released. Please see the announcement thread for more details.
_________________
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
Top 7 Advantages of Playing Online Slots The Evolution of Remote Control