File Structure

The standard controller web pages are distributed as part of the operating system software.  This software is typically a binary "bin" file, e.g. "plmids.bin", that contains the operating system and the web pages in a compressed format.  When the system software is loaded into memory, the standard web pages are automatically expanded and stored in a memory based ROM disk, "/ROMDISK".  Files stored in the ROMDISK can be accessed like any other files only more quickly.

For a controller, the complete file system will typically contain the top-level folders and files that are briefly described in the following table.

/flash

- - - - - -

- - - - - - - - -

 - - -

R/W flash disk for general storage

 

/appweb 

- - - - - - - - -

 - - -

Default custom web page folder

 

/config

- - - - - - - - -

 - - -

PAC files for configuring the controller

 

/projects

- - - - - - - - -

 - - -

GPL executable projects

/GPL

- - - - - -

- - - - - - - - -

 - - -

 

/ROMDISK

- - - - - -

- - - - - - - - -

 - - -

R/O disk files loaded with OS

 

/bin

- - - - - - - - -

 - - -

Scratch area for OS upgrading

 

/config

- - - - - - - - -

 - - -

Default PAC files if PAC files are missing

 

/web

- - - - - - - - -

 - - -

Standard system web pages

 

 

/CopyToFlash

 - - -

Sample /appweb custom web files

 

 

/Images

 - - -

Misc button and image files

 

 

/login

 - - -

Login web pages

 

 

/NavBtn

 - - -

Tab navigation button image files

 

 

/Opr

 - - -

Operator Control and VMCP web pages

 

 

/sb

 - - -

Graphical icons for panel borders

 

 

/sb2

 - - -

Opr Cntrl and VMCP panel borders

 

 

/Sys

 - - -

Majority of system web pages

 

 

/Templates

 - - -

Primary page tab templates

 

 

/TvIcn

 - - -

Tree view icon images files

Typically, all of the files and folders for a custom web are stored on the flash disk in the /flash/appweb folder (although they can be placed elsewhere).  Your custom files can reference the standard web files stored in /ROMDISK/web subject to the password protection access limitations described below.

index.asp Files

When a controller is first referenced by a web browser by specifying only the controller's IP address, e.g. "http://192.168.0.1/", by convention, the browser is redirected to a root web file named "index.html" or "index.asp".  As shipped from the factory, when the web server intercepts a reference to a unspecified web page, "", or to "index.asp", it automatically redirects the web page access to the file stored as "/ROMDISK/web/index.asp".  This web file displays the standard system login screen.

Depending upon the login button pressed, the browser is directed to one of several web pages.  If the "Application" button is pressed, the next page displayed will be the root web file for the custom application web pages, "/flash/appweb/index.asp" by default.   When you design custom web pages, the starting point for your web will typically be the "index.asp" file stored in "/flash/appweb/" (although a different starting file and path can be specified).

To assist in getting you started /ROMDISK/web/CopyToFlash contains some demonstration application web pages.  If you access the ReadMe information provided on the login web page, you will be provided with instructions on how to install and execute this sample web.

Once you have installed the sample application web or you have created your own custom web pages, it is possible to skip the standard PreciseFlex™in page and go directly to your custom web page whenever the controller IP address is specified by itself or the "index.asp" file is specified.  The following describes the Parameter Database values that control this mapping function.

DataID Parameter Name Description

460

Web start application page

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).

461

Web application top-level page

Web Password Security

To restrict access to certain web pages, the system includes web page password protection.  When enabled, this provides four levels of access:  "Administrator", "Maintenance", "Operator", and "Web Application".  The access levels are implemented by restricting web page requests from accessing certain folders in the /ROMDISK and /flash and selected Parameter Database values. 

If password protection is enabled, only a single PC is allowed to connect to the controller via the web server at any given time.  The connected PC is still permitted to have multiple web browsers displaying multiple web pages.  If password protection is not enabled, multiple PC's can be connected to the same web server simultaneously.

The following table describes each of these access levels.

Access Level Description

Administrator

Can access all folders and files in the file system as well as all Parameter Database values.

Maintenance

Can access all folders and files in the file system as well as any Parameter Database values required to maintain and service the system.

Operator

Can access all folders and files in the file system except for /ROMDISK/web/Sys.   This means that the Operator Control Panel, the Virtual MCP as well as the Application Web stored on the /flash can be accessed.  However, pages such as the Setup tab to read and write Parameter Database values cannot be accessed.

Web Application

Can access all folders and files in the file system except for /ROMDISK/web/Sys and /ROMDISK/web/Opr.   In general, this means that only the custom web stored in /flash can be accessed.

As shipped from the factory, web page password protection is disabled.  To enable this protection and to define the required passwords, the following Parameter Database values must be set.

DataID Parameter Name Description

450

Web password security

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.

456

Web administrator password

These are the passwords that must be entered to log onto the web interface whenever "Web password security" DataID 450 is set to 1.  The password comparison is performed taking into account the case of each letter.

457

Web maintenance password

458

Web operator password

459

Web application password

Customizing The Company Logo

On each of the standard web pages, the Brooks company logo is displayed in the upper left corner of the web page.  If you wish to replace this logo with your own logo, you can do so by copying a PNG image to the flash disk and initializing the "Web custom logo file" (DataID 463) parameter.  Each time the controller is rebooted, it will replace the Brooks logo with the custom logo image.

DataID Parameter Name Description

463

Web custom logo file

If this parameter is set to the name of a file on the controller's flash disk that contains a company logo image, the Brooks 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.