@jcaron Isn't this the opposite of what what stated here: Not completely the opposite, it's still more efficient to use a regulated 3.3V supply (low voltage forces the onboard regulator into bypass ECO mode) But it needs to be updated to reflect that 3.3V should be applied to the 5V/VIN pin. Is the Pysense/Pytrack sending power to the module via 5V Yes, all the various shields implementing deep sleep control the *py board's 5V rail

@seb A) FiPy+PyTrack+LiPo-Battery (Not-Attached-to-USB3.0) 
Vin = 4.09~4.10 V 3V3 = 3.32 V B) PyTrack+USB-Serial-device (Attached-to—USB3.0) same port as A)
 Vin = 4.85 V 3V3 = 0.23 V C) PyTrack+USB-Serial-device (Attached-to—USB3.0) + Hotswap-in-FiPy same port as A) & B)
 Vin = 4.55 V 3V3 = 3.32 V D) PyTrack+FiPy+NO-USB-Serial-device (Attached-to—USB3.0) same port as A) & B) & C) same combo as C) Just unplugged USB from PyTrack, and re-attached it…
 Vin = 1.69~2.51 V 3V3 = 1.15~1.91 V Also, worth nothing is that if my hand slips with the measuring probes, I get it to “boot-up” by accidentally shorting GROUND & 3V3, and I get a USB-Serial-Devices on my computer [ergo like A), B) & C) …] … And then, I get the same Vin & 3V3 as C) Which makes me conclude that you’ve guys have a Firmware issue!!! … and not a “bad usb-cable” or “bad usb-port” … etc etc. For some reason, in the boot-sequence of the PyTrack Firmware, it choose not to boot-up FiPy and enable USB-Serial … And, again, it’s odd that I can short GROUND & 3V3 with my measuring probes, and then it boots up FiPy and enables USB-Serial…

@mj Depends on the antenna an it's set-up. With a short wavelength/4 antenna, I had values between 25 and 39 dBm, even depending on how I was placing myself. The wavlength/4 antennas are typicall about 10cm (4") long, whereas wavelength/2 antennas have a length of about 20 cm (8").

@charly86 said in New firmware release v1.18.0: cardgenerator @iwahdan Nice, but that's not my PR so I don't want to get any credit for it ;-) Are you still facing this issue? @charly86 said in New firmware release v1.18.0: @iwahdan Nice, but that's not my PR so I don't want to get any credit for it ;-)

@abhishek2101 That's good. besides that, make yourself familiar with ftp (file transfer protocol), who's only purpose is to transfer files. That avoids any copying errros.

@iwahdan There is another branch now called stable_update. I understand that this is the trial update to 1.18.1.rx. I left a note there on one of the newer commits. Having a note somewhere about the intention of each branch would be helpful.

@jcaron You are absolutely correct on all points: I jest read yesterday that ESP32 has ULP (Ultra Low Power mode) so it makes sense that FiPy will have something like that as well... another field for me to research. But for now I assume that I will not be using deep sleep. About detecting motion: really good point - however my FiPy sits on Expansion Board 3.1 that I believe does not have accelerator...another hurdle... Meanwhile, I did discover something useful that will allow me to experiment with mAh consumption with ease. Check this thread: https://forum.pycom.io/topic/5694/measuring-amperage-consumption BTW, I am using GNSS Click 5 from uBlox with NEO-M8N with cold start of under 30 sec.

Hey @frederik-Leys, the LoPy does not have an LTE Modem so lte = LTE() should be have no effect on LoPy but und FiPy it should start the modem. Change your code to: import pycom import machine import time from network import LTE from network import WLAN wlan = WLAN() lte = LTE() time.sleep(5) lte.init() wlan.deinit() pycom.heartbeat(False) print(pycom.heartbeat_on_boot()) print(pycom.lte_modem_en_on_boot()) print(pycom.pybytes_on_boot()) print(pycom.smart_config_on_boot()) print(pycom.wdt_on_boot()) print(pycom.wifi_on_boot()) #colors in hexadecimal (0xRRGGBB) pycom.rgbled(0x00FF00) # Red time.sleep(1) lte.deinit() machine.deepsleep(40*1000) To get in uA range. Or let it run in powersave mode like: import pycom import machine import time from network import LTE from network import WLAN wlan = WLAN() lte = LTE(psm_period_value=1, psm_period_unit=LTE.PSM_PERIOD_1H, psm_active_value=5, psm_active_unit=LTE.PSM_ACTIVE_2S ) print(lte.psm()) time.sleep(5) lte.init() wlan.deinit() pycom.heartbeat(False) print(pycom.heartbeat_on_boot()) print(pycom.lte_modem_en_on_boot()) print(pycom.pybytes_on_boot()) print(pycom.smart_config_on_boot()) print(pycom.wdt_on_boot()) print(pycom.wifi_on_boot()) #colors in hexadecimal (0xRRGGBB) pycom.rgbled(0x00FF00) # Red time.sleep(1) lte.deinit(detach=False, reset=False) machine.deepsleep(40*1000) which brought me to 300uA.

