@RobTuDelft thx for the help.

Thank you both for your answers! Finnaly with ADC.ATTN_11DB it works!

@robert-hh Perfect, I will have a look at it, thank you.

Ok..it works again using /dev/cu.usbmodemP* device. That confused me...usually its always a tty. Thanks a lot!!

@mikexu007 You can work with same lib

@jmarcelino said in [SOLVED] Having issues build firmware from soure: https://dl.espressif.com/dl/xtensa-esp32-elf-linux32-1.22.0-61-gab8375a-5.2.0.tar.gz once again, @jmarcelino saved my day, thanks

@dbrgn I'm having the same issue and I can reproduce it even with all latest firmware So to get back to your original question, is there a way to reset PIC with a Lopy GPIO, ie in case of I2C Error, reset the PIC should recover. Can we locate the PIC reset pin on the PySense/PyTrack boards? I would like to solder a wire from LoPy GPIO on it. It's difficult to tell our customers to recycle power on devices located in the field.

@bucknall Sounds good! Ok, we gaan met jullie beren...

What Removed Added Resolution --- FIXED Status REOPENED RESOLVED Comment # 5 on bug 104320 from Aleksander Morgado I've pushed the 2 blacklisted devices with rules including vid:pid, but I've also added the whole vid to the "usb adapters greylist", which are only probed if manually requested to do so, so should help to avoid interference with other Microchip-vid-tagged devices. https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=c2b956aefce495865cbdcb9971e2b3cd99cd0e99 All fine & dandy in the end…

I follow the tutorial, checked config many times but my gateway seams to be still offline.. look stuck at the same place you where then posted this question. do you remember the things you've made different that made it work?

@paul-thornton I replied on another thread that I think you responded to that I have this issue with 1.20.0.rc0. I reverted back to my unmodified build of 1.19.0.b4 and the problem disappeared. I found that after machine.reset() the clock still would not sync reliably (or at all) and even sometimes after a hard reset by hitting the reset button.

Hi @cylex, Could you please update to the latest firmware? Version 1.7.0b1 introduced a number of fixes for the BLE code examples. You can check what version of firmware that your device is currently running by using the commands from the REPL import os os.uname() Thanks! Alex

A temporary fix: downgrade Pymakr Atom package from version 1.0.2 to version 1.0.1. Curious to know where the problem lies in version 1.0.2 for my LoPy-Pysense combo.

I have to add some information: I can't use the lastest firmware because the modules are spread and so out of my reach :( I flashed all LoPy modules in April so that's the latest firmware I'm currently using. While searching the web for my problem I found this: https://github.com/Lora-net/LoRaMac-node/issues/104 It says that there is a bug in the SX1276 driver and so maybe in the SX1272, too. It misses a division by 4of the SNR value... And thats the factor I need. So: Does anyone know if this bug was a thing in the LoPy's too and had been fixed in the last weeks after my last update? I can't find anything about it in the last changelogs...

@olivierd Wow, this tip saved a lot of time. The problem still persists in the updater tool as of today.

Having the same issue. Just getting "Pull hack" "Push hack", but gateway not showing up in TTN. Trying to follow the official tutorial, with no changes.

@Cristi You can definitely do this, however you will need to write a simple protocol to talk to the different devices and associate an ID to each of them. Here's a link to some documentation that will help you get started - https://docs.pycom.io/pycom_esp32/pycom_esp32/tutorial/includes/lora-nano-gateway.html Let me know if you need any more support! Thanks, Alex