Fluke Multimode OTDR for troubleshooting and extended certification – 2

Continue from: http://cs04fibercasa.blogspot.sg/2015/08/fluke-multimode-otdr-for.html

Fluke Multimode OTDR

Fluke Multimode OTDR Introduction:

	Multimode module	Singlemode module	Quad module
Wavelengths	850 nm +/- 10 nm 1300 nm +35/-15 nm	1310 nm +/- 25 nm 1550 nm +/- 30 nm	850 nm +/- 10 nm 1300 nm +35/-15 nm 1310 nm +/- 25 nm 1550 nm +/- 30 nm
Compatible fiber types	50/125 μm 62.5/125 μm	Singlemode	50/125 μm 62.5/125 μm Singlemode
Event dead zone 1	850 nm: 0.5 m (typical) 1300 nm: 0.7 m (typical)	1310 nm: 0.6 m (typical) 1550 nm: 0.6 m (typical)	850 nm: 0.5 m (typical) 1300 nm: 0.7 m (typical) 1310 nm: 0.6 m (typical) 1550 nm: 0.6 m (typical)
Attenuation dead zone 2	850 nm: 2.2 m (typical) 1300 nm: 4.5 m (typical)	1310 nm: 3.6 m (typical) 1550 nm: 3.7 m (typical)	850 nm: 2.2 m (typical) 1300 nm: 4.5 m (typical) 1310 nm: 3.6 m (typical) 1550 nm: 3.7 m (typical)
Dynamic range 3, 5, 6	850 nm: 28 dB (typical)1300 nm: 30 dB (typical)	1310 nm: 32 dB (typical)1550 nm: 30 dB (typical)	850 nm: 28 dB (typical) 1300 nm: 30 dB (typical) 1310 nm: 32 dB (typical) 1550 nm: 30 dB (typical)
Max distance range setting	40 km	130 km	MM: 40 km SM: 130 km
Distance measurement range 4, 5, 7, 8, 9, 10	850 nm: 9 km 1300 nm: 35 km	1310 nm: 80 km 1550 nm: 130 km	850 nm: 9 km 1300 nm: 35 km 1310 nm: 80 km 1550 nm: 130 km
Reflectance range 4, 5	850 nm: -14 dB to -57 dB (typical)1300 nm: -14 dB to -62 dB (typical)	1310 nm: -14 dB to -65 dB (typical) 1550 nm: -14 dB to -65 dB (typical)	850 nm: -14 dB to -57 dB (typical) 1300 nm: -14 dB to -62 dB (typical) 1310 nm: -14 dB to -65 dB (typical) 1550 nm: -14 dB to -65 dB (typical)
Sample resolution	3 cm to 400 cm	3 cm to 400 cm	3 cm to 400 cm
Pulse widths (nominal)	850 nm: 3, 5, 20, 40, 200 ns 1300 nm: 3, 5, 20, 40, 200, 1000 ns	3, 10, 30, 100, 300, 1000, 3000, 10000, 20000 ns	850 nm: 3, 5, 20, 40, 200 ns 1300 nm: 3, 5, 20, 40, 200, 1000 ns 1310/1550 nm: 3, 10, 30, 100, 300, 1000, 3000, 10000, 20000 ns
Test time (per wavelength)	Auto setting: 5 sec (typical)	Auto setting: 10 sec (typical)	Auto setting:MM – 5 sec (typical) SM – 10 sec (typical)
	Quick test setting: 2 sec (typical)	Quick test setting: 5 sec (typical)	Quick test setting: MM – 2 sec (typical) SM – 5 sec (typical)
	Best resolution setting: 2 to 180 sec	Best resolution setting: 5 to 180 sec	Best resolution setting: MM – 2 to 180 sec SM – 5 to 180 sec
	FaultMap setting: 2 sec (typical), 180 sec (max)	FaultMap setting: 10 sec (typical), 180 sec (max)	FaultMap setting: MM – 2 sec (typical) MM – 180 sec (max) SM – 10 sec (typical) SM – 180 sec (max)
	DataCenter OTDR setting: 1 sec (typical at 850 nm), 7 sec (max)	DataCenter OTDR setting: 20 sec (typical), 40 sec (max)	DataCenter OTDR setting: MM – 1 sec (typical at 850 nm) MM – 7 sec (max) SM – 20 sec (typical) SM – 40 sec (max)
	Manual setting: 3, 5, 10, 20, 40, 60, 90, 120, 180 sec	Manual setting: 3, 5, 10, 20, 40, 60, 90, 120, 180 sec	Manual setting: MM – 3, 5, 10, 20, 40, 60, 90, 120, 180 sec SM – 3, 5, 10, 20, 40, 60, 90, 120, 180 sec

FiberInspector probe specification
Magnification	~ 200X with OptiFiber Pro Display
Light source	Blue LED
Power source	TFS mainframe
Field of View (FOV)	Horizontal: 425 μmVertical: 320 μm
Minimum detectable particle size	0.5 μm
Dimensions	Approximately 6.75 in x 1.5 in (1175 mm x 35 mm) without adapter tip
Weight	200 g
Temperature range	Operating: 32°F to 122°F (0 °C to +50 °C) Storage: -4°F to +158°F (20°C to +70°C)
Certifications	CE (when used with the mainframe)
VFL specifications
On/Off control	Mechanical switch and a button on the touch screen
Output power	316 μw (-5 dBm) ≤ peak power ≤ 1.0 mw (0 dBm)
Operating wavelength	650 nm nominal
Spectral width (RMS)	±3 nm
Output modes	Continuous wave Pulsed mode (2 Hz to 3 Hz blink frequency)
Connector adapter	2.5 mm universal
Laser safety(classification)	Class II CDRH Complies to EN 60825-2
General specifications
Weight	Mainframe with module and battery: 3 lbs, 5 oz (1.28 kg)
Dimensions	Mainframe with module and battery: 2.625 in x 5.25 in x11.0 in ( 6.67 cm x 13.33 cm x 27.94 cm)
Battery	Lithium ion battery pack, 7.2 volts
Battery life	Four hours to charge from 10% capacity to 90% capacity with tester off
Environmental specifications
Operating temperature*	-18ºC to 45ºC
Non-operating temperature	-30ºC to 60ºC
Operating altitude	4,000 m (13,123 ft) 3,200 m (10,500 ft) with AC adapter
Storage altitude	12,000 m
EMC	EN 61326-1

View:www.fibercasa.com for more information

Fluke Multimode OTDR for troubleshooting and extended certification – 1

Fluke Multi-mode OTDR Introduction

Many OTDRs (Optical Time Domain Reflectometers) used for fiber troubleshooting are designed for carriers and contain cumbersome and complicated features that enterprise users don’t need. Few OTDRs are built with features and usability for enterprise network engineers, SAN designers and cable installers.

As enterprises consume more storage resources and adopt higher bandwidth (40G, 100G) data center architectures,

Fluke Multimode OTDR

the resilience of the cabling infrastructure becomes highly dependent upon maintenance tools to ensure fiber reliability. OptiFiber Pro is the industry’s first purpose-built OTDR that meets the unique challenges of an enterprise fiber infrastructure. With its simple smartphone user interface and powerful feature set, the OptiFiber Pro turns anyone into an efficient and expert premise fiber troubleshooter or installer.

This Multi-mode OTDR with 850nm & 1300nm wavelengths, eliminates errors that occur when testing fiber and features ultra-short dead zones.

Kit includes AC adapter, USB interface cable, user guide and CD, Link Ware software, 2-SC/LC & 1-SC/SC launch cables, fiber inspection probe, 2-launch fiber tool packs, 1.25 & 2.5mm One Click cleaners and carrying case & strap.

Fluke Multimode OTDR Features

Extremely short event and attenuation dead zone, The OptiFiber Pro leverages the most sophisticated optical technology to provide the shortest event dead zone (0.5 m typical for MM) and attenuation dead zone (2.2 m typical for MM and 3.6 m typical for SM) of any OTDR. This technological advancement allows OptiFiber Pro to detect and measure closely spaced faults where no other OTDR can in today’s connector-rich data center and storage area environments.

Two second trace per wavelength Another breakthrough with OptiFiber Pro is the data acquisition speed. While in Quick Test mode, a complete set of data is acquired in as little as two seconds per wavelength. OptiFiber Pro then analyzes the data and displays it as an EventMap event, Table or Trace. The end result is less time spent testing and more time performing other tasks.

