Time Warner Cable: New firmware update does not work

For questions regarding Co-ax wiring, and to complain about your cable co.
Post Reply
Roofsmoker

Posts: 11
Joined: Mon Jun 09, 2014 6:57 pm
Location:

HTPC Specs: Show details

Time Warner Cable: New firmware update does not work

#1

Post by Roofsmoker » Fri Sep 12, 2014 3:48 pm

So since Monday morning my infinitv 4 has been trying to update the latest firmware update from the cable company and it never updates, long story short called a tech from Time Warner over and he tried 2 other cable cards that did the same never update the firmware, and he couldn't fix it. So now I have a Foreman coming over tomorrow to try and resolve the issue, not sure if anyone else is having this same problem in the New York area, but I do know my friends brand new time warner DVR crapped out the same day and he had to go replace it.

This would not be a big issue if time warner did not out source there cable card division, no money in cable cards for them. From what the tech told me and the trouble he was having on the phone with the various departments he had to deal with just to get a straight answer was ridiculous. So before The Tech could take this same cable card to his supervisor have him re-flash, stage the card, and pop it back in like nothing ever happened. Now they have to send the cards out and wait for them to deliver freshly staged cards, so basically when there is an issue like this no departments know until a tech goes and reports it back to his supervisor. The best part though only Time Warner techs go to cable card service calls, what is the point in trying to save money if your tech cant fix the problem?

The FCC just says they have to provide us with cable cards, but doing it right that's a different story, my 2 cents.

RyC

Posts: 724
Joined: Tue Aug 21, 2012 10:21 pm
Location:

HTPC Specs: Show details

#2

Post by RyC » Fri Sep 12, 2014 4:37 pm

If you keep having issues, try opening a support ticket with Ceton. They know people in TWC that can fix the issue.

Roofsmoker

Posts: 11
Joined: Mon Jun 09, 2014 6:57 pm
Location:

HTPC Specs: Show details

#3

Post by Roofsmoker » Sat Sep 13, 2014 8:23 pm

Time Warner foreman visited today, and tried 2 brand new cable cards which did the same exact thing, he called tech support, and they stated it's a known issue with 3rd party ceton devices and that I should contact them for support, so I opened a ticket with them.

If anyone is reading this and having the same issue refer it to Ceton

I guess there's a 1st time for everything, 1st issue I have had with the device going over a year strong.

cwinfield

Posts: 575
Joined: Tue Feb 12, 2013 1:14 am
Location: Monroe, NC

HTPC Specs: Show details

#4

Post by cwinfield » Sat Sep 13, 2014 8:42 pm

Have you tried updating the InfiniTV4 to the latest hw & fw?

Roofsmoker

Posts: 11
Joined: Mon Jun 09, 2014 6:57 pm
Location:

HTPC Specs: Show details

#5

Post by Roofsmoker » Sat Sep 13, 2014 8:54 pm

I have the latest firmware updates from ceton I think they may have been beta drivers. The only thing I have not done is reinstall the ceton software. which I will try now.

Roofsmoker

Posts: 11
Joined: Mon Jun 09, 2014 6:57 pm
Location:

HTPC Specs: Show details

#6

Post by Roofsmoker » Sat Sep 13, 2014 9:24 pm

Ok now I Have officially tried everything I can do on my end. Reinstalled ceton software to factory, reset my bridge and still getting the same in diagnostics, Card is busy with binding authentication process upgrading firmware.

Like I said anyone else having this issue in the nyc area, using time warner cable, with a ceton device refer it to ceton for some reason TWC last upgrade to the system is not taking well with ceton devices. hopefully this will be resolved by next week I really hate internet tv.

I even re-sat the device in the pc as a last ditch effort.

cwinfield

Posts: 575
Joined: Tue Feb 12, 2013 1:14 am
Location: Monroe, NC

HTPC Specs: Show details

#7

Post by cwinfield » Sat Sep 13, 2014 9:33 pm

Yeah TWC is great at breaking things. I hope you have sent Ceton a support request. What does your Cisco Cablecard Diag Screen say? Is your current version OS Ver: PKEY1.5.3_F.p.1101? You could try and send erkotz a PM

