High Split Converter Problem

Reception, channel detection, network issues, CableCARD setup, etc.
KeithAbbott
Posts: 93
Joined: Fri Mar 11, 2011 7:10 pm

Re: High Split Converter Problem

Post by KeithAbbott »

Spent 40 minutes on a phone call with Spectrum level 0.5 cable card support this morning. He claims that there is no difference between how my working device and my non-working device is set up on their end. They're rolling a truck for Thursday morning. Yay...

Fortunately, my other Prime is working just fine, so this is not a high-priority thing for me. But I do want to get it working.

nickk
Silicondust
Posts: 20720
Joined: Tue Jan 13, 2004 9:39 am
x 302

Re: High Split Converter Problem

Post by nickk »

Can you please enable "send diagnostic information" and post back with the Device ID of your HDHomeRun... I will check what the TA is reporting when you scan...

KeithAbbott
Posts: 93
Joined: Fri Mar 11, 2011 7:10 pm

Re: High Split Converter Problem

Post by KeithAbbott »

Device ID is 13256C0B. I just initiated a channel scan on that device.

KeithAbbott
Posts: 93
Joined: Fri Mar 11, 2011 7:10 pm

Re: High Split Converter Problem

Post by KeithAbbott »

Comparing some of the Prime webgui screens between the functional and non-functional units, I notice the UPM Address looks to have a legitimate value (0x0309F4) for the functioning unit. The non-functioning unit has a UPM Address of 0x000000. Could that be some or all of my problem?

KeithAbbott
Posts: 93
Joined: Fri Mar 11, 2011 7:10 pm

Re: High Split Converter Problem

Post by KeithAbbott »

Well, the problem with the second Prime/HSC device has been resolved, yay! Now I am back to how I was before the HSC conversion began, and only had to spend a combined 7 hours talking with Spectrum CableCARD support and working with Spectrum technicians in my basement. Ironically, there was not a single problem with anything on my end, it was entirely on Spectrum's side. The technician in my basement today asked the phone support person what they changed, and didn't get much of an answer.

Also, the UPM Address in the device that was not functioning is now updated to 0x043ED2. Still don't know if that was a contributing factor or not.

Post Reply