Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
en:sw:01-mervis:creating-new-project-hidden [2022/01/10 09:12] avsetula |
en:sw:01-mervis:creating-new-project-hidden [2024/01/24 09:30] (current) avsetula [Uploading a blank configuration] |
||
|---|---|---|---|
| Line 108: | Line 108: | ||
| Now we move to the configuration. This part is especially important if you are just starting a new project with a controller or expansion modules that have been used in the past. That's because these devices may have a previous configuration that is independent of the uploaded solution, even the operating system, and may unexpectedly affect the operation of the entire solution. | Now we move to the configuration. This part is especially important if you are just starting a new project with a controller or expansion modules that have been used in the past. That's because these devices may have a previous configuration that is independent of the uploaded solution, even the operating system, and may unexpectedly affect the operation of the entire solution. | ||
| - | There is no need to worry, just right-click on the modbus table named after the assigned controller in the current clean project and select **Configure Unipi module**. This will load the default configuration. Detailed description of this procedure is in the article: [[cs:sw:01-mervis:unipi-configure-module-hidden|Konfigurace modulu Unipi]]. | + | There is no need to worry, just right-click on the modbus table named after the assigned controller in the current clean project and select **Configure Unipi module**. This will load the default configuration. Detailed description of this procedure is in the article: [[en:sw:01-mervis:unipi-configure-module-hidden|]]. |
| {{ :en:sw:01-mervis:12_creating-new-project_en.png?direct |}} | {{ :en:sw:01-mervis:12_creating-new-project_en.png?direct |}} | ||
