Fix WPILib 2026 protocol compatibility #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes crashes when using QDriverStation with WPILib 2026 simulation.
Problem
When connecting QDriverStation to WPILib 2026's simulation, the robot code would crash with a SIGSEGV in
DecodeUDPdue to protocol encoding mismatches.Root Cause
Two issues in the joystick packet encoding:
Joystick size calculation bug:
get_joystick_size()was including the length byte itself in the count. WPILib expects the length byte to represent the size of data after the length byte.Button encoding bug: The code always sent 2 bytes for button data, but WPILib expects
(numButtons + 7) / 8bytes (variable length based on button count).Changes
get_joystick_size()to correctly calculate joystick data size (excluding length byte)get_button_bytes()helper function for proper button byte count calculationTesting
Tested with:
Robot simulation now runs stably without crashes when QDriverStation connects.
Test plan
🤖 Generated with Claude Code