String name that represents the system password.  This is currently used to logon via TELNET.  This is NOT the password for logging on to the web interface.

Array of parameters that controls remote network access to the system console for the main controller and each slave servo node via the TELNET protocol using TCP port 23.

    0 -  Disable access and immediately close any open TELNET connection.
    1 -  Allow connections but continue to send all system trace messages to the com1 serial console.
    2 -  Allow connection and send most system trace messages to the connected TELNET client.

Output from the Console.Write and Console.Writeline methods is sent to the TELNET connection if this parameter value is 2 and the executing thread was started from TELNET. See the Remarks section for Console.Write and Console.WriteLine for more details on console output.

If you change the parameter between the values of 1 and 2, you must disconnect and re-connect any TELNET client for this change to take effect.

To connect via TELNET, you must provide the "Network password" specified by DataID 410. Once connected, you can execute console commands and get feedback as though you were communicating with the controller locally via its com1 serial line. Only one TELNET connection to each controller is permitted at any time. The TELNET console connection operates independently of the serial line console so both can be active at the same time.

GSB and GIO slave nodes appear in the list of parameters, but always have a value 0 since they do not support a console

The IP address, subnet mask and gateway address of the local node, each in the form "nnn.nnn.nnn.nnn".  These values are immediately stored to NVRAM as soon as you set their new values.  They do not require a "Save to flash".  However, the controller must be rebooted for the new values to take effect.

The values of 421 and 422 are automatically adjusted to be consistent with the value of 420.  Inconsistent sets of values can sometimes lead to communication problems including the inability of Guidance Discovery to locate network nodes.

The IP address of the PC that is running the Precise vision server, in the form "nnn.nnn.nnn.nnn".  This value can be changed at any time and the new value will take effect the next time the vision server is connected.

(Servo Network) In order for the master controller in a servo network to simultaneously send information to multiple slave controllers, the master transmits messages using a "Multicast IP" address. This IP address is different from, and in addition to, the normal IP address.  You should assign a multicast IP address from the range reserved for private use by individual organizations:  from 239.192.0.0 through 239.195.255.255.  This parameter must be set in the master controller to specify its multicast IP address. This parameter does not have to be set in slave controllers since the master transmits this information when the network is initializing.

If this parameter is omitted or set to null, the value "239.192.0.1" is used by default.

As a special case when only 1 slave controller is needed. this value should be set to "0" which disables multicast messages. The master then uses normal UDP to send information to the node 2 IP address.

A string that contains an optional user name and password for remote access of the FTP server. The user name is the first field, optionally followed by a password field. The two fields are separated by one or more spaces.

If the string is empty, no login is required. If the user name field is specified, it must match the login name for FTP. If the password field is empty, no password is required for login. If the password field is specified, it must match the login password for FTP.

Returns an array of Ethernet statistical counters that assist in monitoring the performance of the Ethernet network. The values are defined as follows:

   1. Total number of packets received.
   2. Total number of packets transmitted.
   3. Number of bad packets received.
   4. Number of packet transmission problems.
   5. Number of TCP/IP connections initiated.
   6. Number of TCP/IP connections closed or dropped.
   7. Total number of TCP/IP packets sent.
   8. Total number of TCP/IP packets received.
   9. Number of TCP/IP data packets retransmitted.
  10. Number of times TCP/IP retransmit timeouts have occurred

11: Ethernet port 1 status bit mask

12: Ethernet port 2 status bit mask The port status is a bit mask indicating how the port is connected.

&H01 set if the port is connected, clear if not connected.

&H02 set if the connection is full duplex, clear if half duplex.

&H04 set if the connection is 100mbs, clear if 10mbs.

Note: TNG controllers only support 100mbs.

For more detailed information on send and receive errors, see "Ethernet receiver errors" (DataID 431) and "Ethernet transmitter errors" (DataID 432).

Returns up to 6 strings that contain details on Ethernet transmitter errors. Since the specific errors that can be detected are dependent upon the hardware and the Ethernet driver, the detailed detectable errors may vary over time. Therefore, the information is returned as formatted strings. Currently, the following errors are reported: abort errors, carrier errors, fifo errors, heart beat errors, and window errors.

