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
Atlas 1054 SA
Moderator: Moderators
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Atlas 1054 SA
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
I tried to assign the Audio 2000 CD/AUDIO device by hand and didn't get a double blink confirmation either.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
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.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.