Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:sw:01-mervis:communication-mervis-jablotron100-hidden [2021/05/03 09:32]
avsetula
en:sw:01-mervis:communication-mervis-jablotron100-hidden [2021/08/05 13:52] (current)
avsetula
Line 20: Line 20:
 <​html><​span class="​kbBlue-H4alt">​Prerequisites:</​span></​html>​ <​html><​span class="​kbBlue-H4alt">​Prerequisites:</​span></​html>​
   * Unipi controller running [[en:​files:​software:​os-images:​00-start|Mervis OS v2.3.0]] or higher   * Unipi controller running [[en:​files:​software:​os-images:​00-start|Mervis OS v2.3.0]] or higher
-  * [[https://​www.unipi.technology/​en/​accessories-c4|24V DC power supply]]+  * [[https://​www.unipi.technology/​en/​accessories-c4|24 V⎓ power supply]]
   * local network connectivity (any switch or router)   * local network connectivity (any switch or router)
   * Jablotron 100(+) ESS control panel   * Jablotron 100(+) ESS control panel
   * Jablotron JA-121T, RS-485 module   * Jablotron JA-121T, RS-485 module
-  * [[https://​www.unipi.technology/​en/​accessories-c4|6-28V DC power supply]] for the JA-121T module+  * [[https://​www.unipi.technology/​en/​accessories-c4|6-28 V⎓ power supply]] for the JA-121T module
 </​WRAP>​ </​WRAP>​
 +
  
 ===== 1 Connection of the JA-121T module ​ ===== ===== 1 Connection of the JA-121T module ​ =====
-The JA-121T module provides galvanic isolation of Jablotron100 and RS-485 lines, using the separate power supply for each side highly recommended. One side of the module is powered by the Control Module. For the **galvanically isolated** side, use a 6-28V DC power supply different to the one used for PLC (see the module’s user manual). Connect the **D+** terminal on JA-121T with the **RS485-A** terminal on the PLC. Repeat for the **D-** and **RS485-B** terminals.+The JA-121T module provides galvanic isolation of Jablotron100 and RS-485 lines, using the separate power supply for each side highly recommended. One side of the module is powered by the Control Module. For the **galvanically isolated** side, use a 6-28 V⎓ power supply different to the one used for PLC (see the module’s user manual). Connect the **D+** terminal on JA-121T with the **RS485-A** terminal on the PLC. Repeat for the **D-** and **RS485-B** terminals.
  
 {{ :​en:​sw:​01-mervis:​Jablotron100_en_01.png?​nolink |}} {{ :​en:​sw:​01-mervis:​Jablotron100_en_01.png?​nolink |}}
Line 37: Line 38:
 ==== 2.1 Introduction ==== ==== 2.1 Introduction ====
 Jablotron 100(+) ESS Control Modules and their peripherals communicate via proprietary Jablotron bus. The JA-121T module acts as a gateway, converting the internal Jablotron bus to RS-485 serial bus with ASCII communication and providing information about the ESS to other systems. The module allows the user to set or read states of peripherals,​ sections or PGs. Jablotron 100(+) ESS Control Modules and their peripherals communicate via proprietary Jablotron bus. The JA-121T module acts as a gateway, converting the internal Jablotron bus to RS-485 serial bus with ASCII communication and providing information about the ESS to other systems. The module allows the user to set or read states of peripherals,​ sections or PGs.
 +
  
 === 2.1.1 Section === === 2.1.1 Section ===
 Using **Section_state** data points, it is possible to read or change states of the individual sections (armed, disarmed, maintenance etc.). **Section_flag** datapoints then display states of sirens, types of alarms, or enter and exit delays. ​ Using **Section_state** data points, it is possible to read or change states of the individual sections (armed, disarmed, maintenance etc.). **Section_flag** datapoints then display states of sirens, types of alarms, or enter and exit delays. ​
 +
  
 === 2.1.2 PG === === 2.1.2 PG ===
 Regarding Jablotron Control Modules, PGs are variables that can be controlled by various states, peripherals etc. In some installations,​ physical inputs or outputs can be also mapped to PGs. PGs are especially suitable for this tutorial due to their very short response time. PG can, for example, represent peripheral status, allowing you to read it from the system much faster. Regarding Jablotron Control Modules, PGs are variables that can be controlled by various states, peripherals etc. In some installations,​ physical inputs or outputs can be also mapped to PGs. PGs are especially suitable for this tutorial due to their very short response time. PG can, for example, represent peripheral status, allowing you to read it from the system much faster.
 +
  
 === 2.1.3 Periferie === === 2.1.3 Periferie ===
 The term "​peripheral"​ encompasses various external devices such as window magnetic contacts, motion sensors, camera traps etc. Unfortunately,​ the JA-121T module refreshes the current peripheral states every 10 seconds – this delay makes it unsuitable for some applications as peripheral states may not be always reliably detected. If you need faster read time, you can opt for reading PGs instead. ​ The term "​peripheral"​ encompasses various external devices such as window magnetic contacts, motion sensors, camera traps etc. Unfortunately,​ the JA-121T module refreshes the current peripheral states every 10 seconds – this delay makes it unsuitable for some applications as peripheral states may not be always reliably detected. If you need faster read time, you can opt for reading PGs instead. ​
 +
  
 === 2.1.4 JA-121T modes - Active vs Passive === === 2.1.4 JA-121T modes - Active vs Passive ===
Line 53: Line 58:
  
 //​*Peripheral states are updated once per 10 seconds.// //​*Peripheral states are updated once per 10 seconds.//
 +
  
 == Passive == == Passive ==
 Passive mode is based on a query/​response model. It is necessary to use passive mode if your installation requires the PLC to set anything in the ESS(section settings, PG controls etc.). Passive mode is based on a query/​response model. It is necessary to use passive mode if your installation requires the PLC to set anything in the ESS(section settings, PG controls etc.).
 +
  
 ==== 2.2 Configuration of Control Module ==== ==== 2.2 Configuration of Control Module ====
Line 89: Line 96:
   * prefix + user password   * prefix + user password
   * list of sections and PGs the user can control   * list of sections and PGs the user can control
 +
  
 ===== 3 Mervis IDE settings ​ ===== ===== 3 Mervis IDE settings ​ =====
Line 94: Line 102:
  
 Now create a new Mervis IDE project or open an already existing project. Follow the steps listed below: Now create a new Mervis IDE project or open an already existing project. Follow the steps listed below:
- 
  
 <​html><​figure ondblclick="​redirectImg(this)"​ class="​zoom"​ onclick="​zoom(event)"​ style="​background-image:​ url(https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_05.png)">​ <​html><​figure ondblclick="​redirectImg(this)"​ class="​zoom"​ onclick="​zoom(event)"​ style="​background-image:​ url(https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_05.png)">​
 <img src="​https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_05.png"​ /> <img src="​https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_05.png"​ />
 </​figure></​html>​ </​figure></​html>​
 +
  
 ==== 3.1 Přidání reference na knihovnu Lib.Jablotron ==== ==== 3.1 Přidání reference na knihovnu Lib.Jablotron ====
Line 114: Line 122:
 <img src="​https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_07.png"​ /> <img src="​https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_07.png"​ />
 </​figure></​html>​ </​figure></​html>​
 +
  
 ==== 3.2 Adding a communication channel in Mervis IDE and attachment of Control Module ==== ==== 3.2 Adding a communication channel in Mervis IDE and attachment of Control Module ====
Line 165: Line 174:
  
 The newly added device contains all available Control Module configurations. To ensure proper functionality,​ however, you need to optimize the device first, eg. to remove all data points of unused sections, peripherals,​ or PGs.  The newly added device contains all available Control Module configurations. To ensure proper functionality,​ however, you need to optimize the device first, eg. to remove all data points of unused sections, peripherals,​ or PGs. 
 +
  
 ==== 3.3 Optimization of Control Module device in Mervis IDE ==== ==== 3.3 Optimization of Control Module device in Mervis IDE ====
Line 172: Line 182:
  
 The optimization will be described in a practical installation example. The optimization will be described in a practical installation example.
 +
  
 === 1 Example setup: === === 1 Example setup: ===
 You want the PLC to read from the JA-103 Control Module two sections – Section 1 and Section 2. You also need to monitor 5 sensors mapped to the first five PGs of the Control Module. PG state is read from the Control Modules in 1–1.5 s. The JA-121T module must be set to **passive** mode. Reading from ESS is dependent on traffic on the bus.  You want the PLC to read from the JA-103 Control Module two sections – Section 1 and Section 2. You also need to monitor 5 sensors mapped to the first five PGs of the Control Module. PG state is read from the Control Modules in 1–1.5 s. The JA-121T module must be set to **passive** mode. Reading from ESS is dependent on traffic on the bus. 
 +
  
 === 2 Optimization guide: === === 2 Optimization guide: ===
Line 248: Line 260:
  
 <​html><​span class="​kbBlueText">​Recommended intervals:</​span></​html>​ \\ <​html><​span class="​kbBlueText">​Recommended intervals:</​span></​html>​ \\
-  * Section_flags_and_states_rd ..... 1s to 5s +  * Section_flags_and_states_rd ..... 1 s to 5 s 
-  * pg_rd ................................................... 0 to 500ms +  * pg_rd ................................................... 0 to 500 ms 
-  * peripheral ........................................... ​5s to 30s+  * peripheral ........................................... ​5 s to 30 s
  
 <WRAP center round important 75%> <WRAP center round important 75%>
Line 263: Line 275:
 More info about configuring Jablotron devices in the Mervis IDE and a complete description of all data points and/or groups is available in the Mervis IDE help. To open it, press F1.  More info about configuring Jablotron devices in the Mervis IDE and a complete description of all data points and/or groups is available in the Mervis IDE help. To open it, press F1. 
 </​WRAP>​ </​WRAP>​
 +
  
 ===== 4 Example of using function blocks and enumerated types ===== ===== 4 Example of using function blocks and enumerated types =====
Line 270: Line 283:
 <img src="​https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_23.png"​ /> <img src="​https://​kb.unipi.technology/​_media/​en:​sw:​01-mervis:​Jablotron100_en_23.png"​ />
 </​figure></​html>​ </​figure></​html>​
 +
  
 ==== 4.1 Datapoint transformation – SectionTransform ==== ==== 4.1 Datapoint transformation – SectionTransform ====
Line 275: Line 289:
  
 {{:​en:​sw:​01-mervis:​Jablotron100_en_24.png?​nolink |}} {{:​en:​sw:​01-mervis:​Jablotron100_en_24.png?​nolink |}}
 +
  
 ==== 4.2 Function blocks ==== ==== 4.2 Function blocks ====
Line 284: Line 299:
  
 {{ :​en:​sw:​01-mervis:​Jablotron100_en_25.png?​nolink&​170|}} {{ :​en:​sw:​01-mervis:​Jablotron100_en_25.png?​nolink&​170|}}
 +
  
 === 4.2.1 SectionFlags === === 4.2.1 SectionFlags ===
Line 293: Line 309:
  
 {{ :​en:​sw:​01-mervis:​Jablotron100_en_27.png?​nolink&​170|}} {{ :​en:​sw:​01-mervis:​Jablotron100_en_27.png?​nolink&​170|}}
 +
 +
 === 4.2.2 SectionFlagsHolder ===  === 4.2.2 SectionFlagsHolder === 
 A variant of SectionFlags with enhanced functionality. A SabotageAlarm output is added along with an automatic sabotage detection –if sabotage is detected, the output is set to TRUE. The main addition is the hold function designed to hold alarms until a change on the State section is detected. This means the block also requires a state input for the monitored section. The block is also extended by the Clear optional input for the option to manually reset all alarms on hold by setting them to FALSE. This input is hidden, and its use is optional. A variant of SectionFlags with enhanced functionality. A SabotageAlarm output is added along with an automatic sabotage detection –if sabotage is detected, the output is set to TRUE. The main addition is the hold function designed to hold alarms until a change on the State section is detected. This means the block also requires a state input for the monitored section. The block is also extended by the Clear optional input for the option to manually reset all alarms on hold by setting them to FALSE. This input is hidden, and its use is optional.
  
 {{ :​files:​img_breakline.png?​nolink |}} {{ :​files:​img_breakline.png?​nolink |}}
 +
 +
 ==== 4.3 SectionState enumerated type ==== ==== 4.3 SectionState enumerated type ====
  
Line 306: Line 326:
 **Usage:** to write into the variable, you need to use the ''​SectionState#​STATE''​ format. **Usage:** to write into the variable, you need to use the ''​SectionState#​STATE''​ format.
 <​code>​State := SectionState#​STATE;</​code>​ <​code>​State := SectionState#​STATE;</​code>​
 +
  
 === 4.3.2 FUPLA === === 4.3.2 FUPLA ===