The Systems area in SDX-Cloud is the central place to manage and monitor your registered systems. From here, you can open a system’s detail view to check its current status, configure correction services, manage machine profiles, view quick tasks, and inspect system logs.
Systems list
The Systems list shows all systems in your organization in a searchable, sortable table. Typical columns include: Name, Serial number, Type, License, Description, Correction service, UHF, and Actions.
- Search helps you quickly find a specific system by name or serial number.
- Columns lets you control which columns are visible.
- Actions opens the detail view of the selected system.
System detail view
When you open a system, the detail view provides several tabs: System logs, Machine profiles, Quick tasks, and Settings. Use these tabs to troubleshoot issues, configure the system, and keep track of work items.
Settings
The Settings tab contains the system’s configuration and key information at a glance:
- System status: shows status indicators (e.g., online/offline, scanning state, sensors/camera/GPS). Depending on connectivity and system state, the status area may show warnings such as “No position data”.
- Edit system: basic fields like Name and Description.
- Default correction service: NTRIP connection fields (Ntrip-Server, Ntrip-Port, Ntrip-Mountpoint, Username, Password) and a Check validity button to validate the configuration.
- License: displays your license type and enabled features (for example, photo mode, project grid size).
- Remaining data for scans: shows mobile data usage and an option like Allow mobile data overconsumption (if available for your license/role).
Incorrect NTRIP settings can lead to missing/unstable RTK fixes and reduced positioning accuracy. If you are unsure which NTRIP values to use, confirm the correct server and mountpoint with your correction service provider.
Machine profiles
Machine profiles define how the system is mounted and oriented on different machine types (e.g., dozer, wheel loader, excavator). These profiles help ensure the system’s heading and scanning behavior match the machine configuration.
- Machine type: the machine category the profile represents (e.g., Dozer, Wheel Loader, Excavator).
- Bearing offset: an angular offset used to align the system’s orientation with the machine’s driving direction or mounting direction. For example, values such as 0° or 180° may be used depending on forward/backward mounting.
- Scan area: configuration related to the scanning area (availability and exact behavior can differ by system type and software version).
You can typically edit profiles (pencil icon), delete profiles (trash icon), or add a new profile (plus tile).
Available fields and profile options can vary depending on your system type and SDX-Framework version.
Quick tasks
The Quick tasks tab provides a lightweight Kanban-style board for system-related tasks. Tasks are typically organized into Open, In progress, and Closed.
- Use quick tasks to track follow-ups (e.g., “Check NTRIP credentials”, “Verify sensor power”, “Review logs for upload issue”).
- Create a new task using the + button.
System logs
The system logs can be found in the system log screen in the systems section in SDX-Cloud. Each system has its own log screen showing the latest logs pushed by the system in real time.
The purpose of this log screen is to quickly check the system’s current state and identify problems.
System logs are only stored for 2 weeks.
General functionality
The log screen consists of 3 sections:
- Filter section (on the left)
- Log section (in the center)
- Log details section (on the right, only active if a user selected a log)
- Each log entry includes a timestamp and a type.
- Logs are color-coded according to their severity.
- If multiple logs of the same type appear consecutively, they are summarized into one entry showing the number of occurrences.
Available log types
In the table below, all currently supported log types are listed and explained.
Note that the latest version of the SDX-Framework might be required to have access to all log types. To find out if your system has the latest version, please refer to the CHANGELOG section of our helpcenter.
| Type | Severity | Description |
|---|---|---|
| system_online | INFO | A basic ping sent out by the system every 5 minutes indicating the system is online. Also contains the current version of the SDX-Framework. |
| system_started | INFO | A one time ping sent once the SDX-Framework has started. |
| simple_debug | DEBUG | A simple unspecified debug log containing a message. |
| simple_info | INFO | A simple unspecified info log containing a message. |
| simple_warning | WARNING | A simple unspecified warning log containing a message. |
| simple_error | ERROR | A simple unspecified error log containing a message. |
| simple_critical | CRITICAL | A simple unspecified critical log containing a message. |
| sensor_pwr_on | INFO | Triggered if either the user or the autostart turns on the sensor power of the system. |
| sensor_pwr_off | INFO | Triggered if either the user or the autostart turns off the sensor power of the system. |
| project_loaded | INFO | Triggered if a new project is loaded. The ID and name of the Project is also displayed in SDX-Cloud. |
| autostart_overwritten | INFO | Triggered if the autostart functionality is overwritten by the user using SDX-Mate. |
| creating_snapshot | INFO | Triggered if the SDX-Framework is creating a new snapshot. |
| snapshot_part_uploaded | INFO | Triggered if the SDX-Framework successfully uploaded a new part of a new snapshot to SDX-Cloud. Also displays the part number which has been uploaded and the total number of parts for that snapshot. |
| snapshot_started_processing | INFO |
Triggered if the snapshot is fully uploaded and processing
starts on our servers. Note: the snapshot is not yet displayed and available in SDX-Cloud. |
| snapshot_finished_processing | INFO | Triggered if the snapshot finished processing and is available in SDX-Cloud. |
| creating_ref_img | INFO | Triggered if a new reference image is created in the SDX-Framework. |
| reference_image_uploaded | INFO | Triggered if a captured reference image got uploaded successfully and is available in SDX-Cloud. |
| sdx_mate_note_uploaded | INFO | Triggered if a manually captured SDX-Mate note got successfully uploaded and is available in SDX-Cloud. |
| high_res_layer_loaded | INFO | Triggered if a new high res layer is loaded via SDX-Mate. The layer ID is displayed in SDX-Cloud. |
| high_res_layer_unloaded | INFO | Triggered if a currently loaded high res layer is unloaded using SDX-Mate. |
| high_res_scan_started | INFO | Triggered if capturing for an active high res layer is started. |
| high_res_scan_stopped | INFO | Triggered if capturing for an active high res layer is stopped. |
| high_res_layer_data_uploaded | INFO | Triggered if data of the captured high-res layer got successfully uploaded. |
| high_res_layer_processing_started | INFO |
Triggered if the layer is fully uploaded and processing starts
on our servers. Note: the layer is not yet displayed and available in SDX-Cloud. |
| high_res_layer_processing_finished | INFO | Triggered if the layer finished processing and is available in SDX-Cloud. |
| photo_mode_layer_loaded | INFO | Triggered if a new photo mode layer is loaded via SDX-Mate. The layer ID is displayed in SDX-Cloud. |
| photo_mode_layer_unloaded | INFO | Triggered if a currently loaded photo mode layer is unloaded using SDX-Mate. |
| photo_mode_capturing_started | INFO | Triggered if capturing for an active photo mode layer is started. |
| photo_mode_capturing_stopped | INFO | Triggered if capturing for an active photo mode layer is stopped. |
| machine_profile_loaded | INFO | Triggered if a new machine profile is loaded. The machine profile ID is displayed in SDX-Cloud. |
| scan_started | INFO | Triggered if 2.5D scanning is started by the user (SDX-Mate) or by the autostart. |
| scan_stopped | INFO | Triggered if 2.5D scanning is stopped by the user (SDX-Mate) or by the autostart. |
| points_scanned_last_minute | DEBUG |
Periodic message pushed every minute containing the number
of points scanned in the last minute. Important: Only pushed if 2.5D scanning is active and the system is inserting data. Not pushed if the system is standing still or does not have an RTK-Fix. |
| camera_set_active | INFO | Triggered if either the user or the autostart sets the cameras to active. |
| camera_set_inactive | INFO | Triggered if either the user or the autostart sets the cameras to inactive. |
| uhf_config | INFO | If a UHF radio is configured and what configuration was applied. |
| ntrip_config | INFO | If NTRIP was configured and what configuration was applied. |
Comments
0 comments
Please sign in to leave a comment.