JUNG Visu Pro – the solution for the smart building
The JUNG Visu Pro Server with pre-installed Visu Pro software is ideal for applications in demanding smart buildings. Connected with the KNX installation and the local network, it makes comprehensive individual adaptations of the complete system possible.
Server specification
With its compact design, the Visu Pro Server is conceived for mounting on a DIN rail (included adapter required). However, you can also use it as a desktop device. It is completely silent in use without any active fans as the cooling is passive. The power consumption even under full load is minimal (12 W in operation, maximum 6 W on standby). The built-in processors and memory enable a smooth operation, even with more demanding applications.
Connections
-
![USB 3.0]()
USB 3.0 -
![DHCP]()
DHCP -
![Fixed IP address]()
Fixed IP address -
![HDMI connection]()
HDMI connection -
![12 VDC]()
12 VDC
JUNG Visu Pro software
From the planner version for pre-planning to the full version for hotels: JUNG offers the right Visu Pro software for a given case for all applications, even without hardware. As soon as the project in the home area becomes more comprehensive and even more individual, the JUNG Visu Pro Server is suitable.
Secure, convenient and sustainable
Data security with KNX Secure
Your data are doubly secure: KNX Data Secure encrypts the KNX telegrams in the KNX bus, KNX IP Secure secures the exchange over the IP network.
Connection to the Internet of Things
Update 4.11.0.3 | Direct MQTT connection
The update extends the connection of networked building technology. The MQTT connection enables the direct integration and control of MQTT-capable devices from different manufacturers. This means more flexibility in project design and extended options for the visualisation of complex applications.
New functions:
- New MQTT option in the process model for polling and controlling MQTT-compatible products
- Extended options for the JVP button
- Hiding Visu elements via data points
- General improvements to the Modbus editor
Update V 4.10 | Implementation of HTML calendar and Modbus TCP
With the update, it is possible to set up an HTML annual calendar that executes scenes depending on the start or end of the calendar event. The Modbus process connection can use existing device databases for configuration.
Task of an HTML calendar in a KNX installation
An HTML calendar enables the time-controlled and automated control of functions in a KNX installation (e.g. lighting, blinds, heating). It can be conveniently configured via a web interface and can trigger recurring and one-off events - even taking public holidays and special events into account.
Private use:
1. control of a switched socket in recurring time periods
- The HTML calendar automatically switches the socket for the Christmas tree or pool pump on and off according to a defined schedule - without the need for a manual timer switch. → Increase convenience, reduce standby loads
2. public holidays override the weekly timer
- The shutters stay down on public holidays, even if they would otherwise go up early on working days. → Gain in comfort
3. different heating profiles for "home office" and "company"
- During a "home office" appointment, the office is heated; during a "company" appointment, the heating in the office remains off. → Energy savings, increased comfort
4. presence simulation through "holiday - travel"
- During a trip, the control system simulates presence by randomly moving the blinds and switching the lighting. - A simple "holiday" appointment only prevents the shutters on the ground floor from being raised in the morning. → Energy savings, increased comfort
5. integration of the local waste calendar
- The HTML calendar displays the collection dates for waste bins on a Smart Panel. → Added convenience
Commercial use:
1. switching of power strips and TV only when the room is occupied
- Sockets and devices (e.g. televisions) are only switched on when a meeting room is actually booked. → Reduce standby consumption, energy efficiency
2. air conditioning only when the room is occupied
- The heating or air conditioning is only activated when the room is actually in use. → Energy efficiency
3. control of outdoor lighting over the course of a year
- The outdoor lighting is automatically switched according to a yearly schedule - public holidays and company closures are taken into account. → Energy efficiency
4. prioritisation for overlapping events
- Air conditioning is suspended on public holidays, even if a regular weekly programme is active. → Flexibility, energy efficiency
5. additional lighting in gyms on match days
- The lighting is fully enabled on match days, but reduced to standard lighting during normal school operation. → Energy saving, increased comfort
6. switching off the kitchenette and coffee machine after working hours
- Devices in the kitchenette are automatically switched off after working hours, for example to prevent hobs from being accidentally left on. → Energy saving
7. switch on ambient lighting after opening hours
- Ambient lighting is activated after closing time to create an attractive appearance. → Added convenience, energy efficiency
Modbus in the Visu Pro Server (JVP)
The Visu Pro Server (JVP) now supports the Modbus TCP protocol. Via Modbus TCP, the JVP:
- Read values from Modbus devices (e.g. electricity meters, inverters, heat pumps)
- Write values to Modbus devices (e.g. change the operating mode of air conditioning systems)
- Integrate Modbus data points into the KNX installation and indicate them in the visualisation
Does the device only support serial communication via Modbus "RTU"?
If a participant communicates on the basis of Modbus RTU (via RS485), a Modbus RTU to TCP converter is required.
Solutions:
1. manufacturer-specific converter
- Some manufacturers offer their own RTU to TCP converters that are optimised for their devices.
2. general Modbus RTU to TCP converter
A general RTU-TCP converter can be used - however, the following parameters must be observed:
- Baud rate → Communication speed (e.g. 9600, 19200, 38400 baud)
- Parity → None, even or odd
- Stop bits → 1 or 2
- Data format → e.g. 8N1 (8 data bits, no parity, 1 stop bit)
- Multiple devices on one Modbus RTU converter - If multiple Modbus RTU devices are connected to one converter, each device must have a unique Modbus ID and all Modbus RTU properties, such as baud rate or parity, must match
Where can I find these Modbus properties and registers?
In order to read or write the correct values from a Modbus device, precise information from the manufacturer is usually required.
The manufacturer usually provides a Modbus document (register list or data point list) containing the following information:
- Register ID → Which ID can be used to read or write which information
- Data type → What type the data is (e.g. integer, float)
- Access right → Whether the data point can only be read (Read) or also written (Write)
- Addressing → Whether the start digit of the register begins at 0 or 1
- Data sequence → Whether the data is transferred in big endian (from front to back) or little endian (from back to front) format
Thanks to the constantly growing JUNG Modbus database, the search for standard manufacturer information is no longer necessary. This database is installed locally in every JUNG Visu Pro update. Missing manufacturers can be reported to JUNG under JUNG Modbus Github.
Use cases for Modbus in a KNX installation
Quick start guides
Set up functions and use directly: the Quick Start Guides use short and clear step-by-step instructions to show how you can exhaust the versatile possibilities of the JUNG Visu Pro Server.
Discover the Live Services from JUNG
JUNG Newsletter
Product news, architecture references and smart home trends: With our JUNG newsletters you are always well informed when it comes to trends and news.