I uploaded v1.1 of 3FG's BitExp upgrade files to include these commands.The Robman wrote:Btw, there were 2 additional functions in the UEI list:
29 Delete (58)
45 E-Mail (90)
HUMAX iHD-FOX C (KabelBW - Germany)
Moderator: Moderators
Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)
Interesting. The files that bnordman tested (10802, created using the official UEI executor and Manual Settings, and 10811, created using the new Humax entry in protocols.ini) shoot exactly the same signals. Earl captured both from his Slingbox using the OARI06G. So I guess that something went wrong in bnordman's first test.
Regarding BitExpander, that's a newly created Java class for the Humax executor entry in protocols.ini. We have lots of these classes which help in describing and translating unusual executors in protocols.ini. For example, we have the GrundigXlator for the Grundig16 protocol, SonyComboTranslator, XorCheck, BitDoubler, etc. For Humax, we need to convert e.g. OBC=27 = Mute to 0x36 (shift left 1 bit, and append the complement of the lsb), then expand that to 0x3C18 (0011110000011000) which describes the on and off parts of the variable data. A similar translation needs to be done for the fixed data. This could have been implemented instead as HumaxXlator with a simpler argument list, but it seems prudent to make it more flexible. So it can be used to expand other IR signals into zeros and ones which describe off and on.
If Greg/Graham agree, I'll check it into controlremote at SourceForge so that it is availble in the next version of RMIR.
Regarding BitExpander, that's a newly created Java class for the Humax executor entry in protocols.ini. We have lots of these classes which help in describing and translating unusual executors in protocols.ini. For example, we have the GrundigXlator for the Grundig16 protocol, SonyComboTranslator, XorCheck, BitDoubler, etc. For Humax, we need to convert e.g. OBC=27 = Mute to 0x36 (shift left 1 bit, and append the complement of the lsb), then expand that to 0x3C18 (0011110000011000) which describes the on and off parts of the variable data. A similar translation needs to be done for the fixed data. This could have been implemented instead as HumaxXlator with a simpler argument list, but it seems prudent to make it more flexible. So it can be used to expand other IR signals into zeros and ones which describe off and on.
If Greg/Graham agree, I'll check it into controlremote at SourceForge so that it is availble in the next version of RMIR.
It could certainly be that I have made a mistake with the early file since I am really new to this, but I performed the steps to upload the .bin(s) and testing it several times and had no reaction of the cable box.3FG wrote:Interesting. The files that bnordman tested (10802, created using the official UEI executor and Manual Settings, and 10811, created using the new Humax entry in protocols.ini) shoot exactly the same signals. Earl captured both from his Slingbox using the OARI06G. So I guess that something went wrong in bnordman's first test.
Either way, it works now and I am very thankful to you experts for making me enjoy the Slingbox!