@robert-hh said in Pymakr 1.1.13 does not work with VSCode 1.60.0: @jchernandez mpremote has a --help option. For copying files, you have to use the cp subcommand. So as example for copying a file to the board: mpremote connect /dev/ttyUSB0 cp myfile.py :myfile.py or just mpremote connect /dev/ttyUSB0 cp myfile.py : for using : as a shortcut for the baord's local directory and . for the PC's one. Copying back similar as: mpremote connect /dev/ttyUSB0 cp :myfile.py myfile.py or mpremote connect /dev/ttyUSB0 cp :myfile.py . The device names at Windows are similar COM3, COM4, .... Shortcuts are: u0 for connect /dev/tty/USB0 Unfortunately the mount command of mpremote does not work with the PyCom version of MicroPython. That version is too old. To run a local script without copying it to the board use the run command. If you do not enter a command after the connect, mpremote opens a REPL session cat mario And before I forget it: With Pycom devices and WiFi active you can always use FTP for copying files. A good FTP client is FileZilla. But some file managers allow using FTP paths as well. User name is micro, password is python. you can review the .py file, i think it has that problem

Hi @daniel, Is the work still in progress or have been abandoned?

@bucknall For SIgfox backend registration I beleive I need to put the ID and and PAC out put from with hexlifiy print("ID ", ubinascii.hexlify(sigfox.id())) print("PAC ", ubinascii.hexlify(sigfox.pac())) in my case is: ID b'004e3d90' PAC b'c957cd18b7848c0' so ID that I typed is '004e3d90' and PAC 'c957cd18b7848c0' The device seems to be registered but on backend device webpage I can not see it online at all. How I do I know when is connected to the (Luxembourg) Sigfox network and will get online? It is done immediately or shall I wait?

I just want to remind that this issue remains unsolved on 1.6.13.b1 Counter 1: 10009 Counter 2: 6449 Counter 3: 12757 Counter 1: 10024 Counter 2: 6459 Counter 3: 12778 Counter 1: 10040 Counter 2: 6470 Counter 3: 12798 Counter 1: 10055 Counter 2: 6480 Counter 3: 12818 Counter 1: 10070 Counter 2: 6490 Counter 3: 12838 Counter 1: 10086 Counter 2: 6501 Counter 3: 12858 Counter 1: 10101 Counter 2: 6511 Counter 3: 12878 Counter 1: 10116 Counter 2: 6521 Counter 3: 12899 Counter 1: 10132 Counter 2: 6531 Counter 3: 12919 Counter 1: 10147 Counter 2: 6541 Counter 3: 12939 Guru Meditation Error of type InstrFetchProhibited occurred on core 0. Exception was unhandled. Register dump: PC : 0xffffffff PS : 0x00060a30 A0 : 0x800eb2f0 A1 : 0x3ffe1f50 A2 : 0x3ffe28d0 A3 : 0x00000001 A4 : 0x00000000 A5 : 0x3ffe1f70 A6 : 0x00050823 A7 : 0x00000000 A8 : 0x800eb2ac A9 : 0x3ffe1f30 A10 : 0x3ffe28d0 A11 : 0x00000001 A12 : 0x00000000 A13 : 0x3ffe1f70 A14 : 0x00000003 A15 : 0x00060823 SAR : 0x00000012 EXCCAUSE: 0x00000014 EXCVADDR: 0xfffffffc LBEG : 0x400f753a LEND : 0x400f7543 LCOUNT : 0x00000000 Backtrace: 0x7fffffff:0x3ffe1f50 0x400eb2f0:0x3ffe1f70 0x400dccb8:0x3ffe1fa0 0x400e1672:0x3ffe1fc0 0x400d8244:0x3ffe2050 ================= CORE DUMP START ================= ...

@jmarcelino [Solved ] Resolved, used a different power supply unit and it worked. I guess even though I was getting enough juice of 3.3VDC out of the Expansion board with a LoPy current was not enough. Thanks much!

@robert-hh Yes, it looks like better choise. You could try if the figure changes if you add a smaller pull-up resistor, like 4k7 Ohm. I use already 4k7.

@cduplouy I am also getting around 15mA during deepsleep. I tried with 3.3v and 3.7v using resistor but then it is not sufficient power for the pycom to run.

Hello! I am having issue with activating using method otaa lopy with ttn gateway fot US915. whats correct code i should use I searched a lot of topics over weekend and could not find correct code. Thank you Same time using ttn node US915 with ttn gateway activation worked as shown.

@dicktonyboy You could check, whether P2 is connected at least to the RGB Led. It is one of the connections faced to the LoPy Shield, opposite to P2. [image: 1526890778035-lopy.jpg]

@jcaron Of course!

@jcaron I think that this was @tttadam's conclusion.

@stevo52 Yes, from the distance, it sounds like a hardware problem with the board. Maybe a broken wire or a bad solder point at the P2 pin.