Reply
New Visitor
jtweedy
Posts: 1
Registered: ‎08-05-2012

Re: I thought my BLAST Internet was going to double in speed?

I am having same issue. I have contacted Comcast and every customer service representative tells me that I have received this information in error. 

 

Based on advertising, Blast speed is supposed to double, from 25 - 50Mbs. I still measure at 25Mbs.

I live in NH, just north of Boston.

 

Here is the Contact #'s given to me from Comcast: Case ID 11052448

 

Here are my details you asked another user:

 

 

Modem Model #: UBEE DDM3513

 

Router Model#: Linksys WRT-54g

 

 

Upstream

 


US-1
US-2 US-3 US-4 Channel Type 2.0 N/A N/A N/A Channel ID 2 N/A N/A N/A Frequency 
(Hz)
36500000 N/A N/A N/A Ranging Status Success N/A N/A N/A Modulation 64QAM N/A N/A N/A Symbol Rate 
(KSym/sec)
5120 N/A N/A N/A Mini-Slot Size 4 N/A N/A N/A Power Level 
(dBmV)
52.25 N/A N/A N/A T1 Timeouts 0 0 0 0 T2 Timeouts 0 0 0 0 T3 Timeouts 0 0 0 0 T4 Timeouts 0 0 0 0

 

DOWNSTREAM:

 


  DownDS-1
DS-2 DS-3 DS-4                         Frequency 705000000 711000000 717000000 723000000 Lock Status 
(QAM Lock/FEC Sync/MPEG Lock)
Y/Y/Y Y/Y/Y Y/Y/Y Y/Y/Y Channel Id 59 60 61 62 Modulation 256QAM 256QAM 256QAM 256QAM Symbol Rate 
(Msym/sec)
5.360537 5.360537 5.360537 5.360537 Interleave Depth I=32
J=4
I=32
J=4
I=32
J=4
I=32
J=4
Power Level 
(dBmV)
0.45 -0.22 -0.87 -0.64 RxMER 
(d:smileycool:
37.09 36.84 36.84 36.84 Correctable
Codewords
0 0 0 0 Uncorrectable
Codewords
1418 1455 1416 1372

 

 

 

Error Log:

 

 

First Time Last Time Priority Description Fri Aug 3 15:57:56 2012 Fri Aug 3 15:57:56 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 15:58:04 2012 Fri Aug 3 15:58:04 2012 Warning (5) MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 16:36:49 2012 Fri Aug 3 16:36:54 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 16:36:54 2012 Fri Aug 3 16:36:54 2012 Error (4) DCC-ACK not received;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 16:36:55 2012 Fri Aug 3 16:37:05 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 16:37:35 2012 Fri Aug 3 16:37:35 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Fri Aug 3 16:37:53 2012 Fri Aug 3 16:37:53 2012 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Fri Aug 3 16:38:07 2012 Fri Aug 3 16:38:11 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 16:38:23 2012 Fri Aug 3 16:38:23 2012 Warning (5) MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 16:41:50 2012 Fri Aug 3 17:32:01 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:32:01 2012 Fri Aug 3 17:32:01 2012 Error (4) DCC-ACK not received;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 17:32:02 2012 Fri Aug 3 17:32:12 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:32:42 2012 Fri Aug 3 17:32:42 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Fri Aug 3 17:32:56 2012 Fri Aug 3 17:32:56 2012 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Fri Aug 3 17:33:09 2012 Fri Aug 3 17:33:12 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:33:21 2012 Fri Aug 3 17:33:21 2012 Warning (5) MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 17:36:57 2012 Fri Aug 3 17:37:01 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:37:02 2012 Fri Aug 3 17:37:02 2012 Error (4) DCC-ACK not received;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 17:37:02 2012 Fri Aug 3 17:37:13 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:37:43 2012 Fri Aug 3 17:37:43 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Fri Aug 3 17:37:43 2012 Fri Aug 3 17:37:57 2012 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Fri Aug 3 17:38:08 2012 Fri Aug 3 17:38:11 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:38:21 2012 Fri Aug 3 17:38:21 2012 Warning (5) MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 17:51:59 2012 Fri Aug 3 17:52:03 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:52:03 2012 Fri Aug 3 17:52:03 2012 Error (4) DCC-ACK not received;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 17:52:04 2012 Fri Aug 3 17:52:14 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:52:44 2012 Fri Aug 3 17:52:44 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Fri Aug 3 17:52:46 2012 Fri Aug 3 17:53:00 2012 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Fri Aug 3 17:53:11 2012 Fri Aug 3 17:53:12 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 17:53:27 2012 Fri Aug 3 17:53:27 2012 Warning (5) MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 18:17:03 2012 Fri Aug 3 18:17:07 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 18:17:07 2012 Fri Aug 3 18:17:07 2012 Error (4) DCC-ACK not received;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Fri Aug 3 18:17:08 2012 Fri Aug 3 18:17:18 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 18:17:48 2012 Fri Aug 3 18:17:48 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Fri Aug 3 18:17:49 2012 Fri Aug 3 18:18:05 2012 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Fri Aug 3 18:18:18 2012 Fri Aug 3 18:18:19 2012 Critical (3) No Ranging Response received - T3 time-out Fri Aug 3 18:18:27 2012 Fri Aug 3 18:18:27 2012 Warning (5) MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0; Sat Aug 4 00:56:12 2012 Sat Aug 4 00:56:12 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Sat Aug 4 00:56:39 2012 Sat Aug 4 00:56:39 2012 Critical (3) No Ranging Response received - T3 time-out Sat Aug 4 00:56:47 2012 Sun Aug 5 16:35:17 2012 Warning (5)

MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=c0:cb:38:a2:b3:84;CMTS-MAC=00:21:d8:d1:e7:67;CM-QOS=1.1;CM-VER=3.0;

 

 

Cable Expert
JayInAlg
Posts: 10,543
Registered: ‎03-02-2007

Re: I thought my BLAST Internet was going to double in speed?

[ Edited ]

A WRT54G will not do 50 down, it barely hits 12 on the ones I've seen.  Bypass that old clunky router, and see what you are getting.

 

Your upstream power is also slightly high, if you can cleanup your splitters to get a better signal to the modem you should work on that also.