#Qr factory mac how to#

For this change to take effect, the end device does not need to perform a re-join. The Network Server will then start using the Rx1Delay of 6 seconds for scheduling downlinks. The end device will answer with an RxTimingSetupAns MAC command in the next uplink. The Network Server will schedule an RxTimingSetupReq MAC command to communicate a new Rx1Delay of 6 seconds to the device. To see Rx1 delay change in the current session, modify the 1-delay parameter: ttn-lw-cli end-devices update -application-id -device-id 1-delay RX_DELAY_6 For demonstration purposes, in this example we use 6 seconds. The Things Stack configures the Rx1Delay to 5 seconds by default to accomodate for high latency backhauls and/or peering with Packet Broker, so this is the recommended configuration. If no settings are provided on device creation or unset, defaults are first taken from the device Frequency Plan if available, and finally from Network Server Configuration. See how this applies to the Rx1 delay parameter in the example below. Modify sired_ to make the change permanent.The expected procedure for testing and updating settings is: are applied on the next uplink, and lost on reset. To update settings for testing in the current session, make changes to the sired_parameters. Mac-state can be used to test MAC settings in the current session. It may however be necessary to set mac-settings.RX1_delay for ABP devices where this is not configured as part of activation. represents what the Network Server believes is configured on the end device, and should not be changed, unless the device does not conform to the LoRaWAN specification.

Updates to sired_ take effect on device creation, after OTAA join or ABP FCnt reset, ResetInd, or after MAC state reset.

To configure persistent MAC settings, make changes to sired_.

MAC settings on The Things Stack are configurable per end device.

#Qr factory mac how to#

Learn how to install the CLI MAC Settings and MAC State