DataCenter OTDR™ mode With a simple one-touch selection, users enter DataCenter OTDR mode – without setup time for fine tuning as needed in legacy OTDRs. DataCenter OTDR mode automatically detects OTDR parameters –end-detection algorithms, pulse widths, etc – without getting confused by the short links or number of connectors.

Graphical EventMap™ view To eliminate the learning curve associated with reading an OTDR trace, OptiFiber Pro’s advance logic automatically interprets the information to create a detailed and graphical map of events that includes connectors, splices and anomalies. To accommodate different preferences, users can easily switch between the EventMap, the Event Table and the Trace for test details. Any faulty events will be highlighted with RED icons to facilitate quick troubleshooting.

Dynamic project and user profile management OptiFiber Pro enhances job efficiency by allowing the workflow planner to create and manage operator and job profiles per project – defined jobs or sets of cable IDs can be assigned to specific operators. The progress and status of each project can also be easily monitored.

On-screen help – corrective action On-screen “help” suggests corrective action(s) for resolving fiber problems during each testing step. The “help” offered is context sensitive which allows users to quickly pinpoint possible resolutions. An easy-to-read, gray icon in the bottom, left-hand corner shows detailed corrective action recommendations.

FiberInspector™ probe OptiFiber Pro’s video inspection system examines patch cords and patch panel bulkheads to avoid the number one cause of fiber link failure – contamination. Significant time is saved because the probe is inserted directly into the patch panel’s bulkhead to examine installed fiber terminations without disassembling the patch panel. Technicians assign a pass or fail grade to the fiber, append a comment and save it for use in certification reports.

View: www.fibercasa.com or www.fiber-optic-fusion-splicer.com
for more information

FHO5000 OTDR FAQ for Grandway F2H OTDR

• What is the operating system for the FHO5000 OTDR?

       The operating system for the OTDR is Windows CE.

• How to do the calibration for the FHO5000 OTDR?
• What Modules can be added for the FHO5000 OTDR?

     The FHO5000 OTDR support optional power meter module, light source module, micro scope module, able to add touch screen feature, water proof features.

• How do I know which range to select on my OTDR?

   As for FHO5000 OTDR support Auto testing mode, so it is able to automatically scan the network and set the range setting. The selected range is at least bigger than the total length of the launch cable plus the cable length under test, plus the tail cord. For best result and trace display in the OTDR, the selected length is better about 150% of the total length (total length = launch cable length + cable under test length + tail cord length). 

• What Pulse width should use when testing the fiber?

      The key is to always use the shortest pulse width possible that will satisfy the trace quality and allow the user to see the end of the fiber. Short pulse widths are used for short fibers. Long PW's are used on long fibers. If the trace quality exhibits excessive noise that can't be removed by additional averages, select the next higher pulse width.

For FHO5000 OTDR, please refer to the table below:

PulseWidth-setting-for-FHO500 OTDR

• What Adapters included by FHO5000 OTDR

      The standard fiber adapter for FHO5000 OTDR is FC, but optional SC & ST. But for user who want test SC or LC by standard FC adapter, you are suggest to use FC/UPC - SC/UPC or FC/UPC - LC/UPC launch cable.

      As second solution is to use a bulkhead on the Fiber Under Test side that is hybrid, for example FC to SC.

• How to test a bare fiber

It is recommended to use a pigtail and mechanical splicer to test the bare fiber. Connect a pigtail of the correct fiber type and connector to the OTDR or far end of a launch cable. Cleave the opposite end of the pigtail and insert it into a mechanical splice. Cleave the end of your fiber to be tested and insert it into the opposite side of the mechanical splice. By using the "Real Time" function available on most OTDRs you can adjust the position of the fibers in the mechanical splice to get the best throughput. The cable is now ready to be scanned.

3 Ways to Use Mobile Marketing to Keep Customers Coming Back

Seventy percent of companies say it’s cheaper to retain an existing customer than to acquire a new one, according to a report. And they are right: acquiring a new customer can be five times more expensive, which is hopefully enough to convince you that customer retention should be on your radar at all times.

So how do I retain customers you might ask? The answer is simple: mobile marketing. Given that 60 percent of the time users spend online is through their mobile devices, establishing a solid mobile presence ensures that your customers always have a piece of your brand at the tip of their fingers.

Related: 5 Business Myths About the Mobile Industry

Here’s how it’s done:

The right place, the right time

Mobile devices draw tons of information from users. Some of this information, such as geolocation, can be instrumental in optimizing your brand’s mobile product specifically for consumers. Knowing where consumers are allows marketers to offer users content that’s relevant to the situation they’re currently experiencing.

The most obvious way to use this data would be to alert existing clients on new deals right when they are near your store or company branch; however, there are ways to get more creative.  

Airline KLM is a great example. The company created a mobile game that lets users fly a paper jet over a virtual version of the city of Amsterdam. Aside from being beautifully made and very enjoyable, the game also uses mobile data to promote user loyalty. With every purchase of a KLM flight users' win more points, but the even cooler thing is that users can advance in the game when they are at the airport gate waiting to board their KLM flight (using geo-location technologies).

Related: Rebranding? Don't Forget Your Mobile Strategy

Fresh content and exclusive deals

To ensure users don’t lose interest in your app, introduce new content as often as possible. Whether it’s cool music, text, visuals or attractive deals, these kinds of elements will ensure users keep coming back for more.

Now, you might be thinking at this point, that by introducing as much content as possible, you are spamming people. Wrong. If someone downloaded your app, it means that they’re interested in what you have to offer. The more great content you put out, the more satisfied your users will be. Even content that doesn’t necessarily directly relate to your product but fits with its general concept is fair game.

Let's look at the Starbucks app. The app features a variety of content (such as music) that doesn’t necessarily relate to the products Starbucks is most known for selling. Users who have the app get this content as an added value and check in with it regularly to see what’s new. It’s a great way to make sure that your brand stays on the consumer's radar.

Another way to promote user loyalty is by using the mobile app to keep consumers up to date on new products and deals. Being aware of deals before everyone else is good but not good enough. Instead, offer users deals that are only available through mobile purchases to incentivize app users to check in regularly.

A great example is that of an Israeli hotel chain called Fattal. The company managed to get not two but three birds with one mobile stone by launching an app for last-minute deals. First, the company used this clever move as a way of approaching new clients. Second, Fattal included special discounts for loyalty club members and third, they found a classic solution for their dead inventory.

Engage and interact

The best way to turn any consumer into a loyal one is to make them part of your brand. On mobile, this has become easier than ever, and user-generated content (UGC) is the name of the game.

Mobile apps introduce endless, easy and instant ways for users to participate in brand communities and contribute their own content. For instance, to promote its "What is Perfect Conference", TedXPortland launched a mobile app that overlaid the word "perfect" over user-generated pictures that were shared on social media. People immediately became curious about what those pictures meant, which in turn helped create buzz around the conference. The photos were later projected on the walls of the event as part of the decor.

Investing in retention on mobile is not only interesting and creative, it’s also essential. This is your opportunity -- and obligation -- to make sure that when customers go on their way, they take a piece of your brand with them.  

Related: What They Haven't Told You About Mobile-First Marketing

Cloud Carriers and Cloud Providers: Enemies, Friends or “Frenemies”?

Any given cloud user is dependent upon both the cloud provider running the data center that is hosting the application, and one (or more) network service providers or carriers used to reach the cloud. If the cloud is “down”, meaning the user can’t access the cloud application, whose fault is it? Who is responsible for fixing the problem and who does the user complain to? If we aren’t careful, problems can quickly turn into a finger-pointing exercise that makes no one happy.

One thought is to set up a clear contractual relationship between the carrier and provider. The cloud provider buys access to the users from the carrier. The carrier, in turn, provides a traditional service-level agreement (SLA) to the cloud provider covering availability, loss, latency and jitter measured from locations in close proximity to the user and the data center. This establishes a clear division of responsibility and clean, measurable criteria for determining whether the carrier is living up to the terms and conditions. However, it doesn’t fully solve the finger-pointing problem, because even if the data center and the servers are working fine, and the carrier connections to the data centers are running perfectly, users still may not be able to access the cloud.

Another possibility is to eliminate the distinction by having the cloud carrier buy a cloud provider, as Verizon bought Terremark, or the other way around, as Google bought their own fiber. This way, the cloud customer can buy cloud services from a single organization running both the data centers and the network. This reduces any finger pointing from the customer, but if the organization is internally siloed, the same old problems can persist. Besides, the number of cloud carriers in relation to the number of cloud providers is such that no single enterprise can be large enough to own everything, not even Google.

