Xflow – release note for version 2.4.

Xflow : release note

Xflow V 2.4.2

September 25, 2012

1/19
Xflow – release note for version 2.4.2

1. Document version ............................................................................................................................ 3

2. Document scope .............................................................................................................................. 3

3. Application field ................................................................................................................................ 3

4. Comments about problems tracking ................................................................................................ 3

4.1. Identification of problems ......................................................................................................... 3

4.2. Summary ................................................................................................................................. 3

5. The case of the RAS connection ...................................................................................................... 4

6. Main objectives of this version ......................................................................................................... 4

7. What’s new in this version? .............................................................................................................. 4

7.1. Modem initialization, configuration and feed back improvement............................................. 4

7.2. Various evolutions ................................................................................................................. 13

8. What’s corrected in this version? ................................................................................................... 14

8.1. Device selection mode .......................................................................................................... 14

8.2. Communications / Modems ................................................................................................... 15

8.3. Files management ................................................................................................................. 15

8.4. Alarms management ............................................................................................................. 16

8.5. OPC DA client [not available on the iRio] .............................................................................. 17

8.6. Various corrections ................................................................................................................ 18

2/19
Xflow – release note for version 2.4.2

1. Document version

Date Révision Auteur Commentaire(s)

nd
2 revision before broadcasting. Fixing
Jully 23th, 2012 02 Régis Martin
typo.
nd st
Jully 2 , 2012 01 Patrice Laporte 1 revision before broadcasting

April 24th, 2012 00 Olivier Jullien Creation of the document

2. Document scope
This document is a release note: it talks about what’s new and what’s corrected in the version 2.4.2 of
Xflow.

3. Application field
This version is available for iRIO Remote Terminal Unit and for “desktop PC” or industrial PC box
platforms.

4. Comments about problems tracking

4.1. Identification of problems
All the Xflow modification requirements or issues detected internally or by the end users are notified in
a Telecontrol tracking tool dedicated to the engineering team (Mantis Bug Tracker). In this document,
evolutions or modifications / corrections notified in Telecontrol’s tracking system are referenced as
“BT-XXXX”.

Every customers’ problem that are handled by Telecontrol’s support team are tracked in a CRM,
internally called Vantive : in this document, that kind of problem are referenced as “VC-XXXX”

Air Liquide has its own tracking system : in this document, evolutions or modifications / corrections
notified in Air Liquide’s tracking system are referenced as “ALXF-XXXX”.

4.2. Summary

BT-XXXX : problems tracked in the engineering team tracking tool. BT stands for BugTracker

VC-XXXX : problems tracked in Telecontrol CRM. VC stands for Vantive Case

ALXF-XXXX : problems tracked in Air Liquide tracking tool.

3/19
Xflow – release note for version 2.4.2

5. The case of the RAS connection

RAS (Remote Access Service) is only available on the iRio. That is it's not applicable to Xflow on PC
or XLRIO.

6. Main objectives of this version

Many goals with that version:

Improve modem initialization, particularly GSM/GPRS modem

Improve RAS connection management

improve quality by continually fixing bugs

7. What’s new in this version?

7.1. Modem initialization, configuration and feed back
improvement

7.1.1. Initialization of the modem: general description

The initialization of the modem (PSTN, GSM or RAS) is improved in various ways.

First of all, the modem is first detected and identified. Detection means Xflow tries to fid a modem on
the serial link, whatever speed is configured by the user. If found, Xflow configure the modem at the
desired speed, then it continue the initialization at this speed.

If no modem is found, initialization is stopped.

For a GSM modem (Local GSM or RAS) Xflow is now waiting for the modem to be attached to the
base before going on with the initialization phase: if the modem is not attached, it's useless to try to
use it, so the initialization is considered as failed.

When initialization failed:

For a GSM modem, Xflow doesn't try to retrieve network information, and doesn't try to
configure radio band.

Then, for a RAS connection, Xflow doesn't ask Windows system to connect to the mobile
operator network.

GSM reception level is now shown on the web page.

NOTE: To avoid not understandable error with RAS connection, the network connection process is
started only if the radio reception level is enough.

