Product: Mingcedar CONTROL

Settings | Mingcedar

Open Settings from the system settings entry, or visit /settings on the host. Viewing and management permissions determine which settings are visible and editable.

Published 2026-10-25T12:48:42.631295428Z Updated 2026-10-25T12:48:42.631294656Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="host-settings">User guide: Settings</h2>

Settings includes Display & operation, Device collection, Python and Video service, with separate save and application rules. Ordinary LAN mode hides Site connections parameters; project-certificate mode exposes that category.

<h3 id="host-settings-item-1">Open Settings and inspect application status</h3>

<p>Open Settings from the system settings entry, or visit /settings on the host. Viewing and management permissions determine which settings are visible and editable.</p>

<ol>

<li>Select a category and compare configured values with Currently applied values. Deployment-overridden fields are read-only.</li>

<li>Use category defaults fills the current form only; review and save to apply. Reload discards unsaved changes and reads server settings.</li>

<li>Import & export settings covers this page only. Exports omit secrets; imports populate the form for review before saving.</li>

<li>After saving, check whether the change applies immediately or requires restart. If another window changed the configuration, reload and edit the latest version.</li>

</ol>

</article>

<h3 id="host-settings-item-2">Display & operation: background and command confirmation</h3>

<p>Interface preferences, alarm categories and runtime parameters save independently.</p>

<ol>

<li>Toggle built-in language entry visibility. This preference saves immediately without restart.</li>

<li>Choose whether the host background follows the exported PPT page or uses a uniform color.</li>

<li>Set command confirmation independently for runtime screens and device popups. Reason-required and hold/jog actions retain their own confirmation requirements.</li>

<li>Save background and command-confirmation settings, then restart as indicated.</li>

</ol>

</article>

<h3 id="host-settings-item-3">Alarm categories: number, name, color and priority</h3>

<p>Location: Settings → Display & operation → Alarm categories. The number identifies the category used by rules; it is neither a trigger threshold nor a priority ranking.</p>

<ol>

<li>Add a category with a unique positive integer, a name of 1–64 characters, a color and an execution priority.</li>

<li>Add categories as needed. The five installation defaults are editable; the catalog is not limited to five categories.</li>

<li>Save alarm categories to apply immediately without restart. Removing an item from the editor takes effect only after saving.</li>

<li>A category referenced by rules cannot be deleted or renumbered. Historical events retain the category information recorded at occurrence.</li>

<li>Enter the category number in the Tag alarm configuration, then set the condition, threshold, deadband, delay and enabled state.</li>

</ol>

</article>

<h3 id="host-settings-item-4">Device collection: consumer periods and connections</h3>

<p>Alarms, trends, screens, popups and script triggers share collected values.</p>

<ol>

<li>Set collection periods in milliseconds for each consumer type. A Tag with several active consumers uses the shortest required period.</li>

<li>Custom Tag rules match group codes or name regular expressions only when a Tag has no active consumer. Within a match type, higher numeric priority matches first.</li>

<li>Save Collection Policy to apply automatically, then inspect actual collection in Devices and Tag Diagnostics.</li>

<li>Expand Device connections & performance for default period, connect/request timeouts, reconnect interval, worker concurrency, block reads and OPC UA subscriptions. Respect field ranges and restart when indicated.</li>

<li>Worker concurrency applies across devices. Requests to one PLC remain serial, so more workers do not make one PLC faster.</li>

</ol>

</article>

<h3 id="host-settings-item-5">Python: packages and runtime parameters</h3>

<p>The Python category opens project package management. Runtime parameters have a separate entry in the same category.</p>

<ol>

<li>Manage dependencies per project, including package upload, directory import, custom shared packages and environment application. See Python projects and dependencies for the complete workflow.</li>

<li>Runtime parameters include timeout, memory, concurrency, reliable-event retention and the HTTP inbound signing secret. Adjust for the project workload and save.</li>

<li>Stored secrets are not displayed; leaving a secret blank preserves it. Restart after changing runtime parameters when the page indicates it.</li>

</ol>

</article>

<h3 id="host-settings-item-6">Site connections and video service</h3>

<p>Site-connection settings govern inter-site transport. The source site still controls its PLC collection settings.</p>

<ol>

<li>Ordinary LAN mode hides Site connections and does not require a shared key or CA in Settings. Project-certificate mode exposes the shared key, CA file, route refresh interval and HTTP timeout. Follow the connection chapter for that mode.</li>

<li>Video service selects managed MediaMTX or an existing gateway. Existing gateways need a playback URL; only existing MediaMTX needs a control API URL. Each address must be reachable by the relevant browser or host.</li>

<li>Save and restart when indicated, then open the relevant site or video screen to verify availability.</li>

</ol>

</article>

<h3 id="s7plus-driver-setup">Administrator: S7Plus driver deployment</h3>

<p>Check bundled S7Plus driver availability. For a separate deployment or replacement, follow these steps.</p>

<ol>

<li>Obtain the platform-matching driver, build manifest and license materials. Match the executable SHA-256 to the build manifest.</li>

<li>Set both the absolute S7PLUS_DRIVER_EXECUTABLE path and S7PLUS_DRIVER_SHA256 in protected deployment configuration. Windows uses the .exe executable. These are not everyday Settings form fields.</li>

<li>Schedule maintenance and stop the relevant collection services. Update files and configuration, then start services using the package management procedure.</li>

<li>Select Siemens S7Plus in Devices, enter host, port and required TLS settings, and save. Check configuration application, connectivity and Tag quality. For certificate errors, inspect the trust chain and server name.</li>

</ol>

</article>

</div>

<strong>Figure 1: Alarm categories and execution priorities</strong>

<p>Category IDs are used by alarm rules; execution priority is configured separately. Save Alarm Categories applies the changes immediately.</p>

</figcaption>

</figure>

<strong>Figure 2: Configure collection periods by use</strong>

<p>A Tag used in several places adopts the shortest required period. The values shown belong to this installation and can be adjusted for the project.</p>

</figcaption>

</figure>

</div>