Downlink not working
- This topic has 5 replies, 2 voices, and was last updated 4 years, 9 months ago by .
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
- You must be logged in to reply to this topic.
Tagged: downlink, LoRa, lora-network-server, uplink
Hello!
I have Multitech MTCDTIP-L4E1-266A-868 gateway. As an end-device I am using Lansitec temperature+humidity sensor. Uplink is working fine, it sends uplinks every 5 minutes.
Check link below for sensor documentation:
https://www.lansitec.com/forum/posts/list/7.page
Also check link (image) below for sensor’s downlink registers:7
https://drive.google.com/file/d/1X5cj0AH5T5ttEs-3be5iqu1VvMkkyKl6/view?usp=sharing
I am trying to configure sensor with downlink but it’s not working. I am trying through Downlink queue. Here are my settings:
* DevEUI: choosen correct
* App port: 1
* Data format: Hex
* Data: 090006
* Ack attempts: 0
* Rx window: 0
I want to change period of temperature and humidity report. I am not sure how to do it. I don’t know which port to select? How can I find correct port? Documentation of sensor is not mentioning any ports. Also, please provide example for either Hexadecimal or Base64 format for this specific downlink message. I am new at LoRa systems and some things are confusing me.
Thanks in advance!
Some additional information: Device is sending periodic uplinks every 5 minutes. Downlink does disappear from the queue. I do not see any downlink packet in the Packets page. I tried sending downlink in Node-Red, but situation is the same.
In the Packets table you should see the UpUnc packet and a DnUnc packet.
Do you see only UpUnc packets?
I checked Packets table after some time (30 minutes). I got 5 UpUnc packets in a row, the 6th packet UpUnc was followed by one DnUnc, 1 second after UpUnc. In last 1 hour I did not force any Downlink queue. Should I test if I get some DnUnc after forcing downlink queue?
I suggest opening a ticket at support.multitech.com to share screenshots and gateway log files.
OK, now it’s all working fine. Turns out I’ve been writing wrong payload in Hex format.