JP1 Remotes

Try doing a 983 Signature blink back . If it is a JP1.2 remote, it will have a 4 digit sig starting with "1". JP1.3 signatures are 4 digits starting with "3", JP1.4 are 5 digits starting with "3", and JP2 are 5 digits starting with "2".

As mdavej pointed out, this remote uses a configuration GUI ...

This isn't JP1.4 (or JP1.4N); UEI don't always label the interfaces consistently. AFAIK the only Freescale processors that UEI have used that we know about were the HCS08 series in JP1.2 remotes.


For reasons not clear to me, the product number printed on this MCU "MCQE96C" is missing the digits ...

I have a remote for a Dish satellite box which was made by UEI and which I'd like to program with RMIR.

The back of the case says:
40.0 UHF 2G
FCC ID: MG3-2015
EchoStar Technologies L.L.C.
186228

And the circuit board inside says:
UEI Echostar Xip Freescale Remote
URC-2015BC0-R
60272-2231000 V05 ...

try this list
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=11788

That list contains just a few more, none of which work: 1/56 and 16/46 & 16/47.

Looks like chances are very high that no discrete power commands exist for this soundbar. Could you not simply rely on the Auto ...

Recently, some Sony components have sent device number 0-31 using Sony15 rather than Sony12. So I'd be sure to try all of the device numbers below 32 with both protocols.

Thanks for the suggestion. Unfortunately 1/46, 2/46, 4/55, 6/46, 7/46, 11/46, 15/46, 17/46, and 19/46 don't do anything ...

1. Device: Sony HT-CT60 / SA-CT60
2. Type of device: home theater speaker system / sound bar
3. Year: ~2012
4. JP1/UEI Remote model: OARUSB04G Extender 1.04
5. Do you have a JP1 cable? N/A, it's USB
6. Still have original remote? The Sony RM-ANU159, yes.
7. Checked the file section? Yup.
8. Checked ...

Well, apparently it had something to do with OSX or my MacBook. After trying everything I could think to with the MacBook short of formatting the remote, I booted up my old XP box to give that a shot. Worked first try, and the remote seems to be functioning again. Phew!

This echoes my experience ...