You are on page 1of 12

OmniBER OTN communications performance analyzer

Virtual Instrument User Guide


Version 1.3 April 2005

Page 1

Introduction
The Virtual Instrument application allows complete control of the J723x series of analyzers over a remote link. This application replicates on a PC the instrument user interface allowing complete configuration and results to be obtained as if the user were in front of the instrument. To run the application you will need a PC running Windows 98 or Windows NT. The files are provided from the Agilent web site in a self-extracting archive. Installation instructions are given later. Communication with the instrument can be via LAN or alternatively via a dial-up modem. You will need connectivity for both the PC and test set in each of these cases. This mini-guide gives instruction on the install, setup and operation of Agilent Technologies' Virtual Instrument application. For the Virtual Instrument application files and further details on the J723x series of analyzers go to http://advanced.comms.agilent.com/otn/

Remote Control Defined


The J723x series of analyzers allows remote control in a number of ways. This document discusses remote control using the Virtual Instrument interface. This is the simplest way to gain complete control of the instrument without becoming involved in command-line programming. As an alternative, the instrument may be controlled by use of SCPI commands. This complete set of commands is used to build programs which perform automated routines. Universal Instrument Drivers are also supplied, which allows control from within a development environment such as HP-VEE. Remote control type Virtual Instrument SCPI UID Communication Interface LAN, RS-232 modem LAN, RS-232, GP-IB LAN, RS-232, GP-IB

Virtual Instrument Requirements


The Virtual Instrument is supported on Windows 98 & Windows NT environments. To ensure usability, a PC with a Pentium 2 processor or higher and 64Mb of memory should be used. To connect to the instrument you will also need to be able to communicate to the instrument over LAN or modem interfaces. For LAN connection either 10baseT or 100baseT is supported. For modem dial-up access, V34 compatibility is recommended. To support the Virtual Instrument application the Sun Microsystems PersonalJava Emulation Environment v3.1 is required on the target PC. This is available for free download from Sun's website. See Installation instructions for more details.

Page 2

Two remote and one local user can use the Virtual Instrument simultaneously, although at any one time only one user can be in control of the instrument. It is also possible for one user to run multiple Virtual Instrument windows to control multiple instruments in multiple locations.

Installation
Installation comprises of the following steps: 1. Download and unpack Virtual Instrument files 2. Download and install Sun PersonalJava Emulation Environment (if required) 3. Create a desktop shortcut (Windows 98 platforms only) To download the Virtual Instrument files go to http://advanced.comms.agilent.com/otn/ and register for online technical support. You will then be able to find the Virtual Instrument files under the Software >Latest Releases tab. Executing the Virtual Instrument package will unpack the files to the chosen folder. It is suggested that you accept the default location 'c:\' when appropriate. You should now have a folder on your hard disk called "J72xx".

Most users will need to install Sun Microsystems's PersonalJava Emulation Environment. To check whether this is already installed, use the Add/Remove Programs dialogue box in the Windows Control Panel. If another version is already installed, installing version 3.1 may create compatibility problems with other programs. Seek advice from your applications provider. Go to http://java.sun.com/products/personaljava/pj-emulation.html. Under "Download PersonalJava Windows x86/Win32" Emulation Environment v 3.1" select "Windows x86/Win32 and follow the instructions until you are able to download the executable package (approx 10Mb). Please install these files to the default location. Creating a Desktop Shortcut For Windows 98 platforms it is necessary to create a shortcut to the 'run_me.bat' application. Using Windows Explorer, go into the J72xx folder and find 'run_me.bat'. Right-click and choose 'Create shortcut' as shown below. You might like to place this shortcut on your Windows desktop and rename to 'Virtual Instrument'.

Page 3

Before using this shortcut, you must make changes to prevent "out of environment space" errors, which can occur in Windows 98. Find the shortcut you created above and right-click, choosing 'Properties'. Next choose the 'Memory' tab and in the 'Initial environment' box, type '32000' as above. Click 'OK' and now you are ready to begin using the application through this shortcut.

