NodeMCU-Tool | : wrench : Upload Manage Lua files on NodeMCU

by AndiDittrich JavaScript Version: 3.2.1 License: MIT

X-Ray Key Features Code Snippets(1)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | NodeMCU-Tool Summary

NodeMCU-Tool is a JavaScript library typically used in Programming Style, Arduino applications. NodeMCU-Tool has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i nodemcu-tool' or download it from GitHub, npm.

NodeMCU Tool allows you to. directly from the command line.

Support

Quality

Security

License

Reuse

Support

NodeMCU-Tool has a low active ecosystem.

It has 275 star(s) with 47 fork(s). There are 10 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 55 have been closed. On average issues are closed in 67 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of NodeMCU-Tool is 3.2.1

Quality

NodeMCU-Tool has 0 bugs and 0 code smells.

Security

NodeMCU-Tool has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

NodeMCU-Tool code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

NodeMCU-Tool is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

NodeMCU-Tool releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions are not available. Examples and code snippets are available.

NodeMCU-Tool saves you 15 person hours of effort in developing the same functionality from scratch.

It has 43 lines of code, 1 functions and 28 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed NodeMCU-Tool and discovered the below as its top functions. This is intended to give you an instant insight into NodeMCU-Tool implemented functionality, and help decide if they suit your requirements.

Parse debug options .
Upload a local file to remote server
Fetches the current device .
start a file transfer
Connect to serial serial port .
upload a file
connect to serial serial serial port
Download a remote file
show filesystem info
write chunk to file

Get all kandi verified functions for this library.

NodeMCU-Tool Key Features

No Key Features are available at this moment for NodeMCU-Tool.

NodeMCU-Tool Examples and Code Snippets

Cant upload to the NodeMCU Lua

JavaScript

Lines of Code : 2

License : Strong Copyleft (CC BY-SA 4.0)

Copy

sudo npm install --unsafe-perm nodemcu-tool -g

Community Discussions

Trending Discussions on NodeMCU-Tool

Unable to load Lua Scripts to NodeMCU: Invalid node.chipid()

How do you compile Lua code on ESP8266 Board?

QUESTION

Unable to load Lua Scripts to NodeMCU: Invalid node.chipid()

Asked 2019-Sep-22 at 13:39

For all of these scenarios, I am able to upload the firmware and monitor via serial usb. But after creating my first firmware, for all new firmware, I can't upload Lua scripts using the nodemcu-tool without getting the following:

Error Message

...

ANSWER

Answered 2019-Sep-09 at 08:03

fetchDeviceInfo() first calls node.info() at https://github.com/AndiDittrich/NodeMCU-Tool/blob/master/lib/connector/device-info.js#L9. Then it does an if-else to figure out whether it's running on ESP8266 or ESP32.

With the recent upgrade to SDK 3.0 node.info() was changed in PR #2830. See documentation at https://nodemcu.readthedocs.io/en/latest/modules/node/#nodeinfo. It now returns values the script doesn't consider to be coming from ESP8266. The script then calls node.chipId() in the else branch. So, it's getting a chip id from ESP8266 but it is expecting one from ESP32. Hence, the exception.

I have no idea what "Response: 6935962" means. Is that my chip id or an error code?

It's your chip id.

To cut a long story short: NodeMCU-Tool needs to be adjusted as laid out above to work with the current NodeMCU version.

Source https://stackoverflow.com/questions/57843851

QUESTION

How do you compile Lua code on ESP8266 Board?

Asked 2019-Mar-06 at 13:00

The node module has a method named compile that compiles the code and creates .lc files.

Do I use a tool like nodemcu-tool to connect to the board via the terminal parameter, and execute node.compile('myfile.lua') commands to create .lc files?

If init.lua is compiled as init.lc upon reset will the board execute the compiled code?

...

ANSWER

Answered 2019-Feb-22 at 09:05

How do you compile lua code on ESP8266 Board?

That depends on the tools you use. The workflow I'd use is:

Upload Lua code to NodeMCU using nodemcu-uploader
Connect to the NodeMCU using picocom
Compile the file using node.compile()
(optional) Download the file again using nodemcu-uploader

Different tools may change the involved steps slightly, but overall the idea will remain the same:

upload -> compile (-> download)

If init.lua is compiled as init.lc upon reset will the board execute the compiled code?

Try it ;)

If it doesn't work, you can always just write a one-line init.lua that require init.lc; it's not like that would impact your performance once your chip is booted and running.

Or you could just rename the compiled file to init.lua and it should also work.

But keep in mind, as the documentation says: