Lost a Channel on Cox Cable

Ask fellow members about Ceton's infiniTV tuners here.
Forum rules
Ceton no longer participate in this forum. Official support may still be handled via the Ceton Ticket system.
Post Reply
tfjield

Posts: 1
Joined: Wed Jun 03, 2020 2:24 am
Location:

HTPC Specs: Show details

Lost a Channel on Cox Cable

#1

Post by tfjield » Wed Jun 03, 2020 2:35 am

Hi Everyone,

I'm using a Ceton InfiniTV 6 ETH with a Myth server, using Cox Cable in southern California. Just two days ago I lost the ability to tune CNBC, either in SD or HD. The channel numbers are 44 and 1044.

I have 3 systems: Ceton InfiniTV, a TiVo, and a cable box. The Ceton and the TiVo both take cable cards and require tuning adapters. Funny thing, I can get 44 and 1044 on the cable box, but not on the cable card systems.

Of course, calls to Cox have been useless. They reset my tuning adapters, say there's nothing more they can do, and want to send a technician. All of the other channels work fine. The TiVo and the cable box are on the same run, split close to each other, and the Ceton is on a separate run that split earlier. And yet the cable box works for CNBC, and the other two don't.

So before the technician comes (mid-pandemic, so they can't come inside...) I want to have as much info as possible.

Can anyone tell me what's happening here? I see it looks up the channel info from the tuning adapter, but it reverts back to 0.

Code: Select all

Jan  1 01:06:33 ocur[21]: ocur: [0] Attempting to SetChannel (Channel=44  SourceId=0  Mode=0)
Jan  1 01:06:33 ocur[21]: ocur: Disabled table monitor for instance 0
Jan  1 01:06:33 ocur[21]: ocur: [0] Program number set to 0, was 0
Jan  1 01:06:33 ocur[21]: ocur: [0] Starting TA[6] resolve for channel 44
Jan  1 01:06:33 ocur[21]: libcetontrif: trif[6] Found channel 44 in map
Jan  1 01:06:33 ocur[21]: ocur: [0] Resolved channel 44 -> freq 141000, prog 58780, modulation 16
Jan  1 01:06:33 ocur[21]: ocur: [0] Tune to 44 (mod=q256, freq=141000, program=58780, std=9)
Jan  1 01:06:33 ocur[21]: ocur: [0] Program number set to 58780, was 0
Jan  1 01:06:33 ocur[21]: ocur: Disabled table monitor for instance 0
Jan  1 01:06:33 ocur[21]: ocur: [0] Locked: 1 Acc E: 9
Jan  1 01:06:33 ocur[21]: upnp: Event(cas[0]): DescramblingStatus, "Unknown"
Jan  1 01:06:33 ocur[21]: ocur: [0] Getting pmt for program 58780
Jan  1 01:06:34 ocur[21]: ocur: [0] Got pmt for program# 58780
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x1ffc
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0083
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0084
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0085
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0086
Jan  1 01:06:34 ocur[21]: upnp: Event(tuner[0]): PCRLock, "1"
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0000
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0936
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0154
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0937
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0938
Jan  1 01:06:34 ocur[21]: ocur: [0] Adding pid 0x0939
Jan  1 01:06:34 ocur[21]: ocur: Disabled table monitor for instance 0
Jan  1 01:06:34 ocur[21]: ocur: Enabled table monitor for instance 0
Jan  1 01:06:34 ocur[21]: ocur: [0] Channel is scrambled, expecting CCI
Jan  1 01:06:34 ocur[21]: ocur: [0] Sending ca_pmt to CableCARD for program number 58780 index 0
Jan  1 01:06:34 ocur[21]: libcetonrtsp: object cetonmpeg0
Jan  1 01:06:34 ocur[21]: libctn91xx: Setting mpeg_eth headers for instance 0
Jan  1 01:06:34 ocur[21]: libctn91xx: rip C0A8013A lip C0A80139 rp 50042 lp 43012
Jan  1 01:06:34 ocur[21]: ocur: [0] rtp setup for client 192.168.1.58:50042
Jan  1 01:06:34 ocur[21]: ocur: [0] CCI 00 arrived for program# 58780
Jan  1 01:06:35 ocur[21]: ocur: [0] rtp teardown for client 192.168.1.58:50042
Jan  1 01:06:35 ocur[21]: libcetonrtsp: object cetonmpeg0
Jan  1 01:06:35 ocur[21]: libctn91xx: Setting mpeg_eth headers for instance 0
Jan  1 01:06:35 ocur[21]: libctn91xx: rip C0A8013A lip C0A80139 rp 54498 lp 43012
Jan  1 01:06:35 ocur[21]: ocur: [0] rtp setup for client 192.168.1.58:54498
Jan  1 01:06:39 ocur[21]: ocur: [0] rtp teardown for client 192.168.1.58:54498
Jan  1 01:06:39 ocur[21]: ocur: [0] Attempting to SetChannel (Channel=0  SourceId=0  Mode=0)
Jan  1 01:06:39 ocur[21]: ocur: Disabled table monitor for instance 0
Jan  1 01:06:39 ocur[21]: ocur: [0] Program number set to 0, was 58780
Jan  1 01:06:39 ocur[21]: ocur: [0] Starting TA[6] resolve for channel 0
Jan  1 01:06:39 ocur[21]: ocur: WARNING: [0] OCTA resolution failed. tune_status=7.
Jan  1 01:06:39 ocur[21]: ocur: WARNING: [0] Setting timer to fire resolve error c0046007
Jan  1 01:06:40 ocur[21]: ocur: WARNING: [0] Channel 0 not found
Jan  1 01:06:44 ocur[21]: ocur: WARNING: [0] Firing resolve error c0046007
Jan  1 01:06:44 ocur[21]: upnp: Event(cas[0]): DescramblingStatus, "Not possible (technical reason)"
I'm guessing this is an issue affecting the tuning adapters, but not the cable box, for some reason. Any help would be appreciated!

Thank you.

5N4R35

Posts: 4
Joined: Tue Jun 23, 2020 7:42 pm
Location:

HTPC Specs: Show details

#2

Post by 5N4R35 » Tue Jun 23, 2020 10:46 pm

do you know what your uptx is at the cable card location? SDV operates using the return signal. It's possible for your return signal to be close to failing, (anything over 50dB), if its over 50dB then you will need to change you splitter configuration to improve the signal. This is something technician can do. You can see what your MER is by checking 192.168.200.1 and entering the levels you see for the frequency its trying to lock in on. If there is a low MER, (below 32dB), or a high uptx then it may be the tuner can't lock onto the channel. All the technician is going to do is make sure the signal is good to the house. Since its working on the cable box it probably is good to the side of the house. I'm a technician for a different cable company. Sorry I can't speak to the computer side of things. If you give me some more information from the ceton diagnostic page I can at least rule out anything signal wise though.

Post Reply