There must be something about the way your headend operates that is involved with your problem. I run a couple of SD Primes and 3 Ceton devices (2 usb and 1 PCIe). So I have seen problems that will hit the ceton devices that miss the SD and I've seen problems that hid the SD that doesn't hit the ceton (Watch for m-CARD reset on the Primes along with sometime "lost" TAs)
20130916-23:00:26 CableCARD: Tuner0: vchannel 434 (549MHz-51) access = subscribed
20130916-23:07:24 CableCARD: tr/tr_status_rsp timeout error (cchost_tr_status:86)
20130916-23:07:24 CableCARD: Tuning Resolver reset
20130916-23:07:24 CableCARD: USB device 05A6:0008 connected
20130916-23:08:55 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:08:55 CableCARD: Tuning Resolver reset
20130916-23:08:55 CableCARD: USB device 05A6:0008 connected
20130916-23:10:27 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:10:27 CableCARD: Tuning Resolver reset
20130916-23:10:27 CableCARD: USB device 05A6:0008 connected
20130916-23:11:58 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:11:58 CableCARD: Tuning Resolver reset
20130916-23:11:58 CableCARD: USB device 05A6:0008 connected
20130916-23:13:29 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:13:29 CableCARD: Tuning Resolver reset
20130916-23:13:29 CableCARD: USB device 05A6:0008 connected
20130916-23:14:59 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:14:59 CableCARD: Tuning Resolver reset
20130916-23:15:00 CableCARD: USB device 05A6:0008 connected
20130916-23:16:30 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:16:30 CableCARD: Tuning Resolver reset
20130916-23:16:31 CableCARD: USB device 05A6:0008 connected
20130916-23:18:01 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:18:01 CableCARD: Tuning Resolver reset
20130916-23:18:01 CableCARD: USB device 05A6:0008 connected
20130916-23:19:32 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
20130916-23:19:32 CableCARD: Tuning Resolver reset
20130916-23:19:32 CableCARD: USB device 05A6:0008 connected
20130916-23:21:03 CableCARD: tr/tr_init_rsp timeout error (cchost_tr_discovery:75)
The lesson is there can be problems with either piece of equipment. Make sure you have installed the latest FW no matter which device you use and I keep the log open on the SD devices just incase I suddenly can't get a channel and have to juggle power cycling, etc. For me the devices are about equal in reliability and why one will do something when another doesn't is anyone's guess.
But enjoy your new tuner, and if you're adventuresome you can enable your Ceton Card and have more tuners....
One thing you did eliminate with the SD vs the Ceton is the USB bus on your host computer. Some are more troublesome than other and can be a point of concern with TA and communication with the TA. If you keep the Ceton card, you might want to invest in an add on USB card for the computer and see if that makes a difference. Just make sure to get a different chipset than is on your MB.
Latest beta firmware breaks comms with TA
Forum rules
Ceton no longer participate in this forum. Official support may still be handled via the Ceton Ticket system.
Ceton no longer participate in this forum. Official support may still be handled via the Ceton Ticket system.
- makryger
- Posts: 2132
- Joined: Sun Jun 05, 2011 2:01 pm
- Location: Illinois
- HTPC Specs:
I'm glad you finally got it working. I do get a general sense that the Ceton tuner is much more sensitive to signal issues than the HDHRP, based on what I've seen here. So that just means people who have a fine signal will do well with both, but if a signal is questionable in some way, then you'll see issues on the ceton sooner than the prime. Some people have the time and patience to troubleshoot and rewire their house and complain to the cable company-- and other people just try the HDHRP instead.
In my case, I apparently have a good signal with my InfiniTV4 card, (albeit after installing a motorola amplifier), so I can't complain.
In my case, I apparently have a good signal with my InfiniTV4 card, (albeit after installing a motorola amplifier), so I can't complain.
My Channel Logos XL: Get your Guide looking good! ~~~~ TunerSalad: Increase the 4-tuner limit in 7MC
-
- Posts: 146
- Joined: Tue Dec 04, 2012 2:11 am
- Location:
- HTPC Specs:
The whole problem could very well be related to the USB on my HTPC. I tried a USB 3.0 port at one point and that immediately blue-screened my computer. Other added benefits I have now since switching: I can have my HTPC idle to sleep. I couldn't do that before as the Ceton card would not wake up properly. My HTPC now also boots much faster after I disabled the Ceton card. Previously it would boot in to Windows pretty quick, but then hang for 30-45 seconds or so while (presumably) the Ceton card was firing up. I would have a Windows circle icon on my network adapter in the system tray. There would be no hard drive activity going on, it just looked like the system was frozen for that amount of time. When it finally started moving again everything loaded fine. Now, everything boots quickly like it should.
I'm guessing the card may work very well for someone else, different system, different location, different cable company or setup. Who knows. I plan on eventually pulling it and selling it, probably here at TGB, if there is interest.
I'm guessing the card may work very well for someone else, different system, different location, different cable company or setup. Who knows. I plan on eventually pulling it and selling it, probably here at TGB, if there is interest.