MicroPython Forum (Archive)

spookyrufus wrote: ↑

Tue Jan 26, 2021 8:07 pm

Divergentti wrote: ↑

Tue Jan 26, 2021 7:57 am

Reason is most likely Post of Finland

What are the chances.. I'm across the gulf, in Tallinn. Terve fellow micropythonist!

Heipä hei ja hauska tavata! Some dark and clear nights I can see Tallin's lights from here

Most likely it is missing. Code you might be interested https://github.com/divergentti/airquality/tree/main/esp32/esp32-mhz19-ili9341-touchscreen Thanks for this pointer also. I have ordered a new display from AliExpress (unfortunately there aren't many for sale where I live and shipping from Amazo...

You can connect several SPI slaves to the same SPI BUS. Just activate them alternatively with CS. You may have to switch speed. Thank you @Roberthh for this information. Currently I am using 1.2 MHz for the touchscreen digitizer (VSPI) and I guess 1.31250 MHz is something what I shall use for the S...

Most likely it is missing. Code you might be interested https://github.com/divergentti/airquality/tree/main/esp32/esp32-mhz19-ili9341-touchscreen most likely better display drivers exists, but I used that. I hit into memory issues and decided to leave keyboard etc interaction with user away. Connect...

Update: Problem was bad DUPONT patch cable connectors! You can use them once, then throw them away! Touchscreen with the interrupt works just fine. If you need to debug, check behavior by adding print just after "def int_press" and then print just after "if buss is not None:". Normal operations show...

Thank you @jimmo and @pythoncoder! I am getting there. At least I know what is wrong. For testing I added to the toucscreen driver https://github.com/divergentti/airquality/blob/main/esp32/esp32-mhz19-ili9341-touchscreen/XPT2046.py simple self.pressed status flag, what I continuously monitor in the ...

I am strugling with a touch screen interrupt handler in this code https://github.com/divergentti/airquality/blob/main/esp32/esp32-mhz19-ili9341-touchscreen/main.py Idea is to replace interrupt handler for each setup screen, which seems to work fine, but initial interrupt handler: self.xpt.int_handle...

for some reason after power on boot returned bytearray is like bytearray(b'\x00\x00\xa2\xff\x86\x01\x9a=\x00') but when UART works it is like bytearray(b'\xff\x86\x01\xfd=\x00\x00\x00?') where first FF is the key for proper reading. b'\x00\x00\xa2\xff\x86\x01\x9a=\x00' b'\xff\x86\x01\xfd=\x00\x00\x...

for some reason after power on boot returned bytearray is like bytearray(b'\x00\x00\xa2\xff\x86\x01\x9a=\x00') but when UART works it is like bytearray(b'\xff\x86\x01\xfd=\x00\x00\x00?') where first FF is the key for proper reading. b'\x00\x00\xa2\xff\x86\x01\x9a=\x00' b'\xff\x86\x01\xfd=\x00\x00\x...

Looking into the code you linked, I would do the init of the UARTs differently. so e.g. instead of: self.sensor = UART(uart) self.sensor.init(baudrate=9600, bits=8, parity=None, stop=1, rx=rxpin, tx=txpin) I recommend to use a single statement: self.sensor = UART(uart, baudrate=9600, bits=8, parity...