FC1 - Updating from enSuite 2.x to 3 - Honeywell Elster example, in case Modbus is us ed the...

of 18 Updating to enSuite 3.0

Updating from enSuite 2.x to 3.0 – A brief overview about the changes –

(2015-01-08)

Content

Abstract 2

How-to create new parameterizations for the normal mode? 3

How-to parameterize in normal mode? 5

The general user interface 5 What can be done in normal mode? 6 … and what cannot be done in normal mode? 7

The Expert Mode – Redesigned User Interface 8

How-to convert parameterizations from enSuite 2.x to 3.0? (Expert Mode only) 11

Converting a parameterization (without Archives) 11 Converting a parameterization (with Archives) – includes firmware update 12

Further Enhancements 16

Improving Modbus Lists 16 IP-Settings via enSuite (new feature) 17 Network Service Bindings (for future use) 18


Abstract The update from enSuite 2.x to the new 3.0 brings major changes in parameterizing enCore devices. This document aims to ease the update for users who are already familiar with enSuite 2.x and want to update to enSuite 3.0. It gives a general overview about the changes; as usual, the individual parameters are described in detail in the online help of enSuite.

The focus of enSuite 3.0 lies on improving the user-friendliness, especially for standard flow conversion applications for enCore FC1 device types. The parameterization of enCore FC1 devices types is very flexible and can become complex. Since this flexibility is not needed for standard flow conversion applications, the idea was formed to hide the complexity from the user for standard application wherever meaningful, and at the same time keep all the possibilities accessible the device has to offer. Hence, the major improvement is the introduction of 2 parameterization modes, the normal mode and the expert mode:

Normal Mode Expert Mode

Purpose standard applications for flow computers for gas

any applications

Characteristics − new user interface with a simplified view

− optimized for flow conversion standard applications

− creating a new standard parameteri-zation with just a few mouse clicks

− ≙ "next generation" product para-meterization with a new user interface

− improved former user interface with full flexibility

− improved user-friendliness by opti-mizing the parameter tree, higher configurability of input boards etc.

Typical user − inexperienced users − users with standard flow conversion

requirements

− sales representatives with technical background

− service engineers − user with complex requirements


How-to create new parameterizations for the normal mode? The wizard for new parameterizations was enhanced to create easy to configure standard parameterizations for flow conversions: ► Start the wizard in the navigation tree <device name> with the action New parameterization). Now 3 options are available for enCore FC1 device types:

Opens in…

Normal Mode (new option)

Normal or expert mode

Expert mode

Fig. 1: Wizard for new parameterizations

• Standard flowcomputer for gas The 1st option is newly implemented in enSuite 3.0 to create standard parameterizations for the normal mode and is only available for enCore FC1 devices.

• Copy from product parameterization1 The selected product parameterization will open either in normal mode or in expert mode depending on the mode in which the parameterization was saved with.

• From scratch1 Inherently, this option is only available for expert mode.

► To create a normal mode parameterization, activate the option Standard flowcomputer for gas and simply

select the following characteristics for your application:

Standard case options Description

Approval The approval file sets the underlying user and access rights.

Housing width Defines the maximum number of card slots that can be parameterized in I/O configuration: − 1/3 19'': (max.) 4 × input boards − 1/2 19'': (max.) 7 × input boards

Input board(s) Either MFE7 or ExMFE5 can be used to connect pressure and temperature transmitters, and gas meters with pulse interface.

Stream 1/ Stream 2

Number of given streams: − 1 or 2 flow direction(s) for turbine meters (≙ pulse input) − 1 or 2 flow direction(s) for ultrasonic meters (≙ protocol interface)2

Modbus Specifies the number of Modbus lists. By default the Communication mode is set to Slave or Server.

Archives either used or not used In case archives are used, meaningful archive group for hourly, daily and monthly values are created for a flow conversion.

1 The 2nd and 3rd options were already implemented in former enSuite versions. 2 In case an ultrasonic meter is connected via pulse input, choose the corresponding option for turbine meters.


On the bases of the selected options the default parameterization is optimized as follows:

The required instances of the Basic System and AFBs are already included in the parameterization:

Wizard options Values selected Functional Blocks (FBs) created3

1 × Basic System with all SFBs

Stream 1

1 fd, turbine/ 1 fd, ultrasonic

1 × F l o w C o n v e r s i o n A F B 1 × G a s Q u a l i t y A F B

1 × S t a t i o n A F B




Stream 2 (optional)



2 × S t a t i o n A F B 4




Modbus

not used –

1 list 1 × M o d b u s A F B

2 list 2 × M o d b u s A F B

Archives

not checked –

checked 1 × A r c h i v e A F B

1 × P o s t p r o c e s s i n g A F B 5

Only parameters related to the selected standard case are accessible.

The wizard creates default settings. That means, whenever possible the parameters are initialized with reasonable default values, only meaningful selections are offered and dependent parameters are set accordingly. For example, in case Modbus is used the communication mode is set to Slave or Server and the inter-face is TCP/IP as default. Please note that the communication mode cannot be changed in normal mode, as opposed to the interface which can be set to serial. The list of Modbus registers for the 1st M o d b u s A F B include useful default values for the enCore FC1, in case of 2 Modbus lists were selected, no Modbus registers are created for the 2nd M o d b u s A F B .

3 For normal mode the wizard always uses the latest SFB and AFB Firmware that is available in accordance to the selected approval. In enSuite 3.0 the version 03-00 for all FBs is used. 4 For dual streams the calculation of Station flow totals can be activated. The calculation of Σ streams is always done by the 1st S t a t i o n A F B . 5 A P o s t p r o c e s s i n g A F B is always created and used for input values, but is not accessible in normal mode.


The initial setup cannot be changed in normal mode.

None of the options selected in the wizard can be changed in normal mode without creating a new parameterization or switching to expert mode. The type of AFBs as well as the number of instances for each AFB is fixed after the initial setup.

How-to parameterize in normal mode? The normal mode shows parameterizations in a simplified view. As mentioned before, the options accessible in a standard parameterization depend on the initial setup of the wizard. In general, features and parameters are hidden, in case…

• … they go beyond the easy to configure standard application,

• … they are not needed for the current configuration, or

• … parameters with only 1 option to choose from.

If necessary, you can always view the underlying and dependent settings in expert mode and switch back to normal mode for further editing (via Tools and de-/activating Expert mode).

Normal mode parameterizations can be viewed in expert mode

You can always view the current settings of a parameterization by switching to expert mode. But, once a parameterization is modified in expert mode, switching back to normal mode is not possible anymore; the only exceptions are modifications of user configured displays and user rights.

You open the normal mode either by creating a new parameterization with the option Standard flowcomputer for gas or by opening an existing normal mode parameterization. Dependent parameters are automatically updated, if possible. In case values needed by flow conversion or gas quality are no longer available, this leads to an invalid parameterization. enSuite shows which value(s) are missing – e.g. "Pressure input: Not found".

The general user interface

Fig. 2: Example for a standard parameterization in normal mode

• The parameter tree is shown on the left side always starting with Start (I/O configuration) as 1st node. Following functionalities are available:

Start (I/O configuration), General settings, Stream <x>, [Archives], [Modbus list <x>], [Station].

In normal mode the node order guides you through the most important settings. We recommend to follow this order especially for new parameterizations.


• The parameters for the selected functionality are displayed on the tab in the middle, f.i. tab I/O confi-guration.

• Export data tree

In normal mode a list of dedicated export data objects is available for drag and drop. This list is only needed in case I/O boards, Modbus or archives are parameterized. The list is available in the Export values view you are already familiar with from enSuite 2.x (Window – Export values).

What can be done in normal mode? In normal mode "only" the parts of the FC1 features that are used for flow conversion are available:

• I/O configuration and intelligent measurement devices

On the tab I/O configuration you parameterize all settings that belong to 1 channel. I/O as well as intelligent measurement devices can be configured in this view.

Fig. 3: Parameterizing I/O in normal mode – example

The type of input board(s) used for flow conversion (1 × ExMFE5 or 1 × MFE7 for each stream) cannot be changed in normal mode. But for all other boards, you can select the type of the board for each slot. The matching picture of the board is displayed. You configure a channel by simply clicking the corres-ponding channel in the picture. The selected channel is then marked with a red rectangle and the corres-ponding parameters are shown below the picture and can be edited.

• General settings

This view allows parameterizing the default unit for each physical quantity on tab Default units. Additionally, a stripped-down T i m e S e r v i c e can be parameterized on tab Time Service. It allows setting time zone, daylight saving time, time synchronization with 1 NTP server and the definition of 1 contract hour.

Fig. 4: General settings contains Default units and stripped-down Time Service


• flow conversion functionality (Stream <x>)

Flow conversion functionality is displayed in a combined view (1 × G a s Q u a l i t y A F B , 1 or 2 × F l o w C o n v e r s i o n A F B ) for each stream separately. As the tab labels already indicate …

− … tab Gas meter shows parameters concerning gas meters: In accordance to the selections during the initial setup you modify the connected input boards, manage the flow direction or parameterize a meter correction or VOS comparison (AGA 10).

− … tab Gas condition shows parameters concerning the qas quality f.i.: Here you parameterize pressure and temperature inputs and specify the gas quality according to it's base and end base conditions, calculation method and gas composition.

Fig. 5: Stream 1 contains the flow conversion funtionality for the 1st stream

Furthermore, depending on the initial setup Archives resp. Process value archives, Modbus list <x> and the Station can be accessed.

… and what cannot be done in normal mode? All features and parameters that go beyond the easy to configure standard application cannot be modified in normal mode. An incomplete list:

• general user management and special user rights, user rights on parameter level as well as export values and virtual login

• creating, editing or deleting user defined displays (Basic system) Editing displays is nevertheless possible by switching to expert mode and back to normal mode.

• adding or deleting AFBs

• 2nd end base condition for F l o w C o n v e r s i o n A F B

• pulse integrity checking

In case your application requires functionality that is not covered by normal mode (e.g. L i q u i d Q u a l i t y A F B

and L i q u i d F l o w C o n v e r s i o n A F B ), you need to switch to expert mode to edit your parameterization.


The Expert Mode – Redesigned User Interface The expert mode is the view you are already familiar with from enSuite 2.x. In enSuite 3.0 we also tried to improve the user-friendliness and transparency for this mode. This resulted in a redesign of parts of the parameter structure. These improvements concern for instance:

• Restructured parts the Base system in the Parameter tree:

− The folder I/O boards moved one level up acc. to it's importance.

− All functions of the Gas meter tools and Measurement Tools are now combined in the new node Tools.

− Intelligent measuring devices such as HART transmitter or ultrasonic gas meter can directly be configured in the node I/O boards with the corresponding I/O channel. Measuring devices that are connected via TCP/IP are parameterized in the new folder Mea-suring via IP.

− The former nodes System, Error List and Audit trail are now combined in the newly created node System settings.

Fig. 6: Example – Parameter tree in expert mode

• A reduced depth of the parameter tree brings you "faster to the parameter".

With its many subfolders enSuite 2.x could become non-transparent at times. Where appropriate we tried to reduce the subfolders to a maximum depth of 2 subfolder levels for each node. The subfolders were replaced by sections on the tab Parameters and can be viewed at one glance. The sections can be folded and unfolded separately.

Fig. 7: More clarity due to less subfolders and new sections on tab Parameters


• Parameters which were formerly in the root of SFBs and AFBs are now grouped in the section General at the top of tab Parameters.

Fig. 8: New section General

• Editable export values are now displayed on a separate tab Exports.

In enSuite 2.x editable export values were displayed on the same tab as their parameters. To increase clarity, parameters and editable export values are now disjoined and the export values are displayed on a separate tab Exports. This tab is displayed if at least one export data object is shown for the selected folder in the parameter tree. As in former versions, the unit for single export data objects and the user rights can be modified.

Fig. 9: Example – editable export values displayed on tab Exports

• The toolbar in the column Rights is reduced by default.

In the latest enSuite version a reduced rights toolbar is displayed by default to arrange the parameterization more clearly. Since user rights rarely have to be modified, the symbols to edit user rights are hidden and only the legally relevant access rights ( , ) are displayed on parameter level in the column Rights.

Fig. 10: Reduced toolbox for access rights by default

You expand the toolbar by switching to the root node <device name>, opening the tab Parameters and activating the checkbox Edit user rights.

Fig. 11: How-to display user rights (expanded rights toolbar)

In case the checkbox is disabled, a user without administrator rights is currently logged virtually. Hence, you need to logout the user first by deactivating the checkbox Use virtual login.


As soon as this checkbox is activated, the rights toolbar is expanded and the user rights can be edited in the parameterization:

Fig. 12: Expanded (full) rights toolbar

• Parameters for AFB names and grouping

In enSuite 2.x AFB names and grouping were configured in the parameter list. Now they can be edited directly at the AFB’s root node, when you right-click the node and edit the context menu.

Fig. 13: Renaming and grouping now directly in the AFB's context menu

• User Configurable Displays

The former tab Displays in the parameter tree is replaced by the root node Displays in the parameter tree. Additionally, the copy and paste functionality is now available for most display definitions – apart from displays that are either security switch protected or system display definitions.

Fig. 14: New node Displays now with copy and paste function for display definitions


How-to convert parameterizations from enSuite 2.x to 3.0? (Expert Mode only) Please note that the way to convert a former parameterization to current enSuite 3.0 has not changed. Converted parameterizations can only be opened and edited in expert mode.

Typically, you update an existing enSuite installation by keeping the enSuite data base. In this case, at the start of enSuite 3.0 the former parameterizations are already available in the Navigation branch.

During a conversion enSuite maps the former parameterization to the new data structures. Since enSuite is downwards compatible former parameterizations are not converted automatically. Do the following steps for every parameterization that needs to be converted – the steps differ for parameterizations using the A r c h i v e A F B :

Converting a parameterization (without Archives) (p. 11)

Converting a parameterization (with Archives) – includes firmware update (p. 12)

Converting a parameterization (without Archives) ► We strongly recommend to back-up your parameterization with File – Export first. ► Open the root node <device name> of the desired parameterization. ► On tab AFB configuration select for the Basic System the current version 03-00 by selecting the first entry

in the list.

Fig. 15: Update the Basic System to the latest version 03-00

enSuite adopts this version 03.00 for all AFBs listed and all AFBs that are part of the parameterization are displayed in a green font. The former A r c h i v e A F B is removed and the new AFBs A r c h i v e as well as P r i n t e r are added to the list.

Fig. 16: In enSuite 3.0 the corresponding AFB versions 03-00 are automatically selected

► Start the conversion with [Commit changes] and confirm the security prompt. ► Just to be sure, review the Output window for any indications regarding conversion problems.


Accessing incompatible parameters

As with previous versions incompatible parameters are marked in red font and also the section and higher-level node(s) these parameters are assigned to. Hence, to access such a para-meter you simple need to follow the redly marked node(s) and section, because the incompa-tible parameter is typically the endpoint.

Due to the redesign of enSuite 3.0 in exceptional cases it might seem that the wrong level is marked, because no incompatible parameter lies within this section or node. If this is the case please check the associated node or section.

