Cannot receive data send by raspberry pi +RFM95W on Node-RED

Home › Forums › Conduit: AEP Model › Cannot receive data send by raspberry pi +RFM95W on Node-RED

Tagged: 

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • February 6, 2017 at 8:38 am #16693
    damian nahmiyas
    Participant

    hi people!
    i need some help with this.
    i have a multitech lora gateway and raspberry pi B+ with RFM95w lora node based on LMIC library(https://github.com/hallard/arduino-lmic/tree/rpi).
    iam try to test otaa connection, but not see debug data in node-red.
    the lora network server configured by public.

    console out:
    ttn-otaa Starting
    RFM95 device configuration
    CS=GPIO24 RST=GPIO22 LED=GPIO25 DIO0=Unused DIO1=Unused DIO2=Unused
    DevEUI : ****************
    AppEUI : ****************
    AppKey : ********************************
    14:25:58: Packet queued
    14:26:03: EV_JOINED
    14:26:06: EV_TXCOMPLETE (includes waiting for RX windows)
    14:26:46: Packet queued
    14:26:50: EV_TXCOMPLETE (includes waiting for RX windows)
    14:27:30: Packet queued
    14:27:33: EV_TXCOMPLETE (includes waiting for RX windows)
    14:28:13: Packet queued
    14:28:16: EV_TXCOMPLETE (includes waiting for RX windows)
    14:28:56: Packet queued
    14:28:59: EV_TXCOMPLETE (includes waiting for RX windows)
    14:29:39: Packet queued
    14:29:42: EV_TXCOMPLETE (includes waiting for RX windows)
    14:30:22: Packet queued
    14:30:26: EV_TXCOMPLETE (includes waiting for RX windows)
    14:31:06: Packet queued
    14:31:10: EV_TXCOMPLETE (includes waiting for RX windows)

    February 6, 2017 at 8:59 am #16694
    damian nahmiyas
    Participant

    termial output with LMIC_DEBUG_LEVEL 2

    RXMODE_RSSI
    14:49:22: 618: engineUpdate, opmode=0x8
    Packet queued
    14:49:22: EV_JOINING
    903: engineUpdate, opmode=0xc
    999: TXMODE, freq=902300000, len=23, SF=7, BW=125, CR=4/5, IH=0
    317436: RXMODE_SINGLE, freq=923300000, SF=7, BW=500, CR=4/5, IH=0
    380681: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    383449: engineUpdate, opmode=0xc
    429513: engineUpdate, opmode=0xc
    429702: TXMODE, freq=903000000, len=23, SF=8, BW=500, CR=4/5, IH=0
    744073: RXMODE_SINGLE, freq=923300000, SF=7, BW=500, CR=4/5, IH=0
    807317: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    810048: engineUpdate, opmode=0xc
    1041380: engineUpdate, opmode=0xc
    1041544: TXMODE, freq=903900000, len=23, SF=8, BW=125, CR=4/5, IH=0
    1361230: RXMODE_SINGLE, freq=923300000, SF=8, BW=500, CR=4/5, IH=0
    1424450: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    1427174: engineUpdate, opmode=0xc
    1427367: TXMODE, freq=903000000, len=23, SF=8, BW=500, CR=4/5, IH=0
    1741728: RXMODE_SINGLE, freq=923300000, SF=7, BW=500, CR=4/5, IH=0
    1804973: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    1807708: engineUpdate, opmode=0xc
    2025365: engineUpdate, opmode=0xc
    2025558: TXMODE, freq=903700000, len=23, SF=9, BW=125, CR=4/5, IH=0
    2351053: RXMODE_SINGLE, freq=927500000, SF=9, BW=500, CR=4/5, IH=0
    14:50:00: EV_JOINED
    2353765: engineUpdate, opmode=0x808
    2353888: TXMODE, freq=908900000, len=20, SF=9, BW=125, CR=4/5, IH=0
    2428127: RXMODE_SINGLE, freq=923900000, SF=9, BW=500, CR=4/5, IH=0
    2491300: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    14:50:04: EV_TXCOMPLETE (includes waiting for RX windows)
    2611235: engineUpdate, opmode=0x800
    14:52:04: 10111247: engineUpdate, opmode=0x808
    10111356: TXMODE, freq=909100000, len=20, SF=9, BW=125, CR=4/5, IH=0
    Packet queued
    10185563: RXMODE_SINGLE, freq=924500000, SF=9, BW=500, CR=4/5, IH=0
    10248735: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    14:52:07: EV_TXCOMPLETE (includes waiting for RX windows)
    10316075: engineUpdate, opmode=0x800
    14:54:07: 17816128: engineUpdate, opmode=0x808
    17816254: TXMODE, freq=909300000, len=20, SF=9, BW=125, CR=4/5, IH=0
    Packet queued
    17890459: RXMODE_SINGLE, freq=925100000, SF=9, BW=500, CR=4/5, IH=0
    17953631: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    14:54:10: EV_TXCOMPLETE (includes waiting for RX windows)
    18014043: engineUpdate, opmode=0x800
    14:56:10: 25514110: engineUpdate, opmode=0x808
    25514219: TXMODE, freq=909500000, len=20, SF=9, BW=125, CR=4/5, IH=0
    Packet queued
    25588413: RXMODE_SINGLE, freq=925700000, SF=9, BW=500, CR=4/5, IH=0
    25651589: RXMODE_SINGLE, freq=923300000, SF=12, BW=500, CR=4/5, IH=0
    14:56:15: EV_TXCOMPLETE (includes waiting for RX windows)
    25823235: engineUpdate, opmode=0x800

    February 6, 2017 at 9:35 am #16696
    Jason Reiss
    Keymaster

    Is lmic code in 64 channel mode?
    Conduit can only receive on 8.

    February 6, 2017 at 10:07 am #16700
    damian nahmiyas
    Participant

    hi Jason!
    where see this on LMIC?

    February 14, 2017 at 11:29 am #17110
    damian nahmiyas
    Participant

    hi people!
    post update:
    i recived data sometime:
    17:06:00: EV_JOINED
    4387291: engineUpdate, opmode=0x808
    4387398: TXMODE, freq=910900000, len=20, SF=10, BW=125, CR=4/5, IH=0
    4473304: RXMODE_SINGLE, freq=925100000, SF=10, BW=500, CR=4/5, IH=0
    4479087: Received downlink, window=RX1, port=1, ack=0
    17:06:01: EV_TXCOMPLETE (includes waiting for RX windows)
    17:06:01 Received 7 bytes of payload
    4481205: engineUpdate, opmode=0x800

    very rare. i need some help with this.
    any with the same problem?

    February 14, 2017 at 12:11 pm #17112
    Peter Ferland
    Blocked

    The Conduit is limited to listening on 8 channels at a time. There are 64 uplink channels in LoraWAN between 902.3MHz and 914.9 MHz for a total of 8 subbands. 910.9MHz is channel 43 in frequency sub band 5. If you set the Conduit to using frequency subband 1 it will be listening on the first 8 channels – 902.3MHz to 903.7MHz. Your device is listening for a response on receive channel 3 which is correct based on uplink channel 43, but if the Conduit was not configured for frequency subband 5 then it could not receive the transmission.

    Try restricting your device to only using channels 0-7 (902.3-903.9MHz) and set the Conduit to frequency subband 1.

    Introduction to LoRa

    Conduit AEP: LoRa Use With Third-Party Devices

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.