RC Log Visualizer – User Manual and Online Help

1. Purpose and scope of this manual #

This manual describes the RC Log Visualizer across all program variants. The description is intentionally general so it can be used for every edition of the visualizer. Instead of focusing on individual brand names, it uses neutral terms such as program variant, system-specific telemetry importer, and flight controller/blackbox import.

The RC Log Visualizer is no longer a pure CSV viewer. CSV is only one of several possible input paths. The program combines log import, data checking, charts, animated chart playback, table view, flight replay and aerobatics analysis.

• For new users: an overview of workflow and tabs.
• For testers: clear expectations for what should be visible after each step.
• For advanced users: explanations of project files, replay files, candidates, analysis markers and expert CSV.
• For online help: a basis for searchable and linked documentation.

2. Basic principle of the program #

The program imports telemetry or flight controller data, converts it into a uniform internal table structure and displays it in specialized tabs. Each tab answers a different question.

The tabs follow a practical workflow: import data, check values, play back time or space, then perform special analyses.

3. Data flow and internal building blocks #

The visualizer works with several data levels. This separation explains why a change in the aerobatics analysis does not modify the real flight and why an analysis project contains more information than a CSV file.

4. Important terms #

5. Quick start: from log to analysis #

For normal work, this sequence is usually sufficient:

• In the Imports tab, select the appropriate import function.
• Check whether the import was successful and whether the data are visible in Chart and Table.
• In the Chart tab, select the most important measured values and inspect the curve.
• If required, play back the curves in the Chart Player.
• In Flight Replay, check whether GPS, altitude and replay look plausible.
• For aerobatics or training logs, inspect the full flight in Aerobatics Analysis and search for candidates.
• Save important results as an analysis project.

6. Program structure and importers #

The RC Log Visualizer consists of a shared core and several import paths. Each program variant starts the same basic structure but uses a suitable system-specific importer and appropriate default labels.

6.1 Import paths

6.2 Background processing

• Column names are standardized where known.
• Decimal separators and number formats are normalized.
• Time values are converted into a usable time axis.
• GPS columns are detected and converted into local meter coordinates where possible.
• Altitude, speed, climb/sink and orientation are imported or estimated when enough data exist.
• A flight_replay structure is generated for the replay player.

7. Imports tab #

The Imports tab is the entry point. It loads new log files, opens existing entries from the history or uses special import functions. The goal is not only to read the file, but to prepare it for all following tabs.

7.1 Typical functions

7.2 Expected result after a successful import

• Selectable columns are available in Chart.
• Rows and values are visible in Table.
• For GPS flights, a track is visible in Flight Replay.
• For suitable data, a replay file can be generated or is already present.
• Flight controller data may additionally provide roll/pitch/yaw for aerobatics or 3D views.

7.3 Common import problems

8. Chart tab #

The Chart tab is the main technical measurement view. Values are displayed over an X axis. Usually this is time, but other columns can also be used as X axis if the program variant provides this option.

8.1 Basic operation

• Select Y values: choose the measurements that should be shown as curves.
• Check X axis: usually time; for special analyses other columns may be possible.
• Update chart: rebuild the curves with the current selection.
• Zoom: enlarge a section, for example with the mouse or toolbar.
• Read values: use the mouse position or value display for exact measurements.
• Legend/colors: distinguish curves by legend and colors.

8.2 Own Y axes

Many measurements have very different value ranges. Altitude, voltage, speed and climb rate are difficult to compare on one shared Y scale. Own Y axes create separate scales for individual curves or curve groups.

8.3 Separate chart view

For detailed work, the chart can be opened in a separate window if the program variant provides this function. This is especially useful on small screens or with many curves.

8.4 Expected result

• Selected curves are visible and clearly distinguishable.
• Axes match the displayed measurements.
• When Y values change, old curves and old secondary axes disappear completely.
• Zoom and value display allow detailed inspection of individual flight sections.

9. Chart Player tab #

The Chart Player is an animated chart view. It answers the question of how several measurements change over time. While the normal Chart tab is mostly static, the Chart Player focuses on playback, time cursor and current values.

9.1 Basic functions

9.2 Data transfer

The Chart Player uses the data already present in the chart or imported flight. Depending on program status, either only current chart columns or all available chart data can be transferred. The goal is that the player does not need its own import logic, but uses the same data base.

9.3 Expected result

• During playback, curves move relative to the time cursor or the cursor clearly indicates the current time.
• The value box updates synchronously.
• The time axis is displayed clearly, preferably in minutes or with clear seconds.
• Own Y axes and zero-axis options behave consistently with the normal chart.

10. Table tab #

The table shows imported and calculated values row by row. It is the control view for all automatic detections. If Chart or Replay look unusual, the table should be checked.

10.1 Typical use

• Check whether time columns are filled correctly.
• Check whether GPS, altitude, speed and climb rate contain plausible values.
• Check column names when automatic assignment does not work.
• Detect suspicious values, gaps or wrong units.
• Understand which columns were imported during generic import.

10.2 Expected result

• The table contains at least time and one or more measurement columns.
• For replay-capable flights, GPS or local coordinates exist.
• For aerobatics/FC analyses, roll/pitch/yaw or derivable orientation values are ideally present.

11. Flight Replay tab #

The Flight Replay tab displays the flight spatially. It is the bridge between table/chart data and spatial flight analysis. Depending on the available data, the flight can be displayed in 2D, as exported replay file or in the 3D player.

11.1 2D overview

The 2D view shows the flight path from above or in a map/track view. It is the first plausibility check: start point, flight direction, size and GPS jumps can be spotted quickly.

11.2 3D player

The 3D player uses a replay file with local coordinates, altitude and orientation. It can provide different views such as ground view, follow mode or pilot view. Depending on program status, model selection, HUD, reception values, warnings and terrain/altitude logic may also be available.

11.3 Expected result

• The flight appears at a plausible position and altitude.
• Start and landing are not shown below terrain without reason.
• If GPS data are missing, a clear warning is shown instead of a crash.
• The spatial display broadly matches Chart and Table.

12. Aerobatics Analysis tab #

Aerobatics Analysis is a special analysis for spatial flight assessment, training review and structured post-analysis of figure sections. It supplements Chart, Table and Flight Replay. It is especially useful when a pilot wants to understand a flight not only as measurement curves, but as a spatial sequence with possible figures, box position and correction hints.

12.1 Basic principle

• The raw flight always remains unchanged.
• Candidates are automatic suggestions for noticeable sections.
• Analysis markers are accepted or manually created sections.
• A section can be classified as a figure type without changing the flight path.
• The analysis project stores flight path, markers and candidates together.
• The expert CSV is only for data exchange and does not contain the full analysis.

12.2 Workflow in the tab

12.3 Flight overview and loaded flight

The upper right area „How to use Aerobatics Analysis“ and „Flight overview“ is the entry point. It shows the loaded state and the next useful steps.

• Loaded: shows whether a real replay flight, demo aerobatics or analysis project is active.
• Next step: gives a rough action recommendation.
• Take over current replay flight: transfers the replay data currently available in the main program.
• Load demo aerobatics: loads a synthetic example flight if no real aerobatics log exists.
• Open analysis separately: opens the analysis in a movable and resizable window.

12.4 Detail for the current point

The „Detail for current point“ area shows the data of the selected or played flight point. It is the most important control view for individual values.

• Time: current time and total duration.
• Maneuver/raw: current marker and associated raw section.
• Position, altitude, roll/pitch/yaw, speed and climb show the current flight state.
• Aerobatics box: assessment of position in the training/competition box including correction hint.

12.5 Views for the full overview

The view buttons define the perspective. For first analysis, „3D“ or „Box top 2D“ is usually recommended, then optionally „Judge view 2D“.

• 3D, side, top and front: predefined camera views.
• Flight direction and reset view: quick orientation in confusing flights.
• Judge view 2D: reduces the spatial display to a judge/pilot view in 2D.
• Box top 2D: especially useful for position inside the aerobatics box from above.

12.6 Find and check candidates

The automatic candidate search suggests noticeable sections. It is intentionally cautious. In normal cross-country, thermal or training flights without aerobatics, few or no candidates are expected.

• Search candidates: starts automatic search.
• Delete all: removes all current suggestions.
• Table: shows suggestion, type, time range, quality and percentage.
• Show candidate: highlights the selected candidate.
• Play candidate: plays the selected section.
• Accept: converts the candidate into an analysis marker.
• Reject: removes an unsuitable candidate.
• Accept high-quality candidates: accepts all suggestions with high rating together.

A candidate does not automatically mean that a figure was reliably detected. It is always only a suggestion that should be checked in the plot and during playback.

12.7 Accepted analysis markers

Analysis markers are the actual work results of the aerobatics analysis. Confirmed or manually created sections are managed here.

• Zoom section and play section: check the selected section.
• Start = current point / End = current point: set time limits from the current flight point.
• Name: freely selectable section name.
• Marked as: figure type or classification.
• Start s / End s: exact time limits of the marker.
• Save/update marker: creates a new section or updates the current one.
• Delete: removes the marker from the analysis.

Again: markers change only the analysis, never the flight itself.

12.8 Focus, zoom and display

Display options switch between overview and detailed work. This area is especially useful if the flight path is long or individual figures need detailed inspection.

• Full flight / Current section / Current point / Zoom 1:1: quick focus changes.
• Zoom slider: enlarges or reduces the view.
• Current aircraft symbol, label and orientation marks control additional display elements.
• Competition box: controls box display, 150/175/200 m labels, warning points and pilot hints.
• Replay trace: determines whether only the current section or a preview of the full flight is visible.
• Ground helper line, ground trace/projection and 3D training background/ground help spatial orientation.

12.9 Player and saving/loading

Under „Player“, the playback step per tick is set. Below it is the „Save / Load“ area. For normal users, the analysis project is almost always the relevant option.

• Save analysis project…: saves raw flight, analysis markers and candidates together.
• Load analysis project…: loads a previously saved analysis state.
• Show expert CSV: displays additional CSV functions. These are intended only for data exchange, checking or troubleshooting.

Important note about expert CSV: After clicking „Show expert CSV“, additional buttons open below the hint text. They are not immediately visible if the user does not look or scroll down. When enabled, the buttons „Export CSV…“ and „Import CSV…“ appear. This CSV contains only the flight path table or point data, not the complete analysis with candidates and markers.

12.10 Separate analysis window

Aerobatics Analysis can be opened in a separate window. This window has normal window controls, can be moved and resized and is useful on large monitors or for parallel work with Chart, Table or Flight Replay.

Changes from the separate window can be transferred back into the main window. This allows detailed analysis in a large window and then writing the result back to the main tab.

12.11 Summary for normal users

• Always view the full flight first.
• Then search for candidates.
• Check good candidates individually before accepting them.
• Correct markers manually when needed.
• Save the analysis project at the end.
• Use expert CSV only deliberately for data exchange or troubleshooting.

13. Supported file formats, file types, saving and loading #

The RC Log Visualizer uses several file types. Understanding them is important for the workflow. The old name „CSV Visualizer“ was historically understandable, but too narrow: CSV is only one possible input format.

13.1 Supported input and working formats

13.2 Original log file

The original log file comes from the respective telemetry or flight controller system. It is the raw source and should be kept unchanged.

13.3 flight_replay.json

The replay file is a prepared structure for spatial views and the 3D player. It usually contains time, local coordinates, altitude and orientation.

13.4 Analysis project

The analysis project is the most important working file for Aerobatics Analysis. It stores together:

• the loaded flight path or points used in the tab,
• accepted analysis markers,
• the current candidate list and analysis state.

13.5 General CSV export

General CSV exports are mainly used for exchange with spreadsheet programs or external analysis. They are useful for further processing in Excel, LibreOffice Calc, Python/Pandas or other tools.

13.6 Expert CSV in Aerobatics Analysis

The expert CSV is deliberately not a complete project format. It contains only the flight path table or point data. Candidates, markers and other analysis states are missing. It should therefore not be used as a replacement for the analysis project.

13.7 Recommended practice

• Keep the original log file separately.
• Use flight_replay.json for spatial work where required.
• For aerobatics work, always save/load the analysis project.
• Use CSV only when data should deliberately be exported or imported.

14. Typical workflows #

14.1 Normal telemetry flight

• Import log.
• Open Chart and select important values: altitude, speed, voltage, reception, variometer and similar.
• Zoom suspicious areas in the chart.
• Check Table if values are not plausible.
• Open Flight Replay if GPS exists.
• Use Aerobatics Analysis only when figures or spatial training assessment are relevant.

14.2 Flight controller/blackbox log

• Import or decode the raw log.
• For large files, wait for progress to finish.
• Check in Chart whether time, altitude, speed, roll/pitch/yaw are plausible.
• Check Flight Replay.
• Open Aerobatics Analysis and search candidates.
• Accept candidates only when they look plausible in plot and playback.

14.3 Aerobatics training

• Take over replay flight or load demo aerobatics.
• View full flight in 3D and Box top 2D.
• Search candidates.
• Show and play every candidate.
• Accept good candidates; correct start/end if needed.
• Name markers and classify them as figure types.
• Save the analysis project.

14.4 Test without a real aerobatics log

• Load demo aerobatics.
• Search for candidates.
• Check loop, roll, humpty and turn.
• Test views and competition box.
• Do not confuse the demo with a real evaluation; it is only for function checking.

15. Important settings and displays #

16. Plausibility checks #

Before deeper analysis, check whether the data are plausible. Many apparent program errors are caused by missing or incorrectly detected input data.

17. Troubleshooting and typical questions #

18. Notes for testers #

Testers should not only check whether the program starts, but whether the expected logic of each tab is followed.

• Import: Is the file loaded and is there a status? Are error messages understandable?
• Chart: Are curves, axes and zoom plausible?
• Chart Player: Does the time cursor run synchronously with the values?
• Table: Do columns and values match the log?
• Flight Replay: Are position, altitude and start point roughly correct?
• Aerobatics Analysis: Does the raw flight remain unchanged? Are candidates treated only as suggestions?
• Separate windows: Can they be moved and resized and do they have normal window controls?

19. Online help, search and linking #

For an online version, this manual should be divided into sections with unique anchors. A search field can search headings, body text and keywords. The keyword index should link to the appropriate sections.

• Search field at the top of the page.
• Table of contents with jump links.
• Keyword index with links to relevant sections.
• Keep sections short enough for search results to stay readable.
• Check screenshots and captions after larger interface changes and update them if necessary.

20. Keyword index #

This index is intended for the online version as a linked keyword search. In the PDF version it serves as a reference aid.