add a RELIABLE priority

This commit is contained in:
Kevin Hester 2021-02-12 09:39:35 +08:00
parent 0221e83d68
commit b1aed06442
2 changed files with 6 additions and 2 deletions

View file

@ -727,7 +727,8 @@ connected directly to the node) can set this parameter if necessary.
| UNSET | 0 | Treated as Priority.DEFAULT |
| MIN | 1 | |
| BACKGROUND | 10 | Background position updates are sent with very low priority - if the link is super conjested they might not go out at all |
| DEFAULT | 64 | This priority is used for all messages that don't have a priority set |
| DEFAULT | 64 | This priority is used for most messages that don't have a priority set |
| RELIABLE | 70 | If priority is unset but the message is marked as want_ack, assume it is important and use a slightly higher priority |
| ACK | 120 | Ack/naks are sent with very high priority to ensure that retransmission stops as soon as possible |
| MAX | 127 | |

View file

@ -274,9 +274,12 @@ message MeshPacket {
/* Background position updates are sent with very low priority - if the link is super conjested they might not go out at all */
BACKGROUND = 10;
/* This priority is used for all messages that don't have a priority set */
/* This priority is used for most messages that don't have a priority set */
DEFAULT = 64;
/* If priority is unset but the message is marked as want_ack, assume it is important and use a slightly higher priority */
RELIABLE = 70;
/* Ack/naks are sent with very high priority to ensure that retransmission stops as soon as possible */
ACK = 120;