fieldgate data access software

8/14/2019 Fieldgate Data Access Software

1/44

BA273F/00/en/03.05Valid as of software versionV 2.00

Operating Instructions

Fieldgate Data AccessSoftware

Fieldgate

Fieldgate

Fieldgate

Fieldgate Data Access


2/44

Fieldgate Data Access

2 Endress+Hauser


3/44

Fieldgate Data Access Table of contents

Endress+Hauser 3

Table of contents

1 Introduction . . . . . . . . . . . . . . . . . . . . 4

1.1 Licensing agreement . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Security instructions . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Fieldgate Data Access . . . . . . . . . . . . . . . . . . . . . . . 6

2 Operation . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 List view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5 Context menus . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.6 Status line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.7 Program settings . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.8 Add scheduler entry, setting details . . . . . . . . . . . . 20

3 Further Information . . . . . . . . . . . . . . 28

3.1 CSV-Daten . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2 History database . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3 OPC-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4 FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5 OPC-FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.6 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.7 Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.8 Command Line Parameters . . . . . . . . . . . . . . . . . . 393.9 System Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.10 Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . 403.11 Known Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 413.12 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


4/44

Introduction Fieldgate Data Access

4 Endress+Hauser

1 Introduction

1.1 Licensing agreement

Fieldgate Data Access Tool was developed by Endress+Hauser GmbH + Co. (hereinafter known as"Endress+Hauser"), Maulburg.All rights to this software and to the technical documentation and materials which accompany it arethe exclusive property of Endress+Hauser. Neither the software nor the associated documentation(written or on a data carrier) may be duplicated or reproduced in any form, in whole or in part,

without the express written permission of Endress+Hauser.

The use of the software is subject to the following terms:

The software and associated documentation are subject to revision or update without priornotification from Endress+Hauser. In the event of a revision or update, the end user has no right toautomatic or free-of-charge supply of the revised or updated software nor of the associateddocumentation. It is at the discretion of Endress+Hauser whether a revision or update is or will be

made.The terms of this agreement, however, apply in content and extent to the case of the supply of arevised or updated version of the software or the associated documentation.Every effort has been made to produce a bug-free and stable program and associated documentation.Its online documentation contains an installation and operating manual as Help files. The onlineoperating manual applies only to the version stated on this CD (for installation). Endress+Hauseraccept no responsibility for damage resulting from the use of the software or associateddocumentation except in the case of wilful negligence, which then must be proved. Similarly, noguarantee is given that it will run on a particular hardware platform or with other software. All otherliability is excluded.Endress+Hauser will legally pursue and prosecute any infringement of any of the clauses definedabove in this licence agreement or of respective legislative rules.

This information relates to the software (supplementary components) which is also on

this CD.

All software that can be loaded from this CD (software) is protected by copyright.Use of this software is subject to the conditions of the Licence Agreement (if available)with the enduser, which is supplied with the software or is contained within it (LicenceAgreement).End users are only entitled to install software to which there is a Licence Agreement and to whichthey have previously agreed to its conditions stated in this Licence Agreement.

Only end users within the meaning of the Licence Agreement are entitled to load anduse thesoftware.

Any duplication or distribution of the software outside the conditions stated in theLicenceAgreement is strictly forbidden by law and is subject to civil and criminalpenalties.All infringements will be pursued to the fullest possible extent.

Registered trademarks

All proprietary and product names are trademarks or registered trademarks ofcompanies andorganisations.


5/44

Fieldgate Data Access Introduction

Endress+Hauser 5

1.2 System requirements

The following prerequisites are minimum requirements: Operating system: Windows 98 / NT (SP6a) / 2000 / XP If dial-in connections (modem) are to be used:

Windows 98: DUN 1.3

Windows NT: RAS it must be observed that SP6a must in any case be played again after anRAS installation

Windows 2000 / XP: RAS usually already installed MDAC 2.5 SP3 must be installed (applies especially to Windows NT4) Internet Explorer min 5.x, better still Internet Explorer 6.0 SP1

Required updates can be downloaded from "http://www.microsoft.com".If Fieldgate Data Access has to establish a direct Internet connection, we recommend you updatethe computer via "http://windowsupdate.microsoft.com/" (only works with InternetExplorer)!

1.3 Security instructions

Please note that passwords are in plain text in the configuration database and in the fieldgateda.inifile. This means that the computer on which Fieldgate Data Access is running must be securedaccordingly! Access, at least, to the computer should only be permitted to trustworthy people.

In addition, a computer directly accessing the Internet - this is the case if Fieldgate Data Accessretrieves measured value mails from a POP3 server on the Internet - should be kept up to date asper "http://windowsupdate.microsoft.com/" and, optimally, provided with additional security witha firewall.

The OPC server has an error which prevents access rights from being set especially for the serverobject. Instead, access rights must be configured via the Default Security. This problem will besolved in a future version.


6/44

Introduction Fieldgate Data Access

6 Endress+Hauser

1.4 Fieldgate Data Access

With Fieldgate Data Access, data are retrieved from Fieldgates with periodic time control. Inaddition, data (e-mails) sent by the Fieldgate can be retrieved by POP3 or IMAP4 servers. Fieldgatescan also send measured value mails directly to Fieldgate Data Access.Fetching the data is controlled via scheduler entries. The time can be controlled periodically or at

user-defined times.Under Windows NT4 / 2000 / XP, the data can be collected by a "System Service", which isprocessed in the background ( Page 3).Changes in Fieldgate Data Access over previous versions are documented in the "History"( Page 6).

1.4.1 Data sources

