IR Protocol - NEC2-f16

Discussion forum for JP1 software tools currently in use, or being developed, such as IR, KM, RemoteMaster, and other misc apps/tools.

Moderator: Moderators

eferz
Expert
Posts: 1078
Joined: Thu Jun 03, 2010 1:25 am
Location: Austin, Texas

Post by eferz »

vickyg2003 wrote: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.
It would be great if the device upgrades could be universal, but don't spend too effort if you're converting it for me to use it on a HCS08 remote. I don't have either the Sling Media SlingCatcher nor the Echostar HDS-600RS. My only reason for using it on the Comcast URC-1067 was to juxtapose the results of Rob's SlingCatcher upgrade with my results of the HDS-600RS profile from the Logitech Harmony Database. Instead, I used the Insignia Remote and tested a couple of commands and saw they were similar.

To ease the confusion, I've upload the ICT for the Sling Media SlingCatcher profile from the Logitech Harmony Database.
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.)
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

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

I like to have hcs08 support for everything. Give this a try. See if this makes more sense with the OBC/Byte2 information.
eferz
Expert
Posts: 1078
Joined: Thu Jun 03, 2010 1:25 am
Location: Austin, Texas

Post by eferz »

vickyg2003 wrote:https://www.hifi-remote.com/forums/dload ... le_id=9962

I like to have hcs08 support for everything. Give this a try. See if this makes more sense with the OBC/Byte2 information.
Well, the good news is that I can install this device upgrade into either the Comcast URC-1067 or the Insignia 67100. That's awesome! The bad news is that I can't test whether or not it works and IR Scope no longer matches the respective LHD profile. So, I guess it will have to be up to Alan and his user to test it.
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.)
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

eferz wrote: The bad news is IR Scope no longer matches the respective LHD profile. So, I guess it will have to be up to Alan and his user to test it.
Are you saying I screwed this up? That the IR Scope is different than the logitech harmony learns? Could very well be, but I matched these to the ICT file before I sent them. This does send different codes than Rob's slingcatcher, but that didn't match the logitech signals sent prior to this.

If that's what you are saying, I'll match things up to Rob's file, but I was seeing different hex code from rob's. Or perhaps I chose data from the wrong ICT file.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
3FG
Expert
Posts: 3442
Joined: Mon May 18, 2009 11:48 pm

Post by 3FG »

Well, let's take Prev Channel, as it shows up on my computer.

Code: Select all

Rob SlingCatcher     LHD           Vicky new         Notes
OBC   byte2      OBC  byte2       OBC  byte2
 49      EC       2      DF        140    EC       1.FE.31.EC
The LHD learns are clearly different from Rob or Vicky. However, Vicky and Rob have a different OBC, with the same byte2. The Notes in Vicky's file shows the same OBC as Rob (49/31h).

On the other hand, take digit 3, for which we also have Alan's learns. Everybody agrees that digit 3 is OBC =50, byte 2 = DC.

I suspect that some of Vicky's OBCs are different than intended--at least they aren't matched to the Notes, and are also different than Rob's.

And for most buttons (excepting digits), LHD has different values. So I suppose that we'll need feedback from the user.
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

I suspect that some of Vicky's OBCs are different than intended--at least they aren't matched to the Notes, and are also different than Rob's.
:oops: Ah yes, somehow my copy/paste seemed to have failed. I probably pasted it into another upgrade I had open. Ooops. :lol: :oops: I tested a few of the number keys to make sure the learns matched the ICT. I guess I should have looked a little farther.

I tried to make mine so that the user didn't have to do that left to right thing for the data.
The LHD learns are clearly different from Rob or Vicky. However, Vicky and Rob have a different OBC, with the same byte2. The Notes in Vicky's file shows the same OBC as Rob (49/31h).
The same executor is used, but I marked it as LSB so that the user can use the OBC from the decode, Rob left his MSB so the user needs to reverse the OBC.


I redid the upgrade, but I'm still not sure I am working from the correct ICT file.

For that matter, I'm not sure I pulled down the correct slingcatcher file either.

Edit: I didn't pull down the correct slingcatcher file, I pulled down the old slingcatcher file. Submitted by the Robman, but you all are working with the slingcathcer2.remu that says (Rob) after it. So you are seeing the correct obcs.

I still think it looks funny that #3 if obc 50, I would have thought that was going to be 34.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
eferz
Expert
Posts: 1078
Joined: Thu Jun 03, 2010 1:25 am
Location: Austin, Texas

Post by eferz »

vickyg2003 wrote:I redid the upgrade, but I'm still not sure I am working from the correct ICT file.
That's my fault. Sorry. There are three ICT files referenced in this post. I'm assuming that Alan's learns were from his SlingCatcher remote. However, he vaguely referenced a SlingCatcher and an Echostar box in his post. This lead me to believe that his user needs Echostar HDS-600RS bin files for a Slingbox.

The Echostar HDS-600RS was compared them to Rob's SlingCatcher file because it was eluded that they use the same IR codes/protocol. My findings indicate that the two are similar but not exact. There is not enough "command to signal" matches between the SlingCatcher and the HDS-600RDS to be considered for a converged remote device. This leads me to believe that they should be treated as two separate upgrades.

Since Rob mentioned about making these upgrade reworked for "NEC 4DEV Yamaha Combo", I decided to also upload the Sling Media SlingCatcher ICT recorded from LHD for reference to Rob's SlingCatcher upgrade.
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.)
alanrichey
Expert
Posts: 3533
Joined: Mon Mar 24, 2008 7:14 am
Location: UK/USA

Post by alanrichey »

eferz wrote:I'm assuming that Alan's learns were from his SlingCatcher remote. However, he vaguely referenced a SlingCatcher and an Echostar box in his post.
No. The ICT file was from my Logitech Harmony with the Echostar box installed as I was trying to build a BIN file. As it happened I was using my Slingcatcher when I tried to learn the codes and found that every button I pressed on the Harmony controlled the Slingcatcher.
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

Well, pooh, after opening Rob's slingcatcher, I see that it is a 1 byte protocol, that properly calculates the check byte( nibleswap comp). I should have known that Rob wouldn't have let that stand as a 2-byte protocol when there was a checkbyte so obvious that even I can see the pattern. Doh!
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Post Reply