Not sure if this could be a possible solution to writing to characteristics, can anyone help me please? https://devzone.nordicsemi.com/f/nordic-q-a/8162/ble-driver-python-concurrent-notifications

@pkilcoyne Hello, my two cents about reading your topics, Basically if two lora module have same center Freq, same SF, same SYNCWORD (0x34 for lorawan and 0x12 for private lora), same coding rate, same IQ (IQ is inverted for lorawan and not inverted for private lora usally) and same HeaderSetup (implicit or explicit) the RX/TX work. I dont see where with lopy how we can set header mode, so i suppose it's always explicit ? In ERA-LORA it seem to be the same think (cannot set header mode so may be alway set a explicit?). They use "group ID" term instead of SYNCWORD, and they don't speak about IQ (so it's be supposed to be alway inverted ?) I suggest you to try inverting IQ in Lopy for RX and TX, set group ID to 12xx in era lora , be careful on how you select frequency on both module and try...may be it's change something. *I dont speak about header CRC mode setup it's a little bit fuzzy how it work.

@robert-hh I want to remove the time.sleep and just focus on checking if the packed is sent before sending more so I can max out the send and recv part...

@sameerchouksey sys.getsizeof() is not implemented in micropython. For strings and arrays, len() may give you a useful response, depending on your needs.

@robert-hh Hello, I updated the firmware and it seems to work, thank you ! Can't belive I didn't do this step ...

@seb Thanks!

@robert-hh Thanks ! I finally did it ! Thanks a lot

This thing about the solid green light on a Lopy4. I've been seeing that also. For me it first occurred after about a week of uptime of the LoPy4. I assume that some unobserved fatal error occurred which resulted in a watchdog reset and then a solid green light scenario manifested itself on the reboot. I pressed the reset button about 3 or 4 times, each time getting the solid green light. The next press of the reset button was followed by a normal boot and normal, expected behaviour of running code. I can't see this being a power supply issue, or an issue with file-system corruption.

Also you have not checked if coord = l76.coordinates() return something it can contain None

Thanks for the replies! @robert-hh It might be that the program is not burnt onto my LoPy. I ran the uos command and this is what I got: ['main.py', 'sys', 'lib', 'cert', 'boot.py']

Hey! Did you solve it? I am having the same problem... Can't fix it. Thanks!

@mj Any single cell lipo with a JST-PH connector. Be careful of the polarity of the connector, there doesn't seem to be a standard so you may need to swap the connector wires around before plugging it in.

@juan-narvaezb95 said in Multi-hop End-Device?: listens, sends and transmits at the same time At the RF channel, the LoPy can either Receive or Send at a given moment. You can of course communicate by WiFi and Lora at the same time.

@rachelsimida this is to fast to read it in this way look at pulses_get https://docs.pycom.io/chapter/firmwareapi/pycom/pycom.html#pycompulsesgetpin-timeout sometimes is also good to dissable irq remember = disable_irq() .... enable_irq(remember)

@juan-narvaezb95 Multi-hop is not supported by the LoRaWAN Specification.

@jmarcelino Thanks for these resources - I'll definitely give them a read.

For lower attenuation it would better to go with 433 MHz, even better to 169 MHz that is also an ISM band. The big problem with compost, if I remember well how is processed, it is its high water content. There are several studies that can be found about "soil" and wireless sensors networks, search for WUSN (wirelss underground sensor network) and UG2AG (underground 2 aboveground). Usually are studies made for agriculture, forestry, soil, pipelines, ... sensors deployment.

@seb I notice that the cordination has abit delay first time you upload it... and it start working once you reboot it :)

finally got it working, had to try three cables i had. i didn't realize the world had so many power-only usb cables, unmarked as such. Thanks!