Skip to content

fix(xls): reset signal_name on frame boundary to prevent first signal…#911

Open
oikawa-yusuke wants to merge 1 commit into
ebroecker:developmentfrom
oikawa-yusuke:fix/xls-signal-skip-on-frame-boundary
Open

fix(xls): reset signal_name on frame boundary to prevent first signal…#911
oikawa-yusuke wants to merge 1 commit into
ebroecker:developmentfrom
oikawa-yusuke:fix/xls-signal-skip-on-frame-boundary

Conversation

@oikawa-yusuke

Copy link
Copy Markdown

Problem

When two consecutive frames share the same signal name at the frame
boundary (e.g. frame A ends with "position" and frame B also starts
with "position"), the duplicate-detection guard

if sh.cell(row_num, index['signalName']).value != signal_name

evaluates to False for the first signal of frame B, causing it to be
silently dropped from the output.

Fix

Reset signal_name to "" whenever a new frame is detected so the
first signal of every frame is always processed correctly.

Reproduction

Define two consecutive messages where the last signal of message A and
the first signal of message B have the same name. The first signal of
message B will be missing from the generated DBC.

… skip

When two consecutive frames share the same signal name as the
transition point (e.g. frame A ends with "position" and frame B
also starts with "position"), the duplicate-detection guard

    if sh.cell(row_num, index['signalName']).value != signal_name

evaluated to False for the first signal of frame B, causing it to
be silently dropped from the output DBC.

Fix: reset signal_name to "" whenever a new frame is detected so
the first signal of every frame is always processed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant