@mraj That's the way: Either it is called main.py, or main.py contains a line import mycode or boot.py contains a statement machine.main("mycode.py"), which causes mycode.py to be executed instead of main.py

@jmarcelino @livius I'm working on this as we speak. Will update you shortly.

@Martinnn said in GPS in motion or stationary: I was looking for an "assisted" version that lets you download the data, but for this GPS chip this does not seem to exist. The documentation mention an AGPS mode called EASY and how to set and query the mode. By default it is on. But it neither tells how to upload data nor which format is needed.

Hello all! This release doesn't appear to be changing the LoRaWAN mac version to 1.0.3, on a LoPy4. Update performed with Pycom firmware updater tool (not self built). >>> import os >>> os.uname() (sysname='LoPy4', nodename='LoPy4', release='1.20.3.b3', version='v1.11-92f2b22e on 2021-04-19', machine='LoPy4 with ESP32', lorawan='1.0.2', sigfox='1.0.1', pybytes='1.6.1', pygate='1.0.1') >>> Could it be that the name was not updated, though the firmware still tries to support 1.0.3? If this feature requires me building a more recent beta version, would consider it. Could really do with this for testing. Thanks for any pointers.

Hello, I released a fully new version (v2.0) of my web server here : https://github.com/jczic/MicroWebSrv2. Open source MIT, fully asynchronous, more robust, more fast and more efficient on Pycom modules. It is delivered with a good documentation. Thank you for your support and feedback. ☺️

@robert-hh There is a PR for that to fix the issue OK, thank you for the heads up

@Butch See this link about downgrade: https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users V1.6.8b2 links are canonically derived according to the list: https://software.pycom.io/downloads/LoPy_868-1.6.8.b2.tar.gz or https://software.pycom.io/downloads/LoPy_915-1.6.8.b2.tar.gz or https://software.pycom.io/downloads/WiPy-1.6.8.b1.tar.gz

Sorry to say but those UART pins are not mapped onto test points or external pins on the GPy. They only connect to the ESP32.

@testos As long as you do not use SPI this does not matter. And the SPI pins can be reassigned too. And P11 (External IO 8) seems not to be connected on pytrack. Using I diode tester, I cannot detect any connection. At P10 (external IO 7) seems to be used. At least is show something like a ESD diode behavior of an active chip pin.

@jcaron It's working as you said. Thank you

@crumble Thank you for your explanation. I have another question, i have downloaded the libraries from github.com and currently i am running for the pytrack with lopy for the latitude and longitude data. May i know is it correct to download the .py files (L76GNSS.py, LIS2HH12.py, pytrack.py) and navigate the file to a new folder eg: pytrack lib and in the Atom with pymakr plugin i click on File and Add new folder and select the pytrack lib folder. may i know when i upload the libraries to the pytrack board by "sync folder" or "sync file" it showing the error since the "main folder" is too big. What is the correct way to upload the libraries ?

@chumelnicu @JasonTimmins , @iotmaker Any update with VL53L0X library ? Thank you !

@StefanoF I made a few more tests with the most recent code I have posted (which is the initial goertzel code). a) test for phase jitter. Instead of reading the ADC, i just supplied a artificial 50Hz sine with an amplitude of 50 and an offset of range/2 into the algorithm. Result: constant 49.99993, which means that there is no phase jitter. b) I connected the interface network, but not the sensor. Result: Output values between 0.005 and 0.03. Since the output value of 1Veff is about 240, that is equivalent of ~60µVeff, or about 1 mA through the sensor. c) connect a battery with 1.5V to the input. Result: values of about 0.5 -> Noisy battery! d) connect the SCT013 with no current. Value of 0.04 +/- 0.03. That's about 160µVeff of 3 mA (or 0.5 W at 230V) through the sensor. So it looks as if the sensor picks up some noise, but still ok. e) Using an external ADC (mcp3201). Result: values of 0.05. Slightly worse than using the internal ADC. Lesson learned: I will stick with the initial solution. The challenge is to proper shield the interface network and the cable from picking up unwanted noise.

@DongYin look at: https://docs.python.org/3/tutorial/inputoutput.html there are paragraphs about files also look here https://docs.pycom.io/pycom_esp32/library/uos.html os.mkdir create directory

Allow me to add some more comments. 220uA in deepsleep is too much, this is not expected. Outside of an Expansion board, just supplying vin and gnd, it should be 20-21 uA in deepsleep (with 3.75V supply). In an Expansion board 3.1 I see it as low as 57uA. Do you have jumpers (which) and/or SD card inserted? 57uA is without any.

@jcaron Dear Jcaron: Tnx for your reply. Sorry, if I couldn't make it clear. But, I now I have made it to sending a few hundreds of bytes now (upto 1KB). As soon as I am done with the final project, I will share my updates.

@assia said in LoPy Antenna Setup / Installation: it will be automatic as soon as I set up the external antenna Yes, you do not need to do anything more and as written previously better is not start Lora without antenna at all