Ceton InfiniTV 6 Discussion

[werds]

DVR TV needs to be a rock solid appliance level experience

Yep, which is why this morning I decided to throw in the towel on the 6ETH experiment and back to Amazon it goes - will wait on the pci-e version and hope that taking the tuner off the network and back into the PC fixes things (well it did with the InfiniTV4 checked everything this morning and it all works fine...)

This is almost the exactly the same issue I'm experiencing. Please open a ticket and refer to my existing ticket [#VIU-909-50439]. The more data they have the better Ceton can troubleshoot.

Sorry, =( I uninstalled it early this morning and have decided to sit this one out and wait for the pci-e version or for better resolution from the community or Ceton on this one... time and sleep are precious in a household with a 3 year old and a newborn so after the past couple of days I need to cut losses before return window closes... (and to get caught back up on sleep!)

So it appears that a hot input line causes the Ceton Eth to tune VERY slowly. I just ordered a 6dB, a 10dB, a 16dB, and a 20dB attenuators and am going to do a bit more testing to see what the optimum input power level is for the fastest tuning.

That is very interesting considering most of us have needed to boost the signal coming into the house in order to get our InfiniTV4's to tune in channels correctly... what an odd and interesting tidbit...

[gsr]

I just ordered a 6dB, a 10dB, a 16dB, and a 20dB attenuators and am going to do a bit more testing to see what the optimum input power level is for the fastest tuning.

Can you post links for the attenuators you ordered? The signal strengths into my ETH's seem to be ranging from +4.7 to +8.0, so it might not hurt to try a 6db attenuator and see if that makes my tuning times any better than they are now (they aren't bad now, but if I can make them better for a few bucks, I might as well).

====================================

On another note, I had a recording that failed about 48 minutes into the show last night. The recording history shows:

"Recording of XXX began as scheduled on 5/27/2013 7:58:05 PM and was manually stopped on 5/27/2013 8:48:39 PM for use by another component."

At the time, there was 1 other recording which was using one of my SiliconDust HDHomeRun OTA tuners. No other PC or extender was attempting to use any of the Ceton tuners. I hadn't seen this error in a LONG time with my InfiniTV 4 PCIe cards.

[JohnW248]

I just ordered a 6dB, a 10dB, a 16dB, and a 20dB attenuators and am going to do a bit more testing to see what the optimum input power level is for the fastest tuning.

Can you post links for the attenuators you ordered? The signal strengths into my ETH's seem to be ranging from +4.7 to +8.0, so it might not hurt to try a 6db attenuator and see if that makes my tuning times any better than they are now (they aren't bad now, but if I can make them better for a few bucks, I might as well).

====================================

On another note, I had a recording that failed about 48 minutes into the show last night. The recording history shows:

"Recording of XXX began as scheduled on 5/27/2013 7:58:05 PM and was manually stopped on 5/27/2013 8:48:39 PM for use by another component."

At the time, there was 1 other recording which was using one of my SiliconDust HDHomeRun OTA tuners. No other PC or extender was attempting to use any of the Ceton tuners. I hadn't seen this error in a LONG time with my InfiniTV 4 PCIe cards.

You can find attenuators at a number of places including mcmelectronics. Of course they are cheap and you're going to pay more for shipping etc than for the devices so you might look thru and see if there is anything else you can't live without.

Usually a "manually stopped" with a network tuner is due to a network problem, packet loss, etc. Often seen where the tuner is on a port on a router and not on a switch. Best results are seen when the computers, extenders and tuners are on a switch and not on router ports or wireless.

[gsr]

You can find attenuators at a number of places including mcmelectronics. Of course they are cheap and you're going to pay more for shipping etc than for the devices so you might look thru and see if there is anything else you can't live without.

I was hoping he might have found a source with a better shipping option (such as Amazon) .

Usually a "manually stopped" with a network tuner is due to a network problem, packet loss, etc. Often seen where the tuner is on a port on a router and not on a switch. Best results are seen when the computers, extenders and tuners are on a switch and not on router ports or wireless.

All of the relevant items are connected to a 24 port HP ProCurve 1810G gigabit switch (which is the only thing connected to a LAN port on my ZyXel ZyWALL USG 100 router). The PC is currently using the integrated Realtek NIC. The only things in the house that use wireless are my iPad, iPhone, and Roku Streaming Stick (basically, only items that have no option other than wireless) via an Apple Airport Extreme running in wireless bridge mode.

[JohnW248]

Have you checked the log on the tuner? Open the web gui and click on the log tab and find the time (mine always start at Jan 1 when restarted so you'll have to adjust your search accordingly).

Just because something "might" have been the cause doesn't mean that was your cause, however you'd have to be monitoring for packet loss at the time of the occurrence to determine if that was it.

They are available from Amazon. You'll have to bulk up to get free shipping.

http://www.amazon.com/s/ref=nb_sb_ss_c_ ... Caps%2C254

[cybrsage]

I just ordered a 6dB, a 10dB, a 16dB, and a 20dB attenuators and am going to do a bit more testing to see what the optimum input power level is for the fastest tuning.

Can you post links for the attenuators you ordered? The signal strengths into my ETH's seem to be ranging from +4.7 to +8.0, so it might not hurt to try a 6db attenuator and see if that makes my tuning times any better than they are now (they aren't bad now, but if I can make them better for a few bucks, I might as well).

http://www.a1components.com/Categories/ ... ators.aspx

I bought 4 different attenuators and two cat6 1 foot cables for $11.61 (the cables were on special yesterday), including shipping. Shipping is $3.99, so you might as well buy everything else you need.

[gsr]

Have you checked the log on the tuner? Open the web gui and click on the log tab and find the time (mine always start at Jan 1 when restarted so you'll have to adjust your search accordingly).

Just because something "might" have been the cause doesn't mean that was your cause, however you'd have to be monitoring for packet loss at the time of the occurrence to determine if that was it.

I took a quick look in the logs, but I honestly don't know what to look for. I submitted a ticket with Ceton, so I'll wait and see what they have to say.

[gsr]

http://www.a1components.com/Categories/ ... ators.aspx

I bought 4 different attenuators and two cat6 1 foot cables for $11.61 (the cables were on special yesterday), including shipping. Shipping is $3.99, so you might as well buy everything else you need.

Thanks - if I spend $200, shipping is free .

[cybrsage]

http://www.a1components.com/Categories/ ... ators.aspx

I bought 4 different attenuators and two cat6 1 foot cables for $11.61 (the cables were on special yesterday), including shipping. Shipping is $3.99, so you might as well buy everything else you need.

Thanks - if I spend $200, shipping is free .

You gotta love the free shipping options.

[adam1991]

http://www.a1components.com/Categories/ ... ators.aspx

I bought 4 different attenuators and two cat6 1 foot cables for $11.61 (the cables were on special yesterday), including shipping. Shipping is $3.99, so you might as well buy everything else you need.

Thanks - if I spend $200, shipping is free .

no, shipping is *included*.

TANSTAAFL.

[JohnW248]

I took a quick look in the logs, but I honestly don't know what to look for. I submitted a ticket with Ceton, so I'll wait and see what they have to say.

Here is an example of a channel tune from start to stop for a normal tune. You'd look for this for start and then when it stops the reason for the stop and teardown.

Jan 4 11:44:16 ocur[21]: ocur: [0] Channel is scrambled, expecting CCI
Jan 4 11:44:16 ocur[21]: ocur: [0] Sending ca_pmt to CableCARD for program number 438 index 0
Jan 4 11:44:16 ocur[21]: libcetontrif: WARNING: No outstanding tune req/rsp, ignoring cnf.
Jan 4 11:44:16 ocur[21]: upnp: [192.168.180.2] Get(tuner[0]): Frequency "561000"
Jan 4 11:44:16 ocur[21]: upnp: [192.168.180.2] Get(mux[0]): ProgramNumber "438"
Jan 4 11:44:16 ocur[21]: ocur: [0] Adding pid 0x1939
Jan 4 11:44:17 ocur[21]: ocur: [0] CCI 02 arrived for program# 438
Jan 4 11:44:17 ocur[21]: ocur: [0-0.c0a8b402] Using digital cp 0x40000e2
Jan 4 11:44:17 ocur[21]: ocur: [0] Adding pid 0x19a9
Jan 4 11:44:17 ocur[21]: ocur: [0] Adding pid 0x19df
Jan 4 11:44:17 ocur[21]: ocur: [0] Adding pid 0x19ee
Jan 4 11:44:17 ocur[21]: ocur: [0] Adding pid 0x19f7
Jan 4 11:53:49 ocur[21]: ocur: STT time Tue May 28 01:07:46 2013 UTC
Jan 4 12:23:56 ocur[21]: ocur: STT time Tue May 28 01:37:48 2013 UTC
Jan 4 12:49:21 ocur[21]: upnp: [192.168.180.2] Calling Action(fdc[0]) RequestTables
Jan 4 12:49:21 ocur[21]: upnp: [192.168.180.2] Action(fdc[0]) RequestTables success
Jan 4 12:49:21 ocur[21]: upnp: [192.168.180.2] Calling Action(fdc[0]) RequestTables
Jan 4 12:49:21 ocur[21]: upnp: [192.168.180.2] Action(fdc[0]) RequestTables success
Jan 4 12:49:21 ocur[21]: upnp: [192.168.180.2] Calling Action(av[0]) Stop
Jan 4 12:49:21 ocur[21]: ocur: WARNING: [0] Disabling video
Jan 4 12:49:21 ocur[21]: ocur: [0] Program number set to 0, was 438
Jan 4 12:49:21 ocur[21]: upnp: [192.168.180.2] Action(av[0]) Stop success
Jan 4 12:49:22 ocur[21]: ocur: [0] rtp teardown for client 192.168.180.2:5001

[gsr]

I took a quick look in the logs, but I honestly don't know what to look for. I submitted a ticket with Ceton, so I'll wait and see what they have to say.

Here is an example of a channel tune from start to stop for a normal tune. You'd look for this for start and then when it stops the reason for the stop and teardown.

It looks like the tuner may have rebooted on its own. There are currently about 18 hours worth of logs on it, starting with:

Jan 1 00:00:02 syslogd started: BusyBox v1.17.2
Jan 1 00:00:02 ocur[21]: libctn91xx: compiled on 2013-04-22 22:24:52.971460
Jan 1 00:00:02 ocur[21]: libctn91xx: git id ff64d823a272425115cee74901ef59c0b69bf05c
Jan 1 00:00:02 ocur[21]: libctn91xx: Opening device /dev/ceton/ctn91xx_ctl0
Jan 1 00:00:02 ocur[21]: libctn91xx: system clock freq 100000000, ticks per us 100
Jan 1 00:00:02 ocur[21]: libctn91xx: Chip Info: CTN-9120 v7359 on board version 9
Jan 1 00:00:03 ocur[21]: ocur: detected eth
Jan 1 00:00:03 ocur[21]: ocur: inited slot number callback
Jan 1 00:00:03 ocur[21]: ocur: Set Mac Address: eth0 00:22:2c:80:81:6e
Jan 1 00:00:04 heartbeat[22]: libcetonnet: watching pid 21

There's a whole bunch of stuff that looks like it's related to startup, then a series of various chunks of messages that look like:

Jan 1 00:00:31 ocur[21]: cyrano: [zccard/s:INFO] SPDU - session_number(): 0003
Jan 1 00:00:31 ocur[21]: cyrano: [zccard/a:INFO] <- {oob_rx_tune_req}
Jan 1 00:00:31 ocur[21]: cyrano: [zccard/a:INFO] <- frequency_value = 75250Hz (0x1f9)
Jan 1 00:00:31 ocur[21]: cyrano: [zccard/a:INFO] <- data rate = 2048 kbps (Mode A)
Jan 1 00:00:31 ocur[21]: cyrano: [zccard/a:INFO] <- spectrum = non-inverted
Jan 1 00:00:31 ocur[21]: cyrano: [zccard/a:INFO] <- {/oob_rx_tune_req}
Jan 1 00:00:31 ocur[21]: cyrano: [zccard/a:INFO] -> {oob_rx_tune_cnf}
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] -> status = Tuning Denied - RF Receiver busy
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] -> {/oob_rx_tune_cnf}
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/s:INFO] SPDU - session_number(): 0003
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] <- {oob_rx_tune_req}
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] <- frequency_value = 75250Hz (0x1f9)
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] <- data rate = 2048 kbps (Mode A)
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] <- spectrum = non-inverted
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] <- {/oob_rx_tune_req}
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] -> {oob_rx_tune_cnf}
Jan 1 00:00:32 ocur[21]: cyrano: [zccard/a:INFO] -> status = Tuning Denied - RF Receiver busy

Presumably the "RF Receiver busy" messages are because the ETH was still booting up.

I also see the following:

Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): CaptureMode "Live"
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): DaylightSaving "1"
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): DescramblingMessage ""
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): EALocationCode ""
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): Language ""
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): OOB_MER "36 db/10"
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): RatingRegion ""
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): SourceId "0"
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): TimeZone "-300"
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): VirtualChannelNumber "0"
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): FirmwareUpdateStatus "Done. Please reboot your computer."
Jan 1 11:30:58 ocur[21]: upnp: [192.168.1.204] Get(cas[0]): LastResolveStatus "Unknown"
Jan 1 11:31:26 ocur[21]: upnp: [192.168.1.204] Get(octa[6]): tr_status "Disabled"
Jan 1 11:31:26 ocur[21]: upnp: [192.168.1.204] Get(octa[7]): tr_status "Disabled"
Jan 1 11:31:26 ocur[21]: upnp: [192.168.1.204] Get(octa[8]): tr_status "Disabled"
Jan 1 11:33:53 ocur[21]: ocur: STT time Tue May 28 12:24:26 2013 UTC
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): CaptureMode "Live"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): DaylightSaving "1"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): DescramblingMessage ""
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): EALocationCode ""
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): Language ""
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): OOB_MER "36 db/10"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): RatingRegion ""
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): SourceId "0"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): TimeZone "-300"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): VirtualChannelNumber "0"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): FirmwareUpdateStatus "Done. Please reboot your computer."
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): LastResolveStatus "Unknown"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[6]): tr_status "Disabled"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[7]): tr_status "Disabled"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[8]): tr_status "Disabled"

Note the:

FirmwareUpdateStatus "Done. Please reboot your computer."

messages - I hadn't requested a firmware update, so I'm not sure if that's just normal startup stuff or something else.

I'll be interested in hearing what Ceton has to say.

[JohnW248]

Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): VirtualChannelNumber "0"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): FirmwareUpdateStatus "Done. Please reboot your computer."
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): LastResolveStatus "Unknown"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[6]): tr_status "Disabled"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[7]): tr_status "Disabled"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[8]): tr_status "Disabled"

It will be interesting to see what Eric might have to say. It looks like it didn't get the FW update finish and also if you have a Tuning Resolver there is an issue with it being disabled as well.

You might try typing "reboot" in the command box at the bottom of the log tab and see if it starts with the TR and without the FW update, that's a different start than a power plug pull and reconnect.

[gsr]

Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): VirtualChannelNumber "0"
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): FirmwareUpdateStatus "Done. Please reboot your computer."
Jan 1 11:36:49 ocur[21]: upnp: [192.168.1.205] Get(cas[0]): LastResolveStatus "Unknown"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[6]): tr_status "Disabled"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[7]): tr_status "Disabled"
Jan 1 11:37:21 ocur[21]: upnp: [192.168.1.205] Get(octa[8]): tr_status "Disabled"

It will be interesting to see what Eric might have to say. It looks like it didn't get the FW update finish and also if you have a Tuning Resolver there is an issue with it being disabled as well.

You might try typing "reboot" in the command box at the bottom of the log tab and see if it starts with the TR and without the FW update, that's a different start than a power plug pull and reconnect.

No tuning adapter - I've got Verizon FIOS. And yeah, I'm curious about the firmware update messages - the diagnostic page is reporting the correct firmware (13.5.6.133) and hardware (7359) versions and there were no errors when I updated them when I initially set them up. I included a diagnostic with my ticket, which I would assume includes the logs, so hopefully Ceton will have what they need.

[miles267]

Amazing Ceton Tech Support experience today worth sharing. Just got my InfiniTV 6 ETH. Wasn't working with the same TA that previously worked with my InfiniTV 4 PCIe. WebUI showed TA was paired but waiting for a channel map. This repeated for days. After only 2 business days, Ceton provided me a beta firmware that allowed for what they considered a larger than average channel map. Flashed to beta firmware via webUI. Within 5 mins the error was resolved and all previously inaccessible SDV channels could be tuned and watched.

[JohnW248]

Amazing Ceton Tech Support experience today worth sharing. Just got my InfiniTV 6 ETH. Wasn't working with the same TA that previously worked with my InfiniTV 4 PCIe. WebUI showed TA was paired but waiting for a channel map. This repeated for days. After only 2 business days, Ceton provided me a beta firmware that allowed for what they considered a larger than average channel map. Flashed to beta firmware via webUI. Within 5 mins the error was resolved and all previously inaccessible SDV channels could be tuned and watched.

Could you add your cable system and type of headend? (Moto or Cisco)
never mind, I found your earlier post (#421) and you're on a MOTO headend so it was an issue with the Moto TA, your cable system SDV channel map and the new Ceton device.

A good heads up for others having TA issues on Moto headends.

[gsr]

No tuning adapter - I've got Verizon FIOS. And yeah, I'm curious about the firmware update messages - the diagnostic page is reporting the correct firmware (13.5.6.133) and hardware (7359) versions and there were no errors when I updated them when I initially set them up. I included a diagnostic with my ticket, which I would assume includes the logs, so hopefully Ceton will have what they need.

Ceton got back to me in the early evening last night. For now, they've requested that I enable some additional logging in WMC and report back to them with another diagnostic dump when (if?) the problem happens again. Since the regular TV season is wrapping up, I'll be scheduling some extra dummy recordings on the same channel to see if I can reproduce the problem.

[FlyEspresso]

Hey–

I'm building a Media Center as an alternative to the Tivo Premier XL4 I just recently got (it's going back) as frankly didn't like the 12 month contract at $15 a month... In my case I got it at a local store so never heard about that till after I activated it (it's a long story).

Regardless I'm debating between the Infinitv 4 and 6– seems I might be better off with the 4? I have amazing signal (new 2010 highrise in downtown seattle) so maybe the 6 eth will work?

Any suggestions?

Would love to order one today so it arrives at the same time as all my goodies tomorrow! I'm not really worried if the first time I tune channels it takes a few seconds, the system will be an always on (no sleep) appliance in a shuttle DS61 case with an i3 3225 (HD4000).

Thanks in advance,
Phil

[woodchuck]

I would go for the 6. I had a 4 and moved to the 6 and am very happy with it.

[grinchy]

Hey–

I'm building a Media Center as an alternative to the Tivo Premier XL4 I just recently got (it's going back) as frankly didn't like the 12 month contract at $15 a month... In my case I got it at a local store so never heard about that till after I activated it (it's a long story).

Regardless I'm debating between the Infinitv 4 and 6– seems I might be better off with the 4? I have amazing signal (new 2010 highrise in downtown seattle) so maybe the 6 eth will work?

Any suggestions?

Would love to order one today so it arrives at the same time as all my goodies tomorrow! I'm not really worried if the first time I tune channels it takes a few seconds, the system will be an always on (no sleep) appliance in a shuttle DS61 case with an i3 3225 (HD4000).

Thanks in advance,
Phil

Is a a network based tuner a huge priority for your needs? Are you planning on using WMC extenders like the Echo/Xbox/etc?

If you don't need a networked based tuner, you may want to wait a few more days and look at the iTV6 PCIe (vs. the iTV6 ETH) - I think they said it was supposed to drop next month (June?). I have a iTV4 PCie and will most likely upgrade to the 6 tuner PCIe... personally, I like the idea of having everything in the PC and no real interest in sharing networked tuners since everything is copy-once for me.