docs: roadmap — future LIN bus simulator planning - #46
Merged
Conversation
Capture a concrete, phased plan for a LIN bus simulator: independent per-slave goroutines with pluggable/faultable response behavior (wrong checksum, wrong PID, silent slave), multi-slave conflict detection, and a stretch-goal cross-process transport (Unix domain socket) that would double as a mechanism for go-LIN/cpp-LIN/rust-LIN interop testing — mirroring what vcan+can-utils gives go-CAN and CycloneDDS gives the DDS family, neither of which LIN has an equivalent for today. Grounded in the current codebase: virtual.Bus is a single shared map with no fault-injection path, slave.Node has no independent behavior, and master.Node already has a real schedule-table engine that a simulator transport can reuse unmodified. Signed-off-by: Matt Jones <47545907+SoundMatt@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
virtual.Busis a single shared map (no fault-injection path),slave.Nodehas no independent per-slave behavior, andmaster.Node.Runalready implements a real schedule-table engine that a future simulator transport could reuse unmodified.master.Node, (2) fault injection (wrong checksum, wrong PID, silent slave, injected delay) via a decorator pattern mirroring go-DDS'sFaultPublisher, (3) multi-slave conflict detection incl. LDF cross-validation, (4) stretch-goal cross-process transport (Unix domain socket) that would double as a go-LIN/cpp-LIN/rust-LIN interop-testing mechanism — explicitly not a prerequisite for the simulator's core dev/test value.Test plan
gh pr checksrun to confirm CI is green.