# knxUltimateLogger Node – Tutorial Outline

## 1. Intro (0:00)
- "Welcome! We’re configuring the `knxUltimateLogger` node to capture KNX traffic and generate ETS diagnostic files."
- "We’ll set log intervals, telegram counters, and outputs."

## 2. Inputs & Outputs (0:20)
- Input: KNX telegram stream from `knxUltimate-config` gateway.
- Output 1: ETS diagnostic XML dataset.
- Output 2: Telegram count statistics."

## 3. Core Fields (0:45)
- **Server**: select the KNX gateway providing telegrams.
- **Topic**: optional label for the log stream.
- **Name**: friendly label displaying in the workspace."

## 4. ETS XML Generation (1:05)
- Enable `autoStartTimerCreateETSXML` to start logging automatically after deploy.
- **Interval**: minutes between ETS XML exports.
- **Max Rows**: cap the number of telegrams stored per file (0 = unlimited)."

## 5. Telegram Counter (1:35)
- Separate accordion for counting telegrams.
- Enable `autoStartTimerTelegramCounter` if you want automatic counting.
- **Interval Telegram Count**: seconds (or minutes) between counter reports on output 2."

## 6. Using the Outputs (2:00)
- Output 1: connects to file nodes or email attachments—feeds the ETS XML for diagnostics.
- Output 2: emits an object with telegram totals—ideal for dashboards or alerts when traffic spikes.

## 7. Operational Tips (2:25)
- For long logging sessions, set a `maxRows` limit to prevent huge files.
- Use Node-RED storage nodes to archive ETS XML into dated folders.
- Combine output 2 with `knxUltimateAlerter` to detect unusual activity."

## 8. Demo Ideas (2:50)
- Automatically email the ETS log every 15 minutes during commissioning.
- Display telegram counts on a dashboard to monitor bus health."

## 9. Wrap-Up & CTA (3:10)
- "We connected the logger to the gateway, configured intervals, and explored both outputs."
- "Subscribe and comment with your KNX diagnostic routines!"