@seb How do we get the position we just get: https://forum.pycom.io/topic/2971/lopy-gps-pytrack-no-coordinates-found

@jmarcelino https://forum.pycom.io/topic/2971/lopy-gps-pytrack-no-coordinates-found We dont get any cordination on that...

@livius TYVM!!

@seung-beom-kim said in LoRa Gateway: @bmarkus No, I don't. I'm interesting in dust monitoring system of shipyard using many of Lopy. And I want to know how to install LoRa network using Lopy. For example, when I purchase 100 of Lopy, I want to know which LoRa gateway I should use. Are you saying you do not want to use LoRaWAN? For a 100 devices industrial system I strongly advice to use LoRaWAN. For GW, there are many option, e.g. a Kerlink indor or outdoor, TEKTELIC PICO, etc. For Kelink IoT Station and iFemtocell you either buy SPN which is in embedded LoRaWAN network server, you can buy a MULTITECH CONDUIT. If you need a LoRaWAN server you can chose LORIOT or other cloed services. Plenty of options. But using 100 devices you need a real GW, I mean with SX1301 board which can receive uplink messages on 8 channels, 6 per channels (if DR is different) and can manage the devices. Do not use single channel SX127x based device as a gateway except you are a specialist of networks and you have our own, trusted protocol. But still you can not eliminate hardware limitations.

@mj It's just some math, you don't need a module to do it. However, be aware that most trilateration formulas are based on exact distances, which you are very unlikely to get, so you'll end up with no solutions if you try to solve the equations as equalities. Also, I don't know your use case, but it may indeed make more sense to do this stuff network-side rather than on the node.

@mj SInce the for string for pack contains only two fields, it must be written as: _LORA_PKG_FORMAT = "Bf" pkg = struct.pack(_LORA_PKG_FORMAT, DEVICE_ID, D) But besides that, the receiver must contains a lora_sock.recv(64) call, in order to get something. Please have a look at the simple examples in the documentation on how the code structure has to be set up.

Also it would be helpful to add nSIM card orientation (https://forum.pycom.io/topic/2486/nano-sim-card-orentation/2) to these datasheets (GPy, FiPy).

@robmarkcole there are a few “holes” for I/O under the module, but you’ll need to solder connectors.

@mj Depends on the antenna an it's set-up. With a short wavelength/4 antenna, I had values between 25 and 39 dBm, even depending on how I was placing myself. The wavlength/4 antennas are typicall about 10cm (4") long, whereas wavelength/2 antennas have a length of about 20 cm (8").

@mj both recv_pkg_len and pkg_len are the same value, the second line could well have been written like this also: device_id, _, msg = struct.unpack(_LORA_PKG_FORMAT % recv_pkg_len, recv_pkg)

@livius I have tried to work around this in the past but had no luck, I will get our sysadmin to look into it a bit more

No issue @drgdhorler, have fun coding :)

@mj I had some problem with atom to and the plugin pymakr... I did uninstall atom and remove all packed from c:\user\atom then I install atom again 1.24 then I remove the auto update and after that I run cmd: and apm install pymakr@1.2.7 so it did install that version and it works perfect now :) Im happy... I would say that works perfect right now... No error or so! :)

@burgeh As said, I did not investigate the ping-pong example further. I just used it to check, whether the devices work at all. Using the TTN gateway software was more reliable. At least messages form the node to the gateway arrive all the time. You may have a look at the non-TTN gateway example https://github.com/pycom/pycom-libraries/tree/master/examples/loraNanoGateway That one is a litte bit more elaborate and may be a better starting point. I tried it too, and it worked. The code of interest is in the respective main.py files.

@jcaron Ahhhhhhh. Thanks. I have been using this; https://pycom.io/product/pytrack/ "PIN OUT" link

Hi, Yes, the way the Pytrack/Pysense/Deepsleep shield sleep works is that they disconnect the power from the module, sensors etc entirely. In the case of the Pysense and Pytrack the USB is also de-initialised meaning you will lose the serial connection, this can make talking to the device difficult if it does not wake up for long The Pytrack/Pysense/Deepsleep shield sleep is a a "deep" sleep rather than a regular sleep. Once you use this, when the module wakes up it will be like it was rebooted. Pycom board do not currently support machine.sleep although this is being investigated. The way this differs from the machine.deepsleep is that this uses external hardware and powers off everything on the board, not just the ESP32 processor. You can still use machine.deepsleep if you desire but note that on the WiPy2, LoPy and SiPy, due to an issue with the way the voltage regulator is connected the deepsleep current draw will be quite high (15mA) If you connect P12 to 3.3v with a jumper cable and wait for the device to wake from sleep you will see the on-board LED blink orange. Once this happens you can disconnect the cable. The device will now "safe boot". This prevents the device from running boot.py and main.py and therefore the code putting the device to sleep. The best way to stay informed of firmware updates is to use the forums subscribe feature for the announcements forum. We will always post in there when a new firmware is released

@mj You should specify both the region and frequency when using raw LoRa lora = LoRa(mode=LoRa.LORA, rx_iq=True, frequency = 915000000, region=LoRa.US915) The region parameter is optional an can usually be determined from the choice you made using the firmware upgrade tool, but it doesn't hurt to specify it.

@xykon Problem solved after installed the latest version of the firmware update tools

@bmarkus Good too know .. I will keep that in my mind Thank you!