====== Uploading configuration ====== It is possible to upload from Mervis IDE to PLC: - [[#solution|Solution]] - program, HMI, HW definition - [[#configuration_of_io_modules|Configuration of IO modules]] - change of output modes, default values of outputs, setting of autonomous I/O functions, etc. - [[#configuration_of_the_runtime|Configuration of the Runtime]] - network interface settings, users definition, SSH, Mervis services, etc. ;;# Axon \\ Neuron \\ Unipi 1.1 \\ Extension ;;# ===== 1. Solution ===== **Solution configuration includes:** * Programs * List of channels and devices * HMI Hit **Deploy solution** on the **Ribbon** and select which parts of this configuration (Program, HMI,..) you want to upload and to which PLCs ===== 2. Configuration of IO modules ===== **Each of the IOs can have its own configuration settings. Those are:** * default value applied right after the power connection * mode of the analog inputs and outputs * Direct Switch for the digital inputs * PWM for digital outputs * Master watch dog This configuration isn't uploaded by deploying solution and you can read about the process [[en:sw:01-mervis:unipi-configure-module-hidden|here]] ===== 3. Configuration of the Runtime ===== **RT configuration upload includes:** * Network cards configuration * Language settings * Users definition (login credentials) * SSH, date and time * Proxy, Mervis DB and SSCP settings This configuration is **not** uploaded to the PLC via **Deploy solution**. Check **[[en:sw:01-mervis:updating-a-runtime-configuration-hidden|this tutorial]]** for additional info.