If you work on several project simultaneously and transfer them alternately to the HomeServer or FacilityServer, make sure you do the following:

As you use the same file names for different projects, the contents of these files may differ however, incorrect displays in the browser may result if the browser accesses the cache instead of the current page and attempts to display the page of the same name from a different project.

Microsoft dotNET Framework 2.0. is required for using HSAjaxFramework.

HSAjaxFramework can be found under tools\hsav.

All parameters that can be set are created in the definition file list.hs (XML format).
Use a text editor for this purpose.

Source code list.hs:

The program can also be started with a parameter transfer.

Example: HSAjaxFramework.exe Gira

Gira is the <key> described above.

If no parameter is transferred, a selection mask appears.


Fig. 2.1: Selection mask for parameter transfer

To be able to use the HomeServer AjaxVisu, the users in question have to be granted access under

Users / User rights / Interface / Client program

.

If the area of a standard visualisation page is to be limited, this is possible with the XXPAGE symbol. If this symbol is set on a visualisation page, it defines the bottom right-hand corner. All information which lies outside the limited area is not shown.


Fig. 2.3: Example for the setting of the page size

Create the symbol as described above:

Image ID: XXPAGE

Designation (name): "Ajax_Page_Size".

The symbol can be used as an option. If this symbol is not used, the browser shows the entire area of the visualisation page.

Using a small, square symbol is advisable. The top left-hand corner of the symbol defines the page size. The size and colour of the XXPAGE symbol are not significant, as it of course lies outside the defined display area.

The largest HTML mask included with the sample project is 331 pixels wide and 240 pixels high.

If you define the size of the visualisation area with the XXPAGE symbol to be smaller than the size of the HTML masks, the HTML masks cannot be completely shown.

The HomeServer AjaxVisu offers popup visualisation pages.

If a visualisation page is to be laid over the visualisation page to be called (popup), it is possible with the XXPOPUP symbol. If this symbol is set on a visualisation page, it defines the bottom right-hand corner and at the same time it defines this page as a popup. All information which lies outside the limited area is not shown. The page is laid centred over the existing page when it is called.


Fig. 2.4: Creating a symbol for a popup.
Left: Draft of popup page. Right: Called popup in the visualisation.

Create the symbol as described above:

Image ID: XXPOPUP

Designation (name): "Ajax_PopUp".

Using a small, square symbol is advisable. The top left-hand corner of the symbol defines the page size.

In addition, the popup page should be surrounded by a transparent frame so that the border around the popup is no longer visible.

A mask (e.g. message archive) can be called from a popup page. However, it is not possible to call another visualisation or popup page within a popup page.

Therefore, a navigation element must be defined on each popup page (e.g.: "Navigation: Back" or "Navigation: Starting point"). A draft of the later popup can be seen together with the small red XXPOPUP symbol, which limits the area to be shown, in the left-hand image (see Fig. 2.4). The result which can then be seen as a popup in the HomeServer AjaxVisu is shown on the right.

With a popup page it is possible, for example, to implement device-specific popups, e.g. a popup for blind control.

The project must always be completely (images+data+voice messages) transferred to the HomeServer or FacilityServer.

Code listing using the file startgast.htm as an example (see: Expert directory, under /hsupload/[visualisation path]/):

When using Variant A, the parameters must be placed in single quotation marks and specified separated from each other with commas. Line 41 in the code listing.

Here is an example of the call variant A with permanently entered parameters in line 41:

startClientEx('admin','Alpha.123','D1024V','R1',1);

If all information is correct, the HomeServer AjaxVisu starts with the specified visualisation page. Otherwise, the Login mask is called.

When using Variant B, a question mark (?) is appended to the file name, which is then followed by the individual parameters (with abbreviations), each separated by an ampersand (&).
Here is an example of call variant B with call parameters:

https://192.168.0.51/opt/[visu-path]/startgast.htm?pw=admin&user=admin&cl=D1024V&ref=R1

If all information is correct, the HomeServer AjaxVisu starts with the specified visualisation page. Otherwise, the Login mask is called.

When using Variant C, the startgast.htm file is used as described in the chapter Start files and no parameters are added onto the call.

The HomeServer AjaxVisu starts with the Login mask.

You can also combine the various variants. For example, if you permanently enter only the design and the refresh rate in the start file, you can include the user and/or password as call parameters.

You can also permanently enter all information as described in Variant A. If you then also include individual (or all) parameters as call parameters, the permanently entered parameters will be overwritten by the call parameters!

If you have specified all parameters in one way or another, the HomeServer AjaxVisu starts with the specified page. Otherwise the Login mask in which all known fields (except the password) are shown already filled out is called.

If, as described in Variant A, not all parameters are permanently entered, the entries from the login are saved and the next time the Login mask is called, the fields are automatically pre-filled again in with this information.

As with Variant A, the login data is saved unencrypted, we only recommend only using this variant for users who only have internal access authorisation. Otherwise, it is possible for someone to obtain access to this file and misuse the data.

In general, it is recommended that at least the password not be permanently entered in the start file so that it is not saved in unprotected areas, but is instead requested on each login and each reconnection.

For installers, it is advisable to use Variant B.

In the QuadConfig an entry is structured in the "Navigation button - URL" in such a way that a URL is stored there with call parameters (as described in Variant B). Therefore no critical data is entered in the start file, the user of the QuadClient can, however, nevertheless also log into the visualisation without an additional login procedure in this way.

If the connection to the HS/FS is terminated, e.g. due to restarting the HS/FS, a reddish coloured information window with the heading "HomeServer AjaxVisu" and a note that an attempt is being made to re-establish the interrupted connection are displayed. This attempt at reconnection is repeated at intervals that are determined by the refresh time.

A number of asterisks are shown in the information window, each of which stands for a reconnection attempt already carried out.

As soon as the connection has been restored, the information window disappears.

Then the user is on the page again that was active before the connection failed.

Exception: Popup pages. The user is on the page again from which the popup page was called.

Input field, in the example admin

User name for login to the HomeServer or Facility Server.
This user is assigned the start page in the visualisation.

Input field, in the example Alpha.123

Password for login to the HomeServer or Facility Server.

Input field (abbreviation), in the example D1024V

Indicates which design or which visualisation page is to be displayed. Otherwise, it has no further effect on the HomeServer AjaxVisu.

Input field (abbreviation), in the example R1

If a change is brought about with an element in the visualisation, for example a light is switched on, an automatic refresh of the page (the status of the object in question is determined and shown on the visualisation) is carried out at intervals that double each time.
This takes place until a period of time has passed which was entered under the refresh time in the HS/FS Expert.

Example:

5 minutes (= 300 seconds) are entered as a refresh time. Then an automatic refresh is carried out after 2, 4, 8, 16, 32, 64, 128 and 256 seconds.

Checkbox.

If this checkbox is activated, the user name and password, as well as all other settings are saved on the device as a cookie

Button.

By clicking on this button, the user logs into the HomeServer or FacilityServer with the information previously entered and starts the visualisation following a successful login procedure.

Internet Explorer in all versions lower than Version 7 does not support transparent graphics of the type "png".

These graphics are only displayed correctly from Internet Explorer Version 7.

Designation: ax0.gif

Transparent area, i.e. it has no colour and is therefore 100 percent transparent.

This file is used to be laid over all visualisation elements that are defined as clickable. It makes purely graphic elements into functioning buttons.

Designation: hide.png

Only partially transparent, red-coloured area, i.e. it is not completely transparent.

This file is used to be laid over a visualisation element for a short time after the user has clicked on it. This makes the click visible to the user. After one to two seconds the red area disappears again. However, this only occurs in the visualisation; the masks are excluded from this. See also Chapter Start files.

Designation: hide2.png

Only partially transparent, white-coloured area, i.e. it is not completely transparent.

This file is used, for example, to both display inactive buttons in the masks and to make them inactive for clicking.

Designation: hide3.png

Semi-transparent (grey) full-screen background, which is underlaid after a system mask (e.g. UT, value entry, etc.) is called. This avoids clicks on the background.

Designation: hide4.png

Semi-transparent (grey) full-screen background, which is underlaid after a visualisation popup page is called. This avoids clicks on the background.