MicroPython Forum (Archive)

mad474 wrote:Test rig briefly fried together.

Veeeery clever, kudos!

nui_de wrote:here's the first really cheap board I found, looks nice
https://www.itead.cc/psf-a85.html

Yep, I also ordered a few of those. Now I need to learn to solder such tiny stuff...1/20'' pin width, sigh.

I can confirm that NodeMCU runs out-of-the-box on this SoC: http://frightanic.com/iot/nodemcu-esp82 ... ect-match/ This probably means that MicroPython for the ESP8266 will also work just fine on the ESP8285.

Due to space reasons, there’s no floating point support, and no math module. This sentence is in docs/wipy/general.rst I know but I haven't found out what makes the /wipy/library/math.html path appear. You've got to search for 'math' in the docs for that URL to become available. It's not in the lef...

The docs are misleading and inconsistent indeed. At https://micropython.org/resources/docs/en/latest/wipy/wipy/general.html it clearly says Due to space reasons, there’s no floating point support, and no math module. I'll create an issue at https://github.com/micropython/micropython/issues as I have...

That's what I asked myself when I looked at the available functions. If you're implicitly saying that there's really no math module on the WiPy, which would make sense to me, then why is it in the docs?

According to https://micropython.org/resources/docs/en/latest/wipy/library/math.html there's a math module (I know, no floating point though). Yet, when I run import math the answer is File "<stdin>", line 1, in <module> ImportError: module not found Since Google didn't turn up anything helpful when...

I appreciate your feedback, thanks. So far "IoT" primarily meant ESP8266+NodeMCU for me. So your world doesn't feel familiar yet

Isn't (one of) the issue with that main loop that prototyping in the REPL is a dead end? You can't edit anything anymore once the loop has been set in motion.

I finally sat down and started tinkering with the WiPY I helped fund on Kickstarter last year. (Micro)Python is all new to me. There's documented debounce function for the pyboard that can easily be adapted for use on the WiPy. http://www.eng.utah.edu/~cs5780/debouncing.pdf#page=19 isn't really fond...

My WiPy is in the extension board which is connected via USB to my MacBook running OS X 10.9.5. I put from machine import UART import os uart = UART(0, baudrate=115200) os.dupterm(uart) into boot.py, triggered a reset i.e. reboot but there's no /dev/tty.usbmodem* device. I haven't found any other me...