Data Logging

YuDash data loggers support periodic data logging to an onboard microSD card. This feature is essential for applications requiring offline storage, regulatory audit trails. The files in the microSD card can be downloaded in laptop or it cane be accessed through YuDash interface.

Data Logger Configuration

1. Enabling Data Logging

To enable the SD card logging feature:

1. Navigate to the LYNX Settings section from the side menu.

2. In the Feature Settings block, check the box labeled Data Logging.

3. Click Write LYNX Config to save the changes.

1. SD Card logging requires both the SD Card and RTC (Real-Time Clock) features to be enabled in the configuration. If either is disabled, the logger will not function. Make sure both checkboxes are selected before setting up the data logger.

2. Data Logging Section

• Navigate to the Data Logger Settings tab from the sidebar.

• Click Read Data Logger Settings to load the current configuration from the device.

• Modify the necessary fields such as:

  • Logging interval

  • File cycle and naming

  • Encoder pattern or custom header

• After making changes, click Update Data Logger Settings to save the configuration to the device.

• There is an option to tick Use Default Settings. When this is enabled, the data logger uses its internal default configuration—ignoring all custom fields like encoder, header, and timestamp format. To apply custom settings, ensure that Use Default Settings is unchecked.

3. File directory and name

In this section, you configure where and how the data logger files will be stored:

1. Logger Directory: Specifies the folder path on the SD card where log files will be created. Points to note:

   1. The path must begin with a forward slash / (root directory).

   2. Use / as the folder separator (like in Unix/Linux), not the Windows-style backslash \.

   3. Do not add a trailing slash at the end of the path. ✅ /logger_dir   ❌ /logger_dir/ or \logger_dir\

   4. The directory will be automatically created if it does not already exist on the SD card.

2. File Name

YuDash provides flexible file naming by allowing a customizable prefix, dynamic timestamp insertion (based on selected cycle), and optional suffix. This makes it easy to:

• Align with existing file naming conventions in your systems

• Simplify automated file parsing or importing on downstream software

• Organize logs by project, device, or department

The file name is constructed using a prefix, the cycle-based timestamp, and a suffix. The suffix is typically .csv, .txt, or any other extension as per your application's needs.

File Name: Define a custom file name using a prefix and suffix. The actual file name is generated dynamically using the selected File Cycle:

file_name = Prefix + Cycle + Suffix.

File Naming Examples for different Cylcles

• Prefix: log_ Suffix: .csv

• File Cycle Options

File Cycle	Description	Example File Name
None	Single file	log_.csv
YYYY	Yearly	log_2025.csv
YYYY_MM	Monthly	log_2025_06.csv
YYYY_MM_DD	Daily	log_2025_04_18.csv
YYYY_MM_DD_HH	Hourly	log_2025_04_15_05.csv
YYYY_MM_DD_HH_NN	Per minute (for testing only)	log_2025_04_15_05_03.csv

4. File content

In this section, you define the format of each line in the log file, including optional header text, timestamp placement, and variable encoding using a flexible text template.

1. Optional File Header

   • A one-time header line is added at the top only when a new file is created (e.g., on a new day or month depending on the file cycle).

   • Useful for column labels or unit information.

   • Can be left blank if not needed.

2. Timestamp Format Selection

   • Select the TimeStamp format from the dropdown. This determines the format that will be used when #TS is inserted into the encoder.

   • You can choose from UTC or Local time formats such as:

     • YYYY-MM-DD HH:MM:SS

     • DD-MM-YYYY HH:MM:SS

     • UNIX_EPOCH

     • ISO 8601

   • For a full list of available timestamp formats and codes (TS_50 to TS_66), refer to the Time Stamp formats.
3. Logger Text Encoder

   • This is a simple, text-based encoder that defines how each line in the log file is written. This is of format TEXT_FORMAT_20 of YuTGT
   • You can use:

     • Single-character separators such as ,, :, |, , etc.

     • Variable names (e.g., bod, tss, cod) as defined in earlier configuration flows. These are replaced with their actual values during logging.

     • Special # tags to insert system-defined fields:

       • #TS → Timestamp (as per the selected format)

       • #NL → New line (typically added at the end of each encoder string to ensure proper row formatting)

       • Other #tags as per YuTGT

   • This flexible approach allows you to generate well-structured .csv or .txt files tailored to any downstream system.

Retrieval of data logger files in laptop/PC

The data files created by the YuDash logger on the SD card can be easily accessed using a laptop or desktop system. Follow the steps below (also illustrated in the image):

1. Remove the SD Card from the Logger

   • Gently push the SD card using a non-metal tool (e.g., plastic tweezer) to release it from the slot on the YuDash device.

2. Insert SD Card into Laptop

   • Use the built-in SD card slot (if available), or a USB card reader as shown in the example.

3. Browse the Logger Directory

   • Once inserted, the SD card appears as a removable drive.

   • Navigate to the configured logger directory (e.g., /loggerDir) to view the generated log files.

4. Open Files in Excel or a Text Editor

   • The files (typically .csv or .txt) can be opened in applications like Microsoft Excel, Notepad, or any spreadsheet/data analysis software for review and further processing.

📎 Tip: Ensure the logging cycle has completed (e.g., file has closed properly) before removing the SD card for reliable file reads.