@spacelggo PIL is designed for Python 2.x and not supported on MicroPython. Also much of it's functionality relies on native low level libraries we don't have. There are plans to to offer image manipulation functions but I can't offer a date at this point.

@spacelggo I do not remember what was the cause of slowness you can try to find info on the forum. I suppose that this was releated directly with SD driver not SPI itself. Someone tested this i do not tested this myself. I use always direct connection and built in driver.

@incognico said in Reading BNO055: Maybe try adding some lower value pullup resistors. From the FAQ page of your device BNO055 FAQ #4 "Depending on your system setup, you might need to adjust the pullups on the SCL and SDA lines to be a bit stronger. The BNO055 has very tight timing requirements on the I2C bus, requiring short setup and rise times on the signals. By default the breakout board has 10K pullups, which might be too weak on some setups." I had a similar problem. I'm not sure if it's been fixed or not, because I haven't tested it lately. Anyway, it had to do with I2C Clock Stretching. For me the solution was to set the I2C baud rate as low as it would go and work my way up until i found the fastest value that worked. Maybe give that a try, if you haven't already. =)

@livius That is funny, because I had this work for 2 months before having issues. Now they seem sporadic. I am worried a sensitivity is now showing itself. But we will see after more testing. thanks

Solved: just needed to increase the timeout to 2 seconds before setting machine.pin_deepsleep_wakeup(['P3'],machine.WAKEUP_ALL_LOW, True) and then going into deepsleep

@fsergeys when the callbackfunction is triggered wait for 100ms,then check the status of the input-if it is still pulled to low then the button is pressed,else the button is not pressed and you jump out of the callbackfunction. the reason the callbackfunction is triggered multiple times is the bouncing of the mechanical contact of the switch.

@tenspot said in Bluetooth BL Client won't connect: bt.connect from network import LoRa from network import Bluetooth import machine import socket import pycom import binascii bluetooth = Bluetooth() bluetooth.start_scan(10) adv = None while True: adv = bluetooth.get_adv() #if adv and bluetooth.resolve_adv_data(adv.data, Bluetooth.ADV_NAME_CMPL) == 'JonathanBLE': try: #print(bluetooth.resolve_adv_data(adv.data, Bluetooth.ADV_APPEARANCE)) bluetooth.connect (b'\xe0\x00\xc3\xca\x16\xf9') #JonathanBLE mac adress? Is this the wrong way to connect using the mac adress.. ? I connect to the BLE with the name and it connect in seconds... but I want to be able to connect to devices using there mac adress instead... Im using LOPY btw ... and I want to try send data between 2 LOPY decies with BLE...

@d2xhale said in What is needed to link up with WiPy 2?: The LCD I plan to use is just a 2 digit screen, so I'm looking for a unit that is a little smaller I do not know details about your project but starting point and final point many times provide different result :) e.g. you start with two digit but maybe better is OLED ;-) You can draw there what you need and show more details on it. [image: 1517426396482-d20a35f7-ed42-41ad-87e4-b19587b9f809-image.png]

@jimsmith2354 VSC + Pymakr https://forum.pycom.io/topic/1512/pymakr-visual-studio-code-released

ok,i will try!

@livius Thanks for the Chrono snippet. I'm always glad to find these nicely packaged design patterns.

@semireg Thank a lot, looks great. Good call on catching the descriptor write in modbt.c We'll review it and it should make into the next release.

@semireg We'll have a look to see if there's a bug in the socket implementation.

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

@titusece Those are connected to pins on the ESP32 which cannot drive output signals [image: 1513962622702-c692c62f-970f-4bf9-98a3-67d5b7ea4524-resized.jpeg] http://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf