@jmarcelino Aha! This is excellent, thanks for pointing me in the right direction.

@codemaniac64 Umm I'm not sure, do you have any debug visibility on your PSoC code? Seems like it's rejecting something. Can you see if the BLE connection is still up when you try the .write(b'x0f')? It really helps to have a BLE sniffer like this https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer

@jcaron said in What components are required to build a 915 mhz LoRaWAN Gateway on an Arduino: Note however that the LoPy is a single-channel device. A real LoRaWAN gateway needs to be able to listen on multiple channels at the same time, while the LoPy can only listen on one channel at a time. So you can build what is called a "nano-gateway" here, which will listen on a single channel, and is usable with devices that send on that single channel. If you want to support other devices: Not only single channel but single DR, can detect signal with one Data rate only, no multi-spreading.

OK I realise I hadn't configured my Lopy to connect to my Wifi - all good now, thanks for your help!

@ledbelly2142 Hi ledbelly2142 I am doing a project with the same devices as you. I am a begineer of IoT and it seems I can learn something from your experience. May you share the whole code you have done of this deep sleep shield connected with LoRa, if you still have it. Thanks in advance! Regards Rachel

@juan-narvaezb95 1.17.0.b1 see https://forum.pycom.io/topic/2734/new-firmware-release-v1-17-0-b1-completely-new-lte-class/39

Pins P13 to P18 are input only so these can only be used for MISO, not MOSI, CLK or CS.

@burgeh The timing requirements are defined in the Lora Specs. The details about the implementation and its's behaviour are a result of my measurements and the code analysis. Nevertheless, the changed firmware works reliably, and Daniel is about to publish it some time. The trail of my tests are here: https://forum.pycom.io/topic/2728/lopy-and-nanogateway-example-inaccurate-timing-prevent-otaa-join and here: https://forum.pycom.io/topic/2676/abp-mode-and-frame-counters/18 You see, I spiraled a bit around the problem.

@jmarcelino Thank you that appears to be correct! I get my push and pull acks now.

@gas have done some initial testing what parts of LWM2M were you interested we are only implementing some parts of the protocol

@jmarcelino Thanks a lot for your suggestions. I used the LTE module with some modifications to manage standard LTE modem. As you probably know pycom-esp-idf LWIP fork is not suitable for PPPOS handling. esp-idf original LWIP work properly. Now i'm using UART 2 for external modem LTE and UART 1 for other comunication towards external ST microcontroller. I need to start WiFi(AP)/BLE and LoRaWan only on demand (ask to start from a cloud ..). How can i configure the board to start with WiFi,BLE and LoRaWan disabled and activate these functions only when i need ? For example "WIFI start on boot" seems a configuration that reside on flash memory (wifi_on_boot = config_get_wifi_on_boot(); in mptask.c...), it is possible to change that flash parameter and store it during flashing phase ? Also seams that ble and wifi share the same antenna, i think that is not possible to use both at the same time, right ? Thanks a lot B/R

Hi @daniel, just wanted to make sure these two issues will be addressed in the next release: save/restore channel mask fix MAC command buffers restore Let me know if you need/want issues filed in GitHub and/or PRs.

Yes thanks @robert-hh, Just wanted to make it clear to anyone looking this answer up for the more generic node - gateway separation concern that was being discussed

@emms it would probably be helpful if you specified which region you are in (US or AU I suppose).

I have tried the firmware update on Windows 10 and windows 7 and the update stays stuck on "Please wait. Reading information about the board ..." Last week Xylon sent a *.tar.gz file which I was able to update the firmware using the CLI tool. Could you please provide the same. Thanks.

@seb I write this code to be able to find where it doesn't work from network import Bluetooth import time bt = Bluetooth() print("searching") bt.start_scan(-1) print("connection") conn = bt.connect('C47C8D643FAF') print("connected") def characteristic_callback(char): v = int.from_bytes(char.value(), "little") print("Got new value: {}".format(v)) print("before services") services = conn.services() print("services") for service in services: print("Service: {}".format(service.uuid())) if service.uuid() == b'XXXXXXXXXXXXX': characteristics = service.characteristics() for characteristic in characteristics: print("Characteristic: {}".format(characteristic.uuid())) if characteristic.uuid() == b'XXXXXXXXXXXX': characteristic.callback(trigger=Bluetooth.CHAR_NOTIFY_EVENT, handler=characteristic_callback, arg=None) So, in the terminal it print searching connection connected before services So it never reach the line : services = conn.services() in the page https://wiki.hackerspace.pl/projects:xiaomi-flora , it's specified that "You need to write 0xA01F to the handle 0x0033 to enable real-time data reading " How can I write the value 0xA01F in the handle 0x0033 ? Thanks in advance for your precious help.

Have you tried using something other than pymakr? maybe screen or minicom. Also its worth checking if your user has permissions for the serial port. The procedure to do this varies by linux distro but on most you can add your user to the dialout group and when you reboot that user will have permissions to use serial ports sudo usermod -a -G dialout $USER