Somic Eagle – Settings Page
The Settings page in Somic Eagle is the central configuration hub for the entire application. It allows administrators to configure machine identity, OPC-UA connectivity, storage behaviour, FTP connections, camera triggers, and individual camera setups.
Access control: The Settings page is password-protected. Before any settings are displayed, you must enter the access password. If the wrong password is entered, an “Incorrect password” error is shown in red. Once authenticated, the full settings interface becomes available.
Settings
Section 1: General
The General section displays basic application and machine identity information.
| Field | Editable | Description |
|---|---|---|
| Application Name | No | The configured title of the application (read-only display). |
| Camera Type | No | The type of cameras integrated with the system (read-only display). |
| Machine Name | Yes | The name assigned to this machine. Click the pencil icon to edit inline. Press Enter to save or Escape to cancel. |
The Machine Name is the only editable field in this section. It is saved immediately upon confirmation.
Section 2: OPC-UA Connection
This is the most comprehensive section. It manages the connection between Somic Eagle and the PLC via the OPC-UA protocol. It includes live status polling (every 3 seconds) and real-time connection status updates via Server-Sent Events (SSE).
Connection Status
A colored status indicator shows the current state of the OPC-UA connection:
| Status | Color | Meaning |
|---|---|---|
| Connected | Green | The OPC-UA session is active and communicating. |
| Disconnected | Red | The connection to the OPC-UA server has been lost or was never established. |
| Unknown | Grey | The connection state cannot be determined. |
Auto Connect
A toggle switch that enables or disables automatic reconnection to the OPC-UA server on application startup. Changes are saved immediately when the toggle is switched.
Server Address
The URL or IP address of the OPC-UA server. This field is editable inline.
Important: Changing the Server Address will trigger a confirmation dialog warning that the current OPC-UA session will disconnect and fault monitoring will briefly pause during reconnection. You must confirm the change before it is applied.
OPC-UA Profiles
A composite row that shows the currently active profile name along with a summary of its Namespace Index, Identifier, and Fault Tag. Two controls are available:
- Profile dropdown — Quickly switch between available profiles.
- “Profiles” button — Opens the full OPC-UA Profiles management dialog (see OPC-UA Profiles Dialog below).
Tag Configuration Fields
The following fields define the OPC-UA node identifiers used by Somic Eagle to read fault data from the PLC. All fields are editable inline. Any change to these fields triggers a confirmation dialog before being applied.
| Field | Description |
|---|---|
| Namespace Index | The OPC-UA namespace index for the PLC. Common values: 2 for Schneider, 4 for Codesys, 6 for Rockwell. |
| Identifier | The OPC-UA node identifier string for the data structure leading to the Eagle App Data on the PLC. |
| Fault Number Tag | Full OPC-UA node ID for the fault number tag. The value of this tag must be unsigned. (e.g. ns=2;s=...uliFaultNumber,ns=2;s=...udiFaultNumber ). |
| Fault Trigger Flag | Full OPC-UA node ID for the boolean flag that signals a new fault (e.g. .xFaultTrigger). |
| Fault Message Tag | Full OPC-UA node ID for the fault message string (e.g. .sFaultMessage). |
| Fault Timestamp Tag | Full OPC-UA node ID for the fault timestamp (e.g. .sTimeStamp). Displayed as a formatted locale date/time. |
| Fault Acknowledgement | Full OPC-UA node ID for the acknowledgement boolean (e.g. .xAck). |
Live value badges: When the OPC-UA connection is active, each tag row displays a small badge showing the current live value read from the server (e.g. Live: 42, Live: true).
Permissions badges: Each tag row also shows a badge indicating the current session’s access level for that node: R (read-only), W (write-only), R/W (read and write), or No access.
Fault Trigger Watch
Displays the current state of the fault watchman process:
- Idle — No fault is currently being processed.
- Busy — A fault trigger is actively being handled.
An X button is available to manually clear and reset the fault trigger. This button is only enabled when the watchman is in the Busy state. The status is polled every 5 seconds.
OPC-UA Profiles Dialog
Opened via the “Profiles” button in the OPC-UA Connection section. This dialog provides full management of OPC-UA connection profiles.
Toolbar Actions
- Export — Downloads all profiles as an
opcua-profiles.jsonfile. - Import — Uploads a previously exported JSON file to restore or transfer profiles.
- Reset — Restores the three built-in standard profiles. This is a destructive action and requires confirmation.
- Add Profile — Opens an inline form to create a new custom profile.
Built-in Standard Profiles
Somic Eagle ships with three pre-configured profiles for common PLC platforms:
| Profile Name | Namespace Index | Identifier |
|---|---|---|
| Schneider | 2 | OPC.G_OPC.stIotData |
| Codesys | 4 | |var|CODESYS Control for Linux SL.OPC.G_OPC.stIoTData |
| Rockwell | 6 | OPC_EagleAppData.stCamera |
Standard profiles cannot be deleted, but custom profiles can be added, edited, and removed freely.
Profile Card Information
Each profile card displays:
- Profile name
- Standard badge (if it is a built-in profile)
- Active badge (if it is the currently selected profile)
- Namespace Index and Identifier
- All configured fault tag node IDs
Profile Actions
| Action | Description |
|---|---|
| Select | Activates the profile. A confirmation dialog is shown before switching, as this will reconnect the OPC-UA session. |
| Edit (pencil icon) | Opens the profile form to modify the profile’s fields. |
| Delete (trash icon) | Permanently removes the profile. Only available for non-standard (custom) profiles. |
Profile Form Fields
Used when adding or editing a profile:
| Field | Placeholder / Example |
|---|---|
| Profile Name | — |
| Namespace Index | 2 |
| Identifier | Device.Identifier |
| Fault Number Tag | ns=2;s=Device.Identifier.uliFaultNumber |
| Fault Trigger Flag | ns=2;s=Device.Identifier.stCamera.xFaultTrigger |
| Fault Acknowledgement | ns=2;s=Device.Identifier.stCamera.xAck |
| Fault Message Tag | ns=2;s=Device.Identifier.stCamera.sFaultMessage |
| Fault Timestamp Tag | ns=2;s=Device.Identifier.stCamera.sTimeStamp |
Section 3: Storage
The Storage section controls how Somic Eagle manages disk space on the IPC.
| Field | Editable | Description |
|---|---|---|
| Used Space | No | Displays the current disk usage in a human-readable format (e.g. 1.2 GB). |
| Auto Clean | Yes (toggle) | When enabled, Somic Eagle automatically removes old fault records and their associated media files as storage approaches capacity. |
| Clean button | — | Manually triggers a full cleanup of all recorded fault videos and data. |
When enabled, the system automatically removes old recordings to free up storage space. Any fault recordings older than 2 months — including their videos and preview images — are permanently deleted. This runs automatically in the background every 24 hours.
Section 4: FTP Connection
Configures the primary FTP server used by the event cameras to upload video footage. These credentials must match the FTP server running on the IPC.
Note: FTP Connection is only supported for SICK EVC 625 cameras and will be deprecated in a future release.
| Field | Editable | Description |
|---|---|---|
| Server Address | Yes | The hostname or IP address of the FTP server. |
| Username | Yes | The FTP login username. |
| Password | Yes | The FTP password. Displayed as masked characters (•••••) for security. |
All three fields are editable inline and saved individually.
Section 5: Backup FTP Connection
Configures a secondary FTP server used for exporting fault data as a backup. The FTP server is usually on the customer network that is connected to the Machine.
| Field | Editable | Description |
|---|---|---|
| Server Address | Yes | The hostname or IP address of the backup FTP server. |
| Server Port | Yes | The port number for the connection. Default: 21. |
| Username | Yes | The backup FTP login username. |
| Password | Yes | The backup FTP password. Displayed as masked characters (•••••). |
| Protocol | Yes (dropdown) | Select either FTP or FTPS (FTP over TLS). |
All fields are editable inline and saved individually.
Test Connection
The “Test connection” button sends a live connection test to the configured backup FTP server (with a 20-second timeout). The result is displayed inline directly below the button:
- Green message — Connection successful.
- Red message — Connection failed. Check the server address, port, credentials, and protocol.
Section 6: Camera Triggers
Controls the trigger mechanisms that Somic Eagle uses to initiate camera recordings when a fault is detected.
| Field | Editable | Description |
|---|---|---|
| Enable TCP Trigger | Yes (toggle) | Enables or disables the TCP-based camera trigger mechanism. |
| Enable Auth-free Trigger | Yes (toggle) | Enables or disables unauthenticated trigger access. When enabled, triggers can be sent without authentication credentials. |
Both toggles are saved together. A spinner is displayed while the save is in progress.
Section 7: Cameras
The Cameras section is used to manage all event cameras connected to Somic Eagle. Each configured camera appears as a card, and new cameras can be added at any time.
Global Actions
- “Check cameras now” — Runs a configuration check on all cameras simultaneously. Results appear inline on each camera card:
- OK (green) — The camera configuration matches the expected values.
- Needs config: [list of differences] (yellow) — One or more configuration values differ from what is expected.
Camera Card Information
Each camera card displays:
| Field | Description |
|---|---|
| Name | The full name of the camera. |
| Short Name | The abbreviated name (max 5 characters). |
| Serial Number (S/N) | The unique serial number of the physical camera. |
| IP Address | The network address of the camera. |
| Username | The user account used to access the camera. |
| Error Codes | The list of fault/error codes associated with this camera. |
| Firmware status | Shown after a firmware check is performed (see below). |
Per-Camera Actions
| Button | Description |
|---|---|
| Edit (pencil icon) | Opens the camera edit dialog to modify the camera’s configuration. |
| Firmware | Checks the firmware version of the camera. The result is shown as colored text: green (up to date), yellow (outdated), or red (error). |
| Auto Config | Runs automatic camera configuration. A toast notification confirms success, skipped, or failure. |
| Delete (trash icon) | Opens a confirmation dialog to permanently remove the camera from Somic Eagle. |
Adding a Camera
Click the “Add camera” button at the bottom of the section to open the camera add dialog.
Camera Add / Edit Dialog
| Field | Required | Notes |
|---|---|---|
| Serial Number | Yes | Must match the physical camera’s serial number exactly (e.g. 25080988). This field is read-only when editing an existing camera. |
| Name | Yes | A descriptive name for the camera (e.g. Front camera). |
| Short Name | Yes | An abbreviated label, maximum 5 characters (e.g. FRONT). |
| IP Address | No | The network IP address of the camera (e.g. 192.168.1.21). |
| User | No | The access level for the camera. Options: Run, Operator, Maintenance, Service, AuthorizedClient. |
| Password | No | The password for the selected user account. |
| Error Codes | No | Add error codes one at a time by typing and pressing Enter or clicking the + button. Each code appears as a removable chip. Leading zeros are stripped automatically. |
Note: The serial number of the camera must be entered correctly. An incorrect serial number will prevent Somic Eagle from associating video footage with the right camera.