Navigation

    Welcome to the Pycom forum

    Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Tags
    3. spreading facto
    Log in to post

    • G

      LoPy to LoPy: Raw LoRa sf
      Getting Started • loramac spreading facto raw lora • • GMB124  

      2
      0
      Votes
      2
      Posts
      137
      Views

      L

      Just guessing, but you should probably set the same spreading factor on the receiver also?
    • R

      Lopy Nano Gateway: Multiple Data Rates?
      LoPy • nanogateway data rate spreading facto • • Re  

      2
      0
      Votes
      2
      Posts
      389
      Views

      robert-hh

      @re Yes. The SX1272 of the LoPy of SX1276 of the Lopy4 can only listen to one frequency and one SF/BW setting at a time. The target platform for these chips is motes (= Lora nodes, AFAIK), not gateways. Gateways use typically a different chip set, like the combination of Semtech SX1257 and SX1301/SX1308. If you need a full service gateway, you must get one. There are raspi add-on boards Like the IC880a from ICMP and the RAK831 which offer full service. Or you buy a ready gateway. Look at the The Things site for product lists. ICMP offers also a ready built box with raspi, receivber & software for testing.
    • B

      LoPy Cannot Change DR or SF in LoRaWAN mode (always SF10, dr 0, bw 125kHz)
      LoPy • lopy lorawan data rate adr spreading facto • • brady.aiello  

      4
      0
      Votes
      4
      Posts
      663
      Views

      B

      @jcaron The Rising HF RHF301, on the frequencies described here: https://account.thethingsnetwork.org/api/v2/frequency-plans/US_902_928 So, it looks like that's 903900000 904100000 904300000 904500000 904700000 904900000 905100000 905300000 all on 125 kHz bw.
    • L

      LOPY on a lorawan public network,
      LoPy • lopy lorawan spreading facto join issues • • lj  

      12
      0
      Votes
      12
      Posts
      2327
      Views

      L

      Hello bruno, this is what I did, instead of using the exemple code, I can set and catch the timeout error hence loop while not joint. while lora.has_joined() is not True: try: lora.join(activation=LoRa.OTAA, auth=(dev_eui, app_eui, app_key), timeout=20000, dr=0) except Exception as e: print('Not joined yet...')
    • R

      ADR don't work with LoPy+Pysense and Multitech Conduit
      LoPy • lorawan adr spreading facto • • rloro338  

      5
      0
      Votes
      5
      Posts
      1268
      Views

      R

      Yesterday i was testing ADR on LoPy with confirmed packets. I achieved that LoPy change to a SF8BW125 but no more, the communication range was the same. I forced the LoPy to transmit at SF12 in the socket configuration, and the range is the same too... I looked from lora.tx_power() and the value is 13, i think 13 dBm. About 100 meters in line vision, the gateway measured SNR = 8 dB and RSSI = -78 dB ... it is OK?
    • M

      Solution for Setting spreading factor, power, coding rate and frequency for LoRaWAN join is mandatory.
      Enhancements • lopy lorawan join adr spreading facto • • manu  

      4
      0
      Votes
      4
      Posts
      2160
      Views

      T

      @aris This topic looks quite old, and I really do hope that you have found the solution by now, but if not: To hardcode SF12 when joining this works for us: when joining: self.lora.join(activation=LoRa.OTAA, auth=(self.dev_eui, self.app_eui, self.app_key), timeout=0, dr=0) After setting up the socket: self.s.setsockopt(socket.SOL_LORA, socket.SO_DR, 0)
    • 1 / 1