Yes, most 3D files are available at github.com/pycom/footprints in the pycom.pretty folder

@robert-hh But it's funny that mainly the Fritzbox has the problem. Something must be different.

The most common issue here is using a USB charging cable that does not support a communication link. Make sure you have a USB cable with all conductors present :-) Next to that you can check the device manager to see if the COM port is created correctly, sometimes (rarely) Windows will have driver issues where the board gets assigned the wrong driver. Let me know! Gijs

@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.

@kiltedpython There is also size_check.sh, application.mk. You have to create board subdirectories and change the respective partition map files to get actually space for larger images. For WiPy3, you can use e.g. LoPy4 as template.

@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?

Bist du weitergekommen? Ich suche vergebens nach einer Lösung die API von pushsafer anzusprechen. Leider kann der Betreiber von Pushsafer hier nicht unterstützen.. Grüße Clyde

@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)