-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
class-C RX2 window not working anymore? #699
Comments
Could you please provide the commit hash that is working as expected? We will provide a feedback as soon as possible |
I also had similar problems with lorawan 1.03 development. static void OpenContinuousRxCWindow( void )
} |
Set to CLASS_C device, but the second receiving window is not configured |
I set the demo routine to CLASS_C, but MacCtx. Rx Windows CConfig. Frequency is 0 |
Has anybody found why the frequency is set to 0? |
I'm using the 5.0.0 branch and this function gets called: void SX1276SetChannel( uint32_t freq ) |
I have the same problem :/ |
The code I posted can solve this problem temporarily. |
In OpenContinuousRxCWindow function,add |
Is this issue happening in both ABP and OTAA activation modes? From our analysis it should only happen in ABP mode. |
I only tested it in OTAA. |
Ok, thanks for the feedback. |
And I have tested in ABP mode.
…On Mon, Jun 17, 2019, 5:47 PM yanzi418 ***@***.***> wrote:
I only tested it in OTAA.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#699?email_source=notifications&email_token=AHHIEDI7AYNHHCP2WP2K3Z3P254LXA5CNFSM4G7SVQMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX26HPY#issuecomment-502653887>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHHIEDPT5C7322BZQHYBKLLP254LXANCNFSM4G7SVQMA>
.
|
@yanzi418 and @Mr-Techtron, Could you please check that the below patch solves the observed issue? On my side I will check that the FUOTA project is still operating as expected. Thanks in advance. diff --git a/src/mac/LoRaMac.c b/src/mac/LoRaMac.c
index 319a86fb..145bcd47 100644
--- a/src/mac/LoRaMac.c
+++ b/src/mac/LoRaMac.c
@@ -2586,6 +2586,14 @@ static void ResetMacParameters( void )
// Initialize channel index.
MacCtx.Channel = 0;
MacCtx.NvmCtx->LastTxChannel = MacCtx.Channel;
+
+ // Initialize Rx2 config parameters.
+ MacCtx.RxWindow2Config.Channel = MacCtx.Channel;
+ MacCtx.RxWindow2Config.Frequency = MacCtx.NvmCtx->MacParams.Rx2Channel.Frequency;
+ MacCtx.RxWindow2Config.DownlinkDwellTime = MacCtx.NvmCtx->MacParams.DownlinkDwellTime;
+ MacCtx.RxWindow2Config.RepeaterSupport = MacCtx.NvmCtx->RepeaterSupport;
+ MacCtx.RxWindow2Config.RxContinuous = false;
+ MacCtx.RxWindow2Config.RxSlot = RX_SLOT_WIN_2;
}
/*! |
Work for me! (ABP) |
We assume that the OTAA is also working as there is no feedback. We will apply this patch as soon as possible. |
Hi there, this is still not working correctly. For example when the device received a new set of RX2/RXC params per MAC command, these changes are saved into the NVM variables but not into the actual running variables. This is not too bad for the RX2 params, as these are set once the timer event kicks in after sending a message. However, the local RXC params are never updated. I added this to ScheduleTX in LoRaMac.c to solve the problem (the reason i added it there is that the servers usually change the devices RX2/RXC frequecies once they have received an answer from the node, as this is a ACK MAC command [triggers a tx needed event]):
|
Hi, I haven't updated the LoRa stack in a while, I'm using 5.0.0 feature branch. Today I did an update and now the RX2 window seems to be broken.
Before the update, I can go to the MultiTech gateway and send a downlink at any time, the downlink is sent out right away and the device picks it up, no problems.
Now after the update, same thing, I send the downlink, it is sent out right away but the device pretends like nothing is going on, as if the continuous RX2 window didn't exist anymore.
What do you think went wrong? Is there anything I can check?
For the time being I went back to the previous version of the stack but here I'm dealing with the rare condition where the lora stack gets stuck, thinking it's in TX mode.
The text was updated successfully, but these errors were encountered: