A neqto.js library is a built-in class developed in neqto.js.
Various functions for the control of sensors and devices connected to NEQTO devices, connection to external cloud services, and algorithms are provided as libraries.
A neqto.js library can be accessed directly from the user script in which it is added without the need for calling methods such as "require" in node.js.
For information on adding libraries to Scripts, refer here.
Library usage requirements
Library usage requirements are defined for each library.
|Library usage requirements|
|Type||Library type categorized by function|
|Name||Library name (Built-in class name)|
|Version||Release version of the library|
|Code size used||The script code size used by the library|
|Resources used||The neqto.js object resources required by the library|
|UART||Libraries that use UART interface|
|I2C||Libraries that use I2C interface|
|Utils||Libraries for general purpose functions|
|Integrations||Libraries for connecting to external clouds|
Upgrades of library versions will not change or remove any methods or property specifications that have already been released, and compatibility will be maintained.
There are no dependencies between library versions and NEQTO Engine firmware versions and compatibility is maintained, though it is still recommended to use the latest versions for both.
Code size used
Added libraries will be combined with the user script and passed to the NEQTO Engine. Therefore, the sum of the script code size used by the libraries and the user script code size on the script editor must not exceed the maximum code size supported by neqto.js.
In addition, even if an added library is not used in the user script, it will still consume user script code area, and thus should only be added when necessary.
Ensure in advance that the resources required by a library are available on the NEQTO Engine and NEQTO device to be used. If a library is used when the resource requirements are not met, an exception will be raised.
When using a library, it is necessary to ensure that resources do not conflict with non-library processing.