Home AMX User Forum AMX General Discussion

Anyone know this form of Hex

I am working on a project that the client has a Hitachi Alpha series LCD. I have tried all the ir codes I could find but none of them have the discrete codes for HDMI inputs 4 or 5. So I found this document from Hitachi and it lists all the inputs but I have no idea what R Hex Code is. I have not had a chance to try bringing these into IREdit as I got a new laptop and can't get it to install even as admin and compatibility to XP SP2 or 3. IRCodeDoctor sees it as invalid format.

Discrete Code Table
AV1 = 50AF 21DE
COMPONENT 1 = 50AF 22DD
COMPONENT 2 = 50AF 23DC
AV2 = 50AF 24DB
HDMI 1 = 50AF 3DC2
HDMI 2 = 50AF 20DF
HDMI 3 = 50AF 25DA
TV = 50AF 7689
4:3 = 50AF 6798
AUTO = 50AF 6897
ZOOM 1 = 50AF 6996
ZOOM 2 = 50AF 6A95
16:9 = 50AF 659A
FULL = 50AF 7788
EXPANDED = 50AF 6699
E.SAVE MINIMUM = 50AF 54AB
E.SAVE MEDIUM = 50AF 55AA
E.SAVE MAXIMUM = 50AF 56A9
POWER OFF = 50AF 3FC0
POWER ON = 50AF 3EC1
DYNAMIC = 50AF 6C93
CUSTOM = 50AF 748B
PRO NIGHT = 50AF 758A
PRO DAY = 50AF 7A85
HDMI 5 = 50AF 26D9
HDMI 4 = 50AF 27D8
VGA = 50AF 2CD3

