MicroPython Forum

+1. I'm sure it's great but without Linux support it's no use to me. Or a lot of other developers and makers.

I'm not a Windows user but as a general point the version of cross compiler should match the version of firmware. This is because the bytecode format is subject to change, giving rise to the error message you're seeing.

... Looking forward to the asyncio compatible mqtt code as well! I've made progress with this. I have an asynchronous version of umqtt.robust which has survived testing so far. But I'd be interested to hear comments from yourself or anyone else on this issue. I don't think that umqtt.robust handles...

After removing the jumper you need to reset or power cycle the board.

I've yet to figure that out. I look forward to reading it

Neat! Forcing a garbage collection might give a more accurate figure in cases where unreferenced objects remain on the heap: def free(full=False): gc.collect() F = gc.mem_free() A = gc.mem_alloc() T = F+A P = '{0:.2f}%'.format(F/T*100) if not full: return P else : return ('Total:{0} Free:{1} ({2})'....

Your DRIVE class has a number of instances of return mode As far as I can see this variable doesn't exist (you have self.mode). What I don't understand is why you haven't seen an error message. When you test the robot, have you got a means of viewing the output at the REPL? Either via a USB interfac...

What version of firmware are you running?

This is a query about the Python language rather than anything specific to MicroPython. There are plenty of books and online tutorials which can help you and I suggest getting familiar with the language on a PC. In essence if your program stops for any reason (e.g. running to completion or throwing ...

Error no. 9 is a standard Python code for a bad file number (defined in errno.py). Maybe -78 is something PyCom specific?