Hunter training - How to use i-Scout

+7

No comments posted yet

Comments

Slide 3

Additional information: the bar for CPD might show in the next scan a different probe – always pay attention also to the time delay of a particular CPD source and the probe ID to judge about stability of indication for CPD

Slide 6

Let’s use this different example Here probe 11 consistently indicates CPD We would therefore like to view a map showing where probe 11 is located

Slide 9

Note location of the installed probe 11 at TP0100 Note location of candidate devices, SP0013 & TP0104 Since this measurement is made from the headend, there could be some map distance errors To ensure that this is the correct device, it is recommended that you simply go to some device upstream of Tap 100 and use Quiver in CPD radar mode and take a measurement, then enter into Quiver Navigator

Slide 11

Hunter’s job is done Potential ingress sources are marked with a yellow triangle Simply go to the indicated areas with whatever signal leakage equipment you use and find the leak or use spectrum analyzer

Slide 1

Hunter Training Curriculum How to use i-Scout January 6, 2010

Slide 2

The very first step in using i-Scout will always be to first do some analysis using the Xcor Client To do this, click on the Day AVG cell for the desired node – for the following example we are going to use node KW15 To start, let’s assume that you have determined that a node needs to be repaired – and it turns out that the node has i-Scout probes installed

Slide 3

Information appears on the Day AVG CPD as well as results of all the i-Scout scans performed during the day. Always look at this before doing anything with i-Scout. Consistency of the source is absolutely critical for i-Scout to be used effectively. Here both the CPD and the Ingress sources are steady and constant throughout the day. Since it is consistent throughout all scans, this CPD is a great candidate to go find. As a matter of practice – always get the CPD source before looking for ingress. To find the CPD source, simply go to the most convenient connection point upstream of the installed probe location, and use Quiver.

Slide 4

..continued As a process our recommendation would be to go to probe 23 and find and fix the CPD source. Once that is done, we would suggest that additional i-scout scans be preformed to capture the remaining CPD sources in this node. It would seem that you could also go to probe 28 and find the ingress after the CPD has been mitigated, but that would not be our recommendation. Since there are no CNR problems on this node, there are no assurances that by fixing the ingress source anything would improve in the plant. Only go after non CNR affecting ingress, when CNR problems are gone on all other nodes. Probe 23 Probe 28

Slide 5

Introduction to two concepts, Intelligent monitoring and Predictive maintenance As pertains to ingress, the principle behind the approach that was just described is what we term “Intelligent Monitoring”. Intelligent monitoring is the description of our overall approach to alarming on impairments. We use the carrier to noise ratio (CNR) of return path channels as a criterion to determine if an impairment is worth chasing and to prioritize repair. Often impairments like ingress and impulse noise exist, but they do not affect return signal quality. In our opinion these are not worth fixing. We think it is more important to intelligently look at a problem to see if it is really a problem before expending resources to fix. This concept only holds true with ingress and impulse noise, as there is nothing to say that a source will get worse over time. If it is not network affecting today, there is no reasonable basis to expect that it will become network affecting tomorrow. The same is not true with CPD – results and experience have shown that CPD sources continue to deteriorate over time – they do not fix themselves. That is why we strongly feel that all CPD sources need to be mitigated. Small CPD impairments that exist today will only grow to become larger problems in the future – therefore use Hunter to find and fix these problems before they are network affecting - a term we call “Predictive Maintenance”.

Slide 6

…continuing the search – finding CPD downstream of a probe Probe 11

Slide 7

…cont. Select the upper right pull-down screen, and open any of the i-scout scan records – since the source was consistent it doesn’t matter which one you look at – they are all going to show the same location.

Slide 8

The signal archive record appears showing the i-Scout ID and where it is installed (A) The measured delay and level of the CPD source (B) And target devices (those devices downstream of the probe location within the specified time delay of 103.975µs) (C) Click on View map button to see where this is (D) …cont.

Slide 10

…to find the ingress source Focus on the bottom portion of the screen showing ingress Note that probe 4 is installed at Tap 009 Target devices downstream of probe 4 are listed – it is a list of all devices (but certainly the ingress source could be a cracked cable or a location that is not at a device (unlike CPD)) Again click on view map to see where probe 4 is located

Slide 12

… using Quiver Navigator with i-Scout for ingress Quiver Navigator can also be used to show the location of where a probe is installed. So taking the probe location identified as the source of ingress as measured at the headend - simply enter the i-Scout probe ID at step 6. (ignore steps 2-5) Step 6: i-Scout ID selection box, here probe 20 is picked

Slide 13

… using Quiver Navigator with i-Scout for CPD Steps 1-6 A green check mark next to the device indicates that it is downstream of the indicated probe

Slide 14

Final points

Tags: cpd ingress i-scout probes

More by this User
Most Viewed
Previous Page Next Page
This user hasn't uploaded any other presenations yet.
Previous Page Next Page