Comments

  • a_riot42a_riot42 Posts: 1,624
    I am working on a project that the client has a Hitachi Alpha series LCD. I have tried all the ir codes I could find but none of them have the discrete codes for HDMI inputs 4 or 5. So I found this document from Hitachi and it lists all the inputs but I have no idea what R Hex Code is. I have not had a chance to try bringing these into IREdit as I got a new laptop and can't get it to install even as admin and compatibility to XP SP2 or 3. IRCodeDoctor sees it as invalid format.

    Discrete Code Table
    AV1 = 50AF 21DE
    COMPONENT 1 = 50AF 22DD
    COMPONENT 2 = 50AF 23DC
    AV2 = 50AF 24DB
    HDMI 1 = 50AF 3DC2
    HDMI 2 = 50AF 20DF
    HDMI 3 = 50AF 25DA
    TV = 50AF 7689
    4:3 = 50AF 6798
    AUTO = 50AF 6897
    ZOOM 1 = 50AF 6996
    ZOOM 2 = 50AF 6A95
    16:9 = 50AF 659A
    FULL = 50AF 7788
    EXPANDED = 50AF 6699
    E.SAVE MINIMUM = 50AF 54AB
    E.SAVE MEDIUM = 50AF 55AA
    E.SAVE MAXIMUM = 50AF 56A9
    POWER OFF = 50AF 3FC0
    POWER ON = 50AF 3EC1
    DYNAMIC = 50AF 6C93
    CUSTOM = 50AF 748B
    PRO NIGHT = 50AF 758A
    PRO DAY = 50AF 7A85
    HDMI 5 = 50AF 26D9
    HDMI 4 = 50AF 27D8
    VGA = 50AF 2CD3

    For AMX IR to work you need the Pronto type hex codes which are usually a few dozen strings of hex for each command. Hopefully you can find these on Remote Central, or use serial or IP control.
    Paul
  • a_riot42 wrote: »
    For AMX IR to work you need the Pronto type hex codes which are usually a few dozen strings of hex for each command. Hopefully you can find these on Remote Central, or use serial or IP control.
    Paul

    Thanks, I know I need that and I've searched all of the codes at Remote Central and none have the ones I need. The Tv doesn't have IP or RS232 or I would use that, I prefer to. I'll have to look at the Hex on the codes that I have and see if I can come up with something of converting what is in that table
  • a_riot42a_riot42 Posts: 1,624
    Thanks, I know I need that and I've searched all of the codes at Remote Central and none have the ones I need. The Tv doesn't have IP or RS232 or I would use that, I prefer to. I'll have to look at the Hex on the codes that I have and see if I can come up with something of converting what is in that table

    If you have an AMX IRIS device you can capture the remote codes which will then get converted to Pronto codes in IR Edit so you can create your own IR file. No AMX programmer should be without one for these types of situations.
    Paul
  • banobano Posts: 173
    I am working on a project that the client has a Hitachi Alpha series LCD. I have tried all the ir codes I could find but none of them have the discrete codes for HDMI inputs 4 or 5. So I found this document from Hitachi and it lists all the inputs but I have no idea what R Hex Code is. I have not had a chance to try bringing these into IREdit as I got a new laptop and can't get it to install even as admin and compatibility to XP SP2 or 3. IRCodeDoctor sees it as invalid format.

    Discrete Code Table
    AV1 = 50AF 21DE
    COMPONENT 1 = 50AF 22DD
    COMPONENT 2 = 50AF 23DC
    AV2 = 50AF 24DB
    HDMI 1 = 50AF 3DC2
    HDMI 2 = 50AF 20DF
    HDMI 3 = 50AF 25DA
    TV = 50AF 7689
    4:3 = 50AF 6798
    AUTO = 50AF 6897
    ZOOM 1 = 50AF 6996
    ZOOM 2 = 50AF 6A95
    16:9 = 50AF 659A
    FULL = 50AF 7788
    EXPANDED = 50AF 6699
    E.SAVE MINIMUM = 50AF 54AB
    E.SAVE MEDIUM = 50AF 55AA
    E.SAVE MAXIMUM = 50AF 56A9
    POWER OFF = 50AF 3FC0
    POWER ON = 50AF 3EC1
    DYNAMIC = 50AF 6C93
    CUSTOM = 50AF 748B
    PRO NIGHT = 50AF 758A
    PRO DAY = 50AF 7A85
    HDMI 5 = 50AF 26D9
    HDMI 4 = 50AF 27D8
    VGA = 50AF 2CD3

    Give this a try: http://files.remotecentral.com/view/5899-15034-1/rc5_to_hex_conversion_tool.html
  • John NagyJohn Nagy Posts: 1,740
    bano wrote: »
    Nothing is the cause of something in the absence of which it nevertheless occurs

    Oh how I wish that were universally believed.
    One of the only two jobs we ever failed in was a large home with 44 controlled rooms and 36 touch panels. The panels oscillated on and offline on a predictable 20 minute cycle. The customer, dealer, and AMX blamed us, the software. So we purged the system of -any- software and restarted with a clean NetLinx and empty panels, and the behavior was the same. Some still maintained that we caused it anyway. Ultimately AMX was removed from the job too.
  • a_riot42a_riot42 Posts: 1,624
    John Nagy wrote: »
    Oh how I wish that were universally believed.
    One of the only two jobs we ever failed in was a large home with 44 controlled rooms and 36 touch panels. The panels oscillated on and offline on a predictable 20 minute cycle. The customer, dealer, and AMX blamed us, the software. So we purged the system of -any- software and restarted with a clean NetLinx and empty panels, and the behavior was the same. Some still maintained that we caused it anyway. Ultimately AMX was removed from the job too.

    That couldn't have been that difficult to fix, especially when its doing this so regularly. Had it been random, I can understand a little more.. Clearly its either a network issue or power issue of some kind if empty panels, and no source don't stop the issue. I'm surprised you didn't figure that one out, and move forward.

    I've seen some pretty strange things occur, but haven't yet needed to abandon a job. I had one large project in Telluride CO where every once in a while, perhaps a few times a week, a huge "crack" would come through the very expensive living room BW speakers. The noise was so loud and sudden you'd jump out of your skin, and it didn't matter whether the system was on or not. The only information I had was that when it happened, someone had hit a button on a litetouch keypad that triggered the fireplace to come on. Can you figure out what it was?
    Paul
  • John NagyJohn Nagy Posts: 1,740
    Were we permitted to work on the network, I agree that it "should" have been able to be found. The customer had his own IP guy (same one he employed at his company) and only he could make any changes. Proofs like the no-software test fell on deaf ears, and ultimately shifted a share of the blame to AMX, with the argument that their product could not maintain a connection on a perfectly good network. The customer resorted to yelling about fingerpointing and pulled the plug.

    Re: loud crack: Ground? Spark-style ignighter?
  • a_riot42a_riot42 Posts: 1,624
    John Nagy wrote: »
    Re: loud crack: Ground? Spark-style ignighter?

    Yes. The prewire team had bundled the speaker wires in with the fireplace igniter cabling, sending a huge voltage to the speakers at random intervals whenever it was turned on. Didn't even need the power amps. The wiring was laid behind the fireplace so it was not easy to get at and part of the fireplace had to be disassembled. It would have sucked had I not been correct about the source of the problem, after they dismantled it all. It had to be fixed as it was going to give someone a heart attack from fright whenever it occurred. What was weird was that it didn't occur every time, only once every 20 times, so when I tried it, it never happened, but then the client would and I would get a frantic call, but then couldn't reproduce it. Very frustrating, but we figured it out and got it fixed at our expense. Somehow those BW speakers still worked!
    Paul
  • a_riot42 wrote: »
    If you have an AMX IRIS device you can capture the remote codes which will then get converted to Pronto codes in IR Edit so you can create your own IR file. No AMX programmer should be without one for these types of situations.
    Paul

    I do have an IRIS, but the remote does not have discrete codes for inputs. Below is one that I know works and is for AV1.

    So somehow 50AF 21DE translates to (from a file for a :
    0000 006D 0022 0002 0154 00AB 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 0015 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 003F 0016 05E6 0154 0054 0016 0E3C
  • a_riot42a_riot42 Posts: 1,624
    I do have an IRIS, but the remote does not have discrete codes for inputs. Below is one that I know works and is for AV1.

    So somehow 50AF 21DE translates to (from a file for a :
    0000 006D 0022 0002 0154 00AB 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 0015 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 003F 0016 05E6 0154 0054 0016 0E3C

    Then you may need to find them elsewhere or use anchoring off AV1. If you have an input toggle button, you can always switch to AV1 and then some amount of toggles to get the input you need. Its far from optimal, but sometimes that's all the TV is capable of. Sometimes doing a chan up/dn will put it into antenna mode and you can toggle from there as well. Doesn't sound like the TV was made to be integrated.
    Paul
  • John NagyJohn Nagy Posts: 1,740
    Google is your friend, but you need to make the first move.

    I googled "IR HEX CONVERSION" and got a lot of on-point hits. The short code is called RC5 and there are a lot of sites with information on coversion to Pronto-style hex like AMX uses.

    Here's a live web page converter.
    http://www.awe-europe.com/irhex_converter.html

    Discussion on Remote Central
    http://www.remotecentral.com/cgi-bin/mboard/pro_remotes/thread.cgi?196

    including an actual downloadable app to do it.
    http://files.remotecentral.com/download/5763/rc5tohex.zip.html

    ...which I attach here for your convenience.


    Note that the exact hex output may not match what you get when you capture, because there will be variation in frequency and repeats/duration. The error is typically small and both your capture and the generated conversion will work, being within the margin of slop required in such things. And some might not work; try several.

    For example, your
    50AF 21DE translates to (from a file for a :
    0000 006D 0022 0002 0154 00AB 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 0015 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 003F 0016 05E6 0154 0054 0016 0E3C

    in the online converter, 50AF 21DE becomes
    0000 006D 0022 0002 0155 00AA 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 05ED 0155 0055 0015 0E47

    EDIT:
    I just now pasted both those outcomes into IREDIT, and despite the differences, IREDIT flagged me when entering the second one that "A duplicate function has been found".
    Looking at the waveforms for the two, you can detect a slight shift but clearly these are the same function and should both work.

    Good luck.
  • John Nagy wrote: »
    Google is your friend, but you need to make the first move.

    I googled "IR HEX CONVERSION" and got a lot of on-point hits. The short code is called RC5 and there are a lot of sites with information on coversion to Pronto-style hex like AMX uses.

    Here's a live web page converter.
    http://www.awe-europe.com/irhex_converter.html

    Discussion on Remote Central
    http://www.remotecentral.com/cgi-bin/mboard/pro_remotes/thread.cgi?196

    including an actual downloadable app to do it.
    http://files.remotecentral.com/download/5763/rc5tohex.zip.html

    ...which I attach here for your convenience.


    Note that the exact hex output may not match what you get when you capture, because there will be variation in frequency and repeats/duration. The error is typically small and both your capture and the generated conversion will work, being within the margin of slop required in such things. And some might not work; try several.

    For example, your
    50AF 21DE translates to (from a file for a :
    0000 006D 0022 0002 0154 00AB 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 0015 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 003F 0016 05E6 0154 0054 0016 0E3C

    in the online converter, 50AF 21DE becomes
    0000 006D 0022 0002 0155 00AA 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 05ED 0155 0055 0015 0E47

    EDIT:
    I just now pasted both those outcomes into IREDIT, and despite the differences, IREDIT flagged me when entering the second one that "A duplicate function has been found".
    Looking at the waveforms for the two, you can detect a slight shift but clearly these are the same function and should both work.

    Good luck.

    John,
    Thank you for posting the online converter. I did search and found the RC5 to Hex but I did not understand how to use and still don't, as I stopped looking at it as I found that URC has the code under a Discrete 2009 device. I have not yet converted those and I will most likely use the converted codes from the online tool instead. Believe me I did do a lot of searching but I guess I did not use the right terms. I appreciate your help.

    Thanks
  • a_riot42a_riot42 Posts: 1,624
    John,
    Thank you for posting the online converter. I did search and found the RC5 to Hex but I did not understand how to use and still don't, as I stopped looking at it as I found that URC has the code under a Discrete 2009 device. I have not yet converted those and I will most likely use the converted codes from the online tool instead. Believe me I did do a lot of searching but I guess I did not use the right terms. I appreciate your help.

    Thanks

    He's just showing off :)
    Paul
  • DHawthorneDHawthorne Posts: 4,584
    a_riot42 wrote: »
    Yes. The prewire team had bundled the speaker wires in with the fireplace igniter cabling, sending a huge voltage to the speakers at random intervals whenever it was turned on. Didn't even need the power amps. The wiring was laid behind the fireplace so it was not easy to get at and part of the fireplace had to be disassembled. It would have sucked had I not been correct about the source of the problem, after they dismantled it all. It had to be fixed as it was going to give someone a heart attack from fright whenever it occurred. What was weird was that it didn't occur every time, only once every 20 times, so when I tried it, it never happened, but then the client would and I would get a frantic call, but then couldn't reproduce it. Very frustrating, but we figured it out and got it fixed at our expense. Somehow those BW speakers still worked!
    Paul

    I had something similar ... the job had a bunch of relays to turn speakers on and off as a cheap way to expand the zone capacity of the matrix switch. Any time they did an all-off, the switch locked up. Turns out the RS-232 wire was strapped to the relay feeds, and when they all fired at once, it went down the port and crashed it. I unbundled them and the problem went away. To this day, I have no idea what made me think it was even possibly the problem.
Sign In or Register to comment.