Hi,
We have a customer with a sensor that requires the following parameters:
-
Do you agree to optimize the performance (eg. Battery lifetime, Service level agreement, telegram content/ data points, data granularity) of the sensor in combination with the selected LoRaWAN Network operator?
NOTE: Changing the LoRaWAN Network operator or Network Management Server provider could lead to additional effort and reduced performance of the system. -
How much repetitions do you expect the device to transmit (MAC Command: LinkADRReq, Parameter nbTrans)?
- Note: HYDRUS 2 LoRaWAN meters can work with nbTrans of upto 3 if configured in production. Preferred would be to set it to 1, if network allows it.
- Please provide your Default setting
- Is there the opportunity to modify the parameter device specific and in case which range is possible?
- Are there any consequences using device specific settings?
-
Does your network environment frequently request the device status from the sensor and in case how often (MAC command: DevStatusReq, DevStatusAns)??
- Note: If requested, HYDRUS 2 LoRaWAN meters send 2 values as part of DevStatusAns:
- a valid Signal to Noise ratio (SNR).
- a default (invalid) battery percentage. A valid remaining battery life ‘in days’ is sent as part of weekly static telegram instead.
- Can the network be configured to use battery life from weekly static telegram instead of DevStatusReq?
- Is there an opportunity to deactivate DevStatusReq?
- Note: If requested, HYDRUS 2 LoRaWAN meters send 2 values as part of DevStatusAns:
Anyone able to answer if CHirpstack is able to manage above questions?