The protocol is RC5 (all condensed Pronto Hex beginning 5000 is RC5).

The device number is 0 (the fifth value in that Pronto Hex string).

The function number is 22 (the sixth value, hex 0016 is decimal 22).

Hopefully the above is enough to tell you how to generate it with MakeHex.

Be aware that the RC5 protocol has an internal "toggle bit" that prevents any signal from being accepted when it is completely identical to the last signal accepted.

There are two versions of each signal. You can have MakeHex generate the other version by changing the T=0 in the .irp file to T=1

To send RC5 signals correctly, whenever you want to send the same function as the last signal you sent, you must send the other version of that function. (When sending a different function from the last signal it doesn't matter which version you send).

I don't know enough about AMX controllers to know what methods may be practical for dealing with that issue. Maybe the AMX recognises RC5 and deals with the issue itself. Maybe it is practical to put the whole code set in twice and program something to make sure they are alternated. For some combinations of universal remote and device it is best to identify a do_nothing command and build a copy of that into every other command, so the device will never see the same function twice in a row.

Thanks a lot! All the normal functions are working, like on, off, aspect...
And there is no problem with the toggle bit.
But now I have some direct codes for the different inputs, it is not working yet.
Inputs: 114-120 (decimal)
Maybe you have an idea for this as well...
Thanks!

Where did you get the info "114-120 (decimal)"?

That sounds like it should be the function number, so you should be able to find those in the .hex file generated by MakeHex. But I expect that is what you tried before saying "it is not working". Maybe with more info from the original source I'll have a better guess.

RC5 codes are typically documented including a "system code" or "address" or maybe "custom code", which are all other names for the thing MakeHex calls device. Most of the signals for your TV are device 0, but it is possible that some special functions use a different device number, maybe device=3.

Probably a really stupid question, but is there a way to un-make a hex file? i.e. take the Hex and convert it back to a 'Short Code'.

I am trying to analyse the Hex for a Panasonic TV to work out 'Discrete' codes. There are 104 Columns of Hex, of which 19 change using only: 0010 or 0030 and the final column uses one of the following: 0AAA, 0AAB, 0AA7, 0AAF, 0AB2, 0AB6 the others are static. There does not seem to be a pattern to the usage, except SD seems to use 0010 in column 56&62 (nothing else does, and colum 60 seems to be for aspect control.

I've copied all this data into Excel to analyse, but still to many variations to deal with.

Looking to create the discrete codes for Power on & off, and if possible aspect and AV-input (AV1/AV2/PC/HDMI-1/HDMI-2 etc..) for Panasonic Plasma TV TH-37PV600E (European Model).

Any pointers would be greatfully received.

See post 25 of this thread where I described DecodeCCF, IrTool and DecodeIr.dll

Those take long Pronto Hex and convert to a concise form. That form is basically the same as the input for MakeHex.

That concise form not the same as short Pronto hex, but if short Pronto hex exists, it is easy to convert from the concise form to short Pronto Hex.

It is very unlikely that short Pronto Hex exists for the the signals of a Pansonic TV.

But several people have used MakeHex to generate a few full sets of 256 codes for Panasonic TV (Those TV's unfortunately use signals from more than one set of 256) and have tested all those signals and reported results here at RC or at hifi-remote.com. You should do some more forum searches before attempting such tedious testing yourself.