Posts Tagged ‘Wizard’

Managing your meters, providing the values – the Metering Point Administration

Thursday, March 5th, 2015

MeteringPointAdministrationDo you want to establish energy data management at your plant? You´re using a mixture of meters with just a display and no I/Os etc. connected to zenon? You want to have an overview of the meters and metering points at your site? zenon´s new Metering Point Administration might be the perfect tool for you.

The Metering Point Administration allows you to maintain a list of metering points and meters, stored in an SQL database. You are provided with all the required properties (type, manufacturer, serial number, equipment model, etc.) to easily group the list as you wish and find what you are looking for. By using the same database structure as the Industrial Maintenance Manager (IMM) you can even define maintenance tasks for your meters.

Every metering point provides values to zenon. Absolute values read from the metering points (automatically or manually) can be converted into relative values and be automatically stored in archives. This conversion considers the exchange of meters which would normally lead to negative relative values and thus to incorrect reports. If, for whatever reason, there are still incorrect values in the archives, the metering point administration offers a convenient way to modify them. The archives filled by the Metering Point Administration work perfectly with the zenon Analyzer to provide all different kinds reports, including OEE and EDMS reports.

How to adapt a VSTA-Form to appear as a VSTA-Wizard in the Wizard dialog (VB.Net)

Wednesday, May 16th, 2012

Introduction Although most .Net solution are developed using c#, in some cases porting existing old code (from vba) to VB.Net might be more efficient than starting from scratch in c#. This blog entry explains which methods and functions are to be implemented in order to have a VB.Net Wizard displayed in the zenon Wizard dialog which pops up when creating a new project. Similar, yet different in small details

cialis no prescription

compared to the c# scenario. Integrating VSTA-Code into the wizard dialog In order for VSTA-C ode to be available in the wizard dialog the automation code needs to be contained (implemented) into a Windows-Form. Additionally the Form-Class needs to

popular pills online

implement the following set of static functions (all without parameters): Public Shared Function GetWizardName() As String Return the name of the wizard, displayed as “Name of the wizard” in the wizard dialog. Public Shared Function GetWizardInfo()

purchase viagra

As String Return a description of the wizard, shown as “A more detailed description of the wizard.” in the wizard dialog. Public Shared Function GetWizardCategory() As String Returns the category of the wizard and is displayed as “Wizard category” in the wizard dialog. Note: An existing category can be used here. And a VSTA and a VBA wizard can reside in the same category. Public Shared Function IsZenOnWizard() As Boolean This function determines whether the wizard should appear in the dialog. It offers the possibility to stop a wizard from appearing without having to delete all functions or removing it from the Addin. Public Shared Function GetWizardVersion() As Integer This function returns the version number of the wizard, indicated next to the wizard information. Public Sub StartWizard() This method is called when the wizard has been selected in the wizard dialog and confirmed with “OK”. NOTE: It’s not allowed to have any functions with the same name inside of the wizard class, not even if their return type of parameter count is different from the “Wizard-Functions”.

How to adapt a VSTA-Form to appear as a VSTA-Wizard in the Wizard dialog (C#)

Thursday, March 1st, 2012

Introduction

In average day working with the zenon Editor quite a few actions are required for each project. Actions like creating a default set of users, common drivers, default templates, etc. can be time consuming. Obviously these actions can be replaced and automated by use of VSTA-code in

cialis without prescription

the editor. But if

price of viagra

these actions are to be performed for each new project, it would be more efficient if the actions could be triggered in a more comfortable way: By use of the integrated Wizard dialog which pops up when creating a new project in zenon.

Integrating VSTA-Code into the wizard dialog

In order for VSTA-Code to be available in the wizard dialog the automation code

cheap viagra

needs to be contained (implemented) into a Windows-Form. Additionally the Form needs to implement the following set of static functions (all without parameters):

static public string GetWizardName ()
Return the name of the wizard, displayed as “Name of the wizard” in the wizard dialog.

static public string GetWizardInfo ()
Return a description of the wizard, shown as “A more detailed description of the wizard.” in the wizard dialog.

static public string GetWizardCategory ()
Returns the category of the wizard, shown as “Wizard category” in the wizard dialog.
Note: An existing category can be used here. And a VSTA and a VBA wizard can reside in the same category.

static public bool IsZenOnWizard ()
This function determines whether the wizard should appear in the dialog. It offers the possibility to stop a wizard from appearing without having to delete all functions or removing it from the Addin.

static public int GetWizardVersion ()
This function returns the version number of the wizard, indicated next to the wizard information.

NOTE: It’s not allowed to have any functions with the same name inside of the wizard class, not even if their return type of parameter count is different from the “Wizard-Functions”. If all functions are correctly implemented and the Addin has been successfully compiled, the Form will appear in the wizard dialog.