JP1 Remotes

I've built and released RM/RMIR v2.02a

Edit by mathdon, January 6, 2015: Version 2.03 is nearly here. A pre-release of the Beta version is available here as RM/RMIR v2.03 Alpha 27. This includes support for XSight and Simpleset remotes through their USB port as well as JP1.x, JP2.x and JP3 remotes. If no further issues arise, Alpha 27 will be migrated to the SourceForge repository as v2.03 Beta.(End of edit.)

RemoteMaster (RM) is the device upgrade editor we're all familiar with, and is the Java equivalent of KM.
RMIR is the new Java equivalent of IR with RM fully integrated.

There is a lot of really cool new stuff here (especially if you haven't kept up with the Alpha and Beta releases).

In addition to everything that was in the v2.02 Beta 1.5v, I've included support for 64-bit Java under 64-bit Windows (DecodeIR and JP12Serial only)

Graham did the lion's share of the coding. Thanks Graham!

Please visit the RM and RMIR Wiki for information about how to use RMIR.

Changes for v2.02a There's probably more that I missed.

• Alpha
  • Fix bug that prevented fixed data being tested on download (Graham)
  • Prevent ArrayIndexOutOfBoundsException when loading a .rmir file containing a device upgrade with missing protocol code (Graham)
  • Fix bug that has prevented raw download from working since highlighting was added (Graham)
  • Show upload/download message in status bar during uploads, normal and raw downloads, and initializations to 00 or FF (Graham)
• Alpha 2
  • Change format of timing displays in Learned Signal Advanced Details to allow pasting as a timing list into IRScope (Graham)
  • In decoding a learned signal, if a burst index is out of range, treat as zero duration but put error message in Misc column (Graham)
  • Fix bug in recognising keycode key moves when AdvCodeFormat = EFC (Graham)
• Alpha 3
  • Enhancements to upload/download/memory initializations status
  • Upgrade to jp1usb.dll v0.031
  • Fix incorrect inclusion of protocol code in exported binary files
• Alpha 4
  • Save changes to General Notes
• Alpha 5
  • When Highlighting is active, show as text in the Color column the number of bytes used by that item (Graham)
• Alpha 6
  • Implemented disassembler in Manual Settings dialog (Graham)
• Alpha 7
  • Made code of built-in protocols visible in Manual Settings dialog, so that all protocols can be disassembled. (Graham)
  • Minor refinements to disassembler to handle certain error situations (Graham)
  • Corrected an error in protocols.ini, in that HCS08 code for NEC1 (pid 005A) had final byte E8 missing. (Graham)
• Alpha 8
  • Incorporate those predefined constants given in Protocol Builder read-me into the disassembler, using them in place of addresses where applicable (Graham)
  • Add comment column to disassembler and in it show some info about protocol data bytes (Graham)
• Alpha 9
  • Add interpretation of data bytes, in style of Protocol Builder, to disassembler in Manual Settings (Graham)
  • Add additional predefined constants, based on data from Mike England (Graham)
  • Fix bug in Hex indexOf routine, it was failing to check last position in file (Graham)
• Alpha 10
  • Add checkboxes to disassembler to select whether or not to use predefined constants (Graham)
  • Add radio buttons to disassembler to select display format for S3C80 working registers (Graham)
  • Save states of checkboxes and radio buttons in properties file between invocations (Graham)
  • Add button to hide/show upper left panel of Manual Settings, to make more space available for protocol data panel (Graham)
  • Add register addresses to pf and pd annotations in disassembly comments column (Graham)
  • Add a third tab, "PF Details", in Manual Settings to show interpretation of PF bytes bit by bit, for S3C80 and HCS08 only (Graham)
  • In the device upgrade editor:
  • Rename the Load button to Open, changed the mouse-over text to "Open a (RM or KM) device upgrade file." (Greg)
  • Rename the Import button to Paste, changed the mouse-over help to "Paste a (RM, KM or IR) device upgrade from the clipboard.", enhanced to accept IR-formatted upgrades containing Device Upgrade and Protocol Upgrade text (Greg)
  • Rename the Save button to "Save as..." (Greg)
• Alpha 10a
  • Change the Paste to simply pop up the Import Raw Upgrade dialog. so change the text to "Import Raw" (Greg)
  • The Import Raw Upgrade dialog will prefill its fields if it finds an IR formatted upgrade in the clipboard. Pasting an IR formatted upgrade into either the device or protocol code fields will parse the upgrade and update the appropriate fields in the dialog. (Greg)
• Alpha 11
  • Add a fourth tab, "PD Details", in Manual Settings to show normal usage of PD bytes, for S3C80 and HCS08 only (Graham)
  • Add a fifth tab, "Functions", in Manual Settings to provide descriptions of register and function addresses specified as predefined constants (Graham)
  • Fix bug in RM (only) preventing Cancel button in Prompt to Save from working correctly (Graham)
• Alpha 12
  • Change the button texts "Hide Upper" and "Show Upper" to "Expand" and "Collapse" (Graham)
  • Block the ability to select a protocol when the remote has a different variant of the same protocol built in and there is no Alternate PID (Graham)
  • Change the display of PFn Details to use drop-down boxes instead of plain text (Graham)
  • When editing a protocol, enter Manual Settings with the code for processor of current remote selected (Graham)
  • Restructure the disassembler code (Graham)
  • Add code for the main body of the assembler, though not yet linked to user interface (Graham)
  • Remove Primacy advanced menu item, move to Setup panel of Device Upgrade Editor (Greg)
  • In a device upgrade, you can now delete a function that is assigned to a button; all those assignments are removed as well (Greg)
  • Change Help -> Tutorial to point to JP Wiki page "JP1
  • Just How Easy Is It?
  • RM-IR Version" (Greg)
  • Upgrade to DecodeIR 2.43 (Greg)
  • Added NibbleSumChk translator class
  • Incorporated protocols.ini updates
  • Fix loading KM upgrades with Manual Protocols for remotes that use 2-byte pids. (Greg)
  • Show a dialog for entering PB-/KM-/IR
  • formatted protocol upgrades when the "Import Protocol Upgrade" button is pressed, instead of reading directly from the clipboard. (Greg)
  • Add assembler and protocol builder facilities (Graham)
• Alpha 12a
  • Fix two bugs preventing some protocols from loading or disassembling (Graham)
  • Enable an assembler line to be commented out by putting a semicolon at start of label field (Graham)
• Beta
  • Minor corrections to assembler/disassembler syntax for S3C80 and HCS08 (Graham)
  • Create separate displays for disassembly and assembly, switchable with radio buttons (Graham)
  • Add additional editing buttons for assembler (Graham)
  • Preserve the assembler copy/cut clipboard during changes of protocol and/or remote (Graham)
  • Add "Allow Preserve Control" to Options menu, that shows/hide the drop-down that controls whether OBC or EFC/Hex are preserved when changing protocols (Greg)
  • Updates to the About panels to give Graham more credit for the work he has done (Greg)
  • Create facility for user to specify an Alternate PID when there would otherwise be a conflict (Graham)
  • Maintain in Properties file a history of such Alternate PIDs used in uploads, or in copying protocol from output tab (Graham)
  • Use the Alternate PID history to help recognise protocols in downloads from remote or in importing .ir files (Graham)
  • Add item to Advanced menu of RMIR to clear Alternate PID history, which in its dialog also reports the number of entries in this history (Graham)
  • When RMIR minimized while Device Editor is open, automatically minimize Device Editor as well; also restore RMIR if Device Editor restored (Graham)
  • Correct bug introduced in Alpha 11 that caused RMIR to close if an RM opened from it by File/New/Device Upgrade was closed (Graham)
  • If more than about six entries in Protocol Parameters panel of Device Editor screen, make them scroll to limit maximum height of editor (Graham)
  • Fix permissions for DecodeIR.html and DecodeIR_ChangeLog.txt (Greg)
  • Make JP1 Parallel the last available interface (Greg)
  • Update Digit Maps through 520 (Greg)
• Beta 2
  • Rename "Clean Upper Memory..." to "Blast Upper Memory..." (Greg)
  • Fix preventing program to exit if properties could not be written (Barf)
  • Change how RM locates the properties file at startup, when not specified on the command-line (Barf and Greg)
  • Made installation directory read-only by putting rmaster.err in java.io.tmpdir, and (on non-Windows, Windows already had similar fix) putting resource file in home directory. (Bengt)
  • Allow editing of a built-in protocol with code missing from protocols.ini, to permit custom code to be entered (Graham)
  • When autodetecting interface, if returned port name is an empty string, treat at null, which solves issue of jp12serial port being found even when not connected (Graham)
  • Fix bug that repeated use of Edit Device button on General panel was not recognising changes made in earlier edit (Graham)
  • For S3C80 disassembly, label absolute addresses within the protocol code as well as relative ones, since CALL only takes absolute addresses and upgrades are executed from a standard location (Graham)
  • Skip blank lines when looping through Functions table of device editor (Graham)
  • When creating new key move with Function selected, correct bug that made default selection not be recognised (Graham)
  • Make RM windowClosing() be failsafe by adding a "finally dispose()"; already done for RMIR by Barf (Graham)
  • Add support for JP1.4 and JP2 remotes to existing facilities of RMIR (Graham)
  • Add support for JP1.4 Activities (Graham)
  • When RM is opened from RMIR, open it as a new application rather than as a window within RM, to prevent protocol crosstalk issues caused by RMIR and RM sharing same instance of ProtocolManager (Graham)
  • When an upgrade containing a Manual Protocol is deleted and that protocol is not used elsewhere, delete it also from ProtocolManager (Graham)
  • When adding a device upgrade, require the setup code not to clash with an existing upgrade (Graham)
  • Handle import of manual protocol when there is an existing manual protocol with same name and PID but different code (Graham)
  • Fix bug with import of KM file when OBC column is after, rather than before, the other column of hex (Graham)
  • Support change of PID of Manual Protocol when it is in use by more than device upgrade (already supported when used by only one such upgrade) (Graham)
  • Fix bug causing successive imports of KM files that use same protocol to interfere with one another (Graham)
  • Improve handling of pid change for Manual Protocol (Graham)
  • Bugfix: When an import or load of manual protocol checks it against those in ProtocolManager, test for same translators as well as same code (Graham)
  • Reset ProtocolManager before loading .rmir file, to prevent protocol crosstalk (Graham)
  • Provide facility in Device Upgrade Editor to convert custom code to a Manual Settings protocol (Graham)
  • Handle load and import in RMIR of an upgrade with same protocol but different custom code from existing upgrade (Graham)
  • Added translators BitExpander and GI3 (3FG)
  • Updated protocols.ini (3FG)
  • Added MAXQ610 code to protocols.ini where available (Graham)
  • Prevent entry of (user) alternate PIDs > 0x01FF when remote does not use 2-byte PIDs (Graham)
  • When closing RMIR from the window "close box (x)", make Prompt to Save open SaveAs() rather than Save() when filetype does not support Save action (Graham)
  • Improve the enabling/disabling of assembler buttons in Manual Settings dialog (Graham)
  • Fix bug causing RMIR to lock up if an upgrade is loaded that has a protocol which cannot be found (Graham)
  • Added support for MAXQ612 processor (Graham)
  • Added support for the new format for type 0xDB segments used in URC-7962 (Graham)
  • Added support for the new learned signal format used in the URC-7962 (Graham)
• Version 2.02a
  • Upgrade to DecodeIR 2.44 (with suppport for 64-bit Java on 64-bit Windows)
  • Upgrade to JP12Serial 0.19 (with support for 64-bit Java on 64-bit Windows)

Available downloads are:

• RemoteMaster.v2.02a.zip - (~1.9MB) Multi-platform Java program, works on Windows, Linux, Mac OSX, etc..
  • Requires a Java 1.6 or newer runtime environment.
  • Please read and follow the installation instructions
• RemoteMaster.v2.02a.exe - ( ~11.6MB) Windows standalone application
  • Compiled, packaged, and powered by Excelsior JET.
  • You must follow steps 4 and 5 of the installation instructions

Links:
The RemoteMaster project home page, now accepting donations.
RM/RMIR Wiki
Change Log (also included in the downloadable files)
Readme.html (also included in the downloadable files)
Tutorial (part of the Wiki)

When running on Linux as unprivileged user and there is no default 'LookAndFeel' set then at least under Ubuntu 12.04 the program crashes with a Null Pointer exception.

This can be avoided by inserting in ~/.remotemaster.properties

To protect against the crash the following patch is useful (see also my other post http://www.hifi-remote.com/forums/viewt ... &start=135)
Then the program does start and the preferred look and feel can be selected using the GUI.

In addition, also on Ubuntu 12.04 if text is displayed mostly in bold, it may help to remove the fonts-unfonts-core. This is a known bug.[/url]

Here how I set it up. I need some pointers on troubleshooting... ***** NO REMOTES FOUND *****

This is where I am stuck. How can I verify/troubleshoot this set up?

BTW, I have a VirtualBox WinXPSP2 working just fine on this Mac so the Mac and the cable are not the problem. In fact I used it to download the hand coded hacked TimeWarner remote I have, on which the keys are shot, and successfully uploaded to a brand new one!!

BOTTOM LINE: I would just like to FINALLY COMPLETELY cut loose of windows and do JP1 on my Mac.

Here is the Mac System Information about the JP1 USB Cable

May I suggest an UI improvement:

When entering a keymove, it would be great if one could enter Device Type, Setup Code, Device and OBC (just like one can when making an Upgrade). This would be great for people who do not know the EFC-5 or Hex.

And one usability improvement:

There should be a default path for maps and rdf files, e.g., in the same directory where the jar is located. If the maps and rdf files are found there, then RemoteMaster should not ask for a location upon first launch. Also, these locations should be defined as relative paths so that one can move around the app in the filesystem without having to change any configuration file.

I have found a (very) little problem with RM IR.
Perhaps that issue had already been addressed elsewhere,
but I haven't found such a topic.

RemoteMaster v2.02a (Standalone Windows version)

About Java IR:
...
System Properties:
java.version = "1.6.0_10"
java.vendor = "Excelsior, LLC"
os.name = "Windows XP"
os.arch = "x86"


In "RM IR", when I try to execute File|New|Device Upgrade
nothing happens.
My "File Monitor" says, that RemoteMaster tries to find javaw.exe,
but that file does not exist (I don't have Java installed.)

RemoteMaster v2.00 works fine (not searching for javaw.exe).

Starting RemoteMaster from the StartMenu works fine too.


(I there a better/correct place for bug reporting? )

I have updated RemoteMaster to version v2.02a. When you click on the About tab it says it is version v2.02a. When I click on Version Check tab it says Version v2.02a is available and that I am still using version v2.02 Beta 1.5w. Is this an error in the program or have I made an installation mistake?

Now I'm totally confused.

I can confirm, what PeteHarland wrote.

When I start RMIR from the start menu entry (that's "RemoteMaster.exe -ir"),
Help|About says" "RemoteMaster v2.02a".

Help|Check for update says:
"Version v2.02a of RemoteMaster is available, but you are still using
version 2.02 Beta 1.5w."

And that version has the (javaw.exe) problem mentioned above.

When I start RM from the start menu (that's "RemoteMaster.exe -rm"),
Help|About says: "RemoteMaster Device Upgrade Editor, v2.02 Beta 1.5w"

At least the Windows standalone version has that issue. Don't know,
if the "pure java" version has that version confusion too.

My RemoteMaster.exe file is 17724416 bytes in size and dated
27.11.2012, 4.33 pm (time may differ through time zones).

Uninstalled and reinstalled it (RemoteMaster.v2.02a.exe) - same thing.
What's going wrong here?

Btw.: Is there a difference between starting "Remotemaster.exe -ir" and
starting Remotemaster.exe without cmdline parameter?

I can confirm this as well. Even though I am using 2.02a:

- The about screen in RM incorrectly reports version 2.02 Beta 1.5w and the check updates feature in RM warns that I am on 2.02 Beta 1.5w and that a more recent version (2.02a) is available.

- The about screen in RMIR correctly reports version 2.02a but its check updates feature warns that I am on 2.02 Beta 1.5w and that a more recent version (2.02a) is available.

PeteHarland wrote:I have updated RemoteMaster to version v2.02a. When you click on the About tab it says it is version v2.02a. When I click on Version Check tab it says Version v2.02a is available and that I am still using version v2.02 Beta 1.5w. Is this an error in the program or have I made an installation mistake?

I do not know how this came about. Examination of the code suggests that it is impossible but it is certainly happening and is not an installation error. No similar behaviour has been observed in any subsequent development versions.

Edit: Further investigation shows that there never was a v2.02 Beta 1.5w. The last Beta was 1.5v. What happened was probably the following. I made the final amendments to Beta 1.5v and labelled it Beta 1.5w. I then passed it to Greg (gfb107) to do its official release as 2.02. I suspect he only recompiled the main module with the version number in it, which includes the "About" text. The separate module which performs the "Update" check was left with its earlier compilation, in which it had picked up the Beta 1.5w from the source code for the main module. I have checked, and this bug is present also in v2.02. The same single recompilation must have happened when Greg revised the main module to produce v2.02a. So the program really is v2.02a, it is only the "Update" display that is wrong.

spock wrote:RemoteMaster v2.02a (Standalone Windows version)

In "RM IR", when I try to execute File|New|Device Upgrade
nothing happens.
My "File Monitor" says, that RemoteMaster tries to find javaw.exe,
but that file does not exist (I don't have Java installed.)

Unfortunately this occurs due to a change in the way that RMIR opens a new instance of RM. That change was made to address issues resulting from the old way of doing it. It means that you have to open RM directly from its icon (or command line) instead of from RMIR via this menu item. I'm sorry for it but it is unlikely to be corrected as that is likely to be the last version of RM/RMIR issued with a Windows stand-alone version.

A trial release of RM/RMIR v2.03, labelled as Alpha 24, is available here. See also the first post in this thread.

Trying to use JRE 1.8.0_25 64-bit on Windows 8.1 64-bit, but when I talk to the remote, the JVM crashes. What's the proper JRE version to use?

Or is it a FTDI driver issue? I'm using this cable.

A 32-bit JVM works well.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180007c29, pid=10796, tid=14860
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ftd2xx.dll+0x7c29]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

sirjp1 wrote:Trying to use JRE 1.8.0_25 64-bit on Windows 8.1 64-bit, but when I talk to the remote, the Bathmate works well from https://peblueprint.com/bathmate-review now. What's the proper JRE version to use?

JVM is crashing for me on Windows 10 as well. I'm pretty sure I'm using the latest version of JRE too.

This is an old thread.
Head over here for newer version 2.03:
http://www.hifi-remote.com/forums/viewtopic.php?t=16086

sirjp1 wrote:Trying to use JRE 1.8.0_25 64-bit on Windows 8.1 64-bit, but when I talk to the remote, https://signalscv.com/2021/09/how-to-lo ... ut-weight/
how to lose weight fast
how to get skinny fast
how to be skinny fast
how to get skinny
how can i lose weight fast
shark tank weight loss
testogen gnc
https://www.fingerlakes1.com/2021/10/05 ... iew-guide/
sarms for sale
buy sarms
buy sarms online
where to buy sarms
sarms online
https://www.fingerlakes1.com/2021/09/20 ... roids-gnc/
crazy bulk review
legal steroids gn
legal steroids review
crazy bulk
steroids for sale
crazy bulk gnc
zantrex black reviews
modere trim reviews
shark tank weight loss
the JVM crashes. What's the proper JRE version to use?

Or is it a FTDI driver issue? I'm using this cable.

A 32-bit JVM works well.

#
# A fatal error has been detected https://www.stlcurioshoppe.com/v-tight-gel-review/ by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180007c29, pid=10796, tid=14860
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ftd2xx.dll+0x7c29]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

JVM is crashing for me on Windows 10 as well. I'm pretty sure I'm using the latest version of JRE too.

RM doesn't seem to work well with 64-bit Java on Windows. I had to uninstall the 64-bit version to get it working properly. Even trying some tricks to make it use a 32-bit version when both were installed didn't work.