1. In general terms, how does the Hunter system work?
2. How is Hunter different from all the other test equipment out there?
3. What types of network impairments does the system locate?
4. Why is finding low-level CPD so important?
5. What types of devices have you found?
6. Do you find ingress?
7. What benefits have systems realized through using Hunter?
8. Is there is correlation between return path noise and CPD?
9. What are the different pieces of equipment required for the system?
10. How do all the pieces work together?
11. How many technicians does it take to operate the system?
12. How long does it take to find a problem?
13. What’s the difference between high-level CPD and low-level CPD?
14. Does Hunter find overloaded amplifiers and other non-CPD related impairments?
15. Can the software be configured to notify someone if there is a condition outside of a defined parameter?
16. What is the purpose of calibrating a node?
17. How often and how much of the network do I need to calibrate?
18. How does calibrating work?
19. Will the system work without having maps converted?
20. How important is map accuracy? What if my maps are way off?
21. What is the Xplor module?
22. What happens when maps are updated or a new plant is added, etc.?

In general terms, how does the Hunter system work?
Simply put, we use an operator’s existing QAM channels as radar signals. These signals provide the ability to find the time distance to certain types of impairments within an HFC network. We then query a database generated from electronic maps of the system. This database contains time distances to every device in the network. The database query outputs the number of devices that match the measured time distance within a certain tolerance. We then use field hardware and software to find the exact device that is the root cause of the network impairment.

How is Hunter different from all the other test equipment out there?
There is a lot of equipment on the market that will tell a cable operator that they have a problem on a node. Many manufacturers make gear that looks at various signal parameters and set alarms when the numbers go above thresholds. But often the operator already knows they have a problem – modems are not responding, customers are calling, etc. Unique to Hunter is the ability to tell the operator not only that they have a problem, but also WHERE they have problem.

What types of network impairments does the system locate?
The system operates by locating non-linear distortions such a CPD. But the CPD that we see is a little different than the CPD that operators have become used to seeing over the years. The CPD that is visible using traditional test equipment is, relatively speaking, very high level CPD. This is the recurring 6MHz pattern (NTSC) in the return frequency response that people have become used to seeing. We have the ability to see down up to -70dB to -80dB, well below the cable system noise floor. This allows us to see any and all CPD-related problems in the plant, whether they are currently system affecting or not. It also allows us to locate CPD after it has seemingly disappeared when using conventional equipment.

Why is finding low-level CPD so important?
The presence of CPD is an indicator that there is an impairment in the network. Some argue that there is no benefit in fixing low level CPD. But when you go out in the field and locate the device that is causing the low-level CPD and see how the device or connector is deficient – nobody will dispute the fact that the device or connector needs to be fixed or replaced.

What types of devices have you found?
We have found problems in every type of device installed in a network. We have located nodes without seizure screws, amplifiers with connectors that were hand tightened, rusted seizure screws, splitters where spiders had made a home, under water amplifiers, under water taps, faulty terminators, bad F-connectors, oxidized taps, oxidized splitters, bad splices, overdriven drop amplifiers, overdriven line extenders, bent stingers on pin connectors. In every system where Hunter is installed, we have located devices that were having problems, were network affecting, and that needed to be replaced.

Do you find ingress?
Time and time again, when we go into the network to find the root cause of a network impairment – that impairment is also a source of ingress. This makes sense when you think about it. Devices that are sources of CPD have a problem. There is some flaw in the connection interface of the device or there has been a breech in the moisture seal, allowing oxidation to take place. If there is a path where moisture can get into the unit, there is also an ingress path. Frequently when you find and fix a CPD source or sources with Hunter, there is a positive impact on the system noise floor performance.

What benefits have systems realized through using Hunter?
Every operator has their own unique problems and goals. So of course, benefits are realized in a variety of different ways. One system improved their node certification process from 2-3 nodes per month, to 8 to 10 per week. They went from being way behind on their telephony launch schedule to way ahead. Because of this, they were able to launch early, thereby exceeding their revenue projections. Another system decreased the number of line techs from 8 to 5 within a three-month period – and was able to redeploy those workers on revenue generating tasks. They fixed intermittent problems that had been ignored for years, drastically reducing the number of service calls and repeat calls. This particular network is performing at a much higher level – so well in fact that they were able to reduce their number of line techs. Overall, systems have seen improvements such as decreased service calls, fewer repeat calls, significantly improved noise floors, enhanced data and telephony performance, increased job satisfaction, improved network uptime, decreased operating costs, and significantly a more efficient technical staff.

Is there is correlation between return path noise and CPD?
Yes. Quite often, the root cause of the return path noise problem is also the same root cause of the CPD problem. That is why we highly recommend that if a node has a noise problem, to immediately fix all the CPD sources on that node. There is not necessarily a correlation between CPD severity and ingress. In many instances, Hunter has located relatively low-level CPD sources that turned out to be major ingress sources. This relationship between CPD and ingress is why we added the Xplor module to Hunter system.

What are the different pieces of equipment required for the system?
There are six major pieces of hardware and software required for the system. The headend radar and server, the return path switches, Quiver (hardware), Quiver Navigator (software), the Client (software) and the Xplor module.

