Advertisement
Guest User

Untitled

a guest
Dec 23rd, 2017
1,332
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.42 KB | None | 0 0
  1. HMI Embedded Network Manager for PCU20 Network Drives
  2. © Siemens AG, 2001. All rights reserved
  3.  
  4.  
  5. 1. General
  6. 2. Installation Info
  7. 3. Sharing a Folder with a PCU20
  8. 4. User Management
  9. 5. Troubleshooting
  10. 6. Miscellaneous
  11.  
  12.  
  13. 1. General
  14.  
  15. The HMI Embedded Network Manager represents the communication partner for PCU20
  16. network drives. This Manager must be configured and started on every computer
  17. which is to share folders and files with PCU20. The PCU20 communicate with the
  18. HMI Embedded Network Manager via TCP/IP sockets. The following ports must be
  19. available for this purpose:
  20.  
  21. - pcu20_ftp1 6743/tcp
  22. - pcu20_ftp2 6744/tcp
  23. - pcu20_ftp3 6745/tcp
  24. - pcu20_ftp4 6746/tcp
  25. - pcu20_ftp5 6747/tcp
  26. - pcu20_ftp6 6748/tcp
  27. - pcu20_ftp7 6749/tcp
  28. - pcu20_ftp8 6750/tcp
  29. - pcu20_ftp9 6751/tcp
  30. - pcu20_ftp10 6752/tcp
  31. - pcu20_ftp11 6753/tcp
  32. - pcu20_ftp12 6754/tcp
  33. - pcu20_ftp13 6755/tcp
  34. - pcu20_ftp14 6756/tcp
  35. - pcu20_ftp15 6757/tcp
  36. If necessary, these ports are entered in the "services" file every time the HMI
  37. Embedded Network Manager is started. If a port is already being used by another
  38. program, this program must be deinstalled to free the relevant port for use by
  39. the HMI Embedded Network Manager.
  40.  
  41.  
  42. 2. Installation Info
  43.  
  44. The installation of the HMI Embedded Network Manager is executed by means of the
  45. "setup.exe" setup program. The following can be specified within this installation
  46. program:
  47. - The installation location on the hard disk.
  48. - A folder within the program folder of the start menu.
  49. - Whether the HMI Embedded Network Manager is to be started automatically each
  50. time the operating system starts.
  51. - Whether the HMI Embedded Network Manager is to be started automatically after
  52. installation.
  53. The HMI Embedded Network Manager can be de-installed after a successful
  54. installation. This is done under "Start / Settings / System Control / Software"
  55. by selecting the HMI Embedded Network Manager and de-installing using the
  56. "Add / Remove..." button.
  57.  
  58. The HMI Embedded Network Manager has an HTML help and uses Microsoft's "HTML Help
  59. Viewer" to display this. The "HTML Help Viewer" requires at least Internet
  60. Explorer 4.0 or higher. If the "HTML Help Viewer" is not yet available on the
  61. server computer, it can be installed using the "hhupd.exe" setup file (this is
  62. located in the same directory which contains the setup file for the HMI Embedded
  63. Network Manager). Internet Explorer 4.0 or higher must have been installed
  64. beforehand (this is not on the CD-ROM).
  65.  
  66.  
  67. 3. Sharing a Folder with a PCU20
  68.  
  69. There are two possible ways of displaying a folder of the server computer on a
  70. PCU20. Firstly, a folder can be shared under Windows by the user who started
  71. the Network Manager. Secondly, a folder (also mapped) can be shared as an
  72. HMI-specific drive.
  73. If an operating system share and an HMI-specific share both have the same name
  74. on the server computer, the operating system share will be used first. This
  75. situation can occur only, however, if an operating system share is set up after
  76. the definition of an HMI-specific share as there is a check during the creation
  77. of an HMI-specific share whether an operating system share with the same name
  78. already exists, so that this can be rejected.
  79.  
  80. 3.1 Windows Shares
  81.  
  82. As access to an enabled drive is executed via the Network Manager and not via
  83. the PCU20, the PCU20 has the rights to operating system shares which the
  84. HMI Embedded Network Manager has on the server computer.
  85. If a folder of the server computer is to be displayed on a PCU20, this must
  86. be enabled under Windows for the user who started the HMI Embedded Network Manager.
  87. To do this, right click the folder in Windows Explorer and select "Share..."
  88. in the displayed context menu. Select "Share as" and enter the share name.
  89.  
  90. 3.2 HMI-Specific Shares
  91.  
  92. HMI-specific shares provide an additional method of displaying folders for a
  93. connected PCU20. This is mainly used to also obtain access to mapped folders
  94. of the server computer and thus allow the HMI Embedded Network Manager of the
  95. server computer to be used to access other computers of the network. This requires
  96. that the shared drive of the other computer is connected to the server computer.
  97. This connected drive can then be configured in the HMI Embedded Network Manager
  98. as an HMI-specific shared drive and therefore reached by a PCU20 which is
  99. connected to the server computer.
  100. HMI-specific share names can have up to 40 characters. Upper and lower case
  101. letters, numbers, underscore ("_") and hyphen ("-") are permitted. The share
  102. name must always begin with a letter.
  103.  
  104. 3.3 Access to Shared Folders
  105.  
  106. Now start the HMI Embedded Network Manager if this is not yet active. Do this
  107. by starting HMI Embedded Network Manager in "Start / Programs / <Name selected
  108. during the installation> / HMI Embedded Network Manager". The icon for the
  109. HMI Embedded Network Manager appears in the status area of the task bar. If
  110. the HMI Embedded Network Manager has already been set for the communication with
  111. connected PCU20 (see User Management), the shared folder can now be accessed.
  112.  
  113.  
  114. 4. User Management
  115.  
  116. A right-click on the icon for the HMI Embedded Network Manager and selecting the
  117. "User Management..." menu item or double-clicking the icon displays the user list.
  118. To allow secure communication, a user with the associated password must be
  119. entered on each PCU20. If this PCU20 is to have access to shared folders of the
  120. server computer, this user must also be entered with the associated password in
  121. the user list of the HMI Embedded Network Manager. To actually obtain access to
  122. the shared folders, each user must be assigned those shared drives to which he
  123. is to have access. This is executed in the "New ..." or "Edit ..." dialog boxes.
  124. This allows the precise assignment of the server computers and the folders of this
  125. server computer to be allocated to each PCU20.
  126. Each PCU 20 is supplied with a "PCU20_USER" standard user which the installation
  127. also enters in each HMI Embedded Network Manager. However, because the structure
  128. of the server computer is not known, no shared drive has been configured.
  129. Therefore, at least one shared drive must be assigned to the standard user in
  130. order that a PCU20 can access the server computer. However, this user should
  131. only be used for a simple point-to-point connection as, within a larger network,
  132. access can be made to the data of the server computer and no secure communication
  133. between the PCU20 and the server computer can be guaranteed.
  134. The "User management..." dialog box has the following buttons which open additional
  135. dialog boxes:
  136. - New... : A new user can be created.
  137. - Edit... : A selected existing user can be edited.
  138. - Delete... : A selected existing user can be deleted.
  139.  
  140. 5. Troubleshooting
  141.  
  142. Two options are available for fault finding. Firstly a message window can be
  143. opened, and, secondly, a protocol file can be activated which very precisely
  144. logs all the steps of the data exchange between the HMI Embedded Network
  145. Manager and a PCU20. The fault finding options are secured by the system or
  146. manufacturer's password.
  147.  
  148. -------------------------------------------------------------------------------
  149. Note:
  150. These fault finding options must not be active during normal operation as
  151. otherwise there are speed losses during communication between the HMI Embedded
  152. Network Manager and the connected PCU20. Apart from that, the log file would
  153. use up the entire hard disk.
  154. -------------------------------------------------------------------------------
  155.  
  156. 5.1. Message window
  157.  
  158. You can obtain status information about the current state of the HMI Embedded
  159. Network Manager by right-clicking on the HMI Embedded network manager icon, and
  160. then selecting the "Debug / Message window..." menu item. This dialog is used
  161. for fault finding if it is not possible to set up communication with a connected
  162. PCU20 or if problems occur during communication.
  163.  
  164. The dialog offers the following options:
  165. - The list box for displaying the status information can be deleted with the
  166. "Clear message list" button in order to improve clarity.
  167. - The contents of the list box can be stored in a file for later processing by
  168. using the "Save messages to file" button.
  169. - The maximum number of lines in the list box can be set to between 100 and
  170. 10,000. If the preset upper limit on the number of messages is reached, the
  171. contents of the list box are stored in file "_$TEMP$_.MWI", and the upper
  172. half of the messages just displayed is deleted from the list box.
  173. - The "Show message window during program start" selection box can be used to
  174. specify whether the message window should become active immediately during
  175. the start of the HMI Embedded Network Manager. However, this option should
  176. only be selected during active fault finding.
  177. - There is a filter option between two classes of status information. The
  178. "Show all available messages" selection displays all available messages in
  179. the list box. The "Show command messages" selection only displays the requests
  180. of the PCU20 to the HMI Embedded Network Manager, and hides all intermediate
  181. steps during the processing of the requests. In certain situations it may be
  182. necessary to restrict the amount of status information displayed in order to
  183. obtain better clarity.
  184.  
  185. 5.2. Log file
  186.  
  187. You can activate a log file ("nwmtrace.log") by right-clicking on the HMI Embedded
  188. Network Manager icon and then selecting the "Debug / Activate detailed trace file..."
  189. menu item. All message frames which are sent over the network are logged in this file.
  190. This information may be used to find possible faults in the network communication.
  191. This fault finding option is considerably more precisely subdivided than the
  192. message window, it should only ever be used when the possible fault cannot be
  193. found with the message window. The log file is stored in the installation
  194. directory of the HMI Embedded Network Manager. In order to activate the log file,
  195. the HMI Embedded Network Manager is automatically restarted. When doing so, it
  196. must be ensured that no PCU20 attempts to link to the HMI Embedded Network Manager
  197. during restart as this would fail and no communication would take place.
  198.  
  199.  
  200. 6. Miscellaneous
  201.  
  202. To display the version of the installed HMI Embedded Network Manager, click on
  203. the HMI Embedded Network Manager icon with the right mouse button and select menu
  204. option "About...".
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement