@cts WiPy supports a Pin interrupt, which can be triggered with the rising edge. Look in the documentation for "Pin". And is has a timer module, which could be used for setting the gate time. Look in the documentation at "Timer". However, the precision and speed is very limited. Without testing, I would assume that it works reliably only for frequencies below 1 kHz, with a uncertainty of the gate time of about 1 ms. I

@Xykon @Tomjuarez Please remember to check the voltage of the FTDI cable. It states that it is 3v3 but the VCC pin is actually at 5 V, confusingly! I have made this mistake and it may destroy your device! Thanks! Alex

@kutysam Hmm ok! One of our engineers is having a look at it today so I'll keep you posted!

@ColombianAus Did you tried assigning same procedure to all pins? p_in1.callback(Pin.IRQ_FALLING | Pin.IRQ_RISING, pin_handler) p_in2.callback(Pin.IRQ_FALLING | Pin.IRQ_RISING, pin_handler) p_in3.callback(Pin.IRQ_FALLING | Pin.IRQ_RISING, pin_handler) ... you then can distinguish pins by arg.id() and e.g. Pin.module.P9.id()

You cannot use the pycom updater for a Wipy 1.x. These have to be updated via OTA. Images and instructions are on the micopython.org web site. There is also the forum for that product.

Oops the answer was to reboot after installing those drivers and now it appears to work. :)

@kop524 No clue. But card access of Wipy/Lopy is slow, so there ist no need to use a fast card.

@RobTuDelft ok fair enough. so Following code should work right? import time from machine import Pin import machine import pycom pycom.heartbeat(False) def toggle_rgbled_blue(arg): pycom.rgbled(0xff) time.sleep(2) pycom.rgbled(0) def toggle_rbgled_red(arg): pycom.rgbled(0x7f0000) time.sleep(2) pycom.rgbled(0) button_blue = Pin('P10', mode=Pin.IN, pull=Pin.PULL_UP) button_blue.callback(Pin.IRQ_RISING, toggle_rgbled_blue) buton_red = Pin('P0', mode=Pin.IN, pull=Pin.PULL_UP) button_red.callback(Pin.IRQ_RISING, toggle_rgbled_red) Cheers Colombian

if the error code changes it certainly is another error. No clue what -1 means, sorry.

@AustinBeau yes i wrote this line from memory - fixed in post, thanks :) IP is 192.168.4.1 and rest default www.pycom.io and then micro python like here https://docs.pycom.io/pycom_esp32/pycom_esp32/getstarted.html#initial-configuration-atom

@duffo64 (Ops... must wait 10 minutes before posting again). I have upvoted your post to prevent this ;-)

@jmarcelino I managed to get the firmware version. It is 1.6.7.b1. Is this a stable version? Do I still have to upgrade it? Thank you

@achide I do not use pymakr but if i understand screen correctly you put it into \flash\lib\connections but you should into \flash\lib

Yes. I disable the heartbeat and set a color as part of the BLE initialization.

@robert-hh from what I found in the documents of the ssd1306 the following commands are also required (or are at least different from default) for cmd in ( MEMORY_ADDR, 0x00, DISP_START_LINE | 0x00, SEGMENT_MAP, 0X00, MULTIPLEX_RATIO, 63, Vcom_DESELECT, 0x30, CONTRAST, 0xFF, ENTIRE_ON, NORM_INV, ): anywho in the end it is a syntax problem with the I2C bus. I don't know if the correct syntax for sending long byte-array operations can be included here If it were it would have been crazy helpful for me.

see my topic if you are still interested: https://forum.pycom.io/topic/1344/wipy-2-0-blynk/6

@robert-hh - Yes, thanks, I am using that on the esp8266 ( see my first code snippet df() ) and it works just fine, what I am asking is how can I get the freespace on the pycom port as statvfs() is not available ?

@iotmaker yes, current firmware thanks for the report https://github.com/pycom/pycom-micropython-sigfox/issues/19

@robert-hh, great! I'll give it a shot tonight.

@smssms According to the log the WDT module only became available this past Friday in version 1.7.2. https://forum.pycom.io/topic/1326/firmware-release-1-7-2-b1