miha.horvat@siol.net
Forum Replies Created
-
AuthorPosts
-
miha.horvat@siol.netParticipant
Please be more specific and accurate when writing your posts.
1st device works OK and you also see its payload?
2nd device is registered but you don’t see any payload packets?
Is the above correct?Do you see join packets from 2nd device? Are you sure the device is sending payloads? Check your time interval between on the device for sending uplink. Many sensors have long time intervals (12 hours or 24 hours); therefore you have to configure correct downlink and wait for the next uplink. If your device is A-class, you have to wait for the next uplink for downlink to be configured on the device.
miha.horvat@siol.netParticipantI can’t see your screenshot, can’t download it.
Is problem with uplink or downlink? I’m sory but I don’t understand exactly what is your problem. Please give us more information.
miha.horvat@siol.netParticipantNow it’s all working fine. Thanks for support.
miha.horvat@siol.netParticipantOK, now it’s all working fine. Turns out I’ve been writing wrong payload in Hex format.
miha.horvat@siol.netParticipantI 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?
miha.horvat@siol.netParticipantSome 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.
miha.horvat@siol.netParticipantDevice is sending periodic uplinks every 5 minutes. Yes, downlink does disappear from the queue. I do not see any downlink packet in the Packets page. I am not sure what to do. I tried sending downlink in Node-Red, but situation is the same.
miha.horvat@siol.netParticipantI am trying with Downlink queue but no success. Please check below settings for downlink queue:
* DevEUI: choosen correct
* App port: 1
* Data format: Hex
* Data: 090006
* Ack attempts: 0
* Rx window: 0Please check again image I posted in previous post to see my device’s registers and bytes. Thanks in advance.
miha.horvat@siol.netParticipantUplink is now working fine. But I would like to test some downlink. I want to change period of temperature and humidity report. I am not sure how to do it. I am using LoRaWAN –> Operations tab. I select Message type. I don’t know which port to select? How can I find correct port? Documentation of sensor is not mentioning any ports. Please check out link below to see registers and bytes for downlink message of sensor.
https://drive.google.com/file/d/1X5cj0AH5T5ttEs-3be5iqu1VvMkkyKl6/view?usp=sharing
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!
miha.horvat@siol.netParticipantLooks like my Lansitec temperature and humidity sensor was off. I unscrewed 4 screws, flipped power switch to ON and “voilà!” It works 😀 I can see received packets and communication is successful. Jason Reiss, thank you for quick reply. We engineers should always check basis 😀
-
AuthorPosts