Schneider Electric Telecontrol

Transcription

1 Release notes Product name: Xflow Version number: Language: EN Date: 6th February, 2014 Written by: Checked by: Schneider Electric Telecontrol Schneider Electric Telecontrol 1

2 Summary 1. Introduction Warning Description of the version Bug tracking list ALXF Changed value are not always displayed after value modification RAS_TIMEOUT is not updated in table if badly configured More about RAS_TIMEOUT parameter Synoptic: String variables with empty values are not correctly displayed on synoptic Function "iswithin" does not return expected result Details displayed in French for when you add chart from synoptic Straton Cycle time is always displayed at 100 even if cycle time value is different Data &Time is partially displayed in the chart Values are not refreshed on access direct pages X axis on graphics: sometimes it's very ugly and unreadable Display of a curve: date and time on the X axis are badly displayed sometime Bad string information on field "type" of alarm "system" Case : Xflow doesn't always record data with a period at 1 seconde Failed to send a SMS with the new 3G modem Performance issues on some pages : dashboard and files Reservation module: does not support correctly periodic reservation Web browsing impossible when napbus is "overused" such as "real time variable" with Kervisu OPC OPC tags list is built very slowly Crash during the startup while xflow is making the list of OPC tags OPC OPC variables were refreshed very slowly on distant server Inhibition of alarms doesn't work in all cases : We never saw "back to normal" status

3 1. Introduction Document scope This document describes the Xflow version Application field Apply to any version Comments The version is available in factory where it replaces version EXCEPT for AA and BA applications 2. Warning N/A 3. Description of the version The version fixes some issues. Those issues are identified by a Bug tracker ID. 4. Bug tracking list ALXF Changed value are not always displayed after value modification Here is the description of the problem from the customer: " Ce bug n'est pas reproductible à 100%, mais il arrive très fréquemment Par l'interface web, si l'utilisateur change une valeur et clique sur "Modify", pour autant la nouvelle valeur n'est pas transmisse au Xflow. Dans la pièce jointe en exemple, on a une valeur initiale de 50%. On modifie la valeur à 30% + clique sur "Modify" La valeur 30% est bien affiché par le web, mais la sortie physique est toujours la même. Si on clique sur "refresh this page", on s'aperçoit que c'est finalement toujours 50% qui est affiché. Le problème est le même sur une sortie Digitale. Le test a été effectué avec une carte 14ADIO sur un irio." Actually, there is absolutely no way to reproduce this issue, and it has never been reported by anyone in any situation. 3

4 RAS_TIMEOUT is not updated in table if badly configured «If you set a bad value for this parameter (15 < value < 1440), then default value 15 or 1440 will be used. BUT the value in the SYSTEM table is not updated and you still see what you set in the table.» This parameter is now updated in the SYSTEM table ONLY when this parameter is checked by the RAS module that is each time the module needs the parameter to initiate connection. RAS feature is limited to irio (Not available on PC) More about RAS_TIMEOUT parameter Have a look at release note of version Synoptic: String variables with empty values are not correctly displayed on synoptic With irio / XFlow PC in version 4.0.1: I have a String variable with an empty value (a) This variable is displayed on a synoptic In edition mode this variable is correctly displayed with an empty value (b) In visualization mode this variable is not correctly displayed: it's display with 8.00 value!!! (c) (a) (b) 4

5 (c) 5

6 Function "iswithin" does not return expected result «As documented iswithin must return 0 or 1 in function of parameter. For example: iswithin(var,0,100) return 0 if var is not between 0 and 100 else return 1. Since version 2.4.3, included version the result doesn't change, the function return always the same result.» Details displayed in French for when you add chart from synoptic «Details Displayed in French for when you add chart from synoptic. Enclosed attachment.» 6

7 Straton Cycle time is always displayed at 100 even if cycle time value is different «La modification du temps de cycle Straton par la page est bien pris en compte mais l'affichage qui est retourné est toujours à la valeur 100. Dans la base, dans table systeme, T5_CYCLE est correcte.» 7

8 Data &Time is partially displayed in the chart «year in Data & seconds in Time are truncated in the chart for the last period.enclosed screen shot for reference.» 8

9 Values are not refreshed on access direct pages «Il peut arriver qu'au bout d'un certain temps de fonctionnement de Xflow, sans reset, lorsque l'on demande les variables en accès direct elle ne sont pas rafraichies, si l'on fait un reset de l'appareil, cela résout le problème. Vérifié dernièrement sur une version et à priori sur une version 2.x (officielle, non officielle).» This problem doesn t occurred anymore. 9

