JP1 Remotes

[davecs]

[mathdon]

I have now replaced RMIR v3.0.8 in the RMIR Development folder with v3.0.9.

This build adds a new entry to the Advanced menu. This is "Override Setup Validation". Setup Validation is an entry in the General section of an RDF which can take three values, Off, Warn and Enforce and in most RDFs is set to Warn. This new entry allows a user to override the RDF setting with a value that will apply to all remotes. It offers four choices, Default and the three RDF values. Selecting Default disables the override and so reverts to the RDF setting. This is the default option for this entry.

It also further revises Instructions.txt in the JP1EEPROMSupport folder to clarify that the method of locating pin 1 refers to the aperture in the case, not the markings on the PCB, and adds a link to the Wiki article to clarify the wiring of the Arduino.

@davecs:
I hope this new option achieves what you want. Please check and report back.
_________________
Graham

[stama]

I noticed a couple more issues with the "External Functions" feature of RMDU and added steps to reproduce them here: http://www.hifi-remote.com/forums/viewtopic.php?t=103352

[davecs]

[mathdon]

I have now replaced RMIR v3.0.9 in the RMIR Development folder with v3.0.10. This build fixes the bugs reported by stama in the Import function of the External Functions tab in RMDU.
_________________
Graham

[mathdon]

RMIR v3.0.10 is now officially released, unchanged from the development version with this number. This is the first official release since v3.0.3, as builds 4-9 were also for development purposes.

The changes since v3.0.3 are:

1. A new Settings panel for XSight Touch/Color remotes that allows the Language and Region settings to be changed.

2. A new Settings panel for XSight Lite/Plus remotes that allows the Language setting to be changed.

3. A new entry, Set Progress Bar Colors, on the Options menu to customise the colors of progress bars.

4. A new entry, Override Setup Validation, on the Advanced menu which allows a user to override the Setup Validation setting in the RDF (one of Off, Warn, Enable) with a value that will apply to all remotes. Selecting Default, which is the default entry, disables the override and so reverts to the RDF setting.

5. The Instructions in the JP1EEPROMSupport subfolder have been amended concerning connection to the remote, to clarify how to identify pin 1 and how to correct it if the connector is inadvertently connected the wrong way round. There is now also a link to the new Wiki article "Building the Arduino Interface for older remotes".

6. The RDF for the URC-7560 extender, EBX0EBV0 (URC-7560_7562 Extender).rdf, has been revised to support the new instructions for installing the extender with RMIR rather than IR.exe.

This build also fixes a number of obscure bugs that affected particular remotes in specific circumstances.
_________________
Graham

[mathdon]

The folder JP1EEPROMSupport in the RMIR installation package contains details about using an Arduino Nano to interface original JP1 remotes to RMIR. I am very grateful to user ylaviolette for finding that the instructions are incomplete if used in Windows 11, see this and following posts. I have revised the instructions to take account of Windows 11 and added them to the RMIR 3.0.10 files on SourceForge in a JP1EEPROMSupport folder. The revised instructions will be included in the next RMIR release but this is to make them available immediately.
_________________
Graham

[jackching]

I have a remote here that couldnt handle macros very well on the colored buttons if you include a device button within the macro. It was programmed using an rmir < 3.x. Should version 3.x be able to resolve including device buttons within a macro when programming to a colored button? Im asking because with this remote i have the wires soldered directly to the board and it is just easier to ask before i tackle it.

[mathdon]

You don't say what remote you have, which might help me, but what I can say is that much of the macro support has been substantially rewritten for RMIR v3.0.x so it is worth trying. Also I cannot provide help or debugging unless you are using the latest version, which is currently v3.0.10.
_________________
Graham

[jackching]

[mathdon]

If I understand you correctly, you are creating on the "On Demand" key a macro containing two keys, "On Demand" and "STB". This is a circular reference, the "On Demand" key being included in a macro on itself. A macro cannot call itself, so I think it will depend on the implementation in the remote how it handles this. This is not an RMIR issue. It does not surprise me that the macro calls the function on the "On Demand" key and then terminates. If the order is not significant, I suggest you put the "STB" key first in the macro, followed by "On Demand". If this does not work then you will have to put the macro on a different key from either of those used in the macro.
_________________
Graham

[jackching]

[mathdon]

When you press a key, there is a whole host of things that the remote checks before it actually performs the function assigned to that key. These include macros, keymoves, learning, punchthroughs, duration of keypress, repeat mode, special key type and others that I cannot think of at the moment. I do not know the order, or whether it varies between remotes. So it could be that the behaviour you are getting is because the apps and on demand buttons are set to punch through. The only way to find out is to try it. It is not surprising if you have found that different remotes behave in different ways in such circumstances as yours.
_________________
Graham

[jackching]

[mathdon]

Thank you for letting me know that you have sorted it and now have everything working the way you want.
_________________
Graham