Skip to content
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

Merged
merged 4 commits into from
Mar 10, 2024
Merged

Conversation

thoherr
Copy link
Contributor

@thoherr thoherr commented Mar 8, 2024

Implements #3342 (using timesliced count, not yet configurable)

@thebentern thebentern requested a review from caveman99 March 8, 2024 13:03
@@ -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;
Copy link
Member

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.

Copy link
Contributor Author

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?

Copy link
Member

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.

src/modules/esp32/PaxcounterModule.h Show resolved Hide resolved
src/modules/esp32/PaxcounterModule.cpp Outdated Show resolved Hide resolved
src/modules/esp32/PaxcounterModule.cpp Show resolved Hide resolved
@thoherr thoherr requested a review from caveman99 March 8, 2024 22:53
@caveman99 caveman99 force-pushed the refactor-paxcounter branch from 7a9a1cf to d1b6cc4 Compare March 10, 2024 12:34
@caveman99 caveman99 force-pushed the refactor-paxcounter branch from d1b6cc4 to 26691c0 Compare March 10, 2024 15:08
@caveman99 caveman99 merged commit e33d014 into meshtastic:master Mar 10, 2024
69 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants