Page 1 of 1

RemoteMaster v0.76 now available!

Posted: Mon Nov 17, 2003 11:49 am
by gfb107
I've built and released RemoteMaster v0.76

Changes for v0.76

- RM Maps-and-Images 1.08.zip
- RM Maps-and-Images 1.07.zip
- Added support for new Key Move format used by URC_6131 and Atlas DVR
- Remove all RDFs
- Correctly show "Look and Feel" and "Prompt to Save" settings at startup

Links:
RemoteMaster.v0.76.zip
Release Notes and Change Log (also included in the ZIP file)
Installation Instructions (also in the Readme.txt included in the ZIP file)
The ControlRemote project home page.

Re: RemoteMaster v0.76 now available!

Posted: Mon Nov 17, 2003 11:59 am
by Nils_Ekberg
gfb107 wrote:Added support for new Key Move format used by URC_6131 and Atlas DVR
Support is in RDF's V1.08

Re: RemoteMaster v0.76 now available!

Posted: Mon Nov 17, 2003 6:49 pm
by Mark Pierson
gfb107 wrote:Changes for v0.76

- Added support for new Key Move format used by URC_6131 and Atlas
This doesn't seem to be working properly. If I select the following:

Setup tab:
Remote: 15-1994
Device Type: Cable
Setup Code: 0000
Protocol: NEC1
Device: 1
Sub-Device: 1

Functions tab:
Assign EFC 255 to power

Buttons tab:
Assign power function to Shift-Power button

The resulting Device Upgrade Code is:
Upgrade code 0 = 00 00 (Cable/0000)
5a 00 01 20 7f 7f
KeyMoves
83 f4 00 00 00 c8
END

The Key Move data is wrong. It should be: 83 F3 00 00 A6

It appears that RM is creating 2-byte Key Move data for everything, regardless of the selected remote.

I am using the latest RDF set v1.08.

Re: RemoteMaster v0.76 now available!

Posted: Mon Nov 17, 2003 8:38 pm
by gfb107
Mark Pierson wrote:
gfb107 wrote:Changes for v0.76

- Added support for new Key Move format used by URC_6131 and Atlas
This doesn't seem to be working properly.

It appears that RM is creating 2-byte Key Move data for everything, regardless of the selected remote.

I am using the latest RDF set v1.08.
Yep, I used the wrong default value for AdvCodeFormat.
It should work if you set
AdvCodeFormat=HEX
in the RDF, but that shouldn't be required. Hang on a bit and I'll have another release.