📄 c-xfer3.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Data Upload </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-xfer.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-xfer.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-xfer2.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-xfer4.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="86835">8.3 Data Upload to the Host</a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="86836"> </a>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 <i class="title">VxWorks Programmer's Guide: Local File Systems</i>. 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 <a href="c-xfer3.html#87980">Figure 8-2</a>.) <div class="frame"><h4 class="EntityTitle"><a name="87980"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 8-2: Comparison of TSFS with TCP/IP Sockets and NFS </font></a></h4><dl class="margin"><div class="CellBody"><a name="88034"> </a><img class="figure" border="0" src="images/c-xfera2.gif"></div></dl></div></p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="86889">The Target Server Path</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="89821"> </a>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 <b class="command">-RW</b>. A typical target server command line, which is displayed in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Configure Target Servers</font></b> dialog box, is as follows:</p></dl><dl class="margin"><dd><pre class="Code"><b><a name="89822">tgtsvr.exe 150.50.50.50 -n t50-150 -c E:\wpwr\target\config\mv177\vxWorks -V -R C:\Products\WindView\eventLogs -RW</a></b></pre></dl><dl class="margin"><dd><p class="Body"><a name="89823"> </a>In this example, the root is <b class="file">C:\Products\WindView\eventLogs </b>and <b class="command">-RW</b> is specified. This means that event logs will be saved in the root directory, which will appear in the configuration screen as /tgtsvr. Specifying <b class="command">-RW</b> allows you to write event logs to the file. For more information, see the <i class="textVariable">VxWorks Programmer's Guide: Local File Systems</i>.</p></dl></dl><dl class="margin"><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="86916">Direct to Graph</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="86919"> </a>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 <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Direct to Graph</font></b> upload path option is preconfigured for ease-of-use. <div class="frame"><h4 class="EntityTitle"><a name="87008"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 8-3: Direct to Graph </font></a></h4><dl class="margin"><div class="CellBody"><a name="87010"> </a><img class="figure" border="0" src="images/c-xfer0.gif"></div></dl></div></p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="86744">TSFS to a File</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="86991"> </a>The only configuration steps required to use the target server path to a file are described in <a href="c-upload3.html#84936"><i class="title">File via TSFS</i></a>. 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. <div class="frame"><h4 class="EntityTitle"><a name="87021"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 8-4: Target Server Path Using TSFS to a File</font></a></h4><dl class="margin"><div class="CellBody"><a name="87025"> </a><img class="figure" border="0" src="images/c-xfer5.gif"></div></dl></div></p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="86994">TSFS Sockets</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="86995"> </a>The default <i class="textVariable">hostname</i> 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; <i class="textVariable">hostname</i> is resolved by the target server on the host. Each time you open a view graph using <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">New>WindView Log </font></b>on the main <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">File </font></b>menu, the port increments by 1; you must be sure that the port specified in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Control Properties</font></b> dialog box matches the port the view graph is using. The <b class="command">evtRecv</b> tool uses port 6164 by default; if you want <b class="command">evtRecv</b> to use a different port, you must change it both here and in the <b class="command">evtRecv</b> configuration (see <a href="c-xfer4.html#87462"><i class="title">8.4 The evtRecv Tool</i></a>). <div class="frame"><h4 class="EntityTitle"><a name="87030"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 8-5: Target Server Using a TSFS Socket </font></a></h4><dl class="margin"><div class="CellBody"><a name="87034"> </a><img class="figure" border="0" src="images/c-xfer6.gif"></div></dl></div> </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="86839">The Network Path </a></i></h4></font><dl class="margin"><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="86890">TCP/IP </a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="87798"> </a>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 <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">New>WindView Log </font></b>on the main <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">File</font></b> menu or by starting <b class="command">evtRecv</b>. <div class="frame"><h4 class="EntityTitle"><a name="88238"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 8-6: Network Path Using TCP/IP Sockets </font></a></h4><dl class="margin"><div class="CellBody"><a name="88248"> </a><img class="figure" border="0" src="images/c-xfera1.gif"></div></dl></div></p><dd><p class="Body"><a name="88229"> </a>The default <i class="textVariable">hostname</i> 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 <i class="textVariable">hostname </i>and it can only recognize hosts whose names have been added with <b class="routine"><i class="routine">routeAdd</i></b><b>( )</b>. </p><dd><p class="Body"><a name="87800"> </a>The <b class="command">evtRecv</b> tool uses the default <i class="term">event port number</i>, 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. </p><dd><p class="Body"><a name="87114"> </a><b class="task"></b>Also, be aware that TCP/IP sockets are managed by the VxWorks task <b class="task">tNetTask</b>. This task has a default priority of 50. If application-task priorities interfere with the scheduling of <b class="task">tNetTask</b>, you must raise its priority with <b class="routine"><i class="routine">taskPrioritySet</i></b><b>( )</b> in order to upload your WindView data. </p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="87159">Using NFS</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="86877"> </a>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 <i class="title">VxWorks Network Programmer's Guide: File Access Applications</i>. 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. <div class="frame"><h4 class="EntityTitle"><a name="87048"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 8-7: Network Path Using NFS </font></a></h4><dl class="margin"><div class="CellBody"><a name="87052"> </a><img class="figure" border="0" src="images/c-xfer7.gif"></div></dl></div></p><dd><p class="Body"><a name="87926"> </a>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. </p></dl></dl><a name="foot"><hr></a><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-xfer.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-xfer.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-xfer2.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-xfer4.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -