Logo
Documentation TempApp

TempApp Documentation

18 min read

TempApp is a desktop application designed for monitoring, configuration, device communication, and engineering workflows.

This document covers installation, first launch, interface structure, device connection, configuration, monitoring, data handling, diagnostics, troubleshooting, updates, and support.

1. Overview

TempApp provides a unified interface for interacting with connected devices and monitoring system information.

Typical use cases include:

  • Device monitoring
  • Sensor data visualization
  • Device configuration
  • Network communication
  • Serial communication
  • Runtime diagnostics
  • Application logging
  • Data collection
  • Engineering test environments

The exact functions available may depend on the application version and connected hardware.

2. System Requirements

Before installing TempApp, verify that the target system meets the required environment.

ItemRequirement
Operating SystemWindows 10/11 or Linux
Architecturex86_64 / ARM64
Display1280x720 or higher recommended
Storage200 MB or more
NetworkRequired for TCP/IP devices
USBRequired when using USB devices
SerialRequired when using serial devices

Some hardware interfaces may require additional operating-system permissions.

3. Download

The latest build is available from the CloudEOM Downloads page.

Download TempApp

Select the package matching the target platform.

Example packages:

TempApp-v0.1.0-windows-x64.exe
TempApp-v0.1.0-linux-x86_64.AppImage
TempApp-v0.1.0-linux-arm64.AppImage

Before installing a package, verify that the operating system and CPU architecture match the selected build.

4. Installation

Windows

Download the Windows installer.

TempApp-v0.1.0-windows-x64.exe

Run the installer and follow the installation steps.

After installation, launch TempApp from the Start menu or application shortcut.

Linux

Download the appropriate AppImage package.

Example:

TempApp-v0.1.0-linux-x86_64.AppImage

Set executable permission:

chmod +x TempApp-v0.1.0-linux-x86_64.AppImage

Run the application:

./TempApp-v0.1.0-linux-x86_64.AppImage

For ARM64 systems:

chmod +x TempApp-v0.1.0-linux-arm64.AppImage
./TempApp-v0.1.0-linux-arm64.AppImage

5. First Launch

When TempApp starts, the application initializes its runtime environment and loads the current configuration.

A typical startup sequence is:

  1. Start TempApp
  2. Load application configuration
  3. Initialize communication interfaces
  4. Load device settings
  5. Display the main interface
  6. Wait for device connection

Example status:

APPLICATION READY
DEVICE DISCONNECTED

After a successful connection:

APPLICATION READY
DEVICE CONNECTED

If the application cannot load correctly, check the application log and configuration files.

6. Main Interface

The TempApp interface is divided into several functional areas.

Typical sections include:

  • Main navigation
  • Device status
  • Monitoring values
  • Graphs
  • Configuration
  • Logs
  • Connection controls
  • Application status

The navigation area provides access to the major functions of the application.

Example:

Dashboard
Devices
Monitoring
History
Configuration
Logs
About

The actual menu may vary depending on the application version.

Status Indicator

The current communication state should always be checked before starting an operation.

StateDescription
DISCONNECTEDNo active device connection
CONNECTINGConnection attempt in progress
CONNECTEDDevice communication established
WARNINGCommunication or device warning
ERRORCommunication or runtime failure

7. Device Connection

TempApp may communicate with devices using one or more interfaces.

Possible interfaces include:

  • TCP/IP
  • Serial
  • USB
  • Modbus
  • SCPI
  • Custom protocols

The supported interfaces depend on the target application and hardware.

8. TCP/IP Configuration

For a network-connected device, configure the host address and port.

Example:

Host: 192.168.0.100
Port: 8080
Timeout: 3000 ms

Before connecting, verify network connectivity:

ping 192.168.0.100

If TCP communication fails, verify:

  1. Device power
  2. Ethernet connection
  3. IP address
  4. Port number
  5. Firewall settings
  6. Network routing
  7. Device server status

9. Serial Configuration

For serial devices, configure the serial communication parameters.

Example:

Port: /dev/ttyUSB0
Baud Rate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1

On Windows, typical ports are:

COM3
COM4
COM5

On Linux:

/dev/ttyUSB0
/dev/ttyACM0

Check available serial devices:

ls -l /dev/ttyUSB*

or:

ls -l /dev/ttyACM*

10. Device Configuration

After selecting a device, configure the parameters required by that device.

SettingDescription
DeviceTarget device
InterfaceCommunication interface
HostNetwork address
PortTCP/UDP service port
Serial PortOperating-system serial device
Baud RateSerial communication speed
TimeoutCommunication timeout
SamplingMonitoring update interval

Configuration changes may require reconnecting the device.

11. Monitoring

When a device is connected, TempApp can display live system values.

Possible values include:

  • Temperature
  • Voltage
  • Current
  • Pressure
  • Flow
  • RPM
  • Sensor state
  • Device state
  • Communication state
  • Alarm state

Values are updated according to the configured sampling interval.

Example:

Sampling Interval: 1000 ms

A shorter interval provides faster updates but may increase communication and CPU load.

12. Graphs

Time-series values may be displayed using graphs.

Typical graph functions include:

  • Real-time plotting
  • Multiple data series
  • Time-range selection
  • Zoom
  • Value inspection
  • Historical data display

Graphs should only be considered valid when the device connection and data acquisition state are normal.

13. Data Recording

TempApp may record acquired data for later analysis.

Possible storage formats include:

  • CSV
  • Local database
  • Remote database
  • Time-series database

Typical recorded information may include:

timestamp
device
sensor
value
unit
status

Example:

2026-08-08T13:30:12Z,temp01,temperature,32.4,C,NORMAL

14. Logging

Application logs are useful for diagnosing runtime and communication problems.

Typical log levels include:

TRACE
DEBUG
INFO
WARN
ERROR

Example:

2026-08-08 21:30:11 INFO  Application started
2026-08-08 21:30:13 INFO  Loading configuration
2026-08-08 21:30:14 INFO  Connecting to device
2026-08-08 21:30:14 INFO  Device connected
2026-08-08 21:31:02 WARN  Communication timeout

When reporting a problem, include the relevant log section whenever possible.

15. Configuration Files

TempApp may store configuration locally.

Configuration data can include:

  • Device settings
  • Network settings
  • UI settings
  • Sampling intervals
  • Logging configuration
  • Database configuration

Do not manually modify configuration files while the application is running unless specifically documented.

If configuration becomes invalid, restore the default configuration or remove the invalid configuration file before restarting the application.

16. Normal Operating Procedure

A typical operating sequence is:

  1. Start TempApp
  2. Verify application status
  3. Select the target device
  4. Confirm communication settings
  5. Connect the device
  6. Verify live data
  7. Start the required operation
  8. Monitor status and alarms
  9. Stop the operation
  10. Disconnect the device
  11. Close TempApp

Avoid changing communication settings while an active control operation is running.

17. Troubleshooting

Application Does Not Start

Check:

  • Supported operating system
  • CPU architecture
  • File permissions
  • Required dependencies
  • Application log

On Linux:

chmod +x TempApp*.AppImage

Device Not Detected

Check:

  • Physical connection
  • Device power
  • USB connection
  • Serial port
  • Network connection
  • Driver availability

TCP Connection Failed

Verify:

ping 192.168.0.100

Check that the configured TCP port is correct.

Example:

192.168.0.100:8080

Serial Permission Denied

Check device ownership:

ls -l /dev/ttyUSB0

The current user may require permission to access the serial device.

Data Is Not Updating

Verify:

  • Device state
  • Connection state
  • Sampling interval
  • Communication logs
  • Device response
  • Application errors

A CONNECTED state does not always mean that valid measurement data is being returned.

Application Becomes Slow

Check:

  • Sampling interval
  • Number of monitored channels
  • Graph history length
  • Logging level
  • CPU usage
  • Memory usage
  • Database response time

High-frequency logging and graph rendering may increase system load.

18. Updating TempApp

Before updating:

  1. Stop active operations
  2. Disconnect devices
  3. Close TempApp
  4. Back up configuration if required

Download the latest release:

CloudEOM Downloads

Review version changes before updating.

A new application version may introduce configuration or compatibility changes.

19. Version Information

The current TempApp version is displayed in the application or About page.

Example:

TempApp
Version 0.1.0
Build 2026.08.08

When contacting support, always include the application version.

20. Reporting an Issue

When reporting a problem, provide:

InformationExample
TempApp Version0.1.0
Operating SystemWindows 11 / Linux
Architecturex86_64
DeviceTarget device model
InterfaceTCP / Serial / USB
IP / Port192.168.0.100:8080
Error MessageFull error text
LogsRelevant log section
ReproductionSteps required to reproduce

Screenshots and configuration information may also help diagnose the issue.

Contact CloudEOM Support

21. Security Notes

When TempApp communicates over a network:

  • Use trusted networks whenever possible
  • Do not expose device ports directly to the public internet
  • Restrict access using firewall rules
  • Protect account credentials
  • Keep TempApp updated
  • Verify downloaded packages before installation

Sensitive configuration values should not be included in public bug reports.

22. Backup and Recovery

Before making major configuration changes, back up the current configuration if the application supports it.

Recommended items to preserve include:

  • Device profiles
  • Network settings
  • Database configuration
  • User preferences
  • Application configuration

If the application becomes unusable due to invalid settings, restore the previous configuration and restart TempApp.

23. Uninstallation

Windows

Use the Windows application management interface or the TempApp uninstaller.

Linux

For AppImage distributions, remove the AppImage file.

Example:

rm TempApp-v0.1.0-linux-x86_64.AppImage

Remove additional configuration files only if a complete reset is required.

24. Support

For technical questions, bug reports, installation problems, or device-integration issues, use the CloudEOM support page.

Contact Support

When requesting support, include:

  • Application version
  • Operating system
  • Device model
  • Communication interface
  • Error message
  • Relevant logs