XWEB3000/5000 EVO OPERATING MANUAL (V.1.
TABLE OF CONTENTS 1. 2. 3. INTRODUCTION ....................................................................................................................................... 5 THE RECIPIENTS OF THIS MANUAL ..................................................................................................... 6 USING XWEB-EVO ................................................................................................................................... 6 3.1 INITIAL WIZARD PROCEDURE ....................
.5.5.3 3.5.5.4 3.5.5.5 3.5.6 4. 5. 6. Parameter map saving........................................................................................................ 91 Parameter map loading ...................................................................................................... 92 Export PARAMETERS MAP ............................................................................................... 92 DESKTOP SYSTEM LOGS .........................................................................
CAUTION: TO PREVENT FLAMES FROM DEVELOPING OR ELECTRIC SHOCK, AVOID ANY CONTACT BETWEEN THIS DEVICE AND RAIN OR WATER CAUTION: TO REDUCE THE RISK OF ELECTRIC SHOCK, DO NOT REMOVE THE COVER IT DOES NOT CONTAIN ANY PARTS THAT REQUIRE SERVICING BY THE USER ALWAYS HAVE QUALIFIED STAFF PERFORM THE PROCEDURES.
1. INTRODUCTION Congratulations for having purchased this product. XWEB-EVO represents one of the most advanced monitoring, control and supervision systems available on the market today. The user will benefit from a power tool, which is easy to use and highly customisable for all requirements. It uses the most advanced technology for displaying the web pages and is based on the Linux™ operating system which guarantees its efficiency and reliability.
2. THE RECIPIENTS OF THIS MANUAL The contents of this manual are intended for professional users, such as the XWEB-EVO installer and/or its end user. The configuration and usage procedures of the XWEB-EVO are an integral part of this manual. Users may be professionals such as energy-managers or supermarket directors.
System language. It represents the language that the system uses for the parts that do not refer to a user, thus to its language. For example, for alarm or system notifications. To specify your preference, select the language from the list and press "Next". This language is also used for the Admin user. Local keyboard. Indicate the configuration of the keyboard physically connected to the XWEB. This configuration is not linked to the configuration of your PC's keyboard.
e) Network setup. For the XWEB network interface configuration. Normally, these parameters are to be agreed with the network administrator, so it is advisable to contact him/her for guidance and support. - ‘Lan enable’: disable the check to use the XWEB with local interface only (monitor and keyboard). In this way, it will not be possible to access the server by means of the local network or internet. Disabling is not a common procedure: if in doubt, keep this box enabled.
- ‘2nd web-server port’: is the network port on which the web server is listening. The default port is number 80. However, for some network needs, it may be necessary to change the default port value (port 81 and 8080 may be the values normally used). - ‘Enable local DHCP Server’: it makes sense to enable this function only if you do not wish to connect the XWEB to a network but only to a PC, where the network interface does not specify an IP.
h) Email setup. The XWEBEVO is able to send emails, generally to notify updates on the status of alarms. To enable this function, it is necessary to enable the service by completing the configuration. The configuration parameters can be supplied by your internet provider or by your network administrator.
j) Printer setup The printer can be connected locally or use a network printer. To obtain a list of tested printers, go to www.dixell.com and visit the XWEB support section or click on the following link: http://www.emersonclimate.com/europe/ProductDocuments/DixellLiterature/PrintersXWEB.pdf Local printer Once you have selected the local printer, select the port that the printer is connected to through means of the Local printer list box and then select the correct print driver.
l) Wizard conclusion The first configuration procedure is now complete: press "apply" to apply the configuration and reboot the system. The following screen may appear while the system is rebooting. Wait a few minutes after rebooting to be able to access the login page. 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
3.2 ACCESS TO THE SYSTEM Access the system from your PC by entering the XWEBEVO IP in the browser address bar. With a direct local connection [screen, mouse and keyboard], this operation is not required, simply switch on the screen. The user will be directed to the "login" page. From which all users will consistently have access to the system's user interface. Enter Username and Password to access the system. If the entered details are correct the homepage is loaded, otherwise repeat the operation.
3.3 XWEB SYSTEM SETUP 3.3.1 INTRODUCTION In its configuration, the XWEB-EVO system requires connection to its interface of Modbus devices. Make sure that: 1. the controller network is suitably connected paying particular attention to the configuration of the device addresses, to avoid non-admitted duplications. 2. all instruments are properly powered. Create the list of all connected instruments.
The DESKTOPS and MENU menus can be accessed by clicking on the buttons on the right-hand side of the same page. For the DESKTOPS pages, navigation is carried out via the carousel from which the user can choose the desired page.
3.3.4 CONTROLLER CONFIGURATION The controller-device configuration phase allows for the association of each connected device with the system. For each device, the system will be able to represent and configure its attributes and functions. The system will, in relation to the selected device, only show the attributes (categories, alarms, inputs, etc..) typical of the device itself. To be able to modify the faulty configuration parameters, the acquisitions must be switched off.
3. Specify whether or not the system must run the search by controlling the silence time. The enabling of this parameter allows for the stopping of the search procedure should noise be detected on the line. If in doubt as to whether or not to enable this function, disable it. 4. Specify the Modbus range of addresses to be detected 5. Press "Start search" to run the operation. The search results may display the list of detected devices that can be added to the network configuration.
2. Run the Drag’n’Drop on the "Add Device(s)" area: 3. Specify the configuration parameters of the devices on the network. The correct execution of the procedure will update the left-hand side of the screen with the list of configured controllers. 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
To remove a device 1. Select the device you wish to remove from the network configuration 2. Run a drag’n’drop on the "Remove Device(s)" area. Attention: to correctly execute the drag, click on the dotted area 3. Confirm the removal C. CONFIGURATION OF THE DEVICES-GROUPS The user can assign controller devices to groups so as to order the configuration according to a functional diagram or physical positioning within the supermarket.
It is also possible to assign the devices to the groups directly using the "Device Find" procedure. D. RESOURCE CONFIGURATION OF DEVICES It is possible, for the devices already added to the controller network configuration, to customise their resources. For example, the variable name as well as other features. Select the "Device Resources" tab to access this feature. Customisation of device name.
Enabling of the variable for "DeviceView" page. The variable is inserted in the DeviceView page if the box corresponding to the same variable is enabled. By default, each variable is enabled in this context. Enabling of the Notify variable The variable is inserted in the snapshot table, in the instrument notifications. For example, as seen in the image below, the variable is inserted in "Row 3" of the table. All values in this table are relative to those displayed when the notification is sent.
- “Common Settings”: applicable to all instruments. For a copy of only the compatible parameters that can be detected on the destination device. Select the devices to which you wish to apply the copy of configuration parameters on the network and click OK. The ‘name’, ‘sampling’, ‘no-link time out’ and ‘clock syncro’ parameters, at this point, are all duplicated alongside all descriptions of the variables and their display parameters.
The configuration of a device can be imported into the Template gallery. These devices can then be setup using the “Add/Remove Devices” section as demonstrated in the image below 3.3.5 USER/BOOK CONFIGURATION The user configuration page allows for the configuring of the XWEB-EVO book. This book is unified in the system for all operations involving external users. Users are intended, for example, as those who have access to the web interface; users can also be those receiving alarm notifications.
Clicking on the profile list updates the section on the right-hand side of the screen. By accessing the "Profile Permissions" section, it is possible to browse and/or modify the profile attributes. for any modifications to be applied to the system, they must be confirmed by pressing "Save" in the profile list. Create/Delete profiles Click on "New" in the profile section to add a profile.
The user permissions enable him/her to perform a number of operations. Access to the desktops is configured in the Desktop section and the main desktop that is accessed immediately after login is set. 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
3.3.6 ALARM CONFIGURATION The alarm configuration is accessed from the MENUXWEB SYSTEM SETUPAlarms Management. Access to the page allows for the customisation of the alarm categories and notification parameters: The XWEB-EVO uses this information to detect the alarms from the controllers and notify their status to the users in the book. Principles of operation The XWEB-EVO detects the present controller alarms in an alarm-category.
List of controllers The list of configured controllers is always present on the left-hand side of the screen. Clicking on the lens as demonstrated below - selects the "Category Settings" tab which displays the list of all variables configured as alarms. The buttons are also present on the left-hand side of the window. 1. “Clone Alarm Settings” for copying between instruments of the same alarm-category settings. 2. “Save Configuration” to apply any modifications.
Category parameters: - Name: identifies the category itself; - Delay: stand-by time for the processing of the alarm, from when it is read by the controller network to when it is effectively considered an alarm: if the alarm is resolved before this time runs out, the source of the alarm is ignored. This parameter is useful for the delayed management of the "open door" status which comes from an I/O board: the variable is not an alarm but with the XWEB-EVO it can be used as if it were.
Some parameters must be set for each "Setting": - Setting Name: identifies the notification level - {166Notify on Start167}: enabled for the sending of new alarm notifications - Notify on End: enabled for the sending of alarm-over notifications - Send Single Notification: the enabling of this parameter invalidates the accumulation time. If the system detects two alarms simultaneously, the users will receive two separate notifications.
The HTML part is the format rendered by the browser. The text is better suited to automatic parser and is as follows. Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Alarm Report: XWEBEVO Xweb EVO system name|XWEB EVO system description START|18/10/2013 17:26|RS1-007 New_XR170Cxxxxx|Low Value Pb1 The text is common to all other email formats. 8. EMAIL IMG: the alarm notification is performed by means of the sending of a message, in which the body constitutes an image.
All email formats can be analysed by automatic robots examining the section "text/plain". Below is an example of an alarm email: Tab System Alarms Enable system alarms that must be managed by the system, with notification i.e. via email. The messages sent by the system are of the same type as those managed by "system messages" By selecting “Email” + “EMAIL INFO” for the sending, you select the extended email format demonstrated in the image below.
MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="---------EVO40DFF36D5A44ECBC" Return-Path: example@domain.com X-OriginalArrivalTime: 01 Oct 2013 15:38:57.0073 (UTC) FILETIME=[5774E210:01CEBEBC] -----------EVO40DFF36D5A44ECBC Content-Type: text/plain; charset="utf8" Content-Transfer-Encoding: 8bit IP:10.100.81.208 GATEWAY:10.100.81.1 EXTERNAL-IP:10.100.81.208 DNS1:10.100.80.20 DNS2: -----------EVO40DFF36D5A44ECBC Diminutives errors, of subject Acq OFF The acquisitions are stopped.
- List of alarms for User - Full configuration 3.3.7 STOP/START ACQUISITION The XWEB-EVO principally identifies two mutually exclusive statuses: 1. Acquisitions stopped. This status allows for the configuration of the basic machine parameters. For example, it provides the user with the necessary access to configure parameters relative to the system or to the controller network configuration. This status does not allow for monitoring or supervision.
Access MENUACQUISITIONS Stop Acquisition to stop the acquisitions. 3.3.8 SYSTEM VERSION/UPDATE Access the menu “XWEB System SetupSystem Update” to access the update control panel. This window displays all updates already applied, and it is possible to check if there are further updates present. Depending on the system configuration, there will be three keys for installing new updates: Repository. For remote installation via internet connection.
3.3.11 LAYOUT SETUP MODE Access the menu “XWEB System SetupLayout Setup Mode” to create customised desktops with graphic widgets made available by the system. The user populates the desktop with widgets via drag’n’drop from the palette accessed by pressing "Menu". The procedure requires the user to hold down the left key of the mouse over the desired widget, i.e. "image", and to then drag it onto the work area for positioning. Once the widget is in place, proceed with dimensioning and configuration.
Image Pie chart Gauge Thermometer Global Commands Mini Device View Device Variable 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
3.4 MENU TOOLS The XWEB-EVO allows for the use of different tools for device programmatic management. To access these tool pages, open MENU and select TOOLS as demonstrated below. Many of the functions in this menu require the use of a virtual machine JAVA. Refer to the last pages of this manual for certificate management ( “6.10 HOW TO MANAGE THE JAVA CERTIFICATES” ). 3.4.
The following image shows an example of the operational and configured scheduler The complete daily range (from 00:00 to 24:00) is shown at the base of the window. Each hour is marked with a vertical placeholder. Setting saving Access the menu item FileSave to save the configuration. Attention, once you save it is no longer possible to recover a previous version. Print scheduler configuration Access the menu item FilePrint to launch printing in local on your web-browser.
SCHEDULER Enabling For the unconditional enabling of the scheduler, access the menu FileScheduler Enabled. To completely disable the scheduler, access the menu File and untick any item enabling the same scheduler. A disabled scheduler is recognised by the grey class name and the "x" above the events, as demonstrated above. The scheduler may also be enabled and disabled from a digital input.
Fill in "Class Name" and select a type of device. Select all tools to be associated with the operations of the device class. For example, to send a command to the devices or to run other types of operations as described below. Creation/setting of command events to devices To send timed commands, access the menu EventsAdd Event to create a new event. Each event corresponds to the sending of a command on the controller network to one or more devices.
Activation Time: time the report is created. Marker colour: marker colour of the event on the scheduler (only for printer / ). Add Event to All Days: assignment of the event to all days created in the calendar. Printout Name: name of report used in the header (only for real time report/print). There are two types of created report: real time or archive. The first takes a "photo" of the situation regarding the tools at a certain time. As illustrated in the image below.
Not-extended: This format represents each device with a variable per controller This format represents each device with multiple variables per controller 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
Extended: refers to the representation of data with one column per variable. When reading the data in the column, refer to the number in the header list which identifies the variable. “Print copies” to print on local printer, configured on xweb. FAX for sending the report via fax configured on xweb. Email for forwarding via email, with report in email or as attachment. Creation/setting of system message events To send system messages, access the menu EventAdd System Event.
Creating/setting of events generating historical data Excel files The XWEB-EVO is able to create historical data excel files. There is a 48 hour limit from when the event first occurred. To configure this option, access the menu EventAdd Export Event. Select the class on which to connect to the event. Select the variables for the report.
Once configured, the Excel files will be created as: /-.XLS as per screenshot below. The format of the files is as demonstrated below, where each Excel worksheet is dedicated to a single device. Change/deletion of events Click on the event: the list of all events at that time configured will open, as demonstrated below. Once the event is selected, the list of possible actions appears, as demonstrated below. 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
If you click and hold on an event, it is also possible to perform vertical class movements for a display adjustment or movements on the time axis of the event itself. In the latter case, you can see the new "Activation Time" on the applet title, as demonstrated below. Using the calendar in scheduler By default, for all calendar days, the system uses the "type of day" (Default Day). When configuring the scheduler for the first time, this day is that proposed by the system for configuration.
To create a new (type of) day, access the menu “Edit DaysNew day definition”. The system requests the configuration of the following image window parameters It is necessary to indicate the name of the (type of) day, e.g. "weekend", and give it a colour for recognition. The colour will be important for visual recognition on the calendar. The "Enabled" parameter indicates whether the events configured on the day are active.
To configure the previously created (type of) day, access the menu Days and select the day. Note that the classes are common to all types of day. But that each day defines its specific events. Display options Access the menu “WindowsShow Key” to show the key Access the menu “WindowsShow Calendar” to show the calendar. Access the menu “WindowsShow Logs” to show the scheduler logs, for the list of sent commands and other actions performed.
3.4.2 DEVICE LINE TEST Click on menu “TOOLSDevices Line Test” to access the test page of the communication with the setup devices. Access to the window shows the statistics table on the communication with the configured tools. Each device has been represented in columns: Device: device name Success(%): successful communication total percentage Time Out(%): errors for Time Out percentage.
3.4.3 PERFORMANCE MANAGER Performance Manager (or Performance Meter) is a tool for the analysis and verification of the correct dimensioning of the plant, utility control, operating statistics. To execute this procedure, configure a device class and finalise the calculation indicating the time range on which it is to be applied.
the above example, if you were to set this value at 1: at a graphic level there will be up to 48 possible transactions of various colours low/ok/high, assuming that the data is all within a different range. While, if the average value is 4, there will be a maximum of 12 colour transactions (averages at 4 hours of data). This parameter has the function of avoiding out-of-range temporary values, which do not affect the calculation or the graphic representation.
“PerformanceData ScreenShot” 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
“PerformanceExport To Text File” 3.4.4 COMPRESSOR RACK OPTIMISER (C.R.O., ONLY XWEB5000) C.R.O. works with a proprietary algorithm developed by Dixell that combines the complexity of the cooling system with the simplicity of the parameters that the user must set at a program level. It works on two basic parameters to guarantee the best possible adjustment of the refrigerator: the suction pressure of the compressor plant (detected by a series XC1000D ver.1.
Utility Configuration Create a new class of utilities to use the C.R.O.. The data required to operate the project is extracted from these controllers. Open the "Class" menu and create a class including the utilities of interest. Utilities are those with the saturation pressure set-point in common. Use the Create/Edit/Delete menu items to modify the utility classes. Each utility class can and must be assigned to one of the CRO engines.
- Worst case threshold: allows for the defining of the intervention threshold for the C.R.P. algorithm (in %) - Neutral zone: specifies an oscillation band (centred on the percentage of the worst possible case) inside which the algorithm does not intervene. - Initial value: initial set-point value. The value can be an estimate: in time, the set-point value sent to the plant will change -according to the algorithm (typically in °C). - Min. and Max.
Should the real percentage of the worst possible case be below that set (except the neutral zone), the formula used for the new set-point is: RLS gain Set new Set old % 1000 % (calculated percentage value) - (percentage set for the worst possible case) RLS gain release-gain parameter value And vice-versa, should it be above the set percentage (except the neutral zone), the formula used for the new set-point is: CALL gain Set new Set old % 1000 % (calculate
For each device, in addition to its name, the amount of cold call is also indicated. "Ch." corresponds to the compressor start-ups, while "On/Off" corresponds to the call of the eventual electronic expansion valve. These values are used to calculate the cold call percentage of the algorithm. Each line corresponds to a different moment in which the C.R.O. algorithm has sent a new set-point to the plant: this set-point is shown on the right, below the "Set" column.
3.4.5 DEW POINT MANAGEMENT (SOLO XWEB5000) The Dew-Point managing concept enables the XWEB-EVO to act on the adjustment of the anti-sweat heaters in order to reduce their electricity consumption. The XWEB-EVO acts on the XM600 controllers, to which the Dew-point temperature set-point is sent. Condensation builds up on the controlled bench window surrounding the system. These controllers are defined in the configuration of a class. Each engine can manage a class.
Class Name: class name used in the configuration of the dew-point engine. Typology Filter: filter allowing for the display of only the chosen device list. For each device represented in the list, it is defined: - Check enabled: defines whether or not the device is part of the class - Set Dew Variable: defines the variable towards which the dew-point value will be sent. Attention: if the Set Dew Point variable is not visible in the list, it has probably been disabled by the tool advances.
- Execution Interval: cycle time for sending the dew-point set (in minutes) - Destination Class: class of devices receiving the dew-point set value - Control Device: device for calculating the dew-point set value. Should the XH50/55P box be selected, the calculation is performed by the same device that must be specified with field “XH50/55P Device”. This controller is connected to a temperature and humidity probe in the room.
The possible errors that may occur when sending the set to the central device include: "Timeout" => No response from device. "Exception" => Value not accepted by device. "Unknown" => Unknown error. "Success" => Value sent with success. The device name/address is shown in the "device" column. 3.4.6 XWEB5000 SUPERVISOR SYSTEM (ONLY XWEB5000) The supervision concept significantly expands the possibility of intervention by the XWEB5000 on system management.
SDC, ELS and ODC Each project consists of at least 3 distinct blocks: SDC (source device class) is the set of controllers whose variables (probe values, operating state, etc...) constitute the inputs for the supervision project. ELS (event logic supervisor) is the functional block that combines the input performed by the SDC with the output, that is to say, the sending of the commands to the supervision project controllers.
The ENA status can be activated with a delay, set with parameter DELAY. The above assumed logic continues to always be met and returns the TRUE value. The block status, from the moment in which the logic is met at the end of the delay time, assumes the DLY value. The ENA status can be maintained with a maximum time set with parameter DURATION. After this time, the block status switches from ENA to DUR. ODC BLOCK Choose the "Create" menu. We will create an ODC that sends the reduced set-point command.
This block can be configured with multiple inputs, such as SDC and/or STE blocks. A logic group can be associated with each of these: AND/OR/DIS. The rule that is executed is (∑And | ∑Or) & ∑!Dis where And=AND logic of all parameters in AND; Or=OR logic of all parameters in OR; Dis=NOT logic of all parameters in DIS.
Complete project The complete project is displayed by means of the macroblocks: Press "Note" on all blocks to view what is written during the block realisation phase. Press "On/Off" on ELM block to enable/disable the block execution. Right click with the mouse on all blocks to modify the selected block. Or duplicate it. STE BLOCK This logic block allows for the management of the timed events. It is a programmable filter, the status of which can be added to the project and linked to the ELS block.
For the removal or modification of the band times, move the red/green triangles (red=band end, green=band start) or click with the mouse on the triangle to open the editing menu of the band itself. The bands created for the various STE blocks can vary by calendar. It is possible to create time bands linked to a "type of day" and then associate this to the calendar. Default Day holiday The above images show that the bands differ between "default Day" and "holiday".
EMM BLOCK The EMM block can receive alarms or notifications With the EMM block you can receive alarms or notifications regarding the status of the active supervising programs. The list of receivers depends on the receiver book filled in the ALARM configuration. The message text is the content of the fax/mail that you intend to send. The EMM also report information regarding the status of the controller that will usually correspond to the controller modified by the ODC action or the SDC enabling condition.
PROJECT SIMULATION Once the project is realised, it can be partially or totally simulated before being considered definitive. There are 3 types of simulation: Local test, on-field Simulation and Runtime mode. LOCAL TEST This mode is useful when a rough idea of what happens when varying the status of the inputs is necessary. Access the menu "Tools" and then "Local test".
VISUAL FEEDBACK Once the supervision program is running, it provides the user with important information in graphic form. The following table summarises the possible work situations. Logic block SDC value/colour ENA/green DIS/grey DLY/grey green DUR/blue STE ELS ODC ODS ENA/green DIS/grey red background green background SENT/yellow ??? Act NotAct Set NEQ 3.4.
Restore The procedure allows for the recovering of data in the XWEB memory. The user must select the backup data source to be restored: The “Evo system backup disk” allows for the uploading of a backup previously run in the XWEB memory; The “Usb connected to evo” enables the recovery of data from the USB device and “Upload backup” allows for the remote uploading of a backup with the browser. Once the data source has been selected, select the data to be recovered from "Section".
enabling of the service. Checking this box indicates that the service is enabled. The time of file creation/update. In HH:MM format The time interval filter between the exported samples. In MM format The period for which the service will extrapolate the log. . The source data is always taken from the "main history" archives, i.e. the source data is the sampling time, as indicated in the device configuration (usually 15 minutes).
The user must set the period name and interval as well as the period. 3.5 DESKTOPS The desktops represent the main tasks that the XWE-EVO provides its users. 3.5.1 DESKTOP OVERVIEW The "Overview" desktop is the desktop that appears to the user just after login. This desktop provides the user with an overview of the status of the network tools and allows for the execution of procedures such as sending global commands (e.g.
Move the mouse cursor over the device of interest. A pop-up opens providing the device name and other information. Click on the device box to open the "Device View" desktop which provides the complete details of the device of interest. Active alarms table The "Active Alarms" section represents the list of active alarms, in real time, relating to the configured controls. The list of alarms can use filters, visible and configurable, on the first line of the table.
2. the default time that will appear to the user during printing The user who intends to print can also alter the time during the printing operation. 3. the type of output - download browser: for opening the file in the browser. The browser must have a plug-in for PDF files - print on XWEB Default Printer: for printing using the configured printer in the menuxweb system setupSystem SetupPrinters - send Email to: for sending emails.
The output type represents a configuration summary of the report. Global Command Configuration Global Command Execution 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
Configuration for "HACCP Print" action. 3.5.2 DESKTOP DEVICE VIEW The "Device View" desktop provides the user with all the resources monitored by the selected device. All variables monitored by the field will be listed, including the analogue variables. Set-points and analogue I/O: probe values or from analogue outputs (e.g. output 0-20mA) digital variables. Machine statuses, digital I/O, alarms. For example, "stand-by" status, digital input and high temperature alarm. 3.5.2.
Selecting a device displays: the variables grouped by group of pertinence (Analogue/Status/Alarm etc..). section "deviceView"; the graph for the device. section "dataChart"; the list of available commands per device. section "commandButtons"; list of device parameters. section "parProg" All page values and relative graphs are updated in real time (on polling time). 3.5.2.
Complete The status is shown in blue variables only. Reduced for the digital variables, and in red for the alarm In full view mode, it is possible to select or deselect the variables. The selection of each value allows it to be included in the various page elements, such as in the graph shown below. 3.5.2.3 MODIFICATION OF SET-POINT A set-point can be quickly changed by clicking on its value. The box then goes into edit mode, as demonstrated below.
Set-point change successful Set-point change with error To perform this operation, the page must be in full view mode. 3.5.2.4 START FAST ACQUISITION MODEM (FSM) The FSM mode aims to perform a high speed selective monitoring of the resources for a set time limited to 10 minutes. This type of monitoring allows the user to run the controller debug and/or of its application, as if the other devices were "disconnected" from the tool network.
3.5.2.5 SENDING COMMANDS TO THE DEVICE Commands can be manually sent to the selected device, such as "Device OFF", "Device ON", "Active Defrost", etc., via the "Single view" window. To send the command, press the button as demonstrated below: Confirmation will be requested after which the user is informed whether or not the command was successfully sent. 3.5.2.
IDENTIFICATION OF THE MINIMUM AND MAXIMUM VALUES IN THE CHARTING PERIOD They are graphically marked with the coloured dots. The value and date of each of these is also shown. GRAPH OPTIONS Click on the wrench icon to access the menu: Settings: from here, it is possible to change the view interval of the graph itself, and show/hide the minimum/maximum values as well as the background colours Values: to modify the colour of the graph variables 3.5.2.
Load: loads the parameter map from a previously saved backup. This loads the map from file or from the XWEB-EVO Export: to save a ZIP containing the selected parameter map in CSV, PDF, XLS format on PC; or a BIN file compatible with WIZMATE 3.5.3 CHART DESKTOP The "Chart" desktop allows the user to create a graph with the variables monitored by the XWEB. On accessing the desktop for the first time, the window will appear empty.
TAB “SETTINGS” In this window choose between Chart Source - Main: this option must be enabled if you wish to create a graph using historical data dating back more than two days - Circular: these archives provide records at the maximum speed on the polling round. But are limited to the last two days only. Choose this option if you wish to debug the system from an alarm notification recently received Layout - Show min./max.
Interval Select the time range to be charted. If the “enable real time” option is disabled, additional options will appear including "last 24/48 hours; last week; today; yesterday; from/to". The range available will depend on the maximum duration of the sampling TAB VALUES In this window, choose the variables that will form the list of those to be used to create a graph. The variable may relate to any tool. From the same, choose the representation colour of each variable.
3.5.3.2 READING OF GRAPH The area of the graph is divided into the following sections: A) Axis area (blue): the variables are grouped by axis, for example all temperatures in °C will have the adequate axis and consumptions in Watt will also have an axis. B) Analogue variable graph area (green). All analogue variables, even if relating to different controllers, can be viewed on the same area. C) Digital variable graph area (purple).
3.5.3.4 ZOOMING-IN ON AREA To zoom-in on an area of the graph, click and hold the mouse on a point and drag until the desired area to be zoomed-in on is created. 3.5.3.5 ZOOMING-IN ON AREA OF OVERVIEW GRAPH To zoom-in on an area of the overview graph, click and hold the mouse on the graph and drag to select the desired area. 3.5.3.6 DATA EXPORT The graph data can be exported in Excel(R) format. To access this procedure, press "Export" on the configuration window of the graph.
A dialog box appears where the user must set the interval between samples Upon confirmation by clicking "Ok", the system saves an Excel file on the user's PC. The content of the file will be similar to that of the following image: 1592010880 XWEB3000_5000 EVO OPR GB r1.0 2014.11.
3.5.4 ALARMS DESKTOP The "Alarms" desktop enables the user to visualise the list of all controller network alarms detected by the system. On the initial access, the alarm list appears with the following default that can be subsequently changed by the user: 3.5.4.1 ALARM DISPLAY FILTER The user may use filters to - Level. To visualise only the alarms notified to a specific level. For example ‘Service’; - Alarm-category. To visualise only the alarms configured with a given category.
- Code: univocal alarm ID code. This code corresponds to a precise alarm detected at a precise moment. - Name: alarm name - Category: alarm category - Start: date/time when the system detected the alarm. The time delay that may have been configured for managing the same alarm is not considered. - End: date/time when the system detected the alarm reset. Information available only for the resetting of alarms: or ACTIVE if still active. - Duration: duration of alarm.
3.5.4.3 DISPLAY ALARM DETAILS By clicking on an alarm, the page is updated with new detailed information on the alarm that has just been selected. The "Alarm Detail" section containing the list of notes and the list of users notified of the alarm is updated. 3.5.4.4 READ/WRITE ALARM NOTES Notes can be added by clicking on "New note:" from the detail of the alarm notes and, in particular, from the "Notes" section. To save the note, click on the grey area of the same line.
3.5.5 DESKTOP PARAMETERS The "Parameters" desktop allows the user to read and modify the parameters of the controllers connected to the device network. 3.5.5.1 PARAMETER READING Select the device of interest and possibly the specific group of interest of the parameters to be read. Select "Read" from the menu on the right-hand side and run "Execute". The page will be updated with the parameter list. Loading depends on the number of parameters and the connection speed.
The same file can be reused at a later stage in this or in another XWEB-EVO. Attention: this file cannot be used in previous XWEB versions. 3.5.5.4 PARAMETER MAP LOADING The parameter map files generated using the above-described procedure can be loaded by selecting "Load" from the action menu and pressing "Execute". The XWEB-EVO will request where to load the parameters: from the XWEB-EVO or from a file on your PC. Attention: only files saved with the XWEB-EVO can be loaded. 3.5.5.
3.5.6 DESKTOP SYSTEM LOGS The "System Logs" desktop enables the user to visualise a list of events describing the most significant actions executed by the system and by the users accessing it. On initial access, the system shows the list of all the events that have taken place in the last three days. The user can choose to apply different filters on the display.
4. TRADEMARKS Consider It Solved and Intelligent Store are trademarks and Emerson Climate Technologies and the Emerson Climate Technologies logo are service marks and trademarks of Emerson Electric Co. Windows and Internet Explorer are registered trademarks of Microsoft Corporation in the United States and other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Google and Google-Chrome are a registered trademark of Google Inc.
Example: Figure 1 If no reply is received, your PC is unable to communicate with the XWEB-EVO. Check the cables once again or contact your network administrator. Attention, if a reply is received, it may not come from the XWEB-EVO: it may come from another device on the network. Also in this case, should you continue to have difficulties accessing via your browser, contact your network administrator for advice. 6.
Below, the procedure for emptying the JAVA 1.6 cache: click on Start button , click on Control Panel and then click on the JAVA icon. Click on “Settings” and “Delete Files...” (see figure below): Figure 3 6.5 SOMEONE HAS RECEIVED A CONFLICTING MESSAGE ON THE IP ADDRESS This may mean that the XWEB-EVO is using an IP address that is also being engaged by another network resource. We recommend changing the XWB-EVO IP with a new, free address.
1. The first type of re-send is carried out during the lifespan of the level, where the emails are always re-sent to the same recipients. The parameters affecting this type of re-send are "Resend Time" and "Resend life time", in the level settings. 2. the second type of re-send is carried out through means of an increasing notification level and the consequent notification being sent to a new group of recipients.
“Your browser understands the
addresses are those configured on the tool and are relative to all configured tools-lines: the following example demonstrates how indicating address=2 returns two controllers (one for RS1 and one for RS2). Example: http://10.100.81.208/cgi-bin/rt_format.cgi?DEVLST=2|3|247
NOTES ______________________________________________________________________________________ ______________________________________________________________________________________ ______________________________________________________________________________________ ______________________________________________________________________________________ ______________________________________________________________________________________ __________________________________________________________________
