MicroPython Forum (Archive)

Now I'm on earlier version of things (by some weeks) with some of my own code glued on which ought not to matter but when I run the client.py it connects once, transfers OK and subsequently doesn't. I feel that there's some internal resource that's obviously not being released. It also shows why UDP...

Since Micropython on this platform executes not much faster than BASIC on a BBC Micro if you want sub 1uS you'll need to write it in C. You could cheat and pretend it's an SPI device and clock out something using that.

Jon

It is far better to catch the thing you want to catch (socket.timeout and maybe other OSErrors) and leave other exceptions alone rather than the way you have written it for the simple reason is if you call this from something else in a loop you have now stopped the KeyboardInterrupt so the outer loo...

Generally socket calls throw OSErrors or something derived from them.

As said don't catch everything or it'll include KeyboardInterrupts as well and that'll get annoying.

The other mistake is to catch exceptions and carry on silently as if everything is ok.

Jon

May I suggest the same test written in C to determine whether the problem is MicroPython (as implemented on the ESP).

Jon

Dwight makes a good point. Do not use the term "crash". Say what happened where it deviates from what was expected. Would also be good if you confirmed the power supply arrangement and any local decoupling (which as I have said you really ought to have). How long (time and data) does it typically ru...

Yes of course TCP has transmission timeouts. I though it was to do with inactivity. My mistake. Yesterday was one of those days. I locked myself out due tue a keyring error later on. Anyway the problem with network code is that 1) it is tricky and often misunderstood anyway and 2) This device's netw...

Hate to spoil things but TCP itself has no timeout unless you enable keepalives. SMBus is more about not paying royalties and maybe cranking up the speed a little. As is TWSI and PMBus. Once you've checked the voltage and frequency and (unlikely) 10-bit addressing they're all the same. Very few devi...

The ESP consumes about 80mA and gets a little warm as expected and no problem at all even over a long cable and lots of hubs as long as there is a little local supply decoupling. If something is hot rather than warm there's something very wrong. (Most modern electronics for the most part works perfe...

It's a very very sad state of affairs indeed when a device capable of transferring the odd gigabyte without keeling over is considered in anyway satisfactory. No wonder the banks are in the state they are. Perhaps I'm getting too old for this. (Supplying through USB is absolutely fine but you must h...