Log-In to TLServer


When you execute any i-TRiLOGI command under the "Controller" menu for the first time, you will always be presented with the Username/Password dialog box as shown below:

fullmon1.gif (7163 bytes)

ID (Hex)

Since a TLServer can be connected to as many as 256 M-series/F-Series PLCs, each PLC must have a unique ID for identification. You will need to enter the matching PLC's ID here for successful communication with the PLC. The number entered should be in hexadecimal, hence the range of acceptable numbers is from 00 to FF.

If there is ONLY ONE PLC attached to TLServer and you are not sure of its ID, you can ask i-TRiLOGI to detect its ID by clicking on the "Detect ID" button.  This method however will not work if there are more than one PLC being connected to the TLServer since all connected PLCs will attempt to send their IDs simultaneously and therefore TLServer will receive garbled data.

Username & Password

You must have a username and password defined in TLServer and the same username/password pair must be correctly entered here for authentication.

TLServer's IP Address: Port

i-TRiLOGI Application vs Applet

If i-TRiLOGI is running as an "Application" on local PC, then you will be prompted to enter the HTTP Proxy Server IP Address and Port number  (e.g. 165.23.345.1:8080) . You can ask your network adminstrator for the proxy server's address or check it out from your Netscape or IE5's option menu.

However, if you run i-TRiLOGI as an applet using the browser, then you will not be prompted to entser the HTTP proxy's IP Address. This is because the i-TRiLOGI applet makes use of the browser itself to perform the HTTP tunnelling.  Due to Java Security model, Applet will not be able to connect to the client's network proxy server directly. It can only use the browser's built-in proxy settings to do the job. (The browser's built-in proxy settings must have been correct to access TLServer via proxy server, otherwise you would not have been able to run i-TRiLOGI as an applet from that TLServer in the first place!).

fullmon2.jpg (65239 bytes)