The following can be used as data sources: Access via http. In principle, this is access using a web browser. Access via a proxy server and

via modem dial-in (RAS) are available as options. Access to e-mails (measured value e-mails) sent by Fieldgate via POP3 and IMAP4 mailbox. As

an option, access to the server can also be performed via modem dial-in (RAS). Sending measured value mails directly to Fieldgate Data Access via SMTP.

1.4.2 Data presentation

The data received are: Saved as "CSV files"; national settings for column separation and floating point display are taken

into consideration, Saved in a "history database", Made available via "OPC".

1.4.3 Alarm signalling

Fieldgate Data Access generates alarm e-mails, if scheduler entries cannot be processed. Alarme-mails from connected Fieldgates can also be forwarded.

1.4.4 Miscellaneous

Virtually any number of scheduler entries can be generated. Access to the Fieldgates is carried out in parallel (multi-threading). A modem connection is used for the modem dial-in.


7/44

Fieldgate Data Access Operation

Endress+Hauser 7

2 Operation

2.1 User interface

When first starting the program (the overview is empty except for "Add Entry", it is recommendedthat you enter the first program settings via "Preferences". This affects, above all, the settings forthe "Data Root Directory"; his is where the collected data is stored.

In the next step "Entries are added". These entries then appear in the overview. After a while, thiscould look something like this:

See also "Symbols".

The usual Windows operating elements are used: Menu bar Toolbar List view Context menus Status line


8/44

Operation Fieldgate Data Access

8 Endress+Hauser

2.2 Menu bar

2.2.1 File

Activate & Run

Activate selected entry and set next run time to current clock time Entry is executed.

Activate

Activate selected entry.

XML Data

Display XML data of the selected entry.

CSV Folder

Open the folder with the CSV data of the entry in Explorer.

Delete Connection Document(s)

Delete selected entries.

Delete Data Set(s)

Delete current data of the selected entries (no history or anything similar is deleted!).

Rename

Change entry name.

Properties

Display/edit properties of the entry.

Close

End application.


9/44


Endress+Hauser 9

2.2.2 Edit

Select All

Select all entries (without "Add Entry".)

Create Copy

Create copy of the selected entry. The copy created is selected and deactivated.

2.2.3 View

Entry Name

Sorting according to "Entry Name".

Fieldgate ID

dito

Next Run Time

dito

Last Run Time

dito

Last Result

dito

Alarm Time

dito

Refresh

Update overview.

Auto Refresh

Overview is updated automatically.


10/44


10 Endress+Hauser

2.2.4 Tools

Preferences

Displays the "Program settings".

Show Log

Display log file in standard editor.

Delete Log

Delete log file.

2.2.5 Help

Contens

Display table of contents of the online help.

Topics

Display index of the online help.

About

display information aboutFieldgate Data Access.


11/44


Endress+Hauser 11

2.3 Toolbar

Add Entry

Add a new entry.

Properties

Change existing entry or display properties.

Activate & Run

Activate and start entry.

Activate/Deactivate

Activate/deactivate entry.

Preferences

Program settings.

View

Change overview sorting.

Refresh

Update overview.

Help

Open help file for the overview.

2.4 List view

The following functions can be implemented in the list opinion: The sorting can be changed by clicking on the title columns. Double-clicking on the entries opens a dialogue box containing the entry details. Double-clicking on "Add Entry" creates a new entry and opens the setting dialogue. Right-clicking on an activated entry opens a context menu. Numerous entries can be selected using shift-left mouse button and ctrl-left mouse button.


12/44


12 Endress+Hauser

2.5 Context menus

The context menu is to a large extent the same as the normal "File" menu.Dependent on the selected entries, options are activated/deactivated.

2.6 Status line

Double-clicking on "Auto Refresh On/Off" switches between these two statuses.


13/44


Endress+Hauser 13

2.7 Program settings

The basic program settings are made via "Preferences...". If the scanning (Service) parametershave been changed, a dialog box prompts you to restart the scan service. This takes place underWindows NT/2000/XP with system service installation via the Control Panel and underWindows 98, or if the scan service is not installed as a system service, by closing and then restarting

the program.

2.7.1 Miscellaneous

This tab is used to make basic program settings:

Data Root Directory

Root directory for CSV data, see also "Directory Structure".

Open dialogue box for directory selection using

Open Explorer in the data directory selection using

save data to CSV files

Save received data in CSV files.

use system time for time stamps

Use system time for time stamps: if this option is selected, the PC's clock time is always used as thetime stamp in the CSV data. If it is not selected, the time in the XML data is used for the time stamp(i.e. Fieldgate time).The system time is problematic if data is fetched from e-mail mailboxes because the collected datadoes not contain the measuring date, rather the time at which the mailbox was scanned.

store data to history database

If this option is selected, data records received are marked as history data. If this option is notselected, data records received are marked as records which can be deleted. Such data records areautomatically deleted once a younger data record is received.


14/44


14 Endress+Hauser

History Database Connection

Warning!

This is an option for experts!With the connection string, any external database can be used as a history database. Theconfiguration of the connection string is supported via .

Use to return to the standard connection string via . This is also the value recommended forthe normal user. In this way, an Access-compatible history database is created.

mimimize to system tray

If the Fieldgate Data Access window is minimized, a symbol is shown in the system tray. Thissymbol can be used to restore or close the application.Picture of the system tray:

The symbol outlined in red is the Fieldgate Data Access symbol.

enable bubble help

2.7.2 Mail

Settings relating to sending or receiving mails are made here:


15/44


Endress+Hauser 15

Mail Transmission

Fieldgate Data Access generates e-mails in the event of an alarm (e.g. cannot access Fieldgate,etc). The following settings are required for e-mail transmission.

SMTP Gateway

SMTP gateway specification (server for forwarding e-mails) for e-mail transmission. Ifauthentication is required, it can be performed in the input field with the:@ format. The gateway must be available in the local network.

To

Destination address (this can also be an e-mail address with domain specification!).

Sender

Sender's address (dito).

Forward unknown contentForward unknown data as an alarm e-mail. It can be a good idea to do this, for example, whenscanning the data via mailboxes.

Forward alarm emails

Forward alarm e-mails from Fieldgate.

Mail Reception

Fieldgate Data Access is able to receive mails from Fieldgates and process them further as per thecontents. For example, alarm e-mails are forwarded to the destination address shown above andmeasured value mails in XML format are interpreted correctly.

start Mail Server

This is used to start the mail server. The standard setting is "do not start". The standard port forSMTP (Port 25) is always used.

Username

For authenticating the user name used; the user name is configured on the Fieldgate under"Information & Configuration/Network Setup/Mail Configuration/SMTP Username".

Password

For authenticating the password used; the password is configured on the Fieldgate under"Information & Configuration/Network Setup/Mail Configuration/SMTP Username".

Username/Password can also be left empty. In this case, no authentication is necessary at theFieldgate Data Access Mail Server. However, only measured value mails in XML format are thenaccepted. Alarm mails and mails in an unknown format are not forwarded.

Note!

We strongly recommend using Username and Password as this is the only way to ensure that thedata actually do come from a Fieldgate and to prevent (to a large extent) other measured value mailscoming through!


16/44


16 Endress+Hauser

Below, you can find an example of Fieldgate configuration for sending mail (Information &Configuration/Network Setup):

2.7.3 OPC Server

This tab is used to make settings for the OPC server. The tab itself is only visible if the OPC serverhas been installed.Please note that the OPC server can only start if data can be stored in the history database.


17/44


Endress+Hauser 17

OPC Server

OPC Data Structure

Determines how the OPC tags of the measuring data are created. The following settings are possible:

Allow Write Access to Tags

With this setting, the OPC tags are created with write access. This setting is not recommended butis required by some OPC clients for correct OPC tag scanning (i.e. browsing).

Ignore OPC Data older than [x] days

Measuring data which have not been updated for more than [x] days are not reported to the OPCclients. This scanning only takes place when the OPC server is started; during operation, the "OPC-Quality" of the tags is set to "BAD" if errors occur.The idea behind this function is to prevent old data making the OPC data unclear.

2.7.4 Other Servers (andere Server)

Use this tab to configure other server services of Fieldgate Data Access:


18/44


18 Endress+Hauser

Time Server

start Time Server

This option is used to control starting the time server. Standard is switched off. It is recommendedto turn on the time server for the purpose of distributing the time to the Fieldgates.

use local Time

Use this option to specify whether the local time of the "Fieldgate Data Access" computer is sentto the inquiring Fieldgates or whether the universal time (UTC) is sent.The UTC setting is standard. In this case, the time offset with regard to UTC must be configured atthe Fieldgate as well as the summer-time/winter-time changeover.If the local time is sent, "0h" must be selected at the Fieldgates as the time offset. However, thishas the disadvantage that time stamping is no longer clear due to jumps at summer-time/winter-time transition.

Below, you can find an example of Fieldgate configuration for fetching the time(Information & Configuration/Network Setup):

Firmware Update Server

start Firmware Update Server

This option is used to control starting the update server. This is off as standard.

Port

this is used to select the port under which the server is active. Port 81 is preselected so the updateserver does not collide with any http server present (e.g. Apache).

Open Update Folder

opens the folder in which firmware updates have to be stored.


19/44


Endress+Hauser 19

Below, you can find an example of Fieldgate configuration for a firmware update(Information & Configuration/Special):


20/44


20 Endress+Hauser

2.8 Add scheduler entry, setting details

A dialogue box is opened for adding or editing scheduler entries. The dialogue box contains "Tabs",which help to structure the entry.

Other entry aids: If the entry is invalid, the "OK" and "Apply" buttons are deactivated, it is possible to abort the

entry using "Cancel". A tab, which contains an invalid entry, is marked (see the following screenshot: "Connection".) An input field, which contains an invalid entry, is given a highlighted background; how this

background looks is dependent on the settings (set colours). Settings that are not possible (e.g. when using a direct network connection, specifying a proxy

server is not allowed) are displayed by deactivated input fields.

A description of the individual tabs in the dialogue box will follow.

2.8.1 Description

This tab is used to describe the scheduler entry:

Entry Name

The specified name appears in the overview under the 'Name' column (1st column).

Comments

In this input field you can enter comments about the connection document; these are not shownin the overview.


21/44


Endress+Hauser 21

2.8.2 Connection

The connection model is specified in this tab:

http://, pop3://, imap4://

The basic model is selected in this line. http://

The Fieldgate is scanned directly. pop3://

The Fieldgate sends data to a pop3 mailbox. imap4://

The Fieldgate sends data to an imap4 mailbox.

Fieldgate in ...

The following dropdown list enables you to select a more specific model: LAN / direct Internet

The Fieldgate is located in the local network or the Internet can be accessed directly (e.g. via arouter). Internet via Proxy

The Internet can be accessed via a proxy; this specification can only be made for the httpconnection ("http://").

Internet via ISP (RAS)The Fieldgate or the mail server is accessed via a dial-in to an ISP.

Internet via ISP with Proxy (RAS)The Fieldgate is accessed via a dial-in to an ISP with a downstream proxy; this specification canonly be made for an http connection ("http://").

Dial in to Fieldgate (RAS)Direct dial-in to a modem or GSM Fieldgate; this is in principle an abbreviation for "Internet viaISP (RAS)" with IP/Name 192.168.254.1.


22/44


22 Endress+Hauser

Phonebook Entry

Specification of the telephone book entry for dial-in for "Internet via ISP (RAS)", "Internet viaISP with Proxy (RAS)", "Dial in to Fieldgate (RAS)"; the following button can be used for editingtelephone book entries.

Proxy

Specification of a proxy server for "http://" mit "Internet via Proxy" and "Internet via ISP withProxy (RAS)"; if necessary, the required user name and password can be specified via the followingbutton.

Fieldgate IP/Name

Specification of the server or Fieldgate name; if necessary, the required user name and password canbe specified via the following button.

Retries

Number of repeated attempts until the connection attempt is considered to have failed and an alarme-mail is triggered.

Retries After [min]

Time in minutes after which a retry is started.

Test Connection and Configure Passwords ...

It is recommended that you test the connection to the Fieldgate or to the e-mail server after enteringthe parameters listed above. This is performed using the stated button.User names and passwords that have not yet been specified can also be configured here.During the test, a message is displayed in another dialogue box, which provides information about

the progress of the test:

Use "repeat" to repeat a test as many times as you like. Use "Close" to close the testbox.


23/44


Endress+Hauser 23

2.8.3 Schedule

This tab is used to define the temporal sequence of the scheduler entry.

Enabled (Scheduled task runs at specified time)

This activates the scheduler entry.

Periodic

Periodic schedule. The following input box is used to define the time gap between two scans.

Valid entries are, for example: "20" (= 20 minutes), "20 m" (dito), "2 h" (= two hours), "1 h 30" (= one hour 30 minutes), "1 h 30 m" (dito).

ber die Pfeile wird die Zeit um 5 min verndert. Wenn machbar, werden die Abfragezeitpunkteso gelegt, dass sie u.a. zur vollen Stunde erfolgen (bei "20 m" als um hh:00, hh:20 und hh:40).

Scan Times

Scan at defined times. The times are defined in the input box next to the arrows and adopted intothe input list via "Add" or "Modify". "Delete" can be used to remove entries from the list. Thenumber of times is not subject to any practical restrictions (the number of different entries is smallerthan the number of possible entries).


24/44


24 Endress+Hauser

Alarm Time

If no data is received from a Fieldgate during this defined time, an alarm e-mail is triggered. It mustbe observed that alarm e-mails are also triggered when a connection cannot be established after nretries. This setting is, therefore, useful above all when scanning mailboxes because the mailboxscan can indeed be successful (connection could be established), but the Fieldgate has not been able

to send e-mails for 24 hours.

Mon, Tue, Wed, Thu, Fri, Sat, Sun

Here, the scheduler entry can also be deactivated for particular days.

0/1

This is used to completely set or completely reset the daily activation.

Note!

If the scheduler entry is not activated on any week day, this will be considered as an input error!


25/44


Endress+Hauser 25

2.8.4 Tools

An RAS telephone book entry, via which a Fieldgate can be contacted, can be created on this tabwith a few entries. It must be observed that the entry is suitable for contacting Fieldgates becausediverse network settings cannot be entered (e.g. user name/password).It must also be observed that RAS or DUN must be installed for using this tab. See also "System

requirements".

Entry Name

name of the telephone book entry. If this already exists, the "Create"-Buttons text changes to"Modify".

Phone Number

Telephone number.

Device

Selection of the modem that is to be used.

Open Phonebook

Opens the telephone book.

Create/Modify

Adopts the entries into the telephone book.


26/44


26 Endress+Hauser

2.8.5 SMTP Settings

This tab only appears if the entry selected has been (automatically) generated by SMTP receipt ofdata:

Alarm TimeIf no data are received from a Fieldgate during this defined time, an alarm e-mail is triggered.If a measured value mail is received from a Fieldgate, a data document with a related alarm time iscreated under the "SMTP-Server" connection document (this is a dummy). The alarm time is reseton each new receipt of data; an alarm mail is generated when the alarm time is exceeded.


27/44


Endress+Hauser 27

2.8.6 Data

This tab displays the last received XML data of the scheduler entry, i.e. provides information.


28/44

Further Information Fieldgate Data Access

28 Endress+Hauser

3 Further Information

3.1 CSV-Daten

The data received can be stored in CSV files. The data of one field device are saved per file. Onlythe most important data are contained in the CSV files. In particular, these are the measured values,the related unit and the measurement time stamp.

Notes on the CSV files: CSV data storage switch-on and switch-off in Preferences.

For location of data storage, see Directory structure.New measured values are always appended to the CSV file.The CSV files are notautomatically shortened, i.e. the CSV files are generated without sizerestrictions.The second line of the CSV file is contained for problem analysis.The date and number format are per the German configuration.The CSV files are write-protected. This prevents unintentional changes and the file being

"blocked" by Excel, for example.Tips: To find a CSV file quickly: click the corresponding entry in Fieldgate Data Access and then "CSV

Folder..." oder ber "File"/"CSV Folder..." If the CSV data should be evaluated in Excel, double-clicking the file does not display the data

properly in Excel. The data are correctly displayed by dragging and dropping into Excel.

An example of a CSV file is given below. Two measurements of a Nivotester FTC625 are displayed.

3.1.1 Original CSV file

3.1.2 CSV file viewed in Excel

"FTC625 / Nivotester - FTC-2";"Countrycode used:";"Deutsch (Deutschland)";"LongTimeFormat: hh:mm:ss";"ShortDateFormat: dd.MM.yy";"Device";"Tag";"Date & Time";"Measured Value 1";"Unit 1";"Measured Value 2";"Unit 2";"Measured Value 3";"Unit3";"Measured Value 4";"Unit 4";"high";"low";"device status";"level status";"Used Time";"FTC625 / Nivotester";"FTC-2";28.10.03 12:00:20;0,00;"";171,55;"Hz";0,00;"Hz";;"";0,90;0,10;"0x000x00";0;"UTC+2h""FTC625 / Nivotester";"FTC-2";29.10.03 12:00:14;0,00;"";171,55;"Hz";0,00;"Hz";;"";0,90;0,10;"0x000x00";0;"UTC+2h"

FTC625 / Nivotester - FTC-2Countrycode

used:Deutsch

(Deutschland)LongTimeFormat:

hh:mm:ssShortDateFormat: dd.MM.yy

Device Tag Date & Time MeasuredValue 1

Unit 1 MeasuredValue 2



Unit 4 high low device status levelstatus

Used Time

FTC625 /Nivotester

FTC-2 28.10.03 12:00 0 171,53 Hz 0 Hz 0,9 0,1 0x00 0x00 0 UTC+2h

FTC625 /Nivotester

FTC-2 29.10.03 12:00 0 171,55 Hz 0 Hz 0,9 0,1 0x00 0x00 0 UTC+2h


29/44

Fieldgate Data Access Further Information

Endress+Hauser 29

3.2 History database

The data records received are recorded in the history database. In contrast to CSV data, whenaccessing the database you have the advantage that the desired data records can be directly queriedby SQL. The data can be integrated in a worksheet in Excel (97), for example, via "Data/GetExternal Data/Create New Query..." and then processed further.

The basic settings for the history database are made in "Preferences...". To record the data, "storedata to history database" must be activated. Otherwise, only the Fieldgate data record last receivedis stored (this is necessary for the operation of the OPC serverI

Caution!

The OPC server only works if it is possible to write to the history database.There may only be one application that writes to the database!

3.2.1 Types of database

The history data are saved to an Access database as standard.Working with Access databases is, on the whole, transparent which is why it should also be usedby people with little experience in databases.

However, PostgreSQL, MySQL or SAP DB databases may also be used. Support must be providedso that "Fieldgate Data Access" can react to the particular SQL specialities of the databases:

The database is automatically generated for Access. For all other types, the database must be created

manually (by the system administrator, for example) with the relevant access rights. The tablescontained are generated by "Fieldgate Data Access".

Type of database ConnectionString

Access "Provider" must contain "Microsoft.Jet.OLEDB"

MySQL "Data Source" must begin with "mysql"

PostgreSQL "Data Source" must begin with "postgresql" oder "pg"

SAP DB "Data Source" must begin with "sapdb"


30/44


30 Endress+Hauser

3.2.2 Table structure

The data are stored in the history database in a hierarchical table structure. The variability of thedata increases from left to right (see graphic). This has the advantage of compressing information ordatabase compactness.

Data fields beginning with "x_" are generated directly from the XML data. Fields with anotherprefix are used for database administration or have been partially used to avoid ambiguity (e.g."f_unid").

A brief explanation of the tables and their particular data types follows. Reference is made to theFieldgate Operating Instructions for an explanation of the XML data fields.


31/44


Endress+Hauser 31

3.2.3 TFieldgate

3.2.4 TDevice

3.2.5 TDataConst

Contains Fieldgate configuration data andindicates the data root of a Fieldgate.

"f_isok" indicates whether a Fieldgate issupplying data

"f_unid" is the Fieldgate serial number "f_tag" is the "Fieldgate Identification"

Contains, among other things, the HART

configuration data of a field device. "d_isok" indicates whether a field device is

supplying data "d_xmltype"="f" the data were taken from

a full XML data record "d_xmltype"="p" the data were taken from

a partial XML data record

Contains the data of a process value (a HARTfield device can supply up to four values).

"c_unid" is set as per the measured valuenumber ("1", "2", "3", "4")


32/44


32 Endress+Hauser

3.2.6 TDataVar

3.2.7 Access to the database

The history database is generally accessed via SQL. Microsoft applications offer "Microsoft Query"

as a tool which can be used to create queries graphically:

The related (simplified) SQL query would look like this:

This query can be easily adapted to your own queries.

Contains the variable data of a process value.

"v_islast" indicates whether this is the latestmeasured value

"v_ishistory" indicates whether this value isrecorded in the history

"v_origin" indicates the kind of data sourcethe data record comes from("999" http,sotherwise the codes of the XML mails)

"x_v100" and "x_vlc" are only created for thefirst process value

SELECT *

FROM TFieldgate,TDevice,TDataConst,TDataVarWHEREd_f_nr=f_nrANDc_d_nr=d_nrAND

v_c_nr=c_nrAND(f_tag="Demo.Inventory.Control.A")AND(x_tag="TANK ONE")AND(c_unid="1")ORDER BYx_vtime


33/44


Endress+Hauser 33

3.2.8 Using a data source

Please note that these instructions do not apply to the Access database used as standard!

The following conditions must be met: Database installation (MySQL, PostgreSQL, SAP DB) with corresponding access rights. ODBC installation on the ODBC client side.

Empty) database in this database system, name e.g. "FieldgateData". Creation of a System DSN. Under Windows NT under "Control Panel/Data Sources (ODBC)/

System DSN", under Windows 2000 and XP under "Control Panel/Administrative Tools/DataSources (ODBC)/System-DSN". Database names, connection options and the DSN name areassigned here. The configuration depends on the database which is why we do not go into moredetail here.

In "Preferences..." the system DSN created can only be selected via and then by specifyingthe provider (ODBC).

The server then has to be restarted.

Now the data received are written to the database specified by the system DSN.If the data are to be scanned, you have to select the system DSN (similar to in the second-last point)and you can then access the data.

3.3 OPC-Server

The OPC server is an installation option, i.e. it cannot be activated at a later date after installation.It can only be installed under Windows NT/2000/XP. It is possible to deactivate it via "fxada/uninstall-opc" in the installation folder (see Command line parameters). Basic settings of the OPCserver can be made via "Preferences...".

Caution!

The OPC server only works if it is possible to write to the "history database".

Note:

The name of the OPC server DCOM object is "Endress+Hauser.Fieldgate.OPC", the GUID"5C1BCBBF-8A17-418F-AAA9-CAD25F14F235". The complete data structure of the OPC server cannot be changed via OPC clients (read-only)!


34/44


34 Endress+Hauser

3.3.1 Tag structure

A certain OPC tag structure is created from the measuring data received. Three data trees aregenerally available: "unid", "tag" and "description":

If a section is hierarchically separated, a "." is used. Otherwise a "_" is used. Periods in the text areconverted to "_".In the "unid" and "tag" tree, the data of a complete field device are at the bottom and the data of a

single measured value are in the "description" tree."Preferences..." is used to select how the individual sections are separated. Section separation isthen carried out as follows:

This structure is specified by the program, i.e. all existing tags are generated when the OPC serveris started. This procedure has the advantage that the existing tags can be easily queried by the user.

The disadvantage is that the user cannot add any other tags.

unid The entire tag is created from the "unid" text, the Fieldgate and field device serial numbers.

The name of the parameter is appended.i.e.: "unid"

tag The entire tag is created from the "tag" text, the "Fieldgate Identification" (Fieldgate configuration:Information & Configuration / Fieldgate Location), the field device tag and the name of the parameteri.e.: "tag"

description The entire tag is created from the "description" text, the description text 1, the description text 2 and thename of the parameter. The description texts are set on the Fieldgate in the field device display.i.e.: "description"

Setting Section separation Example

hierarchical =".", =".", ="."

flat devices =".", ="_", ="."

flat fieldgates =".", =".", ="_"

flat ="_", ="_", ="_"


35/44


Endress+Hauser 35

3.3.2 Parameters

Internal parameters start with a "_"; remaining data are taken directly from the XML data. For thisreason, please refer to the Fieldgate Operating Instructions for further information.

The "d", "t", "u" columns indicate whether a parameter is in the tree in question. : oes not appear in the "description" tree; in the "tag" and "unid" tree as per the number

of the measured values appearing in the XML data. For adapting the data type, see also OPC-FAQ. The time stamp of the measured values corresponds to "vtime". The quality of the measured values is GOOD (192) for "_alive"="1", otherwise

OUT_OF_SERVICE (28). If the limit values are undershot or overshot, LIMIT_LOW (+1)

or LIMIT_HIGH (+2) is also set in the quality.No distinction is made between Low and LowLow or High and HighHigh..

Name d t u Type Explanation

_alive x x x String Indicates whether the measured value is valid ('0'/'1')

_ctime x x x Date This is the time when the entry was generated in the history database

_description x x String Reference to the "description" tree

_postfix x String Reference to the corresponding measured value in the " tag" and "unid" tree

_tag x x String Reference to the "tag" tree

_time x x x Date This is the time when the entry was imported into the OPC server

_unid x x String Reference to the "unid" tree

desc x x String Description of HART field devices

dev x x String Name of HART field devices

hh x x x Double Set HighHigh-Limit of measured value

hi x x x Double Set High-Limit of measured value

hlsts x x x String Status of the measured value

ll x x x Double Set LowLow-Limit of the measured value

lo x x x Double Set Low-Limit of the measured value

man x x String Manufacturer of HART field devices

msg x x String Message of HART field devices

tag x x String Tag of HART field devices

u x x x String Unit of the measured value

v x x x Double Measured value

v1_100 x x Double Percentage primary measured value

v1_lc x x Double Value of the current output of the field device

vstslvl x x x Integer Status of the measured value

vtime x x x Date Measuring date in the Fieldgate


36/44


36 Endress+Hauser

3.3.3 Access control to the OPC server

Access rights to the OPC server via the network are given under Windows NT and 2000 via"dcomcnfg.exe" under Default Security.Under Windows XP, it is also dcomcnfg.exe, then "Console Root/Component Services/Computer/My Computer", then Properties and then COM Default Security.

Here, the permitted users are configured under access and start rights.In addition, you must check whether DCOM is activated on this computer (Default properties).

Caution!

These are security settings. Settings should only be made by experienced users or after consultingthe local system administrator.

Note!

Normally, it should be possible to individually configure the DCOM access rights for each DCOMobject. This is currently not possible for the Fieldgate Data Access OPC server. The problem will besolved in a future version.

3.4 FAQ

3.5 OPC-FAQ

Problem Solution

Windows NT4, system service: when the user logs off, amessage is output that "fxada.exe" is not responding.

This seems to be caused by out-of-date DLL versions.Importing Internet Explorer 6.0 SP1 (or later) shouldremedy this SP6a should have been imported previously.

How do I start the "'Fieldgate Data Access" service (or stop orrestart)?

Under Windows NT via Control Panel/Services and then"E+H Fieldgate Data Access".Under Windows 2000/XP via My Computer/Manage/Services and Applications/Services and here also "E+HFieldgate Data Access".

"Start menu/Programs/Endress+Hauser/Fieldgate/ToolDirectory and then 'Fieldgate Data Access (Server Start)"

and "Fieldgate Data Access (Server Stop)".

If the existing RAS connection is interrupted (telephone linedisconnected), Windows 2000/XP opens a dialog box andasks whether it should dial in again. And this even thoughFieldgate Data Access is running as a system service (i.e. inthe background).

In the settings of the dial-up connection entry, deactivate"Redial if line is dropped".

I have encountered an error in Fieldgate Data Access. Whocan I contact?

Please send error messages, with an exact description ofthe error (type of error, how the error condition isgenerated, etc.) and with information on the systemconfiguration to "[email protected]".

Problem Solution

OPC does not work on my "Windows NT"computer. What could be the reason?

This seems to be caused by an out-of-date DLL. Installing InternetExplorer 6.0 SP1 helps!

I am looking for a simple OPC client for testpurposes.

An overview of free OPC tools can be found under "http://www.opcconnect.com/freestuf.php".

For example, Matrikon OPC Explorer, found under "http://www.matrikon.com/drivers/opc/explorer.asp".


37/44


Endress+Hauser 37

3.6 Glossary

I cannot browse through the tags of the "FieldgateData Access" OPC server with my OPC client.

In certain situation, you can configure the client as to which tagsshould be browsed, e.g. tags with read/write access or read-onlyaccess. In this case, configure the client in such a way that it doesnot insist on write-access for the tags as the "Fieldgate Data

Access" OPC tags normally do not allow any write access.

Some OPC clients do not display the tags despite the settingmentioned above. If this occurs, you can try the "Allow Write

Access to Tags" setting in "Preferences..." (restart server!).Precedence should be given to the "don't allow" setting, however!

My OPC client cannot handle floating pointnumbers correctly.

This solution is a trick and should only be applied by

experienced users!

In the fieldgateda.ini, create an entry with the name"OpcFloatType" under Configuration and give the value 2 (16bitInteger), 3 (32bit Integer), 4 (Float) or 8 (String). Do not forget torestart the server!

My OPC client cannot handle integers correctly. This solution is a trick and should only be applied byexperienced users!

In the fieldgateda.ini, create an entry with the name 'OpcIntType'

under Configuration and give the value 2 (16bit Integer), 4 (Float),5 (Double) or 8 (String). Do not forget to restart the server!

My OPC client cannot handle time stamps correctly. This solution is a trick and should only be applied byexperienced users!

In the fieldgateda.ini, create an entry with the name "OpcDateFmt"under Configuration and specify the time stamp format (e.g.

yyyymmdd-hhnnss). Do not forget to restart the server!

Abbreviation Description

CSV Comma Separated Values.Standard text format for data exchange.

DUN See "RAS".

HTTP Hypertext Transfer Protocol.Access protocol, as usually used by web browsers. The Fieldgate provides itsinformation mostly via http.

IMAP4 Internet Message Access Protocol, Version 4.Access protocol, as usually used by e-mail programs. The Fieldgate sends e-mails, which are under certain circumstances (provider-dependent) saved on animap4 server. imap4 is used to fetch the e-mails.Note: the imap4 support in Fieldgate Data Access is experimental!

ISP Internet Service Provider (in Germany e.g. T-Online, Arcor, MSN, freenet,...),

good overview at "http://www.heise.de/itarif/view.shtml?function=ohneanmeldung"!)

OPC OLE for Process Control: "Standard" Windows protocol to exchange data forprocess automation.

POP3 Post Office Protocol, Version3.See "IMAP4".

RAS Protocol under Windows, in order to establish a TCP/IP connection viamodem. A modem Fieldgate can be selected directly via RAS or the dial-in toan ISP can be performed.

SMTP Simple Mail Transfer Protocol.Protocol for e-mail transmission. Is used by Fieldgate for sending e-mails.Optionally, authentication can be performed at the smtp gateway (user name/password).

SQL Standard Query Language.Query language for database access.

Problem Solution


38/44


38 Endress+Hauser

3.7 Symbols

Symbols in the overview

Symbol Description

Add Entry

Add entry by double-clicking.

Direct Fieldgate connection in the network; the connection can also be made via a proxyserver.

Direct Fieldgate connection via RAS; the connection can also be made via an ISP and aproxy server.

Deactivated Fieldgate connection.

POP3/IMAP4 connection in the network.

POP3/IMAP4 connection via RAS.

Deactivated POP3/IMAP4 connection.

Connection document of the SMTP server


39/44


Endress+Hauser 39

3.8 Command Line Parameters

Normally, Fieldgate Data Access v is operated by the user without command line parameters. Inthis case, the GUI component is started and also, if not already started, the server component.Nevertheless, Fieldgate Data Access has some parameters used to complete the separationbetween GUI and service.

3.9 System Service

Installation as System Service

Under Windows NT4 / 2000 / XP, Fieldgate Data Access can also be installed as a systemservice. This means thatFieldgate Data Access also works when no user is logged on.

The following points must be observed:

Administrator rights must be available during installation, When installing Fieldgate Data Access, "Installation as system service" must be activated, The system service must be configured via an administrator account (scheduler settings, etc.),

If the system service is to be installed subsequently, "fxada.exe /install" must be run via acommand line.Deinstallation can be carried out in the same way via "fxada.exe /uninstall".Using "fxada.exe /?" , a complete list of the permitted "Command Line Parameters" can beoutput.

Parameter Description

/gui Start only GUI component (or bring it to the foreground).

/tray Start GUI in the system tray (or send it to the system tray).

/server Only start server/service component.

/stopserver Stop the server/service component.

/install Install as NT service (server component).

/uninstall Deinstall NT service.

install-opc Install OPC server. This option is normally run by the installation routine. IfFieldgateData Access has been installed without OPC, some system libraries are missing.

uninstall-opc Uninstall OPC server.

/silent Above options without issuing a dialogue box.


40/44


40 Endress+Hauser

3.10 Directory Structure

Fieldgate Data Access creates the following files:

File names marked Bold are not files, but Explorer links.

ExeRoot Installation directory Fxada.exe Executable file

Fxada.hlp Help fileFxada.cnt Table of contents of help fileFieldgateda.mdb Configuration database (Access97

compatible)Fieldgateda.mdb.bak Back-up of the configuration database - is

created from the configuration databaseevery time the server component program isstarted

Fieldgateda.txt Log fileData Data directory, can be configured via

"Preferences"Csv Directory, which contains the CSV data

sorted according to serial number(Fieldgate/sensor)

Ser_470009010A0 Fieldgate with serial number 470009010A0with prefix "Ser_"

11c81b80f6.csv CSV data of sensor with the HART uniqueID "11c81b80f6"

1151fe1dde.csv ...:Index.xml Last XML data received from the FieldgateEh_fieldgate Link to directory with symbolic names

Ser_...Csvtag Directory, which contains links to the

actual CSV data. These are sortedaccording to symbolic names (Fieldgate ID/ sensor tag)

Eh_fieldgate Fieldgate IDTEMPOUT Link to CSV data of the field device with the

"TEMPOUT" tagPRESSURE

:Index.xml Link to last XML data received from the

FieldgateSer_470009010A0 Link to directory with serial number sorting

Fieldgatename... ...

:Mail Mail directory (internal use)

...


41/44


Endress+Hauser 41

3.11 Known Restrictions

Passwords for RAS entries, Fieldgate connections etc. are saved as plain text in the INI file andthe configuration database, see also the "Security instructions".

IMAP4 support is experimental, mailbox access via POP3 should be given precedence. SMTP gateway for alarm mail/mail forwarding:

User/password specification is awkward, Must be in the network, i.e. no dial-in connection possible.

Only a RAS connection is used for modem dial-in. History DB: limited to Latin-1 character sets (however, the data coming from Fieldgate are in the

iso-8859-1 character set). No SSL connections. OPC security: accessing users must be entered under Default Security. Bug: time entry fields must be exited for the value entered to be accepted (entering Return is not

sufficient). Bug: with the "Test Connection" dialog box: if a password is required for Fieldgate access, the

dialog box for entering the password is not opened (only Windows XP)

3.12 History

Software version/Date Changes

28052003 (Release 1.0.0)

31102003 (Release 2.0.0 History database OPC server SMTP server for receiving measured value Firmware update server Storing the configuration in the INI file IP/address with "Dial in to Fieldgate (RAS)" connection type can be edited


42/44

Fieldgate Data Access Index

42 Endress+Hauser

Index

Symbols/gui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39/install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

/runasservice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39/server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39/silent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39/stopserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39/try . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39/uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Numerics0/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

AAbout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Activate & Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8, 11Activate/Deactivate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Add Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Adding scheduler entries . . . . . . . . . . . . . . . . . . . . . . . . . 20Alarm signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Alarm Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9, 24Auto Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Auto Refresh On/Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

CClose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8, 22

Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Contens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Create Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Creates a new entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11CSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37CSV Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

DData. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2627Data Root Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Data sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Data storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Delete Connection Document(s). . . . . . . . . . . . . . . . . . . . . 8Delete Data Set(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Delete Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Dial in to Fieldgate (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . 21DUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

EEdit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Editing scheduler entries . . . . . . . . . . . . . . . . . . . . . . . . . 20enable bubble help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Enabled (Scheduled task runs at specified time). . . . . . . . . 23Entry Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9, 20, 25

FFAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Fieldgate Data Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Fieldgate ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Fieldgate in .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Fieldgate IP/Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Forward alarm emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Forward unknown content . . . . . . . . . . . . . . . . . . . . . . . . 15Fri . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

HHelp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37http://. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

IIMAP4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37imap4:// . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Internet via ISP (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Internet via ISP with Proxy (RAS) . . . . . . . . . . . . . . . . . . . 21Internet via Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21ISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

LLAN / direct Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Last Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Last Run Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Licensing agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

MMail Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14mimimize to system tray . . . . . . . . . . . . . . . . . . . . . . . . . . 14Retries After . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23, 25Mon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Multithreading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

NNext Run Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Numerous entries can be selected . . . . . . . . . . . . . . . . . . . 11

OOpen Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

PPeriodic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Phone Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Phonebook Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22POP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37pop3:// . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011, 13Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8, 11

Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

RRAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


43/44

Fieldgate Data Access Index

Endress+Hauser 43

Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9, 11Rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8repeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

S

Sat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24save data to CSV files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Scan Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Select All. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Show Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37SMTP Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Sorting can be changed . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Sun. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

TTest Connection and Configure Passwords .... . . . . . . . . . . 22Thu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24To. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10, 25Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Tue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Uuse system time for time stamps . . . . . . . . . . . . . . . . . . . . 13

V

View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9, 11

WWed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

XXML Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8


44/44

www.endress.com/worldwide

fieldgate data access software

Documents