Streamyx Streamyx Guide

What is a fiber optic continuity tester?

Fiber continuity tester is also called fiber optic continuity checker. It is the simplest visual test of a fiber optic cable link.

To function properly, a fiber optic cable link must be "continuous", meaning no breakage, either within the fiber cable or in the fiber connectors, should exist. The simplest and least expensive way to check is to inject some visual light into one fiber end and check the light coming out from the other end.

To perform this task, two types of fiber testers are available: a fiber optic continuity tester or a laser visual fault locater.

Differences between a fiber continuity tester and a laser visual fault locator

The most important difference is their light source. A fiber continuity tester typically uses a red or green color high intensity LED while a laser visual fault locator uses red color semiconductor laser.

Visible lasers produce a more powerful light and can provide more information to the technician than a LED light. By coupling the fiber link to a visible laser, problems with connectors, breaks in the fiber near connectors or splices, and some bend radius violations can be located.

On the other hand, LED powered fiber continuity tester can only verify that light can travel through the fiber link and no more information is obtained. Fiber continuity tester simply yields a "no go" result. If the light isn't visible at the other end of the fiber link, then the fiber is unusable in its present state and requires further testing and repair.

Applications of a fiber continuity tester

Its best application is testing fiber on a reel before you pull it to make sure it hasn't been damaged during shipment. Look for visible signs of damage (like cracked or broken reels, kinks in the cable, etc.)

The other good application is to check fiber patch cables at patch panels. When connecting fiber cables at patch panels, use the fiber optic continuity tester to make sure each connection is the right two fibers!

And to make certain the proper fibers are connected to the transmitter and receiver, use the continuity tester in place of the transmitter and your eye instead of the receiver.

Understanding the features of a fiber continuity tester

1. Fiber mode compatibility

Some fiber continuity testers only support multimode fibers while the others support both single mode fibers and multimode fibers. So it's best to check the spec sheet from manufacturers to choose the type you need.

2. Fiber connectors supported

Most fiber continuity testers have adapters available for testing 2.5mm ferrule connectors such as ST, SC and FC, 1.25mm ferrule connectors such as LC, MU and special types such as SMA connectors.

3. Fiber distance

Most fiber continuity testers have enough light power to support 2km on multimode fibers.

Find even more detailed information about fiber optic continuity tester, fiber continuity tester, and fiber optic continuity on Fiber Optics For Sale Co web site.

Several years ago, we had thought about using Microsoft SQL Notification Services. At the time it seemed entirely too limiting from a feature standpoint and quite frankly we did not feel comfortable building a business plan around a 3rd party product which could ultimately make or break us as a company.

Validation was delivered recently when we discovered that Microsoft is gutting Notification Services from SQL Server 2008.

Therefore, when selecting a mass notification platform make sure your organization is NOT committed to a costly solution only to then discover the systems core engine is being discontinued by Microsoft.

This MS page: http://download.microsoft.com/download/4/5/3/453739ed-cb74-46b1-b7af-f157ee71db20/ReadmeSQL2008.htm

(which it appears has now been taken a few days ago)

Had said:

5.1 SQL Server Notification Services Removed from SQL Server 2008 Notification Services will not be included as a component of SQL Server 2008, but will continue to be supported as part of the SQL Server 2005 product support life-cycle. Moving forward, support for key notification scenarios will be incorporated into SQL Server Reporting Services. Existing Reporting Services functionality, such as data driven subscriptions, addresses some of the notification requirements. Features to support additional notification scenarios might be expected in future releases."

Right after the above page was taken down, a simple search at Google for "ReadmeSQL2008.htm" produced this new published article:

Version: 10.00.1300.13 Date Published: 2/22/2008

http://download.microsoft.com/download/4/5/3/453739ed-cb74-46b1-b7af-f157ee71db20/ReadmeSQLServer2008.htm

5.0 Features Removed from SQL Server

This section covers SQL Server 2005 features that are no longer included with SQL Server 2008.

5.1 SQL Server Notification Services Removed from SQL Server 2008

Notification Services is not a component of SQL Server 2008, but will continue to be supported as part of the SQL Server 2005 product support cycle. In future releases, support for key notification scenarios will be incorporated into Reporting Services.

.....Which essentially looks like a watered down version of the original article. Very ambiguous and the language shift seems to be an effort to prevent mutiny amongst NS developers. The MS community of developers just never took to NS, so what we have here is a whole new shooting match with reporting Services. No Thanks.

Mass Notification systems built on and around SQL Server Notification Services must now consider major re-writes of their alert engines. That's called "starting over" as the new engine must go through a proving process and gestation period that can take upwards of two or more years.

The best alert that your customers receive next might just be that your company is not based on SQL NS.

Desktop Alert http://blog.desktopalert.net/blogs/da_blog/archive/2008/02/16/25.aspx

Several years ago, we had thought about using Microsoft SQL Notification Services. At the time it seemed entirely too limiting from a feature standpoint and quite frankly we did not feel comfortable building a business plan around a 3rd party product which could ultimately make or break us as a company.

Validation was delivered recently when we discovered that Microsoft is gutting Notification Services from SQL Server 2008.

Therefore, when selecting a mass notification platform make sure your organization is NOT committed to a costly solution only to then discover the systems core engine is being discontinued by Microsoft.

This MS page: http://download.microsoft.com/download/4/5/3/453739ed-cb74-46b1-b7af-f157ee71db20/ReadmeSQL2008.htm

(which it appears has now been taken a few days ago)

Had said:

5.1 SQL Server Notification Services Removed from SQL Server 2008 Notification Services will not be included as a component of SQL Server 2008, but will continue to be supported as part of the SQL Server 2005 product support life-cycle. Moving forward, support for key notification scenarios will be incorporated into SQL Server Reporting Services. Existing Reporting Services functionality, such as data driven subscriptions, addresses some of the notification requirements. Features to support additional notification scenarios might be expected in future releases."

Right after the above page was taken down, a simple search at Google for "ReadmeSQL2008.htm" produced this new published article:

Version: 10.00.1300.13 Date Published: 2/22/2008

http://download.microsoft.com/download/4/5/3/453739ed-cb74-46b1-b7af-f157ee71db20/ReadmeSQLServer2008.htm

5.0 Features Removed from SQL Server

This section covers SQL Server 2005 features that are no longer included with SQL Server 2008.

5.1 SQL Server Notification Services Removed from SQL Server 2008

Notification Services is not a component of SQL Server 2008, but will continue to be supported as part of the SQL Server 2005 product support cycle. In future releases, support for key notification scenarios will be incorporated into Reporting Services.

.....Which essentially looks like a watered down version of the original article. Very ambiguous and the language shift seems to be an effort to prevent mutiny amongst NS developers. The MS community of developers just never took to NS, so what we have here is a whole new shooting match with reporting Services. No Thanks.

Mass Notification systems built on and around SQL Server Notification Services must now consider major re-writes of their alert engines. That's called "starting over" as the new engine must go through a proving process and gestation period that can take upwards of two or more years.

The best alert that your customers receive next might just be that your company is not based on SQL NS.

Desktop Alert http://blog.desktopalert.net/blogs/da_blog/archive/2008/02/16/25.aspx