Menu
Reply
  • 3
  • 0
  • 0
pip20040
Joining in
44 Views
Message 1 of 1
Flag for a moderator

Constant drop outs and slow speed for a few days

 

Sorted, it was a loose Galvanic isolator.

 

 

I'm on Vivid 200 and not getting online most of yesterday and today, area 09 North Lanarkshire. What's going on? Self test says nothing wrong as does status page. Resetting S hub2 makes no difference.

Downstream   DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)299000000267000000275000000283000000291000000307000000315000000323000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID139101112141516
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)-0.560.070.11-0.38-0.57-0.74-1.01-1.16
RxMER (dB)30.2132.8730.8229.1929.1432.3231.9233.16
Pre RS Errors169187020380687294530879500763909581391381142685293420282912757755
Post RS Errors15550241037147363871715120315681394
27/03/2017 17:26:15 GMT27/03/2017 17:26:15 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
27/03/2017 17:25:40 GMT27/03/2017 17:25:40 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:25:25 GMT27/03/2017 17:25:25 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:25:19 GMT27/03/2017 17:25:19 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:25:18 GMT27/03/2017 17:25:18 GMTCritical (3)82000200No Ranging Response received - T3 time-out
27/03/2017 17:25:15 GMT27/03/2017 17:25:15 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
27/03/2017 17:25:13 GMT27/03/2017 17:25:13 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
27/03/2017 17:25:12 GMT27/03/2017 17:25:12 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
27/03/2017 17:25:09 GMT27/03/2017 17:25:09 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
27/03/2017 17:25:05 GMT27/03/2017 17:25:05 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
27/03/2017 17:25:02 GMT27/03/2017 17:25:02 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
27/03/2017 17:24:25 GMT27/03/2017 17:24:25 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:24:01 GMT27/03/2017 17:24:01 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:23:51 GMT27/03/2017 17:23:51 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
27/03/2017 17:23:49 GMT27/03/2017 17:23:49 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:23:42 GMT27/03/2017 17:23:42 GMTCritical (3)82000200No Ranging Response received - T3 time-out
27/03/2017 17:23:28 GMT27/03/2017 17:23:28 GMTCritical (3)82000200No Ranging Response received - T3 time-out
27/03/2017 17:23:24 GMT27/03/2017 17:23:24 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:23:11 GMT27/03/2017 17:23:11 GMTWarning (5)84020200Lost MDD Timeout
27/03/2017 17:23:05 GMT27/03/2017 17:23:05 GMTWarning (5)84020200Lost MDD Timeout
0 Kudos
Reply