• 0 Votes
    4 Posts
    189 Views
    E
    @mnovella Hello Thus, we can say that currently the LoPy4 does not support RejoinRequest natively, and that for it to happen the LoRa Module would have to be v1.1 compliant. Is this correct? LoPy AND LoraWAN operator have to be conform to 1.1 specification to use it. If yes, then given it's not natively supported, the responsibility for rejoining, etc. would fall on the application programmer (that is, me, or the code my LoPy has), just like you said that you start a join procedure after X time of not getting a downlink. Am I right? Yes, that's i do, after two week if no downlink as been recevied the device do a new OTA join request The 1.1 specs say that: "Once activated a device MAY periodically transmit a Rejoin-request message on top of its normal applicative traffic" It's very important when reading ISO/RFC/ETSI/official specification to be veray careful to the use of 'MUST',"MAY" and 'SHOULD" and there's indeed meaning. The low-level stack MUST support processing RejoinRequest but it's not mandatory that the application use it or is allowed to use it. That "MAY" part was the one that made me dubious if it was supported by the device or not... so I guess that even if/when Pycom supports LoraWAN 1.1 it will be up to Pycom to decide if/when to do the RejoinRequest if I'm not mistaken... I don't know what pycom will do when they will working to 1.1 port, but for me it's a "No" if i have had to vote, sending a new RejoinRequest is IMHO and application job and not a low-level stack/driver job. However, RejoinRequest is not send by a device, it's send by the network. When you do roaming (even in same country) you cant be in a specific area where some frequence channel is unusable (jammed), the network send to the device a RejoinRequest, the device perfom a new joinrequest and in the answer it receive a new channel list used in the area (frequency plan). If your device is static you don't have to think about this. My device perform new joinrequest as it's a moved device and can be for a long time out-of-network and when it come back is framecounter is far from when it leave the network and we don't receive anymore it's frame if we don't do a new joinrequest.
  • ADC conversion values

    Discussion adc adc accuracy lopy4 sensor
    4
    0 Votes
    4 Posts
    333 Views
    robert-hhR
    @mrks-tsk The capacitor has to be placed between ADC input and GND. In your diagram at the VBATT side.
  • 0 Votes
    3 Posts
    324 Views
    S
    @mfalkvidd Hi, tks for the reply. Ok, that explains the problems that I have.
  • Communication between LoPy and Node.JS server

    LoPy wireless lopy4 wifi node.js
    1
    0 Votes
    1 Posts
    256 Views
    No one has replied
  • 0 Votes
    2 Posts
    259 Views
    catalinC
    hi @westmaxx, Let's first connect the 2 Lopy4 in the same Mesh network. What firmware are you using? what micropy scripts are you using? Could you run this tutorial: https://docs.pycom.io/tutorials/lora/lora-mesh/ ? The LoRa 868 Mhz antenna is on the right side of the LED, as shown here: https://docs.pycom.io/gitbook/assets/lopy4-pinout.pdf Also, please make sure you're using the same LoRa parameters on both boards? Band, frequency, bandwidth and spreading factor?
  • Maximum output current on 3.3V pin Lopy4

    LoPy lopy4 current consump
    5
    0 Votes
    5 Posts
    459 Views
    P
    @robert-hh Thanks for that information robert.
  • is there a way to check an output pin HIGH or LOW ?

    LoPy lopy4 pinout
    4
    0 Votes
    4 Posts
    338 Views
    robert-hhR
    @soibac35 if pinNumber is already a string, you do not need str(pinNumber).
  • BLE Advertisement Max Length

    Issues & Bugs ble lopy4
    3
    1
    0 Votes
    3 Posts
    322 Views
    J
    Hi @pvstejeswar , did you figure it out ?
  • LoRa communication lopy - rfm9x

    LoPy lopy4 rfm95 lora
    9
    0 Votes
    9 Posts
    880 Views
    M
    @Eric73 Great, thanks for your help !
  • How to get the automatic AP back on lopy ?

    LoPy lopy4 ap mode wifi access point
    9
    0 Votes
    9 Posts
    733 Views
    M
    @robert-hh Ok, thanks !
  • 0 Votes
    2 Posts
    243 Views
    T
    You could look for NVRAM here: https://docs.pycom.io/firmwareapi/pycom/pycom.html
  • LoPy 4 OTAA join fail on some units

    LoPy lopy4 loraserver otaa
    5
    0 Votes
    5 Posts
    499 Views
    C
    Bottom line here is that PyCom sells less than user friendly devices and provides poor documentation on use. I have been trying repeatedly to get my LoPy4 to OTAA join to no avail. I have scoured and tried just about every code sample on GitHub and nothing. Sadly, I did get my 32u4 feather to join with no issues whatsoever. This pisses me off because I dropped nearly $80 on PyCom (board, LoPy4, antenna, shipping) The forum is hardly readable. As are the docs. Just plain lousy.
  • BLE characteristic advertsiing

    LoPy ble lopy4
    3
    0 Votes
    3 Posts
    298 Views
    M
    i have lopy4 that advertisers temperature data every 30minutes and want to consume this data when it's available. At the moment, I'm creating another lopy just to continually scanner for this characteristic and then forward it though mqtt. Would tyhis be the correct way to achieve this?
  • Devices lost LoRa activation

    LoPy lopy4 lorawan
    6
    0 Votes
    6 Posts
    548 Views
    J
    @River are you sure you’re not missing something in your code? When you wake up, you should restore LoRa settings, then check if the node thinks it has joined, and it not, try to join. If some any reason you don’t get to the LoRa save, the next restore will result in the device having lost the join state, and being unable to send anything...
  • waiting for download when I restart the board

    LoPy lopy4
    8
    0 Votes
    8 Posts
    611 Views
    A
    Or, as in my case, the "Boot" microswitch on my dev board was broken and pulling the pin to ground.
  • board and pycom deep sleep

    Expansion Board lopy4 deepsleep
    8
    1 Votes
    8 Posts
    610 Views
    M
    I have noticed that upon wake up, that *.py files randomly get errors but when i reset its fine. Didn't know I had to do machine.deepsleep first to close down OS! I really enjoy the pycom ecosystem BUT the effort should be on a robust OS and not extra hardware. This will bite them...Reliability always win in the long term..
  • 0 Votes
    9 Posts
    751 Views
    B
    @melkoutch hope you still read this as this thread is quite old. I stumbled upon it having the exact same problem (LoPy4 <-> Feather M0 in raw LoRa). Adjusting the spreading factor doesn't seem to solve it for me. Would you be able to post the code fragment that you used to successfully connect the two? Thanks a lot!
  • LoRaWAN low level debug messages

    LoPy lorawan debug lopy4
    10
    1 Votes
    10 Posts
    837 Views
    J
    @mk IIRC a reset will have the same effect as deep sleep, resetting LoRaWAN counters and other state. Unless you join every time you reset, you need to save and restore state.
  • Lopy4 FFT (spectrum analysis) micropython, adding C code?

    LoPy lopy4 fft c code
    23
    1 Votes
    23 Posts
    4k Views
    rcolisteteR
    About FFT, there is 'ulab' module (a micro NumPy/SciPy) for Pycom MicroPython, see the topic "Pycom firmwares with single/double precision and ulab module".
  • LoPy4 locking on sending and receiving data

    LoPy lopy4 sigfox locking
    8
    0 Votes
    8 Posts
    717 Views
    T
    @Eric73, thank you very much. Everything is functioning properly now!