Page 4

Operation
Running the Virtual Instrument Instrument Find the Virtual Instrument files by navigating through Windows Explorer. By default, these will have been installed to C:\J72xx\. Find your shortcut to "run_me.bat" if you created one earlier [Windows 98 platforms require such a shortcut]. The original run_me.bat should remain in the J21xx folder. Double-clicking your shortcut will bring up the Virtual Instrument Launchpad screen as seen below. Here the user can create and save IP addresses of instruments in remote locations.

To create a new connection, click the new connection button. Clicking on the IP address window will allow you to edit the default IP address of '127.0.0.1' to that of the instrument of which you wish to control.

Should communication not be established with the target instrument, a time-out message will be displayed as below. Therefore, we suggest that you use the Windows PING command to prove connectivity before trying to connect. The PING command can be run from the Windows Start Menu, choose 'Run' then type:

Page 5

PING <IP address>. If a 'request timed out' message is returned the communication link with the instrument needs to be checked. Alternatively you will see PING timings being returned indicating that your PC can 'see' the instrument at the far end.

Although the Port number field can be changed, it should not be changed from '5002' for operation with the Virtual Instrument. The remote control settings on the instrument will refer to port number 5001 and should not be changed as it refers to the SCPI remote control interface. Establishing LAN Connection Before connecting to the remote instrument via the LAN, it is important that you know the target's IP address. Before leaving the instrument in its remote location, ensure that the instrument is connected to the LAN with an appropriate IP address. This can be checked on the Network Settings page in the instrument interface.

Power-cycle the instrument while connected to the LAN. If there are any conflicts in the IP address, then the instrument IP address will be reset to 000.000.000.000. Should this happen, contact your network administrator for a valid IP address. Please note that when entering IP addresses in the instrument that the leading zeros are required. However, this should be interpreted as a decimal address, not an octal address. Windows will interpret leading zeros differently so these should be dropped when using Windows commands such as PING. For example, if the IP address 10.225.0.40 was to be used, it should be entered into the instrument as 010.225.000.040 and used in Windows for example, as PING 10.225.0.40. Using the Virtual Instrument Launchpad, choose the IP address of the instrument you wish to remotely control and select 'Connect'. This will now bring up the replica user interface. Please note: if the Virtual Instrument Launchpad fails to appear, but can be seen in the Windows Taskbar you may need to right-click, minimise the Virtual Instrument and by right-clicking again, restore the window. This issue should be rectified in a future release of Sun's PersonalJava Emulation Environment.

Page 6

If the instrument should fail to connect with a "Connection Refused" message, it is likely that two remote users, the maximum number of remote user permitted, are already logged into the instrument. In this case, you will have to wait for one of the remote users to terminate their connection before gaining access and taking control.

Using the Virtual Instrument with a direct connection It is also possible to create a connection between a PC and the instrument by setting up a private network. To do this you will need a category 5 'crossover' LAN cable to make the connection. Ensure that connection is complete between the PC and the instrument by checking the LAN status LEDs (on the J723x the green LAN LED should be continuously green - on a PC the color may be different). For a private network you will need to change the controlling PC's network address. Suggested IP settings are below:
PC Network Settings IP Address Subnet Mask Default Gateway 192.168.0.1 255.255.255.0 192.168.0.254

Change the PC's network settings by right clicking the 'Network Neighborhood' icon and selecting properties. Following the appropriate selections as detailed in the Windows online help, change the network settings as detailed above (default gateway is not required on Windows 98 PCs) then reboot. Next configure the instrument with the settings below, and ensure connectivity by using the Windows PING command.
Instrument Network Settings IP Address Subnet Mask Default Gateway 192.168.0.2 255.255.255.0 0.0.0.0

Once the connection is complete you can start the Virtual Instrument application remembering to use 192.168.0.2 as the target IP address in the Launchpad window.