Returns up to 6 strings that contain details on Ethernet transmitter errors. Since the specific errors that can be detected are dependent upon the hardware and the Ethernet driver, the detailed detectable errors may vary over time. Therefore, the information is returned as formatted strings. Currently, the following errors are reported: abort errors, carrier errors, fifo errors, heart beat errors, and window errors.

An array of two numeric values that determines the behavior of the special "real-time external trajectory generator" mode.

Array element 1 sets the mode of operation as follows:

     0: Disable the external trajectory generator.
     1: Enable version 1.2 of the protocol.
     2: Enable version 1.3 of the protocol.
   10: Enable version 2.1 of the protocol in debug mode.
   11: Enable version 2.1 of the protocol in standard mode.

If set to 0 when the interface is active, all communication stops and any robot motion is stopped as if a soft E-Stop had occurred. When set to non-zero, the external trajectory interface is active and able to communicate via Ethernet. When set to 0, the robot may be placed in jog mode locally, without error.

Array element 2 specifies which of the first 8 local digital output signals are controlled by the external trajectory messages.  This value is a bit mask: &H1 corresponds to digital output 1 and &H80 corresponds to digital output 8.  If a bit is 0, the external trajectory generator messages control this output signal.  If a bit is 1, the external trajectory generator ignores the output signal so that it may be controlled by a GPL program.  By default, this array element is set to 0 for backwards compatibility.

Determines the maximum time in seconds that can elapse with no trajectory data received. If this time is exceeded, the external trajectory interface shuts down and any robot motion is stopped as if a soft E-Stop had occurred.

Specifies the number of 125-microsecond ticks that should occur from when the digital sync output is set to when the interface expects data to be present. This number is used modulo the number of ticks per trajectory cycle.

A value that shows the internal state of the external trajectory interface. Values are TBD.

An array of statistics counters for the external trajectory interface communications. Cleared whenever "Ext trajectory enable" (DataID 440) is changed from FALSE to TRUE. The array elements are as follows:

   1. The number of status packets sent by the controller to the client.
   2. The number of valid command packets received by the controller, not counting any packets with checksum errors.
   3. The number of unexpected packets received.
   4. The number of expected packets missed.
   5. The number of packets received with a bad checksum.
   6. The number of communication task overruns.
   7. The number of setpoint packets missed.
   8. The timestamp of the last received packets.

Enables web interface logon password verification and enables and disables access to the system via the web interface.  The value of this parameter is interpreted as follows:

  -1: Password protection is not enabled.  Any number of simultaneous remote connections are permitted.
   0: No web connections are permitted.  The web interface is disabled.
   1: Password protection is enabled.  Only one PC may be connected to the controller via the web interface at any given time.  The logged on PC can have any number of browsers simultaneously connected to the controller.

Indicates the access level of the individual currently logged on to the web interface.  The access level governs the file directories that can be accessed via the web as well as the parameter database values that can be read or written.  The numerical access level is interpreted as follows:

   40: Administrator, can access all file directories and all Parameter Database values.
   30: Maintenance, can access all file directories and all Parameter Database values required to maintain and service the system.
   20: Operator, can access all file directories except for /ROMDISK/web/Sys.  This level provides access to the operator control and the jog panels.  This permits basic operation of a configured and taught system
   10: Application, can access all file directories except for /ROMDISK/web/Sys and /ROMDISK/web/Opr.  Only permits a custom web interfaced to be accessed.
    0: No one currently logged on.

Returns the IP address of the user who is currently logged onto the web interface.  All subsequent web accesses are tested to verify that the request are coming from the logged on PC.  If a different PC attempts to access the web (other than the login page) while another user's PC is logged on, the access will fail.

(Hidden parameters)  When a user attempts to log onto the web interface, the requested access level and passwords must be written into these parameters.  These parameters are hidden from the normal parameter Setup web pages since logins must be handled by the standard web login page.  Writing the password value triggers the access level and password validation process. See "Web logged on access level" DataID 451 for a list of the access levels.  For a given access level, the corresponding password as defined by DataID's 456-459 must be entered.  If the submitted access level is 0 and the password is "", the web interface will be logged off.

If "Web password security" (DataID 450) is enabled, but you wish to by-pass the standard login web page and directly access a custom web page, the following are the alternatives:

-  You can auto-start a GPL application program that replaces the standard login web page (/ROMDISK/web/index.asp") with your own custom page.
-   You can use a remote Telnet application to connect to the console port and set DataID's 453 and 454 to log into the web interface.  If you log in at level 10 or above, a browser running on the same host is permitted to directly access custom web pages in "/flash".
-   If you know the IP address of the host PC that will connect with the controller, you can auto-start a GPL application program that logs in the web interface by first setting the host IP address (using DataID 466), then setting the desired access level (using DataID 453), and finally setting the password (using DataID 454), which triggers the logon process.

True if a custom web is loaded into the flash disk as indicated by the presence of the file defined by the "Web application top-level page" (DataID 461).  This is used by the web interface to permit access to the custom web.  This value is updated when the system is restarted and each time a user logs off of the web interface.

These are the passwords that must be entered to log onto the web interface whenever "Web password security" DataID 450 is set to 1.  These passwords are compared to the value entered via the "Web logon password submit" DataID 454 parameter.  The specific password that is tested is dictated by the "Web logon access level submit" DataID 453.  The password comparison is performed taking into account the case of each letter.

The access permitted with each of these passwords is as follows:

   Administrator -- Has unlimited access to all web pages and Parameter Database values.
   Maintenance -- Has access to all web pages and Parameter Database values required to maintain and service the system.  This level is similar to the Administrator with the exception of some key values.
   Operator -- This permits basic operation of a configured and taught system.  Has access to the operator control and jog control panels together with any custom application web pages.
   Application -- Only permits access to any custom web pages.

If DataID 460 is True, the base page of the application web, as defined by the "Web application top-level page" (DataID 461), is loaded whenever the standard system base page, "/" or "/index", is requested.  This permits custom applications to be immediately displayed in place of the standard system login page.  If DataID 460 is False, this mapping is not performed.  By default, this parameter is set to False.

By default, the "Web application top-level page" (DataID 461) is set to "/flash/appweb/index.asp".  However, if you wish to store multiple applications on the flash, this parameter can be set to point to an arbitrary starting file and path for a custom web (subject to password security restrictions).

Contains a series of strings that specify the company name and key product names that are presented in the controller's built-in web interface.

If this parameter is set to the name of a file on the controller's flash disk that contains a company logo image, the Precise logo in the top-left corner of the operator interface web pages will be replaced with this alternate logo.  For example, if the logo is stored in a folder named "logo" in a file named "mylogo.png", this parameter should be set to the following value:

      "/flash/logo/mylogo.png"

For compatibility with the standard web pages, the logo should be 170 x 35 pixels and must be a PNG formatted file.  The controller must be rebooted for the new logo to be displayed.  You must also exit and restart your browser since the old logo may be cached.

An array of numeric values that controls the operation of RPC calls from web pages. The array elements are defined as follows:

   1. Debug mode. A bit mask that sets the RPC program debug mode.
     &H01 - If set, any error messages are sent in the RPC response string. Set to see if the RPC call causes an error.
     &H02 - If set, RPC threads do not send events to GDE regarding thread start/stop. Set to prevent RPC-based web pages from interfering with normal program debug
   2. Timeout. Set to the number of seconds to wait for the RPC call to complete. If 0, wait forever. A timeout generates a “Timeout stopping thread” (-752) error.
   3. Stack size. The size of the GPL stack to be used by the RPC thread. If zero, the default size for the project (normally 4Kbytes) is used.

Specifies how often dynamic web pages should be refreshed in seconds.  A value of 0 indicates that the web pages should be refreshed as fast as possible.  Normally, web pages are refreshed every 0.2 to 0.5 seconds.  The interpretation and implementation of this feature is left to the web page designer.