@robert-hh Thanks I agree busy-waiting is bad, my understanding was that machine.idle() would give other threads/interrupts the opportunity to run. That code was added to aid the debugging, to see activity while waiting for the network layer to configure itself. I've substituted your code but unfortunately it hasn't changed the networking behaviour - still no IP layer connectivity.

@andreas said in Pytest integration: Dear @Summer, pytest itself will probably never work on MicroPython. You might also want to follow the discussion at [1]. However, we have been working on building a test harness for our Terkin Datalogger based on pytest just a few days ago, see [2]. The main job was to apply appropriate mocking to the MicroPython ESP32 HALs and to make different modules from the MicroPython standard library compatible with CPython. So, the test harness will not run on the device itself, but within a regular CPython. Let me know what you are aiming at and if I can support you in any way. In fact, I was planning to put all generic parts into a different package so it can be reused by others. With kind regards, Andreas. [1] https://github.com/pfalcon/pycopy-lib/issues/49#issuecomment-603875987 [2] https://github.com/hiveeyes/terkin-happy wheels-datalogger/tree/master/test Thank u for the good informations! It's working!

@Dezert754 You have to connect the GND of both devices and a Pin of the Wipy set as Output to a Pin of the Arduino set as Input. The cables should not be long, and adding a resistor of 4.7kOhm into the wire does not hurt. Since the WiPy runs at 3.3 V and the Arduino at 5V, the level at the Arduino for a high is specified as 3.5V, so it's not sure if it works. Better use a level converter.

well, right now I only have access to win10. Is there any solution for windows 10?

@robert-hh Okay, thanks for your help.

@stanschultz Also very useful: https://github.com/zsquareplusc/mpy-repl-tool

@momentaj When using the pycom uploader 1.15.2, you have tghe option to erase the device on uploading a new firmware image.

@alvaroav Hey glad its working. I've raised it in the team so hopefully the fixes will get ported into the next pybytes firmware release.

@robert-hh Works like a charm, thank you so much!

@robert-hh Top

Any news?

You are sending POST requests. but looking for GET paramaters in the PHP script. use $_POST (or $_QUERY) not $_GET. Sie senden POST-Anfragen. Suchen Sie jedoch nach GET-Parametern im PHP-Skript. Verwenden Sie $ _POST (oder $ _QUERY) und nicht $ _GET.

@modellhaus I suggest you two things for help, the first is to modify your post and please enclose your code in correct code balise ( </> tool in line above )to help reading . The second thing is to post the error message and line number where it happen to help analysis.

In case someone else comes along looking for a solution to this problem. Simply add this callback before the while loop: def char_notify_callback(char): char_value = (char.value()) print("Got new char: {} value: {}".format(char.uuid(), char_value)) And update the char condition: if ((char.properties()) & (Bluetooth.PROP_NOTIFY)): characteristic.callback(trigger=Bluetooth.CHAR_NOTIFY_EVENT, handler=char_notify_callback, arg=None)

@jimmie glad that copy and paste is your biggest problem :)

Hi! You can use this command line tool: https://hackmd.io/s/HJhUcamxQ#