removing physical layer section from spec #95
Merged
Conversation
This file contains 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
As discussed on the dev call, the physical layer specification for CAN transports is significantly less mature than the rest of this specification and is also the most difficult layer to standardize in generic terms. Proper functioning of the CAN data-link layer requires properly designed electrical busses with properties specific to the physical dimensions of a vehicle, the topology of the network, the number of transceivers connected to the network, the location of the transceivers in relation to each other, and the electrical properties of each transceiver. As high data-rate variants like CAN-FD 1/5Mbs are deployed this electrical engineering will become even more important even for very small CAN busses. Because of this we are removing the physical layer specification from the core document but reserve the right to create sibling documents that standardize physical UAVCAN networks based on vehicle morphology and supported transports.
pavel-kirienko
approved these changes
Aug 25, 2020
There was a problem hiding this comment.
Four weeks with no objections. I think this is safe to merge.
This PR invalidates #81
pavel-kirienko
added a commit
that referenced
this pull request
Sep 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As discussed on the dev call, the physical layer specification for CAN
transports is significantly less mature than the rest of this specification and is
also the most difficult layer to standardize in generic terms. Proper
functioning of the CAN data-link layer requires properly designed
electrical busses with properties specific to the physical
dimensions of a vehicle, the topology of the network, the number of transceivers connected
to the network, the location of the transceivers in relation to each other,
and the electrical properties of each transceiver. As high data-rate
variants like CAN-FD 1/5Mbs are deployed this electrical engineering
will become even more important even for very small CAN busses.
Because of this we are removing the physical layer specification from
the core document but reserve the right to create sibling documents
that standardize physical UAVCAN networks based on vehicle morphology
and supported transports.