@livius First i tried it in boot.py - then i moved it to main.py. Both with no success. Then i had an idea. I'm using a FritzBox with Wifi on 2.4 and 5 GHz with the same ssid. I think this is the root cause. I enabled the guest AP and tried to connect to this - and this is working. So at least i have workaround for me! But anyway , thanks a lot for your help!
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.
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...
So better never supply the board by the 3.3V Pin. That's an output, not an input. Use the Vin Pin for supply. @daniel: Please remove note, that the device can be supplied through the 3.3V pin. Even if that may work under certain conditions, the risk is too high that devices will be broken.
I see that we disscuss this 6 months ago ;-) https://forum.pycom.io/topic/316/wipy-pin-3v3-not-work
But conclusion was different.
Now when we have schematic i do not see there any diode or something like LTC4357
And schematic(and description) for LM3281 does not bring light if there is some protection - especially that there is comparator output
It happens when it's connected to my router. I tried first with a static IP adress but I read there are some problems with that (because of DNS), so I use address reservation for DHCP clients in order to have it connected to a specific IP address.
@Arkaik In the list of commits, you have to go back to an entry with the title "Bump to version 1.4.0.b1". There you find the fingerprint. It's not a long way.
In you first port you mentioned 1.4.0b1. But now you mention 1.0.4b1.
About esp-idf. Do use the version indicated by the pycom web site.Try to checkout the most recent version before the date of the wipy firmwar you are using. That might get a little bit of a trial & error game.
Also, "Run" command on a file doesn't update the file on the flash, resulting in a strange behaviour if the current file is also present in the flash.
Editing the script and running it seems to use the classes from the file on the flash memory, and the "top level" instructions from the editor file :/
Now the "Sync" end with an error. I rebooted the board, the PC and updated the firmware....