-
Notifications
You must be signed in to change notification settings - Fork 964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor paxcounter #3351
Refactor paxcounter #3351
Conversation
@@ -31,9 +49,12 @@ bool PaxcounterModule::sendInfo(NodeNum dest) | |||
meshtastic_MeshPacket *p = allocDataProtobuf(pl); | |||
p->to = dest; | |||
p->decoded.want_response = false; | |||
p->priority = meshtastic_MeshPacket_Priority_MIN; | |||
p->priority = meshtastic_MeshPacket_Priority_DEFAULT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please leave this as min, regular message traffic should have priority.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, no problem.
Just a question: When would BACKGROUND be appropriate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty well explained in https://github.com/meshtastic/protobufs/blob/00332412b238fe559175a6e83fdf8d31fa5e209a/meshtastic/mesh.proto#L819-L878 ... I think BACKGROUND may be more appropriate than MIN here, and in other places that use it. (Telemetry and so on...) For now i'd stick to min cause the other plugins use min too. Let's address this in a different PR.
7a9a1cf
to
d1b6cc4
Compare
…late (count mode != 1); use flag to signal changed count data
d1b6cc4
to
26691c0
Compare
Implements #3342 (using timesliced count, not yet configurable)