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

[Bug]: 2.3.2 instantly maximum transmission duty cycle and high chUtil #3492

Closed
francisuk1989 opened this issue Mar 25, 2024 · 8 comments
Closed
Labels
bug Something isn't working

Comments

@francisuk1989
Copy link

francisuk1989 commented Mar 25, 2024

Category

LoRa - 868MHz

Hardware

Heltec Wireless Tracker v1.1

Firmware Version

2.3.2.63df972 Alpha

Description

Upgraded to 2.3.2 last night with a full wipe and i was sending a message in the default channel and i suddenly got maximum transmission normally i never got this message in the previous builds as im using a standard antenna out the box and only seem to pickup just one node.

So next morning i have tried to send another message again but just got a instant cross over a the cloud, Also my node in the android app is ChUtil 0.0 and AirUtilTX 0 0

I have also tried the option "override due cycles" just to test if anything works but nothing.

Edit
I have factory reset the node again and Setup my Name, Wireless and LoRa via serial on https://client.meshtastic.org
I connected to my android phone to the node and sent a message and i can see my chUtil going from 0.7 my AirUtilTX stays at 0.1% and watching it in the app i can see chUtil jumping to 1.7, 2.4 and the highest is been is 13.2

I have checked on a SDR at around 869.400 but i can only see my node sending packets, And nothing around me explains why my chUtil is going so high again i never experienced this in previous builds.

Relevant log output

MacbookWiFi:~ francis$ meshtastic --noproto\
WARNING file:mesh_interface.py _sendToRadio line:686 Not sending packet because protocol use is disabled by noProto\
Connected to radio\
WARNING file:mesh_interface.py _sendPacket line:536 Not sending packet because protocol use is disabled by noProto\
WARNING file:mesh_interface.py _sendToRadio line:686 Not sending packet because protocol use is disabled by noProto\
INFO  | ??:??:?? 3 \
\
//\\ E S H T /\\ S T / C\
\
@francisuk1989 francisuk1989 added the bug Something isn't working label Mar 25, 2024
@francisuk1989 francisuk1989 changed the title [Bug]: 2.3.2 instantly maximum transmission duty cycle [Bug]: 2.3.2 instantly maximum transmission duty cycle and high chUtil Mar 25, 2024
@GUVWAF
Copy link
Member

GUVWAF commented Mar 25, 2024

Do you have MQTT downlink enabled?

Can you show the serial logs with the CLI command meshtastic --noproto or any serial monitor on baud 115200?

@francisuk1989
Copy link
Author

francisuk1989 commented Mar 25, 2024

Do you have MQTT downlink enabled?

Yes for MQTT but only set to Uplink only in Channels and also ignore MQTT is set under LoRA

Can you show the serial logs with the CLI command meshtastic --noproto or any serial monitor on baud 115200?

Give me around 2 hours and i will give send the serial logs but just wonted to say about MQTT.

@francisuk1989
Copy link
Author

francisuk1989 commented Mar 25, 2024

Can you show the serial logs with the CLI command meshtastic --noproto or any serial monitor on baud 115200?

@GUVWAF i have attached a serial logs to the 1st post.

@GUVWAF
Copy link
Member

GUVWAF commented Mar 25, 2024

I don’t see anything special in that log. It shows you tried to send a message, but after a while no one acknowledged it. Is the issue still happening?
With which app/client are you connecting to the node?

@francisuk1989
Copy link
Author

I don’t see anything special in that log. It shows you tried to send a message, but after a while no one acknowledged it. Is the issue still happening? With which app/client are you connecting to the node?

Macbook using client meshtastic.org
Android (google pixel 8 pro)

@francisuk1989
Copy link
Author

francisuk1989 commented Mar 25, 2024

Is the issue still happening?

Not got the maximum transmission since factory reset yet.

@garthvh
Copy link
Member

garthvh commented Mar 25, 2024

Max retransmit means nobody got your message, has nothing to do with the duty cycle.

@thebentern thebentern closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2024
@francisuk1989
Copy link
Author

Max retransmit means nobody got your message, has nothing to do with the duty cycle.

the whole issue was just a sudden message of "maximum transmission" but since i not get that message again then i cant debug it.

never mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants