@jonaswg I never did that with a newer xxPy device. But I used Wipy 1 in that mode with a Debian Linux computer. If you terminal emulator has flow control, switch that off. The other settings are 115200 baud, 8 bit, no parity. If you push reset at the FiPy, you shoudl at least see some boot messages.

@monersss At the moment, with my example, that happens when you get a timeout. But again, that would require some "out-of-band" signaling, meaning: in addition to the "payload", the jpg file, some control information must be exchanged. And that is part of a protocol. That could be pretty simple. If I grab one out of the air, it could be: Define record types, where the first letter defines the type of the record, followed by 3 bytes record length, followed by the payload, like: 'fnnn': filename (of length nnn) 'd128': data 'x000': done You would first receive 4 bytes, decode type and length, and then receive further 'length' bytes. And for every record received, your LoPy would send a confirmation, like the three bytes: "ok!" or "bad", in case of errors (or just a single byte). That would implement flow control and the EOF signal. It does not have other elements like check sums and sequence control. But you might not need that.

Hi...I haven't found anything short of implementing a significant chunk of the bluetooth protocol stack (which I have no desire to take on).All of the bluetooth modules I've been able to find are similar to the one used by the arduino BT in that they only support one serial connection. smt assembly service

Every update seems to be different. This time, the PyTrack was detected as a COM device. With the same number as before :). But I was not able to connect. To fix it, I had to select show unconnected devices in the device manager, browsed for the usk driver and deleted the unknown and unconnected device.

@monersss Then, start your script with: from network import LoRa import socket import time import os os.dupterm(None) ...

@jcaron It worked! My bad. Didn't even think about that. I erased flash memory and uploaded most recent firmware. Thank you @robert-hh as well. For the future, are there any best practices for connecting/disconnecting, from both a hardware and software standpoint. e.g. my boot.py file: import os from machine import UART uart = UART(0, 115200) os.dupterm(uart) Should I include anything else?

@ccarducci you could enable a for loop running every second, this way you can interrupt your program every second.

hank for your help but i tried hard but didn't succeed so for now i'll go with telnet connection. To do it with my desktop Pc i use my android smartphone with the usb tethear function

A temporary fix: downgrade Pymakr Atom package from version 1.0.2 to version 1.0.1. Curious to know where the problem lies in version 1.0.2 for my LoPy-Pysense combo.

@jacquej1 You should create a new post as your problem is really different from the original I posted to avoid confusing people. That beeing said, I see a typo on address path "/dev/ttyUS0" should be /dev/ttyUSB0" If you want to continue the discussion please create a new topic.

@iber LoPy currently only supports Bluetooth LE GATT protocol which in simple terms is a key/value read+write protocol (like a simple database) and ill suited for streaming serialized data like JSON. You should however be able to make your mobile app write to Bluetooth LE characteristics on the LoPy which then set the WiFi and password. The GATTS example should give you the right idea: https://docs.pycom.io/pycom_esp32/library/network.Bluetooth.html#network.characteristic.events

Hi @adrien3d, Could you please try following the instructions at the bottom of this page, https://atom.io/packages/pymakr? It looks like you're having issues with the serial port module! Let me know if this helps, Alex

@lcgeldenhuys 5000000 https://www.esp32.com/viewtopic.php?t=1285

Yep, Put a 10k and a 0.01uF on the RST to 3.3v and see almost no noise now on the RST pin. Went form running for less than 30 seconds to... well it just seems to keep working now. I am pretty sure the is the same issue, wanted to post to help people like myself in the future.

@Vercellotti a) You must set Putty to "No flow control", 8 N 1 b) Try to exchange RX/TX. (RX to Rx, TX to TX). The labeling is sometimes swapped. c) And yes, you do not need DTR.

@PiAir Thank you for sharing this

Expansion board. Sry for late answers. Must wait 600s between different replies.