Been reading a lot of horror stories about CableCard MCE's and setup issues.  At the same time, a number of new OEMs are starting to ship CableCard enabled MCE's.

I just ordered a HP m8100y with CableCard.  I plan to use this with Time Warner in the Austin area.   To watch shows I will always use my 360's as extenders into this PC, but I was wondering if during the initial CableCard setup my PC DVI display had to be HDCP compliant?

Has any one had any success with Time Warner and CableCards with an HP m8100y?

 Thanks!

We're actually not doing anything smart during setup - so if you're not hooked up to an HDCP compliant monitor, you won't be able to watch TV on that monitor, but you can successfully get through setup then connect your 360s.

I've had requests to detect the monitor during TV setup and display something to the user that tells him/her his display isn't compliant if it isn't (not say anything if it is), but I haven't agreed to that yet. I kind of feel like that information isn't all that useful at that point - what's a user going to do, stop going through setup and run out to Best Buy and get a new TV? Not that finding out by trying to watch TV and having it fail is much better, but it ties the action the user tried to do to something, vs. providing information and another page to click through during setup when we know people barely read what's there already.

Will standard channel still come in on my local PC that has a non-HDCP monitor? 

Will there be any warning when my wife for some reason tries to watch TV on the PC?

I could go either way on the during the install setup about displaying a warning if the display is found to be non-HDCP.  I'd rather see a warning when someone tried to watch TV if that is not there already.

 

The answer depends on whether you have a CableCARD inserted or not; all recordings made with the CableCARD in are subject to these rules based on connection type (I've simplified a tiny bit, but should be accurate):

DVI/HDMI with HDCP: Windowed mode, Downres applied - 520,000 pixels; full-screen: full resolution

VGA/Composite/S-Video/Component: Downres applied; 520,000 pixels

 

 

Sounds good, I ended up just buing a HDCP capable Samsung LCD over the weekend.  Would rather spend a few hundred dollars than confused my wife. :)

I recently learned from AVS Forums that the internal analog tuner will no longer work once I set up my external ATI CableCard adapter.  Time Warner is coming out tomorrow to give me a cablecard.

Jessica, before they arrive what exactly should I do?  Should I disconnect cable going to the internal tuner and set up the external tuner ATI tuner?  If so, what kind of tuner do I set the ATI CableCard device up as before I have the CableCard?  Do I choose the digital guide listings or the normal (non-digital) guide listings?  The MS page was not clear on this.  Thanks!

It shouldn't matter if the internal analog is connected; if you go through automatic signal detection with the TV signal connected to the ATI digital cable tuner, Media Center will "prefer" that and will set that one up only. You'll get some annoying page that says something like "CableCARD rocks. Don't you want one? If you have one, put it in now." Click past that - you'll get to set up the CableCARD later. Then you should pick the digital guide listings.

When Time Warner comes, open Media Center and then just insert the CableCARD. Media Center should detect it and say "Do you want to set up the CableCARD now?" You say yes, and you only have to do the CableCARD part, not all the rest of TV setup.

Let me know how it goes.

Things have not been working with my HP m8100y and Time Warner.  The tech came out yesterday to install the CableCard.  Below are some of the issues we saw and are seeing.

1) Non-digital channels (0-99) were not working on the tuner without the CableCard plugged in.  I had tried to set this up the day before.  I know that my signal strength is good.  I've tested this before and it worked fine with my analog tuner.  The tech also checked my signal strength later and said that it looks good.

2) After shutting down, unplugging the ATI external device, putting in the CableCard, and powering back up I went through the Set up signal menus.  The Digital Tuner was detected correctly and the tech called in the CableCard ID and Host ID.  Local channels worked, but none of the digital ( > 99) or HD channels worked.  The tech had to leave.  Under the Network ATI Device settings the Card Status was Error.  I called TW tech support, read them all the numbers and they said that the CableCard ID did not match the CableCard Serial number of file.  They sent a tech back over with a new CableCard.

3) Powered down, unplugged the ATI external device, and plugged in the new CableCard.  Upon booting and running through the TV Signal Setup everything went fine.  Tech called in the CableCard ID and Host ID.  Setup the guide listings and went to TV, got a message saying that no tuner was found.  Restarted Media Center, same deal.   Went through Signal Setup again and it did not find the Digital Cable Device, only the HD analog antenta.  The ATI device did show up in the Network settings with a Card status of inserted.

4) Restarted, went through the TV Signal setup and it found the digital cable again, tuning to analog stations works (< 99), but I have a Card status of Error again.  Just like in (2) above.  The tech said that all the numbers matched.  He left.  Below is the log from the trace window:

[00:00000.0] DK3LedManager.cpp => ChangeLED: process state 'System Init Start' (0)
[01:00000.0] DK3LedManager.cpp => ChangeLED: process state 'System Init Step' (3)
[02:00000.0] DK3LedManager.cpp => ChangeLED: process state 'System Init OK' (1)
[03:00000.5] DK3LedManager.cpp => ChangeLED: process state 'DHCP Complete' (5)
[04:00000.5] dhcp_server.cpp => UdpStart: server IP address 192.168.3.53
[05:00000.6] dhcp_server.cpp => UdpProcessData: no IP for MAC address 0006BB1009FF
[06:00000.6] dhcp_server.cpp => UdpProcessData: no IP for MAC address 0006BB1009FF
[07:00001.6] dhcp_server.cpp => UdpProcessData: IP 192.168.3.49 is issued. Expire in 0xFFFFFFFF s
[08:00004.2] ctrpanel.c => ControlPanelState: device ATI TV Wonder OpenCable Receiver (09FF)
[09:00004.2] ctrpanel.c => ControlPanelState: firmware {D9CA0D41-672C-462c-A354-D8EC45BE59A8}
[10:00004.2] ctrpanel.c => ControlPanelState: version 1.15.2007.04051 [Apr 5 2007 - 16:48:56]
[11:00007.1] rio_user.cpp => Ati binary loaded is : [ATI LIB=CTRL.bin,08.03.20104]
[12:00010.1] DK3LedManager.cpp => ChangeLED: process state 'Card in' (7)
[13:00010.3] cas.c => pod1aReportModuleInserted: card detected 'ScientificAtlanta', 'POD Module', 0. Status 0x0
[14:00011.0] upnpcc.c => upnp_FindDeviceService: failed to acquire service lock 0x0
[15:00011.0] gendiag.c => gd_diagnostic_req: pod1aDiagnosticGet failed with 0x81000015
[16:00011.2] fdc.c => pod2cOOBRXTune: tuning OOB at 70000 KHz, 1544, 0
[17:00012.5] fdc.c => pod2cOOBRXTune: tuning OOB at 70000 KHz, 1544, 1
[18:00013.0] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[19:00013.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[20:00016.3] fdc.c => FDCState: loaded 0 table sections from NVRAM
[21:00017.6] diag.c => DiagState: host ID is '0840002DFC'
[22:00028.0] drm.c => DrmOnStatusChange: current DRM status Green
[23:00041.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[24:00042.3] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[25:00042.7] DriDevice.cpp => FdcDeviceEvent: FDC lock lost when IB tuner is tuned to 141000 - 0x1000
[26:00042.8] DK3LedManager.cpp => ChangeLED: process state 'OOB Tuner Unlocked' (16)
[27:00044.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[28:00045.8] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[29:00047.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[30:00048.3] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[31:00050.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[32:00051.4] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[33:00053.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[34:00054.3] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[35:00056.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[36:00057.3] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[37:00059.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[38:00060.3] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[39:00062.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[40:00063.3] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[41:00066.0] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[42:00066.3] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[43:00068.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[44:00069.8] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[45:00071.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[46:00072.6] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[47:00074.9] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[48:00075.5] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[49:00094.1] DkSTime.c => Device safe time: 9/12/2007 14:29:18, UTC time: 9/12/2007 14:29:18
[50:00103.0] DriDevice.cpp => FdcDeviceEvent: FDC lock lost when IB tuner is tuned to 141000 - 0x1000
[51:00106.6] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[52:00107.0] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[53:00192.2] DK3LedManager.cpp => ChangeLED: process state 'Card out' (10)
[54:00196.0] trans.c => SendCommandTpdu: link layer failed TPDU 4c39b0 with 0x8114400E
[55:00196.0] cas.c => pod1aReportModuleRemoved: card has been removed
[56:00196.0] DkDrmTx.c => Invalid protection state 0x2000000 detected. License rotation aborted
[57:00196.0] DkDrmTx.c => Invalid protection state 0x2000000 detected. License rotation aborted
[58:00263.3] rftuner.c => TunerSetTunerParameters: frequency 73250, modulation NTSC-M (parsing result 0x0)
[59:00267.9] rftuner.c => TunerSetTunerParameters: frequency 72000, modulation NTSC-M (parsing result 0x0)
[60:00275.7] rftuner.c => TunerSetTunerParameters: frequency 121250, modulation NTSC-M (parsing result 0x0)
[61:00282.1] rftuner.c => TunerSetTunerParameters: frequency 120000, modulation NTSC-M (parsing result 0x0)
[62:00283.1] rftuner.c => TunerSetTunerParameters: frequency 120000, modulation NTSC-M (parsing result 0x0)
[63:00283.8] rftuner.c => TunerSetTunerParameters: frequency 121250, modulation NTSC-M (parsing result 0x0)
[64:00285.6] rftuner.c => TunerSetTunerParameters: frequency 120000, modulation NTSC-M (parsing result 0x0)
[65:00287.0] rftuner.c => TunerSetTunerParameters: frequency 120000, modulation NTSC-M (parsing result 0x0)
[66:00287.7] rftuner.c => TunerSetTunerParameters: frequency 127250, modulation NTSC-M (parsing result 0x0)
[67:00289.5] rftuner.c => TunerSetTunerParameters: frequency 133250, modulation NTSC-M (parsing result 0x0)
[68:00291.2] rftuner.c => TunerSetTunerParameters: frequency 132000, modulation NTSC-M (parsing result 0x0)
[69:00292.8] rftuner.c => TunerSetTunerParameters: frequency 132000, modulation NTSC-M (parsing result 0x0)
[70:00294.5] rftuner.c => TunerSetTunerParameters: frequency 133250, modulation NTSC-M (parsing result 0x0)
[71:00295.7] rftuner.c => TunerSetTunerParameters: frequency 132000, modulation NTSC-M (parsing result 0x0)
[72:00297.6] rftuner.c => TunerSetTunerParameters: frequency 132000, modulation NTSC-M (parsing result 0x0)
[73:00298.4] rftuner.c => TunerSetTunerParameters: frequency 139250, modulation NTSC-M (parsing result 0x0)
[74:00299.4] tunemngr.c => nav_SetMacrovisionProtection( 0, 3 )
[75:00299.4] DkDrmTx.c => wmdrm_UpdateCopyProtectionInfo(0, 3, 0, 1)
[76:00300.4] rftuner.c => TunerSetTunerParameters: frequency 145250, modulation NTSC-M (parsing result 0x0)
[77:00302.9] rftuner.c => TunerSetTunerParameters: frequency 151250, modulation NTSC-M (parsing result 0x0)
[78:00304.3] rftuner.c => TunerSetTunerParameters: frequency 157250, modulation NTSC-M (parsing result 0x0)
[79:00307.1] rftuner.c => TunerSetTunerParameters: frequency 77250, modulation NTSC-M (parsing result 0x0)
[80:00310.0] rftuner.c => TunerSetTunerParameters: frequency 83250, modulation NTSC-M (parsing result 0x0)
[81:00311.3] rftuner.c => TunerSetTunerParameters: frequency 83250, modulation NTSC-M (parsing result 0x0)
[82:00312.4] SITableParsing.cpp => TableParser: can not find matching filter handle for 0x334B24
[83:00313.4] rftuner.c => TunerSetTunerParameters: frequency 85250, modulation NTSC-M (parsing result 0x0)
[84:00314.7] rftuner.c => TunerSetTunerParameters: frequency 84000, modulation NTSC-M (parsing result 0x0)
[85:00316.5] rftuner.c => TunerSetTunerParameters: frequency 84000, modulation NTSC-M (parsing result 0x0)
[86:00317.1] rftuner.c => TunerSetTunerParameters: frequency 175250, modulation NTSC-M (parsing result 0x0)
[87:00318.8] rftuner.c => TunerSetTunerParameters: frequency 174000, modulation NTSC-M (parsing result 0x0)
[88:00321.3] rftuner.c => TunerSetTunerParameters: frequency 175250, modulation NTSC-M (parsing result 0x0)
[89:00323.1] rftuner.c => TunerSetTunerParameters: frequency 181250, modulation NTSC-M (parsing result 0x0)
[90:00326.0] rftuner.c => TunerSetTunerParameters: frequency 187250, modulation NTSC-M (parsing result 0x0)
[91:00328.4] rftuner.c => TunerSetTunerParameters: frequency 193250, modulation NTSC-M (parsing result 0x0)
[92:00330.0] rftuner.c => TunerSetTunerParameters: frequency 199250, modulation NTSC-M (parsing result 0x0)
[93:00331.7] rftuner.c => TunerSetTunerParameters: frequency 199250, modulation NTSC-M (parsing result 0x0)
[94:00333.9] rftuner.c => TunerSetTunerParameters: frequency 198000, modulation NTSC-M (parsing result 0x0)
[95:00335.1] rftuner.c => TunerSetTunerParameters: frequency 205250, modulation NTSC-M (parsing result 0x0)
[96:00337.8] rftuner.c => TunerSetTunerParameters: frequency 211250, modulation NTSC-M (parsing result 0x0)
[97:00418.7] rftuner.c => TunerSetTunerParameters: frequency 591250, modulation 8-VSB (parsing result 0x0)
[98:00425.5] rftuner.c => TunerSetTunerParameters: frequency 597250, modulation 8-VSB (parsing result 0x0)
[99:00432.3] rftuner.c => TunerSetTunerParameters: frequency 603250, modulation 8-VSB (parsing result 0x0)
[00:00439.2] rftuner.c => TunerSetTunerParameters: frequency 645250, modulation 8-VSB (parsing result 0x0)
[01:00446.0] rftuner.c => TunerSetTunerParameters: frequency 573250, modulation 8-VSB (parsing result 0x0)
[02:00452.9] rftuner.c => TunerSetTunerParameters: frequency 621250, modulation 8-VSB (parsing result 0x0)
[03:00459.7] rftuner.c => TunerSetTunerParameters: frequency 615250, modulation 8-VSB (parsing result 0x0)
[04:00466.6] rftuner.c => TunerSetTunerParameters: frequency 579250, modulation 8-VSB (parsing result 0x0)
[05:00473.4] rftuner.c => TunerSetTunerParameters: frequency 633250, modulation 8-VSB (parsing result 0x0)
[06:00480.3] rftuner.c => TunerSetTunerParameters: frequency 549250, modulation 8-VSB (parsing result 0x0)
[07:00487.1] rftuner.c => TunerSetTunerParameters: frequency 501250, modulation 8-VSB (parsing result 0x0)
[08:00493.9] rftuner.c => TunerSetTunerParameters: frequency 693250, modulation 8-VSB (parsing result 0x0)
[09:00500.8] rftuner.c => TunerSetTunerParameters: frequency 651250, modulation 8-VSB (parsing result 0x0)
[10:00507.6] rftuner.c => TunerSetTunerParameters: frequency 639250, modulation 8-VSB (parsing result 0x0)
[11:00514.4] rftuner.c => TunerSetTunerParameters: frequency 567250, modulation 8-VSB (parsing result 0x0)
[12:00521.3] rftuner.c => TunerSetTunerParameters: frequency 555250, modulation 8-VSB (parsing result 0x0)
[13:00557.7] DK3LedManager.cpp => ChangeLED: process state 'Card in' (7)
[14:00558.1] cas.c => pod1aReportModuleInserted: card detected 'ScientificAtlanta', 'POD Module', 0. Status 0x0
[15:00559.4] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 0
[16:00559.7] fdc.c => pod2cOOBRXTune: tuning OOB at 74000 KHz, 1544, 1
[17:00708.6] DK3LedManager.cpp => ChangeLED: process state 'OOB Tuner Locked' (15)
[18:00717.0] si.c => si_parse_STT > current network time is 1189609800
[19:00720.2] si.c => si_updateVcm > current VCM size is 20
[20:00720.6] si.c => si_updateVcm > current VCM size is 40
[21:00720.6] si.c => si_updateVcm > current VCM size is 60
[22:00720.6] si.c => si_updateVcm > current VCM size is 80
[23:00720.6] si.c => si_updateVcm > current VCM size is 100
[24:00720.6] si.c => si_updateVcm > current VCM size is 120
[25:00720.6] si.c => si_updateVcm > current VCM size is 140
[26:00720.6] si.c => si_updateVcm > current VCM size is 160
[27:00720.6] si.c => si_updateVcm > current VCM size is 180
[28:00721.0] si.c => si_updateVcm > current VCM size is 200
[29:00721.0] si.c => si_updateVcm > current VCM size is 220
[30:00721.0] si.c => si_updateVcm > current VCM size is 240
[31:00721.0] si.c => si_updateVcm > current VCM size is 260
[32:00721.4] si.c => si_updateVcm > current VCM size is 280
[33:00721.8] si.c => si_updateVcm > current VCM size is 300
[34:00762.1] gendiag.c => gd_diagnostic_req: pod1aDiagnosticGet failed with 0x81003007
[35:00762.1] gendiag.c => gd_diagnostic_req: pod1aDiagnosticGet failed with 0x81003007
[36:00762.1] gendiag.c => gd_diagnostic_req: diagnostic ID 9 is not supported
[37:00762.1] gendiag.c => gd_diagnostic_req: diagnostic ID 10 is not supported
[38:00762.1] gendiag.c => gd_diagnostic_req: diagnostic ID 11 is not supported
[39:00762.1] gendiag.c => gd_diagnostic_req: diagnostic ID 12 is not supported
[40:00852.4] cas.c => CASSetChannel: channel number 3, source ID 0, mode Live (parsing result 0)
[41:00853.1] cas.c => CASSetChannel: returning 0x103002
[42:00867.1] cas.c => CASSetChannel: channel number 239, source ID 0, mode Live (parsing result 0)
[43:00867.5] cas.c => CASSetChannel: returning 0x103002
[44:00884.5] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[45:00884.5] trans.c => SendDataTpdu: link layer failed TPDU 607cec with 0x8115400B
[46:00884.5] cas.c => PODware reports error 0x8115400B. POD Error Code is 0 (0x0). Error text: CableCard is not responding
[47:00889.7] DK3LedManager.cpp => ChangeLED: process state 'Card in' (7)
[48:00894.1] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[49:00894.1] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[50:00894.1] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[51:00894.1] link.c => link_Start: transport layer failed with -2129313784
[52:00894.1] trans.c => trans_Stop: can not shutdown nonexistent connection
[53:00903.7] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[54:00903.7] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[55:00903.7] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[56:00903.7] link.c => link_Start: transport layer failed with -2129313784
[57:00903.7] trans.c => trans_Stop: can not shutdown nonexistent connection
[58:00903.7] cas.c => pod1aReportModuleInserted: card detected 'ScientificAtlanta', 'POD Module', 0. Status 0x81154008
[59:00903.7] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text:
[60:00913.3] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[61:00913.3] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[62:00913.3] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[63:00913.3] link.c => link_Start: transport layer failed with -2129313784
[64:00913.3] trans.c => trans_Stop: can not shutdown nonexistent connection
[65:00919.5] cas.c => CASSetChannel: channel number 1511, source ID 0, mode Live (parsing result 0)
[66:00919.8] cas.c => CASSetChannel: returning 0x103002
[67:00922.9] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[68:00922.9] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[69:00922.9] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[70:00922.9] link.c => link_Start: transport layer failed with -2129313784
[71:00922.9] trans.c => trans_Stop: can not shutdown nonexistent connection
[72:00932.4] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[73:00932.4] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[74:00932.4] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[75:00932.4] link.c => link_Start: transport layer failed with -2129313784
[76:00932.4] trans.c => trans_Stop: can not shutdown nonexistent connection
[77:00942.0] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[78:00942.0] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[79:00942.0] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[80:00942.0] link.c => link_Start: transport layer failed with -2129313784
[81:00942.0] trans.c => trans_Stop: can not shutdown nonexistent connection
[82:00951.6] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[83:00951.6] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[84:00951.6] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[85:00951.6] link.c => link_Start: transport layer failed with -2129313784
[86:00951.6] trans.c => trans_Stop: can not shutdown nonexistent connection
[87:00961.2] phys.c => readChannelData > Error, DA not set after 5s - STATUS is 0x40
[88:00961.2] trans.c => SendCommandTpdu: link layer failed TPDU 4c091c with 0x8115400B
[89:00961.2] cas.c => PODware reports error 0x81154008. POD Error Code is 10 (0xA). Error text: [10] No Create_T_C reply received from CableCard
[90:00961.2] link.c => link_Start: transport layer failed with -2129313784
[91:00961.2] trans.c => trans_Stop: can not shutdown nonexistent connection

I'm unsure why this is happening, but I forwarded the info to our digital cable folks. They will likely get back to me with something to share with you.

Looks like a bad CableCARD to me.  Has TWC brought a second (or even third) CableCARD out to try?

Yes, they brought the first - things did not work.  When I called they said that the CableCard ID did not match the CableCard Serial # they had on file, so they could not link.

TW then brought me a second card.  They verified that all the ID's match, but now I get a status of "Error" after several minutes of a status of "Inserted".  The log attached above is from this second CableCard.

BTW, I am using MS OneCare with all the 360 ports open (can connect just fine to my MCE box via them) and both LED lights on the External ATI digital cable box are green.

All CableCARDs are flakey, so you might want to see if they will bring another card to try.

Chris - Moderator:

All CableCARDs are flakey, so you might want to see if they will bring another card to try.

I agree with Chris, try another card. Plus, TW is ridiculous. If they tell you that the ID doesn't match the device or whatever, THEY CAN CHANGE THIS!@!!! The problem is that none of these techs are trained (ok, maybe very few) for Media Center PC's, which the pairing is different than TVs. Just insist that they can change the data on their side to match the information, and then they can push a signal from their end which should light things up.

btw, just to make sure your tuner's ok, you tested QAM on it right? And all the regular channels work?

Yes, regular (<99) channels work. QAM appears to work also, at least occassionall, for instance channel 1511 and the such (local HD stations) do work.   After awhile once the CableCard status goes from "Inserted" to "Error", nothing appears to work, even regular stations.  Regardless, based on what Jessica comes back with I'll see how hard it will be to get HP to send me a different ATI Digital Tuner device.  I'll also try to get another CableCard from TW if things do not turn around tonight when I get home to toy with things again...

if QAM & NTSC channels work fine without the cable card, then it's not a problem with the Tuner. It's a problem with the card and/or the pairing.

Do you have a TV with Cablecard, or a STB? that way you could verify the cards good before you waste more time.