• LOPY BLE Peripheral

    LoPy lopy ble peripheral
    4
    0 Votes
    4 Posts
    541 Views
    M
    @johand Thanks for the answer this work prefect
  • How to send/receive LORAWAN MAC Commands?

    LoPy lorawan lopy mac time rtc
    3
    1 Votes
    3 Posts
    775 Views
    O
    @paul-thornton said in How to send/receive LORAWAN MAC Commands?: https://docs.pycom.io/firmwareapi/pycom/network/lora.html#lorastats I'm not sure whether lora.stats() rx_timestamp is of use, it does not seem to represent a time value, but if it does, how do I convert it? [LORA ] 2019/02/21 04:51:55 (rx_timestamp=0, rssi=0, snr=0.0, sfrx=0, sftx=0, tx_trials=0, tx_power=14, tx_time_on_air=0, tx_counter=0, tx_frequency=0) [LORA ] 2019/02/21 04:52:04 (rx_timestamp=30539834, rssi=-45, snr=7.0, sfrx=3, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=57, tx_counter=0, tx_frequency=0) [LORA ] 2019/02/21 04:52:11 (rx_timestamp=38155453, rssi=-38, snr=8.0, sfrx=3, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=47, tx_counter=1, tx_frequency=0) [LORA ] 2019/02/21 09:04:47 (rx_timestamp=45778581, rssi=-43, snr=8.0, sfrx=3, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=47, tx_counter=2, tx_frequency=0) [LORA ] 2019/02/21 09:15:32 (rx_timestamp=690412324, rssi=-47, snr=6.0, sfrx=5, sftx=5, tx_trials=2, tx_power=0, tx_time_on_air=57, tx_counter=4, tx_frequency=0) [LORA ] 2019/02/21 09:15:38 (rx_timestamp=696682500, rssi=-48, snr=6.0, sfrx=5, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=57, tx_counter=5, tx_frequency=0) [LORA ] 2019/02/21 09:15:44 (rx_timestamp=702935506, rssi=-47, snr=6.0, sfrx=5, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=57, tx_counter=6, tx_frequency=0)
  • 0 Votes
    3 Posts
    853 Views
    J
    @paul-thornton Thanks, this worked! I figured out that the same addition 'region=LoRa.EU868' is needed at 4 locations in nanogateway.py: around line 169, 263, 355, and 378. I still have a problem with the downlink not getting to the node (without giving any error message). This may be a timing problem: Only in one instance, the TTN website indicated that the node confirmed receipt of the downlink. In all other cases, no such confirmation was received. Let me investigate that further first.
  • 2 Votes
    2 Posts
    761 Views
    P
    Im not the correct person to answer your BLE queries. but if you let me know what they are Ill get them infront of someone who can and get you answers :) Otherwise. Awesome work :D
  • Access LoPy mac address without using atom.

    LoPy lopy mac address serial
    4
    0 Votes
    4 Posts
    566 Views
    P
    @hobbypy any programming language with a serial library should work. simply open a serial connect to the board via your preffered language / framework. and send the code as a string over it. The response will come back over serial just like the REPL does.
  • <class 'OSError'> Avialable Interfaces are down

    LoPy lopy4 oserror lopy interfaces
    15
    0 Votes
    15 Posts
    2k Views
    M
    @johand After I've set IP for HTTP server wlan.ifconfig(id=1, config=('192.168.4.10', '255.255.255.0', '192.168.4.1', '192.168.4.1')) i've tried to read IP address of HTTP Server and that was the problem, it's keep returning me '0.0.0.0'. IP address was set properly to '192.168.4.10' but function returns '0.0.0.0'. print('Network config:', wlan.ifconfig()) Network config: ('0.0.0.0', '0.0.0.0', '0.0.0.0', '0.0.0.0') Thank you for your help. @pigamonte I've managed to do it with 1.18.2.
  • Lopy freezes after 6 - 12 hours

    LoPy lopy freeze serial
    7
    0 Votes
    7 Posts
    792 Views
    P
    @crumble said in Lopy freezes after 6 - 12 hours: I do not understand why pycom does not declare the 1.20 branch as stable. It fixed so many errors for me that I like to see it as the stable branch. Maybe they want to deploy it together with some cloud changes. But 23 will be the better number for this ;) Features are still being worked on and improved. Even more stability cant hurt :D
  • UART READ WRITE

    WiPy 2&3 uart buffer lopy fipy
    3
    0 Votes
    3 Posts
    660 Views
    D
    Hi @robert-hh , Both Lopy and Fipy have firmware release='1.18.2.r1'
  • Firmware update over FTP

    Firmware lopy
    2
    0 Votes
    2 Posts
    293 Views
    P
    You can specify the Lora region via the Lora() constructor in your code instead. I believe (but will have to confirm) that the drop down setting it only used when dealing with pybytes. I will confirm this however. Example for the EU868 region: lora = LoRa(mode=LoRa.LORAWAN, region=LoRa.EU868)
  • 0 Votes
    11 Posts
    1k Views
    robert-hhR
    @arthurmed So what are the properties of the pulses to receive, and what kind of device is it that you want to connect? Edit: I just tested that: Even if you specify then number of pulses, it will not return until a timeout happens (and the documentation is still wrong, because pulses_get() does not accept any arguments).
  • Long time before transmitting a packet.

    Discussion lopy lora time
    13
    0 Votes
    13 Posts
    995 Views
    robert-hhR
    @snehasg96 main.py is executed automatically when the device boots. If ouy wnat to run a script, like recv.py, manually, just enter at the REPL prompt (the one with >>>): import recv
  • Lopy and SIM800L connection

    LoPy lora lopy sim800
    2
    0 Votes
    2 Posts
    375 Views
    R
    @iplooky Hi, I think I am looking for the same concept to. My case is to implement a Lora Nano-GTW and use a SIM808 to backhaul the data via GPRS. Is it the same case you have? I am actually a the planning stage. If you have advanced something, please share your ideas. I am thinking to do it with an arduino module. I am going to try to create a serial connection with it and also connect other arduino's pins with the SIM808 and create another serial Then I guess hard code programming should be necessary in order to create the flux of information between the pycom to an arduino's logical buffer and then to the SIM808 to be transmitted to some internet server through GPRS cell network. Please, destroy my idea with anything. Thanks to all.
  • time.sleep() not accurate

    Issues & Bugs time time of arrival lora lopy utime
    6
    0 Votes
    6 Posts
    577 Views
    S
    @crumble also, is it fine to use the utime.time() in the receiver as well or just use it in the sender? Also i tried running the code after removing time.sleep() in the receiver but for some reason i still experience the same issue.
  • Is the L01 specsheet correct?

    LoPy lopy specs
    2
    0 Votes
    2 Posts
    295 Views
    robert-hhR
    @thosch42 The LED is indeed connected to P2 = GPIO0.
  • Default Parameters

    Discussion lora lopy
    3
    0 Votes
    3 Posts
    395 Views
    S
    @robert-hh thanks there is not much described here about the standard values in the initialiazation.
  • 0 Votes
    8 Posts
    818 Views
    S
    @snehasg96 Can you try the same thing with utime.sleep() instead? I haven't tried it myself yet, but I plan to do so.
  • PyBytes Firmware OTA update failed?

    Firmware lopy
    3
    0 Votes
    3 Posts
    405 Views
    P
    Hey. Whilst not super convinient as its 50 miles from you. If you can reclaim it and flash https://forum.pycom.io/topic/4185/new-pybytes-firmware-1-18-1-r9-experimental-lte-support manually Is should solve the issue with corrupted / weird data from Lora.
  • How to set join request SF in OTAA mode?

    LoPy lopy otaa ttn
    4
    1
    0 Votes
    4 Posts
    672 Views
    E
    @miroslav-petrov Hi, yes adr need to be driven by gateway. In pycom documentation adr is parameter of lora constructor. So what make you said it's not work ? As far i know some network compute adr setting only after a big sample of rx frame (for a nation wide operator in france they use approximatly one hundred of frame before send first downlink adr request to my device). Does your gateway show if adr is set in your uplink frame ?
  • Sock_stream in Lopy ?

    LoPy lopy socket lora sockstream
    4
    0 Votes
    4 Posts
    467 Views
    P
    @snehasg96 Not without significant development effort. And honestly you would not want to. Lora just isnt setup for that kind of two way comm's without a ton of latency and bandwith issues.
  • RED LORA CON LOPY4

    LoPy lopy
    5
    0 Votes
    5 Posts
    2k Views
    John BairdJ
    @gustavo said in RED LORA CON LOPY4: buenas noches @John-Baird si es correcto pero estoy tratando de usar estos equipos lopy4 tanto para el nodo como para el gateway nose si se pueda hacer eso y el sensor para medir el flujo de agua 1/2" YF-S201 nose si ud conoce otro sensor mas bueno y es para armar una red lorawan por favor quisiera su opinion y su ayuda sobre este proyecto gracias Hi Gustavo - Sorry for the delay, I've been unwell for the past two weeks. Darn influenza! I'm not sure about the LoRaWAN side of things as I mostly use LTE for wide area networking. There are folks on this forum who use LoRaWAN a lot who can help. As for the YF-S201, there are a few things to consider: The device requires at least 4.5v to run. This means you can run it from the VIN of the WiPy, but only if you are supplying it with more than 4.5v. The WiPy will run happily from 3.5v - the YF-S201 will not. This might make using batteries difficult. The YF-S201 has an accuracy of 10%, but most of this is on the low side. A measurement of 100L might be as much as 110L, but is probably somewhere between 100L and 90L. If you wish you can experiment and figure out a "correction factor". Be aware that the lower the flow rate, the worse the error is. The device works best if it measures the output of a pump. If the water is moved by gravity it's not so good. The YF-S201 out is 5v TTL, while the inputs of the WiPy are 3.3v. This means you need to shift the level of the output. A simple pair of resistors will work. I'd suggest you look at using the output of the meter to drive an interrupt on the WiPy. This will let you count pulses while doing other things. If you need help with any of the above, let me know. Hola, Gustavo. Lo siento por la demora, no he estado bien durante las últimas dos semanas. Maldita gripe! No estoy seguro del lado LoRaWAN de las cosas, ya que principalmente uso LTE para redes de área amplia. Hay gente en este foro que usa mucho LoRaWAN que puede ayudar. En cuanto al YF-S201, hay algunas cosas a considerar: El dispositivo requiere al menos 4.5v para funcionar. Esto significa que puede ejecutarlo desde el VIN del WiPy, pero solo si lo está suministrando con más de 4.5v. El WiPy se ejecutará felizmente desde 3.5v, el YF-S201 no lo hará. Esto podría dificultar el uso de las baterías. El YF-S201 tiene una precisión del 10%, pero la mayoría está en el lado bajo. Una medida de 100L puede ser tanto como 110L, pero probablemente se encuentre entre 100L y 90L. Si lo desea, puede experimentar y averiguar un "factor de corrección". Tenga en cuenta que cuanto más bajo es el caudal, peor es el error. El dispositivo funciona mejor si mide la salida de una bomba. Si el agua es movida por la gravedad no es tan buena. El YF-S201 de salida es 5v TTL, mientras que las entradas del WiPy son 3.3v. Esto significa que necesita cambiar el nivel de la salida. Un simple par de resistencias funcionará. Le sugiero que mire el uso de la salida del medidor para provocar una interrupción en el WiPy. Esto te permitirá contar pulsos mientras haces otras cosas. Si necesita ayuda con alguno de los anteriores, hágamelo saber.