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:creating-new-project-on-unipi11-hidden [2021/08/05 11:42] – avsetulaen:sw:01-mervis:creating-new-project-on-unipi11-hidden [2024/07/22 12:58] (current) – kcerny
Line 13: Line 13:
 ;;# ;;#
 </WRAP> </WRAP>
 +</WRAP>
 +
 +<WRAP center round alert 60%>
 +Mervis 2.6.5 and newer do not use this way anymore, please refer [[en:sw:01-mervis:creating-new-project-hidden|to this article]].
 </WRAP> </WRAP>
  
Line 23: Line 27:
   - MicroSD->SD adapter or a microSD card reader with USB connector   - MicroSD->SD adapter or a microSD card reader with USB connector
   - [[https://www.unipi.technology/napajeci-zdroj-pro-din-listu-5v-dc-2-4a-p65?categoryId=15|5 V⎓ / 2 A power supply]]   - [[https://www.unipi.technology/napajeci-zdroj-pro-din-listu-5v-dc-2-4a-p65?categoryId=15|5 V⎓ / 2 A power supply]]
-  - Downloaded archive with [[en:files:software:os-images:00-start#unipi_11_mervis_os|Mervis OS for Unipi 1.1/Lite]]+  - Downloaded archive with [[en:hw:03-unipi11:download-image:01-mervis|Mervis OS for Unipi 1.1/Lite]]
   - Computer with [[en:files:software:mervis:00-start|Mervis IDE]] installed.    - Computer with [[en:files:software:mervis:00-start|Mervis IDE]] installed. 
  
Line 31: Line 35:
   - [[en:sw:01-mervis:01-mervis-ide| Get to know Mervis IDE]]   - [[en:sw:01-mervis:01-mervis-ide| Get to know Mervis IDE]]
   - [[en:sw:01-mervis:connecting-to-unipi-hidden| Connect the PLC to your computer]]   - [[en:sw:01-mervis:connecting-to-unipi-hidden| Connect the PLC to your computer]]
-  - [[en:sw:01-mervis:running-on-neuron-hidden#mervis_on_unipi_neuron_11| Deploy Mervis OS to the SD card]]+  - [[en:sw:01-mervis:running-on-unipi11-hidden| Deploy Mervis OS to the SD card]]
   - Plug in the power supply and wait for at least a minute until the PLC's OS boots up.    - Plug in the power supply and wait for at least a minute until the PLC's OS boots up. 
 </WRAP> </WRAP>
Line 99: Line 103:
  
 ===== Connecting inputs/outputs ===== ===== Connecting inputs/outputs =====
-In Mervis IDE you now have Unipi 1.1/Lite attached. Construction-wise, Unipi controllers consist of a computing module (Raspberry Pi in our case) and a circuit board with inputs and outputs. The board communicates with the computer using **Modbus TCP** and **I2C**. This is the reason why you need to set up **two** communication channels to control Unipi 1.1/1.1 Lite boards. The first channel is for controlling analog and digital I/Os via Modbus TCP protocol while the I2C channel controls relay outputs. +In Mervis IDE you now have Unipi 1.1/Lite attached. Construction-wise, Unipi controllers consist of a computing module (Raspberry Pi in our case) and a circuit board with inputs and outputs. The board communicates with the computer using **Modbus TCP** and **I²C**. This is the reason why you need to set up **two** communication channels to control Unipi 1.1/1.1 Lite boards. The first channel is for controlling analog and digital I/Os via Modbus TCP protocol while the I²C channel controls relay outputs. 
  
 Add two **communication channels** to the PLC. TO add a channel right-click on the **PLC** name and then click on **Add Channel**. Repeat for the second channel.  Add two **communication channels** to the PLC. TO add a channel right-click on the **PLC** name and then click on **Add Channel**. Repeat for the second channel. 
Line 109: Line 113:
 {{ :en:sw:01-mervis:12_creating-new-project-on-unipi11_en.png?direct |}} {{ :en:sw:01-mervis:12_creating-new-project-on-unipi11_en.png?direct |}}
  
-If you click on the first channel, its properties will appear in the right panel. The first item determines the channel's name; we recommend to give channels descriptive names - in this case, I2C will do. +If you click on the first channel, its properties will appear in the right panel. The first item determines the channel's name; we recommend to give channels descriptive names - in this case, I²C will do. 
  
-Click on **no protocol** and select **PlatformIO** from the list. By doing so more options will appear - all you need to do here is to make sure the **link protocol** is set to **I2C**. +Click on **no protocol** and select **PlatformIO** from the list. By doing so more options will appear - all you need to do here is to make sure the **link protocol** is set to **I²C**. 
  
 The first channel for relay outputs is already set.  The first channel for relay outputs is already set. 
Line 125: Line 129:
 With both channels configured we can now move to add individual devices. These device definitions **are different between Unipi 1.1 and Unipi 1.1 Lite**, making the correct selection of definition necessary.  With both channels configured we can now move to add individual devices. These device definitions **are different between Unipi 1.1 and Unipi 1.1 Lite**, making the correct selection of definition necessary. 
  
-==== I2C ==== +==== I²C ==== 
-In the **left panel** right-click on the I2C channel. Select **Add Library Device** from the context menu. +In the **left panel** right-click on the I²C channel. Select **Add Library Device** from the context menu. 
  
 {{ :en:sw:01-mervis:15_creating-new-project-on-unipi11_en.png?direct |}} {{ :en:sw:01-mervis:15_creating-new-project-on-unipi11_en.png?direct |}}
  
-In the **Add Library Device** dialogue window you will see a list of devices. Find and expand the **Unipi (v1.1)** folder and move to the **I2C** subfolder. Select the suitable device definition accordingly (eg. **Analog-Inputs + Unipi1_Relays** for Unipi 1.1 and **Unipi1Lite_Relay** for Unipi 1.1 Lite). If you have the definition selected, click on the arrow icon {{:files:dialog_arrow_right.png?nolink|}} to add the controller into the list of the selected device. After that, you need only to confirm by clicking on OK. +In the **Add Library Device** dialogue window you will see a list of devices. Find and expand the **Unipi (v1.1)** folder and move to the **I²C** subfolder. Select the suitable device definition accordingly (eg. **Analog-Inputs + Unipi1_Relays** for Unipi 1.1 and **Unipi1Lite_Relay** for Unipi 1.1 Lite). If you have the definition selected, click on the arrow icon {{:files:dialog_arrow_right.png?nolink|}} to add the controller into the list of the selected device. After that, you need only to confirm by clicking on OK. 
  
 {{ :en:sw:01-mervis:16_creating-new-project-on-unipi11_en.png?direct |}} {{ :en:sw:01-mervis:16_creating-new-project-on-unipi11_en.png?direct |}}
Line 145: Line 149:
 {{ :en:sw:01-mervis:18_creating-new-project-on-unipi11_en.png?direct |}} {{ :en:sw:01-mervis:18_creating-new-project-on-unipi11_en.png?direct |}}
  
-The new device will appear below the corresponding I2C / Modbus TCP channel. +The new device will appear below the corresponding I²C / Modbus TCP channel. 
  
 {{ :en:sw:01-mervis:19_creating-new-project-on-unipi11_en.png?direct |}} {{ :en:sw:01-mervis:19_creating-new-project-on-unipi11_en.png?direct |}}
Line 245: Line 249:
 {{ :en:sw:01-mervis:37_creating-new-project-on-unipi11_en.png?direct |}} {{ :en:sw:01-mervis:37_creating-new-project-on-unipi11_en.png?direct |}}
  
-In the **Insert existing variable**, a list of all available variables, inputs and outputs of your controller will be displayed. If the list is nearly empty, you probably did not use Autogen to define variables available for your PLC. In that case, right-click on devices in both I2C and Modbus TCP channels and click on **Set autogen** in the context menu. +In the **Insert existing variable**, a list of all available variables, inputs and outputs of your controller will be displayed. If the list is nearly empty, you probably did not use Autogen to define variables available for your PLC. In that case, right-click on devices in both I²C and Modbus TCP channels and click on **Set autogen** in the context menu. 
  
 If you followed the guide closely, Simple Mode already generated all variables for the program. If you followed the guide closely, Simple Mode already generated all variables for the program.
(Still can't find what you're looking for?)