Page 1 of 1

Atlas 1054 SA

Posted: Sat Oct 10, 2009 7:48 am
by vickyg2003
I've beeb trying to get my neighbors WOW Atlas to send a power off signal.

The existing keymoves read in as an error. So its no wonder that the keymoves don't work, but I've made an upgrade (Note I had to define 2 keys in the KM or RM, or this would not import into IR 8 RC6. However i uploaded this to the remote, and downloaded it again after use to make sure it wasn't doing a Reset, but the AUX device is sending a RCA signal, not the NEC signal I'm expecting.


What am I doing wrong????????

https://www.hifi-remote.com/forums/dload ... le_id=7355

Posted: Sat Oct 10, 2009 8:39 am
by mdavej
I don't know the solution, but I do see differences in the key moves, if that's any help.

As calculated by IR: 00 9D and 00 62

As read in error: 02 9D and 01 62

RMIR seems to have no problem reading it. IR reports an error (both version 7 and 8.01RC9).

Posted: Sat Oct 10, 2009 8:59 am
by vickyg2003
I tried to assign the Audio 2000 CD/AUDIO device by hand and didn't get a double blink confirmation either.

Posted: Sat Oct 10, 2009 12:12 pm
by binky123
This post mentions that keymoves on this remote are special.

Posted: Sat Oct 10, 2009 12:16 pm
by vickyg2003
This particular Atlas model shares a keymove limitation with the URC-6131. These two remotes do not understand normal keymoves, and cannot process keymoves for protocols that use more than one command byte. I'm not sure how RM is handling this in your case, but KM would simply not generate the keymoves.

How you work around this has been discussed before. You either have to create upgrades that use protocols with one-byte commands, or you have to make a dummy upgrade with the functions mapped to buttons and create the keymoves on the remote itself. You can create this type of keymove in IR also; you select the Key type instead of EFC or HexCmd.


Yes I get that it has a different style of keymove, but I can't even assign the upgrade to Aux. Something is definately hinky, binky.