30323032 An Atlas DVR (day) IR/RF remote?

[Capn Trips]

Well, I received my 5 remotes today, and despite expecting a mix, all five are 1056 OCAPs!

The user's manual make no mention of learning, but the download (30333033) indicates 2Mb of learning memory, so will have to give it a try.

First I have to find some time to extract the device upgrades preloaded to see if they are new to the file section, before i start mesing with uploads and stuff.

We need to modify the rdf first. I've never done that.

Rob, what would be most useful? To post a raw IR dump of the remote?
A dump using the CURRENT 3033 rdf? And making a bunch of keymoves and/or macors to match buttons to keycodes?

[Evan_s]

Looks like you made out pretty well on your purchase then. I contacted the seller and it looks like I he's at least willing to try and work out some compromise with my non OCAP remotes since they didn't match the listing.

[The Robman]

Rob, what would be most useful? To post a raw IR dump of the remote? A dump using the CURRENT 3033 rdf? And making a bunch of keymoves and/or macors to match buttons to keycodes?

For the purpose of creating an RDF, always do a raw download. However, if there's already an RDF with the right signature, you can try using the RDF to see if the results make sense.

Anyway, if you need to create a new RDF, here's some starter steps...

1. Take a dump before you do anything on the remote.
2. Load up all FFs and then do a 981 reset, then take another dump.
3. If the remote has Sxx octal numbers on the PCB, compile a list and post them, otherwise program a bunch of macros to cover all the buttons on the remote (keeping track of what's what). Dump.
4. Play with the VPT, dump.
5. Play with any other programming options, dump.

[Capn Trips]

Got it. Opening up the remote seems problematic. I've opened up others (1994, 8910) in the past, but this seems a LOT tighter and snugger, I don't have access to some of the "nice-to-have" tools (my family and most of our household have moved back to the US while I finish up here in London for a few more weeks with almost no tools/equipment with me), and I fear for damaging it too much.

Evan, have you by any chance opened up one of your OCAP 1056 remotes? If so, a pic of the PCB would be VERY useful.

[Evan_s]

No I haven't opened any of mine up. I hadn't planned on opening anything up. I was hoping that it would be close enough to the existing remotes that wouldn't be necessary. Additionally I'll be out of town for a week starting saturday so I don't expect to have much time to play with it for a bit.

[Capn Trips]

OK. I pried one open and (drum roll) ...

the PCB does NOT have the octal Keycodes printed. Only the actual button names mirrored from the upper shell. Rats!

Well, while it's open, I thought I'd transcribe whatever I can read off the thing so here goes (no camera available, hence no picture(s):

on the bottom of the PCB-

UEI ATLAS DVR OCAP
URC-1056BG1
60062-1011100
DEC.2006 REV:04
FEB 27,2007

LT-2
0712

on the top-

obviously one can see all of the traces, and the button names are all reproduced adjacent to their respective buttons. There are also a number of labelled spots that appear to be missing components. Of interest:

LEDs 1 thru 5 are on the five device buttons - makes sense since these light up at various times;
LEDs 7-20 are missing. LED 7 would be on the SETUP key and LED 8 would be on the POWER key, whilst the remainder are disributed about the PCB, likely for backlighting. Obviously these optional LEDs would be present for a variant with backlighting.

There are also a number of "missing" transistors, resistors and capacitors. I presume they would be present if this was to have an RF transmitter, or possibly for learning. (I have yet to test learning, but the factory manual that came with it makes no mention of it, despite the IR download showing 2Mb of learning memory.)

Crappy cameraphone pics posted here, along with the raw downloads. Working on the macro-loaded downloads.

[Evan_s]

I wouldn't give up on the learning yet. There was no mention of it in my manuals either but the all the remotes seemed to accept the process altho I didn't really test actually learning a button and using or downloading it.

[vickyg2003]

I've got several Atlas remotes, and they all ACT like they are going to accept learning with the rapidly flashing LED, however I only have one that actually learns a signal to a key.

BTW Evan_s, please check your PM's.

[Evan_s]

Good to know. I'll have to actually test learning then. I assumed that if it didn't have learning that it would give some sort of error response, EG single long blink, and then not go into learning mode. The one I actually did the learn test with seemed to react to my button press on the other remote since it immediately stopped flashing the device button when I let up on the key on the other remote.

[Capn Trips]

OK, so here is what I did:

TuneIN1 is labelled "HELP" (on the generic UEIC support page it is "F1")
TuneIn2 is labelled "ON DEMAND" (also on the UEIC support page)
TuneIn3 is labelled "MY NEWS" (on the generic UEIC support page it is "F2")

(0) Before programming macros, the TuneIn keys had preprogrammed macros as follows (I did not actively delete these macros at any time (yet)):
(a) TuneIn1=CBL;9;6;0
(b) TuneIn2=CBL;9;2;0
(c) TuneIn3=CBL;B

(1) I then programmed the following macros:

(a) on the TuneIn1 key: Guide;Exit;Info;Menu;Settings;Day+;Day-;Pg+;Pg-
(b) on the TuneIn2 key: UP;DOWN;RIGHT;LEFT;SELECT;A;B;C;D
(c) on the TuneIn3 key: VOL+;VOL-;FAV;CH+;CH-;MUTE;LAST;Replay;LIVE
(d) on the Play key: REW;FFWD;STOP;PAUSE;REC;1;2;3;4
(e) on the List key: SOURCE;PIP On/Off;PIP Swap;PIP Move;PIP Ch+;PIP Ch-;*;0;#

(2) I then tested the programmed buttons. LIST and PLAY behaved as expected. The macro ran as programmed. the TuneIn buttons, however, alternated between running the original preprogrammed macro, and my programmed macro. Subsequent testing suggests that (in accordance with the User's Guide) the TuneIn buttons can "stack" up to five macros. This is similar to the behaviour of FAV keys on other remotes, right? These "stacked" macros do not properly display in IR, only the FIRST programmed macro is displayed. I then added the macros that I had programmed on TuneIn1, TuneIn2 and TuneIn3 to buttons 1, 2, and 3, respectively. Here is the IR Macro page display:


# Key Macro Keys Note
1 TuneIn1 CBL;9;6;0
2 TuneIn2 CBL;9;2;0
3 TuneIn3 CBL;B
4 1 GUIDE;EXIT;INFO;SETTINGS;phantom3;DAY+;DAY-;PageUp;PageDown
5 2 UP;DOWN;RIGHT;LEFT;SELECT;A;B;C;phantom1
6 3 VOL+;VOL-;FAV;CH+;CH-;MUTE;LAST;Replay;LIVE
7 List SOURCE;PIP On/Off;PIP Swap;PIP Move;PIP Ch+;PIP Ch-;[*];0;[#]/Enter
8 PLAY REW;FFWD;STOP;PAUSE;REC;1;2;3;4

So I can make the button name changes required:
old SETTINGS=new MENU;
old phantom3=new SETTINGS
old phantom1=new D

a couple of minor mods to the rdf will include:
"[#]/Aspect" instead of "[#]/Enter";
Add the colors to A-D;
Renaming the TuneIn1-TuneIn3 keys F1, On Demand, and F2, respectively.
Change all references to AUX to read VCR.

What changes need to be made to the rdf to display the stacking macros on the F1-F3 keys?

(3) Tried learning. Although the rapid blinking would start, no successful learns resulted. I suspect that the required components are amongst the ones absent from the PCB.

Will upload a draft modified rdf tomorrow.

[Capn Trips]

So I'm really gonna waste all of that learning memory unless somebody develops an extender for me

I presume that my excessive upgrades will naturally spill over, but my Keymove/Macro space is still limited.

[Capn Trips]

Here is my draft rdf. I made the changes outlined above and renamed it, leaving the same signature, but I get list index out of bounds errors when I try to use it in IR. Help?

Also, how do I turn this
into a RM image and map file(s)?

[binky123]

I didn't see the same error but saw a "string not terminated" error. Anyway, I changed the multimacro to OnDemand instead of "on demand" and I was able to get rid of the error and IR started up correctly.

MultiMacro buttons allow multiple macro entries to be assigned to that button so you can use IR to create another macro on that same button. IR allows up to 3 macros but I think the remote manual says it can have up to 5.

[gfb107]

Also, how do I turn this
into a RM image and map file(s)?

Map This - How To Create Maps for RM

[Evan_s]

LEDs 1 thru 5 are on the five device buttons - makes sense since these light up at various times;
LEDs 7-20 are missing. LED 7 would be on the SETUP key and LED 8 would be on the POWER key, whilst the remainder are disributed about the PCB, likely for backlighting. Obviously these optional LEDs would be present for a variant with backlighting.

I'm pretty sure your right about the LED backlighting being an option. The seller I have been dealing with offered me some alternative replacements and I'm pretty sure they are gonna be backlit atlas OCAP remotes. I'm assuming they will be the same sig but we'll see when they get here.

Check em out for yourself.
http://www.hifi-remote.com/forums/dload ... le_id=4970