IR Protocol - NEC2-f16

alanrichey · Post by **alanrichey** » Fri Sep 23, 2011 2:50 pm

I am getting this decode on IRScope. From the notes I can understand NEC2-16, but what does the 'f' represent ?

3FG · Post by **3FG** » Fri Sep 23, 2011 10:16 pm

It just means that the function code (OBC) is 16 bits, rather than the usual 8bits followed by the complement. Frequently some part of the 16 bits is the same for the entire set of signals, and it is possible to write a small executor. Vicky has done that for Onlyo receivers. It is also possible to use a simple executor and supply it with 4 bytes of command data.

alanrichey · Post by **alanrichey** » Sat Sep 24, 2011 12:55 am

So what do I use in RemoteMaster ? Just NEC2 or is that not going to work ?

Post by **vickyg2003** » Sat Sep 24, 2011 3:19 am

As far as I can tell the Nec2-f16 is another form of GAP. Its just 32 bits of data that have timings near the nec2 with a full frame repeat.

The Nec2 protocol won't handle it.

In order to really identify it, we need to see the complete set of decodes.

AFAIK, there isn't anything built in to Protocols.ini to handle this protocol.

Since you don't need EFC's for keymoves, you really don't care if the protocol can be distilled down to 256 OBCs that transfer down to 3 digit EFC's, but whenever possible, we like to have that option so we like to do an analysis of the protocol for patterns.

I noticed that it was said that I wrote an executor for the Onkyo nec1-f16, but that was really for an IOData32{38k,550}<1,-1|1,-3>(16,-8,D:8,S:8,E:8, f8 ,^108m) 3 fixed bytes, 1 function byte.

What we need to do is see how this signal shakes out as far as a pattern goes.

Bottom line, post your ICTs and let us have a look.

alanrichey · Post by **alanrichey** » Sat Sep 24, 2011 7:54 am

Here is one with the Power button and the numeric buttons. Is that enough ?

https://www.hifi-remote.com/forums/dload ... le_id=9959

Al

Post by **vickyg2003** » Sat Sep 24, 2011 9:55 am

Code: Select all

power:1000000001111111 1000 0000 1111 0111
0:----- 1000000001111111 1001 0100 1011 0110
1:----- 1000000001111111 0000 0100 1011 1111
2:----- 1000000001111111 1000 0100 1011 0111
3:----- 1000000001111111 0100 1100 0011 1011
4:----- 1000000001111111 1100 0100 1011 0011
5:----- 1000000001111111 0010 0100 1011 1101
6:----- 1000000001111111 1010 0100 1011 0101
7:----- 1000000001111111 0110 0100 1011 1001
8:----- 1000000001111111 1110 0100 1011 0001
9:----- 1000000001111111 0001 0100 1011 1110

Well it would be nice to see if the pattern holds up. So far it looks like this is 2 bytes of fixed data, followed by a one byte function, and then the nibble swapped complement of the function.

alanrichey · Post by **alanrichey** » Sat Sep 24, 2011 10:23 am

I guess that is a gentle hint you want some more

I'll get to it, but I can't at the moment as I happen to be using my SlingCatcher to catch up on some episodes of 'Alphas' recorded on my Tivo in the USA (I'm in the UK at the moment and we don't get it here) and I have found it uses the same codes.

Makes sense I guess at this Echostar box has the Sling system built in so this is probably a 'Company' IR Protocol.

It won't help you at all, and there are no files in the system relating to the Slingcatcher but maybe Rob has seen something in his early work with Sling ?

eferz · Post by **eferz** » Sat Sep 24, 2011 11:16 am

alanrichey wrote:Makes sense I guess at this Echostar box has the Sling system built in so this is probably a 'Company' IR Protocol.

It won't help you at all, and there are no files in the system relating to the Slingcatcher but maybe Rob has seen something in his early work with Sling ?

Guessing that you're probably referring to the Echostar HDS-600RS since there are already a few SlingCatcher related device upgrades in the file section.

I've downloaded the respective remote profile from the Logtech Harmony Database. It appears that IR signals are similar to Rob's SlingCatcher upgrades. So, I took the liberty of recording and uploading the ICT file for the Echostar HDS-600RS. Hope it helps.

ICT file: https://www.hifi-remote.com/forums/dload ... le_id=9960

P.s.,