The way out of this mess is for cloud carriers and cloud providers to collaborate and move up the stack. They need to test the service as the users see it, rather than the circuits as the carriers provide them, and also test the virtual machines in the data center as the cloud provider manages them. If the service being stored is cloud storage, the storage should be tested. If the service is a platform for running websites, the websites should be tested. If the service is an application like email, the application must be tested. However, these tests should not be local tests from the data center; in order to test the service effectively, testing must be performed from locations as close as possible to users. These locations are buried deep within the carrier’s network, out-of-reach to cloud providers.

To make the collaborative effort work, new kinds of business relationships will probably need to be established between cloud carriers and cloud providers, i.e., relationships that are cooperative as opposed to the adversarial seller/buyer relationships governed by SLAs. For instance, relationships in which the carrier accepts responsibility for testing the service the cloud provider sells, and in which the carrier and provider share test results honestly and in real time. In such relationships, both organizations’ operations staffs would work together to solve problems.

So, how do we evolve to this collaborative model in which cloud carriers and providers work together? The obstacles are not technical, as effective solutions are already available from Fibercasa and others. The answer lies in cloud carriers and cloud providers getting together to establish a viable business model enabling them to cooperate effectively. Business partnerships are based on equal relations, in which the parties involved are neither friends nor enemies.

If you'd like to learn more about testing cloud services, you can read Testing the Cloud white paper. You can also watch the Network Forecast - Mostly Cloudy webinar that I've recently co-hosted with my colleague Bruno Giguère  about the cloud and its many benefits, including reduced capital and elimination of the time, space, power and cost constraints that plague the traditional computing environment.

RMB devaluation will help China or not ?

People's Bank of China (PBC) said that the improving US economy was one of the factors weighted in its decision to devalue the yuan.

"The US economy is recovering and markets are expecting at least one interest rate hike by the FOMC (Federal Open Market Committee of the Federal Reserve) this year", a PBC spokesperson said on the bank's website on Tuesday.

The PBC also said that strengthening dollar valuation is pushing down against the Euro and Yen.

China's large trade surplus has put the yuan's (RMB) real effective exchange rate in a relatively strong position, which is not entirely consistent with market expectation, the central bank said.

"Therefore, it is good time to improve quotation of the RMB central parity to make it more consistent with the needs of market development", the spokesperson added.

According to Amy Yuan Zhuang, a senior analyst at the Nordea financial services group, Beijing has previously steered clear of devaluing the yuan because it did not want to risk volatility in both the stock and currency markets.

"If the CNY trading band is to be widened, the aim would be to show progress on financial reform", she said.

Showing progress on financial reform, flexibility, and that Chinese markets can weather crises is critical to Beijing's aim of being included as a global currency reserve.

Earlier in the year, Chinese Premier Li Keqiang said:"China will speed up the basic convertibility of yuan on the capital account and provide more facility for domestic individual cross-border investment and foreign institutional investment in China's capital market."

The International Monetary Fund, which holds the key to the Chinese yuan becoming an international reserve currency through a review of its Special Drawing Rights (SDR) basket, visited Beijing this summer for technical discussions.

The 1.9 per cent downward move by the central bank was its biggest one-day change since 1993 -- and since China abandoned its tight currency peg for a managed float in 2005. It pushed the renminbi's "daily fix" to Rmb 6.2298 against the dollar, compared with a Rmb 6.1162 rate the day before. Before Tuesday, the biggest shift this year had been a 0.16 per cent adjustment.

The People's Bank of China said the move was a one-time adjustment to reflect changes in the way it calculates the daily fix -- the rate at which the central bank sets the currency every morning and from which the currency is allowed to move as much as 2 percentage points in either direction.

10,000 Hours the Link Between the Beatles and a Telecom Text Exper

10,000 Hours the Link Between the Beatles and a Telecom Text Expert

An increasingly critical part of our service to operator and managed service clients is consultation on test strategy, and helping to devise appropriate methods and procedures that drive on-time and under-budget project delivery. Time and again, the same key challenge arises: how to minimize OPEX spending. It's a critical question for most operators, given that the ratio in their published CAPEX/OPEX spending is 1:4 (this rises as high as 1:10 in the initial years of longer ROI business cases, such as FTTx). Addressing this challenge successfully in our domain of testing during the construction, activation and troubleshooting phases has a direct impact on key project metrics, including first time right (FTR), number of repeat visits/truck roll, lead to cash, and customer satisfaction levels resulting in increases average revenue per user (ARPU) and reduce churn.