When Xflow failed to initialized the modem, it will wait for 1 minute before trying again the initialization,
and it will do that 10 times (by default). If initialization failed after those 10 attempts, it will wait for 60
minutes before starting again the whole cycle. Those parameters are configurable.

4/19
Xflow – release note for version 2.4.2

In the case of a RAS connection, the same process is used once the modem is initialized by Xflow: if
the network connection failed, Xflow tries again up to 10 times with 1 minute between two attempts. If
it failed 10 times, Xflow waits for one hour before re-launching the whole process.
st nd
NOTE: the 3 parameters (number of attempts, 1 and 2 delay and) are common between modem
initialization and RAS connection.

This is a better way to control modem initialization.

When a RAS resource is created, the initialization of the modem is the same as the initialization
performed with a GSM resource. That means Xflow first initializes the GSM modem the same way it
does when you create a "Local GSM" connection. This enables Xflow to identify the modem and
retrieve some information about the GSM network. Then Xflow lets the Windows system handling the
RAS connection.

In case of an error during the initialization phase of the modem, a specific message is indicated on the
"resource" web page, and the delay before the next retry is indicated in the web page:

In the case of a RAS connection, when the connection to GPRS/3G network failed, the delay before
the next retry is also indicated in the web page.

A new link on the page is provided to ask Xflow to retry initialization right now, without waiting for the
retry delay to expire.

ISP (Internet Services Provider) information are now part of the connection: the parameters found on
the system web page is no more used (excepted at startup after an upgrade from a version older than
2.4.2)

Following paragraphs give detail about how to control some initialization parameters.

7.1.2. Control the initialization of the modem: various timeouts

Three new parameters are introduced to control initialization timing, especially when an error occurred.

Maximum number of attempts : default is 10

Delay between two initialization attempts : default is 1 minute

Delay between two initialization cycles : default is 60 minutes

5/19
Xflow – release note for version 2.4.2

As mentioned earlier, it works this way: when Xflow failed to initialized the modem, it will wait 1 minute
before trying again an initialization phase, and it will do so up to 10 times (by default). If the
initialization phase failed after those 10 attempts, it will wait 60 minutes before starting again the whole
cycle. These 3 parameters are configurable.

7.1.3. Radio/frequency band configuration

User can configure authorized radio band and preferred radio band. It's preferable not to set
anything here, and let Xflow and the modem do their job.

It could be useful to configure it in some special cases such as a roaming situation, or if the iRio is in a
country where available band is restricted (regarding to Europe, for instance). This parameter allows
Xflow to ask the modem not to scan all possible bands to find the operator network, but to scan only
within the specified bands. It can improve the duration of the initialization.

The radio bands available for configuration are pre-defined in a list.

7.1.4. GSM network information

Xflow retrieves and displays some information about wireless network:

Current radio band: this is the current frequency band used by the modem

Cell ID: this is the identification number of the Base Transceiver Station (BTS) the modem is
connected to. This number is first shown in hexadecimal in so far it's the way t he modem
provide it. It's then shown in decimal for a more convenient use by user.

Operator name: the name of the mobile operator

Base Station ID: Base Station Identity Code (BSIC). A code to identify the base station.

Type of network

6/19
Xflow – release note for version 2.4.2

Until the modem is attached/connected to the Base Station, information is not available. In this case
the modem answers special values in place of IDs (see later "network registration")

7.1.5. Configuration of APN and ISP

APN and ISP (Login/password and phone number) are now available in the resource web page.

GSM/PSTN modem

RAS

With a RAS resource, the parameter « Modem init string » is automatically filled by Xflow with the AT
command to configure the APN into the Modem:

+CGDCONT = 1,"ip","APN_NAME"

APN_NAME is the name of the access point of the wireless operator.

The user should configure only the APN with the name given by his operator.

The “Modem init string” is then not available with RAS resource. And the phone number as well. For
GPRS communication, the phone number is a specific number. Xflow configure it automatically.

7/19
Xflow – release note for version 2.4.2

Backward compatibility is done with older versions where ISP was configured in the system web page.

7.1.6. Network registration

New AT commands have been used into the sequence of initialization of the modem: AT+CREG
AT+CGREG/AT+CGATT.

These AT commands allow detecting that the modem is correctly attached and registered to the
network GSM or GPRS/3G.

If the modem does not succeed to register to the network after a timeout, the initialization of the
modem failed.

The default value of this timeout is 20s and it could be configured from the SYSTEM table.

This parameter is not yet in the resource page: this page is huge enough today and user doesn't need
to be annoyed with too many advanced parameters. If you need to configure this delay because you
think radio network negotiation is long, you can do it.

8/19
Xflow – release note for version 2.4.2

7.1.7. Inactivity or unexpected lost of network preventive action

The RAS session is stopped and restarted if no data are received since a configured timeout.

It prevents unexpected lost of network and unavailability of the iRIO.

The timeout is configurable in the SYSTEM table. If this parameter is 0 or doesn't exist, this behavior
is disabled. If the parameter exist, the maximum value (in minutes) is 1440, and minimum value (in
minutes) is 15.

This parameter is read only once the connection is effective, that is while Xflow is connected this
timeout is not updated even if you change it in the table.

9/19
Xflow – release note for version 2.4.2

7.1.8. PIN code management

Improvement of the PIN code management:

If PIN code field is empty, nothing is sent to the modem

If PIN code field is lower than 4 digits, the PIN code is completed with 0 digit and sent to the
modem

If PIN code field is greater than 4 digit, the PIN is sent to the modem

7.1.9. Active link to re-launch the initialization of the modem

When the initialization of the modem failed, the user can re-launch it immediately by clicking on active
link at the bottom of the web page.

7.1.10. Warning of low level Radio reception

If the Radio reception level is lower than 109db, a warning message is displayed in the resource web
page.

10/19
Xflow – release note for version 2.4.2

7.1.11. Radio reception level pictogram

The radio reception level is shown with a pictogram.

7.1.12. Periodic refresh of network information

Some information about the wireless network is retrieved during the initialization of the modem.

Allowed Radio Band Frequencies

Preferred Radio Band Frequencies

Current Radio Band frequency used by the modem

Name of the operator

Cell ID

Station ID

Type of Wireless network

Current Radio reception level

Some information are updated every 30s.

Cell ID

Station ID

Current Radio reception level

This is valid ONLY for Local GSM connection.

For a RAS connection, information is read only during the modem initialization.

7.1.13. GPRS Counters

Some counters representing number of bytes exchanged have been added in “Permanent GPRS
communication” (RAS).

2 counters to indicate the number of bytes sent/received to/from the port. These counters are
set to 0 when the port is closed.

11/19
Xflow – release note for version 2.4.2

2 counters to indicate the payload in “Permanent GPRS communication” (RAS). These

counters are initialized to 0 when the resource is created and are set to 0 only by the user
when clicking on dedicated active link.

7.1.14. RAS Error code

With RAS resource, an additional field has been added to give more information about the current
connection attempt.

This “Error code” could be:

Current step when the RAS connection is in progress to connect

Error code when RAS connection failed

It could be useful to help diagnose a network connection problem.

7.1.15. RAS connection and Network level

To avoid not understandable error with RAS connection, the network connection process is started
only if the radio reception level is strong enough.

7.1.16. Disable modification of a modem if in use

The links [modify] are removed if the modem is connected or in use.

RAS resource not used

12/19
Xflow – release note for version 2.4.2

RAS resource in use

7.1.17. Default baud rate for a new connection

The default baud rate when a GSM Modem or RAS resource is created is now 115200 bps instead of
300 bps.

7.1.18. No attached device with modem resource

There are no attached device with « Local Modem », « Local GSM Modem » and « RAS » resources.
The link to attach a new device is removed from the web pages of these types of resources.

7.2. Various evolutions

7.2.1. Trace is available for UDP and TCP connection

When you configure an UDP or TCP connection, you can now enable the "trace" feature.

This will enable to log data exchanged between Xflow and a peer, ie Xflow and Kerwin.

We only log the application protocol data, not the UDP or TCP protocol layer.