alanrichey wrote:I am getting this decode on IRScope. From the notes I can understand NEC2-16, but what does the 'f' represent ?

I vote for the "F" in F16 to represent "Fighter" as in the F-16 Fighter Jets and opposed to the B-16 Bombing Planes.

alanrichey wrote:catch up on some episodes of 'Alphas'

i <3 = that show.

alanrichey · Post by **alanrichey** » Sat Sep 24, 2011 11:30 am

eferz wrote:I've downloaded the respective remote profile from the Logtech Harmony Database. It appears that IR signals are similar to Rob's SlingCatcher upgrades. So, I took the liberty of recording and uploading the ICT file for the Echostar HDS-600RS. Hope it helps.

Yes, thanks, saves me from doing it

But what do you mean by Rob's SlingCatcher upgrades ? Is there an RM file somewhere ?

eferz · Post by **eferz** » Sat Sep 24, 2011 11:32 am

alanrichey wrote:Yes, thanks, saves me from doing it But what do you mean by Rob's SlingCatcher upgrades ? Is there an RM file somewhere ?

Yes, I linked in the earlier post, but here it is spelled out: https://www.hifi-remote.com/forums/dload ... ingCatcher

alanrichey · Post by **alanrichey** » Sat Sep 24, 2011 11:50 am

Perfect, so we can forget about figuring out NEC2-f16 as we have it in that RM file.

So Vicky, thanks for your help but no need to go any further. I'll get the user to test it on the Echostar box and report back.

Post by **The Robman** » Sat Sep 24, 2011 11:56 am

The NEC 4DEV Yamaha Combo was developed for signals somewhat like these, maybe we could adapt it for these too.

eferz · Post by **eferz** » Sat Sep 24, 2011 12:25 pm

The Robman wrote:The NEC 4DEV Yamaha Combo was developed for signals somewhat like these, maybe we could adapt it for these too.

Would that make these device upgrades more portable?

I tried to use the SlingCatcher device upgrades with a "Comcast-URC-1067 (CS301009)" but I was given the following syntax error, "The selected protocol "PID 01 AB" (01 AB) is not compatible with the selected remote. This upgrade will NOT function correctly. Please Choose a different protocol."

Guessing this due to a difference between the remote's HCS08 processor and the S3C8+ which it was meant to be used with.

Post by **vickyg2003** » Sat Sep 24, 2011 3:03 pm

eferz wrote:I tried to use the SlingCatcher device upgrades with a "Comcast-URC-1067 (CS301009)" but I was given the following syntax error, "The selected protocol "PID 01 AB" (01 AB) is not compatible with the selected remote. This upgrade will NOT function correctly. Please Choose a different protocol."

Guessing this due to a difference between the remote's HCS08 processor and the S3C8+ which it was meant to be used with.

I can get that to work for you. No biggie. Its a simple upgrade. I am having trouble with the upgrade though. The Slingcatcher doesn't send the same signals for power as the ICT showed. This is a little

Personally I think this would be a lot easier to work with if we could use the OBC's reported in the nec2-f16 protocol. but I do believe this those are lsb, and the upgrade is marked to be msb.

I also think that it would be better to do a 1 byte protocol, instead of a two byte in this situation, for ease of use, since there IS an easy to calculate check-byte which is a nible-swap complement. However an F-16 protocol listed where you just enter the hex from the misc column would be easy too.

I notice that this signal doesn't repeat with this protocol. Is that a problem? Or is this like the NEC1 thingy where there needs to be a limit on repeats for the slingbox.

alanrichey · Post by **alanrichey** » Sat Sep 24, 2011 3:12 pm

vickyg2003 wrote:I am having trouble with the upgrade though. The Slingcatcher doesn't send the same signals for power as the ICT showed.

You may not follow this, but the SlingCatcher is a special case. The Power command is a 2-stage process. It first sends a signal that pops up a message on the screen asking if you want to send a power command to the remote Slingbox to turn the remote device off, or whether you want to actually turn the SlingCatcher off. So there is no such thing as a 'standard' power command.

vickyg2003 wrote:I notice that this signal doesn't repeat with this protocol. Is that a problem? Or is this like the NEC1 thingy where there needs to be a limit on repeats for the slingbox.

Because the Slingbox does not support long presses, you never need to use the repeat function. My job would be a lot easier if all the protocols had zero repeat