10 X axis on graphics: sometimes it's very ugly and unreadable «Sometime when a graph is displayed, the dates are all scrambled and we can't read them. See attached picture» Display of a curve: date and time on the X axis are badly displayed sometime «With that configuration, the legend is not well displayed. See picture.» 10

11 Bad string information on field "type" of alarm "system" «In field type of alarm "system" the name is "Failure Mode" instead of "Modem failure" in English web interface version.» Case : Xflow doesn't always record data with a period at 1 seconde «Air Liquide has reported that they have seen a problem when the record period file is 1 sec. Sometimes, some records are missing. We have reproduced the problem on an irio with version (for Air Liquide) and standard version » Data are now well recorded every second during few hours. (tested with history files with 6 variables from a MAD) Failed to send a SMS with the new 3G modem «[Problem on customer site: EDF EN] Everything is in the title: with the PH8/3G modem, Xflow failed to send a SMS. We are missing logs files here to progress, it could be useful. The problem is: the initial configuration has a resource with a flag the "flow control off" > When used with version 4, Xflow configure the modem with flow control but the serial port with no flow control. Or something like that. More information will be a good thing.» This issue cannot occur anymore: if resource parameters (RS232 flow off for example) is not OK in a configuration then this parameter is corrected after an Xflow reset Performance issues on some pages : dashboard and files. «[Problem on customer site: EDF EN.] Between version 2.4 and 4, there is 2 to 3 seconds more to fetch and display a dashboard or the list of files. This is visible when you have "many" dashboard or files, not in the case of a basic configuration with only 1 dashboard for example. The problem is the location of the filter by id in the XML request: we all know, at different level that it MUST be at the end of the request, not the beginning, so the server can filter directly when issuing g the request. In the other case it does something like "I fetch everything then I filter" The solution if to move the <id><?param.totoiid?></id> at the end of the request..» 11

12 Reservation module: does not support correctly periodic reservation «If the customer try to configure a periodic reservation for each week, the first occurrence is done and after switch to the next month instead of next week.» It works fine for weekly, monthly and daily periodic reservations Web browsing impossible when napbus is "overused" such as "real time variable" with Kervisu «[Problem on customer site: EDF EN] Kervisu is connected to the irio and is getting some variables through its "real time variable" feature. When doing this it's impossible to use a web browser to navigate on the web pages. It looks like that when the client's SCADA is connected to the irio to pool variables, we have the same effect: no web is possible.» OPC OPC tags list is built very slowly «Affaire Voltalia - La Faye XFlow est paramétré de manière à interroger des variables réparties sur 2 serveurs OPC différents. Dans le cas de cette affaire il faut plus de 20 minutes avant d'avoir un fonctionnement normal. Pendant ce temps il n'y a plus aucun rafraichissement sur les périphériques OPC (pas de trames émises). Le premier serveur Vestas est installé sur le même PC que XFlow (ici un XLRIO). Le second (IFM mesures vibratoires) est installé sur un autre PC du même réseau local. Le Debug sur site à montré que l'identification des tags arrive au cout par cout. 1 ou 2 puis 10 puis 1 toutes les x longues secondes.» Crash during the startup while xflow is making the list of OPC tags «Crash during the startup while xflow is making the list of OPC tags. Peut-être une piste pour le Crash. J'ai voulu mettre un site à jour avec les 1ere modifications OPC => Impossible Crash systématique lors de la création des Tags au démarrage de XFlow. Beaucoup sont créés mais dans le tas après plusieurs secondes BOUM... (Cf Debug joint). En faisant la manip suivante j'ai pu lancer XFlow. - Laisser un seul périphérique OPC déverrouillé (ici 5 dans la config) - Lancer XFlow, le debug montre bien la création des Tags + Refresh en parallèle. - Lorsqu'on est sur que tous les Tags sont créés, on déverrouille le 2eme périph OPC. 12

13 - etc...» OPC OPC variables were refreshed very slowly on distant server «On constate que le cycle de rafraichissement des variables est très, très long (de l'ordre de plusieurs minutes). Au niveau périphérique le compteur de trames émises ne bouge pratiquement pas. Sur l'ensembles des tags déclarés j'ai même l'impression que certains ne sont jamais interrogés.» Inhibition of alarms doesn't work in all cases : We never saw "back to normal" status «This is a regression revealed with version : - not present with version problem exists with problem exists with problem exists with all versions 4, from to The issue has been detected by customer LCDV on site on week 7 of It was initially detected by P&EC during year 2008/2009, we fixed it (no trace of it in SVN, it was BEFORE we add Xflow in SVN). The first official version with the fix is » 13