Fig. 17: Example – the incompatible parameter in associated section above (exception)

In the example you would expect to access the incompatible parameter Substitute value mode in the node Simulated values – Run number: Counter, but instead you access it as endpoint in the associated section Simulated values – Run number above.

Converting a parameterization (with Archives) – includes firmware update In this release the data access speed to archives is improved. Thus, the data management of the A r c h i v e A F B was refactored internally. Due to these major changes a new A r c h i v e A F B version 03-00) replaces the former A r c h i v e A F B (version 02-14 and smaller).

Please note that an archive written with a former version of the A r c h i v e A F B cannot be accessed with the new A r c h i v e A F B . Additionally the firmware can only be updated if the current parameterization in the device does not contain the former A r c h i v e A F B . Hence a workaround is needed. The steps to be taken are in short: readout the archive before the firmware update, transfer a parameterization to the device that does not contain an instance of the former A r c h i v e A F B (!), include the new A r c h i v e A F B into the firmware update, copy the archive definitions and transfer the converted parameterization to the device.

A firmware update will delete the archive data in the device!

Readout the archives before updating the firmware of the device, because the data of the archives will be irrecoverably deleted!


In detail, follow the following steps to update the firmware and convert a parameterization that uses archives: ► Readout the parameterization twice that uses archives with Readout parameterization:

• name the 1st f.i. Read_<date>_BACKUP

Fig. 18: 1st read parameterization is used as a back-up

This parameterization will be used to copy the former archive definitions.

• name the 2nd f.i. Read_<date>_WORK

Fig. 19: 2nd readout parameterization is used for the workaround

This parameterization will be used for the firmware update and will be converted. ► We strongly recommend to back-up the parameterization Read_<date>_BACKUP with File – Export first.

Before the firmware can be updated, … ► … open the parameterization Read_<date>_WORK. ► Open the context menu of the former A r c h i v e A F B and Delete AFB.

Fig. 20: Delete the former instance of the A r c h i v e A F B

► As usual Transfer parameterization to device. ► After the reboot of the device reconnect with Connect….

To update the firmware … ► … switch to the Navigation view and select the node <device name>.

Fig. 21: Select the desired device

► In the Action panel click Firmware configuration.


► On tab Firmware select the latest Firmware source with […] and [Search updates].

Fig. 22: Select the path to the latest Firmware 03-00 (example)

The latest updates are shown in column New. Additionally new software modules are listed in the table installable modules.

► Importantly, add the new A r c h i v e A F B in the table installable modules by selecting the latest version 03-00.

Fig. 23: Add the new A r c h i v e A F B by selecting the latest version

► Optionally, you can add further installable modules in the same way. ► Update the firmware with [perform firmware change]. ► As usual, login and confirm to transfer the selected software to the device. ► Importantly, do not transfer a parameterization to the device by activating the following checkbox:

Fig. 24: Activate Do not use a parameterization …

► Start the update with [OK]. ► Confirm to deactivate the listed modules, in case this dialog is displayed.

The device runs with the latest firmware.


Now the parameterization needs to be converted to the latest SFB and AFB versions: ► Open the parameterization Read_<date>_WORK. ► On tab AFB configuration select for the Basic System the current version 03-00 by selecting the first entry

in the list.

Fig. 25: Update the Basic System to latest version 03-00

enSuite adopts this version 03-00 for most AFBs listed and AFBs that are part of the parameterization are displayed in a green font. New AFBs like A r c h i v e and P r i n t e r are added to the list.

Fig. 26: In enSuite 3.0 the corresponding AFB versions 03-00 are automatically selected

► Start the conversion with [Commit changes]. ► Confirm the dialog that summarizes the changes. The parameterization is converted. Incompatible data or AFBs are marked in red font in the Parameter tree.

