Decoding hdmi switch's weird remote.

[dinomight]

Ok so i just bought a fairly cheap 5 port hdmi switches (like 30$) and it came with a little 5 button remote (1 button for each input) but i need help figuring out the proper devicecodes and keys for this essentially no name remote. I have used my little logitech/ast ir sensor to learn all of the codes using winlirc but i'm really no expert and have no idea how to take this and transform it into codes that i can use in IR. I've pasted the config from winlirc below. If anyone could help me decode it i would be very greatful. I know there are some experts out there so hopefully i can get this working soon. Thanks,
-D

Code: Select all

begin remote

  name  hdmi
  bits           16
  flags SPACE_ENC
  eps            25
  aeps          100

  header        300 13448
  one           300  1025
  zero          300  2152
  ptrail        300
  repeat        300 11188
  pre_data_bits   16
  pre_data       0xFE01
  gap          40457
  toggle_bit      0


      begin codes
          1                        0x000000000000BF40
          2                        0x000000000000DF20
          3                        0x0000000000005FA0
          4                        0x0000000000009F60
          5                        0x000000000000EF10
      end codes

end remote

By the way what is a good really cheap jp1 learning remote. I really only need it for learning (i use th urc6131 remotes for my home currently but it obiously doesn't have learning functions.)

[Capn Trips]

I know you say it's a "no-name" switcher, but can you provide its name anyways? ..and/or a picture of it and/or its remote? The Code Search template is still a valuable tool, even if you don't think it applies. I'd recommend using it. There are a number of "no-name" HDMI Switcher upgrades in the upgrade file section, and I'd wager that if you tried them, you have a better that 50% chance that yours is already there.

[dinomight]

Well i tested a bunch of the ones in the upgrade section none so far seem to work. here are a bunch of images of the device, remote and packaging. the only product number i can find is hsw0501 (probably Hdmi SWitch 05 inputs 01 outputs) which doesn't really help. If you want a link to where it was purchased it is here http://www.cecompass.com/index.asp?Page ... ID=66&HS=1

images located http://www.thurstonco.com/public/hdmi/

[speaker.guy]

Did you try to learn it on a UEI remote?

[dinomight]

unfortunately i don't have a learning remote. Any recommendations on a cheap one (or is someone willing to let me send them this little remote and learn the codes for me. I'll pay postage both ways (i figure postage couldn't be more than a few bucks seeing as how this remote weighs next to nothing.)
-D

[speaker.guy]

Where are you?

[dinomight]

provo, utah, USA

[johnsfine]

I don't see any need for a learning remote.

The LIRC data gives all the information you would need to construct a new executor with PB.

I don't recall seeing exactly this protocol before. We might have the executor already done somewhere, but even if so, finding it might be harder than doing it over.

I'm assuming the LIRC capture was done with an accurate time source. The signal structure is the same as NEC1, but with much slower timing. If the capture time source weren't trusted, I would just conclude the real signal is NEC1.

I don't know if I can find the time to set this up in PB. Hopefully someone else can.

[dinomight]

I'm not really sure how to know if the timing source is accurate (i don't know where the timing source came from. I used the default values for everything when trying to learn the remote in lirc)

Like i said this remote was learned using an ast/logitech reciever. Again, I'm not sure if the device provides proper timing or if that was something i was supposed to setup.

Also i don't really know how or what you mean by setting up an executor in PB (?).

I kinda feel useless in helping you help me. Please if there is anything i can do that would help(relearning the remote using some timing, learning how to create an executer) let me know how or what to do and i'll do it.

[speaker.guy]

It seems a lot simpler to try to learn the signals rather than reinvent the wheel.....

[johnsfine]

It seems a lot simpler to try to learn the signals rather than reinvent the wheel.....

I thought the point was to use the signals in a 6131.

Learned signals can't be used directly in a 6131. You need an upgrade. If the timing info is correct, the learned signals wouldn't give a correct decode, nor any info that isn't in the LIRC file. Either way, you need an executor.

But I guess it's worth verifying the difference between this protocol and nec1.

Dinomight,

Create an upgrade for the 6131 for nec1 protocol, device, 128. For the five functions, put in OBC numbers 2, 4, 5, 6 and 8.

Try that in the 6131 with the switch. There is a small chance it will just work. If it doesn't work, use you ir sensor to make an lirc file of those five signals from the 6131. The differences between that and your first lirc file will then verify the exact differences between the hdmi switch protocol and nec1.

[dinomight]

Yeah just to confirm the point of all this is to have a device upgrade that will work on the 6131 remotes that i already have. (in case it matters i use a 6131 2k with an extender). By the way how can i tell if the timing is correct. and if it isn't how can i correct it.
-D

[johnsfine]

By the way how can i tell if the timing is correct. and if it isn't how can i correct it.

I was editing those instructions in my post above while you were replying, so reread my previous post.

[dinomight]

Ok so i think i created the upgrade I see where you got the 2,4,5,6,8 but where did you get the device number (128) from. also in remote master does it matter what i put for the setup code or does that just need to be unique.

I will have to wait until i get home to test this out. but thanks for the help so far. I will let you know how things go when i test them tonight.
-D

Upgrade Code 0 = 00 80 (Cable/0128) (RM v1.86)
5A 00 81 00 FE FE 00 BF DF 5F 9F 1F 00 00 00 00
End

[johnsfine]

I see where you got the 2,4,5,6,8 but where did you get the device number (128) from.

I thought it would take a fair amount of experience with hex and/or IR encoding to see the OBC numbers and if you could see those, you could also see the device number.

Code: Select all

  pre_data       0xFE01
 
          1                        0x000000000000BF40
          2                        0x000000000000DF20
          3                        0x0000000000005FA0
          4                        0x0000000000009F60
          5                        0x000000000000EF10

The OBC number for '1' is either an LSB-comp conversion of BF or an LSB conversion of 40. Is that what you saw?

Similarly, the device number is either an LSB-comp conversion of FE or an LSB conversion of 01.

I do such conversions easily in my head. Others might want to use the EFC calculator in IR.exe tools menu and/or use the functions sheet in RM after choosing an appropriate protocol.

does it matter what i put for the setup code or does that just need to be unique.

The number just needs to be different from each of the other setup codes of equal or equivalent type that you are actually using in your 6131.

The number doesn't need to be unique relative to built-in setup codes you're not using nor relative to setup codes of non equivalent types.

Upgrade Code 0 = 00 80 (Cable/0128) (RM v1.86)
5A 00 81 00 FE FE 00 BF DF 5F 9F 1F 00 00 00 00
End

Notice the 1F code for '5' in your upgrade. I think that is OBC 7. It should have been OBC 8.