Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:sw:01-mervis:attaching-1-wire-devices-hidden [2018/06/08 13:42] – martin_kudlaceken:sw:01-mervis:attaching-1-wire-devices-hidden [2024/09/24 11:22] (current) – avsetula
Line 1: Line 1:
 ====== Attaching 1-Wire devices ====== ====== Attaching 1-Wire devices ======
 +<WRAP group>
 +<WRAP half column 81%>
 In this tutorial, we are going to demonstrate, how to connect [[https://www.unipi.technology/1-wire-temperature-sensor-p63?categoryId=3|1-Wire temperature sensor]] and create very simple temperature regulator.  In this tutorial, we are going to demonstrate, how to connect [[https://www.unipi.technology/1-wire-temperature-sensor-p63?categoryId=3|1-Wire temperature sensor]] and create very simple temperature regulator. 
 +</WRAP>
 +<WRAP half column 15%>
 +;;#
 +<html><span class="dev-tag dev-patron">Patron</span></html> \\
 +<html><span class="dev-tag dev-neuron">Neuron</span></html> \\
 +<html><span class="dev-tag dev-unipi11">Unipi&nbsp1.1</span></html> \\
 +<html><span class="dev-tag dev-axon">Axon</span></html>
 +;;#
 +</WRAP>
 +</WRAP>
  
-===== Prerequisites ===== +<WRAP center round box> 
-  * UniPi controller running Mervis OS+<html><span class="kbBlue-H4alt">Prerequisites:</span></html> 
 +  * Unipi controller running Mervis OS
   * Basic project in Mervis IDE in **Full mode** with   * Basic project in Mervis IDE in **Full mode** with
     * attached controller     * attached controller
-    * created ModbusTCP channel with the UniPi controller device+    * created ModbusTCP channel with the Unipi controller device
     * defined **Executable project** with one program     * defined **Executable project** with one program
     * setted **Autogen** on the Unipi controller device     * setted **Autogen** on the Unipi controller device
     * defined task running a program from **Executable project**     * defined task running a program from **Executable project**
     * successfully executed **Build**     * successfully executed **Build**
-  * [[https://www.unipi.technology/power-supplies-c15|24V power supply]]+  * [[https://www.unipi.technology/power-supplies-c15|24 V⎓ power supply]]
   * [[https://www.unipi.technology/1-wire-temperature-sensor-p63?categoryId=3|1-Wire temperature sensor]]   * [[https://www.unipi.technology/1-wire-temperature-sensor-p63?categoryId=3|1-Wire temperature sensor]]
  
-In this tutorial, we will use [[https://www.unipi.technology/unipi-neuron-l503-p105?categoryId=10|Unipi Neuron L503]].+In this tutorial, we will use [[https://www.unipi.technology/neuron-c2|Unipi Neuron L503]]. 
 +</WRAP>
  
 ===== Attaching 1-Wire temperature sensor ===== ===== Attaching 1-Wire temperature sensor =====
-The [[https://www.unipi.technology/1-wire-temperature-sensor-p63?categoryId=3|1-Wire temperature sensor]] available in our eshop is equipped with RJ45 connector, which can be directly connected to [[en:hw:01-products:neuron|UniPi Neuron]] units. 
- 
-FIXME obrazek pripojeni cidla k Neuronu 
  
-FIXME pripojovani k Axonu+You can find all the informations about how to connect the DS18B20 based temeperature sensor [[en:automation:02-glossary:1wire-hidden|here]].
  
 ===== Configuring 1-Wire bus in Mervis ===== ===== Configuring 1-Wire bus in Mervis =====
Line 43: Line 54:
  
 {{ :en:sw:01-mervis:attaching-1-wire-devices-04-set-channel-link-protocol.png?direct |}} {{ :en:sw:01-mervis:attaching-1-wire-devices-04-set-channel-link-protocol.png?direct |}}
 +
 +You now need to **deploy the solution** into the PLC to create the **OneWire** communication channel on it. 
  
 ===== Detecting 1-Wire sensors ===== ===== Detecting 1-Wire sensors =====
  
-1-Wire bus is a serial bus, which can interconnect many sensors. Each sensor has its unique HW address, through which the master of the bus addresses the slave and reads data from. Therefor we need to tell UniPi controller to look for a certain devices on the bus. Luckily, we can detect all the sensors on the bus and then select the ones we are interested in.+1-Wire bus is a serial bus, which can interconnect many sensors. Each sensor has its unique HW address, through which the master of the bus addresses the slave and reads data from. Therefor we need to tell Unipi controller to look for a certain devices on the bus. Luckily, we can detect all the sensors on the bus and then select the ones we are interested in.
  
 To detect the sensors, right click on the **1wire** channel name under the PLC in the **Solution** tab of the **Left panel**. In the context menu, click on the **Detect One Wire Sensors**. To detect the sensors, right click on the **1wire** channel name under the PLC in the **Solution** tab of the **Left panel**. In the context menu, click on the **Detect One Wire Sensors**.
Line 65: Line 78:
  
 {{ :en:sw:01-mervis:attaching-1-wire-devices-09-selecting-sensors.png?direct |}} {{ :en:sw:01-mervis:attaching-1-wire-devices-09-selecting-sensors.png?direct |}}
 +
 +<WRAP center round important 90%>
 +If you have connected a Unipi 1W-TH-IB(2) sensor and after autodetection **1W-UniversalAi** is not automatically selected in the "Prototype name" column, you must manually select it, otherwise the sensor will not work correctly.
 +</WRAP>
  
 The importing of the sensor will proceed and finish with restoring the PLC's mode. The importing of the sensor will proceed and finish with restoring the PLC's mode.
Line 77: Line 94:
  
 ===== Debugging solution ===== ===== Debugging solution =====
-The Mervis IDE has a feature called **Debugging**, which allows to connect to the running UniPi controller, read its state and even alter the variables on-the-fly. To start the debugging, click on the **Start Debugging** button on the **Ribbon**.+The Mervis IDE has a feature called **Debugging**, which allows to connect to the running Unipi controller, read its state and even alter the variables on-the-fly. To start the debugging, click on the **Start Debugging** button on the **Ribbon**.
  
 {{ :en:sw:01-mervis:attaching-1-wire-devices-13-debug.png?direct |}} {{ :en:sw:01-mervis:attaching-1-wire-devices-13-debug.png?direct |}}
  
-To view the variables and their state in debug mode, click on the **Variable Browser** tab on the **Main window**. You will be presented with all the variables available in the controller. You can use searching by **Name**. Our temperature sensor has been autonamed "1W-Thermometer" (check the device in the **Left panel** under the **1wire** channel), so enter this name into the **Name** searchbox. The variable containing the actual temperature is called **1W-Thermometer_Temperature** and its current value in PLC is **29.875**°C.+To view the variables and their state in debug mode, click on the **Variable Browser** tab on the **Main window**. You will be presented with all the variables available in the controller. You can use searching by **Name**. Our temperature sensor has been autonamed "1W-Thermometer" (check the device in the **Left panel** under the **1wire** channel), so enter this name into the **Name** searchbox. The variable containing the actual temperature is called **1W-Thermometer_Temperature** and its current value in PLC is **29.875** °C.
  
 {{ :en:sw:01-mervis:attaching-1-wire-devices-14-variable-browser.png?direct |}} {{ :en:sw:01-mervis:attaching-1-wire-devices-14-variable-browser.png?direct |}}
Line 88: Line 105:
 We have connected the temperature sensor to our controller and verified, that we can read current temperature. Now we can use it in very simple temperature regulator. We have connected the temperature sensor to our controller and verified, that we can read current temperature. Now we can use it in very simple temperature regulator.
  
-We will be monitoring temperature and if the temperature will be under 30°C, we will turn the ''RO2.1'' ''ON'' and when the temperature will be greater or equal to 30°C, we will turn the ''RO2.1'' ''OFF''. The ''RO2.1'' will represent a heating element.+We will be monitoring temperature and if the temperature will be under 30 °C, we will turn the ''RO2.1'' ''ON'' and when the temperature will be greater or equal to 30 °C, we will turn the ''RO2.1'' ''OFF''. The ''RO2.1'' will represent a heating element.
  
-We could "hardwire" the temperature "30°C" into the program, but we wouldn't be able to change it afterwards other than reprogramming the PLC. Most likely, we would like to set the threshold (or desired) temperature by some knob, buttons or even HMI device. So it is better to define it as another variable and set the threshold by changing the variable's value. Later we can wire this variable to some other HW input.+We could "hardwire" the temperature "30 °C" into the program, but we wouldn't be able to change it afterwards other than reprogramming the PLC. Most likely, we would like to set the threshold (or desired) temperature by some knob, buttons or even HMI device. So it is better to define it as another variable and set the threshold by changing the variable's value. Later we can wire this variable to some other HW input.
  
 Our program will therefor need two inputs: ''measured_temperature'' and ''threshold_temperature''. In programming, each variable has to have some type - a definition, of what it can store. It can be integer, real number, boolean, character, string of characters or even more complicated type. Temperature by its nature is real number and so will be our variables ''measure_temperature'' and ''threshold_temperature''. Our program will therefor need two inputs: ''measured_temperature'' and ''threshold_temperature''. In programming, each variable has to have some type - a definition, of what it can store. It can be integer, real number, boolean, character, string of characters or even more complicated type. Temperature by its nature is real number and so will be our variables ''measure_temperature'' and ''threshold_temperature''.
Line 98: Line 115:
 Let's start creating our program. Programming has to be done when the **Debugging** is stopped, so stop it by clicking on the **Stop Debugging** on the **Ribbon**, if you have it still running. Then double click on the name of the program in the **Left panel** to display it in the **Main window**. Let's start creating our program. Programming has to be done when the **Debugging** is stopped, so stop it by clicking on the **Stop Debugging** on the **Ribbon**, if you have it still running. Then double click on the name of the program in the **Left panel** to display it in the **Main window**.
  
-If you remember, in the **Variable browser**, the name of temperature variable was **1W-Thermometer_Temperature**. The name is autogenerated, and the first part is from the name of the sensor. That's not very descriptive, so we will change the name of the sensor to **office**, because it is measuring temperature in our office. Click on the name of the sensor in the **Left panel**. In the **Properties panel**, you can see property **Name**. Change it's value to **office** and either click on the **V** or submit by **ENTER** key. +If you remember, in the **Variable browser**, the name of temperature variable was **1W-Thermometer_Temperature**. The name is autogenerated, and the first part is from the name of the sensor. That's not very descriptive, so we will change the name of the sensor to **office**, because it is measuring temperature in our office. Click on the name of the sensor in the **Left panel**. In the **Properties panel**, you can see property **Name**. Change it's value to **office** and either click on the {{:files:dialog-confirm_button_2.png?nolink|}} or submit by **ENTER** key. 
  
 {{ :en:sw:01-mervis:attaching-1-wire-devices-16-sensor-name.png?direct |}} {{ :en:sw:01-mervis:attaching-1-wire-devices-16-sensor-name.png?direct |}}
Line 132: Line 149:
 If you have the correct connections, you can **Build** the solution and if the **Build** succeeds, **Deploy** the solution to the controller. If you have the correct connections, you can **Build** the solution and if the **Build** succeeds, **Deploy** the solution to the controller.
  
-If your **Deploy** went well, you can **Start Debugging**. In the debugging mode, you can see actual values of each input and output of each block. You can see temperature in our office is 29.625°C, which is less then threshold of 30°C and therefor the heating is ''ON'' (''TRUE'').+If your **Deploy** went well, you can **Start Debugging**. In the debugging mode, you can see actual values of each input and output of each block. You can see temperature in our office is 29.625 °C, which is less then threshold of 30 °C and therefor the heating is ''ON'' (''TRUE'').
  
 {{ :en:sw:01-mervis:attaching-1-wire-devices-23-debugging-low.png?direct |}} {{ :en:sw:01-mervis:attaching-1-wire-devices-23-debugging-low.png?direct |}}
  
-I warmed up the sensor a little bit and now it shows 30.875°C which is more than 30°C and therefor the heating is ''OFF'' (''FALSE'')+I warmed up the sensor a little bit and now it shows 30.875 °C which is more than 30 °C and therefor the heating is ''OFF'' (''FALSE'')
  
 {{ :en:sw:01-mervis:attaching-1-wire-devices-23-debugging-high.png?direct |}} {{ :en:sw:01-mervis:attaching-1-wire-devices-23-debugging-high.png?direct |}}
  
-Also the relay on your UniPi controller should switch ''ON'' and ''OFF''. If yes, congratulations! You just created your very first temperature regulator.+Also the relay on your Unipi controller should switch ''ON'' and ''OFF''. If yes, congratulations! You just created your very first temperature regulator.
  
 ===== Download ===== ===== Download =====
  
 You can download the whole project here: {{ :en:sw:01-mervis:attaching-1-wire-devices.zip |}} You can download the whole project here: {{ :en:sw:01-mervis:attaching-1-wire-devices.zip |}}
(Still can't find what you're looking for?)