Replies: 1 comment 3 replies
-
For Class B operation a gateway with a GPS module and its PPS signal connected to the SX130x chip is required. If yes, then usually an end-device connects to the network server and then tries to acquire the beacon signal sent by the gateways. Once this step is done the end-device is able to enable the Class B mode of operation, I would recommend to read the LoRaWAN 1.0.4 specification as well as potentially read the following article In-Depth: LoRaWAN® 1.0.4 Class B and C for End Devices |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my specific use case
Class B
would be the perfect solution with a good balance between responsiveness and power consumption. I want to be able to send a downlink from the gateway to the lora device to "activate" my device with a maximum time window of about 120 seconds. I could do this withClass A
(just sending a LoRaWAN message every 2 minutes) but then I would probably be going over the fair use policies.However so far I've not been able to get
Class B
working.I've enable
Class B
in Chirpstack with the correct setting to my EU868 region:I've set
LORAWAN_DEFAULT_CLASS
toCLASS_B
When I send the first few messages out I see
DeviceTimeReq
and the seeOnSysTimeUpdate isSynchronized: 1
But I'm not able to schedule downlink messages with the 128 second interval window.
Could anybody please help me with getting this working?
Beta Was this translation helpful? Give feedback.
All reactions