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:automatic-restart-of-1-wire-hidden [2021/05/03 09:36] – avsetulaen:sw:01-mervis:automatic-restart-of-1-wire-hidden [2025/11/21 10:49] (current) – added links to comm attrib ofojt
Line 13: Line 13:
 </WRAP> </WRAP>
  
-<WRAP center round info 60%>+<WRAP group center round box 95%> 
 +{{ :files:img_warning-line_b.png?nolink |}} 
 +<WRAP half column 13%> 
 +{{ :en:hw:08_safety-instructions_pseudo-ISO-7010-info.png?nolink |(!)}} 
 +</WRAP> 
 +<WRAP half column 83%> 
 +**Note:** \\
 In Mervis, the property controlling the power supply for the 1-Wire bus is called **OW_off_1**. By setting the value to ''TRUE'', the bus will be disconnected from the power supply and by resetting back to ''FALSE'' the power supply will be connected back. In Mervis, the property controlling the power supply for the 1-Wire bus is called **OW_off_1**. By setting the value to ''TRUE'', the bus will be disconnected from the power supply and by resetting back to ''FALSE'' the power supply will be connected back.
 +</WRAP>
 </WRAP> </WRAP>
  
-You can reset the power supply manually, but with the help of **commerror** attributes, you can let Mervis do it automatically. The attributes are available on the particular device or the whole channel and they indicate when the Mervis wasn't able to read the datapoints for given device/channel.+You can reset the power supply manually, but with the help of **commerror** [[.:comm-attributes-hidden|communication attributes]], you can let Mervis do it automatically. [[.:comm-attributes-hidden|The communication attributes]] are available on the particular device or the whole channel and they indicate when the Mervis wasn't able to read the datapoints for given device/channel.
  
 We will start the project in the **Full mode**, attaching to the controller, creating a FBD program and setting a task executing this program. Next we create ModbusTCP channel for the IOs of the PLC and 1-Wire channel for the 1-Wire bus. Then deploy the solution and detect the 1-Wire sensors. Your workspace should look like this: We will start the project in the **Full mode**, attaching to the controller, creating a FBD program and setting a task executing this program. Next we create ModbusTCP channel for the IOs of the PLC and 1-Wire channel for the 1-Wire bus. Then deploy the solution and detect the 1-Wire sensors. Your workspace should look like this:
Line 40: Line 46:
 {{ :en:sw:01-mervis:automatic-restart-of-the-1-wire-04-complete-project.png?direct |}} {{ :en:sw:01-mervis:automatic-restart-of-the-1-wire-04-complete-project.png?direct |}}
  
-All we need to alter is the length of the pulse and the pause between pulses to some reasonable values such as Ttrue = 1s and Tfalse = 4s, deploy the solution and start debugging. Then you can unplug the 1-Wire sensor and you will see that the measured values are red and the **commerror** attribute is ''TRUE'' and the **Pulse Generator** is sending reset pulses to the bus:+All we need to alter is the length of the pulse and the pause between pulses to some reasonable values such as Ttrue = 1 s and Tfalse = 4 s, deploy the solution and start debugging. Then you can unplug the 1-Wire sensor and you will see that the measured values are red and the **commerror** attribute is ''TRUE'' and the **Pulse Generator** is sending reset pulses to the bus:
  
 {{ :en:sw:01-mervis:automatic-restart-of-the-1-wire-05-debugging.png?direct |}} {{ :en:sw:01-mervis:automatic-restart-of-the-1-wire-05-debugging.png?direct |}}
(Still can't find what you're looking for?)