VISU+ 2 ...

Visualization software for Windows® systems

Version 2.53 or later

Data sheet
8150_en_06 © PHOENIX CONTACT 2021-11-30

1 Description
VISU+ 2 is a SCADA1 visualization software with HMI func- Information on maximum limits
tions, trending, and alarming.
The following maximum limits are individual limits that may
It comprises an engineering environment (engineering li- vary depending on the application.
cense) and a runtime environment (runtime license). The
development environment can be used to program applica- When you implement a project, please observe
tions. After completion, the runtime environment can be the limits of the PCs and HMI devices used (e.g.,
used for visualizing the application. database, ODBC, etc.). These limits are listed in
the following tables.
Features The following must be taken into consideration:
– Creation of visualization pages with operating and mon- – The listed limits are not binding but are rec-
itoring functions. ommended based on the tests carried out.
– Full range of SCADA functions. The user is responsible for defining the proj-
– Scalable visualization creation for PC (all Windows op- ect limits depending on available hardware
erating systems) and HMI (Windows Embedded CE). and overall resources used.
– Runtime licenses with HMI functions that are scalable – The resource limits refer to projects that are
and adjustable. executed on PCs with the minimum require-
ments or on WinCE devices from
Phoenix Contact.
– This data sheet does not claim to cover all
system limits of VISU+ 2. Further limits result
1 SCADA: Supervisory Control And Data Acquisition from the hardware used.

Make sure you always use the latest documentation.

It can be downloaded at phoenixcontact.net/products.

This document is valid for the products listed in Section “Ordering data” on page 3.
 VISU+ 2 ...

2 VISU+ products
VISU+ offers a range of different products.

2.1 Development environment (configuration software)

The editor is required to create the project. Everything that is required to create the visualization is integrated in the configu-
ration tool.
The VISU+ development environment offers the complete The VISU+ Express development environment is a free ver-
range of SCADA functions. Use the Phoenix Contact li- sion of the configuration tool with reduced functions.
cense manager that is automatically installed on every PC to
license the development environment.

2.2 Runtime environment (Runtime CE)

VISU+ Runtime is already part of an HMI and must not be licensed separately.

The HMI scope of functions is described in Sec-

tion “Overview of functions” on page 21.

2.3 Runtime environment (Runtime PC)

VISU+ Runtime for PC can be adapted to the visualization project. You can select from several I/O bytes (see Section “Notes
on the I/O data of the runtime environment” on page 2) and from licensed SCADA options.

2.4 Runtime environment (Runtime PC, linked to the device)

VISU+ Runtime for PC is linked to the device. It is a cost-effective HMI runtime version only available in conjunction with an
industrial PC and can be configured on the Phoenix Contact website when ordering an industrial PC.
The runtime is supplied with 1024 I/O bytes.

For the other HMI functions, please refer to the

following sections.

Notes on the I/O data of the runtime environment

The scope of the license depends on the actively used I/O The variables can be used in different structures: <name_-
bytes that are associated with the field. This way, projects structure>:<name_member> or <name_TAG.number_bit>
can contain an unlimited number of variables since only the in bits.
active bytes that are associated with the field are taken into Example: A license with 512 I/O bytes is required to ex-
account. change a 256-word data block with a SIEMENS PLC. How-
ever, the project can still have an unlimited number of vari-
Please note that a runtime license with 64 I/O
ables but can only exchange 512 bytes with the PLC at the
bytes, 512 type “bit” variables, or 32 type “word”
same time. If it can be ensured that no more than 256 bytes
variables can correspond to, for example: 1 word
are exchanged in a project at the same time, a license with
= 2 bytes or 16 bits.
a lower number of I/O bytes (RT 256 I/O bytes) is enough.
1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 VISU+ allows for exceeding the maximum number of I/O
bytes for a maximum of 2 hours.
Byte 0 Byte 1
– Only variables that are actually used and exchanged
with the field are counted for the license.
– The variables are counted as I/O bytes.
– Internal variables are not counted.
– Network variables are not counted (on the server).

8150_en_06 PHOENIX CONTACT 2 / 24

 VISU+ 2 ...

3 Ordering data

Products
Description I/O data1 Type Order No. Pcs./Pkt.
Development environment (engi- VISU+ 2 2988544 1
neering license) for VISU+ projects
Development environment for all op- VISU+ 2 EXPRESS 2402774 1
erator panels with integrated runtime
128 bytes VISU+ 2 RT 128 2988586 1
256 bytes VISU+ 2 RT 256 2988609 1
VISU+ 2 RT ... is the runtime envi- 512 bytes VISU+ 2 RT 512 2988612 1
ronment (runtime license) for 1024 bytes VISU+ 2 RT 1024 2988641 1
VISU+ 2 with the following restric- 2048 bytes VISU+ 2 RT 2048 2988528 1
tions for I/O data: 4096 bytes VISU+ 2 RT 4096 2988531 1
8192 bytes VISU+ 2 RT 8192 2988557 1
No restrictions VISU+ 2 RT UNLIMITED 2988654 1

128 bytes VISU+ 2 RT-D 128 2988696 1

256 bytes VISU+ 2 RT-D 256 2988719 1
VISU+ 2 RT-D ...2 is the runtime en- 512 bytes VISU+ 2 RT-D 512 2988722 1
vironment (runtime license) for 1024 bytes VISU+ 2 RT-D 1024 2988735 1
VISU+ 2 with the following restric-
tions for I/O data. Two direct drivers 2048 bytes VISU+ 2 RT-D 2048 2988764 1
can be connected additionally: 4096 bytes VISU+ 2 RT-D 4096 2988913 1
8192 bytes VISU+ 2 RT-D 8192 2988573 1
No restrictions VISU+ 2 RT D UNLIMITED 2988748 1
1 See Section “Notes on the I/O data of the runtime environment” on page 2
2
-D: as an addition to OPC DA (can be connected to 2 additional communication drivers)

Optional functions for VISU+ 2

Description Type VISU+ 2 RT(-D) ...

