Loading files with Coolterm is easy - just set a 300ms (max) delay in Coolterm on output - I paste in large fles and have them uploaded without issue. Any command except accessing the terminal fails, for example: nodemcu-tool mkfs -connection-delay 1000 (it uses the project settings file. There, a very useful program called CooltTerm receives the data and saves it into a. I have a Wemos D1 mini, followed instructions on (cloud build service, NodeMCU PyFlasher, and nodemcu-tool based on Node.js). After a certain time (standard is 4h) the results are sent to a PC. g/n HT40 Wi-Fi transceiver, so it can not only connect to a WiFi network. Basically, the the program counts signals from the gasmeter and does some arithmetics with it. If nothing new appears, I would think of hardware or connectivity problem, otherwise a driver issue. Typing in your web browser (ESP8266 IP address)/TestPrint4 you will see the. You can do it opening Device Manager, expanding Ports (COM&LPT) and checking what you see there before and after you connected the device. Not IDE, but you can use you favorite editor and upload lua script to ESP8266 flash with luatool Check if when you connect your board via USB a new device is detected. There is a python app to do this via a PC TCP/IP server to a client esp8266 which is nice for net updating but for testing scripts a terminal type IDE might be pleasant.ĭo we have a terminal type IDE available? In this way *.lua files could be edited with a PC editor and uploaded to update the esp8266 lua scripts. IDE would also choose and configure the comm port. Luatool: from wrote: picstart1 wrote:OK the only issue that is a little tiresome is with the rs232 interface ( ex a Coolterrn Windows app and a usb to comm port) lua files need to be typed in.Īn IDE that allows the *.lua file to be read in and uploaded in a way that doesn't overrun the '>' esp8266 prompts would be less tiresome. Unless I've missed something, further HW troubleshooting would require deeper knowledge of the board and advanced tools.ESP8266App(python): from wrote:I am using python build a lib,features:Ģ.using python xconsole into run LUA script.ģ.using xcon_tcp.py to run LUA through wifi connection.Ĥ.tcp/udp server/client for debug and auto-testing. Check if LED would blink and/or use FTDI programmer connected on RX-TX pins. Another check would be connecting 3.3 V source to the corresponding pin directly.In the end my laziness foced me to use my 2.0 front panel. Also worth trying connecting it to another PC - captain obvious. My troubleshooting (with NodeMCU 12-E, V3): I tried plugging it after removing the driver from the Device Manager in Windows 10, reinstalling the (CH341SER) driver and 3 cable swaps. Also an obvious one to make sure your cable has data lines and not just a charging cable. Don't underestimate the last one, using dodgy cables or adapters (like to USB-C) can result in brownout of your ESP ending up without receiving enough power. Simply trying to plug your board in different port or using different cable. For hardware problem easiest would be to check cable and usb port functionality.If nothing new appears, I would think of hardware or connectivity problem, otherwise a driver issue. Check if when you connect your board via USB a new device is detected.If as you said LED won't even flash ones as it should upon getting power, it is likely a hardware (HW) or wiring issue.I can think of several issues including that you board is not working.
0 Comments
Leave a Reply. |