LANTEK User Manual - Ideal Industries
Share Embed Flag
Download ePaper

LANTEK User Manual - Ideal Industries

LANTEK User Manual - Ideal Industries LANTEK User Manual - Ideal Industries

idealindustries.com
from idealindustries.com More from this publisher
22.12.2013 Views

Chapter 3 Structured Cable Field Calibration and Testing 3. When finished, press ESCAPE to return to the Autotest screen. Understanding Test Failures A failure result for Autotest indicates that one or more tests did not meet minimum cable parameter levels for the cable type selected. Note: Be sure that you have selected the correct cable type and are using appropriate connectors and links. Identifying which tests failed and the characteristics of the failure will determine the type of fault. If the Autotest shows a failure on a particular sub-test, perform Analyze testing for the failing test in order to troubleshoot the cable. When more than one test fails on Autotest, the test order used for troubleshooting is an important element in eliminating the source of the problem. If any tests fail, Analyze tests should be performed in the following order: 1. Wire Map 2. DC Resistance 3. Length 4. Delay and Skew 5. Impedance 6. Attenuation 7. NEXT 8. Dual Return Loss Refer to the Analyze Testing section to run these tests. WARNING SCREENS In response to a change in parameter(s), failure, harmful condition, or operational limitation, the tester will display a warning screen advising you of the activity or request you are engaged in. The screen will prompt you to YES (continue) or NO (exit). Figure 3-4: Sample Warning Screen 3-14

Chapter 3 Structured Cable Field Calibration and Testing USING JOBS TO STORE TEST RESULTS The LANTEK tester can store cable test results under separate Job names. You can create Jobs, assign any name to them, and store test results on a Job-by-Job basis. By using Jobs, you can logically group and store test results in a descriptive manner You can set up a separate Job for each floor in a building, each building on a campus, each customer, or for any other user-defined classification. To create a New Job: 1. Select Stored Results on the Ready screen. Press ENTER. At this point, you will see a list of all the jobs which are currently available. If you have never created a Job, the list will be empty. 2. To create a new Job select . The Job Options screen appears. 3. Press the ARROW keys to select New Job. Press ENTER. The New Job screen appears. 4. Type a name into the text field on the New Job screen using the alphanumeric keyboard. Press a key a second or third time to select the second or third character on the key. Press the RIGHT ARROW key or wait a few seconds to advance to the next character position. 5. After entering the name, press ENTER, returning to the Job Options screen where you can Access Job information, Delete Jobs, Rename Jobs, make a Job the current Job, or create more Jobs. The new active job name is displayed at the top left corner of the display. SAVING CURRENT AUTOTEST RESULTS The maximum individual Autotest results of 500 TIA CAT 6 with graphs or 30,000 plus without graphs can be stored in the LANTEK internal tester memory and accessed later using the Test Results menu. Autotest results can be saved immediately following the test. ‣ Only overall passed Autotests can be automatically saved. ‣ The entire set of test results is saved as one file. ‣ Test results are automatically saved if the AutoSave preference is enabled. Refer to Setting Preferences. ‣ Test names are automatically assigned to completed tests. If a different name is desired, a test can be named manually using the ‘Rename’ selection. To manually save Autotest results (AutoSave Disabled): 1. Press SAVE. The Test Saved screen will be displayed for a brief period, showing the name the test is saved under. 2. If the current name already exists, a warning screen appears asking you to overwrite the currently existing file or rename the results to another file or new file name. 3. Press NO to exit and return to the previous screen without performing a save operation. Press YES to overwrite the existing file. 4. Select to rename the current test. The Save Test screen will appear with a new name option. 5. Press ENTER to accept the change and return to the Test Results screen. 3-15

Chapter 3<br />

Structured Cable Field Calibration and Testing<br />

3. When finished, press ESCAPE to return to the Autotest screen.<br />

Understanding Test Failures<br />

A failure result for Autotest indicates that one or more tests did not meet minimum<br />

cable parameter levels for the cable type selected.<br />

Note: Be sure that you have selected the correct cable type and are using appropriate<br />

connectors and links.<br />

Identifying which tests failed and the characteristics of the failure will determine the<br />

type of fault. If the Autotest shows a failure on a particular sub-test, perform Analyze<br />

testing for the failing test in order to troubleshoot the cable.<br />

When more than one test fails on Autotest, the test order used for troubleshooting is<br />

an important element in eliminating the source of the problem.<br />

If any tests fail, Analyze tests should be performed in the following order:<br />

1. Wire Map<br />

2. DC Resistance<br />

3. Length<br />

4. Delay and Skew<br />

5. Impedance<br />

6. Attenuation<br />

7. NEXT<br />

8. Dual Return Loss<br />

Refer to the Analyze Testing section to run these tests.<br />

WARNING SCREENS<br />

In response to a change in parameter(s), failure, harmful condition, or operational<br />

limitation, the tester will display a warning screen advising you of the activity or<br />

request you are engaged in. The screen will prompt you to YES (continue) or NO<br />

(exit).<br />

Figure 3-4: Sample Warning Screen<br />

3-14

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!