This feature is also available for a "RAS client" connection. In that case the communication with the
modem during the initialization phase will be logged, but once connection to the network is established
nothing more will be logged.

7.2.2. User name and access level is shown on the top of each web page
Once you are connected to Xflow, your user name and your access level is shown on the top of each
web page.

13/19
Xflow – release note for version 2.4.2

8. What’s corrected in this version?

8.1. Device selection mode

BT-5580 ALXF-14216

If more then one meter is having communication loss physically like modbus cable is disconnected
then only one meter is reporting communication loss error in Xflow.

For example if PM210 & PM750 meters communication cable is removed then only PM210
communication loss status is updated in Xflow. Similarly if PM210 & PM1200 meters communication
cable is removed then only PM1200 communication loss status is updated in Xflow. This is not
expected as there may be a possibility when more then one meter may have a communication loss
physically, so in such a scenario user will never come to know about the communication loss of all the
devices in the network.

To manage that case, we introduced a way for Xflow not be stuck trying to read/write on a device
when this device looks to be definitely out of order.

If such a case is meet, then Xflow will discard the device for a certain amount of time, thus giving more
time to spend for selection of other variables on other devices.

This amount of time is of a maximum value of 1 minute, and is computed like this:

selection_delay (in ms) = (device_timeout * 3) + number_of_device_on_the_connection

IF selection_delay > 60000 THEN selection_delay = 60000

With the following information:

device_timeout : the timeout configured on the selected device

number_of_device_on_the_connection : this is the number of device configured on the same

connection as the selected one

This delay is considered only after 10 consecutives I/O errors. An error is:

A time out (no answer from the device)

A protocol error: an answer with an error code, an unknown frame etc.

A frame error: bad frame (bad checksum, bad crc…)

Once a device is in that state, you can see it on the device web page:

14/19
Xflow – release note for version 2.4.2

The remaining number of ms before Xflow will consider before selecting the device again, is also
shown.

The numerical value of the status is 0x800040 / 8388672:

0x80000 is for "device selection is delayed"

0x00040 is for "device on error"

8.2. Communications / Modems

8.2.1. Modem GSM MTSMC-E Baud rate

BT-5037 BT-5036 ALXF-8054 ALXF-8055

There is no more limitation on the baud rate of the modem MTSMC-E: this modem is able to work at
any baud rate.

Previously, the baud rate was limited to 9600bps and 115200bps.

8.2.2. Baud rate of COM port

BT-4661 ALXF-5550

The configuration of the baud rate of COM port is now available in any case.

8.3. Files management

8.3.1. Unable to read a file with more than 65536 records

BT-4813 ALXF-7639

The transfer of a file with more than 65536 records was previously wrong with Napbus protocol.

If there are N records with N > 65536, only N-65536 was read.

The behavior of Xflow is now corrected and a Napbus master can read a file greater than 65536
records.

8.3.2. Crash of a measure file when the name is changed with Kervisu

BT-6168 ALXF-10335

It was possible to change the name of a file in the RECORD table with Kervisu. And then the measure
file is locked and strange behavior occurred.

It is now not possible to write the field NAME of the table RECORD.

15/19
Xflow – release note for version 2.4.2

8.3.3. Disk I/O error slows down I/O communication with external devices

BT-4176

On iRio, if you save historical data on compact flash and the storage device is damaged Xflow might
freeze (slow down) during the write process. The new status “Disk I/O error” displays the state of the
historical file on the web interface and closes the file (no further writing to the damaged storage
device).

8.3.4. Error during transfer of historical values between Kerwin and Xflow if
the number of values is too large (example 100 variables)

BT-4088

Xflow was not designed to handle multiple napbus requests to pass the complete number of columns
for the file.

8.3.5. Value 0 (zero) are not recorded in state file for virtual variables of
type 'pulse'
BT-4592

For a variable of type pulse, only the first change of state from 0 to 1 was logged into the STATE file.
The return from 1 to 0 was not logged.

8.3.6. Events in historical files contain wrong values

BT-3406

Events in historical file might appear to be in the future (2061) or back in the past (1980).

This is really rare: the file must be full, it must have rotated, it must be read with napbus protocol and
from the latest record, and the size of a record must be a modulo of some internal buffer used by the
napbus module of Xflow. This is why it has been seen only once.

8.4. Alarms management

8.4.1. Acknowledgment by SMS of an alarm does not work anymore

BT-6126 / 6574 / 6573 ALXF-10132

If you configure a recipient of type GMS/SMS with no automatic acknowledgement the alarm was not
acknowledged.

Reminder: when you receive an SMS for an alarm for example on your mobile phone you can
acknowledge the alarm simply by sending back the SMS you received.

16/19
Xflow – release note for version 2.4.2

8.4.2. The variable page does not display the raw value of an alarm which
is of type "different"
BT-6966

A variable with an alarm of type “Different” did not display the raw value on the variable page.

8.4.3. Wrong display of alarm type “bigger than” instead of “bigger than or
equal”.

BT-7022

Correct translation is "greater than or equal" instead of "greater than" and "lower than or equal"
instead of "lower than".

8.5. OPC DA client [not available on the iRio]

8.5.1. A variable with a wrong address is still read by the Xflow driver

BT- 4191

If you configure an OPC variable in Xflow with a wrong address (that is a bad tag name) the variable
will still be read by the driver because of variable group management.

8.5.2. Variables do not change anymore when network is down

BT- 7288 7279

If OPC server is no longer available, Xflow doesn't see it and continue to try to read tags. The RPC
error "RPC_E_SERVERFAULT" wasn't managed by the OPC client.

This can be the case, for example, if you remove Ethernet cable, even if you re-plug it.

8.5.3. Server shutdown was badly manage in some cases

BT- 7290

When server is stopped, it informs Xflow: in some cases the OPC client was falling in a infinite loop.

8.5.4. "Hard" server stop was badly managed

BT- 7291 6507

When the server is killed, that is not stopped but strongly killed and removed from memory, Xflow OPC
client was not aware of it, and continues trying to read tags.

17/19
Xflow – release note for version 2.4.2

8.6. Various corrections

8.6.1. Error status of a RAS connection is not clear

BT-4204 ALXF-5552

Many improvement documented in paragraph Modem initialization, configuration and feed back
improvement will give user a better feedback.

8.6.2. Annual program which contains a program range with a year which is
different to the current year will not be executed

BT-7104

If you configure an annual program for a variable and the program’s first range has a range with a year
which is different to the current year all other program ranges will be ignored (even if the following
program ranges are configured for the current year).

8.6.3. Xflow crashes when you insert a lot of weekly scheduler programs
from Kervisu.

BT- 1338

If you insert a lot of weekly scheduler programs, Xflow might freeze and restart.

8.6.4. HTTP server stops to serve web page if it is "too busy" for a long
time.
BT-7125

8.6.5. Can not write to a table with a frame napbus of exactly 256 bytes
with Kervisu
BT-7147

It was not possible to write to a table with a napbus frame of exactly 256 bytes: Xflow returned "Frame
too long"

8.6.6. Sunezy : sometimes some variables are not read

BT-6933

Some error codes from sunezy inverter are not well managed: the variable is not set with "in error"
status but with "bad address" status. Problem is that when a variable is in "bad address" Xflow never
tries to read it anymore. This is because this status is supposed to exist only during configuration
phase.

18/19
Xflow – release note for version 2.4.2

8.6.7. RIO UPS2: bad unit display for variable "power source"
BT-5764 ALXF-8932

This variable reflects the power source: battery or power sector. It wasn't managed well when battery
is connected and power sector is connected.

8.6.8. Tabulation format is not correctly displayed in report page.

BT-7033 ALXF-13253

When you export a report you can select the tabulation format (US or FR). Changing the selection of
the format did not change the display on the web page.

8.6.9. iRio crashes when it starts without its synthesis file

BT-1502

When Xflow had a very big alarm file (more than 5000 records) and it starts without the synthesis file
(because for an unknown reason it doesn’t exist anymore (for example someone had removed it from
the SRAMDISK), then it crashes.

19/19