Measured using only software : about 16 ms to wake up from light sleep. Both using wake on pin (interrupt) or timed light sleep.
Need to confirm with external measurement : i(t) powering LoPy4 by using oscilloscope + shunt resistor.
More simple procedure on Linux :
start from the Linux menu "Pycom Firmware tool", quote "include dev releases"
then just choice /dev/ttyACM0 in High transfert mode
the firmware is flashed in 1.18.1.r1
Wrote 1.19 MiB from sipy.bin in 1 minute and 13.88 seconds
It appears that there has been some good progress with addressing a number of the issues with lte implimentation. Band 20 users are reporting connection success.
What is happening with band 8 support my debelopment functions, along with others are dead in the water until the modem can support this band.
Please provide an update on progress.
@xykon said in New Firmware Updater version 1.15.1:
@bmarkus Win32:Evo-gen [Susp] is a broad classification used by the Avast Behavior Monitor feature for software that exhibits suspicious behavior categorized as potentially malicious. The Behavior Monitoring feature observes the behavior of processes as they run programs.
The firmware updater connects to the Internet. That is considered "suspicious" for some anti-virus applications.
Thanks for the details. However it is a bit strange,a s I'm frequently installing programs connecting to the net during installation and have never seen such message from my AVAST.
Anyhow, I will ad it as an exception.
@frida I couldn't agree more! It took me some time to understand that when I get to a topic the first message is the OP and then I have to scroll all the way down and start reading from bottom to top. Really weird. At least order by oldest to newest by default, please =D
Hi @mongkol, so you have this error every time you try to update? Or just once in a while? I would suspect the PC USB port to be the problem, you could:
change the USB-microUSB cable
use the PC direct USB port, not thru a USB hub;
remove other USB peripherals from PC
The firmware update packages are sent over DFU protocol, which runs over USB bulk transfer channel, it might happen that the CRC of a package was wrong (or delayed).
I have upgraded device (WIPY2.0) from 1.7.2.b1 to 1.9.2.b2 and have problems:
ntp_sync most of the time not wrok (hang and never ending)
i use for it old method
def getNTPTime(host = "pool.ntp.org"):
port = 123
buf = 1024
address = socket.getaddrinfo(host, port)[-1]
msg = '\x1b' + 47 * '\0'
msg = msg.encode()
TIME1970 = 2208988800 # 1970-01-01 00:00:00
# connect to server
client = socket.socket(AF_INET, SOCK_DGRAM)
msg, address = client.recvfrom(buf)
t = struct.unpack("!12I", msg)
t -= TIME1970
tuple_time = time.localtime(t)
but also tested if rtc.ntp_sync could help but same result :(
i2c not work - i2c buss error
i init it with id=0 (i do not remember if in 1.7.2 it was hardware or software based)
bus=I2C(0, I2C.MASTER, baudrate=100000, pins=("P19", "P20"))
to test it what is going on i have updated board 3 times (all times sucessfully)
but with the same result
i have downgraded firmware back to 1.7.2.b1
all work without any problems - any hint?
when i press download into new folder (pymakr VS configured on COM port)
all files are downloaded but 3 of them cannot be downloaded
tried many times with reset, disconnect ...
Downloading 3 files...
[1/3] Reading lib/sensor.py
Failed to download lib/sensor.py
[2/3] Reading lib/konfig.py
Failed to download lib/konfig.py
[3/3] Reading lib/GPS2.py
Failed to download lib/GPS2.py
this is how it looks like in Filezilla:
Do you have any concept what can be wrong? - because e.g. file sensory.py is quite small
name is also in lower letters without numbers - nothing special.
konfig.py is really small file 696 bytes...
I can of course do this by Filezilla but..
I am using @Butch 's BME280 lib from HERE
If I can get away with using P10 sequentially I will. Moving SCL to another pin is a great alternative. My BME280's are pretty close, about 5cm, but they are plugged into the LoPy expansion shield pin headders, which have some 'play' in them (not a solid connection). I would prefer to solder them somewhere for impact testing. What's hot glue for anyway :-)
I'm using a fully made breakout BME280 board from HERE
@jmarcelino thought moving the I2C pins is best, since you can't move the deep sleep shield pin 10. -Thank you!
in the main.py I added the pin assignment:
i2c = I2C(0, I2C.MASTER, baudrate=100000, pins=('P8','P9'))
Works fine now.