Page 41 of 59
Posted: Sat Apr 23, 2011 6:56 am
by mathdon
Vynce wrote:I have an IR file that won't open in RMIR. I've tried re-saving it in IR 8.03 and I've tried opening it in RMIR 2.01 and 2.02 alpha. RMIR doesn't give any errors; the file just doesn't open.
I've fixed this in
RMIR v2.02 Alpha 2. In addition to this fix, Alpha 2 has two other minor changes:
- Change format of timing displays in Learned Signal Advanced Details to allow pasting as a timing list into IRScope.
- In decoding a learned signal, if a burst index is out of range, treat as zero duration but put error message in Misc column.
Posted: Sat Apr 23, 2011 11:25 am
by Vynce
Thanks for fixing it so quickly. I can confirm that it works for me as well.
Posted: Mon Jun 20, 2011 7:50 pm
by gfb107
Uploaded RM/RMIR v2.02 Alpha 3, adding the following:
- Fix incorrect inclusion of protocol code in exported binary files
Posted: Mon Jul 11, 2011 7:03 pm
by gfb107
Uploaded
RM/RMIR v2.02 Alpha 4:
- Save changes to General Notes
Posted: Sun Jul 24, 2011 12:16 pm
by mathdon
I have uploaded
RM/RMIR v2.02 Alpha 5. When Highlighting is selected in the RMIR Options menu, the Color columns in the tables now show as text the number of bytes of memory used by each item. This meets a feature request made some time ago by Capn Trips, and does so without introducing another column. I've left the column name simply as Color as I can't think of a better one.
Posted: Mon Jul 25, 2011 10:58 pm
by 3FG
This is a great feature! Now it is really easy to see how much memory a given feature takes up. Much quicker (and more accurate) than highlighting and counting.
Thanks!
Posted: Sat Jul 30, 2011 12:49 pm
by mathdon
I have uploaded
RM/RMIR v2.02 Alpha 6. The new feature here is that I have implemented a disassembler. This shows as a new pane in the Manual Settings dialog that opens when a protocol is added or edited, both in RMIR and in RM. This dialog has a table that shows the hex code of the processor for each processor type (although often there is code for only one type). If you select a row with hex code then a disassembly of that code shows in this new pane.
The longer term aim is to make the disassembly code editable and compilable, to provide RM/RMIR with similar facilities to Protocol Builder. I emphasise "longer term", however. I'm not promising a timescale, just an ambition at present!
In implementing this disassembler, I have drawn heavily on the code for the protocol disassembler in IR.exe, without which I would not even have attempted the task. My grateful thanks to its author.
Posted: Sat Jul 30, 2011 1:31 pm
by The Robman
Sounds great Graham! Is there a way to access the disassembler for regular (non-Manual) protocols?
Posted: Sat Jul 30, 2011 3:31 pm
by mathdon
The Robman wrote:Is there a way to access the disassembler for regular (non-Manual) protocols?
Sort of. In RM (as distinct from RMIR) you can disassemble any protocol that is not built in to the selected remote, i.e. which, when the remote and protocol are selected on the Setup tab, show up as a required protocol upgrade on the Output tab. If you then select Edit Protocol on the Advanced menu, the protocol hex will show in the Protocol Code box. Select that row and the disassembly will be shown in the new panel.
It should be easy to make ALL protocols, built-in or not, show up when Edit Protocol is selected, then they could all be disassembled. I'll look into that. It would be a good improvement.
Posted: Sat Jul 30, 2011 4:13 pm
by 3FG
Graham said: "In RM (as distinct from RMIR) ...."
Not sure what you mean, but it seems to me that the capability works using RMIR.
A quick test here shows:
Start RMIR and open a .IR file (apple_remote.ir--don't know where it came from.)
The device tab shows a device upgrade that uses PID 00 4B* and Protocol "Thomson", where the asterisk implies that the 00 4B executor wasn't native to the URC-8820 remote.
Clicking on Thomson in the protocol or PID columns brings up a "Manual Settings" window, which includes the disassembler. Clicking instead on the Device Type or Setup code column brings up the usual Device Upgrade Editor.
This new capability is excellent--my need to use IR.exe is just about done.
Posted: Sat Jul 30, 2011 10:25 pm
by The Robman
Thanks Graham, I just tried it and it works perfectly.
Posted: Sun Jul 31, 2011 4:31 am
by mathdon
3FG wrote:Graham said: "In RM (as distinct from RMIR) ...."
Not sure what you mean, but it seems to me that the capability works using RMIR.
What I meant was that if you use RM then you can disassemble ANY available protocol that is not built in to the selected model of remote, but in RMIR you are restricted to those protocols that are in that specific remote as upgrades.
3FG wrote:This new capability is excellent--my need to use IR.exe is just about done.
Thank you!

Posted: Mon Aug 01, 2011 8:06 am
by vickyg2003
Does this Alpha version contain 3FG's decodeir Alpha?
Posted: Mon Aug 01, 2011 9:45 am
by mathdon
vickyg2003 wrote:Does this Alpha version contain 3FG's decodeir Alpha?
DecodeIR is not part of the RemoteMaster.jar file and these Alpha versions only provide that jar file, so it depends on what full version you are importing the jar file into. There hasn't yet been a full version with 3FG's DecodeIR, so unless you have downloaded it separately the answer is no, but Greg has said he intends to include it in the next full release.
Posted: Mon Aug 01, 2011 10:04 am
by mathdon
I have uploaded
RM/RMIR v2.02 Alpha 7. This now shows the code of all protocols, for all processors, in the code panel of the Manual Settings dialog so that they can all be disassembled. Code that is not present as an upgrade is taken from protocols.ini and shown in gray.
As a reminder, editing a built-in protocol creates a custom version that is used by the remote in place of the built in version.