In addressing our clients' need to address OPEX challenges, I usually steer the meeting slightly off-course by engaging in a discussion about The Beatles. This may seem completely irrelevant, but bear with me. My own experience in supporting many successful deployment and upgrade projects has led to the insight that a key success factor lies in developing the expertise of the telecom engineers that we are asking to deploy, commission and maintain our next-generation networks. In our field, the ability of devise appropriate test plans, methods and procedures is just one side of the equation: without a expert engineering force, these projects will be marked by setbacks, delays and budget overruns. The classic root cause discussion pertaining to such unsuccessful projects usually pinpoints this lack of expertise, confirming that engineers do not have enough training/knowledge to accomplish their tasks right the first time.

Like me, I'm sure you have met with many genuine and self-styled experts along the way. However, I wonder if you are curious as to what in fact really makes an expert an expert, and perhaps more importantly, how the formula can be mass produced and bottled to serve our own needs?

My own research led me to an outstanding story about high achieves in sports, music and industry. In his book Outliers: The Story of Success, author Malcolm Glad-well frequently refers to the "10,000-Hour Rule", stating quite simply that mere talent and training are not enough, and that the key to success in any field is dependent upon prolonged and deliberate practice of the art, skill or discipline in question within the right environment, and that these factors are what really differentiates the highest performers. To a large extent, this equates with practicing the said task for an estimated 10,000 hours (i.e. , 5 years of hard labor working 6 days a week, and 8 hours a day). Of the many examples in the book, the reference that I would like to draw your attention to is that involving The Beatles. When the band got its initial "break" and went mainstream, the four band members hadn't just met that same day and set about to writing and performing the hit songs that propelled their rise to fame. In actual fact, they spent year playing the circuits in UK, Holland and Germany, perfecting their art individually and together as a band. They logged their 10,000 hours in the clubs of Hamburg, developing the expertise that is both admired and envied in equal measure. On reflection, it makes perfect sense-expertise is born not only of talent and knowledge, but also of the deliberate application of these skill over time, leading to complete mastery of one's subject.

Back to next-generation telecom deployment. It is easy to see why so many projects run over time and budget. Training courses are great (but cost time and money); however, without the deliberate practice leading to "expertise", is it any wonder that there are so many issues with respect to training retention, or that so many unresolved issues lead to escalations and repeat truck rolls?

I would go so far as to say that the challenges remain the same, whether the company has ten engineers, or 1,000 to 10,000. The fact of the matter is that a lack of expertise in the field force hurts, and very badly. From a telecom contractor supporting cell-tower applications (moving from testing low-speed TDM services to 10G Ethernet services) to a large incumbent operator deploying FTTx (moving from their legacy xDSL residential network), the key challenge seen time and again is not in the field engineers, who are already "experts" in one area, but who suddenly find themselves faced with a need to rapidly absorb completely new technologies with a completely different set of standards, tools and methodologies.

Happily, that's where Fibercasa can provide relief and support, as we've placed our "10,000 hours" inside the box. Functionality and technical compliance are critical elements when selecting a test solution, but our secret sauce is that we deliver these solutions in such a way that engineers are able to quickly pick up and start utilizing them in an expert manner, and right the first time. There is no magic formula here enabling us to reduce learning and retention curves to zero. However, in partnership with many clients, we have developed and all of this expertise is readily available to be applied to your own projects today. For example, an engineer with 30 minutes of training can pick up an Fibercasa OTDR and, via the iOLM application, characterize an optical link in 20 seconds with the same level of accuracy that a 30 year veteran would be able achieve in 10 minutes with a traditional tool. That's the result of our 10,000 hours--right inside every iOLM, and ready to go, now.

I'd like to leave an open invitation to my colleagues to respond to this blog by sharing HOW they personally contribute to delivering 10,000 hours toward the development of solutions and applications such as iOLM (optical fiber), SmartR(VDSL), WMDi (DWDM and TravelHawk Pro (3G/LTE deployment). Meanwhile, when working with Fibercasa to address your OPEX challenge, feel free to ask us to show you how our 10,000 hours can be found inside the box. You will be surprised!

View: www.fibercasa.com or www.fiber-optic-fusion-splicer.com
for more information