User Manual
Table Of Contents
- 1 Cyber security disclaimer
- 2 Preconditions of this document
- 3 System overview
- 4 Desigo workflow, tools and programming
- 4.1 Coverage of the technical process
- 4.2 Coverage of the system
- 4.3 Main tasks
- 4.4 Tools for different roles
- 4.5 Working with libraries
- 4.6 Working in parallel and subcontracting
- 4.7 Workflow for primary systems
- 4.8 Workflow for room automation classic
- 4.9 Workflow for Desigo room automation
- 4.10 Desigo Configuration Module (DCM)
- 4.11 Desigo Xworks Plus (XWP)
- 4.12 Desigo Automation Building Tool (ABT)
- 4.13 Programming in D-MAP
- 5 Control concept
- 6 Technical view
- 7 Global objects and functions
- 8 Events and COV reporting
- 9 Alarm management
- 9.1 Alarm sources
- 9.2 Alarm example
- 9.3 Effects of BACnet properties on alarm response
- 9.4 Alarm response of the function blocks
- 9.5 Alarm functions
- 9.6 Alarm management by notification class
- 9.7 Alarm routing over the network
- 9.8 Alarm queuing
- 9.9 Common alarms
- 9.10 Alarm suppression
- 9.11 Alarm message texts
- 10 Calendars and schedulers
- 11 Trending
- 12 Reports
- 13 Data storage
- 14 Network architecture
- 15 Remote access
- 16 Management platform
- 17 Desigo Control Point
- 18 Automation stations
- 19 Logical I/O blocks
- 20 Room automation
- 21 Desigo Open
- 22 System configuration
- 22.1 Technical limits and limit values
- 22.2 Maximum number of elements in a network area
- 22.3 Desigo room automation system function group limits
- 22.4 Devices
- 22.4.1 PXC..D automation stations / system controllers
- 22.4.2 LonWorks system controllers
- 22.4.3 Automation stations with LonWorks integration
- 22.4.4 PX Open integration (PXC001.D/-E.D)
- 22.4.5 PX Open integration (PXC001.D/-E.D + PXA40-RS1)
- 22.4.6 PX Open integration (PXC001.D/-E.D + PXA40-RS2)
- 22.4.7 PX KNX integration (PXC001.D/-E.D)
- 22.4.8 TX Open integration (TXI1/2/2-S.OPEN)
- 22.4.9 Number of data points on Desigo room automation stations
- 22.4.10 Number of data points for PXC3
- 22.4.11 Number of data points for DXR1
- 22.4.12 Number of data points for DXR2
- 22.4.13 PXM20 operator unit
- 22.4.14 PXM10 operator unit
- 22.4.15 Desigo Control Point
- 22.4.16 PXG3.L and PXG3.M BACnet routers
- 22.4.17 SX OPC
- 22.4.18 Desigo CC
- 22.4.19 Desigo Insight
- 22.4.20 Desigo Xworks Plus (XWP)
- 22.4.21 Desigo Automation Building Tool (ABT)
- 22.5 Applications
- 23 Compatibility
- 23.1 Desigo version compatibility definition
- 23.2 Desigo system compatibility basics
- 23.2.1 Compatibility with BACnet standard
- 23.2.2 Compatibility with operating systems
- 23.2.3 Compatibility with SQL servers
- 23.2.4 Compatibility with Microsoft Office
- 23.2.5 Compatibility with web browsers
- 23.2.6 Compatibility with ABT Go
- 23.2.7 Compatibility with VMware (virtual infrastructure)
- 23.2.8 Compatibility of software/libraries on the same PC
- 23.2.9 Hardware and firmware compatibility
- 23.2.10 Backward compatibility
- 23.2.11 Engineering compatibility
- 23.2.12 Compatibility with Desigo Configuration Module (DCM)
- 23.2.13 Compatibility with Desigo PX / Desigo room automation
- 23.2.14 Compatibility with Desigo RX tool
- 23.2.15 Compatibility with TX-I/O
- 23.2.16 Compatibility with TX Open
- 23.3 Desigo Control Point
- 23.4 Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3
- 23.5 Siemens WEoF clients
- 23.6 Migration compatibility
- 23.7 Hardware requirements of Desigo software products
- 24 Desigo PXC4 and PXC5
- 25 Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5
Logical I/O blocks
Input blocks
19
256 | 351 CM110664en_07
Pulse converter (pulse counter)
The pulse converter object cumulates pulses for a meter. The Pulse converter object is used where meter
values already manipulate in a meter object or where changes of values are required to further process
control programs. Applications include: Establishing 24-hour/7-day/monthly meters, transmission by the
minute of meter values to peak load programs, etc. Precision and round off error based on real arithmetic is
possible.
Specific properties
The counter value is scaled as a REAL number directly in the object using the scaling factor. COV forming
the Present_Value can be value or time-related and a timestamp with the logged time is always provided
with the Present_Value. Reduction of Present_Value by a value (subtraction) is supported as a standard.
You can set it to a pre-defined value using a trigger function (proprietary expansion).
The Pulse Converter object can be used in two different manners: Counting or metering. The type of
application is parameterized using the FnctMod parameter.
The referenced object, e.g., an external device provides the pulse value:
● Present_Value for the pulse converter object represent the pulse count of the referenced object: The
difference to the last read value is added for each record.
● Present_Value can be set via the system.
● After start-up, the pulse converter object encompasses the last stored counter value:
● After a change in counter, the pulse converter object encompasses a false counter value.
● Typical application: On-board I/O with pulse logging.
The referenced object, e.g., an external device provides the absolute pulse value:
● Present_Value from the pulse converter object represents the absolute counter value of the referenced
object.
● Under no circumstance may the Present_Value be set via the system.
● After start-up or a change in counter, the pulse converter object after includes the correct counter
value.
● Typical applications:
– Access to an accumulator or pulse converter object is another BACnet device
– I/O Open module or M-bus with counter value integration
– Integration of a device via LON
● Incorrect applications: I/O module with pulse recording
Accumulator object (counter value)
The accumulator object can map counter states unchanged and free of errors due to rounding off or add
the counter pulse without loss and scale the same. The accumulator object is suitable to displaying meter
values that justify monetary performance. For this type of counter values, manipulations such as monthly
values, etc., must never be made directly in the meter object.
The addition of counter pulses and scaling without loss is accomplished using whole-number operations
with residual value processing. The conversion of physical pulses can be adapted using a presale
parameter. The resulting Present_Value is a scalable variable.
Present_Value depends on the function mode to synchronized adjustable to any value using a physical
meter with the last value prior to setting saved with a date/time stamp.