@sneha Hey, I’m just a user like you, I’m trying to help, but you probably need to do your own research, or ask Pycom directly...

@seb Yes, I do get the led to blink orange. That has not been an issue at all, works fine. I tried uploading my code and keeping 3.3v and G28 connected, and the result was this: [image: 1520259532693-safe-boot-error.png] I tried removing the wire connecting 3.3v and G28 and I could finally upload! Thanks for all the help!

@colateral said in CRITICAL: Guru mediation erases the data from flash: We did o LOpY but not possible on L01. it is possible but harder ;-) However in this way Guru mediation output is not catched. good point, core crash will not go then to SD card.. then only external device can catch this

@jmarcelino It works! Thank you.

Got it. Thanks @seb and @jcaron for all your help !

Hi, Thanks for reporting this issue, it will be resolved in the next firmware release coming shortly

@areli_anzures Can you try connecting just the expansion board without the LoPy? It should still appear as a serial port. If it works without the LoPy please check if the LoPy is correctly connected and in the right orientation.

@kop524 format your post http://commonmark.org/help/ and show exact error message with line number and why you connect your DS18X20 to different pins? You can support few sensors on the same pin. DS18X20 work on onewire protocol. I do not know about which implementation of DS18X20 lib you have but parameter for DS18X20 is onewire bus not pin Pin can not be OUT if you need to read something from it use e.g.: oWire=OneWire(Pin('P22', Pin.PULL_UP)) temp=DS18X20(oWire, True) # you can ommit True if your lib does not have this param

@seb here you are: (sysname='LoPy', nodename='LoPy', release='1.15.0.b1', version='v1.8.6-849-baa8c33 on 2018-01-29', machine='LoPy with ESP32', lorawan='1.0.0') Forget about my code above. I thought this is the problem but it's not. Actually my board freezes when doing wlan operations. However I'm not able to reproduce with a minimum example... Just forget about it. I'll report back once I have a minimum example which shows the issue ... Sorry for bothering ...

@livius Internal antenna was used. The purpose of WiFi interface was to provide web configuration interface accessed from close proximity to the device and it worked surprisingly well with internal antenna transmitting through the aluminium housing. In case of LoPy boards which did not crash of course :).

This error refers to a old firmware version, have you updated to the latest firmware?

@brotherdust thanks for your proposal. It seems the best way to speed up any connection test with the LTE modem. Regarding AT commands, can you suggest me a sequence that worked under same (or similar) technical conditions?

Hi, I've been following this thread, in which had problems with Modbus Serial too: https://forum.pycom.io/topic/2363/lopy-sp3485-modbus-lib-test-register-read-error I've upgraded the uModbus libraries to the latest ones, as well as the LoPy firmware: https://forum.pycom.io/topic/2541/new-firmware-release-v1-15-0-b1/8 After performing these actions both the demo and my code worked again! This thread can be considered solved. Cheers!

@apantano Hi I took a new LoPy+Pysense and I measured the consumption w/o LAN and BT by modifing the boot.py (the main.py is empty) like this Import os import machine from machine import UART from network import WLAN, Bluetooth uart = UART(0, baudrate=115200) os.dupterm(uart) wlan = WLAN() wlan.init(mode=WLAN.STA) wlan.deinit() bt = Bluetooth() bt.deinit() machine.main('main.py') The currrent is 45-46 mA. Probably there is some active resource that I don't know. Thanks Andrea

Hi, RTS and CTS remove ( also the LED one ). Performed a couple of reset, the deep mode still consume 70-80 ma. During wake up it rise to 240 ma, 80 - 84 ma during boot and main. Does the sigfox init library routine ( or socket ) without send anything cause power drain? Do you suggest to init LTE modem and then deinit? ( Anyway if you write in the boot.py insert LTE.init() and LTE.deinit() one after the other, Fipy stuck you need to remove the lines above, maybe a small delay can help. ) Thanks, Andrea

@rkeiii Version 1.15.0b1 now contains the utimeq module and a slightly changed utime module, which matches the needs of the uasyncio lib. The only change needed to the lib is swapping the arguments of the single utime.ticks_diff() in usanycio.core.py.

Hello, The problem with this particular device is that it was flashed with a LoPy firmware instead of a LoPy4 firmware. Cheers, Daniel

@Xykon , thanks. Btw are there any advantages of using libusbK? cos I used USB Serial(CDC) driver ( when flashing from zadig ) and it works well. I see the COM port and I can use Atom/Pymakr to program. With libusbK, I wasn't sure how to connect from Atom as there is no longer a serial port available.