You rock.

@Bryan Hello Bryan, you also asked on the micropython.org board, which is the right forum for your problem. I placed an answer there, which may fix your issue.

@BetterAuto When set to Pin.IN, the pin can be used for input only. changing the output value does not affect it's state. A pin declared as Pin.OPEN_DRAIN can be used for input AND output, but needs an Pull-Up resistor for a high value. When set to high, the output stage does not drive the pin any more, and the input value can be read, if that is driven by the peripheral. It's a of wired or for the low value. This method is used e.g. by I2C.

@jmarcelino Thank you for detailed answer

@tobz https://www.sparkfun.com/products/11189 Or one of the many others (look for MAX3232 on Aliexpress or EBay for example)

Hello, Thanks for pointing out this bug. It has been fixed on the latest release 1.7.1.b1. Cheers, Daniel

@amartinez for server node it is not good to have while not wlan.isconnected(): time.sleep_ms(50) You do not connect wifi here only you start Access Point (AP) - look if it start on network list scan on client node side or your PC

Hello, any update on this? I have some old modbus plc lying around and i'm trying to use my lopy to communicate as a modbus master with a SP3485 breakout board...but i cannot find a decent modbus library for micropython

@pwest We've found out how. On iBeacon, when you read the data you get an Array. You need to do int(lastHexValue, 16) and then -256. This results in the set TxPower the BLE Beacon has Edit: this site explains very well how the iBeacon protocoll is built, aswell as to where to find the TxPower: http://www.warski.org/blog/2014/01/how-ibeacons-work/

I managed to find a USB-to-serial adapter and tried some things with that. My Windows machine won't recognize it, and on my mac I can't figure out what tty port it's on. I did however dig out a Raspberry Pi where it seem to work. Unfortunately it didn't help, because the linux-version of the pycom updater just keeps saying "Something failed trying to connect to the device." and then gives no further info. I also tried modifying the baud rate in the updater.py script as some thread suggested, but no luck.

Ah derp. yeah that works. I'm new to (micro)python & coding for hardware, so learning lots at the moment. Thanks.

@Brunus Did you try to set a long server timeout with server.timeout(86400) Which for instance will set the timeout to a full day.

@Arkaik classic way always work ;-)

Solved! These are the right drivers to install! http://www.ftdichip.com/Drivers/D2XX.htm

Hi @bucknall, I finally found this library for using queues on micropython. However, this library need collections.deque and uasynio.core. 1 from collections.deque import deque 2 from uasyncio.core import sleep I went to the github repository, I downloaded collection.deque but I couldn't find uasynio.core anywhere. I think I'm not importing libraries correctly because I need to modify the line from collections.deque import deque to from collections import deque So now I would like to find the uasyncio.core module to be able to use the queue library ^^ I hope I do not need to open a new thread for this question. If so, I'm sorry ;)

Hi @amartinez, There's a really good explanation about GATT (Generic Attribute Profile) here - https://learn.adafruit.com/introduction-to-bluetooth-low-energy/gatt Currently BLE is the protocol available but classic Bluetooth will be coming in the future! Thanks!

@tenspot No problem! :) It was likely that you had a very old version of the firmware tool installed!

Tidied things up a bit and added some constants to make it 'easier' to see what is going on, may get round to writing a module to for the MCP23017. Any guidance on what the interfaces should look like any where would be useful..? #!/usr/bin/python # # This program is free software: you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the Free # Software Foundation, either version 3 of the License, or (at your option) # any later version. # # This program is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY # or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License # for more details. # # You should have received a copy of the GNU General Public License along # with this program. If not, see <http://www.gnu.org/licenses/> # I2CBUS = 0x00 # I2C bus number (Always 0 on WiPy) ADDRESS = 0x20 # I2C address of I/O expander. IODIRA = 0x00 # Port A data direction register. IODIRB = 0x01 # Port B data direction register. IPOLA = 0x02 IPOLB = 0x03 GPINTENA = 0x04 GPINTENB = 0x05 DEFVALA = 0x06 DEFVALB = 0x07 INTCONA = 0x08 INTCONB = 0x09 IOCON = 0x0A GPPUA = 0x0C GPPUB = 0x0D INTFA = 0x0E INTFB = 0x0F INTCAPA = 0x10 INTCAPB = 0x11 GPIOA = 0x12 # Port A data register. GPIOB = 0x13 # Port B data register. OLATA = 0x14 OLATB = 0x15 from machine import I2C # Initialize I2C bus i2c = I2C(I2CBUS, I2C.MASTER, baudrate=100000) # Configure all pins on Port A and B as outputs. i2c.writeto_mem (ADDRESS, IODIRA, bytes([0x00, 0x00])) # Send 0xf0 to Port A data register (GPIOA) i2c.writeto_mem (ADDRESS, GPIOA, bytes([0xf0])) # Clear all outputs and reset data direction bits. i2c.writeto_mem (ADDRESS, GPIOA, bytes([0x00,0x00])) i2c.writeto_mem (ADDRESS, IODIRA, bytes([0x00, 0x00])) I was going to post something slightly more useful, but had a hardware problem that has stopped me developing anything further for now (think it was just a broken jumper cable but I haven't had time to do any more yet).

OK so heres what I have found. On one board it works if connected directly to 3.3v, the onboard regulater seems to be not working. The other board has the ChipPU pin pretty much low all the time -- about 400mv, goes to 0v when the button is pressed. putting a pullup on that pin doesn't help, it seems to be shorted. So that board is in permanent reset.