Data Upload

8.3 Data Upload to the Host

WindView 2.0 supports two separate paths for uploading data from the target to the host: a path through the target server, and a path directly to the host. The path through the target server is supported by TSFS and allows you to send your event data to either a file (any file the target can open) or a TSFS socket (usually the view graph). For more information on TSFS, see the VxWorks Programmer's Guide: Local File Systems. The path directly to the host is supported by the target network facilities. You can send your event data to any file the target can open, or to a target-native TCP/IP socket (if you have the optional WindView product installed). (See Figure 8-2.)

Figure 8-2: Comparison of TSFS with TCP/IP Sockets and NFS

The Target Server Path

In order to use TSFS to upload WindView data to either a file or the view graph, the target server must be started with TSFS enabled and set to -RW. A typical target server command line, which is displayed in the Configure Target Servers dialog box, is as follows:

tgtsvr.exe 150.50.50.50 -n t50-150 -c E:\wpwr\target\config\mv177\vxWorks  
    -V -R C:\Products\WindView\eventLogs -RW

In this example, the root is C:\Products\WindView\eventLogs and -RW is specified. This means that event logs will be saved in the root directory, which will appear in the configuration screen as /tgtsvr. Specifying -RW allows you to write event logs to the file. For more information, see the VxWorks Programmer's Guide: Local File Systems.

Direct to Graph

The target server path using TSFS is the easiest to configure and uses the fewest target resources. It provides the flexibility of sending your data directly to the view graph or to a file, and supports all the upload modes. The Direct to Graph upload path option is preconfigured for ease-of-use.

Figure 8-3: Direct to Graph

TSFS to a File

The only configuration steps required to use the target server path to a file are described in File via TSFS. The target server must have a TSFS root specified, which must be read/write. The root must be a path visible to the target server. If the machine running the target server is different from the one running WindView, you may make the root reference a mapped network drive.

Figure 8-4: Target Server Path Using TSFS to a File

TSFS Sockets

The default hostname for TSFS sockets is your WindView host and the default port is 6164. You can change the hostname or use the host IP number to send the event log to another host; hostname is resolved by the target server on the host. Each time you open a view graph using New>WindView Log on the main File menu, the port increments by 1; you must be sure that the port specified in the Control Properties dialog box matches the port the view graph is using. The evtRecv tool uses port 6164 by default; if you want evtRecv to use a different port, you must change it both here and in the evtRecv configuration (see 8.4 The evtRecv Tool).

Figure 8-5: Target Server Using a TSFS Socket

The Network Path

TCP/IP

One alternative to the target server path is provided by TCP/IP network sockets. To use this facility, you must have a host-target Ethernet connection, including all the networking modules on the target. You must also open a socket on the host capable of accepting the socket connection from the target. You can do this either by opening a view graph using New>WindView Log on the main File menu or by starting evtRecv.

Figure 8-6: Network Path Using TCP/IP Sockets

The default hostname is your WindView host and the default port is 6164. You can chose to use a different hostname or a host IP number to direct your data to a different host. Remember that the target must resolve hostname and it can only recognize hosts whose names have been added with routeAdd( ).

The evtRecv tool uses the default event port number, 6164. However, each time you open another new view graph, the port number it uses increments. Open your view graph and then replace the default in the configuration window with the actual port number shown at the top of the view graph.

Also, be aware that TCP/IP sockets are managed by the VxWorks task tNetTask. This task has a default priority of 50. If application-task priorities interfere with the scheduling of tNetTask, you must raise its priority with taskPrioritySet( ) in order to upload your WindView data.

Using NFS

This upload path sends your event data to any file your target can open. Usually you would have the Network File System installed on your target, as well as the TCP/IP network stack. For information about configuring NFS on your target, see the VxWorks Network Programmer's Guide: File Access Applications. You must mount a file system on the target and specify the appropriate path in the configuration window for the file you wish to access.

Figure 8-7: Network Path Using NFS

Another way to use this path would be to send your event data to a file on the target, for example, on a RAM disk. You could upload the file at a later time using NFS or FTP.