Update multipacket send to have a que #100
Open
Conversation
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
Added multipacket send que, if multipacket send is busy, message qill go to que and will be processed when next possible. If same message arrvies when in que values will be updated.
kellergoech
changed the title
Only make an log entry if sending of message is not possible and dont crash the application. (automatically works again when CAN sending is working again)
use pgn.value instead of pgn for send buffer index
Author
|
can this please be merged? |
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.
Added multipacket send que, if multipacket send is busy, message will go to que and will be processed when next possible. If same message arrvies when in que values will be updated.
Also only set logging error when sending not possible, when other can partner reconnects automatically continues to send.
fixes #76