The functions listed here are optionally available for VISU+ 2. To order these functions, contact your nearest
Phoenix Contact representative.
VISU+ 2 alarm statistics VISU+ 2 Alarm Statistics Optional
VISU+ 2 OPC server VISU+ 2 OPC Server Optional
(OPC DA server, OPC XML DA server)
VISU+ 2 redundancy VISU+ 2 Redundancy Optional
VISU+ 2 alarm dispatcher VISU+ 2 Alarm Dispatcher Optional
(SMS, voice, fax, modem connection, e-mail)
VISU+ 2 networking VISU+ 2 Networking Optional
VISU+ 2 Web Client (xx = number of web clients) VISU+ 2 WBxx Optional

8150_en_06 PHOENIX CONTACT 3 / 24

 VISU+ 2 ...

Documentation
Description Type Order No. Pcs./Pkt.
User manual UM EN VISU+ VBA DRIVER – 1
Programmable VBA driver interfaces (APIs) for VISU+ 2 ... INTERFACES
User manual UM EN VISU+ – 1
Communication drivers for VISU+ 2 ... COMMUNICATION
DRIVERS
User manual UM EN VISU+ PROG – 1
Programming of VISU+ 2 ... under Windows® for desktop
systems
Quick start guide UM QS EN VISU+ TUTO- – 1
VISU+ 2 ... RIAL
User manual UM EN VISU+ VBA – 1
Programming with VBA script language in VISU+ 2 ...
User manual UM EN VISU+ WEB CLIENT – 1
Web Client technology in VISU+ 2 ... GUIDE
User manual UM EN VISU+ CE PROG – 1
Programming of VISU+ 2 ... under Windows CE
User manual UM EN VISU+ ALARM – 1
Configuration and operation of the alarm dispatcher in DISPATCHER
VISU+ 2 ...
Application note AH EN VISU+ BEST PRAC- – 1
Tips for using the VISU+ software TICE
Application note AH EN VISU+ MOBILE – 1
App for mobile system visualization
Application note AH EN VISU+ SCRIPTING – 1
Notes on creating scripts in VISU+ GUIDE
Application note AH EN VISU+ OPC UA – 1
How to import OPC UA variables into VISU+ and VISU+ Ex- IMPORT
press
Application note AH EN VISU+ TIA IMPORT – 1
How to import TIA Portal projects into VISU+ and VISU+ Ex-
press
Application note AH EN VISU+ HMI & CODE- – 1
Instructions on how to import CODESYS V3 variables into SYS V3
VISU+ and VISU+ Express
Application note AH EN VISU+ HTML5 – 1
HTML5 WebClient with VISU+ and VISU+ Express WEBCLIENT

8150_en_06 PHOENIX CONTACT 4 / 24

 VISU+ 2 ...

4 Available communication drivers for VISU+ 2 ...

Driver name Protocol Supported devices VISU+ Express VISU+

WinCE Win 32/64 WinCE Win 32/64
3S Codesys PLC Handler (gate- CoDeSys runtime X X X X
way) version 2.3, version 3.x
BacNet/IP BACNet/IP - All devices compatible with – X – X
Annex J BacNet/IP
Beckhoff TwinCAT ADS TwinCAT SoftPLC and I/O X X X X
B+R PVI Interface System 2000 and other de- X X X X
vices via PVI library
Bosch Rexroth MLPI All devices compatible with – X – X
MLPI (Motion Logic Pro-
gramming Interface)
Control-Techniques Modbus/TCP, All devices compatible with X X X X
CMP protocol Modbus/TCP and the CMP
protocol
Control-Techniques Modbus/RTU, All devices compatible with X X X X
CMP protocol Modbus/RTU and the CMP
protocol
CTI NITP, CAMP, All CTI 2500 devices with X X X X
TCP/IP an Ethernet interface
Endress + Hauser Energy Manager Endress + Hauser Energy – X – X
RMS621 Manager controllers
GE General Electric SNP-X GE PLCs 90 Series, X X X X
Micro Series
GE General Electric SRTP2 GE PLCs 90 Series, X X X X
Micro Series
Hilscher CIF 50 PROFIBUS DP, – X X X
PROFINET, EtherCAT,
PowerLink, CANopen,
Sercos, etc.
Hilscher CIFX PROFIBUS DP, – X X X
PROFINET, EtherCAT,
PowerLink, CANopen,
Sercos, etc.
Hilscher netX MPI Simatic S7-300, S7-400, – X X X
VIPA controllers
Hilscher S7 MPI Simatic S7-300, S7-400, – X X X
VIPA controllers
Hitachi Hitachi serial H Series – X – X
protocol
Hitachi Ethernet H-protocol H Series X X X X
KNX Konnex, EIB of 1 to All devices compatible with – X – X
15 KNX-EIB
IEC 60870-5-101 IEC 60870-5-101 All compatible RTUs, over X X X X
unbalanced serial RS-232 or RS-485
communication for
remote controlled
units RTU

8150_en_06 PHOENIX CONTACT 5 / 24

 VISU+ 2 ...

Driver name Protocol Supported devices VISU+ Express VISU+

WinCE Win 32/64 WinCE Win 32/64
IEC 60870-5-104 IEC 60870-5-104 All compatible RTUs, over X X X X
over TCP/IP (client) TCP/IP
IEC 60870-5-104 IEC 60870-5-104 All compatible RTUs, over X X X X
over TCP/IP (server) TCP/IP
IEC 61850 IEC 61850 MMS All IEC 61850 MMS serv- – X – X
Client ers
Jetter JetIPCOM7 Jetter controllers X X X X
Lenze Lenze Serial LecomAB X X X X
LonWorks LonWorks All compatible LonWorks – X – X
devices
Mitsubishi PTP Serial MELSEC-FX and X X X X
MELSEC-FX2N controllers
Mitsubishi MC protocol MELSEC-FX3U controllers X X – X
Mitsubishi Format 1 with MELSEC-Q series control- X X X X
checksum serial lers
protocol
Mitsubishi Melsec TCP for MELSEC-Q series control- X X X X
Q series protocol, lers
Melsec UDP for
Q series protocol
Moeller Sucom Serial proto- PS4-200, PS300, and – X X X
col PS400 series controllers
Modbus Modbus/TCP All devices that can be X X X X
(client) used as Modbus/TCP cli-
ents
Modbus Modbus/TCP All devices that can be X X X X
(server) used as Modbus/TCP
servers
Modbus Modbus/RTU, All devices that can be X X X X
Modbus/ASCII used as Modbus/RTUs
and Modbus/ASCII slaves
(master)
Modbus Modbus/RTU, All devices that can be X X X X
Modbus/ASCII used as Modbus/RTUs
and Modbus/ASCII mas-
(slave)
ters
MQTT Message Queuing - – X – X
Telemetry Transport
(MQTT)
Omron FINS Ethernet CS1/CJ1 controllers, X X X X
CV series, C200HX/
C200HG/C200HE control-
lers, CP/CPM2x controllers
Omron EtherNet/IP Omron NJ controllers X X X X
Omron FINS Serial CS1/CJ1 controllers, CV – X – X
series, C200HX/C200HG/
C200HE controllers, C/
CPM2x controllers

8150_en_06 PHOENIX CONTACT 6 / 24

 VISU+ 2 ...

Driver name Protocol Supported devices VISU+ Express VISU+

WinCE Win 32/64 WinCE Win 32/64
Omron Host Link CS1/CJ1 controllers, CV X X X X
series
C200HX/C200HG/
C200HE controllers, CP/
CPM2x controllers, CQM1
controllers
Panasonic MEWTOCOL - serial NAIS PLC FP series X X X X
and Ethernet com-
munication
Phoenix Contact INTERBUS All devices and I/Os com- – X X X
patible with INTERBUS
Phoenix Contact PLCI ILC 1x1 class, AXC 1000 X X X X
class, AXC 3000 class, PC
WORX SRT, PC WORX
RT BASIC
Phoenix Contact DualCAN CANopen, CANraw, – X X X
SAEJ1939
PROFIBUS PROFIBUS DP All controllers compatible – X X X
with PROFIBUS DP
Rockwell DF1 Serial PLC-5, SLC-500, Mi- X X X X
Automation croLogix, ControlLogix,
CompactLogix, and Flex-
Logix
Rockwell EtherNet/IP PLC-5, SLC-500, Mi- X X X X
Automation croLogix, ControlLogix,
CompactLogix, and Flex-
Logix
SAIA-Burgess Saia S-Bus protocol All controllers in the PCD – X – X
(multi mode) series
SAIA-Burgess Saia Data Mode pro- All controllers in the PCD X X X X
tocol series
Schneider Electric Modbus RTU, Modicon TSX and every X X X X
Group Modbus ASCII device that can be used as
a standard Modbus slave
(master)
Schneider Electric Modbus/TCP Modicon TSX and every X X X X
Group (server) device that can be used as
a standard Modbus/TCP
slave
Schneider Electric Uni-Telway Slave Telemecanique controllers – X X X
Group and devices compatible
with Uni-Telway
Siemens S7-MPI Simatic-S7-300/400 – – – –
Siemens S7-PPI Simatic-S7-200 – X X X
Siemens Siemens S7 Func- Simatic S7-300/400 X X X X
tions over MPI or
PROFIBUS
Siemens S7-TCP Simatic-S7-200/300/400/ X X X X
1200/1500

8150_en_06 PHOENIX CONTACT 7 / 24

 VISU+ 2 ...

Driver name Protocol Supported devices VISU+ Express VISU+

WinCE Win 32/64 WinCE Win 32/64
Siemens TIA PORTAL Simatic-S7-1200/1500 X X X X
SNMP SNMP All devices compatible with – X – X
SNMP
WITS WITS Master Serial Devices that support level – X – X
0 of the WITS protocol

8150_en_06 PHOENIX CONTACT 8 / 24

 VISU+ 2 ...

5 System requirements

Requirements for a VISU+ 2 development environment (engineering license) and requirements for a VISU+ 2
runtime environment (runtime license) with Win32/64 operating system
CPU Celeron/Sempron 1.6 GHz (Windows® XP), minimum, 3
GHz recommended
RAM 512 MB RAM (Windows® XP), minimum, 1 Gbyte recom-
mended
Hard drive space 1 Gbyte free memory (Windows® XP), minimum, 2 Gbytes
recommended
Monitor VGA (640 x 480 pixels), minimum, XGA (1024 x 768 pixels)
recommended
Supported operating systems Windows® XP SP 3
Windows® 2003 Server
Windows® 2008 Server
Windows® 2008 Server R2
Windows® Vista
Windows® 7
Windows® 8 (VISU+ version 2.31 or later)
Windows® 8.1 (VISU+ version 2.41 or later)
Windows® 10 (VISU+ version 2.41 or later)
Windows® 2012 Server
Windows® 2012 Server R2
Windows® 2016 Server

VISU+ 2 runtime environment (runtime license) with WinCE operating system

HMI devices under WinCE are delivered with VISU+ 2 runtime environment. Since devices have different capacities, some
VISU+ 2 functions can only be used to a limited degree on some HMI devices (see Section “Limits for VISU+ 2 projects
under WinCE” on page 14).

8150_en_06 PHOENIX CONTACT 9 / 24

 VISU+ 2 ...

6 Limits for VISU+ 2 projects on Win32/64 operating systems

Limits for VISU+ 2 projects (Win32/64)

