Easy Config System

[Deanna]

TheEasy Config System configuration software allows you to configure your Socomec measuring and load breaking equipment, while viewing all the electrical quantities in real time. Its speed and simplicity make the Easy Config System software an essential tool for

Access to Easy Config System can be done either locally, by connecting to the products via a USB cable, or remotely by connecting via the Ethernet network. This system provides great flexibility, taking into account the constraints of facilities. Remote access allows any user to change settings, correct any configuration or wiring errors without having to physically travel to the site.

Easy Config system is equipped with a dynamic dashboard depending on the type of product, and can display the Fresnel diagram, the alarms in progress, or the detected sensors and their calibers. This also gives an overview of the topology, containing the list of connected products, the quality of communication, their firmware version and their internal clock. This helps ensure precise wiring, reliable configuration and therefore actionable data for the user.

The new Easy Config System software now offers a system approach for a quicker, more reliable, and more flexible configuration of your power monitoring system.

It includes visualization dashboards with real-time data to detect potential wiring or configuration errors early during commissioning. The software also allows to configure multiple devices simultaneously.

The Easy Config System configuration software allows you to configure your Socomec measuring and load-breaking equipment while viewing all the electrical quantities in real-time. Its speed and simplicity make the Easy Config System software an essential tool for: the panel builder, the system integrator, wanting to guarantee a correctly configured cabinet to his customer the operator, wishing to configure his products himself or modify certain parameters The plus: all the configurations created can be saved, modified and easily transferred from one device to another or from one system to another.

Easy Config System allows panel builders and system integrators to configure their installations easily and quickly: auto-detection of connected products configuration of several products simultaneously duplication of a configuration from one product to another.

Access to Easy Config System can be done locally by connecting to the products via a USB cable or remotely via the Ethernet network. This system provides excellent flexibility, taking into account the constraints of facilities. Remote access allows users to change settings and correct configuration or wiring errors without traveling to the site.

Easy Config system is equipped with a dynamic dashboard depending on the product type. It can display the Fresnel diagram, the alarms in progress, or the detected sensors and their calibers. This also gives an overview of the topology, containing the list of connected products, the quality of communication, their firmware version, and their internal clock. This helps ensure precise wiring, reliable configuration, and, therefore, actionable data for the user.

It automatically opens if you keep the Finish installation in MyQ Easy Config option selected during the installation of the server. Otherwise, you can find it on the Apps screen in Windows 8.1+, Windows Server 2012 and newer. After you open the application, you see its menu on the left side. From this menu, you can access the following settings:

On the Home tab, you can quickly change the default password of the Server Administrator account, and generate data for support. You can also be redirected to the MyQ Web Administrator Interface to finish the server setup.

On the Settings tab, you can modify the Windows Services, Server administrator, and Database Administrator accounts, change file paths of the MyQ system data and jobs files, change the port configuration of the MyQ server, and clean up your Cache and Temp folders.

Luckily, the majority of software delivery mechanisms are being designedaround either autotools or CMake or, perhaps, some simple fileextraction/copy pattern. In that case, a generic easyblock can beleveraged; see Overview of generic easyblocks.

Yet, in case the software build calls for more elaborate steps(scientific software never fails to surprise us in this regard), asoftware-specific easyblock may be required; seeImplementing easyblocks.

A tuple adds the possibility to specify where patch should be applied.This is mostly needed if a patch file adds new files or it is generallynot possible to determine the starting directory. The first element isthe patch file and the second is either the patch level (as an integer)which is used in the patch command (patch -p) or a directoryrelative to the unpacked source dir.

tuple also has a special use case if the patch file has any other extension than .patch.In this case, the first tuple argument is a file which should becopied to the unpacked source dir and the second tuple argument isthe target path, where the files should be copied to (relative tothe unpacked source dir). See below for an example of this use case.

A dict adds the ability to pass the patch command additionalarguments. For example, the --binary flag is needed to patch fileswith CRLF endings. The dict has a required filename key, withlevel and opts being optional ones.

EasyBuild does not enforce checksums to be available for all sourcefiles and patches. Provided checksums will be 'consumed' first for thespecified sources (in order), and subsequently also for patches.

Multiple easyconfigs can be specified when using --inject-checksums,they will be processed in sequence. In addition, you can also combine--inject-checksums with --robot, seeSynergy between --inject-checksums and --robot.

Along with injecting checksums, EasyBuild will also reorder the source_urls, sourcesand patches specifications, in that order and if they are present,and include the checksums specification afterwards. This is doneto facilitate working towards a uniform style in easyconfig files,which also applies to the order of specified easyconfig parameters.

When one or more checksums are already specified, EasyBuild requires theuse of --force together with --inject-checksums to replace thosechecksums. A clear warning will be printed to notify that existingchecksums will be replaced.

Any existing checksums are blindly replaced when--inject-checksums --force is used: the existing checksums arenot verified to be correct as during normal use of EasyBuild(since that would kind of defeat the purpose of--inject-checksums).In addition, it also doesn't matter whether or not checksums areavailable for all sources & patches: with --inject-checksums,checksums will be added for all sources and patches, including forextensions listed in exts_list (if any).

Because of the optional argument that can be passed to --inject-checksums,you should not specify an easyconfig file name directly after the--inject-checksums, since it will be assumed to specify a checksumtype, which will result in an error message like:

In some cases, it can be required to provide additional information nextto the name of a source file, e.g., a custom extraction command (becausethe one derived from the file extension is not correct), or an alternamefilename that should be used to download the source file.

Custom extraction commands can also be specified as a 2-element tuple, but this format has been deprecatedin favour of the Python dictionary format described above; see alsoSpecifying source files as 2-element tuples to provide a custom extraction command.

You can use the download_instructions parameter to specify steps forthe user to do. This parameter takes string value and prints it wheneverbuild fails because any file needed was not found. Ifdownload_instructions is not specified, Easybuild prints the defaultmessage stating the paths that were tested.

Whenever you have the option to download a source tarball (orequivalent) directly (for example from GitHub, which also allowsdownloading a tarball of a specific commit), we strongly recommendyou to do so, git_config is intended for other Git repos.

For each of the specified (build) dependencies, the corresponding modulewill be loaded in the build environment defined by EasyBuild. For theruntime dependencies, module load statements will be included in thegenerated module file.

By default, EasyBuild will try to resolve dependencies using the same toolchain as specified for thesoftware being installed. As of v3.0, if no easyconfig exists toresolve a dependency using the default toolchain EasyBuild willsearch for the dependency using a compatible subtoolchain.

When a system toolchain is used, themodules for each of the (build) dependencies are always loaded,regardless of the toolchain version (as opposed the behaviour with thedummy toolchain in EasyBuild versions prior to v4.0, seeMotivation for deprecating the dummy toolchain).

Besides dependencies, which are found outside the software being builtbut are part of the site's EasyBuild installation, it is also possibleto incorporate extensions to the software within the build. This is donevia the exts_list array.

That third instance uses the name and version variables defined inthe easyconfig file. Since EasyBuild v4.2.2, a single-entry sourcesdictionary (see Alternative formats for sources) may be included in an exts_list entry. For example, todownload Git sources from a private repository and convert them to atar-ball for installation:

During this process, the environment is reset and the build directory iscleaned up after each cycle, while the installation directory is leftuntouched (in order to not destroy the result of earlier cycles).

If several (pre)buildopts parameters are defined asbeing a list of strings, the number of items in the lists must be thesame. Any of these parameters defined as a single string value are justreused for each of the cycles performed. For example:

3a8082e126