Page 7

Establishing Modem Connection If you wish to control the test set over a telephone line, you will need to use a Hayes compatible modem connected to the RS232 port on the instrument. The instrument should also be set to 'modem' on the remote control page. Once this is complete, the instrument's status line should now say 'Waiting for an incoming call'. Using Windows Dial-up Networking, create a new connection, giving a name and select the PC modem you intend to use as below:

Next type in the phone number to which the instrument is connected. Click 'Finish' and your new connection will be available in the 'Dial-up Networking' folder. Before connecting, right-click your connection and select properties, choose the 'server' tab and click 'TCP/IP Settings'. Now uncheck the "Use default gateway on remote network' box and click 'ok'.

Page 8

Connect to the instrument using your new connection. Ignore the prompt for a user name and password.

Now the Virtual Instrument application can be started. At the Launchpad window, use the IP address 192.168.1.1 to connect to the test set over the modem link.

Page 9

Using the Virtual Instrument Interface The Virtual Instrument interface operates for the most part, exactly like you would if in front of the instrument, with menu selections and navigation operating in the same way. Control of the user interface may be performed by using the p.c. keyboard only, or by using the p.c. mouse and clicking on fields and pull-down menus on the Virtual Instrument interface. If controlling the user interface by the PC keyboard - predominately with the arrow keys (), '+' for menu, 'enter' as select and 'escape' as cancel. The keyboard function keys are used to simulate the buttons on the front panel of the test set.

Real-time LED information

The keyboard function keys operate The green LED if lit, indicates that the instrument is in a test period. The red LED if lit, indicates historical alarm or error information

Logging into the instrument remotely will allow you to see the instrument settings, LED status, error and alarm counts, etc. However, if you try to change settings or change viewing tabs, you will be asked if you want to take control.

Page 10

Once control has been taken, you will be able to use any of the test set's functions. Taking control however, will mean that any local users or the alternative remote user will lose control since only one user can have control at any time. Nevertheless, when you log into the instrument you will be able to see if the gating LED is lit, indicating a test is in progress. The instrument interface will not 'mirror' that which is seen on the Virtual Instrument. Although cumulative results, Troublescan details and LED history can be seen by the three potential users of the instrument simultaneously, pointer graph & Signal Wizard results can only be seen by the user who started these applications. If the instrument is running Signal Wizard, other users will not be able to change settings until Signal Wizard is stopped. In this case, a warning message will be displayed informing the user Signal Wizard is running. Please note that the speed of response of the Virtual Instrument will depend on the quality of network connection. Exiting the Virtual Instrument The Virtual Instrument can be exited by clicking the close box at the top right-hand corner of the user interface window and by the same on the associated JAVA window.

Page 11

Troubleshooting and further support


Troubleshooting 'Bad command or filename' error when starting the application Ensure that the installation of the Sun PersonalJava was made into the default directory. Virtual Instrument fails to appear after choosing an IP address on the Launchpad window If the Virtual Instrument Launchpad fails to appear, but can be seen in the Windows Taskbar you may need to right-click, minimise the Virtual Instrument and by right-clicking again, restore the window. This issue should be rectified in a future release of Sun's PersonalJava Emulation Environment. Remote interface fails to respond If the remote interface no longer responds to keyboard commands, it is possible that communication with the instrument has terminated. Use the Windows PING command to establish if the instrument is still visible on the network. If so, restart the Virtual Instrument application. Connection refused message while connecting to the instrument This would imply that two remote users are already logged in and controlling the instrument. Access to the instrument will not be permitted until one of the remote users logs out. "Out of environment space" error This occurs when the create shortcut step is not followed. Please refer to 'Installation' on page 3.

Contacting Agilent Customer Support For Agilent Customer Support details, the latest software or Frequently Asked Questions, please go to the following web link: http://advanced.comms.agilent.com/otn/.

Page 12

You might also like