BEIJER - StartUp Ix (09 - 2014)

Start-Up
XAML-Import into iX Developer 2.10
KI00365 2014-09
1 Function and area of use

This document explains how to import vector graphics, XAML-components, into iX
Developer 2.10. WPF uses vector graphics and the appearance of the graphic is described in
XAML-code.
When using a XAML-component in a PC/TxC-application its possible to dynamically
change the Fill color, Stroke color and the Stroke thickness in Runtime. For Panel-targets its
only possible to change these properties in Designtime.
Software requirements:
- iX Developer 2.10
- Microsoft Expression Design 4 (Freeware)
- Kaxaml (Freeware)
Hardware requirements:
- iX Panel (TxA, TxB, TxC)
2 About the Start-up document

This Start-Up document should not be considered as a complete manual. It is an aid to be
able to start up a normal application quickly and easily. For further information we refer to
the iX Developer reference manual and User guide.
MAxx831x (Reference manual)
MAxx832x (User Guide)
This document and other Start-Up documents can be downloaded from

www.beijerelectronics.com.
Please use the address manuals@beijerelectronics.com for feedback on our Start-Up
documents.
KI_sv.dot, 090709
Parent company: Sweden

Registered office: Malmoe
Internet: www.beijerelectronics.com
E-mail: info@beijerelectronics.com
VAT reg no SE556025185101
Beijer Electronics AB (publ)

Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01
Beijer Electronics Inc.

939 North Plum Grove Road, Suite F
US-Schaumburg, IL 60173
USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674
Beijer Electronics GmbH

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599 10
KI00365 2014-09
3 Basic Import XAML into iX
KI_sv.dot, 090709
Install and open Expression Design 4. The software is free and can be downloaded at
http://www.microsoft.com/expression/eng/
Open Microsoft Expression Design and draw your image
Select all your components and choose File -> Export
Use the same settings as shown in the picture below:
www.beijerelectronics.com
2 (7)
KI_sv.dot, 090709
KI00365 2014-09
Click Export All and save the file.
Open iX Developer. Right mouse click on a node in the Component Library and
choose Add Component.
Select the XAML file that you exported from Expression Design.
3 (7)
KI_sv.dot, 090709
KI00365 2014-09
4 (7)
KI00365 2014-09
4 Advanced XAML bindings in iX

Its possible to bind some of the components properties to tags directly in iX Developers
property grid. The following properties are supported:
Fill, outline and outline thickness
4.1 Kaxaml
Download Kaxaml from http://www.kaxaml.com. Open your exported xaml file in Kaxaml.
Localize which part of the graphic that you want to control with fill, outline and outline
thickness. Changing the fill color for each section makes it easier to find which parts of the
XAML-code that needs to be modified.
4.2 Dynamic properties

The following dynamic properties are supported by iX Developer:
KI_sv.dot, 090709
//Namepace
xmlns:signatures="http://www.beijerelectronics.com/hmi/ix/signatures"
//Fill
Fill="{Binding Fill, RelativeSource={RelativeSource AncestorType={x:Type
signatures:ISymbolViewboxSignature}}}"
//Stroke
Stroke="{Binding Stroke, RelativeSource={RelativeSource AncestorType={x:Type
//Stroke Thickness
StrokeThickness="{Binding StrokeThickness, RelativeSource={RelativeSource AncestorType={x:Type
5 (7)
KI00365 2014-09
XAML code before modification

<?xml version="1.0" encoding="utf-8"?>
<Canvas xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Width="293.5" Height="284.5" Clip="F1 M 0,0L 293.5,0L
293.5,284.5L 0,284.5L 0,0">
<Ellipse Width="293.5" Height="284.5" Canvas.Left="0" Canvas.Top="-7.62939e-006" Stretch="Fill"
StrokeThickness="20" StrokeStartLineCap="Round" StrokeEndLineCap="Round" StrokeLineJoin="Round" Stroke="#FFFF0000"
Fill="#FFFFFF00"/>
<Path Width="56.32" Height="90.88" Canvas.Left="49.24" Canvas.Top="91.62" Stretch="Fill" Fill="#FF000000"
Data="F1 M 105.56,182.5L 49.24,182.5L 49.24,167.14L 68.44,167.14L 68.44,110.82L 49.24,114.66L 49.24,99.3L
87.64,91.62L 87.64,167.14L 105.56,167.14L 105.56,182.5 Z "/>
Data="F1 M 142.26,165.48L 142.26,165.86L 179.8,165.86L 179.8,182.5L 119.64,182.5L 119.64,166.86L 146.1,142.24C
151.433,137.307 155.183,133.17 157.35,129.83C 159.517,126.49 160.6,122.98 160.6,119.3C 160.6,111.087
155.953,106.98 146.66,106.98C 138.58,106.98 130.853,109.967 123.48,115.94L 123.48,98.56C 131.56,93.9333
140.673,91.62 150.82,91.62C 160.327,91.62 167.747,93.9 173.08,98.46C 178.413,103.02 181.08,109.18 181.08,116.94C
181.08,127.3 174.547,138.007 161.48,149.06L 142.26,165.48 Z "/>
Data="F1 M 224.08,183.78C 202.24,183.78 191.32,168.887 191.32,139.1C 191.32,123.647 194.273,111.87 200.18,103.77C
206.087,95.67 214.653,91.62 225.88,91.62C 247.213,91.62 257.88,106.76 257.88,137.04C 257.88,152.12 254.967,163.68
249.14,171.72C 243.313,179.76 234.96,183.78 224.08,183.78 Z M 225.02,106.98C 216.207,106.98 211.8,117.527
211.8,138.62C 211.8,158.487 216.12,168.42 224.76,168.42C 233.187,168.42 237.4,158.18 237.4,137.7C 237.4,117.22
233.273,106.98 225.02,106.98 Z "/>
</Canvas>
Modify the xaml code
Replace Fill, Stroke and StrokeThickness with dynamics properties. Dont forget to
add the namespace.
KI_sv.dot, 090709
<?xml version="1.0" encoding="utf-8"?>

<Canvas xmlns:signatures="http://www.beijerelectronics.com/hmi/ix/signatures"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Width="293.5" Height="284.5" Clip="F1
M 0,0L 293.5,0L 293.5,284.5L 0,284.5L 0,0">
<Ellipse Width="293.5" Height="284.5" Canvas.Left="0" Canvas.Top="-7.62939e-006"
Stretch="Fill" StrokeThickness="{Binding StrokeThickness, RelativeSource={RelativeSource
AncestorType={x:Type signatures:ISymbolViewboxSignature}}}" StrokeStartLineCap="Round"
StrokeEndLineCap="Round" StrokeLineJoin="Round" Stroke="{Binding Stroke,
RelativeSource={RelativeSource AncestorType={x:Type signatures:ISymbolViewboxSignature}}}"
Fill="{Binding Fill, RelativeSource={RelativeSource AncestorType={x:Type
signatures:ISymbolViewboxSignature}}}"/>
<Path Width="56.32" Height="90.88" Canvas.Left="49.24" Canvas.Top="91.62"
Stretch="Fill" Fill="#FF000000" Data="F1 M 105.56,182.5L 49.24,182.5L 49.24,167.14L
68.44,167.14L 68.44,110.82L 49.24,114.66L 49.24,99.3L 87.64,91.62L 87.64,167.14L
105.56,167.14L 105.56,182.5 Z "/>
Stretch="Fill" Fill="#FF000000" Data="F1 M 142.26,165.48L 142.26,165.86L 179.8,165.86L
179.8,182.5L 119.64,182.5L 119.64,166.86L 146.1,142.24C 151.433,137.307 155.183,133.17
157.35,129.83C 159.517,126.49 160.6,122.98 160.6,119.3C 160.6,111.087 155.953,106.98
146.66,106.98C 138.58,106.98 130.853,109.967 123.48,115.94L 123.48,98.56C 131.56,93.9333
140.673,91.62 150.82,91.62C 160.327,91.62 167.747,93.9 173.08,98.46C 178.413,103.02
181.08,109.18 181.08,116.94C 181.08,127.3 174.547,138.007 161.48,149.06L 142.26,165.48 Z "/>
Stretch="Fill" Fill="#FF000000" Data="F1 M 224.08,183.78C 202.24,183.78 191.32,168.887
191.32,139.1C 191.32,123.647 194.273,111.87 200.18,103.77C 206.087,95.67 214.653,91.62
225.88,91.62C 247.213,91.62 257.88,106.76 257.88,137.04C 257.88,152.12 254.967,163.68
249.14,171.72C 243.313,179.76 234.96,183.78 224.08,183.78 Z M 225.02,106.98C 216.207,106.98
211.8,117.527 211.8,138.62C 211.8,158.487 216.12,168.42 224.76,168.42C 233.187,168.42
237.4,158.18 237.4,137.7C 237.4,117.22 233.273,106.98 225.02,106.98 Z "/>
</Canvas>
6 (7)
KI00365 2014-09
4.3 Import to iX Developer
Open iX Developer. Right mouse click on a node in Component Library and choose
Add Component.
Select the XAML file that you modified in Kaxaml
Observe how your components appearance is changed when changing change fill/outline
color or when changing the outline thickness.
KI_sv.dot, 090709
When you have modified the component you can easily copy it to the Component Library.
This will allow you to reuse the graphic/component later on.
7 (7)
Start-Up
Alarm Distributor in iX Developer 2.0
KI00357 2013-12

This document explains how an iX Developer application can be configured in order to send
e-mail, SMS and printouts when alarms occur in the system.


documents.
KI_sv.dot, 090709


Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599 10
KI00357 2013-12
3 Configuring an alarm
The first step is to configure alarms in the applications, when the alarms are configured we will add the
Alarm Distributor service to the application. This service listens for alarm events that could be sent from
either another panel/pc but also from an internal alarm server.
KI_sv.dot, 090709
^

d

K^s
d

^
2 (17)
KI00357 2013-12
4 The Alarm Distributor service

The Alarm Distributor makes it possible to send alarm notification via printer, SMS or e-mail. The
function can be enabled internally in a project, or in another operator panel that acts as a server towards
several connected clients. Regardless of acting as server or client, distributed alarms are saved temporary
in the local project database to ensure that information is not lost in case of e.g. interrupted power. After
receiving alarms from client, the server will send a confirmation to the client. The alarms will then be
removed from the clients database.
4.1 Adding and configure a internal Alarm Distributor service

When you congfigure a internal Alarm Distributor it will act as Client and Server in the target that will
run the application
/Z

K^
KI_sv.dot, 090709
3 (17)
KI00357 2013-12
^

d^d^/
K<

E
/'
KI_sv.dot, 090709
4 (17)
KI00357 2013-12
E

KI_sv.dot, 090709

5 (17)
KI00357 2013-12
Z^/Z
^D^
K<

KI_sv.dot, 090709
&

^/

6 (17)
KI00357 2013-12
^/
dD&
K
KI_sv.dot, 090709
7 (17)
KI00357 2013-12
4.2 Adding and configure a external Alarm Distributor service

When you configure an external Alarm Distributor it will in the target that will run the application act as a
Server towards several Clients. This means that you only need to configure the distribution devices in one
operator panel or PC.
4.2.1
Settings for a Client
K^

KI_sv.dot, 090709
8 (17)
KI00357 2013-12
d^d^/W
^/WE^
WE
Y

K<

E
/
KI_sv.dot, 090709
d
9 (17)

4.2.2
KI00357 2013-12
Settings for a Server
/Z
KI_sv.dot, 090709

^dW^dWd

E

10 (17)
KI00357 2013-12

KI_sv.dot, 090709
11 (17)
KI_sv.dot, 090709
KI00357 2013-12
Z^/Z
^D^

&

^/

12 (17)
KI00357 2013-12
^/
dD&
K
KI_sv.dot, 090709
4.3 Configure Distribution Devices

13 (17)
KI00357 2013-12
4.3.1 E-mail Device

There are a numbers of parameters to configure for a establish connection to an e-mail server. More
information about how to setup an e-mail server and sending e-mail from an operator terminal, please
refer to the start-up document:
</^'^D^
KI_sv.dot, 090709
3DUDPHWHU

)URP1DPH

)URP(PDLO$GGUHVV
60736HUYHU1DPH,3
3RUW

$XWKHQWLFDWLRQ0RGH
8VHU1DPH3DVVZRUG
5HWU\6HQGLQJ
7LPH,QWHUYDO

6XEMHFW

%RG\

'HVFULSWLRQ

7KHQDPHRIWKHVHQGHURIWKHHPDLO

7KHHPDLODGGUHVVRIWKHVHQGHURIWKHHPDLO

7KHQDPHRU,3DGGUHVVRIWKH6073VHUYHUIRUVHQGLQJHPDLO
7KHSRUWQXPEHURIWKHHPDLOVHUYHU

6HOHFW1RQHRU$XWKHQWLFDWHG/RJLQ

8VHUQDPHDQGSDVVZRUGLI$XWKHQWLFDWHG/RJLQZDVVHOHFWHG

1XPEHURIUHWULHVLIWKHHPDLOFDQQRWEHGHOLYHUHG

1XPEHURIVHFRQGVEHWZHHQUHWULHV
7KHHPDLOVXEMHFW$ODUP9DULDEOHVFDQEHXVHG
7KHHPDLOERG\$ODUP9DULDEOHVFDQEHXVHG
14 (17)

4.3.2
KI00357 2013-12
Printer Device

3DUDPHWHU

3ULQWHU&RQQHFWRU
3ULQWHU7\SH

1HWZRUNVHWWLQJV
6HULDOVHWWLQJV
%XIIHUVHWWLQJV
3DJH2ULHQWDWLRQ
7H[W)RQW6L]H

%RG\

'HVFULSWLRQ

6HOHFW86%(WKHUQHWRUVHULDOSULQWHUFRQQHFWLRQ

6HOHFWSULQWHUW\SH
1HWZRUNVHWWLQJVLI(WKHUQHWSULQWHUFRQQHFWLRQZDVVHOHFWHG

6HULDOVHWWLQJVLIVHULDOSULQWHUFRQQHFWLRQZDVVHOHFWHG

%XIIHUVHWWLQJVLI86%SULQWHUFRQQHFWLRQZDVVHOHFWHG
3RUWUDLWRUODQGVFDSHRULHQWDWLRQRIWKHSULQWRXW

7KHIRQWVL]HRIWKHWH[WWREHSULQWHG
7KHERG\RIWKHSULQWRXW$ODUP9DULDEOHVFDQEHXVHG
3ULQWRXWVYLD2SHUDWRU3DQHO
When printing to a serial printer from an operator panel, the printer must support IBM character set (850).
When printing to a USB printer from an operator panel, the printer must support the printer classes
according to the table below:

3ULQWHUW\SH

&RORUODVHUSULQWHU
3ULQWHUFODVV
UHTXLUHPHQW

5HFRPPHQGHG
3ULQWHUPRGHO
86%3&/F +3/DVHU-HW
0RQRFKURPHODVHUSULQWHU 86%3&/H +3/DVHU-HW
KI_sv.dot, 090709
&RORULQNMHWSULQWHU86%
86%3&/H
+3'HVNMHW
15 (17)
KI00357 2013-12
When printing via Ethernet from an operator panel, the network printer must be a shared resource in
theWindows network.
1RWH
&RQQHFWLQJDSULQWHUYLD(WKHUQHWUHTXLUHVWKDWD3&LVFRQQHFWHGEHWZHHQWKHRSHUDWRU
SDQHODQGWKHSULQWHU
1RWH
3ULQWLQJWRDFRORUODVHUSULQWHUYLD(WKHUQHWLVQRWVXSSRUWHGIRURSHUDWRUSDQHOV
1RWH
7KHSULQWHUFODVV3&/LVQRWVXSSRUWHGDWDOOIRUFRQQHFWLRQWRRSHUDWRUSDQHOV
4.3.3 SMS Device

To be able to send alarms via SMS, you have to purchase an SMS Gateway Service. You will then get a
URL configuration string with a unique username and password (marked with blue) and the service
provider also have to include two variables, {0} for telephone number and {1} for SMS body (marked
with red).
3DUDPHWHU

%DVLF85/IRUZHE606
KI_sv.dot, 090709
5HWU\6HQGLQJ
7LPH,QWHUYDO
%RG\

'HVFULSWLRQ
7KH85/FRQILJXUDWLRQVWULQJDFFRUGLQJWRWKH606*DWHZD\
6HUYLFHVXSSOLHUWKDWPXVWLQFOXGHWZRYDULDEOHV^`IRU
WHOHSKRQHQXPEHUDQG^`IRU606ERG\

1XPEHURIUHWULHVLIWKH606FDQQRWEHGHOLYHUHG

1XPEHURIVHFRQGVEHWZHHQUHWULHV
7KH606ERG\$ODUP9DULDEOHVFDQEHXVHG
16 (17)

4.3.4
KI00357 2013-12
Alarm Variables
Variables collected from the alarm server definitions can be included in distributed
alarm information. Variables are enclosed by curly brackets; for example Alarm
text: {3}. The following variables can be used:

1XPEHU
9DULDEOH
'HVFULSWLRQ

6WDWH
7KHFXUUHQWVWDWHRIWKHDODUP

6WDWH7LPH
7KHWLPHWKHDODUPHQWHUHGWKHFXUUHQW
VWDWH

$ODUP,G
$XQLTXHDODUP,'

$ODUP7H[W
$ODUPLWHPWH[W

$ODUP,WHP'LVSOD\1DPH
$ODUPLWHPQDPH

&RXQW
7KHQXPEHURIWLPHVWKHDODUPKDVRFFXUUHG

$FWLYH7LPH
7KHWLPHWKHDODUPEHFDPHDFWLYH

,QDFWLYH7LPH
7KHWLPHWKHDODUPEHFDPHLQDFWLYH

1RUPDO7LPH
7KHWLPHWKHDODUPEHFDPHQRUPDO

$FNQRZOHGJH7LPH
7KHWLPHWKHDODUPZDVDFNQRZOHGJHG
For example if you enter following in any subject or body fields of a distributon device:
Alarm notification! | {4} is {0}
{4}: {3}, occurred at {0} and has occurred {5} time/times.
If the alarm item below will be active you will get this information from the distribution device:
Alarm notification! | AlarmItem0 is Active

AlarmItem0: Tag1 > 90, occurred at 2011-07-06 15:09:01 and has occured 1 time/times.
KI_sv.dot, 090709
17 (17)
([WHUFRQYHUVLRQWRL;'HYHORSHU
.,
Function and area of use

iX Developer has a built-in function for converting your old Information Designer project to
an iX Developer project.
This startup document will provide help regarding what to consider when chosing a
replacement HMI in the iX series and the easiest way of getting started with your converted
project.


documents.
KI_sv.dot, 090709


Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599 10
.,
6HOHFWLQJWKHULJKWUHSODFHPHQW
The following chapter will describe the different models to help you select the right
replacement model.
*HQHUDOGLIIHUHQFHV
Exter HMIs are available in both touch- and key-based HMIs.
iX HMIs are only available with a touchscreen configuration (but it is possible to connect
external physical buttons, keyboards etc).
If your original project is for a key based Exter HMI, there are several points you need to
take into consideration compared to if it is a touch based HMI.
For instance, keybased push events are handled differently.
The navigation in a converted iX project will also behave differently compared to the
navigation in a key based Exter HMI.
Since all navigation will need to be redesigned for the touch based iX project, more screen
surface will be needed (since you will need to add touch buttons that handle the navigation).
An Exter HMI with touch screen will be more graphically oriented and will be more easily
converted to an iX project and generally, you will be able to convert to a matching iX HMI
of the same size.
An Exter HMI with lots of lists, texts and less focus on the graphical interface will usually
need to be converted to a larger iX HMI to be able to better handle the lists and texts in a
good way.
But with some of the newer functions available in iX or simple reorganizing, you will be
able to better optimize the project.
KI_sv.dot, 090709
Differences regarding conversions will be discussed in more detail later on.
2 (26)
.,
&RPSDULVRQEHWZHHQ([WHUDQGL;+0,V
Below you will find two tables covering the properties of Exter and iX HMIs.
Exter HMIs:
Model
CPU
K10m K20m
K30m K60
RISC CPU, 512kB

application
memory, 1MB
RAM
Display
Resolution
Black
and
white
5,5"
5,5"
160x
32
GreyGreycolor
color
scale
scale
color
5,7"
240x
64
3,5"
Greyscale
5,7"
320x240
RS232
1x9 pin D-SUB
RS485/
422
1x25 pin D-SUB
color
6,5"
640x480
10,4"
10/100 Mbit RJ45/TP
USB
1 x for use of keyboard, mouse, printer, USB-stick etc.
CF-slot 2
10"
800x600
Ethernet
CF-slot 1
KI_sv.dot, 090709
T60m K70 T70 K100 T100 T150
RISC CPU (Intel Xscale) 32 MB Intel Strata Flash, 64 MB RAM
black and white

Display in
inches
K60m T40 T40m T60
15"
1024x
768
1 x internal slot (for memory

expansion of 32 - 1024 MB)
1 x external slot (for data

capture/export)
3 (26)
.,
iX HMIs:
Series
TxA
TxB
TxC
QTERM
Models
T4A, T7A, T10A
T7B, T12B, T15B
T12C, T15C, T21C
QTERM-A7,
QTERM-A12
Display in inches
4.3", 7", 10.4"
7", 12", 15"
12", 15", 21"
7", 12"
Resolution
480x272
800x480
640x480
800x480
1280x800
1280x800
1280x800
1280x800
1920x1080
800x480
800x600
Widescreen
T4A, T7A
All
All
A7
Full HD
T21C
CPU
400 MHz ARM9
1.1 GHz Intel Atom
Intel Celeron
or Core i7
XScale PXA 300

ARM 624 MHz
Serial interfaces
2 x RS232, 2 x
RS422/485
(9-pin D-SUB)
2 x RS232, 2 x
RS422/485
(9-pin D-SUB)
2 x RS232, 2 x RS485 1 x RS232/422/485,

(9-pin D-SUB)
1 x RS232
(9-pin D-SUB)
Ethernet
1 x 10 Base-T / 100
Base-T
2 (1 x 10/10/1000
Mbit/s, 1 x 10/100
Mbit/s)
2 x 10/10/1000 Mbit/s 1 x 10 Base-T / 100

Base-T
USB
1 x USB Host 2.0,

max output current
200 mA
3 x USB Host 2.0,

max output current
500 mA
4 x USB Host 2.0,

max output current
500 mA
2 x USB Host 2.0
Application flash
80 MB
1.4 GB
8 - 64 GB
3.5 GB
Memory slot
1 x SD card slot
1 x SD card slot
Via USB
Fieldbus
(expansion modules)
1 x Extension Module 1 x Extension Module 1 x Extension Module

Slot for Fieldbus
Slot for Fieldbus
Slot for Fieldbus
(Optional)
(Optional)
(Optional)
Misc. Interfaces
Working temperature -10 to 60C
KI_sv.dot, 090709
IP class
IP65
Audio: 3,5mm
Video: 1 x VGA, 1 x
DVI
Expansion:
Mini PCIe
-10 to 50C
0 to 50C
-30 to 70C
IP65
IP65
IP66
4 (26)
.,
0DWFKLQJ+0,V
Below is an estimation table for which iX HMI to use to replace your Exter HMI.
All suggestions have the same or larger screen size and resolution.
The Exter Pro+ HMIs have support for PDF, if this function is necessary your HMI needs to
be replaced with either a TxB or a TxC series.
KI_sv.dot, 090709
Information Designer
iX Developer
Exter K10m
L;7$
Exter K20m
L;7$
Exter K30m
L;7$
Exter T40
L;7$
Exter T40m
L;7$
Exter K60
L;7$,47(50$
Exter T60
L;7$,47(50$
Exter K60m
L;7$,47(50$
Exter T60m
L;7$,47(50$
Exter K70
L;7$,47(50$
Exter K70 Pro+
L;7%,47(50$
Exter T70
L;7$,47(50$
Exter T70 Pro+
L;7%,47(50$
Exter K100
L;7$, 47(50$
Exter K100 Pro+
L;7%, 47(50$
Exter T100
L;7$, 47(50$
Exter T100 Pro+
L;7%,47(50$
Exter T150
L;7%
Exter T150 Pro+
L;7%
5 (26)
.,
&RPPXQLFDWLRQ
TxC does not have support for an RS422 interface on the serial ports, those only support
RS232 and RS485.
If RS422 is a required interface, a converter can be used, for example RS232 to RS422.
All iX HMIs support serial communication via 2 9-pin D-SUB.
Each D-SUB is separated into 2 virtual ports on the TxA, TxB and TxC series.
KI_sv.dot, 090709
All iX HMIs have ethernet interface (RJ45 contact), the later series (TxB and TxC) have
two separate network interface cards.
6 (26)
.,
&RPPXQLFDWLRQ'ULYHUV
Below is a list of all available drivers (at time of writing). Are you missing a driver?
Please contact your closest Beijer office.
Communication Drivers
ABB
iX
Developer
Information
Designer
ABB Comli Slave

ABB Comli Master
ABB Modbus AC500
Allen-Bradley
AB ControlLogix
AB DF1
AB DH485
AB SLC/PLC5 Ethernet
AB MicroLogix Ethernet
Altus
Altus Alnet I
Animatics
Animatics SmartMotor
B&R
Bernecker+Rainer Mininet
Baumueller
Baumueller bmaxxOS
Beckhoff
Beckhoff ADS
Beckhoff Modbus
Bosch Rexroth
Bosch Rexroth IndraDrive
J1939
J1939 EM
CoDeSys
CoDeSys ARTI
CoDeSys Soft Control Direct Access
Cognex
Cognex DVT
KI_sv.dot, 090709
Cognex In-Sight
Control Techniques
Control Techniques Unidrive
CIMON
CIMON
CTC
CTC Serial Binary
Danfoss
VLT FC Drive
Delta Tau
Delta Tau PMAC/UMAC
Delta
Delta DVP
Demo
DEMO
ELMO
Elmo Maestro
Emerson
EMERSON Modbus Master
Eurotherm
Easy Serial 631
Fatek
Fatek Facon
FESTO/BECK
FESTO/BECK FST CI
7 (26)
.,
FESTO/BECK FST CI Ethernet

Galil
DMC series
GE Fanuc
GE Fanuc Ethernet
GE Fanuc SNPX
Generic CAN open
Generic CAN Open
Generic Profibus
Generic Profibus driver
Giddings&Lewis
G & L Motion Control Serial

G & L Motion Control Ethernet
Hitachi
Hitachi H-COMM
IAI
XSel
RoboCylinder
Idec
IDEC FA 1:1
IDEC FA 1:1 (expanded)
IDEC Micro
Johnson Control
JCONTROL
KEB
COMBIVERT
Keyence
KEYENCE KV-Series
Koyo
Koyo DirectNET
Koyo ECOM
Koyo K-Sequence
Lenze
Lenze LECOM A/B
LIYAN Electric
LIYAN EX
LS Industrial Systems
Glofa
Master-K
Matsushita
MEWTOCOL-COM
Mitsubishi
(MELSEC)
Alpha2
A-Series (C24)
A-Series (CPU)
Freqrol FR-A PLC
FX Series Serial
MC Protocol
QnA/Qnn Profibus DP
FX Series ADP/BD
MR-J2/MR-J3-T
QnA/Qnn Serial (CPU)
QnA/Qnn-Series (C24)
KI_sv.dot, 090709
QnA/Q-Series (E71) Ethernet
8 (26)
Modbus
.,
Modbus Master RTU/ASCII

Modbus Master RTU/ASCII IEC
Modbus Slave
Moeller
Moeller PS4 series (SUCOM-A)
NMEA 0183
NMEA 0183
OMRON
OMRON FINS
OMRON Host Link
Parker
GeParker6K
Regin
EXOline
SAIA
S-BUS Serial/Ethernet
SEW
MoviLink/SMLP
SIEMENS
SIMATIC S5 3964R
SIMATIC S7 MPI (EM)
SIMATIC S7 MPI (HMI Adapter)
SIMATIC S5 PG/AS511
SIMATIC S7 3964R
SIMATIC S7 ISO over TCP/IP
SIMATIC S7 MPI Direct
SIMATIC S7 200 PPI
SIMATIC S7 Profibus DP
KI_sv.dot, 090709
SIMATIC TI500
Telemecanique/
Schneider Electric
Toshiba
TSX UNI-TELWAY
WAGO
WAGO Modbus TCP
Vigor
Vigor M/VB-Series
Yamaha
Yamaha VIP
Yaskawa
Yaskawa Memobus Master

Yaskawa FSP
Computer Link
YET
SMC series
YET XtraDrive
Yokogawa
Yokogawa FA-M3
9 (26)
.,
7DJV
In iX, exponents must be configured for the control the tag is bound to.
Format
Data type
E-Designer
Data type
iX Developer
Range
Bit
Bit
BIT
0 and 1
Bool
BOOL
Values can be false (0) or true (1)1
Signed 16-bit
Signed 16-bit
INT16
-32,768 +32,767
Unsigned 16-bit
Unsigned 16-bit
UINT16
0 +65,535
Signed 32-bit
Signed 32-bit
INT32
-2,147,483,648 +2,147,483,6472
Unsigned 32-bit
Unsigned 32-bit
UINT32
0 +4,294,967,2952
Float with
exponent, 64-bit
DOUBLE
1.7E3081
FLOAT
3.4E381
DATETIME
An Analog Numeric object can present the

time format3. See help for more information.
Storing character strings in tags.
For this data type, size can be selected.
Float with
exponent, 32-bit
7 x Signed 16-bit
Float with exponent
String
String
STRING
BCD Float
BCD Float
FLOAT4
BCD 16-bit
BCD 32-bit
BCD 16-bit
BCD 32-bit
0 9999,9999
INT/UINT16
0 - 9999
INT/UINT32
0 - 99999999
0 - FFFF
HEX 16-bit
HEX 16-bit
INT/UINT16
HEX 32-bit
HEX 32-bit
INT/UINT324 0 FFFF FFFF
1. Controller representation for this type is dependent on the driver software.

2. Regarding resolution of values in 32-bit format: both iX Developer and the operator panel
can handle up to six decimal digits of an integer 32-bit value. Remaining digits will be
truncated or changed into zeros.
3. yyyy = year, MM = month, dd = date, hh = hour, mm = minute, ss = second.
KI_sv.dot, 090709
4. Displayed value have to be changed for the specific object, not the tag in general.
10 (26)
.,
,PSRUW3URMHFW
iX Developer supports the function of project import from Information Designer,
E-Designer and H-Designer.
The following functions are supported by the import:
Text Library
Tag list
Alarm Server
Multi Language
During the import, a log is generated where you can find which objects and functions where
not successfully imported. The log file can be saved for later trouble shooting.
KI_sv.dot, 090709
Note! Before you continue, make sure that:
The Exter project is saved in the latest version of Information Designer.
That objects in the project are ungrouped.
That a matching HMI has been decided.
That you have read about the limitations in the end of this chapter.
11 (26)
KI_sv.dot, 090709
Start iX Developer. Select Import Project at the splash wizard.
Press Browse... then navigate and select which project to import.
.,
12 (26)
.,
In the list Files of type, select which type of project you wish to import.
KI_sv.dot, 090709
In this case, select Information Designer:
Select your target type. Either PC or a specific iX HMI.
Select target folder and project name for the new converted project.
Press Finish when done.
13 (26)
KI_sv.dot, 090709
.,
Select matching controller. It is important that this step is made correctly for iX to be
able to handle the imported device addresses from the original Exter project.
In this example, the SIMATIC S7 ISOoverTCP driver is used in the Exter project. The
matching driver will be the SIMATIC S7IsoTcp.
When you have selected your new controllers, press the OK button.
14 (26)
.,
/LPLWDWLRQV
Certain functions, like recipes and data logging (Data Logger) work differently in iX
Developer and you will need to reconfigure these functions in your converted project.
Functions to consider in your converted project:
Text Library/Message Library Works without issues.
Tag list/Name List Indexing, poll groups and poll interval must be reconfigured
manually.
Gain/offset settings are now global and found in the tags editor
Indexing and poll groups can be converted via manual import of the Name list.
Alarm Server/ Alarms Properties for Alarms must be configured manually.

Acknowledge notify must be configured manually and is replaced by the Alarm
acknowledge property in iX.
To Printer has been replaced with Alarm Distributor Server function in iX.
Multi Language Works without issues.
Controller settings are not converted and must be manually configured.
KI_sv.dot, 090709
Note! Always verify that the import has been correctly made for all functions.
15 (26)
.,
0DQXDOLPSRUWRIWKHQDPHOLVW
Below follows an example of how you can manually import the name list from Information
Designer into iX Developer.
KI_sv.dot, 090709
The correct controller must be used in the iX project to be able to import the name list from
the Information Designer project.
Export the name list from Information Designer.
Select the devices/tags belonging to the driver you wish to export. You are only able to
export from one controller/driver at a time. Push Export
16 (26)
KI_sv.dot, 090709
Select Semicolon as the separator, push OK.
Save the exported tags to a file with a suitable name.
Start Excel (Excel 2003 is used in this example).
Open the exported text file from Information Designer.
.,
17 (26)
.,
Text Import Wizard will be displayed automatically by Excel.

If it does not start up automatically, use Import Data and manually select your file:
KI_sv.dot, 090709
Select Next.
18 (26)
.,
Select Semicolon as the Delimiter. A preview will be shown in the lower textbox. If it
looks correct, press Finish.
KI_sv.dot, 090709
The imported file should look something like this and have the correct column separation:
19 (26)
KI_sv.dot, 090709
.,
Save the file in the Excel format .xls.
20 (26)
.,
It is a good idea to export a sample of a tags list from iX to later use as a template when you
want to create files to import.
In this example, we only go over the differences between the two Export/Import formats (see
below). Using the template as a guide for what you need to change should help you be able
to convert your name list to a file that can be imported in iX Developer.
Start iX Developer 2.0.
KI_sv.dot, 090709
Let us use the following tag as an example, AiCurrentPump1:
Configure an identical tag in iX Developer 2.0.
Export the complete taglist.
21 (26)
.,
Select to export to Excel format. Select target filename.
Select a suitable name and press Export.
Open the file you exported in Excel.
See explanation below covering the different properties and how they match up between
Information Designer and iX Developer.
,QIRUPDWLRQ'HVLJQHU
L;'HYHORSHU
1DPH
1DPH
$GGUHVV
$GGUHVVB
&RPPHQW
'HVFULSWLRQ
'DWD7\SH
'DWD7\SH
,QGH[
!
!
!
,QGH[5HJLVWHU1XPEHU
'HIDXOW

(WF
!
!
!
3ROO*URXS1DPH
3ROO*URXS'HIDXOW
3ROO*URXS
3ROO*URXS
(WF

,
,
,27LPHJURXS

KI_sv.dot, 090709
How to modify the export file from Information Designer:

Remove the two top rows.
22 (26)
.,
Change names of the columns to match them with what iX Developer understands.
Information Designer:
iX Developer:
KI_sv.dot, 090709
Replace the incorrect data types.
23 (26)
.,
For example:
KI_sv.dot, 090709
Import your tags list in iX. Select Excel file.
24 (26)
KI_sv.dot, 090709
.,
25 (26)
.,
A preview is shown:
If it looks correct like the example below, press Import.
Done.
$IWHUWKHSURMHFWLVFRQYHUWHG
You must locate your Gain/offset settings in your old Exter project manually.
It is not a global settings like in iX, it is instead configured on individual objects/controls.
KI_sv.dot, 090709
Save the log file that is generated during an import. It will contain clues as to what
screens/objects in your project was not converted, and that should help you learn what needs
to be converted manually/redesigned in your converted project.
26 (26)
Start-Up
Download project via Ethernet/USB
KI00352 2013-09

This document explains how to download an iX Developer 2.0 project via Ethernet/USB to
an iX panel. The file copying via USB to TxA and TxB panels is handled automatically at
startup. For TxC, you must move the project manually. Note that the runtime database will
be replaced by the database in the design project when you make a download to the panel.
- iX Developer 2.0
- iX Panel (TxA, TxB, TxC)
- Network cables
- WinCE 6.0 Compatible USB-stick (see our home page for recommendations)


documents.
KI_sv.dot, 090709


Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599 10
KI00352 2013-09
3 Download project via Ethernet
In the project application click on Download under Project in the ribbon menu.
iX Developer will build and validate the project before showing the transfer dialog
When the project has been validated all accessible panels in your network show up in
the dialog.
KI_sv.dot, 090709
If nothing shows up, examine your firewall settings.
2 (5)
KI00352 2013-09
Edit Change IP address remotely
Download Transfer project to panel

Verify Compare design project with runtime project.
Log View transfer log file
Option Download all source code (for later upload) with password protection. This
option will zip the whole design project for later editing. This option is only available
with ethernet transfer. This option is required to perform Verify and Uploads from panel
targets.
KI_sv.dot, 090709
Choose your target and press download. If the target for the download contains newer
files or files that dont exist in the project, a dialog will appear. Choose if you want
to keep, overwrite or delete the files.
3 (5)
KI_sv.dot, 090709
KI00352 2013-09
You can follow the transfer progress.
4 (5)
KI00352 2013-09
4 Transfer via USB

The project can be exported to a USB stick and then transfered to the panel. In TxA and
TxB, the file copying is handled automatically at startup. For TxC must user move the folder
manually.
In the project application click on Export under Project in the ribbon menu.
Select the root path of your USB device. The exported project folder contains only
Runtime files. You can not open this project in iX Developer.
4.1 Transfer via USB TxA, TxB
4.2
Plug in USB memory stick to the panel. Reboot the panel. If the panel detect a valid
project on the USB, an Update project message is displayed. The system will ask you if
you want to make a backup of the existing (running) project before overwriting.
Transfer via USB, TxC
Stop/Exit the running project. Make a backup of your existing project before the next
step. On Windows7 the path is:
KI_sv.dot, 090709
C:\Users\Public\Public Documents\Beijer Electronics AB\iX Developer Runtim

2\Project
Delete the existing project folder. All the necessary files you need is stored in the new
project folder on your USB.
Copy the folder Project from USB memory stick to TxC panel.
5 (5)
Start-Up
How to set up OPC UA with KepServer
KI00344 2013-07-10
iX Developer provides an OPC UA Server which is an industrial communication standard

created in a collaboration of automation hardware and software suppliers. The standard defines
methods for exchanging real-time automation data. An OPC server acts as a controller towards
an operator panel.
- iX Developer 2.0 (or higher)
- KEPServer
- Unified Automation UA Expert
http://www.unified-automation.com/downloads/opc-ua-clients.html

able to start up a normal application quickly and easily. For further information we refer
to the iX Developer reference manual and User guide.
(For more information regarding the OPC Server please see Reference manual chapter 5.3)

documents.
KI_sv.dot, 090709


Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599 10
How to set up OPC UA with KEPServer
KI00344 2013-07-10
3 iX Settings
KI_sv.dot, 090709
Create a Panel or a PC project. Select a Panel and press Next, choose OPC UA Server
and type in the OPC Servers URL.
2 (9)
KI00344 2013-07-10
4 Settings for the KEPServer
KI_sv.dot, 090709
Right click on the KEPServer Icon and choose OPC UA Config (the Icon is locked in
the task bar).
3 (9)
KI00344 2013-07-10
KI_sv.dot, 090709
4.1 Security and Basic settings
Set Localhost only and Port Number: 49320. Security Policies should not be used since
iX does not support Encryption. (Refer to limitations in the Reference manual
Maxx831x).
After the changes has been made right click on the KEPServer Icon and click on Reinitialize to
enable the OPC UP Server functionality.
4 (9)
KI00344 2013-07-10
KI_sv.dot, 090709
5 Controller settings in iX
Open iX and enter Tags/Controllers
Choose Settings in the Controllers tab.
5 (9)
KI00344 2013-07-10
5.1 OPC UA Properties
The namespace URL needs to correspond with the namespaces in the OPC UA Server. A
third party OPC UA Client, Unified Automation UA expert, will be used to find the
correct namespace.
6 Install Unified Automation UA Expert
To be able to install Unified Automation UA Expert please follow the instructions given
on the website.
http://www.unified-automation.com/downloads/opc-ua-clients.html
KI_sv.dot, 090709
When the Software is installed right click on Servers and choose Add
6 (9)
KI00344 2013-07-10
6.1 Server Settings
Write URL //localhost:49320 and select the OK button
6.2 Connect
KI_sv.dot, 090709
Right click on the Server and choose connect
7 (9)
KI00344 2013-07-10
KI_sv.dot, 090709
6.3 NamespaceArray
Open the Server tree and you will find a tag called NamespaceArray, drag and drop the
NamespaceArray in to the window (Default DA view)
Double click on the Value address and the NamespaceArray for NS2 will be shown
8 (9)
KI00344 2013-07-10
7 Set NamespaceArray in iX
KI_sv.dot, 090709
Copy the NamespaceArray in to the Properties settings for iX OPC UA Client, click on
the OK button. The communication should now work OK.
9 (9)
Start-Up
iX Runtime
KI00336 2013-04

This document describe what is included in the iX runtime installation.
It also contain a step-by-step guide on how to install a new or update an older driver on a
runtime PC/TxC and also how to update the iX Runtime version on a PC/TxC.


documents.
3 What the runtime installation contains

The iX runtime installation includes the .NET framework and SQL CE files required to run
applications designed in iX Developer.
It also includes the latest release of all the communication drivers available in iX Developer.
If a new driver is released or if a new version of an older driver is available, it must be
installed manually by an operator.
When you update your iX runtime installation to a newer version, you will automatically
replace the communication drivers included in the original runtime installation with the
newer driver included in the newer version of the software installation package.
If you have manually updated any driver, it will also be replaced by the one included in the
software installation package.
KI_sv.dot, 090709


Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599 10
Provide Start-up documents name
KI00XXX 2013-04
4 How to install a new driver/update an existing one
If only a .cab file is available, extract all the files from the archive.
There should be 3-4 files in the archive (depending on which driver is used),
they all have the same name, but different file endings:
.chm, .dll, .dll.ce6 and .dll.ce6x86.
Copy the driver files to e.g. a USB memory stick for easy transfer to the RT PC/TxC.
Paste the files to the driver default folder on the RT PC/TxC.
The default folder for a TxC is:

C:\Program Files\Common Files\Beijers Shared\OPC Drivers\
Open the Run window (shortcut: + R) and type:
regsvr32.exe "C:\Program Files\Common Files\Beijers Shared\OPC

Drivers\name_of_driver_file.dll"
KI_sv.dot, 090709
The path above refers to the location of the driver on a TxC.
2 (5)
KI00XXX 2013-04
Example:
To register the ABB COMLI master driver seen in the screenshot above, the syntax in the
Run window would be:
regsvr32.exe "C:\Program Files\Common Files\Beijers Shared\OPC
Drivers\ABB_COMLI_master_Pre2.dll"
You will get a popup from DllRegisterServer to verify if registration was successful or not:
5 How to update the Runtime version on a PC/TxC
KI_sv.dot, 090709
Press Windows Button, select Control Panel.
3 (5)
KI00XXX 2013-04
KI_sv.dot, 090709
Select Uninstall a program:
Find your version of the iX Developer Runtime 2.0 and press Uninstall.
Follow the on-screen instructions until the uninstall is complete.

Copy the new iX Runtime installation files to the PC/TxC.
4 (5)
Placing them in a folder on the desktop is usually the easiest.

The following is the files and folders your complete installation package should contain:
Run the setup.exe as an administrator and follow the instructions until the installation is
complete.
Your update of the iX Runtime is now complete.
KI_sv.dot, 090709
KI00XXX 2013-04
5 (5)
Start-Up
iX RT vs iX panels
1
KI00335 2013-04
Function and area of use

This document describe the differences between iX RT and iX Panels.
iX RT is an abbreviation for iX Runtime and refers to an iX project running on a PC with the
appropriate software and hardware installed.
This includes both iX Runtime software package and a iX RT dongle.
About the Start-up document

KI00336x (iX Runtime Start-Up document)

documents.
Main differences
Its important to understand the main differences between iX RT and iX panels.
iX RT runs on a PC with more powerful hardware compared to an iX panel.
The OS on our TxC Panel PCs is Windows 7, which supports both hardware acceleration
and .NET framework 4.0. It also fully supports WPF (Windows Presentation Foundation).
As such, projects running on this platform will utilize vector based graphics.
iX Panels, like the TxA and TxB series, use Windows CE 6.0 as their operating system.
Only .NET 3.5 compact framework is included in these operator panels and as such, an
integrator is limited to this when scripting in his iX Developer project.
There is no support for WPF in these panels, and all vector based objects in the project are
bitmap converted when the project is compiled.
Page 1 (5)
KI_sv.dot, 130411


Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00

USA
Telephone +1 847 619 6068

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +46 40 93 23 01
Telefax +1 847 619 6674
Telefax +49 711 327 599 10
iX RT vs iX panels
KI00XXX 2013-04
iX RT license dongles are currently available in 3 different sizes: 250, 2000 and 4000 tags.
iX TxC series do not use dongles, they are delivered with an internal 4000 tag license,
except the IPC versions which do not have iX RT and license installed.
iX Panels use a different licensing solution and are do not have any tag limitations.
This does not mean that you can configure 4000 tags in entry level hardware like the TxA
series without a noticable performance hit.*
*Our recommendation for TxA is to use less than 1000 tags, if you need more you should consider upgrading to a TxB
Function availability depending on hardware platform

TxA
TxB/TAxx
TxC/PC
Vector graphics in
Runtime
No
No
Yes
Advanced
graphical effects
(shadow/opacity)
No
No
Yes
PDF viewer
No
Basic*
Yes
Web browser
No
Basic*
Yes
Object rotation
No
No
Yes
Screen rotation
Yes**
Yes
No***
*Only basic version available, no advanced functions available. No support for Flash/Shockwave/Java
functionallity in Basic web browser.
**Not available in T4A
***Not configurable in iX Developer project, but possible to change in Windows 7. Only landscape and
Landscape(flipped) work after a recalibration has been done. Currently, there is no support for Portrait or
Portrait(flipped) due to limitation in touch calibration.
Updating projects in RT and Panels

When new functionality is available in newer versions of iX Developer, image updates may
be required to take advantage of said functionality.
iX panels are updated using image loaders that are available on Beijer Electronics Help
Online. After the image update is complete, you can rebuild the design project in your new
version of iX Developer and download the project to the HMI.
Updating the communication drivers in the panels usually does not require an image update.
To update the communication drivers in the panels, download and install the drivers on your
designer PC, open the project and rebuild it.
KI_sv.dot, 130411
When rebuild is complete, download the project to the iX panel.
2 (5)
iX RT vs iX panels
KI00XXX 2013-04
iX RT on PCs behave differently.

First of all, the iX RT installation on the PC should be of the same version and build number
as the designer version and build number that is used to create the project.
So if you have a new iX Developer version that you are building your projects in, you should
also install the matching version of the iX RT software package.
When transfering the project to the iX RT PC, the communication drivers are not transferred,
you use the drivers that are included in the iX RT installation.
To update the driver on a iX RT PC, you must follow the procedure described in our iX
Developer Runtime start-up document, KI00336.
Functions not included in iX RT compared to iX Panels

The VNC server and FTP server are not available in iX PC and iX TxC projects.
It is still possible to install third party software to get this functionallity in a PC.
Examples of software that accomplishes this is Bulletproof FTP Server and RealVNC.
KI_sv.dot, 130411
Since TxC panels comes with Windows 7 Ultimate installed, it is also possible to configure
them for remote desktop usage with the built-in Remote Desktop functionality:
3 (5)
iX RT vs iX panels
KI00XXX 2013-04
The COM2 and COM4 ports on TxC panels does not support RS422.
This limitation is reflected in the design tool, where it is not possible to configure the ports
for anything other than RS485:
It is also not possible to configure region settings in TxC/PC projects:
It is possible to change the region settings directly in the TxC/PC instead.
KI_sv.dot, 130411
You can access this setting via the Control Panel in Windows:
4 (5)
iX RT vs iX panels
KI00XXX 2013-04
Explore the Clock, Language, and Region setting:
Press Change location to access the Location settings:
KI_sv.dot, 130411
Under Formats you find the different formats for Time and Date.
5 (5)
Start-Up
RESTful Web Service API
KI00334 2013-04

iX Developer provides an API for interacting with tags via the built-in Web Server. The tags can
be read from or written to using the HTTP verbs GET and POST. GET to read tags and POST to
perform batch operation. The API will typically be used when external applications wants to
read/write tag values from a panel/controller.
- iX Developer 2.0
- Chrome Web Browser
- Simple REST Client (Chrome Plugin)


documents.
KI_sv.dot, 090709


Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599 10
KI00334 2013-04
3 iX Settings
Create a Panel-project or a PC-project. This document is based on a Panel-project but the
same approach is applied to a PC-project.
Lets start by configuring iX and creating a layout. In this example the Demo controller is
used.
Select the System ribbon tab click on Web Server.
Check Enable Web Server and enter a port number, the default port is 80.
When Enable forms authentication is checked; Free definable username and password can
be set. The authentication is not encrypted, but sent in plain text.
When unchecked; Anonymous authentication is used.
KI_sv.dot, 090709
The Web Server will be active as soon as the application is running.
2 (7)
KI00334 2013-04
4 Install Simple REST Client

An easy way to test the API is to install a REST client. Most browsers provides this support
via a plugin.
In this sample we are using Chrome and a plugin called Simple REST Client.
Navigate to https://chrome.google.com/webstore/detail/simple-restclient/fhjcajmcbmldlhcimfajhfbgofnpcjmb
Click on the Add to Chrome button:
Click on the Add button:
KI_sv.dot, 090709
The plugin is now installed, just click on the small icon in order to activate it:
3 (7)
KI00334 2013-04
5 GET and POST

By using different verbs its possible to read and write tag values via the API.
5.1 GET Tags in application or specific tag

The GET verb allows the external application to retrieve a list of all tags running in the
application or information about a specific tag.
This can easily be tested by typing the following URL string in the client followed by
clicking on the Send button:
KI_sv.dot, 090709
The Web Server will reply with:
4 (7)
KI00334 2013-04
To retrieve information about a specific tag the URL string will need to be modified slightly:
KI_sv.dot, 090709
5 (7)

5.2
KI00334 2013-04
POST Read/Write tag batches

In order to read/write a batch of tags the POST verb can be used. The sample below will
receive information about Tag1 and Tag2:
KI_sv.dot, 090709
6 (7)
KI00334 2013-04
In order to write values to a batch of tags the URL string will need to be altered, refer to the
picture below:
KI_sv.dot, 090709
7 (7)
,3VHF931WXQQHOWRL;SDQHO
.,
)XQFWLRQDQGDUHDRIXVH
This document will explain how to set up a VPN tunnel between computer and iX-panel
using TheGreenBow IPsec VPN client software on the computer side and Westermo MRD350 3G router connected to the panel side.
Sofware requirements:
iX Developer
TheGreenBow IPsec VPN Client 5.1 Available as 30 days trail.

http://www.thegreenbow.com/vpn/vpn.html
Westermo MRD 3G router
PC running windows
$ERXWWKLV6WDUW8SGRFXPHQW
This Start Up document should not be considered as a complete manual. It is an aid to be
the manual for iX Developer.
This document and other Start Up documents can be obtained from your closest distributor
of operator terminals.
Please use the address manual@ beijer.se for feedback on our Start Up documents.
Page 1 (12)
KI_eng.dot, 070221
Beijer Electronics Automation AB a company in the Beijer Electronics Group

Parent Company (Reg. office)
Beijer Electronics Automation AB
P.O. Box 426
SE-201 24 MALM, SWEDEN
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Visitors address 6WRUD9DUYVJDWDQD, Malm
Reg no. 556701-3965 VAT no SE556701-3965-01, Internet www.beijer.se, e-mail info@beijer.se
Subsidiaries
Norway, Drammen: Beijer Electronics AS, +47 32 24 30 00
Finland, Helsinki: Beijer Electronics Oy, +358 207 46 35 40
Denmark, Copenhagen: Beijer Electronics A/S, +45 70 26 46 46
Estonia, Tallin: Beijer Electronics Eesti O, +372 6 518140
Latvia, Riga: Beijer Electronics SIA, +371 7 842280
Lithuania, Vilnius: Beijer Electronics UAB, +370 5 2323101
.,
'RFXPHQWFRQWHQWV
This is the setup for this start-up document:
The following software versions where used creating this document:
TheGreenBow version 5.1
MRD-350 firmware version 1.53
iX Developer 2.0 SP1
Windows XP SP3
KI_eng.dot, 070221
Make sure you have configured your MRD-3xx router as described in the User Guide before
continuing.
www.beijer.se
2 (12)
.,
KI_eng.dot, 070221
6HWWLQJXS7KH*UHHQ%RZ931FOLHQW
Open up TheGreenBow.
Click on Global Parameters and make sure Dead Peer Detection (DPD) is selected.
DPD monitors the status of the VPN tunnel.
www.beijer.se
3 (12)
KI_eng.dot, 070221
Create or open up phase 1. Set a suitable name. Enter parameters as follows.
Still under Gateway, click on Advanced tab. Enter the parameters as follows.
Save.
www.beijer.se
.,
4 (12)
Create Phase 2 by right clicking on Phase 1 and select New Phase 2.
Select Phase 2 and enter the parameters as follows.
.,
KI_eng.dot, 070221
The configuration of TheGreenBow is now complete.
www.beijer.se
5 (12)
.,
6HWWLQJXSWKH05'URXWHU
KI_eng.dot, 070221
Make sure you have configured your MRD-3xx router as described in the User Guide and
have working internet access.
Login to your MRD router and click on VPN to configure IPsec.
Click on Add new tunnel.
www.beijer.se
6 (12)
KI_eng.dot, 070221

.,
.($XWKHQWLFDWLRQ3KDVH
www.beijer.se
7 (12)
KI_eng.dot, 070221

.,
,.($XWKHQWLFDWLRQ3KDVH
Use the same settings as in Phase 2 in TheGreenBow.
Enable Dead Peer Detection (DPD).
Enable IPsec and click on Update.
www.beijer.se
8 (12)
KI_eng.dot, 070221
www.beijer.se
.,
9 (12)
Click on Access Control under Firewall and select to allow IPsecVPN.
Update.
.,
KI_eng.dot, 070221
Click on Status and you will notice that VPN is marked red with the text Fault. It will stay
this way as long as no VPN tunnel connection is correctly established.
www.beijer.se
10 (12)
.,
2SHQ931WXQQHO
When both the MRD router and TheGeenBow is correctly configurated, we can open the
tunnel.
Open up TheGreenBow and right click on Tunnel, select Open Tunnel.
A green light will indicate when tunnel is opened.
KI_eng.dot, 070221
Ping the panel to ensure panel connection.
www.beijer.se
11 (12)
.,
'RZQORDGLQJL;SURMHFW
When downloading iX-project to panel via VPN tunnel, the panel will not show in
Connected targets. Editing the target settings is, because of this, not possible.
KI_eng.dot, 070221
You have to enter the IP of the panel manually and click on Download.
www.beijer.se
12 (12)
iX TxB SoftControl
- FnIO-S NA-9173 / NA-9473 Modbus RTU
KI00331 2013-06

With the HMI soft controllers in the iX TxB SoftControl series, any HMI application can
have an intuitive graphic iX interface with total CoDeSys control.
The terminal iX TxB SoftControl communicates with a remote I/O (Crevis FnIO-S Serie) in
a Modbus RTU (serial) network.
2 About this Start Up document

able to start up a normal application quickly and easily.
Use the following software and drivers in order to obtain a stable application:
Programming software, Image, Driver (iX HMI to SoftController)
See StartUp document KI00326 (TxB SoftControl, Basic setting)
Driver, CoDeSys
x Modbus Com Ver 3.4.0.0, communication to Crevis remote I/O
x Modbus Master Ver 3.5.1.0, communication to Crevis remote I/O
x Modbus Slave Ver 3.5.1.0, communication to Crevis remote I/O
Library manager, CoDeSys
x Standard 3.5.1.0
In this document we have used following software
x CoDeSys 3.5 SP1 Patch 4 (compiler version 3.5.1.40)
x iX Developer 2.0 SP1
In this document we have used following hardware
x iX T7B SoftControl
x Remote I/O, Crevis FnIO-S Series, NA-9173 and I/O modules
For further information we refer to
x iX Developer Reference Manual (MAxx831)
x iX Developer User's Guide (MAxx832D)
x Driver help in iX Developer
x CoDeSys, Manuals and help in the software
This document and other Start Up documents can be obtained from our homepage.
Please use the address manual@beijer.se for feedback on our Start Up documents.
1 (31)
~2733497.dot, 130103
Beijer Electronics Automation AB a Beijer Electronics Group company

Head Office
Subsidiaries

P.O. Box 426, Stora Varvsgatan 13a
SE-201 24 Malm, SWEDEN
Telephone +46 40 35 86 00
Fax +46 40 93 23 01

Finland, Vantaa: Beijer Electronics Oy, +358 207 46 35 00
Denmark, Roskilde: Beijer Electronics A/S, +45 75 76 66
Estonia, Tallinn: Beijer Electronics Eesti O, +372 6 518140
Lithuania, Kaunas: Beijer Electronics UAB, +370 5 2323101
Reg no. 556701-3965 ~ VAT no SE556701396501 ~ www.beijer.se ~ info@beijer.se
iX TxB SoftControl - FnIO-S NA-9173 / NA-9473 Modbus RTU
KI00331 2013-06
Table of Contents
1 Function and area of use ..................................................................................................................................................1

2 About this Start Up document .........................................................................................................................................1
3 Table of Contents ..............................................................................................................................................................2
4 First step! ...........................................................................................................................................................................3
5 Program example ..............................................................................................................................................................3
6 Configuration of iX TxB SoftControl and Modbus RTU..............................................................................................4
6.1 CoDeSys project .........................................................................................................................................................4
6.2 Modbus Master...........................................................................................................................................................8
6.3 Modbus Slave, NA-9173, Example ...........................................................................................................................14
6.4 Global Variable List (for programming and export to iX Developer) .....................................................................15
6.5 Persistent variables (32 kbyte) .................................................................................................................................17
6.6 Write program in PLC_PRG................................................................................................................................19
6.7 Export Variables to iX HMI .....................................................................................................................................21
6.8 Transfer CoDeSys project to iX TxB SoftControl.....................................................................................................22
7 Getting started, iX Developer (iX TxB SoftControl) ...................................................................................................24
7.1 Rename the driver.....................................................................................................................................................24
7.2 Import of variables ...................................................................................................................................................25
7.3 iX Developer project.................................................................................................................................................28
7.4 Download iX project to iX T7B SoftControl.............................................................................................................28
~2733497.dot, 070221
8 Hardware iX TxB SoftControl, NA-9173 and NA-9473..............................................................................................29

8.1 Installation................................................................................................................................................................29
8.2 Dip Switch setting, NA-9173 ....................................................................................................................................30
www.beijer.se
2 (31)
KI00331 2013-06
4 First step!
Read StartUp document iX TxB SoftControl Basic setting, KI00328.
Prepare the computer and the programming tools CoDeSys and iX developer.
x
Add iX TxB SoftControl to CoDeSys
Add iX TxB SoftControl to iX Developer
Install the driver for iX HMI to the SoftControl
Note!
Always use the correct version of the drivers and software!
5 Program example
The folder ProgExample_TxB_SC_ModBusRTU contains the program example from this
StartUp document.
~2733497.dot, 070221
Download from homepage!
www.beijer.se
3 (31)
Configuration of iX TxB SoftControl and Modbus RTU
6.1
CoDeSys project
KI00331 2013-06
6.1.1 Programming and configuration of the SoftControl
~2733497.dot, 070221
Standard project
x
Start CoDeSys
Click File and Choose New project
In Templates, mark Standard project
In Name, write the name of the project
In Location write the library to save the project in
Click OK
www.beijer.se
4 (31)

x
KI00331 2013-06
Select Ladder Logic Diagram (LD)
6.1.2 How to add a POU

x Highlight the Application option in the Device window and right click
~2733497.dot, 070221
Select Add Object and choose POU.

Customize the POU according to desired characteristics.
www.beijer.se
5 (31)
KI00331 2013-06
6.1.3 How to add a Task

When a Standard project is selected, it automatically creates a "Main Task"
x
Highlight the Application option (to make a TaskCofiguration)

or highlight the TaskCofiguration (to make a Task
Select Add Object and choose Task Configuration or Task
Click Open, a task named Task is automatically created
~2733497.dot, 070221
6.1.4 How to add a POU to a Task

Connect the created POU to the task in order for the IEC code in the POU to get executed.
x
Open the MainTask
Under POUs, select Add POU
In the Items window, under Application, highlight desired POU and click OK
www.beijer.se
6 (31)
KI00331 2013-06
6.1.5 Add a Task for update the I/O

We need a task to trig read and write I/O status to the remote I/O.
x
Make a new task BusTask
Note!
The interval time depends on the application. A small application, set this task (BusTask) to
10 ms and the program task (MainTask) to 20 ms.
x
Add the BusTask to PLC setting
Double click at Device (TxB SoftControl) and select PLC setting
Set value like the picture
~2733497.dot, 070221
Note!
Before writing the PLC-program we need to configure the driver for communication with
the remote I/O (NA-9173 / NA-9473).
www.beijer.se
7 (31)

6.2
KI00331 2013-06
Modbus Master
~2733497.dot, 070221
The iX TxB SoftControl uses the driver Modbus Master to communicate with the slave
units. We have to config a Modbus device and connect Modbus Master and the Modbus
Slave node.
x
Highlight Device (TxB SoftControl) and right click
Click Add Device and mark Modbus COM (use versionlink)
Click at Add Device and Close
www.beijer.se
8 (31)
~2733497.dot, 070221
KI00331 2013-06
Highlight Modbus COM and right click
Click Add Device and mark Modbus Master, COM Port (use versionlink)
www.beijer.se
9 (31)
KI00331 2013-06
6.2.1 Modbus Slave

x
Highlight Modbus_Master_COM and right click
Click Add Device and mark Modbus Slave, COM Port (use versionlink)
~2733497.dot, 070221
Results
www.beijer.se
10 (31)
KI00331 2013-06
6.2.2 Setup the COM port

x Double click on Modbus_COM
x
COM 2 (support for COM 1, 2 and 3)

Baud Rate 115200, 8 Data Bit, None Parity, 1 Stop Bit
Note!
Setup the hardware NA-9173 / NA-9473 (link to hardware setting)
6.2.3 Config the Modbus Master
x Double click on Modbus_Master_COM_Port
x
Set Frame to 1 ms
6.2.4 Config the slave node

x Double click on Modbus_Slave_COM_Port
~2733497.dot, 070221
Set Slave Adress to 1
www.beijer.se
11 (31)
KI00331 2013-06
6.2.5 Config the Remote I/O

Select functioncode and data for read and write area to node.
x
Select Modbus Slave Channel and Add Channel
For this application, set like the picture and click OK .

More information in next chapter.
~2733497.dot, 070221
Results
www.beijer.se
12 (31)
KI00331 2013-06
~2733497.dot, 070221
6.2.6 Modbus addresses in CoDeSys

x Mark Always update varibles
www.beijer.se
13 (31)

6.3
KI00331 2013-06
Modbus Slave, NA-9173, Example

x
Analog input ST-3424, 4 channel 0-10 V
Analog output ST-4422, 2 channel 0-10 V
Digital input ST-1218 (8 channel), ST-1214 (4 channel)
Digital output ST-2328 (8 channel), ST-2524 (4 channel, with diagnostic)
6.3.1 Input and Output Register Map

x 6 register for input (address 0x0000 0x0005)
x
3 register for output (address 0x0800 0x0802)
Input Process Image (mode 2, default)

Addr.
0x0000
0x0001
0x0002
0x0003
0x0004
#15 #14 #13 #12 #11 #10 #9 #8

Analog Input Ch0 high byte (Slot#1)
Discrete In 4pts
Empty
Always 0
(Slot#4)
Diagnostic In 4pts
0x0005
Empty
Always 0
(Slot#7)
Output Process Image (mode 0, default)
#7 #6 #5 #4 #3 #2 #1 #0
Analog Input Ch0 low byte (Slot#1)
Discrete In 8 pts (Slot#3)
Empty
Always 0
Discrete In 4pts
(Slot#5)
Addr.
0x0800
0x0801
0x0802
#15 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4 #3 #2 #1 #0

Analog Output Ch0 high byte (Slot#2)
Analog Output Ch0 low byte Slot#2)
Discrete Out 4pts
Empty
Discrete Out 8pts (Slot#6)
(Slot#7)
0x = hex => 0x0800 = 800 hex
In our example we use Function Code 23 (Read/Write multiple register in one telegram).
~2733497.dot, 070221
If you change the function code to 04 (read input register) and code 16 (write multiple
register) there will be two telegram to the slave node.
www.beijer.se
14 (31)

6.4
KI00331 2013-06
Global Variable List (for programming and export to iX Developer)
6.4.1 Global Variable list

x Highlight the Application entry in Devices
x Right click and select Add Object
x Choose Global Variable List
x Name: GVL and click Open
~2733497.dot, 070221
Write global name for the I/O.

The global name should be connected in Modbus Slave I/O-Mapping.
www.beijer.se
15 (31)
~2733497.dot, 070221
KI00331 2013-06
Write global name for memory cells and register (without battery backup)
www.beijer.se
16 (31)

6.5
KI00331 2013-06
Persistent variables (32 kbyte)
~2733497.dot, 070221
Persistent variables (battery powered) can ONLY be declared in a special global variables
list of object type, which is assigned to an application. There might be only ONE such list
per application.
x
x
x
x
Highlight the Application entry in Devices

Right click and select Add Object
Choose PersistentVars
In next PopUp write the Name PersistentVars and click Open
Write Persistent Variables (with battery backup)
www.beijer.se
17 (31)
KI00331 2013-06
6.5.1 I/O Mapping, Modbus Generic Serial Slave

x Input (digital and analog)
~2733497.dot, 070221
Output (digital and analog)
www.beijer.se
18 (31)
~2733497.dot, 070221
6.6
KI00331 2013-06
Write program in PLC_PRG
www.beijer.se
19 (31)

x
Rebuild the program
If no Error, go to next step!

View error, warning and message with view \ Messages
KI00331 2013-06
~2733497.dot, 070221
NOTE!
x
This warning are OK
When Generate code there can be warning like the picture.

Its only a warning. The project is working correct.
Compiler warning like C0308 can be not checked.

Menu Project \Project setting\Compiler warning\.
www.beijer.se
20 (31)

6.7
KI00331 2013-06
Export Variables to iX HMI

In Codesys we have to make a XML file for import to iX Developer.
In order to be able to export application variables from CoDeSys to iX HMI a
Symbol configuration is needed.
~2733497.dot, 070221
The XML file for iX Developer is created when you transfer the project to the iX TxB
SoftControl or Generate code in menu Build. The file is saved in same library as the
CoDesys project.
x
Choose Symbol configuration
Enter chosen name in the Name option and click Open
Mark GVL and move with >. Do the same with Persistent
www.beijer.se
21 (31)
KI00331 2013-06
6.8 Transfer CoDeSys project to iX TxB SoftControl

A gateway needs to be created in order to communicate between the PC and the HMI.
x
Double click the TxB SoftControl option under Devices
Select the Communication setting options
If no gateway present, create one by selecting Add Gateway (choose default value)
Highlight the gateway
Press Scan network and wait until scanning is done
All CoDeSys devices on the network will be listed below the gateway.
The last two number (11) in the id [004F.C011] are the last group in ip-adress
(Hex 11: Dec 17).
~2733497.dot, 070221
NOTE!
If you dont find your CoDeSys devices, try to Add Device
www.beijer.se
22 (31)
~2733497.dot, 070221
KI00331 2013-06
Select the device that the project will be downloaded to and press Set active path.
This device will be highlighted by a bold font.
Download the project to the device (TxB SoftControl) which was selected above
menu Online select Login.
The project will now be downloaded to the device
Set the PLC (SoftController) to RUN with F5 or the symbol
When all are green (see picture), the SoftController is running!
www.beijer.se
23 (31)
KI00331 2013-06
Getting started, iX Developer (iX TxB SoftControl)

Setup an iX application
~2733497.dot, 070221
7.1
In the start-up wizard, select Create New Project
Choose the iX TxB SoftControl panel size on which the application will run (iX T7B
SoftControl in this example)
Click Next
Select the driver. The brand is CoDeSys and the protocol is SoftControl Direct
Access
Click Next
Enter the name and the path of the project
Click Finish
Rename the driver

x
In Functions, double click the Tags option and open Controllers
Change the name to SoftController
www.beijer.se
24 (31)

7.2
KI00331 2013-06
Import of variables
~2733497.dot, 070221
7.2.1 At this stage, it is time to import the variables that were exported from CoDeSys
x In Functions, double click the Tags option
x
In the window, choose the Import tags to option
Select the CoDeSys V3 import format (Import Modules) and browse to the location
where the CoDeSys project is saved
Choose the xml file with the same name as the CoDeSys project and press Open.
Mark Connect selected import file to project.
Select Import or Refresh
Select All items and press OK
Press OK in the Import Completed dialog
The imported variable(s) should now be featured in the Tags list
www.beijer.se
25 (31)
KI00331 2013-06
7.2.2 Import rules for connected import file

The import module makes it possible to import symbols and structs from XML export files
generated by CoDeSys.
x
Click on . to add rules for import
~2733497.dot, 070221
Function in Import module

x
This would import all tags starting with application or which included the text HMI
Click Import to Select Tags to import
www.beijer.se
26 (31)
KI00331 2013-06
7.2.3 Timeout settings for the connection to SoftController

x In the Controllers folder, select the Settings option
x
In the dialog, choose Settings
Check the settings.

This picture has default value.
~2733497.dot, 070221
Timeout and Driver help
www.beijer.se
27 (31)

7.3
KI00331 2013-06
iX Developer project
Add and configure a project in iX Developer.
x
7.4
You can copy from the example project
Download iX project to iX T7B SoftControl
~2733497.dot, 070221
Finally download the iX project to the device

x
Menu Project
Select Download
After the validation is performed, a screen with the available devices appears.
Highlight the chosen one and press Download.
After download, the HMI application starts up and communicates with the iX TxB
SoftControl.
www.beijer.se
28 (31)
KI00331 2013-06
Hardware iX TxB SoftControl, NA-9173 and NA-9473
8.1 Installation
Connect iX TxB SoftControl to NA-9173 / NA-9473 like the picture.
The iX TxB SoftControler support com 1, 2 and 3.
iX TxB-SC
NA-9173
120 :
120 :
iX TxB-SC
NA-9473
120 :
~2733497.dot, 070221
120 :
Use CAB112 to connect iX TxB SoftControl with NA-9173 / NA-9473
www.beijer.se
29 (31)
KI00331 2013-06
8.2 Dip Switch setting, NA-9173

Set the slave address to 1:
- MSD (X10) set to 0
- LSD (X1) set to 1
~2733497.dot, 070221
Communication (SW1-4:ON, SW5-8:OFF)

COM 2, Baud Rate 115200, Enable Watchdog, 8 Bit, None Parity,
1 Stop Bit, RTU mode
www.beijer.se
30 (31)
KI00331 2013-06

The dip switches are placed at left side of NA-9473
Set Node adress to 1 (SW1, 1:ON, 2-4:OFF)
Set Baudrate to 115200, RTU mode (SW2, 1-3:ON, 4:OFF)
~2733497.dot, 070221
NOTE!
Byte Format are fixed to: 8 Bit, No Parity, 1 Stop Bit
www.beijer.se
31 (31)
iX TxB SoftControl - FnIO-S NA-9189 Modbus TCP
KI00330 2013-06

The terminal iX TxB SoftControl communicates with a remote I/O (Crevis FnIO-S Serie) in
a Modbus TCP network.

See StartUp document KI00326 (iX TxB SoftControl, Basic setting)
Driver, CoDeSys
x Ethernet Adapter Ver 3.4.2.0, communication to Crevis remote I/O
x Modbus TCP Master Ver 3.5.1.0, communication to Crevis remote I/O
x Modbus TCP Slave Ver 3.5.1.0, communication to Crevis remote I/O
x Standard 3.5.1.0
1 (29)
~2733497.dot, 130103

Head Office
Subsidiaries

Telephone +46 40 35 86 00
Fax +46 40 93 23 01

KI00330 2013-06
Table of Contents

4 First step! ...........................................................................................................................................................................3
5 Program example ..............................................................................................................................................................3
6 Configuration of iX TxB SoftControl and Modbus TCP ..............................................................................................4
6.1 CoDeSys project .........................................................................................................................................................4
6.2 Modbus Master...........................................................................................................................................................8
7.4 Download iX project to iX T7B SoftControl.............................................................................................................28
~2733497.dot, 070221
8 Hardware iX TxB SoftControl, NA-9189 .....................................................................................................................29

8.1 Installation................................................................................................................................................................29
www.beijer.se
2 (29)
KI00330 2013-06
4 First step!
x
Note!
5 Program example
The folder ProgExample_TxB_SC_ModBusTCP contains the program example from this
StartUp document.
~2733497.dot, 070221
www.beijer.se
3 (29)
Configuration of iX TxB SoftControl and Modbus TCP
6.1
CoDeSys project
KI00330 2013-06
~2733497.dot, 070221
Standard project
x
Start CoDeSys
Click OK
www.beijer.se
4 (29)

x
KI00330 2013-06

~2733497.dot, 070221

www.beijer.se
5 (29)
KI00330 2013-06

x

~2733497.dot, 070221

x
Open the MainTask
www.beijer.se
6 (29)
KI00330 2013-06

x
Note!
The interval time depends on the application. A small application, set this task (BusTask) to
10 ms and the program task (MainTask) to 20 ms.
x
Double click at Device (iX TxB SoftControl) and select PLC setting
~2733497.dot, 070221
Note!
the remote I/O (NA-9189).
www.beijer.se
7 (29)

6.2
KI00330 2013-06
Modbus Master
~2733497.dot, 070221
The iX TxB SoftControl uses the driver Ethernet to communicate with the slave units.
We have to config a Ethernet device and connect Modbus Master and the Modbus Slave
node.
x
Highlight Device (iX TxB SoftControl) and right click
Click Add Device and mark Ethernet (use versionlink)
www.beijer.se
8 (29)
~2733497.dot, 070221

x
Highlight Ethernet and right click
Click Add Device and mark Modbus TCP Master (use versionlink)
www.beijer.se
KI00330 2013-06
9 (29)
KI00330 2013-06
6.2.1 Modbus Slave

x
Highlight Modbus_TCP_Master and right click
Click Add Device and mark Modbus TCP Slave (use versionlink)
~2733497.dot, 070221
Results
www.beijer.se
10 (29)
KI00330 2013-06

x Double click on Modbus_TCP_Master
x
Set like picture (auto-reconnect restart communication with slave(s))

x Double click on Modbus_TCP_Slave
~2733497.dot, 070221
Set like picture
www.beijer.se
11 (29)
KI00330 2013-06

Select function code and data for read and write area to node.
x

~2733497.dot, 070221
Result
www.beijer.se
12 (29)
KI00330 2013-06
~2733497.dot, 070221

All variables status are updated (even those that are not used in the program)
www.beijer.se
13 (29)

6.3
KI00330 2013-06

x

x

Addr.
0x0000
0x0001
0x0002
0x0003
0x0004
#15 #14 #13 #12 #11 #10 #9 #8

Empty
Discrete In 4pts
Always 0
(Slot#4)
Diagnostic In 4pts
0x0005
Empty
Always 0
(Slot#7)
#7 #6 #5 #4 #3 #2 #1 #0
Empty
Always 0
Discrete In 4pts
(Slot#5)
Addr.
0x0800
0x0801
0x0802
#15 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4 #3 #2 #1 #0

Empty
Discrete Out 4pts
(Slot#7)
0x = hex => 0x0800 = 800 hex
~2733497.dot, 070221
www.beijer.se
14 (29)

6.4
KI00330 2013-06

~2733497.dot, 070221

www.beijer.se
15 (29)
~2733497.dot, 070221
KI00330 2013-06
www.beijer.se
16 (29)

6.5
KI00330 2013-06
~2733497.dot, 070221
per application.
x
x
x
x

www.beijer.se
17 (29)
KI00330 2013-06

~2733497.dot, 070221
www.beijer.se
18 (29)
~2733497.dot, 070221
6.6
KI00330 2013-06
www.beijer.se
19 (29)

x
Rebuild the program

KI00330 2013-06
~2733497.dot, 070221
NOTE!
x
This warning are OK


www.beijer.se
20 (29)

6.7
KI00330 2013-06

~2733497.dot, 070221
The XML file for iX Developer is created when you transfer the project to the TxB
CoDesys project.
x
www.beijer.se
21 (29)
KI00330 2013-06

x
(Hex 11: Dec 17).
~2733497.dot, 070221
NOTE!
www.beijer.se
22 (29)
~2733497.dot, 070221
KI00330 2013-06
www.beijer.se
23 (29)
KI00330 2013-06
Getting started, iX Developer (iX TxB SoftControl)

~2733497.dot, 070221
7.1
Choose the iX TxB SoftControl panel size on which the application will run (iX T7B
Click Next
Access
Click Next
Click Finish
Rename the driver

x
www.beijer.se
24 (29)

7.2
KI00330 2013-06
Import of variables
~2733497.dot, 070221
x
www.beijer.se
25 (29)
KI00330 2013-06

x
~2733497.dot, 070221

x
www.beijer.se
26 (29)
KI00330 2013-06

x
Check the settings.

~2733497.dot, 070221
www.beijer.se
27 (29)

7.3
KI00330 2013-06
x
7.4
Download iX project to iX T7B SoftControl
~2733497.dot, 070221

x
Menu Project
Select Download
SoftControl
www.beijer.se
28 (29)
KI00330 2013-06
Hardware iX TxB SoftControl, NA-9189
8.1 Installation
x
Connect iX TxB SoftControl to NA-9189 like the picture (LAN A)
Standard RJ-45 cable
24 VDC COM 1/2 LAN A USB
LAN B
COM 3/4
~2733497.dot, 070221
TCP
www.beijer.se
29 (29)
iX TxB SoftControl FnIO-S NA-9186 EtherCAT
KI00329 2013-06

The terminal TxB SoftControl communicates with a remote I/O (Crevis FnIO-S Serie) in a
EtherCAT network.

x See StartUp document KI00328 (TxB SoftControl, Basic setting)
Driver, CoDeSys
x EtherCAT Ver 3.5.1.0, communication to Crevis remote I/O
Device description, Crevis NA-9186
x Crevis_EtherCAT_V1.000.xml, I/O moduls for configuration
x Standard 3.5.1.0
1 (28)
~2733497.dot, 130103

Head Office
Subsidiaries

Telephone +46 40 35 86 00
Fax +46 40 93 23 01

KI00329 2013-06
3 Table of Contents
4 First step! ...........................................................................................................................................................................3
5 Program example ..............................................................................................................................................................3
6 Configuration of iX TxB SoftControl and EtherCAT...................................................................................................4
6.1 CoDeSys project .........................................................................................................................................................4
6.2 EtherCAT Master........................................................................................................................................................7
6.3 Configure the Task for update the I/O........................................................................................................................8
6.4 Install device description file for Crevis FnIO-S Series, NA-9186.............................................................................9
6.7 I/O Mapping, EtherCAT NA-9186............................................................................................................................17
6.8 Write program, POU PLC_PRG..........................................................................................................................18
7.4 Download iX project to T7B SoftControl .................................................................................................................27
~2733497.dot, 070221
8 Hardware iX TxB SoftControl, NA-9186 .....................................................................................................................28

8.1 Installation................................................................................................................................................................28
www.beijer.se
2 (28)
KI00329 2013-06
4 First step!
x
Note!
5 Program example
The folder ProgExample_TxB_SC_EtherCAT contains the program example from this
StartUp document.
~2733497.dot, 070221
www.beijer.se
3 (28)
KI00329 2013-06
6 Configuration of iX TxB SoftControl and EtherCAT

6.1
CoDeSys project
~2733497.dot, 070221
Standard project
x
Start CoDeSys
In Location write the folder to save the project in
Click OK
www.beijer.se
4 (28)

x
KI00329 2013-06

~2733497.dot, 070221

www.beijer.se
5 (28)
KI00329 2013-06

x

~2733497.dot, 070221

x
Open the MainTask
www.beijer.se
6 (28)

6.2
KI00329 2013-06
EtherCAT Master
~2733497.dot, 070221
The iX TxB SoftControl uses the driver EtherCAT Master to communicate with the slave
units.
x
Highlight Device (iX TxB SoftControl) and right click
Click Add Device and mark EtherCAT Master (use versionlink)
Result (the task EtherCAT_Master are created automatically)
www.beijer.se
7 (28)

6.3
KI00329 2013-06
Configure the Task for update the I/O

Task EtherCAT_Master are used for update the remote I/O.
x
Double click at EtherCAT_Master
Add the task EtherCAT_Master to PLC setting

x
Double click at Device (TxB SoftControl) and select PLC setting
~2733497.dot, 070221
Note!
the remote I/O.
www.beijer.se
8 (28)

6.4
KI00329 2013-06
Install device description file for Crevis FnIO-S Series, NA-9186
~2733497.dot, 070221
The configuration file xml are used for setting up the I/O moduls from Crevis FnIO-S
Series. The file can be found in Start-kit in KI00328.
x
Install Crevis_EtherCAT_V1.xxx.xml to CoDeSys (use versionlink)
Select EtherCAT XML Device description.
Select Crevis_EtherCAT_V1.xxx.xml and Open
The file is installed in EtherCAT\Slave...
www.beijer.se
9 (28)
KI00329 2013-06
6.4.1 Configure the EtherCAT connection

x Double click on EtherCAT_Master
x
Set value like picture
Note!
- The iX TxB SoftControl network port (LAN B) use the name TxB EtherCAT (LAN B).
- Autoconfig Master/Slave will open som usable parameters for monitoring in tab
EtherCAT Configuration. The function can be disable/enable in Tools\Options\Device
editor.
- The function Auto restart slaves disable/enable start of comminication to a node after
communication error.
When the computer (CoDeSys) are connected to the iX TxB SoftControl
~2733497.dot, 070221
Use Browse to find the TxB-SC
www.beijer.se
10 (28)
KI00329 2013-06
~2733497.dot, 070221
6.4.2 EtherCAT Slave node

x Highlight EthetCAT_Master and right click
x
Click Add Device and mark NA-9186 EtherCAT Adapter, Crevis

(use versionlink)
Click Add Device and Close
Result
www.beijer.se
11 (28)
KI00329 2013-06
~2733497.dot, 070221
6.4.3 Connection I/O modules

x Highlight NA_9186_Crevis, right click and click on Add Device
x
Select the modules to add, dubbel click or click on Add Device
All selected? Then Click Close
Highlight ST_1214_1 and right click then click on Properties
Change the name to ST_1214_2 and ST_1214 to ST-1214_1
www.beijer.se
12 (28)
KI00329 2013-06
~2733497.dot, 070221
6.4.4 EtherCAT addresses in CoDeSys

www.beijer.se
13 (28)

6.5
KI00329 2013-06

~2733497.dot, 070221

The global name should be connected in EtherCAT I/O Mapping.
www.beijer.se
14 (28)
~2733497.dot, 070221
KI00329 2013-06
www.beijer.se
15 (28)

6.6
KI00329 2013-06
~2733497.dot, 070221
per application.
x
x
x
x

Choose PersistentVariables
www.beijer.se
16 (28)

6.7
I/O Mapping, EtherCAT NA-9186

x
~2733497.dot, 070221
KI00329 2013-06
Output module in red (digital and analog) and Input module in green (digital and analog)
www.beijer.se
17 (28)
~2733497.dot, 070221
6.8
KI00329 2013-06
Write program, POU PLC_PRG
www.beijer.se
18 (28)

x
Rebuild the program

KI00329 2013-06
~2733497.dot, 070221
NOTE!
x
This warning is OK

Compiler warning like C0308 can be unchecked.

www.beijer.se
19 (28)

6.9
KI00329 2013-06

~2733497.dot, 070221
The XML file for iX Developer is created when you transfer the project to the iX TxB
CoDesys project.
x
www.beijer.se
20 (28)
KI00329 2013-06

x
(Hex 11: Dec 17).
~2733497.dot, 070221
NOTE!
www.beijer.se
21 (28)
~2733497.dot, 070221
KI00329 2013-06
www.beijer.se
22 (28)
KI00329 2013-06
7 Getting started, iX Developer (iX TxB SoftControl)

~2733497.dot, 070221
7.1
Choose the iX TxB SoftControl panel size on which the application will run (T7B
Click Next
Access
Click Next
Click Finish
Rename the driver

x
www.beijer.se
23 (28)

7.2
KI00329 2013-06
Import of variables
~2733497.dot, 070221
7.2.1 At this stage, its time to import the variables that exported from CoDeSys
x
www.beijer.se
24 (28)
KI00329 2013-06

x
~2733497.dot, 070221

x
www.beijer.se
25 (28)
KI00329 2013-06

x
Check the settings.

~2733497.dot, 070221
www.beijer.se
26 (28)

7.3
KI00329 2013-06
x
7.4
Download iX project to T7B SoftControl
~2733497.dot, 070221

x
Menu Project
Select Download
SoftControl
www.beijer.se
27 (28)
KI00329 2013-06
8 Hardware iX TxB SoftControl, NA-9186

8.1 Installation
x
Connect iX TxB SoftControl to NA-9186 like the picture
Standard RJ-45 cable
~2733497.dot, 070221
24 VDC COM 1/2 LAN A USB LAN B COM 3/4
www.beijer.se
28 (28)
iX TxB SoftControl, Basic setting
KI00328 2013-06

The SoftController communicate with an external device, for example Remote I/O.

Programming software
x iX Developer 2.0 SP1 (b 2.0.463.0) or later, programming the HMI in iX TxB
SoftControl
x TxB SoftControl setup(.msi), enable iX TxB SoftControl in iX Developer
x CoDeSys 3.5 SP1 Patch 4 or later, programming the SoftControl (Compiler 3.5.1.40)
Image, iX TxB SoftControl
x IML_TxB_b0138(.exe)
Driver, iX TxB SoftControl
x CoDeSys_SoftControl_Direct_Access ver 4.01.02, driver iX HMI with SoftController
Device description, iX TxB SoftControl
x TxB-SoftControl.devdesc(.xml) version 3.5.1.45, enable iX TxB SoftControl in
CoDeSys
Device description, CREVIS EtherCAT NA-9186
x Crevis_EtherCAT_V1.000.xml, enable NA-9186 in CoDeSys
x Standard 3.5.1.0
Driver version for communication to Remote I/O
x StartUp document: KI00329 EtherCAT, KI00330 ModbusTCP, KI00331Modbus RTU
1 (15)
~2733497.dot, 130103

Head Office
Subsidiaries

Telephone +46 40 35 86 00
Fax +46 40 93 23 01

KI00328 2013-06

~2733497.dot, 070221
www.beijer.se
2 (15)
KI00328 2013-06
3 Table of Contents
4 Configuration of CoDeSys and iX Developer .................................................................................................................4
4.1 Add iX TxB SoftControl to CoDeSys ..........................................................................................................................4
4.2 Add iX TxB SoftControl to iX Developer....................................................................................................................5
4.3 Install the driver for iX HMI to the SoftControl .........................................................................................................5
5 iX TxB SoftControl connections ......................................................................................................................................6
6 Communication between iX HMI, iX TxB SoftControl and Remote I/O ...................................................................7
7 Programming tools............................................................................................................................................................7
8 Persistent variables (32 kbyte) .........................................................................................................................................9
9 Important settings...........................................................................................................................................................10
9.1 Boot after Online Change and Restart of iX TxB SoftControl..................................................................................10
10 Project backup ................................................................................................................................................................11
10.1 CoDeSys, Create backup files ..................................................................................................................................11
10.2 CoDeSys, Project Archive ........................................................................................................................................11
10.3 CoDeSys, Sourse Download to iX TxB SoftControl .................................................................................................11
10.4 CoDeSys project to iX TxB SoftControl using USB memory....................................................................................12
11 Diagnostic, SoftController..............................................................................................................................................13
~2733497.dot, 070221
12 Files in Start-kit...........................................................................................................................................................15
12.1 Device Description iX TxB .......................................................................................................................................15
12.2 Device Description Crevis NA9186..........................................................................................................................15
12.3 CoDeSys SoftControl Direct Access.........................................................................................................................15
12.4 iX TxB SoftControl image.........................................................................................................................................15
12.5 iX TxB SoftControl to iX...........................................................................................................................................15
12.6 Diagnostic Tag .........................................................................................................................................................15
www.beijer.se
3 (15)
KI00328 2013-06
4 Configuration of CoDeSys and iX Developer

This installation has to be done once for every computer.
~2733497.dot, 070221
4.1

x
Change Standard to Professional
Install iX TxB SoftControl (Device description file) to CoDeSys

(iX TxB_SoftControl.devdesc.xml) (use versionlink)
The file is installed under PLCs
www.beijer.se
4 (15)

4.2
KI00328 2013-06

To get the iX TxB SoftControl terminals in iX Developer.
Run the file: TxB SoftControl Setup.msi.
x
4.3
Double click on the TxB SoftControl Setup.msi file to install

The driver (CoDeSys_SoftControl_Direct_Access) is installed with iX Developer.
Update the driver
x
To update the driver, you should be logged in as administrator.

Right-click the icon for iX and select "run as administrator".
Start iX developer and make a T7B SoftControl project (dont select any driver) or start
a demo project
Click on the symbol under iX in the upper left corner of the program
Select Update Drivers, then Update Drivers From File or Internet
Update from file

x
Browse to the location where the driver is found
Highlight the CoDeSys_SoftControl_Direct_Access_Pre2.mpd file and press Open
Highlight the driver in the new window and press Install
~2733497.dot, 070221
Once installed, re-start iX Developer

Note!
The installation of the driver needs only to be done once for every computer running iX.
www.beijer.se
5 (15)
KI00328 2013-06
5 iX TxB SoftControl connections
24 VDC COM 1/2 LAN A USB
LAN B
COM 3/4
RTU
TCP
Ethernet
Modbus
EtherCAT
~2733497.dot, 070221
Note!
The Ethernet port "LAN B" is always dedicated to the EtherCAT driver (even when the
EtherCAT driver is not used in the application).
LAN B can not be used for other functions such as Modbus TCP or downloading of iXDeveloper or CoDeSys-project.
www.beijer.se
6 (15)
KI00328 2013-06
6 Communication between iX HMI, iX TxB SoftControl and

Remote I/O
The terminal uses two drivers for communication between iX HMI, iX TxB SoftControl and
remote I/O.
Driver 1: iX HMI application with iX TxB SoftControl (CoDeSys SoftControl Direct
Access)
Driver 2: iX TxB SoftControl with Remote I/O
EtherCAT on LAN B, Modbus TCP on LAN A, Serial Modbus RTU at COM 1, 2 or
3.
TxB SoftControl
Example:
Crevis FnIO-S Series
Driver 1
iX-driver
iX HMI
application
Direct
access
Driver 2
SoftControl
~2733497.dot, 070221
7 Programming tools
x
iX Developer for iX HMI application
CoDeSys for the SoftControl
www.beijer.se
7 (15)
KI00328 2013-06
TxB SoftControl
iX HMI
application
SoftControl
EtherCAT
Modbus TCP/RTU
~2733497.dot, 070221
Ethernet
www.beijer.se
8 (15)
KI00328 2013-06
8 Persistent variables (32 kbyte)
~2733497.dot, 070221
per application.
x
x
x
x

Choose PersistentVariables..
Persistent variables, function.

iX TxB SoftControl supports Persistent variables.
www.beijer.se
9 (15)
KI00328 2013-06
9 Important settings
9.1
Boot after Online Change and Restart of iX TxB SoftControl

This must be done to make a safe restart after power off.
In other case the CoDeSys project have to be downloaded again.
x
Highlight the Application option in the Device window and right click
Select Properties and Boot application
~2733497.dot, 070221
Default setting in iX TxB SoftControl
www.beijer.se
10 (15)
KI00328 2013-06
10 Project backup
10.1 CoDeSys, Create backup files
If this option is activated, at each saving the project will not only be saved in
<projectname>.project but also copied to a file <projectname>.backup.
If needed you can rename this backup-file and re-open in CoDeSys.
Menu \Tools\Options
10.2 CoDeSys, Project Archive

The best way to get all components from a CoDeSys project is to make a Save/Send
Archive. That will save and pack all files referenced by and used within the currently
opened project in to one archive file. The archive file can either be stored or sent as
attachment of an email. The archive file can easily be unpacked by use of Extract Archive
Note! The archive function is not intended for restoring a project environment.
It is designed for an easy packing of all files belonging to a project!
10.3 CoDeSys, Sourse Download to iX TxB SoftControl

The CoDeSys project can be saved in the terminal and uploaded to CoDeSys.
Upload / Download
~2733497.dot, 070221
Project setting
Alternative to upload the archive.prj file

www.beijer.se
11 (15)
KI00328 2013-06
10.4 CoDeSys project to iX TxB SoftControl using USB memory

It is possible to export a CoDeSys project and then save it in the root on a USB memory
stick. If booting the iX TxB SoftControl panel with the USB memory plugged in it should be
possible to upload the CoDeSys project from the USB memory to the iX TxB SoftControl.
Note! SD memory can also be used.
Export project from CoDeSys programming tool
x
In menu Online select Create boot application and save the project files (.app/.crc)
in the root of the USB memory
Copy CoDeSys project from USB to iX TxB SoftControl

x
Restart the iX TxB SoftControl panel with USB memory
You will be asked if you wish to load the CoDeSys project

Copy PLC project from USB memory?
Important note!
x
When download a CoDeSys project the SoftControl memory will be cleared!

Also the Persistent area (the battery powered memorycells and register)
Tip!
~2733497.dot, 070221
Its also possible to download the iX Developer project in same way!
www.beijer.se
12 (15)
KI00328 2013-06
11 Diagnostic, SoftController
The driver supports some diagnostics tags, for example the RUN-state of the controller
application. These tags are all addressed by the prefix "Diagnostics.", which is why tags
which start with "Diagnostics." can't be used in the controller application.
All diagnostics tags are listed below.
Up to 20 Tasks are supported and can be addressed by changing the task-number in the tagsyntax between 0-19. For example the name of task 6 (the seventh since the number begins
at 0) is addressed with Diagnostics.Task6.Name.
All diagnostics times and intervals are given in microseconds.
x
From example project
~2733497.dot, 070221
Diagnostic and RUN / STOP of the SoftControl
www.beijer.se
13 (15)
KI00328 2013-06
~2733497.dot, 070221
Tip!
Import Diagnostic Tag to your project:
- Import the following file: T7B_SC_NA91xx_Ex1_Diagnostic_TagsImport_To_iX.txt.
You find the file in library StartKit_TxB_SoftControl\DiagnosticTag\..
www.beijer.se
14 (15)
KI00328 2013-06
12 Files in Start-kit
The folder in StartKit_TxB_SoftControl contains the latest files to prepare
iX TxB SoftControl.
12.1 Device Description iX TxB

Files:
- TxB-SoftControl.devdesc.xml*
- T7B.bmp
Enable iX TxB SoftControl in CoDeSys.
12.2 Device Description Crevis NA9186

File:
- Crevis_EtherCAT_V1.xxx.xml*
Enable NA-9186 in CoDeSys.
12.3 CoDeSys SoftControl Direct Access

Files:
- CoDeSys_SoftControl_Direct_Access_Pre2.mpd
- CoDeSys_SoftControl_Direct_Access_Pre2.cab
HMI Driver, iX application with iX TxB SoftControl. Use update driver in iX developer.
12.4 iX TxB SoftControl image

File:
- IML_TxB_b0xxx.exe*
Latest image for iX TxB SoftControl.
12.5 iX TxB SoftControl to iX

File:
- TxB SoftControl Setup.msi
Enable iX TxB SoftControl in iX Developer 2.0 SP1.
12.6 Diagnostic Tag

File:
- T7B _SC_NA91xx_Ex1_Diagnostic_TagsImport_To_iX.txt
Import of Diagnostic Tag to your project
~2733497.dot, 070221
*, use versionlink
www.beijer.se
15 (15)
iX TxA SoftControl
- FnIO-S NA-9173 / NA-9473 Modbus RTU
KI00327 2013-05

With the HMI soft controllers in the iX TxA SoftControl series, small HMI application can
The terminal iX TxA SoftControl communicates with a remote I/O (Crevis FnIO-S Serie) in
a Modbus RTU (serial) network.

x See StartUp document KI00326 (iX TxA SoftControl, Basic setting)
Driver, CoDeSys
x Modbus Com Ver 3.4.0.0, communication to Crevis remote I/O
x Modbus Master Ver 3.5.1.0, communication to Crevis remote I/O
x Modbus Slave Ver 3.5.1.0, communication to Crevis remote I/O
x Standard 3.5.1.0
x iX T7A SoftControl
1 (31)
KI_eng.dot, 130103

Head Office
Subsidiaries

Telephone +46 40 35 86 00
Fax +46 40 93 23 01

TxA SoftControl - FnIO-S NA-9173 / NA-9473 Modbus RTU
KI00327 2013-05
Table of Contents

4 First step! ...........................................................................................................................................................................3
5 Files in ProgExample_TxA_SC_ModbusRTU ...........................................................................................................3
6 Configuration of iX TxA SoftControl and Modbus RTU .............................................................................................4
6.1 CoDeSys project .........................................................................................................................................................4
6.2 Modbus Master...........................................................................................................................................................8
6.8 Transfer CoDeSys project to iX TxA SoftControl.....................................................................................................22
7 Getting started, iX Developer (iX TxA SoftControl) ...................................................................................................24
7.4 Download iX project to T7A SoftControl .................................................................................................................28
KI_eng.dot, 070221
8 Hardware iX TxA SoftControl, NA-9173 and NA-9473..............................................................................................29

8.1 Installation................................................................................................................................................................29
www.beijer.se
2 (31)
KI00327 2013-05
4 First step!
Read StartUp document iX TxA SoftControl, Basic setting, KI00326.
x
Add iX TxA SoftControl to CoDeSys
Add iX TxA SoftControl to iX Developer
Note!
5 Files in ProgExample_TxA_SC_ModbusRTU
The folder in ProgExample_TxA_SC_ModbusRTU contains the program example from
this StartUp document.
KI_eng.dot, 070221
www.beijer.se
3 (31)
Configuration of iX TxA SoftControl and Modbus RTU
6.1
CoDeSys project
KI00327 2013-05
KI_eng.dot, 070221
Standard project
x
Start CoDeSys
Click OK
www.beijer.se
4 (31)
KI00327 2013-05
6.1.2 How to add a POU project

KI_eng.dot, 070221

www.beijer.se
5 (31)
KI00327 2013-05

x

KI_eng.dot, 070221

x
Open the Task task
In the Items window, under Application, highlight POU and click OK
www.beijer.se
6 (31)
KI00327 2013-05

x
Note!
The interval time depends on the application. A small application, set this task to 10 ms and
the program task to 20 ms.
x
Double click at Device (TxA SoftControl) and select PLC setting
KI_eng.dot, 070221
Note!
the remote I/O (NA-9173 / NA-9473).
www.beijer.se
7 (31)
6.2
KI00327 2013-05
Modbus Master
KI_eng.dot, 070221
The iX TxA SoftControl uses the driver Modbus Master to communicate with the slave
units. We have to config a Modbus device and connect Modbus Master and the Modbus
Slave node.
x
Highlight Device (TxA SoftControl) and right click
Click Add Device and mark Modbus COM (use versionlink)
www.beijer.se
8 (31)
KI_eng.dot, 070221
KI00327 2013-05
Highlight Modbus COM and right click
Click Add Device and mark Modbus Master, COM Port (use versionlink)
www.beijer.se
9 (31)
KI00327 2013-05
6.2.1 Modbus Slave

x
Highlight Modbus_Master_COM and right click
Click Add Device and mark Modbus Slave, COM Port (use versionlink)
KI_eng.dot, 070221
Results
www.beijer.se
10 (31)
KI00327 2013-05
6.2.2 Setup the COM port

x Double click on Modbus_COM
x
COM 2 (support for COM 1, 2 and 3)

Baud Rate 115200, 8 Data Bit, None Parity, 1 Stop Bit
Note!
Setup the hardware NA-9173 / NA-9473 (link to hardware setting)
x Double click on Modbus_Master_COM_Port
x
Set Frame to 1 ms

x Double click on Modbus_Slave_COM_Port
KI_eng.dot, 070221
Set Slave Adress to 1
www.beijer.se
11 (31)
KI00327 2013-05
KI_eng.dot, 070221

Select functioncode and data for read and write area to node.
x

Results
www.beijer.se
12 (31)
KI00327 2013-05
KI_eng.dot, 070221

www.beijer.se
13 (31)
6.3
KI00327 2013-05

x

x

Addr.
0x0000
0x0001
0x0002
0x0003
0x0004
#15 #14 #13 #12 #11 #10 #9 #8

Discrete In 4pts
Empty
Always 0
(Slot#4)
Diagnostic In 4pts
0x0005
Empty
Always 0
(Slot#7)
#7 #6 #5 #4 #3 #2 #1 #0
Empty
Always 0
Discrete In 4pts
(Slot#5)
Addr.
0x0800
0x0801
0x0802
#15 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4 #3 #2 #1 #0

Discrete Out 4pts
Empty
(Slot#7)
0x = hex => 0x0800 = 800 hex
KI_eng.dot, 070221
www.beijer.se
14 (31)
6.4
KI00327 2013-05

KI_eng.dot, 070221

www.beijer.se
15 (31)
KI_eng.dot, 070221
KI00327 2013-05
www.beijer.se
16 (31)
6.5
KI00327 2013-05
KI_eng.dot, 070221
per application.
x
x
x
x

www.beijer.se
17 (31)
KI00327 2013-05

KI_eng.dot, 070221
www.beijer.se
18 (31)
KI_eng.dot, 070221
6.6
KI00327 2013-05
www.beijer.se
19 (31)
Rebuild the program

KI00327 2013-05
KI_eng.dot, 070221
NOTE!
x
This warning are OK


www.beijer.se
20 (31)
6.7
KI00327 2013-05

KI_eng.dot, 070221
The XML file for iX Developer is created when you transfer the project to the iX TxA
CoDesys project.
x
www.beijer.se
21 (31)
KI00327 2013-05
6.8 Transfer CoDeSys project to iX TxA SoftControl

x
Double click the TxA SoftControl option under Devices
The last two number (07) in the id [004F.C007] are the last group in ip-adress.
KI_eng.dot, 070221
NOTE!
If you dont find your CoDeSys devices, try to Add Device (example with
192.168.98.17)
www.beijer.se
22 (31)
KI_eng.dot, 070221
KI00327 2013-05
Download the project to the device (TxA SoftControl) which was selected above
Start the SoftControl with F5 or the symbol
www.beijer.se
23 (31)
KI00327 2013-05
Getting started, iX Developer (iX TxA SoftControl)

KI_eng.dot, 070221
7.1
Choose the iX TxA SoftControl panel size on which the application will run (iX T7A
Click Next
Access
Click Next
Click Finish
Rename the driver

x
www.beijer.se
24 (31)
7.2
KI00327 2013-05
Import of variables
KI_eng.dot, 070221
x
Select Import
www.beijer.se
25 (31)
KI00327 2013-05

x
KI_eng.dot, 070221

x
www.beijer.se
26 (31)
KI00327 2013-05

x
Check the settings.

KI_eng.dot, 070221
www.beijer.se
27 (31)
7.3
KI00327 2013-05
x
7.4
Download iX project to T7A SoftControl
KI_eng.dot, 070221

x
Menu Project
Select Download
After download, the HMI application starts up and communicates with the iX TxA
SoftControl.
www.beijer.se
28 (31)
KI00327 2013-05
Hardware iX TxA SoftControl, NA-9173 and NA-9473
8.1 Installation
Connect iX TxA SoftControl to NA-9173 / NA-9473 like the picture.
iX TxA-SC
NA-9173
120 :
120 :
iX TxA-SC
NA-9473
120 :
KI_eng.dot, 070221
120 :
Use CAB112 to connect iX TxA SoftControl with NA-9173 / NA-9473
www.beijer.se
29 (31)
KI00327 2013-05

Set the slave address to 1:
- MSD (X10) set to 0
- LSD (X1) set to 1
KI_eng.dot, 070221
Communication (SW1-4:ON, SW5-8:OFF)

COM 2, Baud Rate 115200, Enable Watchdog, 8 Bit, None Parity,
1 Stop Bit, RTU mode
www.beijer.se
30 (31)
KI00327 2013-05
KI_eng.dot, 070221
The dip switches are placed at left side of NA-9473
Set Node adress to 1 (SW1, 1:ON, 2-4:OFF)
Set Baudrate to 115200, RTU mode (SW2, 1-3:ON, 4:OFF)
NOTE!
Byte Format are fixed to: 8 Bit, No Parity, 1 Stop Bit
www.beijer.se
31 (31)
iX TxA SoftControl, Basic setting
KI00326 2013-05

With the HMI soft controllers in the iX TxA SoftControl series, any HMI application can
The SoftController communicate with an external device, for example Remote I/O.

Programming software
x iX Developer 2.0 SP1 (b 2.0.463.0) or later, programming the HMI in iX TxA
SoftControl
x TxA SoftControl setup(.msi), enable iX TxA SoftControl in iX Developer
x CoDeSys v3.5 SP1 Patch 4 or later, programming the SoftControl (Compiler 3.5.1.40)
Image, iX TxA SoftControl
x IML_TxA_b0420(.exe)
Driver, iX TxA SoftControl
x CoDeSys_SoftControl_Direct_Access ver 4.00.17, driver iX HMI with SoftController
Device description, iX TxA SoftControl
x TxA-SoftControl_V3_5_1_40.devdesc(.xml), variabel list from CoDeSys to iX
x Standard 3.5.1.0
Driver version for communication to Remote I/O
x See StartUp document KI00327 (Modbus RTU)
x iX T7A SoftControl
1 (13)
KI_eng.dot, 130103

Head Office
Subsidiaries

Telephone +46 40 35 86 00
Fax +46 40 93 23 01

KI00326 2013-05
Table of Contents

4 Configuration of CoDeSys and iX Developer .................................................................................................................3
4.1 Add iX TxA SoftControl to CoDeSys ..........................................................................................................................3
4.2 Add iX TxA SoftControl to iX Developer....................................................................................................................4
4.3 Install the driver for iX HMI to the SoftControl .........................................................................................................4
5 iX TxA SoftControl connections......................................................................................................................................5
6 Communication between iX HMI, iX TxA SoftControl and Remote I/O...................................................................5
7 Programming tools............................................................................................................................................................6
8 Persistent variables (16 kbyte) .........................................................................................................................................7
9 Important settings.............................................................................................................................................................8
9.1 Boot after Online Change and Restart of iX TxA SoftControl....................................................................................8
10 Project backup ..................................................................................................................................................................9
10.1 CoDeSys, Create backup files ....................................................................................................................................9
10.2 CoDeSys, Project Archive ..........................................................................................................................................9
10.3 CoDeSys, Sourse Download to iX TxA SoftControl ...................................................................................................9
10.4 CoDeSys project to iX TxA Softcontrol using USB memory.....................................................................................10
11 Diagnostic, SoftController..............................................................................................................................................11
KI_eng.dot, 070221
12 Files in Start-kit...........................................................................................................................................................13
12.1 Device Description iX TxA .......................................................................................................................................13
12.2 CoDeSys SoftControl Direct Access.........................................................................................................................13
12.3 iX TxA SoftControl Image ........................................................................................................................................13
12.4 iX TxA SoftControl to iX...........................................................................................................................................13
12.5 Diagnostic Tag .........................................................................................................................................................13
www.beijer.se
2 (13)
KI00326 2013-05
4 Configuration of CoDeSys and iX Developer

This installation has to be done once for every computer.
KI_eng.dot, 070221
4.1
Add iX TxA SoftControl to CoDeSys

x
Change Standard to Professional
Install iX TxA SoftControl (Device description file) to CoDeSys

(iX TxA-SoftControl_Vxxx.devdesc.xml) (use versionlink)
www.beijer.se
3 (13)
4.2
KI00326 2013-05
Add iX TxA SoftControl to iX Developer

To get the iX TxA SoftControl terminals in iX Developer.
Run the file: TxA SoftControl Setup.msi.
x
4.3
Double click on the TxA SoftControl Setup.msi file to install

The driver (CoDeSys_SoftControl_Direct_Access) is installed when installing
iX Developer.
Update the driver
x
To update the driver, you should be logged in as administrator.

Right-click the icon for iX and select "run as administrator".
Start iX developer and make a iX T7A SoftControl project (dont select any driver)
Click on the symbol under iX in the upper left corner of the program
Select Update Drivers, then Update Drivers From File or Internet
Update from file:

x
Browse to the location where the driver is found
Highlight the CoDeSys_SoftControl_Direct_Access_Pre2.mpd file and press Open
Highlight the driver in the new window and press Install
KI_eng.dot, 070221
Once installed, re-start iX Developer

Note!
The installation of the driver needs only to be done once for every computer running iX.
www.beijer.se
4 (13)
KI00326 2013-05
5 iX TxA SoftControl connections

24 VDC
COM 1/2
LAN
COM 3/4
Ethernet
Modbus
6 Communication between iX HMI, iX TxA SoftControl and

Remote I/O
The terminal uses two drivers for communication between iX HMI, iX TxA SoftControl and
remote I/O.
Driver 1: iX HMI application with iX TxA SoftControl (CoDeSys SoftControl Direct
Access)
Driver 2: iX TxA SoftControl with Remote I/O (Serial Modbus RTU*) *Support for COM 1, 2, 3.
iX TxA SoftControl
Example:
Crevis FnIO-S Series
Driver 1
iX-driver
iX HMI
application
Direct
access
Driver 2
SoftControl
KI_eng.dot, 070221
COM 1, 2, 3
(RS-232/485)
www.beijer.se
5 (13)
KI00326 2013-05
7 Programming tools
x
iX Developer for iX HMI application
CoDeSys for the SoftControl

iX TxA SoftControl
iX HMI
application
SoftControl
COM 1, 2, 3
KI_eng.dot, 070221
Ethernet
www.beijer.se
6 (13)
KI00326 2013-05
8 Persistent variables (16 kbyte)
KI_eng.dot, 070221
per application.
x
x
x
x

Persistent variables, function.

iX TxA SoftControl supports Persistent variables.
www.beijer.se
7 (13)
KI00326 2013-05
Important settings
9.1
Boot after Online Change and Restart of iX TxA SoftControl
KI_eng.dot, 070221
This must be done to make a safe restart after power off.

In other case the CoDeSys project have to be downloaded again.
x
Highlight the Application option in the Device window and right click
Select Properties and Boot application
www.beijer.se
8 (13)
KI00326 2013-05
10 Project backup
10.1 CoDeSys, Create backup files
If this option is activated, at each saving the project will not only be saved in
<projectname>.project but also copied to a file <projectname>.backup.
If needed you can rename this backup-file and re-open in CoDeSys.
Menu Tools\Options
10.2 CoDeSys, Project Archive

The best way to get all components from a CoDeSys project is to make a Save/Send
Archive. That will save and pack all files referenced by and used within the currently
opened project in to one archive file. The archive file can either be stored or sent as
attachment of an email. The archive file can easily be unpacked by use of Extract Archive
Note! The archive function is not intended for restoring a project environment.
It is designed for an easy packing of all files belonging to a project!
10.3 CoDeSys, Sourse Download to iX TxA SoftControl

The CoDeSys project can be saved in the terminal and upload to CoDeSys.
Upload / Download
KI_eng.dot, 070221
Project setting
Alternative to upload the archive.prj file

www.beijer.se
9 (13)
KI00326 2013-05
10.4 CoDeSys project to iX TxA Softcontrol using USB memory

It is possible to export a CoDeSys project and then save it in the root on a USB memory
stick. If booting the iX TxA SoftControl panel with the USB memory plugged in it should
be possible to upload the CoDeSys project from the memory to the iX TxA SoftController.
Export project from CoDeSys programming tool
x
In menu Online select Create boot application and save the project files (.app/.crc)
in the root of the USB memory
Upload CoDeSys project from USB to iX TxA SoftControl

x
Restart the iX TxA SoftControl panel with USB memory
You will be asked if you wish to load the CoDeSys project

Copy PLC project from USB memory?
Important note!
x
When upload of CoDeSys project the SoftController memory will be cleared!

Also the Persistent area (the battery powered memorycells and register)
Tip!
KI_eng.dot, 070221
Its possible to upload the iX developer project
www.beijer.se
10 (13)
KI00326 2013-05
11 Diagnostic, SoftController
The driver supports some diagnostics tags, for example the RUN-state of the controller
application. These tags are all addressed by the prefix "Diagnostics.", which is why tags
which start with "Diagnostics." can't be used in the controller application.
All diagnostics tags are listed below.
Up to 20 Tasks are supported and can be addressed by changing the task-number in the tagsyntax between 0-19. For example the name of task 6 (the seventh since the number begins
at 0) is addressed with Diagnostics.Task6.Name.
All diagnostics times and intervals are given in microseconds.
x
From example project
KI_eng.dot, 070221
Diagnostic and Star /Stop of the SoftController
www.beijer.se
11 (13)
KI00326 2013-05
KI_eng.dot, 070221
Tip!
Import of Diagnostic Tag to your project:
- Import the tags in tags in T7A_SC_NA9173_Ex1_Diagnostic_TagsImport_To_iX.txt.
You find the file in library StartKit.\DiagnosticTag
www.beijer.se
12 (13)
KI00326 2013-05
12 Files in Start-kit
The folder in StartKit_TxA_SoftControl contains the latest files latest files to prepare
iX TxA SoftControl.
(download from homepage)
12.1 Device Description iX TxA

Files:
- TxA-SoftControl_V3_5_1_x*.devdesc.xml
- T7A.bmp
Enable iX TxA SoftControl in CoDeSys.
12.2 CoDeSys SoftControl Direct Access

Files:
- CoDeSys_SoftControl_Direct_Access_Pre2.mpd
- CoDeSys_SoftControl_Direct_Access_Pre2.cab
HMI Driver, iX application with iX TxA SoftControl. Use update driver in iX developer.
12.3 iX TxA SoftControl Image

File:
- IML_TxA_bxxx*.exe
Latest image for iX TxA SoftControl.
12.4 iX TxA SoftControl to iX

File:
- TxA SoftControl Setup.msi
Enable iX TxA SoftControl in iX Developer 2.0 SP1.
12.5 Diagnostic Tag

File:
- T7A_SC_NA9173_Ex1_Diagnostic_TagsImport_To_iX.txt
Import of Diagnostic Tag to your project
KI_eng.dot, 070221
*, use versionlink
www.beijer.se
13 (13)
TxC factory reset procedure

KI00325 2013-04

This document can be seen as a compliment to iX Help documentation.
The recovery allows the end-user to restore his TxC back to factory defaults without
needing any image loading software licenses or an additional PC.
The recovery procedure requires additional hardware (not provided with the unit):
A USB keyboard
A USB DVD drive
2 About this Start-Up document

to the installation manual for iX TxC panels. This document and other Start-Up
documents can be downloaded from www.beijerelectronics.com.
documents.
Page 1 (3)
KI_sv.dot, 021106

10

Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599
KI00325 2013-04
3 Required Software
With the delivery of a TxC you will get 2 DVDs:
KI_sv.dot, 021106
With the bootable Recovery DVD , the system can be brought back to the factory settings.
2 (3)
KI00325 2013-04
4 The Procedure
- Connect DVD drive with Recovery DVD inserted, keyboard and power-supply
- Switch on Power-supply
- During booting press F7 to open boot Menu
- Select DVD as boot media
- Press any key to boot from the Recovery DVD
- Accept the EULA text by selecting the checkbox
KI_sv.dot, 021106
Press Start Recovery to start

Additional window will appears, warning user that all data will be lost!
Press OK
Recovery takes approximately 10 minutes.
After recovery is done, switch off and disconnect the USB DVD drive.
Power on, WINDOWS 7 will start from the internal SSD/HDD.
3 (3)
Optimizing your iX application

KI00324 2013-04

This document discusses several different aspects of how an iX application can be
improved to run smoother and different pit falls that a designer should be aware of when
working with iX Developer.

to the manual for iX Developer 2.0. This document and other Start-Up documents can be
downloaded from www.beijerelectronics.com.
documents.
Page 1 (7)
KI_sv.dot, 021106

10

Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599
KI00324 2013-04
3 Driver performance
Different signal types
Driver communication can be divided in two types of devices, Static and Dynamic and
these are updated in different ways.
Static tags
Static tags are always updated even if the are not shown on the HMI screen.
This type of devices is connected to Trends, Data loggers, Alarms, Data Exchange and
system devices.
Any external tag which has been configured as Always Active will also be considered a
Static Device.
The Always Active setting is found under the Others Columns in the tags editor:
Tags which have actions configured on them are also treated as Always Active.
Tags used in scripts are also handled as Always Active.
Minimizing the amount of static devices is one way of improving the performance of your
HMI application. Another way to improve the application is to keep your static devices in
consecutive order.
Dynamic tags
KI_sv.dot, 021106
Dynamic tags are only updated when they are shown on the screen and the most common
example of this type of signal is a tag which is connected to an Analog numeric object; it
is only updated when it is shown on the screen.
2 (7)
KI00324 2013-04
4 Keep signals in consecutive order

When the signals are transferred to the controller, all signals are not transferred
simultaneously. Instead they are divided into packages with a number of signals in each
package. To decrease the number of packages that have to be transferred and make the
communication efficient this number has to be considered.
The number of signals in each package depends on the used driver and information about
this can be found in the driver help for the used driver:
To make the communication as fast as possible the number of packages has to be

minimized.
Consecutive signals require a minimum of used packages but it is not always possible to
have consecutive devices.
In such cases the so-called waste between two signals has to be considered.
5 Waste
KI_sv.dot, 021106
Waste is the maximum gap between two signals that still keeps them in the same
package/telegram. The waste depends on the used driver and information about this can
be found in the driver help for the used driver.
3 (7)
KI00324 2013-04
To make communication times shorter, you also need to consider station handling
compared to adding a separate controller for each station you wish to poll.
Since all our communication drivers are sequential, they will poll all devices from one
station, followed by the next station in the list and so on.
If a lot of stations are configured and you use a variety of signals in each, this will lead to
a long poll cycle for the configured controller. In this case, its a good idea to split the
stations into 2 or more separate controllers (not possible for serial interface drivers).
Note:
Each controller will take up a certain amount of resources (memory and CPU load).
This may require that you use more powerful hardware, for example upgrading from a
T7A to a T7B.
6 Bit-addressed words compared to normal bit-devices

In most drivers it is better to use bit addressed words instead of normal bit devices. The
reason for this is that when using bit address words you can fit more digital devices in one
telegram compared to using bit devices.
Example:
This specific driver can have 29 Analog devices in one telegram or 124 Digital
devices(bits).
If you where to use bit addressed word devices in the selected driver you could fit 464
(29*16) digital devices in one package. This is almost four times as many devices.
7 ASCII Strings
ASCII strings are transmitted in separate telegrams and having a large number of strings
will affect the communication performance negatively.
KI_sv.dot, 021106
If an ASCII string only has a small number of different string values then it may be a
good idea to use the Text Library functionality in iX with predetermined content to
maximize the projects performance.
4 (7)
KI00324 2013-04
8 Poll groups
The default setting in iX Developer is that all signals update every 500ms.
If there are certain signals that dont need to be updated this fast it is possible to assign
them to another poll group and slow down the update time.
If some need to be update more often, they can be configured in a faster poll group.
Poll groups are configured in the Tags editor, you can configure up to 5 different poll
groups.
It is generally a good decision to let alarm tags be updated less regularly to optimize
performance.
This is especially true if you have an application with a large amount of alarms.
9 Screen update time

Optimizing screen update time has to do with minimizing CPU load and Flash operations.
This can make a big difference in a graphics intense project that approaches the limits of
the panels capabilities.
If you want faster screen jumps in the application, make sure that the tags used in the
relevant screens are connected to a poll group with a low poll time. The lowest possible
poll time supported in iX Developer is 100ms.
An alarm viewer screen with a long list (default: 1000) will have a longer loading time
compared to if it was configured to only show the last 100 alarms.
10 Resize symbols
The resize function in iX Developer is a good function to use if a small number of
symbols are used.
If you are planning on incorporation a large number a symbols it is recommended to
change the size before using the symbol in the application.
KI_sv.dot, 021106
This can have a big impact on the performance of the panel.
5 (7)
KI00324 2013-04
Example:
If you are designing an application for an iX T7A, which has a resolution of 800*480
pixels, there is little point in using pictures with full HD resolution (1920*1080 pixels).
11 Gradients
Using objects with gradients creates a slightly higher load on the CPU and if a large
number of them are used it will make the screen update/load time slower.
12 Consider how your Objects/Controls are used

Avoid object stacking. Placing several buttons on top of eachother and controlling
which is shown via dynamics is a bad way of solving a design problem.
A better solution (performance wise) would be to only have one button and write a script
to handle the different actions needed.
The same is true for stacking symbols/multisymbols on top of buttons.
A better solution is to use the embedded symbols in the buttons, which can be configured
under the General ribbon settings for the button:
Some objects are more CPU intense than others.

For example, the AnimatedLabel, RollerPanel, TouchComboBox and TouchListBox are
more CPU intense than your average basic control, like the AnalogNumeric object.
KI_sv.dot, 021106
As a general rule, try to limit the use of CPU intense objects on each screen, especially if
you are using entry level hardware like the TxA series.
6 (7)
KI00324 2013-04
13 Trends and Data logger

Using a lot of trends and data loggers will cause the panel to do a lot of flash operations
and thereby slow down the screen update time.
One way to remedy this is the Log changes only option.
This can potentially reduce the number of write operations to the flash, if the tags
configured in the datalogger does not change very often.
It is more efficient to have one large Datalogger containing many log values (tags),
compared to having several Data loggers with a few log values in each.
14 Data Exchange
To maximize the performance of your data exchange, you should try to only use
consecutive signals and you should use a data trigger to control the data exchange.
KI_sv.dot, 021106
Value change triggered data exchange will greatly impact the performance of the HMI if
the tags configured for data exchange change values frequently in the PLC.
7 (7)
Configuring Data Exchange in iX Developer

KI00323 2013-04

This document explains how an iX Developer application can be configured to facilitate data
exchange between different controllers (PLCs).

to the manual for iX Developer 2.0. This document and other Start-Up documents can be
downloaded from www.beijerelectronics.com.
documents.
3 Configuration
To be able to configure data exchange, at least two controllers must be configured in the
project. It is currently not possible to configure data exchange between stations in a single
controller.
Data exchange is configured in the Tags editor:
The Data Exchange checkbox under Columns Visible must be ticked to be able to see
the configuration. (it is filtered by default).
Unchecking the checkbox will not remove your settings, it is just a visibility filter.
Page 1 (4)
KI_sv.dot, 021106

10

Box 426
SE-201 24 MALMOE
SWEDEN
Telephone +46 40 35 86 00
Telefax +46 40 93 23 01

USA
Telephone +1 847 619 6068
Telefax +1 847 619 6674

Zettachring 2A
DE-705 67 Stuttgart
GERMANY
Telephone +49 711 327 599-0
Telefax +49 711 327 599
KI00323 2013-04
The three dotted button to the right in each field in the Direction column is where you
configure in which direction you wish the data exchange to occur:
In the following screenshot, data exchange is configured to move the data for the selected
tag from the device configured under the Demo_Controller_2 to the device configured
under Demo_Controller_1.
In this case, it would mean that the value from C1 in Demo_Controller_2 would be
copied to D1 in Demo_Controller_1:
Note:
The direction setting must be configured separately for each tag.
This configuration is included when you perform a Tags list export, so the best way to do
this configuration for a large amount of tags is to export the tags list to an excel sheet,
make the changes in Excel and save, then import the modified excel file using the Merge
option.
The fields you will need to change are the AccessRight_x and AccessRight_y
KI_sv.dot, 021106
The number corresponds to the different controllers. Read corresponds to From and
Write corresponds to To in the direction configuration popup.
2 (4)
KI00323 2013-04
4 Triggers
Due to the implementation of Data Exchange, the default setting in the When column is
Value Change. This means that every time the tag value changes, it will trigger a data
exchange which in turn will trigger a write to the controller(s).
If a lot of tags have this configuration, it can potentially generate a large amounts of
telegrams and will impact the performance of the project in a bad way.
A better configuration is to change the When column setting to Trigger instead.
Triggers are configured in the Tags section as well:
A trigger can be either cyclic (time) or activated on a tags value change event.
If a cyclic trigger is chosen, the fastest (and most intense) data exchange allowed is 1
second.
If a tag is connected to the trigger, the trigger will activate on the tags value change event.
If this is used, it is possible to achieve data exchange faster than 1 second, but it will
greatly reduce the performance of the project depending on which hardware platform is
used.
The benefit of using triggers, is that the driver will generate more efficient telegrams and
not affect the performance as much as the Value Change alternative does.
5 Group controller devices consecutively

The devices from the controller are read most rapidly if all devices are consecutive. If the
devices are spread out (e.g. 4, 17, 45, etc.) the updating is slower.
Packaging of signals
KI_sv.dot, 021106
When the devices are transferred to the controller, all devices are not transferred
simultaneously. Instead they are divided into packages with a number of devices in each
package. To decrease the number of packages that have to be transferred and make the
communication faster this number has to be considered. The number of devices in each
package depends on the used driver.
3 (4)
KI00323 2013-04
To make the communication as fast as possible the number of packages has to be

minimized. Consecutive devices require a minimum of used packages but it is not always
possible to have consecutive signals. In such cases the so-called waste between two
signals has to be considered. The waste is the maximum distance between two signals you
can have and still keep them in the same package. The waste depends on the used driver.
Note: ASCII Strings and arrays are packed into one package for each object.
The number of devices that fit into a communication telegram is dependent on which
communication driver is used.
The maximum number of devices and the largest allowed waste for each driver can be
found in respective drivers help file.
Example with FX Series Serial driver:
This driver allows a maximum of 32 analog devices or 248 digital devices in each
telegram.
The maximum allowed waste (space between 2 signals before they are separated into
different telegrams) is 20.
KI_sv.dot, 021106
To maximize the performance of your data exchange, you should try to only use
consecutive devices and you should use a data trigger.
4 (4)
:HE6HUYHULQL;'HYHORSHU
.,
The Web Server adds the possibility to use a server-side Application Programming Interface
(API) to interact with a running project. The API operates over the HyperText Transfer
Protocol (HTTP) and can be access from any compatible device. In addition, the web server
can host web pages and related media to be consumed by web browsers.
The bundled Javascript Software Development Kit (SDK) makes it easy to build interactive
web pages that utilize the API.
Login settings for the web server are available from Server group on the System ribbon tab.
This document can be seen as a complement to iX Help documentation.
- iX Developer 2.0
- Text editor for editing HTML files.
Example:
Notepad Build in text editor in Windows.
Notepad++ - Free source code editor with syntax highlighting and more.
http://notepad-plus-plus.org/
Visual Studio Express 2012 for Web May require payment depending on circumstances.
http://www.microsoft.com/visualstudio/eng/downloads#d-express-web
Page 1 (15)
P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
.,
the manual for iX Developer 2.0. This document and other Start Up documents can be
obtained from your closest distributor of operator terminals.
6HWWLQJXSL;
KI_eng.dot, 070221
Create a Panel-project or a PC-project.

This document is based on a Panel-project but the same approach is applied to PC-project.
Lets first configure iX Developer and create a layout. In this example Demo-controller is
used.
Under the System ribbon click on Web Server.
Check Enable Web Server and enter a port number, default: 80.
KI_eng.dot, 070221
When Enable forms authentication is checked; Free definable username and password can
be set. When unchecked; Anonymous authentication is set.
www.beijer.se
2 (15)
KI_eng.dot, 070221
.,
Go to Tags. Add 4 tags, one of which is a System Tag. These tags will be shown when
the web server is accessed. The different formatting will be handled differently in the
HTML-file.
Tag Name
Data Type
Value1
Int32
Value2
Float
Value3
String
SystemTagDateTime
DateTime
www.beijer.se
3 (15)
.,
Add 3 analogue numerics to your screen. Connect the tags accordingly.
KI_eng.dot, 070221
Note that you have to change the display format for Value2 and Value3, changed under
General of the object. Value2 is displayed with 3 decimals and Value3 is displayed as string.
www.beijer.se
4 (15)
.,
6HWXSZHEVHUYHULQWHUIDFH
The web server files must be stored in the root folder: ProjectName\Project Files\WebSite.
If WebSite does not exist, create it. The startpage must be called index.html.
Create index.html in the folder WebSite as mentioned.
Open the html file with your html-editor. In this document Visual Studio Express for
Web is used.
There are two ways of working with the source files with iX panel.
One way is to work online and replace/modify the files in the root folder of the panel. This is
done by enabling FTP server on the panel and using an FTP client to access the files/folders.
The changes take effect immediately and you dont need to restart the application.
Please see startup document article ID: DSSE-8ZBGH6 on how to set up FTP server.
Open up index.html with your HTML-editor.
Create a simple code which will display Hello World to check that the setup is correct.
Example, index.html located in WebSite:

<!DOCTYPE html>
<html>
<head>
<title>Webserver demonstration</title>
</head>
KI_eng.dot, 070221
<body>
<p>Hello World</p>
</body>
</html>
Save the file and open up, or rebuild, your project.
Download.
www.beijer.se
5 (15)
.,
To access the web server you simply type in the IP address into your web browser.
If authentication is enabled, a login screen will first appear.
If you are not running on the default port 80 you have to enter this manually.
The port no. is separated with colon E.g. 192.168.1.10:800.
KI_eng.dot, 070221
Now we know that the web server is correctly set. Further, we will connect iX-tags to the
web server.
www.beijer.se
6 (15)
.,
-DYDVFULSW6'.2YHUYLHZ
The JavaScript SDK provides a rich set of client-side functionality for accessing the server-side
API calls. This enables the possibility to build highly interactive web pages that uses tags defined
in the project.

&RQQHFWL;6'.WR+70/GRFXPHQW
1. The first step to build an interactive web page is to reference the SDK by inserting the
following script into to the header of the html.

2. Next, the SDK needs to be initialized. In its simplest form the following lines need to be added
in the header after the reference to the SDK:

This will make it possible to use the defined tag metadata attributes to incorporate the project tags
into the web page.
The
following line will, for example, insert the value of Tag1 into the html document:

Example of neccecary header tags:

The header lines in the example above needs to be included in each HTML document that requires
iX SDK functionality.

7DJ9DOXHRU3URSHUWLHV
To insert the current value of a tag or tag property into an html element, the data-ix-tag attribute
can be used. The value of the attribute should be the name of the tag as defined in the project and
the property of a tag. Separate the names with a dot ..
If no property is provided, the value of the tag is used.
KI_eng.dot, 070221

<span data-ix-tag="Tag1.DataType">Replaced with the datatype of Tag1</span>
www.beijer.se
7 (15)

.,
)RUPDWWLQJ
Formatting of a tag value can be applied to a tag of numeric type or a datetime. The format is
defined using the data-ix-format attribute.

In the first example the Date will be shown as Year-Month-Day, where Year is a four digit
number, month as the abbreviated name of the month and the day of the month as 2 digit
number from 01 to 31. eg. 2012-Jan-01.
In the latter example the NumericTag will be shown with 3 decimals.
In iX Developer 2.0 help documentation (F1) you can find complete table of custom date and
time format as well as custom numeric formats.

5HIUHVK0RGHV
To control how tag values are refreshed, the data-ix-refresh attribute can be used with
elements defined with data-ix-tag .
It is recommended to use a interval of 5 seconds.

onetime
= Refreshes only once. E.g. screen opened or refreshed.
none
= Only refreshes when tag is invoked by refresh action.
interval
= Refreshes at the interval set in iX.setup (default interval of 5s. This can be
changed, see further down in this document)
Optional to refreshing the tags individually, global settings can be made when referencing iX
SDK in the header of the HTML document.
Read more about refreshing tags in chapter 8.

6HWWLQJWDJYDOXH
To set the value of tag, two elements must be defined.
The first element has the data-ix-setter attribute on the position where the tag value can be
entered. The second element has the data-ix-submitbutton attribute used to submit the new
tag value.
The data-ix-submitbutton attribute takes the tag names, separated by comma ,, to be
submitted when the button is clicked. To submit all tags an asterisk * can be used.
KI_eng.dot, 070221

www.beijer.se
8 (15)
.,
&RPSOHWHH[DPSOHSURMHFW
In this document we will first create a simple layout which will display the four tag values
we created earlier.
This is the code which is used for connecting the tags and to refresh the tags at an interval of
5 seconds (default). Value 2 and Date also has to be formatted.

<span style="text-align:center";><h1>Web Server</h1></span>

KI_eng.dot, 070221
You will now be able to read the tag value from the application.
Save the html file/s.
Download and test.
www.beijer.se
9 (15)
.,
Lets add input and set-button to Value1-2-3. Something like this:
Add the following in the body under date:


KI_eng.dot, 070221
You should now be able to set values 1-3.
www.beijer.se
10 (15)
.,
&KDQJHORJLQ
If forms authentication is enabled the default login screen will first appear and provide a
login authentication using any code.
Security notice! Username and Password are sent in plain text. Its recommended to use
encrypted tunnelling (VPN) if considering to use web browser connecting over unsafe
networks.
Its possible to override the default login page by creating your own login.html and place
it in the Website folder. Authentication must be enabled.
The Javascript SDKprovides tools for creating the form using a few conventions. Note that
this only applies if you have authentication enabled in the web server settings.
Reference to the authentication script must be made in head:

Assign id:s to Username and Password field with the predefined ids ix-username and
ix-password. In body:

KI_eng.dot, 070221

www.beijer.se
11 (15)
.,
Assign id to login button with the predefined id ix-login. Any element can be used. In body:

Optionally add an element with the predefined id ix-invalid-credentials that will be shown if
the login fails. Style is located in the header.
In html head:

In html body:

Simple login example:

KI_eng.dot, 070221

www.beijer.se
12 (15)
.,
$SSHQGL[L;2EMHFWFRQILJXUDWLRQ
After loading the JavaScript SDK, call iX.setup to initialize the framework. This will wire
the tag metadata attributes that you have defined in html and will start periodical polling.
iX.setup has a set of parameters that can be modified.
Options:
Property
Type
Description
Argument Default
refreshInterval
Int
The refresh interval of tag values in ms. For performance

reasons it is recommended not to use low values for this Optional
setting.
5000
refreshMode
String
Overrides the default refresh mode of tag values.

Accepted modes are: none, onetime, interval.
Optional
onetime
refreshModeSetter
String
Overrides the default refresh mode of tag setters.

Accepted modes are: none, onetime, interval.
Optional
onetime
This example below will set periodical refresh interval to 10 seconds, set the refresh mode of html
elements marked with the data-ix-tag attribute to interval and set the refresh mode of html
elements marked with the data-ix-setter attribute to refresh only once. Note upper and lower case!

KI_eng.dot, 070221
www.beijer.se
13 (15)

.,
L;LQYDOLGVW\OH
Basic validation is done on input values. If the value cannot be assigned to the Tag then the
value will not be set. To indicate an invalid value the framework will set the CSS class ixinvalid on the element. This can then be used to provide the user with visual cues of the
invalid state. For example, the following CSS snippet adds a red border around the input
when the input is incorrect:
Located in head:

</head>
Locaded in body:
<body>
<input type="number" data-ix-tag="Tag1" class="ix-invalid" />
</body>

L;UHIUHVK(OHPHQWV
Refresh tag values manually. Values can be manually updated on event E.g. button.
In the example below, the html elements with id "Value1Id" to Value3Id will be updated
when the element with id "refreshButton" is clicked. This example uses jQuery (bundled
with iX.js) to bind to the click event of the "refreshButton".
In html head:

In html body:

KI_eng.dot, 070221

www.beijer.se
14 (15)
.,
&RPSOHWHH[DPSOHKWPOFRGH


KI_eng.dot, 070221
www.beijer.se
15 (15)
5HSRUW*HQHUDWRULQL;'HYHORSHU
.,
The report generator allows generating Excel reports based on an Microsoft Excel made
report template.
The generated report can be output to a printer or saved as an Excel file.
- iX Developer 2.0
- Microsoft Excel or substitute
Page 1 (14)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
.,
6HWWLQJXSUHSRUWJHQHUDWRULQL;
This Start-Up is based on a PC-project. While Panel-projects differs from PC-projects, the
same method is used.
KI_eng.dot, 070221
We will create a report that will include 3 values.
Start iX Developer and open Tags.
Create 3 tags that we will have in the report.
www.beijer.se
2 (14)

.,
([FHOWHPSODWH
Create a new Excel xls-file which will be the template for iX.
The tag data to be displayed in the report file are set up in the template file using
placeholders. The placeholders acts as substitute for the actual tag data that is to be
inserted when the report is generated in iX Runtime.
To add a placeholder, enter the following text inside a cell in the Excel report template:
<#Tag(TagName)>
Replace TagName with the actual name of the tag to be displayed. When the template file
is complete it needs to be added to the iX Developer project.
Note! The tag placeholders can only be used in the cells of the Excel template file, they can
not be used in, for example, Microsoft Excel WordArt texts.
KI_eng.dot, 070221
Insert the tags (Value1,2,3) into the xml-file using the text above. Save and close.
www.beijer.se
3 (14)
KI_eng.dot, 070221

.,
,PSRUWWHPSODWHLQL;
Go back to iX Developer.
Insert Reports found in the Insert ribbon.
Open Reports.
Add report by clicking on Add and browse for the template xml-file we created.
www.beijer.se
4 (14)
Enter a name for the report.
Save your project.
.,
KI_eng.dot, 070221
Saving the project will create a new folder structure in the project files and a copy of the
template we imported.
www.beijer.se
5 (14)
KI_eng.dot, 070221

.,
6FUHHQOD\RXWDQGFRQQHFWLRQV
Create a screen layout containing of 3 analogue numerics and 1 button.
Connect the 3 tags to the analogue numerics.
Select the button and set action for Click to Generate report found under Reporting.
www.beijer.se
6 (14)
.,
We can choose between sending the report to a printer or saving it to disk. Note: Printer
setup is found under System Settings in the ribbon menu.
In this case select File.
Having File selected, click on to set the destination of the file.
PC-project:
Name
Function
KI_eng.dot, 070221
The file will be saved in a folder named Project Files in the projects execution
Project Files Folder
path.
Browse
A save dialog will be show in runtime. The user will be able to select path and
filename.
Path
The file will be save to a specific path.
www.beijer.se
7 (14)
.,
KI_eng.dot, 070221
Panel-project:
Name
Function
Project Files
Folder
The file will be saved in a folder named Project Files in the projects execution
path.
USB
The file will be saved to a connected USB memory.
Memory Card
The file will be save to a external memory card.
In this document the file is saved to My Documents, on the PC drive, by selecting Path.
Select the report you want to use. In this case only one is available.
www.beijer.se
8 (14)

.,
*HQHUDWHUHSRUW
Run the project and enter values.
Click on Generate Report.
The report file has now been created in the folder selected earlier. A new file will be created
every time the generate button is clicked. The filename includes date and time.
Open the file.
KI_eng.dot, 070221
The values entered earlier will now be shown in the file.
www.beijer.se
9 (14)
.,
KI_eng.dot, 070221
64/
Add Data Logger and open it.
Add 3 log items and connect them to the tags.
Open Settings and select Log with interval of and enter the log interval e.g. 5sec.
Click OK.
Open up the xml-template.
www.beijer.se
10 (14)

.,
&RQILJXUDWLRQ6KHHW
The configuration sheet is a repository where configurations on the Microsoft Excel report
template can be made. This sheet will not be visible in the generated report.
1. Create a new worksheet in the report template. Name the sheet <#Config>.
2. Row 10, and all rows below, in column A and B can be used to configure the SQL queries.
Enter the SQL query in column B. Use the corresponding cell in column A to enter a name
for the query. The name will be used to refer to the query in the report template.
Enter the SQL queries in the following format:
SQL(DatabaseName; SQL query)
In this case: SQL(General; SELECT * FROM DataLogger1)
KI_eng.dot, 070221
There are two available databases: General and AuditTrail.
www.beijer.se
11 (14)

.,
3UHVHQWWKH'DWDEDVH'DWDLQWKH5HSRUW
To present the data in the report, enter the following syntax into the cells included in the
named range:
<#QueryName.DatabaseColumnName>
Replace the DatabaseColumnName entry with the actual name of the table in the SQL
database that you wish to present in the report.
The data retrieved from the SQL database, using the queries in the configuration sheet, can
be presented in the report using named ranges in Microsoft Excel.
A named range is created in Microsoft Excel by following these steps:
1. Select the cells to be included in a named range.
2. Click the Define name command from the Insert menu. (In Excel 2007, go to the Formulas
tab and choose Name Manager).
3. Enter a name for the range. The name must be entered in the following format:
__QueryName__. Replace QueryName with the name that you have chosen for your
SQL query.
KI_eng.dot, 070221
Note! It is possible to use the named range cells in Microsoft Excel charts and functions. To
be able to use the named range in functions, an empty row must be inserted under the named
range cells. This empty row must also be included in the function.
www.beijer.se
12 (14)
Re-open the template to re-initialize the changes.
Run the project.
Enter random values to be logged by the Data Logger.
Generate a report and open the report file.
.,
KI_eng.dot, 070221
You should now see the values that have been logged.
www.beijer.se
13 (14)
.,
/LPLWDWLRQV
Microsoft Excel xlsx format is not supported by the Report Generator.

Reports containing charts and pictures can not be printed from a panel target.
Reports containing macros will not be run, before being printed.
The report generation is not an instant process. It may elapse a shorter period of time between
the first sampled tag and the last sampled tag, depending on the number of tags to process.
KI_eng.dot, 070221
www.beijer.se
14 (14)
Transparent mode with iX Developer 2.0
KI00318 2013-02

This document explains how too set up transparent and passthrough mode in
iX Developer 2.0.
This document will explain the two routing features, transparent and passthrough mode.
Focus will be on Mitsubishi driver (FX) with serial communication.
- iX Developer 2.0
- Serial/IP
Harware requirements:
- Mitsubishi FX

Page 1 (9)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Visitors address Stora Varvsgatan 13a, Malm
Subsidiaries
KI00318 2013-02
3 Set up routing in iX Developer 2.0

This chapter will explain how to set up transparent and passthrough- mode.
Transparent mode
The transparent mode function enables the HMI to continue to communicate with the
controller while the routing takes place. The communication will be split between the HMI
and the routing unit. Routing in this mode will affect the performance of the controller
communication since two units will share the same communication.
If routing over Ethernet, the routing unit have to support Ethernet communication.
Note: When using transparent mode it might be wise to set the baudrate as high as possible
because of the time delay.
Passthrough mode
KI_eng.dot, 070221
When Passthrough mode is activated and the routing unit communicates with the controller
through the HMI, communication between the HMI and connected controller will stop. A
HMI where communication in Passthrough mode is in progress becomes locked for the
operator, and the text Passthrough is shown in the display.
www.beijer.se
2 (9)
KI00318 2013-02
KI_eng.dot, 070221
3.1 Serial communication with controller

x
Menu Tags Controllers and click on Controller
Make sure that you have FX Series Serial selected in controller. Click OK.
Still under Tags Controllers, click Settings.
Under Serial, enter the settings for the communication between the application (panel)
and the controller.
www.beijer.se
3 (9)
Parameter
Description
Port
Select which COM port to use for the connection.
Baud
Set the communication speed in baud for the selected COM port.
Parity
Set the parity for the selected COM port.
Data bits
Set the data bits for the selected COM port.
Stop bits
Set the stop bits for the selected COM port.
KI00318 2013-02
KI_eng.dot, 070221
When running a panel project you can see settings for the serial ports under System.
Example below is a TxA panel.
www.beijer.se
4 (9)
KI00318 2013-02
KI_eng.dot, 070221
3.2 Serial routing

x
Expand the branch Routing. This is where we set up the communication with the device that
will communicate through the panel.
Enter Serial as communication and select Transparent or Passthrough as mode. Enter the
rest of the parameters equivalent to the device parameters. When done click OK.
Parameter
Description
Communication
Enable routing communication by selecting the communication method.
Mode
The kind of routing mode used when communicating through the HMI.
Timeout
The number of seconds with no routing communication the HMI will wait before
returning from the routing mode and start functioning normally again.
Serial port
The serial port used for running routing communication. NOTE: If the HMI is
connected to the controller using a serial port a different port has to be selected in
this setting.
Baud
Set the communication speed in baud for the selected COM port.
Parity
Set the parity for the selected COM port.
Data bits
Set the data bits for the selected COM port.
Stop bits
Set the stop bits for the selected COM port.
Ethernet port
The Ethernet port number used in the HMI for running routing communication.
www.beijer.se
5 (9)
KI00318 2013-02
3.3 Ethernet routing

x
In Controller Settings, choose TCP as communication. Set Ethernet port or use default.
Download the the new settings.
KI_eng.dot, 070221
3.3.1 Settings in Serial/IP

Serial / IP is a software program that creates a virtual COM port for Ethernet
communications. It can be used in different programming tools for transfer and monitoring
of the PLC program via Ethernet.
A 30-day trial version can be found on Beijer Electronics website.
x
Open Serial/IP.
Enter the terminal IP-address and port number (selected in the routing settings) and
select a COM port higher than 5.
Click on Configuration Wizard.
www.beijer.se
6 (9)

x
KI00318 2013-02
Click on Start.
KI_eng.dot, 070221
Serial/IP is now connected to the panel.
www.beijer.se
7 (9)
KI00318 2013-02
3.3.2 Settings in GX (IEC) Developer

x Click on the menu Ports under Online Transfer Setup.
KI_eng.dot, 070221
Double click on Serial in the top left corner and select the COM port and transfer speed
used in Serial/IP. Click on Setup and verify the serial setup. Click OK.
www.beijer.se
8 (9)
KI00318 2013-02
Double click on PLC module and select via MAC/MTA transparent mode. Click OK.
Click on Connection test.
KI_eng.dot, 070221
The configuration is done!
www.beijer.se
9 (9)
Setting up Trend Viewer in iX Developer 2.0
KI00317 2013-02

This document explains how to set up Trend Viewer in iX Developer 2.0.
Trend Viewers are used to present chronological data from controller tags. The curves in a
trend viewer can have different sources of data. The source of data can be a log item for a
data logger. The values of the tag connected to the log item is then stored in the projects
database. The source can also be a Tag. The trend viewer curve then only shows real-time
values and is stored in a RAM cache.
- iX Developer 2.0

Page 1 (20)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
KI00317 2013-02
3 Set up taglist
KI_eng.dot, 070221
Just for example, we want to show the current from 3 motors in our Trend Viewer.
x
Open taglist from the Project Explorer.
Create 3 tags which will be our source.
www.beijer.se
2 (20)
KI00317 2013-02
4 Set up Data Logger

In this case we will be using a historical trend viewer so we will need a data logger. If you
want to use a trend only with tags as source (realtime trend view), you can skip this chapter.
x
Create a Data Logger found under the Insert tab in the ribbon menu.
KI_eng.dot, 070221
Once added it will show up in the Data Loggers ribbon of the Project Explorer.
www.beijer.se
3 (20)
KI00317 2013-02
4.1 Add tags in Data Logger

x
Use the Add button to add tags to your Data Logger. Enter suitable names and connect
the tags we ceated earlier.
The Settings button allows you to select how the data is collected.
You can log data on a fixed interval, on a tag event or using an action.
Logging of data can be made either by collecting all samples at every log event, or by
collecting only changed values. Collecting only changed values saves memory and improves
performance.
Limit the overall size by setting a maximum number of logged data rows.
x
In this case, enter a name for the logger and select to log with an interval of 5 seconds.
Click OK.
3.
KI_eng.dot, 070221
Run or Simulate the application in order to get the database populated.
www.beijer.se
4 (20)
KI00317 2013-02
5 Set up Trend Viewer

x
Enter a empty screen.
Create a Trend Viewer located under Home.
Drag and drop to create the desired size of the Trend Viewer.
KI_eng.dot, 070221
Outlook of a trend in chrome layout:
www.beijer.se
5 (20)
KI00317 2013-02
5.1 Trend Viewer curves

Under General in trend, there are numerous options. Select desired formatting on the trend
viewer.
x
Click on Edit Curves.
Add curves and name them. Select a suitable colour.
Connect the tags from the Data logger.
Click OK.
Because we are using a historical Trend Viewer we connect the Data Logger under Log Item
and select the correct tag. If we where to be using realtime trend view we would connect the
tags under the column Tag.
KI_eng.dot, 070221
You can mix and match data from different database tables (e.g. Data Logger) and realtime
tag data in the same trend object.
www.beijer.se
6 (20)

5.2
KI00317 2013-02
Trend Viewer Historical control

Two actions allow you to control the Trend Viewer while the application is running.
1. Show Trend Viewer Legend Allows you to hide/show trends and displays the values of
the curves at the cursor.
KI_eng.dot, 070221
2. Trend Viewer History Allows you to turn on/off history mode, or show a dialog that
lets the user set start/stop time.
www.beijer.se
7 (20)
KI_eng.dot, 070221
5.3
KI00317 2013-02
Trend Viewer - Historical Funtions

x
Create 4 buttons.
Create an action for the button HISTORY - On.
In the same way, create an action for the other 3 buttons.
www.beijer.se
8 (20)

x
KI00317 2013-02
Create 3 analogue numeric to set different values on the tags we made.
When done, you should have something like this:
KI_eng.dot, 070221
www.beijer.se
9 (20)

x
KI00317 2013-02
Create a action on the Trend Viewer itself. Select the action Show Trend Viewer Legend
under Mouse Down.
KI_eng.dot, 070221
This legend will show when you click on the trend viewer:
www.beijer.se
10 (20)
KI00317 2013-02
Trend dynamics
Several trend viewer properties can be made dynamic, i. e. dependent on tag values. This
may be useful, for example, when presenting trend viewer values of different formats in the
same trend viewer object.
KI_eng.dot, 070221
If dynamic trend viewer properties are used, the corresponding property settings made in the
Value Scale group for the trend viewer object are ignored.
Parameter
Description
Value Scale Min /

Value Scale Max
Minimum/maximum value of the Y-scale. The design mode value is used only for
increased understanding in design time when tag values do not affect the minimum
and maximum values.
Time Span
The time span of the X-axis in seconds.
Time Offset in
History Mode
Makes it possible to use an offset to step back in history mode. The start value is
when history mode was entered. The unit is seconds.
www.beijer.se
11 (20)

6.1
KI00317 2013-02
Trend Dynamics - Time span
KI_eng.dot, 070221
Lets add Trend Dynamics so that we can change the time span and time offset in our trend.
x
Start by adding two tags in taglist; TimeSpan and TimeOffset.
Select the tags in Trend Dynamics.
Add a ComboBox and a text object.
www.beijer.se
12 (20)
KI00317 2013-02
Select the ComboBox and under General click on Configure Text.
Connect TimeSpan to the configuration and type in the text you want to display. Type in
the values for each text. Remember that the time span is in seconds.
KI_eng.dot, 070221
So as when you change the value of the ComboBox the time span will change
correspondingly.
www.beijer.se
13 (20)

6.2
KI00317 2013-02
Trend Dynamics - Time Offset

By making some simple buttons we can navigate through the history offset.
You can only change the offset when in history mode so a enable/disable function on these
buttons is a good idea.
x
Create buttons so we can navigate. You will find these buttons in your component
library.
The pause and play-buttons have the same functions as History-On and Off as we used
earlier.
KI_eng.dot, 070221
Setup the buttons as follows.
www.beijer.se
14 (20)

6.3
KI00317 2013-02
Trend Dynamics - Zoom
KI_eng.dot, 070221
To be able to navigate freely In, Out, Up, Down, Left, Right we must supplement with some
buttons.
x
First, add "Ymin" and Ymax to your taglist. And also add a initial of 100 to "Ymax" to
set the default value on the trend. Make sure you have "Others" checked.
Connect the tags in Trend Dynamics.
Add the following buttons to your screen:
www.beijer.se
15 (20)
KI00317 2013-02
Select the Up button and under Action, extend the Click ribbon.
Do the same thing with the Down button but Decrement instead of Increment.
Select the Zoom In button and under Action extend the Click ribbon.
KI_eng.dot, 070221
By decrementing "Ymax" and incrementing "Ymin" we get the effect of zooming in.
Do the same thing with the Zoom Out button but vice versa to get the effect of zooming
out.
www.beijer.se
16 (20)
KI00317 2013-02
KI_eng.dot, 070221
Now you might have something looking like this:
www.beijer.se
17 (20)
KI00317 2013-02
7 Data Logger Control

Four actions allows you to control the Data Logger:
Clear Data Logger allows you to clear a log.
LogOnce allows you to force the logger to log data.
Start logging allows you to start logging data.
KI_eng.dot, 070221
Stop logging allows you to stop logging data.
www.beijer.se
18 (20)

7.1
KI00317 2013-02
Data Logger - Export

Any individual data logger database can be exported in csv format using the Database Export
action. It can be saved to a USB memory stick, an external memory card or to the project files
folder. The following databases are available for csv export: Alarm Server, Audit Trail, Data
Logger and Trend Viewer.
The export is triggered via an action, select Database Export, found in the Database group.
Clicking the "..." button next to the selected database opens up a dialog from which the default
database export properties may be altered.
KI_eng.dot, 070221
Database Export from Operator Panel Target:
It is possible to select export to USB memory stick or external memory card, and also setting
another name of the export file. Leaving the Overwrite box unchecked adds date and time to the
export file name, thus avoiding overwriting an existing export file.
www.beijer.se
19 (20)
KI_eng.dot, 070221
KI00317 2013-02
Create a button and set click action to Database Export. Select the Data Logger you want to
export.
Depending on if you run a panel-project or a PC-project this dialog looks different. Select the
option you want. Remember that export will not work in simulation.
www.beijer.se
20 (20)
Screen ID in iX Developer 2.0
KI00316 2013-02

This document explains Screen ID and how it can be set up.
There are 2 systemtags in iX which enables you to read the current screen and to set a new
screen. This is done by setting a unique number to the screens.
This function for example enables you to control the screens with PLC/controller.
- iX Developer 2.0

Please use the address manual@ beijer.se for feedback on our Start Up documents
Page 1 (6)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
KI00316 2013-02
KI_eng.dot, 070221
3 Adding systemtags
x
Open taglist from the Project Explorer.
Add System Tag by expanding the Add button.
Select Current Screen ID located under the Project group. Click "OK".
Also add the tag New Screen ID in the same way.
www.beijer.se
2 (6)
KI00316 2013-02
4 Set Screen ID
x
Add 2 more screens to your project.
Select the first screen and under "General". Type in a screen ID number. In this case
Screen 1 = 10, Screen 2 = 20...
This can also be done in Property Grid of the screen.
KI_eng.dot, 070221
Now we have given each screen a unique ScreenID.
www.beijer.se
3 (6)
KI00316 2013-02
Create 2 analogue numeric in Screen 1. Connect the tags and add explaining text.
Simply copy these to the other screens.
Add text to tell you which screen is which.
Run the project and now you will be able to change screen by typing 10, 20 or 30 in "New
Screen ID".
KI_eng.dot, 070221
Example:
www.beijer.se
4 (6)
KI00316 2013-02
KI_eng.dot, 070221
Lets replace the analogue numeric. We can use anything that can change the screen ID. One
example of that is RollerPanel.
x
Add a RollerPanel.
Select the RollerPanel and under General, click on Configure Text.
Connect the "NewScreenID"-tag, type the text you want to be displayed and enter the correct
values in Start/end value. Click OK.
Copy & paste the RollerPanel to the other screens.
www.beijer.se
5 (6)

x
KI00316 2013-02
Test.
KI_eng.dot, 070221
Screen ID enables you to control the screens from the PLC/controller. If this is to be used it's
important to remember that "NewScreenId" only reacts to value changes.
www.beijer.se
6 (6)
Remote Alarm Server in iX Developer 2.0
KI00315 2013-02

This document explains how to set up Remote Alarm Server in iX Developer 2.0.
The alarm server in the iX-Developer project can operate as a stand-alone alarm
server, processing alarms and showing these in the alarm viewer and alarm
indicator. Alternatively, the alarm server can distribute alarms to clients. Each
alarm server can function as alarm server and/or alarm client. The remote alarm
server functionality is set up via properties.
- iX Developer 2.0

Page 1 (6)
P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
KI00315 2013-02
3 Set up Remote Alarm Server

Start with creating an alarm viewer in your alarm server application. Found in the ribbon
menu Objects.
Add a new button and set it to toggle a tag which will create our alarm. Rename it to
Generate Error.
KI_eng.dot, 070221
KI_eng.dot, 070221
Something like this:
www.beijer.se
2 (6)
KI_eng.dot, 070221
KI00315 2013-02
Open Alarm Server.
Add alarm to the server. Connect the same tag as we used on the button in the alarm
screen. Set condition to EqualTo and trigger value to 1.
www.beijer.se
3 (6)
KI00315 2013-02
3.1 Alarm Server Communication

x
When in Alarm Server click on the text an open Property Grid.
Make sure that Property Grid is selected in the View Ribbon.
The following properties, located in the Misc group, needs to be set up for the remote alarm
server:
Property
MaximumAlarm
EventsToDistribute
Description
The number of events to distribute to the clients. The number of distributed alarms
affects performance.
ServerMode
The alarm server can assume the following modes:

Disabled: The alarm server is disabled and no alarms are processed
Local: The alarm server processes alarms of its own.
Remote: Alarms are distributed to remote clients.
Both: The alarm server processes alarms of its own and also distributes them to
remote clients.
ServerPort
Any available port. The port needs to correspond to the port setting for the remote
alarm client.
Because we want to distribute our alarm server to remote clients we select ServerMode
as Remote. And we set ServerPort at the default value of 1000.
KI_eng.dot, 070221
The configuration of the Alarm Server is done.
www.beijer.se
4 (6)
KI00315 2013-02
4 Set up Remote Alarm client

x
Create an alarm viewer in your alarm client application.
The following properties, located in the Misc group, need to be set up for the
remote alarm client:
Property
ServerAddress
Description
The IP address of the remote alarm server.
ServerPort
Any available port. The port needs to correspond to the port setting for the remote
alarm server.
Select the alarm viewer and go to properties. Look under Misc.
Enter the IP-Address of the remote alarm server and the matching port no.
The configuration of the alarm client is done!
KI_eng.dot, 070221
Run both applications and test.
www.beijer.se
5 (6)
KI00315 2013-02
5 Remote Alarm Server limitations
KI_eng.dot, 070221
Most functions work exactly the same regardless if a local or remote alarm server is used,
but there are a few limitations:
x
In projects where multiple languages are used, switching language in the alarm server
results in using the current language for all new alarm texts. Alarms distributed before
the language was switched in the server will remain in the previous language in the
client.
Pressing the Info button in the alarm viewer in runtime will not result in any actions for
a remote alarm, unless the same project is used for the server and the client. The script
event AlarmInfoRequested can be used instead.
Unless the same project is used for the server and the client, filtering (pressing the Filter
button in the alarm viewer) can only be made in runtime for remote alarms, since the
remote server may include e.g. alarm groups that are different from the project in which
the alarm viewer was configured.
www.beijer.se
6 (6)
Remote Access (FTP and VNC) in

iX Developer 2.0
KI00314 2013-02

This document explains how to set up Remote Access in iX Developer 2.0.
When FTP is enabled, it is possible to upload/download files to/from the operator panel
provided that there is an FTP client program in the PC, e.g. Internet Explorer, Windows
Commander or some other standard FTP program.
The Remote Access function makes it possible to access, reflect and control an operator panel
from a PC by using the free VNC client program Remote Access Viewer together with the built-in
VNC server in the operator panel.
- iX Developer 2.0
- Remote Access Viewer
- FTP-Client
- iX-Panel

Page 1 (9)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
Remote Access (FTP and VNC) in iX Developer 2.0
KI00314 2013-02
3 Set up Remote Access in iX Developer 2.0

x
In the project application click on Remote Access under System in the ribbon menu.
Check Enable Remote Access Server and, if wanted, add password.
The view only password allows reflecting the panel remotely; the full access password
allows also control of maneuverable objects in the panel.
Note: To protect secrecy when entering a password via Remote Access Viewer, it is
recommended to use the PC keyboard. Otherwise it is possible that the cursor on the remote
operator panel displays which keys are pressed on the alphanumeric keyboard.
KI_eng.dot, 070221
Download the application for the settings to take effect.
www.beijer.se
2 (9)
KI00314 2013-02
4 Remote Access Viewer

x
If not already, download and install Remote Access Viewer.
Only one VNC client can connect to the VNC server.

Only available when an operator panel is selected as target.
x
Open the program and simply type in the panel IP-address. Click on Connect.
A message box will ask for password. Enter password and click OK.
A mirror of the project is displayed on your screen.
KI_eng.dot, 070221
Depending on the password entered, the slider below will be accessible or not.
www.beijer.se
3 (9)
KI00314 2013-02
5 Web browser
You can also remote view with a web browser.
Java needs to be installed for remote viewing to work.
KI_eng.dot, 070221
Type in the target IP-address and port no. The IP-address and port no. is separated with
colon.
www.beijer.se
4 (9)
KI00314 2013-02
6 FTP
It is possible to set up access to the FTP server with login requirements and/or as
anonymous. An anonymous user has read-only access rights. A user that logs in with the
correct user name and password gets read/write access rights
Only available when an operator panel is selected as target.
FTP is not supported for Panel TxC.
x
In the project application click on FTP under System in the ribbon menu.
KI_eng.dot, 070221
Download the application for the settings to take effect.
www.beijer.se
5 (9)
KI00314 2013-02
6.1 Connection to the panel

When the application has been downloaded and started we can access the FTP-server.
There are many programs that will work as FTP-client, ex web browsers, windows explorer,
Command Prompt, FileZilla, Total Commander etc etc.
Its recommended to run a clean FTP-client for best result. For example FileZilla which is a
free software.
6.2 Using Windows Explorer

x
Open any Windows Explorer window (My Documents, My Computer etc) and enter the
target server address.
In this case: ftp://192.168.1.10.
KI_eng.dot, 070221
If you allowed anonymous login you will now be able to access the folder with read-only
access.
x
If you entered a password an error- message will appear. Click OK.
Right-click inside the folder and click on Login As.
www.beijer.se
6 (9)

x
KI00314 2013-02
Enter username and password. Click on Log On.
KI_eng.dot, 070221
You can skip the above message and login screen by using:
ftp://username:password@ftpserver in this case ftp://beijer:beijer@192.168.1.10.
www.beijer.se
7 (9)
KI00314 2013-02
6.3 Using Command Prompt

Using Command Prompt is useful to check connection and login. But its not very user
friendly.
x
Open cmd.exe.
Type ftp.
Type open ServerIP ex. Open 192.168.1.10.
Enter your username.
Enter your password.
KI_eng.dot, 070221
Type help to list all commands.
www.beijer.se
8 (9)
KI00314 2013-02
6.4 Using FileZilla

Install and open FileZilla. FieZilla can be downloaded at http://filezilla-project.org/.
x
Enter IP-address, username and password and click on Quickconnect.
KI_eng.dot, 070221
Here you can add and remove files:
www.beijer.se
9 (9)
QnUDE Ethernet - iX Panel
KI00313 2013-02

This document explains how to set up a QnUDE Ethernet connection with iX Developer 2.0
with MC Protocol.
Start to read the Start-up document of QnUDE(H) Cpus (KI00278), it can be downloaded
from Beijer Electronics homepage.
- iX Developer 2.0
- GX IEC Developer 7.04, GX Developer or GX Works2
-
QnUDE (ex Q03UDE)
iX Panel (TxA, TxB, TxC)

Page 1 (5)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
QnUDE Ethernet iX Panel
KI00313 2013-02
3 Set up Q-CPU
This chapter will explain how to set up the Q-CPU in GX (IEC) Developer and GX Works2.
3.1 Settings in GX (IEC) Developer

x
Adjust the Built-in Ethernet port open settings located in PLC-Parameter.
Note!
The setting in Host station port No. must always be hexadecimal format, for example
port no. 1025 dec => 0401 hex.
KI_eng.dot, 070221
Check Enable online change (FTP,MC protocol) to be able to write to the iX-terminal,
otherwise it's read only:
www.beijer.se
2 (5)
KI00313 2013-02
KI_eng.dot, 070221
3.2 Settings in GX Works2

x
Adjust the Built-in Ethernet port open settings located in PLC-Parameter.
Port no. in decimal.
www.beijer.se
3 (5)
KI00313 2013-02
4 Set up iX Developer 2.0
KI_eng.dot, 070221
When creating a new project or adding/changing controller:

x
Select MELSEC controller with MC Protocol.
Open settings located under Tags.
www.beijer.se
4 (5)

x
Change settings if needed on your set up.
Click on Stations to change IP and Port no. (in decimal). Click OK
KI00313 2013-02

Tip!
KI_eng.dot, 070221
Help about driver, click on Help
www.beijer.se
5 (5)
OPC UA Server - iX Developer 2.0
KI00312 2013-02

This document explains how to set up OPC UA Server in iX Developer 2.0.
OPC is an industrial standard created in a collaboration of automation hardware and
software suppliers. The standard defines methods for exchanging real-time automation data
between PC-based clients using Microsoft operating systems.
An OPC server acts as a controller towards iX Developer.
OPC UA Server enables the possibility to publish tags.
- iX Developer 2.0

Page 1 (6)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
KI00312 2013-02
3 Set up OPC UA Server

x
In the application you want to use as OPC UA Server, open OPC UA Server properties
under System ribbon.
Enable OPC UA Server. In this case the port nr 4840 is used. Enter password if desired.
Click OK.
Parameter
Description
Enable OPC UA Server Click this checkbox to enable n the OPC UA server.
Port
Enter a server port number.
Allow anonymous login Click this checkbox to enable anonymous login. For a secured login
enter user nameand password and leave the checkbox unchecked.
KI_eng.dot, 070221
Add a analogue numeric and connect it to a tag. We will later look at the same tag from
the OPC UA client.
www.beijer.se
2 (6)
KI00312 2013-02
4 Set up OPC UA Client
KI_eng.dot, 070221
Settings for the OPC UA client can be made in the Choose Controller dialog.
x
Go to Tags. Under Controllers, add a new controller by clicking on Add.
Enter the URL of the OPC UA Server. Click OK.
Rename the controller to something suitable and click on Settings.
www.beijer.se
3 (6)

x
KI00312 2013-02
If you have choosen password protection in OPC UA Server this is where you enter the
password. Click OK.
Parameter
Description
URL
Authentication
settings
Enter URL to the UPC UA server.

Only UA TCP Binary is supported which means the URL must start with opc.tcp://
Choose whether to use anonymous login or enter a user name and password to enable a
secured login.
Namespace settings
This setting offers a possibility to declare a namespace URI and bind it to a prefix.
Tag View settings
Namespace separator character: Enter a character to be used to separate the namespace

URI prefix from the tag ID when presented on the tag tab.
KI_eng.dot, 070221
Default namespace: Select the default namespace URI prefix to be used when entering a
tag on the tag tab.
www.beijer.se
4 (6)
KI00312 2013-02
4.1 Add Tags from OPC UA Server

x
Go back to Tags and add a new tag.
Now you have two controllers, one of which is OPC UA Server in the field Controllers.
x
Simply type in the name of the tag you want to access. Press Enter and you will see the
Tag ID along with the preferred namespace URI prefix, defined in the controller settings
dialog.
Note: No prefix is needed when connecting to an iX server.
Array tags are not supported by OPCUA controllers.

When having a lot of tags its much easier to export tags to Excel, modify them and import
them to the OPC UA Client.
Export client tags with the setup as the picture above (server added in controller). This is to
have the right template for the tags.
Export the tags from the server. Copy the tags (name) you want to use and paste them into
the client taglist under controller.
Create a analogue numeric in the OPC UA Client application and connect it to the tag.
KI_eng.dot, 070221
www.beijer.se
5 (6)
KI00312 2013-02
5 OPC UA General Information And Limitations

5.1 Address space
All tags, except array tags, defined in project will be shown.
The tags will be put in a folder named Tags in Namespace TagProvider in the server.
The NodeClass of all tags will be Variable.
All tag values will be published scaled with the offset and gain of the tag.
5.2 Tag PropertiesMapping

Parameter
Description
Tag property
UA Server Attribute
Name
DisplayName / BrowseName
Data Type
DataType
Access Right
AccessLevel / UserAccessLevel
Description
Description
Poll Group Interval
MinimumSamplingInterval
5.3 Certificate
A certificate will be auto generated and self-signed when the server first starts up.
The certificate will be valid for 20 years.
The certificate contains no IP address since this could change after the certificate has been
generated.
KI_eng.dot, 070221
5.4 Limitations
Parameter
Description
Discovery
Not supported
Encoding / Transport
Only UATCP Binary
User authentication
Only user name / password. Only one account
Security
No encryption support
Array of tags
Not supported
www.beijer.se
6 (6)
FX3U-ENET - iX Panel
KI00311 2013-02

This document explains how to set up a FX3U-ENET connection with iX Developer 2.0.
- iX Developer 2.0
- FX Configurator EN 1.30
-
FX3U ENET
SC-09 cable
iX Panel (TxA, TxB, TxC)

eng.dot, 070221
KI_eng.dot, 070221
Page 1 (8)
P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
KI00311 2013-02
3 Set up FX Configurator EN
Make sure that you have FX Configurator installed. The installation comes with the same CD as
the GX (IEC) Developer installation, it can also be found on our website.
x
Open FX Configurator, either via GX (IEC) Developer or directly from your computer (when
using GX Works2 for example).
How to open from GX (IEC) Developer:
KI_eng.dot, 070221
Select Module Type and Module Name. Click on Configure module... and FX Configurator
will open.
www.beijer.se
2 (8)
KI_eng.dot, 070221
KI00311 2013-02
When FX Configurator is opened click on Module None to select where the special module
is located. If its located as the first special module to the right of the basic unit, choose
Module 0. If its located as the second special module to the right, choose Module 1 etc.
Click on Operational settings and set the parameters as follows. Click on End.
www.beijer.se
3 (8)
x
KI00311 2013-02
Click on Open settings on the start screen.
1. Set UDP.
2. Set Receive.
3. Set Procedure exist (MC).
4. Set Disable.
5. Set No confirm.
6. Set 5001.
7. Click No Settings and set 255.255.255.255 in decimal or FF.FF.FF.FF in hex.
KI_eng.dot, 070221
8. Set Transmission target device Port No. : 65535
www.beijer.se
4 (8)
KI_eng.dot, 070221
KI00311 2013-02
Click on Transfer setup on the start screen and select Serial port/USB. Click on Connection
test to make sure you have connection. End with OK.
Click on Write on the start screen. Click write again and the parameters will be downloaded to
the module. Use SC-09 cable.
Make a reset on the PLC.
Make sure to save the configuration.
www.beijer.se
5 (8)
x
KI00311 2013-02
Only when using GX IEC Developer, select the saved configuration.
KI_eng.dot, 070221
The module configuration is done!
www.beijer.se
6 (8)
KI00311 2013-02
4 Set up iX Developer 2.0
KI_eng.dot, 070221
When creating a new project or by changing the controller in Tags.

x
Choose FX3U-ENET protocol.
Open settings located under Tags - Controllers.
www.beijer.se
7 (8)
KI_eng.dot, 070221
x
Change settings if needed on your set up.
Click on Stations to change IP and Port no. Click OK
KI00311 2013-02

www.beijer.se
8 (8)
Alias in iX Developer 2.0
KI00310 2013-02

This document explains how to set up and use aliases in iX Developer 2.0.
An alias should be treated as a property of a screen and can act as a stand-in for a tag. The
alias can be used to reference a tag wherever that tag can be referenced directly. When used,
iX Developer will act the same as if the original tag had been used. Each screen using
aliases can be configured with a different instance with different tag references.
Using aliases will enable reuse of screens without having to create a new duplicated screen.
- iX Developer 2.0

Page 1 (6)
KI_eng.dot, 070221

P.O. Box 426
Telephone +46 40 35 86 00
Fax +46 40 93 23 01
Subsidiaries
KI00310 2013-02
3 Set up screens and creating aliases

In this Start-Up document we will pretend that we have 3 motors which we want to set 2
parameters to, Speed and Max current. Aliases will help us to make this easy.
x
Create 3 buttons on the startup screen and name them Motor 1/2/3.
Create a new screen.
Add 2 sliders and 1 button to the new screen.
KI_eng.dot, 070221
The sliders will represent the motor parameters and the button will close the screen.
www.beijer.se
2 (6)
KI00310 2013-02
3.1 Adding aliases

x
On the bottom left of the screen, on the desktop view mode tabs, click on Aliases.
Add two aliases by clicking on Add. Name the 2 aliases like the parameters we want to
use. These names will only be shown locally on the current screen.
In the Default Value column, type in a default tag name. Click on enter and the tag will
automatically be created or browse for desired tag.
Parameter
Alias Name
Default
Value
KI_eng.dot, 070221
Data Type
www.beijer.se
Description
Symbolic name. The name can be any alphanumeric string, beginning with a letter (a-z, AZ).
Selection of tags to create aliases of. If no tag is selected the alias will be treated as a local
screen variable.
The default value will be the default value for the alias in the created instances. It will also
be the reference for the default instance.
Selection of data type. This setting is enabled by first clicking the Data Type checkbox.
The data type will by default reflect the data type of the selected Default Value.
3 (6)
KI00310 2013-02
3.2 Adding instances

x
Click on Instances.
The aliases created in the project are presented in a table on the instances tab. It is possible
to change the value for the aliases in this tab, in order to override the default value
configured in the aliases tab.
If a value for an alias is changed in the instances tab, the new value is displayed with bold
text to indicate that it differs from the alias default value.
x
Add 3 instances.
Add instance names and alias values.
Parameter
Instance
KI_eng.dot, 070221
Aliases
www.beijer.se
Description
Symbolic name. The name can be any alphanumeric string, beginning
with a letter (a-z, A-Z).
The names of all aliases created in the project will be displayed in the
columns headers. The values connected to the aliases will be listed in
each columns.
4 (6)
KI00310 2013-02
3.3 Connecting alias to object

x
Go back to layout view mode.
Select the Speed-slider and expand the tags configuration window. Click on Aliases
and select MotorSpeed.
KI_eng.dot, 070221
When connected:
Do the same thing with Max current-slider.
Set the Close-button action to close the screen.
www.beijer.se
5 (6)
KI00310 2013-02
3.4 Show screen action with instances

The Show Screen action can be used to display a specific screen. For screens that have
aliases, it is also possible to select which instance of the screen to use, and thereby also
which set of tags to assign to the screens aliases.
x
Back on the startup screen. Select button Motor 1 and click on Actions. Select Show
Screen and choose Screen2 (with aliases). Now we can select which instance we want to
use. In this case ParamMotor1.
The Default option is a virtual instance configured with the alias default values.
Do the same thing with motor 2 and 3.
Run the program and test the function.
4 Limitations
Alias do not support array tags.
Alias can not be used in connection with expressions.
Alias can not be used with the TrendViewer object.
KI_eng.dot, 070221
There is no scripting support for ValueChange-event on an alias.
www.beijer.se
6 (6)
Load IX project from USB
This procedure applies to Terminals running CE operating system e.g. TxA, TxB series.
1. Create and rebuild the IX project in IX developer
2. Insert an USB memory into the computer, or export to e.g the desktop, if files are to be
sent by email.
Select destination for the export and press OK
Framtagen av
Datum
OPN
2012-10-25
Godknd av
Revision
Revisionsdatum
Nummer
Sida
1 (2)
Load IX project from USB
3. If the export target is an USB stick, the USB is now ready to be inserted to a terminal
4. If the project is to be emailed to the end user, you need to zip the folder named Project,
and email this folder. The end user then unzip this to his USB device.
The other files\folder created are not necessary, for USB transfer.
This files make it possible to launch the IX project transfer interface, without having IX
developer installed. Making it possible for the end user to transfer the project via Ethernet, as
if IX were installed.
The only folder needed on the USB, is the Project folder, and it has to be located in the root
catalogue (lowest level, e.g E:\project)
5.
6.
7.
8.
Insert the USB to the terminal

Restart the terminal
You will now be asked if you wish to load the project from the USB
Then if there is already a project in the terminal you will be asked if you wish to create a
backup of the existing project. (yes\no)
9. If yes a backup will be created on the USB stick,
10. Project will then be loaded, and the terminal restart
PC targets:
Use same procedure for PC targets, except here you need to copy the Project folder from the
USB to the Runtime PC manually, overwriting the previous project.
To start the project on a Runtime pc, create a shortcut or click the projectName.exe file
located inside the Project folder. (e.g. project50.exe inn sample below)
Framtagen av
Datum
OPN
2012-10-25
Godknd av
Revision
Revisionsdatum
Nummer
Sida
2 (2)
Alarm List Generator Excel macro

Introduction
The alarm list generator Excel macro takes a previously exported iX-Developer XLS tag list and
converts it into a XLS file that can be imported back into the iX-Developer alarm list.
The main program dialog
The converter reads all the tags and creates one alarm item of every tag with some preset
settings.
* The alarm item Name is AlarmItem followed by a number and the groupname set in the dialog.
* The alarm item Text is set to the Description in the taglist.
* The alarm item Tag is set to the Tagname in the taglist.
* The alarm item group name is taken from the settings dialog (see above).
* The alarm item Condition is taken from the settings dialog (see above).
* The alarm item Trigger Value is taken from the settings dialog (see above).
* The alarm item History is taken from the settings dialog (see above).
* The alarm item Acknowledge Required is taken from the settings dialog (see above).
* The alarm item Repeat Count is taken from the settings dialog (see above).
* The alarm items Expression, Remote Acknowledge, Remote Ack Expression and Action are left
blank.
Tip!
Docmal_eng, 001110
The Alarm List Generator tries to generate alarm list

items for all tags found in the exported tag list.
If you do not want to generate alarm list items for all,
you might want to edit the exported tag list before
converting it.
Initiated by
Date
RAN
2011-09-14
Approved by
Revision
Revision date
Number
Page
1 (2)

How to use the macro
The macro needs a complete talist, with all columns exported.
Export the complete taglist in iX-Developer as a XLS-file and save it to a known location.
Open the AlarmGen.xls, you might be greeted by the following dialog:
The actual look of the dialog might differ depending on version of Excel used.
[Enable Macros] to start the macro.

You are presented with the main dialog:
Name of the
alarm group
Alarm trigger
conditions
Alarm item
settings
Setup the conditions for the alarm items, the Alarm Group name an the additional settings, when
done, [Load and convert tag list to alarm list].
You are presented by an open file dialog, select the previously exported taglist file and [Open]
The tag list is opened and converted to an alarm list, close Alarm List Generator by clicking on
the close button at the top right corner of the window.
Modify and adjust the alarm list to match you needs, remove unwanted alarm items, modify
trigger conditions and save the new alarm list.
Docmal_eng, 001110
In iX-developer, import the XLS file back into the alarm list, and you are done.
Initiated by
Date
RAN
2011-09-14
Approved by
Revision
Revision date
Number
Page
2 (2)

BEIJER - StartUp Ix (09 - 2014)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

BEIJER - StartUp Ix (09 - 2014)

Încărcat de

Drepturi de autor:

Formate disponibile

Start-Up

XAML-Import into iX Developer 2.10

1 Function and area of use

2 About the Start-up document

MAxx831x (Reference manual)

MAxx832x (User Guide)

This document and other Start-Up documents can be downloaded from

Parent company: Sweden

Beijer Electronics AB (publ)

Beijer Electronics Inc.

Beijer Electronics GmbH

XAML-Import into iX Developer 2.10

3 Basic Import XAML into iX

Open Microsoft Expression Design and draw your image

Select all your components and choose File -> Export

Use the same settings as shown in the picture below:

XAML-Import into iX Developer 2.10

Click Export All and save the file.

XAML-Import into iX Developer 2.10

XAML-Import into iX Developer 2.10

4 Advanced XAML bindings in iX

Fill, outline and outline thickness

4.2 Dynamic properties

XAML-Import into iX Developer 2.10

XAML code before modification

Modify the xaml code

<?xml version="1.0" encoding="utf-8"?>

XAML-Import into iX Developer 2.10

4.3 Import to iX Developer

Select the XAML file that you modified in Kaxaml

Alarm Distributor in iX Developer 2.0

1 Function and area of use

2 About the Start-up document

MAxx831x (Reference manual)

MAxx832x (User Guide)

This document and other Start-Up documents can be downloaded from

Parent company: Sweden

Beijer Electronics AB (publ)

Beijer Electronics Inc.

Beijer Electronics GmbH

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

4 The Alarm Distributor service

4.1 Adding and configure a internal Alarm Distributor service

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

4.2 Adding and configure a external Alarm Distributor service

Settings for a Client

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

Settings for a Server

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

Alarm Distributor in iX Developer 2.0

4.3 Configure Distribution Devices

Alarm Distributor in iX Developer 2.0

4.3.1 E-mail Device

Alarm Distributor in iX Developer 2.0

0RQRFKURPHODVHUSULQWHU 86%3&/H +3/DVHU-HW

Alarm Distributor in iX Developer 2.0

0RQRFKURPHODVHUSULQWHU 86%3&/H +3/DVHU-HW

Function and area of use