Cisco CableCARD(tm)
Diagnostics
H/W Model: 0802, Ver: 0012
MAC Address: XX:XX:XX:XX:XX
SL. No: PKKVWXJFR, Mode: MMODE
Boot Time
Tue Sep 9 2014, 9:31:19 PM GMT
Current Time
Sat Sep 13 2014, 9:28:40 PM GMT
Free Memory: 1519 KB
Bldr Ver: 124
OS Ver: PKEY1.5.3_F.p.1101
Build Time: Jun 6 2013, 16:26:58
Resource Status: 00021C1F00027DBF
BFS: Received, Hub ID: 6
CPU Channel, Generic Diags

Roofsmoker

Posts: 11
Joined: Mon Jun 09, 2014 6:57 pm
Location:

HTPC Specs: Show details

#8

Post by Roofsmoker » Sat Sep 13, 2014 11:36 pm

I cant get into any of the cards diags screens for the cable card because it is stuck in firmware upgrade, today when the technician first installed both freshly staged cards everything loaded up ok in the device menu you could see the mac address and the other diagnostic menus, in the cable card tab all the green checks that should be on were on. Than about 1 minute later on the refresh of screen the cable cards start giving this message below and nothing is accessible.

Your CableCARD is currently in the process of updating its firmware.
Please wait for it to complete. If it never finishes please contact your cable company for a replacement CableCARD.


CableCARD: Firmware Upgrade

Card Manufacturer: Cisco (Scientific-Atlanta)

Card Version: 65535

Card MAC: 00:00:00:00:00:00

Card Serial:

Card Authorization: Card is busy with binding authentication process

Card Message: CableCARD upgrade in progress. SC[0x00000001]




Card Applications:

and this is the end of the log:

Jan 1 00:30:37 ocur[21]: libctn91xx: Clearing pid filter on 4
Jan 1 00:30:38 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 00:30:38 ocur[21]: ocur: [0] Locked: 0 Acc E: 0
Jan 1 00:30:38 ocur[21]: ocur: [0] Tune finished to freq 657000
Jan 1 00:30:38 ocur[21]: libctn91xx: Clearing pid filter on 4
Jan 1 00:30:38 ocur[21]: upnp: Event(tuner[0]): PCRLock, "1"
Jan 1 00:30:39 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 00:30:39 ocur[21]: ocur: [0] Locked: 1 Acc E: 0
Jan 1 00:30:40 ocur[21]: ocur: [0] Tune finished to freq 657000
Jan 1 00:30:40 ocur[21]: libctn91xx: Clearing pid filter on 4
Jan 1 00:30:40 ocur[21]: upnp: Event(tuner[0]): PCRLock, "0"
Jan 1 00:30:40 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 00:30:40 ocur[21]: ocur: [0] Locked: 0 Acc E: 0
Jan 1 00:30:41 ocur[21]: ocur: [0] Tune finished to freq 658000
Jan 1 00:30:41 ocur[21]: libctn91xx: Clearing pid filter on 4

cwinfield

Posts: 575
Joined: Tue Feb 12, 2013 1:14 am
Location: Monroe, NC

HTPC Specs: Show details

#9

Post by cwinfield » Sat Sep 13, 2014 11:40 pm

Should have expected that. Why not disconnect the card coax, reboot then check circumventing the update process.

Roofsmoker

Posts: 11
Joined: Mon Jun 09, 2014 6:57 pm
Location:

HTPC Specs: Show details

#10

Post by Roofsmoker » Sun Sep 14, 2014 12:09 am

The technician tried that with the 2nd card an as soon as the coax was plugged in it starts giving the message I just posted and will stay locked on that message even after reboot and or removal of coax and card. so basically the card is locked until it finds a frequency and can start and finish the latest channel update for TWC. TWC phone techs cannot see the device either because it has to complete the firmware upgrade first, So Ceton and TWC need to communicate to get this issue addressed. I opened a ticket today with Ceton hopefully I wasn't the 1st and things will be working by Tuesday.

Roofsmoker

Posts: 11
Joined: Mon Jun 09, 2014 6:57 pm
Location:

HTPC Specs: Show details

#11

Post by Roofsmoker » Sun Sep 14, 2014 12:08 pm

GOOD NEWS! at around 10 pm last night I was watching Netflix off windows media center, and I got a pop up message to install new cable card. I minimized and checked the diagnostic and all my green checks were back except for CP auth which I have to call them for since its a new cable card.

So I guess TWC got there shit together and fixed the problem, because it just fixed itself with no supervision. Thanks for the help again, and hope this helps someone in the future.

Post Reply