Open vinsanitycarter opened 5 years ago
What a great and throughout report! I love it.
From the channel setting it seems you want to downlinks to use a single channel (64). To achieve that you should use the "US 902-928MHz (Private Hybrid)" region. Try that, please.
What a great and throughout report! I love it.
From the channel setting it seems you want to downlinks to use a single channel (64). To achieve that you should use the "US 902-928MHz (Private Hybrid)" region. Try that, please.
Thank you for answer. I didn't think to use a single channel(64). Just i set it to [0-7, 64] because uplink uses channel 0-7 channel. But i tried changing the region to US902-928MHz(Private Hybrid) as you told me. And test it. The results are nothing new. I also tested the changing the region to [0-71]. There was nothing that changed either. It seems that setting the server's region is not a problem. Is there anything else that could be a problem?
What a great and throughout report! I love it.
From the channel setting it seems you want to downlinks to use a single channel (64). To achieve that you should use the "US 902-928MHz (Private Hybrid)" region. Try that, please.
Additional testing has confirmed that this is not a gateway issue. There seems to be a problem on the lorawan-server side.
I have no idea what could be wrong, unfortunately. These types of errors are hard to debug remotely.
I am having uplink_missed and downlink_missed error.
First of all, let me know the test enviroment.
[End device setting]
[gateway setting]
Here is global_conf.json
[lorawan-server]
gateway configuration
network configuration
Device configuration
Here is a description of the test environment. When i send a LoRaWAN message, the server does not display any data like this.
and this is gateway console display.
However, the message that end device is turned on and transmitted for the first time is normal.
This problem occurs when sending a confrmed message. When sending an unconfirmed message, it is normal as shown below.
And if the payload size is reduced and a confirmed message is sent, the data received from the server is displayed, but the downlink is not performed. End device can not confirm the ack signal.
gateway console display
And, I've senn warning message on the gateway console.
The warning message is "|a downlink was already scheduled, overwritting it."
I post parse_uplink and build downlink for reference.
I don' think there is a problem with the end device. Because, donwlink was normally done on The Thing Network[TTN].
At "at+recv=1,0,0" message, if first parameter is 1, confirmed message transfer was successful and ack signal is received from server.
Downlink was also done normally.
At at+recv=0,2,-40,26,5,0908070605 0: Indication that data was received 2: port -40 : rssi 26 : snr 5 : data length 0908070605 : data
this picture is gateway traffic
this gateway hardware is raspberry pi3 + risingHF rhfm031, and software is TTN Packet Forwarder on a raspberry pi with and IMST ic880a board.
There seems to be a problem with the gateway or the lorawan-server. First, I will check the lorawan-server. Is there anything wrong with the server settings?