Forum Discussion
Have you heard back from them yet? If not, shining the Bat signal for becky
yes, truck is rolling out today
- WiderMouthOpen2 years agoEsteemed Contributor
Great to hear. Let us know how it goes.
- Nick4402 years agoNew Contributor
They tightened the line from the pole to the house, replaced the splitter on the outside of the house and checked the signal levels at the outlet where the modem is inside the house.
No more issues since they came out.
I did signup for complete care before they came out. Do you know if this would have been considered a billable tech visit, if not I am going to cancel complete care.
- WiderMouthOpen2 years agoEsteemed Contributor
Basically anything past the demarcation point(where the coaxial grounds) is considered customer wiring, so it may have been considered billable with that splitter. I think you have to keep it for 3 months for the call to be covered, which is cheaper then one visit, so I would keep it for atleast that long.
BTW, did you edit the post about the splitter? I thought before you said you had no splitters, not one. If I would have seen that I would have suggest replacing it before hand. Atleast now you now you have a "Cox official" splitter. I assume the splitter is for TV service? If so, any problems there?
Last, could you post your new signal levels? I am curious if replacing the splitter fixed your minor SNR issue.
- Nick4402 years agoNew Contributor
The splitter is inside the Cox enclosure on the side of the house. It was originally put there by Cox and they replaced it with an identical model. It is what has the ground wire attached to it.
One Coax wire from the box goes to the modem in the basement and the other goes to another outlet.
Would that splitter be considered past the DMARC?
Here are the current levels.
Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 21 801000000 Hz 9.2 dBmV 34.1 dB 47935 0 2 Locked QAM256 17 777000000 Hz 8.4 dBmV 34.2 dB 10919 0 3 Locked QAM256 18 783000000 Hz 8.7 dBmV 34.4 dB 15573 0 4 Locked QAM256 19 789000000 Hz 8.7 dBmV 34.3 dB 23762 0 5 Locked QAM256 20 795000000 Hz 8.9 dBmV 34.1 dB 32698 0 6 Locked QAM256 22 807000000 Hz 9.1 dBmV 34.1 dB 67080 0 7 Locked QAM256 23 813000000 Hz 9.3 dBmV 33.7 dB 94883 0 8 Locked QAM256 24 819000000 Hz 9.5 dBmV 34.1 dB 139057 0 9 Locked QAM256 25 825000000 Hz 9.8 dBmV 34.2 dB 178221 0 10 Locked QAM256 26 831000000 Hz 10.0 dBmV 33.9 dB 256249 0 11 Locked QAM256 27 837000000 Hz 10.1 dBmV 33.6 dB 345823 0 12 Locked QAM256 28 843000000 Hz 10.1 dBmV 33.7 dB 535569 0 13 Locked QAM256 29 849000000 Hz 10.2 dBmV 33.0 dB 708629 0 14 Locked QAM256 30 855000000 Hz 10.3 dBmV 33.6 dB 888750 0 15 Locked QAM256 31 861000000 Hz 10.2 dBmV 33.0 dB 1182203 0 16 Locked QAM256 32 867000000 Hz 10.3 dBmV 33.6 dB 1468069 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 17600000 Hz 42.0 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 24000000 Hz 42.0 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 30400000 Hz 43.5 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36800000 Hz 43.4 dBmV - WiderMouthOpen2 years agoEsteemed Contributor
Looks identical to me, but we can't see the upstream SNR, which would be causing the T3 errors. My guess is someone put the splitter in place because your signal levels are so strong and they replaced it as a troubleshooting step and the tightening the connection at the drop is what really fixed your problem.
Would that splitter be considered past the DMARC?
Yes.