Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:sw:01-mervis:unipi-configure-module-hidden [2021/06/04 13:25]
avsetula
en:sw:01-mervis:unipi-configure-module-hidden [2021/06/07 06:48] (current)
avsetula
Line 2: Line 2:
 <WRAP group> <WRAP group>
 <WRAP half column 81%> <WRAP half column 81%>
-A Unipi Neuron/​Patron consists of small computer running a GNU/Linux and HW IO modules (see inner diagram for [[en:​hw:​02-neuron|Neuron]] and [[en:hw:01-axon|Axon]]). These modules offer different functionality based on the IOs they present. For example [[en:​automation:​02-glossary:​digital-inputs-hidden|digital inputs]] can act as Direct Switches, [[en:​automation:​02-glossary:​analog-inputs-hidden|analog inputs]] can measure different quantities, [[en:​automation:​02-glossary:​digital-outputs-hidden|digital outputs]] can output PWM and so on. Any output can have a default value, which applies right after powering up the PLC, way before the finishing the boot up sequence of the operating system. This configuration also applies to the [[en:​hw:​04-extensions|Unipi Extensions]],​ albeit they don't run any OS.+A Unipi Neuron/​Patron consists of small computer running a GNU/Linux and HW IO modules (see inner diagram for [[en:​hw:​02-neuron|Neuron]] and [[en:hw:007-patron|Patron]]). These modules offer different functionality based on the IOs they present. For example [[en:​automation:​02-glossary:​digital-inputs-hidden|digital inputs]] can act as Direct Switches, [[en:​automation:​02-glossary:​analog-inputs-hidden|analog inputs]] can measure different quantities, [[en:​automation:​02-glossary:​digital-outputs-hidden|digital outputs]] can output PWM and so on. Any output can have a default value, which applies right after powering up the PLC, way before the finishing the boot up sequence of the operating system. This configuration also applies to the [[en:​hw:​04-extensions|Unipi Extensions]],​ albeit they don't run any OS.
 </​WRAP>​ </​WRAP>​
 <WRAP half column 15%> <WRAP half column 15%>
Line 14: Line 14:
 </​WRAP>​ </​WRAP>​
  
-<WRAP center round tip 60%>+ 
 +<WRAP center round tip 90%>
 All of these configurations are OS-independent and are permanently stored into the modules. If you receive an used Unipi unit, the best approach is to save a blank new configuration to overwrite possible unwanted settings. All of these configurations are OS-independent and are permanently stored into the modules. If you receive an used Unipi unit, the best approach is to save a blank new configuration to overwrite possible unwanted settings.
 </​WRAP>​ </​WRAP>​
- + 
 +<WRAP center round important 90%> 
 +After changing parameters for serial lines **ttyNS** (see: port mapping table for [[en:​hw:​007-patron:​portmap|Patron]]/​[[en:​hw:​02-neuron:​portmap|Neuron]]/​[[en:​hw:​01-axon:​portmap|Axon]]) it is then necessary to upload the configuration to the controller. Before uploading the configuration,​ always make sure that the other settings (output mode, default values, etc.) are set correctly. 
 + 
 +If the configuration is not loaded after changing the serial line settings, the serial line configuration may be reset when the I/O board is restarted. 
 +</​WRAP>​ 
 In Mervis, the configuration is pushed via context menu of the connected prototype. Right click on the prototype name in the **Left Panel** and in the context menu click on "​**Unipi - Configure Module**"​. In Mervis, the configuration is pushed via context menu of the connected prototype. Right click on the prototype name in the **Left Panel** and in the context menu click on "​**Unipi - Configure Module**"​.