Arris HMC-4000 - weird situation

chuliu · Post by **chuliu** » Sat Sep 15, 2018 11:17 am

I have a friend who help others making bin files for slingbox and makes some money from it. He recently encountered a weird situation. The customer mailed him a remote and it was decoded as nec1 32,8. However, after uploading to slingbox, it won't work. He asked the customer to mail him the slingbox 500, and he tested with his own stb by uploading a working bin to the 500. It worked. He made sure the customer placed the 500 and stb close enough and also there was a ir blaster in front of the stb. The customer also asked the cable company to replace a new stb. All the above been done, but the slingbox just won't control the stb.

Now the remote has been returned to the customer and I couldn't ask him to send the ict file for analysis. What can we do now?

Post by **The Robman** » Sat Sep 15, 2018 4:01 pm

It might help if we knew what this mystery NEC1 32.8 device was so we could Google to see if others have had problems with it.

We have Slingbox bin files for several Kaon STBs that use that code:
Kaon KVR-1000 PVR
Kaon NA1600HD
Kaon VM 1910
Kaon VM1400P
Kaon-171

And also the following remote file:
Strong 5290 PVR Digital TV

chuliu · Post by **chuliu** » Sun Sep 16, 2018 1:24 am

it is arris hmc-4000.
I know from a fact that for this same model, there are 2 types, one decoded as mce 38,80, and the other nec1 32,8.

In harmony database, I downloaded to my harmony 650 and it is mce 38,80.
The one that uses mce was for bbtv, a taiwan cable company, while the other that uses nec1 32,8, was for netwave, another Taiwan cable company.

chuliu · Post by **chuliu** » Sun Sep 16, 2018 1:29 am

https://www.hifi-remote.com/forums/dload ... e_id=25330

My friend asked his customer to mail him the remote and here is a ict for power button.

more buttons with long press:
https://www.hifi-remote.com/forums/dload ... e_id=25331

I will also attached a complete rmdu for it that doesn't work.

rmdu we created:

https://www.hifi-remote.com/forums/dload ... e_id=25332

chuliu · Post by **chuliu** » Sun Sep 16, 2018 4:30 am

I just wonder if it was due to the no repeat issue with slingbox ir blaster that stopped the bin from working. Can we make the nec1 signal repeat like thoese in the ict file?

chuliu · Post by **chuliu** » Mon Sep 17, 2018 4:10 am

Can any forum expert take a look at my ict file?
Thanks.

I compared signal from ict file with signal from a jp1 with nec1 32,8 and they look almost identical.

Post by **The Robman** » Mon Sep 17, 2018 8:47 am

chuliu wrote:Can any forum expert take a look at my ict file?
Thanks.

I compared signal from ict file with signal from a jp1 with nec1 32,8 and they look almost identical.

Could you post the ICT file for the JP1 with NEC1 32.8 so I can compare them side-by-side

chuliu · Post by **chuliu** » Mon Sep 17, 2018 9:12 am

I have attached a ict file from slingbox loaded with nec1 32,8.
I didn't want to upload one from jp1 remote fearing that it should work on netwave cable stb. As far as I know slingbox signal won't work on it.

Thanks.

https://www.hifi-remote.com/forums/dload ... e_id=25335

Post by **The Robman** » Mon Sep 17, 2018 10:01 am

The last file that you loaded shows 7 signals, with OBCs: 0, 28, 29, 30, 64, 65, 0 whereas the original file just showed a single signal with OBC 0. Any idea why that is?

As for comparing the signals, I see that the frequency on the original is 38.1 whereas on the others it's 38.7. Normally I wouldn't expect that to make a difference, but if the device is overly sensitive, it might.

chuliu · Post by **chuliu** » Mon Sep 17, 2018 10:04 am

Please take a look at the second file I posted above.
There is one signal in the first file while there are more in the second file.

Post by **The Robman** » Mon Sep 17, 2018 11:25 am

chuliu wrote:Please take a look at the second file I posted above.
There is one signal in the first file while there are more in the second file.

It's always helpful to link to a specific file. I see that you have loaded 4 files:

File 1 contains a single signal with OBC 2
File 2 contains several signals
File 3 is the RMDU file
File 4 contains several signals

I assume that File 1 is the one that contains the POWER button as learned from the original remote. Which file is the one that contains the POWER button as learned from the Slingbox IR blaster?

chuliu · Post by **chuliu** » Mon Sep 17, 2018 11:32 am

Sorry for the confusion.
File 1 is the original learns from remote with power only.
File 2 is the original learns from remote with more buttons learned.
File 3 is a rmdu file created with nec1 32,8.
File 4 is the learns from slingbox.

Post by **The Robman** » Mon Sep 17, 2018 1:52 pm

So, what I would do if it were me, is create a modified version of the NEC executor with the frequency lowered a bit, then do some testing capturing the signals from the Slingbox to see if it's about 38.1 to match the original, then test it on the device to see if that fixes it.

chuliu · Post by **chuliu** » Mon Sep 17, 2018 2:35 pm

The Robman wrote:So, what I would do if it were me, is create a modified version of the NEC executor with the frequency lowered a bit, then do some testing capturing the signals from the Slingbox to see if it's about 38.1 to match the original, then test it on the device to see if that fixes it.

Thanks. I did created a nec1 (no repeats) upgrade and test it on slingbox with no luck. Nec1 no repeats in protocol builder shows it uses 37.795, and captured in irscope as 38.1.

Further, I made a manual protocol with 1=(580,-540) 0=(580,-1645) and LI=(9000,-4500) and LO=(580,-45000). LI Repeat every frame. hold=no, count=0, and repeat=minimal. This resulting in a nec 32,8 which sends only 1 frame. I don't know how to make a manual nec1, and I made a manual nec2 and set repeat to zero. I made sure frequency was 38.1.

The above files are of no luck. I posted them for reference.

File 5 is ict from manual protocol for nec2
and File 6 is rmdu of manual protocol

Post by **The Robman** » Mon Sep 17, 2018 2:51 pm

Here's the raw code for the regular NEC executor (which generates NEC1, NEC2, etc). To adjust the carrier frequency, you adjust the first 2 bytes of the code.

Upgrade Protocol 0 = 00 5A (S3C8+) NEC1 (KM v9.22)
43 8B 31 8B 12 CF 44 08 08 01 18 01 06 01 18 03
39 D2 DC 11 94 08 B6 20 01 08 03 37 04 15 F6 01
46 FB 10 37 0B 07 E4 05 04 60 05 8B 0E B6 04 80
B6 05 80 37 0B 05 E4 04 05 60 05 E4 06 07 60 07
20 11 37 06 05 F6 01 04 7B 12 37 09 15 37 02 06
F6 01 49 F6 01 46 37 01 03 46 29 0D 46 29 01 8D
01 49 E4 20 1E E4 21 1F 37 01 EB F6 01 49 E6 28
C1 60 04 E6 12 01 8B E4
End

You can use PB to see what it should be. If I enter 38.1 with a 33% duty cycle, I get "43 8B", so this executor is certainly trying to generate 38.1. If I enter 37.9, I get "44 8B". This will take some trial and error to see what the Slingbox actually generates based on the code.