Jump to content

mdob07

Honored Premier Sponsor
  • Content Count

    1,336
  • Joined

  • Last visited

  • Days Won

    10

mdob07 last won the day on March 24

mdob07 had the most liked content!

Community Reputation

981 Trusted

About mdob07

  • Rank
    Member Level: 4G WiMax
  • Birthday 03/01/1991

Profile Information

  • Phones/Devices
    Galaxy S9+
  • Gender
    Male
  • Location
    Shepherdsville KY
  • Here for...
    4G Information
  • Twitter Handle
    @mdob07

Recent Profile Visitors

8,263 profile views
  1. Love the nod to Abbott and Costello, those never get old.
  2. After almost 45 minutes of on hold, got in touch with a rep at Spectrum. Should have a tech out here in the morning to look at it. I got a picture of the gear at the pole, the line on the left with the loop is the one feeding my house.
  3. I''m hoping that fixes this issue. The cable from the pole feels really thin and brittle and has a perforation on it like it was a Siamese cable that was pulled apart.
  4. Heres a look at the logs this morning: Time Priority Description 2020-03-23, 23:13:03 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:13:03 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:08:17 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.0;CM-VER=3.0; 2020-03-23, 23:08:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2020-03-23, 23:07:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2020-03-23, 23:07:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:35 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:33 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:28 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:16 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; 2020-03-23, 23:07:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:04:84:40;CMTS-MAC=00:01:5c:76:c8:6c;CM-QOS=1.1;CM-VER=3.0; Time Not Established Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
  5. Just saw this; before I turned it off for the first time to switch to the cable I ran out my back door it was showing a high number of both correctables and uncorrectables on all of the channels. Still showing 0 for now though. We'll see what it looks like in the morning.
  6. Its a little further apart than the picture makes it look, I had to use scenery mode to get it all in frame and it gave it a wide angle lens effect. Decent night picture quality in low light for my S20 Ultra.
  7. Nice, mine will be easy as its all overhead. 50-60 ft run max accounting for the vertical drop on the side of my house.
  8. Yeah, I think I'll make that my next step. I pretty much eliminated everything in my house by connecting straight to the splitter outside. I couldn't find an adapter to connect two cables together or I would connected straight to their cable on the side of my house. When our house was build it was just a small regional Cable Co, that was then bought out by Insight, which merged with Time Warner, which merged to create Spectrum... I have no idea what kind of shape their infrastructure is in around here. Does anyone know if they typically charge to run a new line from the pole to my house? Or is that considered their responsibility? I don't know if they consider the demarc to be my splitter or the junction box on the pole.
  9. Oh, and I forgot to add once my modem is running for more than a day it usually drops to just one uplink channel. I have to power cycle to get bonded uplink channels back. When its using bonded uplink channels the light on the front is green, but turns to amber if in single channel mode.
  10. Modem is a Netgear CM600. Its only about 1.5 -2 years old as my old Arris modem didn't last very long. I do own the Modem. The cable run from the pole to the house is about 25-26 years old, so I may start by requesting a new line. It did feel very brittle when I was messing with it while changing out the splitter. I may order some ends from Amazon and try to re-terminate them myself. I reset the event log earlier when I was messing with everything and so far its still empty. I'll check again in the morning. Seems like everytime it goes out its the uplink that is failing. The downlink will connect but it will sit on uplink trying to establish and eventually reboot and start over. This has been going on for 5-6 months now but progressive seems to be getting worse in the last few weeks. Sometimes I can pull power and let it sit for a few minutes and then it will successfully connect, and sometimes it goes at least a day before I can get it to connect.
  11. I know this is a bit off topic but I figure someone on here might be able to help me. We've been having a lot of issues with our Spectrum internet for the past few weeks, and even before that it would intermittently go out maybe once a month or so but nothing like it is doing recently. I've been checking the signal levels on my Netgear modem and the downstream seems to be within spec, but the upstream power seems to be way off. On a speedtest from my wired desktop the pings are always high and speeds are not close to what they are supposed to be. Not sure if anyone here is experienced with cable modems and can offer any suggestions. I'd like to make sure the issue isn't on my end before calling Spectrum out to investigate. I have changed out the main splitter on the side of my house, as well as tested with a cable straight from the new and old splitter into my modem but neither seemed to make any difference to either speed or signal strength. I will be working from home for the foreseeable future and need my internet to work. Here is the signal info from my modem, anyone see anything that stands out to them? Startup Procedure Procedure Status Comment Acquire Downstream Channel 561000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Override MDD IPv6 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 17 561000000 Hz 3.2 dBmV 40.0 dB 0 0 2 Locked QAM256 1 459000000 Hz 1.7 dBmV 40.0 dB 0 0 3 Locked QAM256 2 465000000 Hz 1.8 dBmV 40.1 dB 0 0 4 Locked QAM256 3 471000000 Hz 2.2 dBmV 40.2 dB 0 0 5 Locked QAM256 4 477000000 Hz 2.6 dBmV 40.2 dB 0 0 6 Locked QAM256 5 483000000 Hz 2.3 dBmV 40.1 dB 0 0 7 Locked QAM256 6 489000000 Hz 1.6 dBmV 39.9 dB 0 0 8 Locked QAM256 7 495000000 Hz 1.3 dBmV 39.9 dB 0 0 9 Locked QAM256 8 507000000 Hz 2.2 dBmV 38.0 dB 0 0 10 Locked QAM256 9 513000000 Hz 2.2 dBmV 40.1 dB 0 0 11 Locked QAM256 10 519000000 Hz 2.4 dBmV 40.0 dB 0 0 12 Locked QAM256 12 531000000 Hz 3.0 dBmV 40.1 dB 0 0 13 Locked QAM256 13 537000000 Hz 3.0 dBmV 40.1 dB 0 0 14 Locked QAM256 14 543000000 Hz 2.9 dBmV 40.0 dB 0 0 15 Locked QAM256 15 549000000 Hz 3.0 dBmV 39.9 dB 0 0 16 Locked QAM256 16 555000000 Hz 3.2 dBmV 39.9 dB 0 0 17 Locked QAM256 21 585000000 Hz 3.8 dBmV 40.8 dB 0 0 18 Locked QAM256 22 591000000 Hz 4.0 dBmV 40.9 dB 0 0 19 Locked QAM256 23 597000000 Hz 4.0 dBmV 40.9 dB 0 0 20 Locked QAM256 24 603000000 Hz 4.2 dBmV 40.8 dB 0 0 21 Locked QAM256 25 609000000 Hz 4.3 dBmV 40.9 dB 0 0 22 Locked QAM256 26 615000000 Hz 4.5 dBmV 41.4 dB 0 0 23 Locked QAM256 27 621000000 Hz 4.6 dBmV 41.4 dB 0 0 24 Locked QAM256 31 645000000 Hz 5.0 dBmV 41.4 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 17 5120 Ksym/sec 17600000 Hz 51.0 dBmV 2 Locked ATDMA 18 5120 Ksym/sec 24000000 Hz 51.0 dBmV 3 Locked ATDMA 19 5120 Ksym/sec 30400000 Hz 51.0 dBmV 4 Locked ATDMA 20 5120 Ksym/sec 36800000 Hz 51.0 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Current System Time: Mon Mar 23 19:42:51 2020
  12. I've been having a weird GPS issue, but I think its software not hardware. When I plug my phone into my truck for Android Auto it will kill my GPS fix and will not re-establish until a reboot. If I've just rebooted my phone it won't kill it. It couldn't figure out why Waze and Google Maps were all over the place and why my mapping wasn't showing up in CellMapper. Hopefully this gets fixed in a future update. The only other complaint I've got so far is that it loves to stick to B12 LTE, which isn't an anchor band for N5. Its annoying when trying to hunt/map N5. Assuming it's something with this phone as my S9+ hardly saw B12 as primary carrier.
  13. I noticed my phone sitting on T-mobile this morning. Took a full reboot to get back on Sprint, airplane mode cycle wouldn't do it. Speeds seem to be limited to around 5mbps on T-Mobile for me since they first enabled roaming. Sent from my SM-G988U using Tapatalk
  14. I'm starting to see my 5G mapping show up on CellMapper. I'm still surprised by how little N5 is active in Louisville, especially considering how many sites should be capable based on B5 LTE added during the recent upgrades. I thought it was just a firmware update to switch from B5 to N5. Only a handful of sites even have the 5G indicator, and of those only a smaller group are actually broadcasting N5. The good part is that as long as the adjacent sites have been upgraded it will keep the N5 connection while connected to LTE from another site. Map of Louisville: I've seen the 5G indicator whenever a site has "Support" for the UPPERLAYER_IND_R15 field in the Service Mode screen. It will not show when connected to a non-anchor LTE band. For N5 its B2, B4(B66), and B30 as the anchor bands. N260 adds B12 as an anchor band. I'll have to do some more in depth testing to see how much N5 is contributing speed wise, the sites I've tested so far I don't really have any before data to compare to. My phone (S20 Ultra) doesn't seem to have any trouble initially connecting to and staying connected to N5, and it seems to want to hang on to a tower that supports it longer before handing off to the next tower at times. I have noticed NR PCIs high into the 900s, vs LTE PCIs that didn't go much higher than 500. MM-Wave testing SO far I've only found N260 on one site in Louisville. Looks like an Ericsson M-MIMO panel. I was wondering if it would be on all of the small cells they are throwing up everywhere but so far they're still only B2/B46 LTE. I wasn't able to test range much in the below example as its downtown around lots of buildings and bridges. Luckily there is a McDonald's right next to the tower, so that is where this testing is from. Disclosure: I was going for best case scenario for testing. I had the case off and was holding it out my window to get the best signal. But I did connect to it just fine in my truck with the windows up and case still on for the first test. The first round of tests were done at 6:30pm on March 13th. I had the opportunity to test this site again at 1:30am last Sunday morning from the same spot to see the difference from a high traffic time to a low traffic time: Ping was consistently around 14-15ms
×
×
  • Create New...