@stefan85e MicroPython - as used on the Pycom boards - would count as a different implementation from CPython

@meven What you advised: "python -m pip install pycom" is working for me also, thank you However next, I got this error: "[pylint] E1101:Module 'pycom' has no 'heartbeat' member" but I could ignore it by: # pylint: disable=maybe-no-member pycom.heartbeat(False) pycom.rgbled(0xffff00)

Hi @jhollan3 Pylint and the Python extension aren't really meant for MicroPython or the Pycom boards so it'll throw a lot of errors. There's no linter or extension I know of that would work correctly.

hi @stefan85e, Short between G28 and 3V3 it's for safe-boot (booting without executing micropython scrips or loading previous OTA firmware). This is not required. Let's simplify and isolate problems. upload scripts with Atom Here make a simple print("hello") , no UART usage, yet; it should work usage of UART class. Here if you just want to output messages, print() method should be enough. UART 0 is already indirected to P0/P1, thru print(). The second UART (#1), it's for communicating with another device connected to the Expansion Board (not with the USB/FTDI chip).

@robert-hh I know :) it was a pic I took between :) I reinstall it and install latest plugin and atom.version still nothing

Not sure if this could be a possible solution to writing to characteristics, can anyone help me please? https://devzone.nordicsemi.com/f/nordic-q-a/8162/ble-driver-python-concurrent-notifications

@kbman99 This INA169 device is also interesting, because you can set the sensitivity yourself with the appropriate shunt resistor. But the INA219 device @timh mentions is even more interesting, since it takes both voltage and current, and avoids the noisy ADC of the ESP32.

@robert-hh I want to remove the time.sleep and just focus on checking if the packed is sent before sending more so I can max out the send and recv part...

@xykon Thanks. Even if I'm a little bit self-confident, please give it a second thought and a second test.

@ahelllycan I think we would need to see code, or general overview of your process. At the moment we are guessing. But @jcaron is right. You should have a call back on message receive and you choose when to send messages based on other criteria. The rest of the time you will be sleeping or waiting.

Hi, Yes, the way the Pytrack/Pysense/Deepsleep shield sleep works is that they disconnect the power from the module, sensors etc entirely. In the case of the Pysense and Pytrack the USB is also de-initialised meaning you will lose the serial connection, this can make talking to the device difficult if it does not wake up for long The Pytrack/Pysense/Deepsleep shield sleep is a a "deep" sleep rather than a regular sleep. Once you use this, when the module wakes up it will be like it was rebooted. Pycom board do not currently support machine.sleep although this is being investigated. The way this differs from the machine.deepsleep is that this uses external hardware and powers off everything on the board, not just the ESP32 processor. You can still use machine.deepsleep if you desire but note that on the WiPy2, LoPy and SiPy, due to an issue with the way the voltage regulator is connected the deepsleep current draw will be quite high (15mA) If you connect P12 to 3.3v with a jumper cable and wait for the device to wake from sleep you will see the on-board LED blink orange. Once this happens you can disconnect the cable. The device will now "safe boot". This prevents the device from running boot.py and main.py and therefore the code putting the device to sleep. The best way to stay informed of firmware updates is to use the forums subscribe feature for the announcements forum. We will always post in there when a new firmware is released

@stefan85e Have you tried disabling the safe-boot feature, does this work?

Could you try deleting C:\Users\Stefan\.atom\packages\pymakr\ and re-install the pymakr plugin

@jhoguaman You can not. There is no OS on pycom modules. Micropython is the OS. If you build your own firmware, you can write C modules, wich you then can call from Python.

Found my answer after hours of looking around. Found this beautiful post on TTN regarding decoding the values of different types and what have you found here by Arjanvanb on TTN The main answer was posted on Stackoverflow by Ilya Bursov.