-
Notifications
You must be signed in to change notification settings - Fork 327
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
uplink fail (re-up) #584
Comments
Hello. Re-Up means "repeated uplink". All your uplink frames have FCnt=0, so the server considers them as a retransmissions of one uplink frame. |
I put the code in a loop and tried to send multiple frames successively, it Worked! Am I missing something? Why would it work for multiple transmissions but not for a single one? |
@BouTayehGaby Hello, your gateway has nothing to do with the FCnt counter, that is your device that is sending the data uplinks and not increasing the Up counter, hence the server ignores the data as ducplicate. You can check if that is the correct data by disabling the FCnt check in your device's Profile. |
Yeah. The server ignores retransmitted frames, so if the FCnt is the same it does not sent anything to backend. Try setting the "FCnt check" in your device profile to "Disabled". |
Thank you. Problem Solved, you may close this issue. |
hello!
Why my gateway is failing to upload data to the app server (red arrow, when I hover the mouse over it, it says "re-up")? I checked the configuration of my handler and my connector it seems correct. I tried to use postman to simulate and uplink to my app server, and the app server is working just fine.
Another unrelated question, what is the field "confirmed"?
Thank you
The text was updated successfully, but these errors were encountered: