Skip to main content
Version: Ver.4.10

Getting Started with Signal Analysis

Feature Overview​

“Signal Analysis” in Analyze Window converts acquired communication logs using signal definitions, letting you compare values, waveforms, alert occurrences, and source frames. Use Signal Window for values during monitoring and Basic Analysis Operations for frame-level searching and combining.

Analysis definitions are handled separately from Signal Window. Editing definitions in the analysis screen alone does not change monitoring settings or transmission data. See Signal Catalog for explanations of signals, Raw/physical values, state names, and Signal Sets.

See Changes in Ver.4.10 for the related screen and workflow updates.

Starting Analysis​

1. Prepare a Log and Definitions​

If monitoring is running, stop it and open the “Signal Analysis” tab in Analyze Window (① in Figure 1).

Top of analysis screen with Signal Analysis tab, Source: Monitor buffer, and Open Log outlined in red and numbered

Figure 1. Selecting the log to analyze.

Figure 1 shows an example after stopping monitoring of two channels. Source in ② is Monitor buffer, containing 11,605 records. Use “Open Log” in ③ to switch to a saved log.

  • To examine a saved log, open a communication log CSV from this product using “Open Log.” Do not use arbitrary CSV files created in spreadsheet software or signal analysis CSV exports as input.
  • To examine the most recent monitoring session, stop monitoring, open “Signal Analysis,” and check that “Source: Monitor buffer” appears.
  • To prepare definitions from a DBC, import them using Signal Catalog on the main toolbar, add the required signals to a Set, and assign channels. Prepare the analysis definitions and select the Set in step 2.

If “Open Log” is canceled or loading fails, for example because a limit is exceeded, the previous log and analysis results are retained.

Starting a new monitoring session switches the analysis source back to the monitoring log and clears previous analysis results. Export any results you need before starting.

2. Select the Signal Set for Analysis​

Prepare the analysis definitions

Saved logs use definitions from the analysis Catalog. To use the definitions from the time of capture, open “Signal Catalog” in Signal Analysis and use “Load” to load the MPXSIG saved with the log (for example, run.mpxsig for run.csv).

The first analysis after opening Monitor buffer imports the current shared Current Set. If differences from the definitions or channel assignments at monitoring start are reported, reselect definitions matching the log.

Analysis Signal Catalog with Current Set, Load, In Set, and CH columns outlined in red and numbered

Figure 2. Items to check in the analysis Catalog.

① in Figure 2 is the Current Set. To use a saved MPXSIG, load it with “Load” in ②, then check signal membership and assignments to log channels using “In Set” and “CH” in ③. In this example, signals with ID 0x310 are assigned to CH1-1 and signals with ID 0x330 to CH1-2.

If a definition selection screen appears, choose one of the following.

OperationDefinitions used
Use current Signal SetImports the shared Current Set with its saved channel assignments for analysis. Check correspondence with log channels.
Load Signal SetLoads a saved MPXSIG for analysis. Select the version and Set matching the log.
CancelCancels definition selection.

Compare channel assignments in the analysis definitions with CH, Protocol, ID, Direction, and data length in the log. If derived signals are included, also check their inputs and formulas.

Select the Set for the next analysis

When “Open Log” displays “Log Analyze,” check the Set name and “Matched signals.” To choose another Set or update the definitions, close “Log Analyze” with the × in the upper-right corner or press Esc. The log stays selected.

With monitoring and analysis stopped, prepare the definitions if needed and choose the Set from “Signal Set” at the top of Signal Analysis. Click “Analyze” in the same toolbar to run the analysis.

If you select another Set after analysis completes, “Signal Set” switches to the Set for the next run while the waveforms and Values still show the previous results. The selector is labeled “Signal Set (next analysis):”. “Export CSV” is disabled while reanalysis is pending. Click “Analyze” and confirm that the new results contain samples to export.

Figures 3–5 show analysis of the saved communication log FD2FanDemo_1-1.csv, switching from Fan Demo - CAN FD to Fan Demo - CAN FD RPM. This saved-log example differs from the Monitor buffer and 2-channel examples elsewhere on this page.

  1. Complete analysis with Fan Demo - CAN FD and open the Signal Set selector (Figure 3). The existing results show four graph areas for RPM, current/load, phase/fault, and temperature/time.
Fan Demo - CAN FD analyzed results with four graph areas and the selector offering Fan Demo - CAN FD RPM

Figure 3. Choose the Set for the next analysis.

  1. Select Fan Demo - CAN FD RPM. Figure 4 still shows the previous four-area results and Values, while the selector identifies the next analysis Set. Export CSV is disabled. A changed selector alone does not mean that the displayed results have been updated.
Fan Demo - CAN FD RPM selected for next analysis while old four-area results and Values remain and Export CSV is disabled

Figure 4. Previous results remain while reanalysis is pending.

  1. Run Analyze. Figure 5 shows the completed RPM Set results: only Target_RPM_demo and Simulated_RPM_demo, with one graph area. Export CSV is enabled again. At the displayed cursor around 25.165 s, Values shows 2351 rpm / 092F and 2522 rpm / 09DA, respectively. These are held values at the cursor; compare exact sample timestamps using Frame Log.
Completed Fan Demo - CAN FD RPM analysis with two RPM signals in one graph area, Values 2351 and 2522 rpm, and Export CSV enabled

Figure 5. Check the RPM Set results after reanalysis.

3. Run Analysis​

In Log Analyze, shown when a log is opened, check the file name, frame count, duration, Signal Set, and Matched signals, then click Analyze.

Ver.4.10 Log Analyze for FD2FanDemo_1-1.csv: 8305 frames, 118.641 seconds, Fan Demo - CAN FD RPM, 2 matched signals

Figure 6. Analysis confirmation when opening a saved log.

Figure 6 uses the same FD2FanDemo_1-1.csv as the Set-switching example: 8,305 frames over 118.641 s, Signal Set Fan Demo - CAN FD RPM, and 2 Matched signals.

If a log is already selected, click “Analyze” at the top of Signal Analysis (① in Figure 7).

Analyze button at the top of Signal Analysis for an already selected log, outlined in red and numbered

Figure 7. Starting analysis for the selected log.

If Matched signals is 0, open the analysis definitions with “Open Signal Catalog” and review Set membership, channel assignments, and frame conditions. If the log contains no frames, select another log.

4. Compare Values with Source Frames​

After analysis, select the signal and time of interest and compare Values, the graph, and Frame Log data.

Analysis results with CH1/CH2 waveforms, C marker 24.964 seconds, Simulated_RPM_demo 1296 rpm and 0510, and corresponding source frame in Frame Log outlined in red and numbered

Figure 8. Comparing waveforms, values, and source frames.

  1. Select the time of interest on the graph. The C marker in ① in Figure 8 shows 24.964 s.
  2. Select the signal of interest in Values. In ②, Simulated_RPM_demo is 1296 rpm and Data(Hex) is 0510.
  3. Check “Signal source frame” in ③ and the source frame row in Frame Log. The example source row has CH1-1, ID 310, Direction Rx, Length 16, and data 7B 05 10 05 ….

Screen Layout and Checking Waveforms describes each region and marker operations.

5. Rerun Analysis After Changing Conditions​

Make analysis-specific changes using “Signal Catalog” within Signal Analysis (① in Figure 9).

Signal Catalog button within Signal Analysis for analysis definitions outlined in red and numbered

Figure 9. Entry point for the analysis Catalog.

  1. To change definitions used for analysis, wait until monitoring and analysis have stopped, then open “Signal Catalog” within Signal Analysis. Edit the target Set, channels, and signal conditions. To switch to a matching MPXSIG, use “Load” in this Catalog.
  2. Confirm individual edits and close. If completed results exist, the previous results are retained and new definitions are treated as candidates for the next analysis.
  3. Check the pending-analysis indication and click “Analyze” again. Compare Values, waveforms, and Frame Log in the new results before exporting. Before changing logs or Sets, record results or annotations you need to retain and follow the on-screen confirmations.

See Select the Signal Set for Analysis to identify the next Set while the previous results are displayed.

“Signal Catalog” on the main toolbar opens the shared definitions also used for monitoring/transmission. The shared Catalog is read-only during monitoring or analysis. Once analysis is complete and monitoring is stopped, you can edit shared definitions while retaining results. Use the entry point within the analysis screen described above for analysis-specific changes. Definitions edited/applied for analysis are not automatically reflected in monitoring or existing transmission settings. After closing the analysis Catalog and before resuming monitoring, check the enabled state and target signals of start/stop conditions in Trigger Window.

If Analysis Is Unavailable​

SituationWhat to check
Analyze cannot be selectedCheck that monitoring is stopped, a log is selected, definitions are ready, and no processing is in progress.
Matched signals is 0Check Set membership and the log's CH, Protocol, ID, Direction, and data length.
Signal values are missing or invalidCheck signal bit ranges, conversions, valid ranges, multiplexing conditions, and derived signal inputs. Do not interpret values before reception as zero.
Only waveforms are missingCheck Graph targets and Graph/Area assignments. Distinguish value analysis targets from waveform display targets.
Loading limit exceededUp to 5,000,000 frames across all channels can be analyzed. A CSV opened with “Open Log” must be no larger than 400 MB (400,000,000 bytes) and contain no more than 5,000,000 data rows across all channels, excluding the header. Split or reduce logs exceeding these limits and reopen them.

Playback within the analysis screen moves the displayed time through analysis results. Its purpose differs from Log Replay, which actually transmits onto the bus. To retain results, see Recording and Exporting Results.