It is the reference to the class variable TIMEOUT_US in the __init__ method.
def __init__(self, trigger_pin, echo_pin, echo_timeout_us=HCSR04.TIMEOUT_US):
Delete the class name HCSR04 from the default value.
def __init__(self, trigger_pin, echo_pin, echo_timeout_us=TIMEOUT_US):
Search found 29 matches
- Thu Jun 08, 2017 4:44 pm
- Forum: ESP8266 boards
- Topic: HCSR04 module usage
- Replies: 3
- Views: 3853
- Tue Apr 25, 2017 6:28 pm
- Forum: General Discussion and Questions
- Topic: Jupyter notebook kernel from adafruit
- Replies: 2
- Views: 3880
Jupyter notebook kernel from adafruit
Hi, just in case you did not notice already. Tony D. from adafruit has made a kernel wrapper for jupyter notebook that allows to interact with micropython on MCUs. I have tested so far with pyboard, esp8266 and esp32 boards. I really like it, as it allows to take notes and code and test incrementall...
- Thu Feb 09, 2017 5:42 pm
- Forum: ESP8266 boards
- Topic: 1.8.7 fails to install
- Replies: 17
- Views: 16261
Re: 1.8.7 fails to install
I can somehow reproduce your problem when flashing with --flash_size=8m on a 4MB board.
When i flash with --flash_size=32m it is working.
Sorry i have no more ideas what could be wrong.
When i flash with --flash_size=32m it is working.
Sorry i have no more ideas what could be wrong.
- Thu Feb 09, 2017 11:53 am
- Forum: ESP8266 boards
- Topic: 1.8.7 fails to install
- Replies: 17
- Views: 16261
- Thu Feb 09, 2017 6:01 am
- Forum: ESP8266 boards
- Topic: 1.8.7 fails to install
- Replies: 17
- Views: 16261
Re: 1.8.7 fails to install
This is reproducable. After flashing without -fm dio: Fatal exception (28): epc1=0x4000228b, epc2=0x00000000, epc3=0x00000000, excvaddr=0x000000b5, depc=0x00000000 Fatal exception (28): epc1=0x4000228b, epc2=0x00000000, epc3=0x00000000, excvaddr=0x000000b5, depc=0x00000000 Fatal exception (28): epc1...
- Wed Feb 08, 2017 5:07 pm
- Forum: ESP8266 boards
- Topic: 1.8.7 fails to install
- Replies: 17
- Views: 16261
Re: 1.8.7 fails to install
I had the same issue when trying to burn the latest firmware to a new Amica nodeMCU board.
Adding -fm dio to the write_flash did help.
Adding -fm dio to the write_flash did help.
Code: Select all
esptool.py --port /dev/ttyUSB0 erase_flash
esptool.py --port /dev/ttyUSB0 --baud 115200 write_flash -fm dio 0 ../esp8266-20170208-v1.8.7-205-g181f7d1.bin
- Sun Nov 20, 2016 7:04 pm
- Forum: General Discussion and Questions
- Topic: Can a python script know when webrepl is open?
- Replies: 5
- Views: 5888
Re: Can a python script know when webrepl is open?
Hi, i'm having similar problem with a sensor board in development. I use the following approach to get into webrepl when i need to. I have connected Pin 12 to ground normally and when i need to update the board i connect the pin to high. flag = Pin(12, Pin.IN) if flag.value() == 1: print("starting w...
- Sun May 22, 2016 10:52 am
- Forum: ESP8266 boards
- Topic: Progress with resolving WebREPL issues
- Replies: 2
- Views: 4334
Re: Progress with resolving WebREPL issues
We're having a good progress with debugging WebREPL issues, and by now fixed two issues: 1) after 5-6 WebREPL connections, a module went unstable; 2) unable to connect more than 5 times via WebREPL (these seemed to be the same issue, but turned out to be 2 separate ones). ... MicroPython v1.8-95-gb...
- Sun May 15, 2016 7:47 am
- Forum: ESP8266 boards
- Topic: Reading VCC level
- Replies: 2
- Views: 4227
Re: Reading VCC level
I came across this topic when playing with LUA and NodeMCU.
There was a discussion in the Espressif BBS http://bbs.espressif.com/viewtopic.php? ... dd33#p2922.
Perhaps this is helpful.
There was a discussion in the Espressif BBS http://bbs.espressif.com/viewtopic.php? ... dd33#p2922.
Perhaps this is helpful.
- Sat May 14, 2016 4:25 pm
- Forum: ESP8266 boards
- Topic: MemoryError when importing a custom module
- Replies: 44
- Views: 44408
Re: MemoryError when importing a custom module
I tried to rebuild and reflash everything from scratch several times but I simply get "access denied" from the webREPL every time I try to type in the webREPL password (and yet the password is the right one as I type it just before at the initialisation step). Apparently it's wrong, or you discover...