@hobbypy any programming language with a serial library should work. simply open a serial connect to the board via your preffered language / framework. and send the code as a string over it. The response will come back over serial just like the REPL does.

@crumble said in Lopy freezes after 6 - 12 hours: I do not understand why pycom does not declare the 1.20 branch as stable. It fixed so many errors for me that I like to see it as the stable branch. Maybe they want to deploy it together with some cloud changes. But 23 will be the better number for this ;) Features are still being worked on and improved. Even more stability cant hurt :D

Hi, I tried via ftp and it works perfectly. Regards

@hopkapi If you connect G24 aka P3 -> 7 G11 aka P4 -> 6 GND -> 8 GND Vin -> 2 (5V) and run the LoPy from USB. then the electrical conditions shoul be OK, and the device shoudl be accessible via UART 1. SOmetimes the definition of Tx and Rx are reversed, so you may swap P3 and P4. That should not cause any harm to the devices. The UART setting according to the data sheet is baud rate: 9600, databits: 8, stopbits: 1, parity: no Some test code would be like: from machine import UART uart = UART(1, 9600) # init with given baudrate uart.init(9600, bits=8, parity=None, stop=1) # init with given parameters while True: data = uart.readall() if data is not None: print(data)

I found out what was the problem: not the cable, not the up to date expansion board3, but simply the out-of-date lopy4 firmware. Updating it fixed it!

@ricardo85 I think you’ll need to use the C API and ESP-IDF directly for that, see https://github.com/MrBuddyCasino/ESP32_MP3_Decoder. That should run on the Pycom boards

@pierrot10 which model of the expansion board arte you using. Version 2 (one push button) or version 3 (two push buttons). Version 2 is more simple. If you cannot see the serial port, it is a problem of the physical connection (cable, jumpers on the board) or the OS X driver. Version 3 adds to the list of trouble sources the firmware in the PIC controller on the board. I assume that you also do not get a REPL prompt.

@jcaron I think I got it The calibrate_rtc() in library pycoproc break the console output, if I comment this call from get_sleep_remaining() No problem Connecting on COM24... # OK! starting, Reset= 0 stage 1 stage 2 Wakeup reason: 4 ; Aproximate sleep remaining: calibrate_rtc 0 sec stage 4 Wait for update ............. may be the deal is out there def calibrate_rtc(self): # the 1.024 factor is because the PIC LF operates at 31 KHz # WDT has a frequency divider to generate 1 ms # and then there is a binary prescaler, e.g., 1, 2, 4 ... 512, 1024 ms # hence the need for the constant self._write(bytes([CMD_CALIBRATE]), wait=False) self.i2c.deinit() Pin('P21', mode=Pin.IN) pulses = pycom.pulses_get('P21', 100) self.i2c.init(mode=I2C.MASTER, pins=(self.sda, self.scl)) idx = 0

@monersss Raw LoRa is a best effort medium with absolutely no acknowledgements or retransmissions. If you want to be sure that data has been received, you will need to implement such a strategy. That involves adding frame counters (not absolutely needed in the most basic case, but it’s usually a good idea), sending back ACKs when you have received data, and resending data if you don’t get the ACK. Note that if your target scenario is not point to point but multiple senders to one receiver, LoRAWAN may be a simpler option as this can be handled by LoRaWAN. However be aware of the limitations on the band.

@monersss Can you post a sample of the file stored on the SD card? I programmed the first lopy to constantly send hello, and this was my result: Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello ...

@seb Yup, that solved it

Hello guys, The issue fixed in the IDF is definitely affecting us. We will merge that patch and will be available for our next release this week. Cheers, Daniel

@testos As long as you do not use SPI this does not matter. And the SPI pins can be reassigned too. And P11 (External IO 8) seems not to be connected on pytrack. Using I diode tester, I cannot detect any connection. At P10 (external IO 7) seems to be used. At least is show something like a ESD diode behavior of an active chip pin.

@livius It features a MAX3421E USB host controller chip and USB-A port. We created this board to communicate with existing serial-over-USB (CDC, or communications device class) devices. Adding support for other USB "drivers" is a matter of understanding the USB endpoints and writing the implementation in MicroPython. Update: Check out the First look: USB Host Expansion Board by Semireg

@jmpratt Would you mind providing me a link for the hardware you used? I was thinking of using the RS485 library and a 485 to uart breakout board.

Thank you. Everything works now. I hope that pymakr will be fixed as well.