How do all the pieces work together?
The headend radar/server, return path switches and the Client software work together to provide statistical information about what is happening in each node as pertains to the existence and magnitude of CPD and ingress. The Client is used to access the server from any IP address. Statistical information gathered and processed in the server is used as an input to determine which nodes host the CPD and Spectrum Statistics databases and perform the extensive processing of the signals in the search for. It also continually scans the network and processes the forward and return signals looking for sources of CPD. It then looks at the forward signals and compares simulated signal characteristics with actual return path signal.

How many technicians does it take to operate the system?
Just one. We’ve gone to great effort to make the system easy to use. Traditional CPD hunting techniques require multiple people: typically one technician pulling returns (physically disconnecting parts of the network – think of what happens to a phone call when this happens) and another looking at a spectrum analyzer to see if the problem goes away. It is an archaic process that also only finds very high level CPD.

How long does it take to find a problem?
Typically, a technician can find a problem in about an hour. An experienced and well-trained technician can take a little less – a new user could take a little more.

What’s the difference between high-level CPD and low-level CPD?
Generally speaking, when experienced cable system workers think about CPD, they think about high-level CPD. This is the CPD that can be viewed on a spectrum analyzer. If you can see high-level CPD, it is most likely already network-affecting and causing problems. When you hear someone say they don’t have a CPD problem, what they really mean to say is that they don’t see high-level CPD very often. They can’t say they don’t have a low-level CPD problem for the simple reason that without Hunter, they have no way to measure it. Low-level CPD is what we’re calling CPD that is below the noise floor of the system. All high-level CPD first starts out as low-level CPD. That’s why it makes sense to address low-level CPD before it becomes network-affecting. This concept is what we call Predictive Maintenance. Through Predictive Maintenance, problems can be found and fixed on a less frantic basis – and they can be found before they impact the network and customers.

Does Hunter find overloaded amplifiers and other non-CPD related impairments?
Yes. We have seen this many times in different ways. In one system, we saw a large number of house amps that had problems. They were easily overloaded and became network affecting. We located them and proved that they were a problem. In another system we found that all of a particular brand of nodes were set up incorrectly and were generating beats on the system. In yet another system we found that a particular brand of multitap had ferrites that were saturated, and that they generated significant beats from time to time. In many systems, incorrectly aligned and overloaded amplifiers have been found. Without our equipment these problems would have been very difficult to find. An overloaded amplifier is a nonlinear distortion because new additional carriers are generated. It is similar to CPD in that CPD is also a nonlinear distortion. That is why our system finds these types of impairments.

Can the software be configured to notify someone if there is a condition outside of a defined parameter?
We have e-mail alarm features that are built into the Hunter Platform. The alarm is easily configurable and customized to provide information as required.

What is the purpose of calibrating a node?
The purpose of calibrating a node is to speed up the scanning process by calculating the exact distance to the fiber node. Since CPD cannot occur within fiber, it does not make sense to the take time to scan this portion of the network. When you calibrate a node, the calibration information is automatically transferred to the device database. The information is used by the system, and the next time the network is scanned – the scan only takes place in the RF portion of the plant.

How often and how much of the network do I need to calibrate?
The nodes are the only devices that need to be calibrated. It is typically a one-time event unless some fiber distances have changed.

How does calibrating work?
In the calibration process, Quiver simulates a tiny non-network affecting source of CPD. To distinguish our calibration CPD from other CPD sources we alter the waveform in a particular fashion. In the continual scanning process, Hunter monitors each node for CPD. When Hunter detects CPD with this certain altered characteristic, it knows that this CPD had to come from a calibration signal – and it is recorded as such.

Will the system work without having maps converted?
No, electronic maps of the system are required in order for the system to work. Arcom Digital uses electronic maps in any form (AutoCAD, Focus, Microstation, Spatial, etc.), and from this creates a database used by the Hunter system.

How important is map accuracy? What if my maps are way off?
Map accuracy isn’t a big deal. What it comes down to is that if the maps are off it will take a little longer with Quiver and Quiver Navigator to track down the problem. Perhaps the technician will have to go to one or two more locations before finding the problem. If the maps are really good, then tracking will take less time, if not, it will take a little more time.

What is the Xplor module?
Xplor is an add-on module to the Hunter system. Its focus is on return path ingress. In this module, every time Hunter scans a node for CPD, it simultaneously scans for ingress. If the return spectrum performance exceeds certain user-established thresholds, the software will record and time-stamp a copy of a spectrum analysis shot of portions of the return path for that node. This feature is similar to some competing tools offered by various vendors. But what Hunter uniquely offers is a way to look at both Ingress and CPD conditions on a node simultaneously in order to help the operator make intelligent choices as to what node they need to have a technician look at first.

What happens when maps are updated or a new plant is added, etc.?
Arcom Digital has programs, processes and staff in place to quickly and efficiently convert updated maps; and load the maps and updated Hunter database onto the Hunter server located at the customer premises. Everything is done electronically, including remotely updating the server with the new database.