I'm using RHF0M301 LoRaWAN Gateway module with my custom gateway board, not the Raspberry Pi platform and Semtech packet forwarder.
When i send a confirmed uplink message, the problem is occured.
The problem is that i can't receive downlink(ACK) with warning message.
In packet-forwarder console window
WARNING : A downlink was already scheduled. overwritting it...
INFO : [jit]lgw_status returned TX_SCHEDULED
There is no problem sending a unconfirmed message.
Packet forwarder work fine without any problems.
It is only a matter of receiving the downlink.
However, there is no such problem in the raspberry pi platform environment.
In the raspberry pi platform environment, I can receive downlink or ack.
This problem seems to be caused by the differnce between custom board and
raspberry pi.
I think that spi and reset pin are connected properly.
When i excute test_loragw_reg, the following message is displayed.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
End of register verification
IMPLICITY_PAYLOAD_LENGHT = 197 (should be 197)
FRAME_SYNCH_PEAK2_POS = 11(should be 11)
PREAMBLE_SYMB1_NB = 49253(should be 49253)
ADJUST_MODEM_START_OFFSET_SF12_RDX4 = 3173(should be 3173)
IF_FREQ_1 = -1947(should be -1947)
End of test for loragw.reg.c
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I think these messages prove that the pins are properly connected.
Is there anything else to consider besides pin connection?
When i send a confirmed uplink message, the problem is occured.
The problem is that i can't receive downlink(ACK) with warning message.
In packet-forwarder console window
WARNING : A downlink was already scheduled. overwritting it...
INFO : [jit]lgw_status returned TX_SCHEDULED
There is no problem sending a unconfirmed message.
Packet forwarder work fine without any problems.
It is only a matter of receiving the downlink.
However, there is no such problem in the raspberry pi platform environment.
In the raspberry pi platform environment, I can receive downlink or ack.
This problem seems to be caused by the differnce between custom board and
raspberry pi.
I think that spi and reset pin are connected properly.
When i excute test_loragw_reg, the following message is displayed.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
End of register verification
IMPLICITY_PAYLOAD_LENGHT = 197 (should be 197)
FRAME_SYNCH_PEAK2_POS = 11(should be 11)
PREAMBLE_SYMB1_NB = 49253(should be 49253)
ADJUST_MODEM_START_OFFSET_SF12_RDX4 = 3173(should be 3173)
IF_FREQ_1 = -1947(should be -1947)
End of test for loragw.reg.c
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I think these messages prove that the pins are properly connected.
Is there anything else to consider besides pin connection?