Your Universal Remote Control Center
RemoteCentral.com
Philips Pronto NG Family Forum - View Post
Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Original thread:
Post 6 made on Monday June 11, 2007 at 16:11
johnsfine
IR Expert
Joined:
Posts:
September 2002
5,159
On June 11, 2007 at 15:47, roden said...
NEC Cutom Code: 1AE8h

Manufacturers almost never give the bit of information that tells you whether it is what MakeHex calls NEC1 vs. NEC2. Sometimes (rarely) they even say "NEC" when it is what MakeHex calls "NECx1" or "NECx2". So I would guess NEC1, but I'm not sure.

Also, many manufacturers express the custom code using an encoding different from that documented by NEC. So "1AE8" probably has the standard meaning, but that isn't certain.

MakeHex uses a "Device Number" instead of a Custom Code. The device number consists of the two halves of the custom code seperately converted to decimal: 1A hex is 26 decimal and E8 hex is 232 decimal, so in MakeHex that is
Device=26.232

Decimal: 84

Based on all the above best estimates:

NEC1 Device Code: 26.232 Function: 84
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0689 0157 0056 0015 0E94

If that isn't right, post a learned signal from the same device. That would tell me what the protocol and device code really are (using IrTool and DecodeIr.dll)


Hosting Services by ipHouse