Scribd
Upload
99 views

After Double Clicking On The k15 Protocol Tester Icon, Startup Window Opens Like

1. To start with Tectronics Protocol Analyzer, you need the protocol analyzer system, power cord, continuous power supply, and loop cord connector. 2. You create online monitoring and recording scenarios/pipelines and connect the analyzer to the E1 port using RX cables. 3. The logical link must be set up properly by selecting the board/port, protocol stack, and timeslot before saving the trace files. Monitor the live trace and ensure no errors.

Uploaded by

supriyasenapati
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
99 views

After Double Clicking On The k15 Protocol Tester Icon, Startup Window Opens Like

1. To start with Tectronics Protocol Analyzer, you need the protocol analyzer system, power cord, continuous power supply, and loop cord connector. 2. You create online monitoring and recording scenarios/pipelines and connect the analyzer to the E1 port using RX cables. 3. The logical link must be set up properly by selecting the board/port, protocol stack, and timeslot before saving the trace files. Monitor the live trace and ensure no errors.

Uploaded by

supriyasenapati
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

● How to start with Tectronics Protocol Analyzer?

# Tools Required.

1. Tectronics’ Protocol Analyzer system.


2. Power cord.
3. ( Continuous ) power supply.
4. Loop cord connector.

# Process.

1. Start the K15 protocol tester software installed in the system HDD.

After double clicking on the k15 protocol tester icon, startup window opens like:

Fig. 1
Please wait until the StatusWindow closes automatically.
Note: If any system configuration is already loaded, a small window opens like this:

Fig. 2
Please close the window without loading any preloaded configuration.
After closing, an untitled data flow window opens like this:

Fig. 3
Note: if no system configuration is already loaded, the dataflow window opens automatically.
2. Start with protocol testing scenarios.

In the untitled data flow window you may find some scenarios are already there, these are
actually the last used scenarios made by last user.

Fig. 4
Note: to view the data flow measurement scenarios, measurement scenario TAB under List of
scenarios subwindow must be selected [highlighted in red border in the above fig.]
To, delete any pre-existing [online // offline] scenario, just rightclick on Online [and//or offline]
scenario then select Remove all Online [and//or offline] Scenarios and confirm. By doing this,
the right hand side window [measurement scenarios] gets empty.
3. Creation of scenarios.

There are to categories in each scenario: a. monitoring.


b. recording.

To create a online monitoring pipeline : right click on Online Scenario then select Add Scenario
with Pipeline and then select Online monitoring.

Fig. 5
An online monitoring pipeline opens inside measurement scenario window.
User can change the name of the pipeline as per their own choice. For example, ABC is the user
defined name of the scenario for the following case.

Fig. 6
To create an online recording pipeline, rightclick on the online monitoring inside list of scenarios
subwindow then select Add Branch and then Online Recording. Find the below fig. :

Fig. 7
Online recording pipeline adjacent to online monitoring opens like this:

Fig. 8
This is all to create online monitoring and online recording adjacent to each other; attached for
a single scenario.

4. Connecting with E1 port.

Once Online scenario is created with recording and monitoring pipelines, it is important to
connect the protocol tester with the E1 on which user wants to collect [and // or view] traces.
There are 2 connector available on the top of the system for a protocol tester system. Each
connector supports 2 pair of cables. Each cable is marked as RX1, RX2, RX3 & RX4.
Note: RX1 & Rx2 and RX3 & RX4 is used for one E1 as a pair.
As an example take RX1 and RX2 cable for one Abis. User has to connect them accordingly in
the Rx and Tx port of the E1 in DDF.
There are 4 LEDs on the top of the System beside the connector port marked 1,2,3 & 4. These
4 LEDs are indicating the connection perfection and the signaling through the cable.
Note: Unless the parameters are set properly [i.e. logical link set up is done properly] on the
program, LEDs [1&2 in this case] will not be stable in green which is wanted.
5. Logical Link Setup.

To enter into the logical link setup window, click on the first block of Online Monitoring Pipeline
i.e. Î

After clicking, a Logical Link Setup window opens like this:

Fig. 9
To setup the logical link, follow the below instructions carefully:
FihF

Logical Link setup


Select Monitoring Pair
Select the Board as
DS1/E1 and the port on
this board to which the E1
link is connected
The most important step is
selecting the protocol stack. For
ISUP select the protocol stack
file wh97isup.stk located in
c:\K12XX\stacks\whibisup folder

Select the timeslot which is


carrying signaling

Click on Apply

After you click on Apply,


the configured logical
link is shown in this
window

Fig. 10
Following is the Protocol Stack Selection Window, where from protocol stack [as per need] can be
chosen.

Fig. 11
To make the search process easy, user can filter-out in each field in this window.
6. Save the Trace.
Once logical link setup is done properly, LEDs corresponding to used pair is blown in green and User is ready to start the
trace. But to store the trace, user has to click on the open tab in the last block [i.e. Recording file].

A window opens like this and user has to give the path where he/she wants to store the trace file:

Fig. 12
Now, user is again back to the main window. To start trace monitoring and recording user has to
click on the triggering block of both pipelines to make them ON with minimum gap of time [not
more than 1sec].

Traces are being stored now in the given path with given file name.
User can Monitor the live trace also, by clicking on the Monitor No.1 block of

Online Monitoring Pipeline.

7. Checks

User can visualize the online trace live. One thing should be noticed that the first block of
monitoring pipeline must be in green always and no alarm indication should not be there. If any
thing such found, user is recommended to stop the trace [both recording and monitoring],
check the physical connectivity of the wire, and after correction please redo the trace, from
point no. 6.
Under Short View Subwindow also, no. of error messages also as less as possible.
• User is highly recommended to keep a restless monitoring on the live Trace.

Fig. 13

You might also like