General
Maximum number of pages Unlimited
Real-time database (variables database (tags))
Maximum number of variables (tags) 128000 I/O bytes
Size of the structure variables Total size: 32767 bytes, maximum
Variable names – Must not contain special characters
– Must not start with a special character or a digit
– May be up to 64 characters long
– “k” or “K” as an initial is reserved for IL logic (instruction
list: “Constant”)
Maximum number of remanent variables 16000
Maximum number of variables that can be linked in the 32000
network
Maximum number of variables with statistic evaluation 2048
Number of variables in the audit trail 2048
Maximum number of variables linked via ODBC 2048
Objects in process images
Maximum number of objects in a process image Unlimited, recommended: 5000 vector segments, maximum
Expressions Local variables may not be used in the expression for objects
that use VBA (Visual Basic for Applications) expressions.
Gradual filling The “pipe” object does not support gradual filling.
Network functions
Maximum number of network variables 32000
Maximum number of network connections for each display 32
window
Alarm management
Maximum number of alarms 32000 alarm threshold values for each project, a maximum
of 2048 alarm threshold values thereof with internal script
Maximum number of alarm priorities 99
Maximum number of characters for each alarm text string 256
Maximum number of alarm threshold values for each 128
alarm
Alarm dispatcher
Maximum number of possible alarm indications in the proj- 32000
ect
Maximum number of users (default) for each alarm indica- 32
tion
Maximum e-mail file size 512 kbytes
Maximum number of e-mail files 10
Data loggers
Maximum number of data loggers for each project 512
Maximum number of columns for each data logger 1024 (127 with IMDB, maximum)
Archive life cycle of the data logger (maximum number of 9999
days)

8150_en_06 PHOENIX CONTACT 10 / 24

 VISU+ 2 ...

Limits for VISU+ 2 projects (Win32/64)

The maximum life cycle of the data logger archive depends on the selected maximum database capacity (e.g.,
SQL Express: 2 Gbytes, maximum).
Maximum string size of historical data 256 bytes
Maximum sampling rate 100 ms
Recipes
Maximum number of recipes for each project 512
Maximum number of columns for each recipe 1024 (127 with IMDB, maximum)
Trends and data analysis
Maximum number of pens for each trend 64
Maximum number of displayable sampling points/nodes 10000
for each trend
Maximum sampling rate 10 ms
Events
Maximum number of event objects/events for each project 512
Schedulers
Maximum number of schedulers for each project (maxi- 512
mum number of event objects/events for each project)
Scalable objects
Maximum number of scalable objects 512
Language selection
Maximum number of strings for each language 32000
Maximum number of languages (columns) 128
Maximum number of characters for each string 1024
Memory and ODBC links
DSN name Some databases such as SQL Server do not support spaces
in the DSN name. Therefore, please do not use spaces in the
project names.
Column names Some databases such as SQL Server CE do not support
spaces in the column names of the databases. Therefore,
please do not use spaces in column names of the memories
or protocols such as data loggers, recipes, etc.
Recording frequencies The recording frequency depends on several factors. It
should not be less than 50 milliseconds.
User management (users and passwords)
Maximum number of users 8192
Maximum number of user groups 512
VBA scripts and IL logic (instruction list)
Maximum number of scripts 4096, 128 of which can be executed simultaneously (mul-
tithreads)
Maximum number of code lines for IL logic (instruction list) 12000
Variable types The following variable types are not supported:
– Double type variables (64-bit accuracy)
– String and byte array variables

8150_en_06 PHOENIX CONTACT 11 / 24

 VISU+ 2 ...

Limits for VISU+ 2 projects (Win32/64)

Web Clients
Maximum number of Web Client stations on a VISU+ 2 100
server
Maximum number of sub-projects for each higher-level proj- 32
ect

7 Limits for direct drivers in VISU+ 2 projects (Win32/64)

Limits for direct drivers in VISU+ 2 projects (Win32/64)

Maximum number of stations on a driver 128 stations per driver, depending on protocol addressing
and protocol boundaries
Maximum number of drivers that can be used simultaneously 2 (depending on the license)
Data structures Data structures are supported depending on the driver and
the protocol.
Sub-projects The same driver cannot be used in main and sub-projects. If
required, the driver must be copied and renamed.

8 Performance results of selected systems as an indication for the performance

of the drivers
Average update time in seconds
The test results listed here are based on the hard- Data type = WORD
ware/software combination mentioned and can Active variables for writing
only be taken as an indication for achievable com- Active variables 1 10 50
munication speeds. for reading
Please note that the specified speeds depend on 500 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.0
the systems used. Depending on your applica- 1000 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.0
tion, there may be other speeds, since the speed
2500 0.3 ± 0.0 0.3 ± 0.0 0.3 ± 0.0
depends in particular on the controller hardware
and the distribution of the data in the controller. 5000 0.5 ± 0.0 0.5 ± 0.0 0.6 ± 0.0
10000 1.0 ± 0.0 1.0 ± 0.0 1.1 ± 0.1
8.1 S7 TCP in combination with a Win32 PC
Average update time in seconds
Test parameters:
Data type = REAL
PC operating sys- Windows® XP Professional (SP2) Active variables for writing
tem:
Active variables 1 10 50
Driver: S7 TCP (S7TCP.dll), for reading
version 10.1.0.7
10 < 0.1 < 0.1 –
Controller: VIPA Speed7 - DataBlock area
50 < 0.1 < 0.1 < 0.1
100 < 0.1 < 0.1 < 0.1
Average update time in seconds
Data type = WORD 500 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.0
Active variables for writing 1000 0.2 ± 0.0 0.2 ± 0.0 0.2 ± 0.0
Active variables 1 10 50 2500 0.5 ± 0.0 0.5 ± 0.0 0.5 ± 0.0
for reading 5000 1.0 ± 0.0 1.0 ± 0.0 1.1 ± 0.0
10 < 0.1 < 0.1 – 10000 2.1 ± 0.0 2.1 ± 0.0 2.1 ± 0.0
50 < 0.1 < 0.1 < 0.1
100 < 0.1 < 0.1 < 0.1

8150_en_06 PHOENIX CONTACT 12 / 24

 VISU+ 2 ...

8.2 Allen-Bradley (EtherNet/IP) in combination with

Average update time in seconds a Win32 PC
Data type = BIT Test parameters:
Active variables for writing
PC operating sys- Windows® XP Professional (SP2)
Active variables 1 10 50 tem:
for reading
Driver: Allen-Bradley EtherNet/IP driver
10 < 0.1 < 0.1 – (EthernetIP.dll), version 10.1.0.1
50 < 0.1 < 0.1 < 0.1 Controller: Allen-Bradley SLC5/05 CPU 1747-
100 < 0.1 < 0.1 < 0.1 L551 OS 501
500 < 0.1 < 0.1 < 0.1 This test has not been carried out with bit variables, since
1000 < 0.1 < 0.1 < 0.1 the driver always processes a bit as a single task.
2500 < 0.1 < 0.1 < 0.1
5000 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.1 Average update time in seconds
10000 0.2 ± 0.0 0.2 ± 0.0 0.2 ± 0.0 Data type = WORD
Active variables for writing
Active variables 1 10 50
for reading
10 < 0.1 < 0.1 –
50 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.0
100 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.0
500 0.3 ± 0.1 0.3 ± 0.1 0.3 ± 0.1
1000 0.6 ± 0.1 0.6 ± 0.1 0.6 ± 0.1
2500 1.3 ± 0.1 1.3 ± 0.0 1.3 ± 0.1

Average update time in seconds

Data type = FLOAT
Active variables for writing
Active variables 1 10 50
for reading
10 0.1 ± 0.0 0.1 ± 0.0 –
50 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.0
100 0.1 ± 0.0 0.1 ± 0.0 0.1 ± 0.0
500 0.2 ± 0.0 0.3 ± 0.0 0.3 ± 0.0
1000 0.4 ± 0.0 0.4 ± 0.0 0.5 ± 0.0
2500 1.0 ± 0.0 1.1 ± 0.0 1.1 ± 0.0

8150_en_06 PHOENIX CONTACT 13 / 24

 VISU+ 2 ...

9 Limits for VISU+ 2 projects under WinCE

WinCE devices do not support some VISU+ 2 functions.
If possible, start to develop a VISU+ 2 project for
NOTE: Damage an HMI device with a new project in VISU+ 2 that
is identified exclusively with the WinCE target
The flash memory of the touch panels is not suit-
platform. This avoids incompatibilities between
able for write-intensive operations (e.g., logging).
Win32 and WinCE platforms. And you can set the
Therefore, use SD cards for tasks that require a
constraints of the device for your hardware accu-
high number of write cycles.
rately.
– Please note the restrictions for WinCE proj-
ects listed below and adapt your project to
the capabilities of the HMI device hardware. In VISU+ 2, several target platforms can be se-
VISU+ 2 indicates functions that cannot be lected simultaneously. In this case, the strongest
used or used in a restricted way only when performing platform is taken for the constraints of
WinCE is specified as the only operating sys- the target platform.
tem in the project.
– The WinCE HMI devices have different hard-
ware equipment. This equipment influences
the functions that can be used with VISU+ 2.
– Please note that the same editor is used for
all VISU+ 2 projects on all operating systems.
This is a great advantage for the user, since
the user can later easily exchange projects
between PCs and HMI devices.
In this context, please note that different
functions are supported depending on the
configured device.
Before you start the configuration, please an-
alyze which demands you have on your proj-
ects and which hardware and which runtime
system support these requirements properly.
Should you have any questions, please con-
tact your nearest Phoenix Contact represen-
tative.

Limits for VISU+ 2 projects (WinCE/WEC7)

General
Maximum number of pages Phoenix Contact sets a recommended limit in the constraints
file, depending on the hardware (e.g, 16 for BTP 2XXXX and
64 for TP 3XXXX).
Real-time database (variables database (tags))
Maximum number of variables (tags) 4096 I/O bytes
Phoenix Contact sets a recommended limit in the constraints
file, depending on the hardware (e.g, 256 bytes for BTP
2xxxx and 4096 bytes for TP 3xxxx).
Size of the structure variables Total size: 32767 bytes, maximum

8150_en_06 PHOENIX CONTACT 14 / 24

 VISU+ 2 ...

Limits for VISU+ 2 projects (WinCE/WEC7)

Variable names – Must not contain special characters
– Must not start with a special character or a digit
– May be up to 64 characters long
– “k” and “K” as an initial is reserved for IL logic (instruction
list: “Constant”)
Number of variables in the audit trail 64
Maximum number of variables linked via ODBC 64
Objects in process images
Maximum number of objects in a process image Phoenix Contact sets a recommended limit in the constraints
file, depending on the hardware.
Expressions Local variables may not be used in the expression for objects
that use VBA (Visual Basic for Applications) expressions.
Gradual filling The “pipe” object does not support gradual filling.
Rotating It is not possible to rotate objects.
Polygon filling Polygons (e.g., tank sections) cannot be filled in the correct
form but are filled in a rectangular form.
Network functions
Maximum number of network variables 512
Maximum number of network connections for each display 8
window
Alarm management

Acquisition of large data volumes (alarm system with data storage higher than 1 Mbyte) can have a negative
effect on the runtime behavior/start behavior of the touch panel.

Maximum number of alarms 4096 alarm threshold values for each project and a maxi-
mum of 16 alarm threshold values thereof with an internal
script
Maximum number of alarm priorities 99
Maximum number of characters for each alarm text string 256
Maximum number of alarm threshold values for each 16
alarm
Maximum number of observer clients that are connected 16
to an alarm server
Alarm dispatcher
Maximum number of possible alarm indications in the proj- 4096
ect
Maximum number of users (default) for each alarm indica- 16
tion
Maximum e-mail file size 256 kbytes
Maximum number of e-mail files 10
Data loggers

Acquisition of large data volumes (data acquisition with data storage higher than 1 Mbyte) can have a negative
effect on the runtime behavior/start behavior of the touch panel.

Maximum number of data loggers for each project

Windows Embedded Compact 7 16
Maximum number of columns for each data logger 128 (90 with IMDB, maximum)

8150_en_06 PHOENIX CONTACT 15 / 24

 VISU+ 2 ...

Limits for VISU+ 2 projects (WinCE/WEC7)

Archive life cycle of the data logger (maximum number of 365
days)

The maximum service life of the data logger archive depends on the selected maximum database capacity
(e.g., SQL Server CE: 2 Gbytes, maximum).
Maximum string size of historical data 256 bytes
Maximum sampling rate 1s
Recipes
Maximum number of recipes for each project 16
Maximum number of columns for each recipe 128 (90 with IMDB, maximum)
Trends and data analysis

Acquisition of large data volumes (trends with data storage higher than 1 Mbyte) can have a negative effect
on the runtime behavior/start behavior of the touch panel.

Maximum number of pens for each trend 16

Maximum number of displayable sampling points/nodes 500
for each trend
Maximum sampling rate 1s
Events
Maximum number of event objects/events for each project 64
Schedulers
Maximum number of schedulers for each project (maxi- 64
mum number of event objects/events for each project)
Scalable objects
Maximum number of scalable objects 32
Language selection
Maximum number of strings for each language 8192
Maximum number of languages (columns) 32
Maximum number of characters for each string 256
Memory and ODBC and IMDB links
ODBC ODBC links are not supported. They will be converted auto-
matically in ADOCE links.
IMDB 90 columns, maximum
Phoenix Contact sets a recommended limit in the constraints
file, depending on the hardware (e.g., 4 Mbytes for TPs of the
3xxx series).
DSN name Some databases such as SQL Server do not support spaces
in the DSN name. Therefore, please do not use spaces in the
project names.
Column names Some databases such as SQL Server CE do not support
spaces in the column names of the databases. Therefore,
please do not use spaces in column names of the memories
or protocols such as data loggers, recipes, etc.
Recording frequencies The recording frequency depends on several factors. The
frequency should not be less than 1 second.
User management (users and passwords)
Maximum number of users 1024

8150_en_06 PHOENIX CONTACT 16 / 24

 VISU+ 2 ...

Limits for VISU+ 2 projects (WinCE/WEC7)

Maximum number of user groups 64
VBA scripts and IL logic (instruction list)
Maximum number of scripts 64, 4 of which can be executed simultaneously (multi-
threads)
Maximum number of code lines for IL logic (instruction list) 2048
Web Clients (WinCE 6.0 or later)

Parallel access via the HTML5 browser and the Java Applet can affect the runtime performance.

Maximum number of Web Client stations on a VISU+ 2 2

server

OPC client

– OPC client and server must run on the same device. They cannot be connected via a network.
– DCOM technology is not supported under WinCE.

Redundancy
Redundancy mechanisms Under WinCE, the redundancy mechanisms of a project are
not supported in VISU+ 2.
Reporting
Crystal reports The crystal reports engine is not supported under WinCE.
Integrated graphical reporting Under WinCE, the graphical reporting integrated in VISU+ 2
is not supported.
Textual reporting Textual reporting and report printing are possible under
WinCE.
Embedded report Embedded reporting is available for Win32/64 systems as
well as for WinCE systems.
Direct drivers
Maximum number of direct drivers that can be used simul- 2 (plus shared memory I/O driver)
taneously under WinCE

8150_en_06 PHOENIX CONTACT 17 / 24

 VISU+ 2 ...

9.1 Details on the restrictions of VISU+ 2 under porting are also available under WinCE.
WinCE Since the report engine is not available under WinCE, there
are commands missing in the WinCE device that are rele-
Supported graphical functions: vant for the creation of the statistics report about alarms.
Function WinCE Win32, Win64 The alarm notification functions are managed by the “Alarm
Coloring Yes Yes Dispatcher” component. Under WinCE, only the alarm noti-
Linear filling Yes Yes fications via SMS and e-mail are available as shown in the
following table:
Polygonal filling No Yes
Rotations No Yes
Function WinCE Win32, Win64
Dynamic x, y movement Yes Yes
SMS via GSM modem Yes Yes
Graphical objects Yes Yes
SMS via SMPP No Yes
Templates library Yes Yes
Voice Yes
Button/Dundas gauge with No
No Yes (voice syntheses)
3D
Fax No Yes
Trend Yes Yes
E-mail via TAPI No Yes
Diagrams No Yes
E-mail via MAPI Yes Yes
Database viewer Yes Yes
E-mail via SMTP No Yes
Embedded process images Yes Yes
Alarm statistics No Yes
Further graphical restrictions
Graphical restrictions
Dotted lines Dotted lines (only solid and dashed)
that are thicker than 1 are blurred
under WinCE.
Font “Escapement” font is not supported.
Image status The image status is not supported.
EditPenProperties EditPenProperties support is limited.
Trend setting The files are not compatible between
the desktop and WinCE device.
Metafile images External metafile images (WMF,
EMF) are not supported.
Opening the pro- Opening a process image as a frame
cess image as a (“Open Frame (Multi-Monitor)” com-
frame mand) is not fully supported under
WinCE. The process image is
opened, but it is not in the foreground;
if you click the area outside the pro-
cess image opened as a frame, it is
put to the background and is no longer
visible.
Scrollbars Scrollbars are not supported under
WinCE. The scrollbars of a process
image are not displayed in a project
that is executed in a WinCE environ-
ment.

Restrictions of the alarms under WinCE

Restrictions are relevant for notification management and
statistics examination. Textual reporting and embedded re-

8150_en_06 PHOENIX CONTACT 18 / 24

 VISU+ 2 ...

Restrictions with data loggings/recipes and reports in Restrictions of the drivers under WinCE
WinCE
The communication drivers for WinCE have been compiled
WinCE projects normally store the log files using the IMDB specifically for this operating system. Not all drivers of
technology (InMemory DB) that can be executed more eas- VISU+ 2 are also available on the WinCE HMI devices.
ily and in a more powerful way than ODBC/ADOCE thanks Supported drivers:
to the XML text format used. With this technology, the actual
database is completely in the RAM memory of the system. Drivers WinCE Win32, Win64
Therefore, the IMDB technology should be used preferen- Modem Telecontrol (TAPI) No Yes
tially for applications with a limited data volume. VBA interface Yes Yes
If you have chosen ODBC for storing log files in develop- Multidriver 2, max. Yes
ment mode (desktop), it will be replaced by ADOCE on the
WinCE device, because WinCE does not support ODBC. In Restrictions of OPC under WinCE
this way, even WinCE devices can store historical data lo-
cally in an open database. More than two OPC servers can be connected,
depending on the VISU+ runtime version. If the
For WinCE devices from Phoenix Contact, “MS SQL Server
controller in the network fails, reconnection times
Compact Edition for CE” is taken as a database manage-
can be longer.
ment system (DBMS) when ADOCE is used.
VISU+ 2 for WinCE supports OPC technology as a client,
Please always make sure that the WinCE device but not as a server. “OPC client XML” technology is not sup-
provides enough memory capacity to store the ported either.
historical data defined in the project.
Supported OPC functions:
Supported functions: Function WinCE Win32, Win64
Function WinCE Win32, Win64 OPC DA client Yes Yes
Data loggers Yes Yes OPC DA server No Yes
Recipes Yes Yes OPC XML DA client No Yes
Embedded reporting Yes Yes OPC XML DA server No Yes
Crystal reports machine No Yes OPC UA client Yes Yes

Restrictions for WinWrap Basic (in WinCE) Restrictions of the Web Clients under WinCE
VISU+ 2 for WinCE supports VBA (Visual Basic for Applica-
Parallel access via the HTML5 browser and the
tions). The VBA program code for the WinCE device is iden-
Java Applet can affect the runtime performance.
tical with the one for the desktop PC.
It cannot be guaranteed that all functions, features, meth- VISU+ 2 for WinCE supports Web Client technology. The
ods, and events in VBA available on the desktop are fully number of simultaneous Web Client connections is limited
supported, since correct execution of each single instruction to two in order to save resources on WinCE devices.
has not been fully tested. Using VBA on a WinCE device
uses memory and computing power. Therefore, use VBA
sparingly depending on the device's computing power.
Supported functions:
Function WinCE Win32, Win64
_CurDir No Yes
_Declare No Yes

The alarm dispatcher is not supported by the

basic script code management. Thus, you cannot
use the SMS and e-mail functions, etc. in the
basic script code.

8150_en_06 PHOENIX CONTACT 19 / 24

 VISU+ 2 ...

9.2 Notes on creating VISU+ 2 projects for WinCE Function

HMIs
Sending a voice message Not available
Please observe the restrictions of the operating system Sending a fax Not available
when implementing a project for WinCE. While creating a Sending an e-mail Not available
VISU+ 2 project under WinCE, please take into consider-
Recording historic data Representation only
ation that the memory space of devices with WinCE is often
limited. Alarm statistics (report) Not available

For further information on memory space on de- 10.3 Data logging/recipe/report - restrictions of the
vices with WinCE, please refer to the Web Client
AH EN VISU+ BEST PRACTICE application Data logging is performed on the server. The Web Client
note. only permits access for visualization of historical data.

10.4 WinWrap Basic restrictions of the Web Client

10 Web Client restrictions
The Web Client permits execution of a VBA script on the
Some functions of VISU+ 2 cannot be used with the Web server during the boot process. For example, the Web Client
Client. does not support representation of VBA script dialog boxes.
The user interface (project UI) is also loaded for those ob-
10.1 Graphical restrictions of the Web Client jects and process images that are represented in a Web Cli-
ent session. This makes it possible that some commands
Graphical restrictions of the Web Client such as OpenSynoptic, OpenSynopticEx, OpenSynop-
ticParameter, OpenSynopticModal, or ExecuteCommand
Value editing As a local edit box only
can be managed by the Web Client. Nevertheless, it is im-
Touch screen com- Not available portant to consider that some of these commands interact
mands with the UI instance of the server. In order not to block these
Menu Not available commands, the project planner may not call up certain func-
Shortcuts Not available tions in Web Client sessions. Please also observe the UM
Modal window Not available EN VISU+ WEB CLIENT GUIDE user manual. The docu-
frame window ment can be downloaded at phoenixcontact.net/products.
These commands only make sense if they are used within a
ActiveX in process Not available
process image since there is no connection between a
images
script executed as a resource and a Web Client session.
Modal window/ The Web Client does not support
frame modal window or frame window 10.5 Web Client IL logic restrictions
management on the client. A window
opened on the server as a modal The IL logic (instruction list) is started on the server only.
window (or frame window) will be
displayed as a full screen on the 10.6 Web Client password restrictions
Web Client. Passwords are also used on the Web Client. The system
Script dialog boxes Not supported by Web Client. also requires access passwords on the Web Client based
Numeric pad for Not supported by Web Client. on the settings made by the project developer on the server.
touch screens The server registers every access by the users and the con-
nected Web Client stations. The Web Client does not sup-
10.2 Web Client alarm restrictions port the creation of new user passwords.
The Web Client permits visualization of alarms and actions
that are executed on it. The restrictions only concern the no-
tification and management of the statistics analysis, since
the Web Client cannot process anything locally. These ac-
tions remain tasks of the server.

Function
Sending an SMS Not available

8150_en_06 PHOENIX CONTACT 20 / 24

 VISU+ 2 ...

11 Overview of functions
The following functions are available in the VISU+ 2 versions:

Function BTP 2xxxx TP 3xxxx BL2 BPC / PPC xxxx Industrial PC

TP 6xxxx VL2 BPC / PPC xxxx
DL PPC xxxx
Software option Functionality
depends on the

HMI RT 1K (S30)

HMI RT 2K (S31)

HMI RT 4K (S32)
purchased license

I/O bytes (tags)1 256 1024 1024 2048 4096 64 to unlimited

Process images1 16, max. 64, max. 1024 4096 8192 Unlimited
Graphics libraries Yes Yes Yes Yes
Templates Yes Yes Yes Yes
Alarms 1024, max. Yes 1024 4096 8192 Unlimited
Shortcuts and menus Not available Not available Yes Yes
Touch screen support Yes Yes Yes Yes
Event logging Yes Yes Yes Yes
Language selection Yes Yes Yes Yes
IL logic (SoftLogic) Yes Yes Yes Yes
VBA multithreading1 4, max. 4, max. Yes Yes
ActiveX OCX Not available Nicht verfügbar Yes Yes
Debugger online/remote Yes Yes Yes Yes
IP camera Yes Yes Yes Yes
Dundas gauges Not available Not available Not available Yes
Speech recognition Not available Not available Not available Yes
Dynamic trends Yes Yes Yes Yes
Historical trends Yes (TXT/XML only) Yes Yes Yes
Recipes Yes Yes Yes Yes
OPC DA client22 Yes Yes Yes Yes
OPC XML DA client Not available Yes Not available Yes
OPC UA client Yes (one server) Yes (two servers) Yes (two servers) Yes
Modem driver connection Not available Not available Not available Yes
Modem RAS service Not available Not available Not available Yes
VBA driver interface Not available Not available Not available Yes
3D evaluation Not available Not available Yes Yes
Networking Yes Yes Yes Yes
Data loggers 1, max. Yes Yes Yes
(TXT/XML) (TXT/XML/ADO CE)
Reports Text reports Text reports Text reports Yes
Direct drivers 2, max. 2, max. 2, max., others as an 2 or others as an
option option
SMS/voice/fax/e-mail Not available E-mail only Optional Optional

8150_en_06 PHOENIX CONTACT 21 / 24

 VISU+ 2 ...

Function BTP 2xxxx TP 3xxxx BL2 BPC / PPC xxxx Industrial PC

TP 6xxxx VL2 BPC / PPC xxxx
DL PPC xxxx
Software option Functionality
depends on the

HMI RT 1K (S30)

HMI RT 2K (S31)

HMI RT 4K (S32)
purchased license

Alarm statistics Not available Not available Not available Optional

OPC DA server Not available Yes Not available Optional
OPC XML DA server Not available Not available Not available Optional
Redundancy Not available Not available Not available Optional
FDA CFR 21 Part 11 Yes Yes Yes Yes
Web client 1 web client 2 web clients 2 web clients Optional
1
Restricted by the engineering environment
2
The WinCE device must have an AX OPC Server for this function

11.1 Explanations for the functions

I/O bytes (tags) Shortcuts and menus

Licenses are limited to the specified number of I/O bytes. You can configure a menu bar (e.g., Open file). In addition,
Not to be confused with variable tags. Active communica- shortcuts or function keys can be pre-assigned (e.g., F2 ->
tion with the controller is measured. Open page) to execute an action.

Process images Touch screen support

Process images are visualization pages that are configured In the visualization, you can respond to touch panel opera-
in VISU+. The number of pages and of the graphical objects tions (mouse or finger touch) by a press or release action.
may be limited. VISU+ also supports operating gestures for page changes
or navigation by swiping or zooming the graphical user inter-
Graphics libraries face (e.g., on the trend).
VISU+ has a pre-installed collection of symbols. The sym-
Event logging
bols can be extended specifically for the customer. Various
graphics formats (wmf, png, jpg, etc.) are supported. Events can be easily configured and connected to variables.
You can configure an action in VISU+ (e.g., set a value, start
Templates a program, etc.) for cases where a variable value changes.
Templates for BTP 2XXXX/TP 3XXXX are stored in VISU+
Language selection
for easy project creation. A template is also available for in-
dustrial PCs with VISU+ Express or for every PC in general. The visualization can be represented in many languages.
The templates automatically set up the project to match the For this purpose, a translated text is stored for each text ob-
resolution of the target device. Only communication drivers ject. All languages are clearly stored in a table format. The
compatible with the selected device are provided. languages can be exported or imported.

Alarms IL logic
VISU+ has a signaling system with various alarms, degrees The IL logic is an application language similar to a PLC. To
of severity, and trigger options. The number of alarms may manipulate variables, the IL logic enables programs in the
differ depending on the runtime. visualization to run cyclically.

8150_en_06 PHOENIX CONTACT 22 / 24

 VISU+ 2 ...

VBA multithreading Modem RAS service

In parallel, scripts can be processed in their own tasks. An RAS connection is a function of the operating system.
This function can be used to connect a server and a client
ActiveX OCX between two stations using a modem connection. The TCP/
ActiveX OCX are independent programs that are supported IP protocol can be used to exchange data between the
and executed by the operating system. It is not recom- server and the client, provided that the connection is actu-
mended to use this technology. ally working. An RAS connection can be established via
“Control Panel -> Network Connections”.
Debugger online/remote
VBA driver interface
VISU+ is provided with WinWrap Basic. VB.NET is available
depending on the platform. You can execute the created Access to communication driver functions using a script
basic source code and view it on the debugger. (WinWrap Basic or VB.NET).

IP camera Networking

VISU+ supports typical Ethernet webcams that generate im- Via Ethernet, variable values can easily be transported from
ages individually and time-controlled. one operator panel to another networked operator panel
(e.g., can also be used in the signaling system).
Dundas gauges
Data loggers
Dundas gauges comprise a graphics collection of speed-
ometer and indication elements. Time-controlled recording of variable values and different
storage options (database, file, etc.).
Dynamic trends
Reports
Trends that acquire and display time-controlled variable val-
ues. Reports can be used to graphically display measured val-
ues.
Historical trends
Direct drivers
Indicate the history of a recorded trend development. A filter
for searching the date or time is available. VISU+ has many communication drivers of renowned man-
ufacturers. Normally, VISU+ can read in a symbol file so that
Recipes the process variables can be immediately used in VISU+.

Variable values can be stored and loaded on the operator SMS/voice/fax/e-mail

panel.
It is possible to send an SMS or e-mail, e.g., from the signal-
OPC clients ing system.

The following OPC clients are supported: Alarm statistics

– OPC UA client
Alarm statistics provide a clear overview of the messages.
– OPC XML DA client
Redundancy
OPC server
You can create a redundant system. One operator panel is
The following OPC servers are available. They require a li- used on two identical controllers, for example. If one control-
cense: ler fails, VISU+ automatically switches to the second con-
– OPC DA server troller.
– OPC XML DA server
– OPC UA server Web Client
VISU+ has various options to access the operator panel via
Modem driver connection remote maintenance.
It is possible to forward a driver from “A” to “B” via a modem.

8150_en_06 PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany 23 / 24
phoenixcontact.com
 VISU+ 2 ...

– Java Applet (own program that can be started)

– HMTL5 browser (standard PC browser)
– Mobile clients (Android or iPhone)
Please observe that the number of sessions that can be run
in parallel is limited. The number depends on the runtime.

8150_en_06 PHOENIX CONTACT 24 / 24