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

python: add QueueStatus support #386

Merged

Conversation

pavelb-techspark
Copy link
Contributor

This makes Python API parse QueueStatus packages returned by the firmware allowing for TX Queue status control from the phone or PC. This makes it easier to not overwhelm device with packages that are going to be ignored anyways.

Fixes meshtastic/firmware#1819

Signed-off-by: Pavel Boldin pavel.b@techspark.engineering

@pavelb-techspark
Copy link
Contributor Author

Sorry about that. I will test these today and update the commit after that.

@pavelb-techspark
Copy link
Contributor Author

I did some testing on this, using ping -f -c 100, out of 100 packets destination node receives ~85 echo requests, with ~70 echo replies successfully received. Most likely this is due to overlapping in time between receiving and sending ends.

On average ping takes ~3 seconds for round trip, given that the queue is empty.
Time difference between last packet sent and last packet received from the source:

22:54:28.030570 IP 10.0.105.76 > 10.0.105.88: ICMP echo request, id 77, seq 100, length 64
22:57:06.419293 IP 10.0.105.88 > 10.0.105.76: ICMP echo reply, id 77, seq 100, length 64

Same packet on the destination:

22:57:02.296597 IP 10.0.105.76 > 10.0.105.88: ICMP echo request, id 77, seq 100, length 64
22:57:02.296621 IP 10.0.105.88 > 10.0.105.76: ICMP echo reply, id 77, seq 100, length 64

This makes Python API parse QueueStatus packages returned by
the firmware allowing for TX Queue status control from the phone
or PC. This makes it easier to not overwhelm device with packages
that are going to be ignored anyways.

Signed-off-by: Pavel Boldin <pavel.b@techspark.engineering>
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.

when outgoing TX Queue is full messages are simple dropped without notification
2 participants