( See note Accessing incompatible parameters, p. 12) ► Just to be sure, review the Output window for any indications regarding conversion problems. ► Add a new A r c h i v e A F B on tab AFB configuration by selecting the list entry Archive and clicking

[Add AFB]. ► Open the back-up parameterization Read_<date>_BACKUP that still contains the former Archive

definitions ► Go to the instance of the former archive <branch> – Archive – Archive groups. ► Open the context menu and Copy the definitions of the Archive groups.

Fig. 27: Copy the archive definitions of the former Archive (Read_<date>_BACKUP)


► Switch to the work parameterization Read_<date>_WORK and go to the instance of the newly added archive <branch> – Archive – Archive groups.

► Open the context menu and Paste the definitions to the Archive groups.

Fig. 28: Paste the former archive definitions to the new Archive (Read_<date>_WORK)

The former archive definitions are now available in the instance of the new A r c h i v e A F B . Save your changes and transfer the parameterization to the device.

If Archives are readout via Modbus, the import values need to be updated manually

If you readout the archive via Modbus protocol, all import values linked to the A r c h i v e A F B need to be reassigned manually. The reassignment is finished successfully, as soon as no more entries are displayed in red font below the node Modbus <x>.

Further Enhancements

Improving Modbus Lists The parameterization of the M o d b u s A F B is improved significantly in enSuite 3.0. While Modbus lists could become very nested and unwieldy in enSuite 2.x, the M o d b u s A F B is now based on the organizational structure of normal mode. The major modifications and enhancements in short:

• Modbus lists are available in normal mode and in expert mode accordingly.

In export mode additionally the communication mode, user rights and units can be parameterized.

• Parameters are organized in 3 tabs to keep the overview

Fig. 29: Paramerers organized in 3 tabs – example normal mode

− On tab Settings the communication settings are parameterized. (≙ in enSuite 2.x: subfolder Communication mode – Interface, tab All parameters)

− On tab Areas list the areal parameters are parameterized. (≙ in enSuite 2.x: subfolder Communication mode – <device> – <Register Areas> – <Area x:> Register Area, tab All parameters)

− On tab Register list the register lists plus details to single registers can be parameterized if applicable.


Fig. 30: Register list with register details (context-sensitive) – example Qm

(≙ 2 combined views of enSuite 2.x:

1. subfolder Communication mode – <device>, tab Register list 2. subfolder Communication mode – <device> – Register areas – <Area x:> Register Area – Registers – Register <x>, tab All parameters)

Communication lost to other devices when connected via Modbus TCP

In case the FC1 communicates with other devices via Modbus TCP, please check the communication every time the network of the FC1 is interrupted. An interrupt can f.i. be caused by a reboot after transferring a new parameterization to the FC1. Depending on the TCP driver used some devices do not reset the communication connection after an interrupt. If this is the case you need to reboot the other devices to re-establish the communication.

IP-Settings via enSuite (new feature) Formerly the FC1 Ethernet settings could be configured at the device only. Now, the Ethernet interface of the mainboard can also be parameterized in enSuite 3.0 (I/O boards – Board 0: CPU, section Ethernet I/F):

Fig. 31: Ethernet I/F settings of the device (new)

Parameters are critical for accessibility of the device

Make sure that the Ethernet settings match the settings of device. Otherwise the device can no longer be accessed via Ethernet – in that case the device can only be accessed via USB.


Network Service Bindings (for future use) Until now the enCore network services (MMS and trace services, connecting to remote operation channel) were configured automatically, plus only a binding to a single network interface was possible. As soon as the ESER4 board will be available, it is possible to assign different bindings for each service manually. Without an ESER4 board installed the section Network service bindings has no effect.

Fig. 32: Network Service Bindings (for future use)

FC1 - Updating from enSuite 2.x to 3 - Honeywell Elster example, in case Modbus is us ed the...

Documents

Transcript of FC1 - Updating from enSuite 2.x to 3 - Honeywell Elster example, in case Modbus is us ed the...