-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #19 from YuyueBalabala/main-api-en
doc: add en_US api doc and modify en_US directory.
- Loading branch information
Showing
11 changed files
with
862 additions
and
41 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# HTTP API | ||
|
||
NeuronEX provides management and monitoring REST APIs that conform to the OpenAPI (Swagger) 3.1 specification. | ||
|
||
Once the NeuronEX service is started, you can access http://localhost:8085/api-docs/index.html to view the API documentation. You can also try executing some of the APIs directly in the Swagger UI. | ||
|
||
This section will guide you on how to get started with the NeuronEX REST API quickly. | ||
|
||
[JWT authentication:](./jwt.md) The API uses JWT authentication to ensure secure communication and authentication between IIoT platforms or monitoring applications and NeuronEX devices. This enhances the overall security of the system. | ||
|
||
[Data type description:](./data-type.md) To ensure that data is represented and interpreted clearly and consistently, the API describes the data types used. This facilitates seamless integration and analysis of data in IIoT platforms or monitoring applications. | ||
|
||
[Data collection function error code description:](./error-code.md) The API includes comprehensive error code descriptions that provide information about the nature and cause of the errors encountered. This helps with effective troubleshooting and issue resolution. | ||
|
||
[API documentation:](https://docs.emqx.com/en/neuronex/latest/api/api-docs.html) Includes the relevant APIs for system, data collection, and data statistics functions. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,116 @@ | ||
# Data collection function data types | ||
|
||
## Concepts | ||
|
||
### Node | ||
|
||
In NeuronEX, each node can connect to a device or a northbound application. | ||
|
||
* In the device node, you can add and manage device tags. | ||
* In the northbound node, you can select the data groups that you need to subscribe to. | ||
|
||
### Group | ||
|
||
You can create multiple data groups under each node to categorize tags. For example, if a device is connected to multiple temperature sensors and multiple humidity sensors, you can create two data groups, temperature and humidity to categorize the collected tags. NeuronEX uploads the collected data to the northbound application by group. | ||
|
||
### Tag | ||
|
||
You can create multiple collection tags under each group. For example, if a temperature sensor collects multiple temperature values, each temperature value is a tag. | ||
|
||
### Plugin | ||
|
||
In NeuronEX, each plugin corresponds to an implementation of a protocol. For example, one Modbus TCP protocol corresponds to one plugin, and the MQTT protocol corresponds to one plugin. | ||
|
||
## Data types | ||
|
||
* INT8 = 1 | ||
* UINT8 = 2 | ||
* INT16 = 3 | ||
* UINT16 = 4 | ||
* INT32 = 5 | ||
* UINT32 = 6 | ||
* INT64 = 7 | ||
* UINT64 = 8 | ||
* FLOAT = 9 | ||
* DOUBLE = 10 | ||
* BIT = 11 | ||
* BOOL = 12 | ||
* STRING = 13 | ||
* BYTES = 14 | ||
* ERROR = 15 | ||
* WORD = 16 | ||
* DWORD = 17 | ||
* LWORD = 18 | ||
|
||
## Serial port | ||
|
||
### Baud rate | ||
|
||
* 115200 = 0 | ||
* 57600 = 1 | ||
* 38400 = 2 | ||
* 19200 = 3 | ||
* 9600 = 4 | ||
* 4800 = 5 | ||
* 2400 = 6 | ||
* 1800 = 7 | ||
* 1200 = 8 | ||
* 600 = 9 | ||
|
||
### Parity | ||
|
||
* NONE = 0 | ||
* ODD = 1 | ||
* EVEN = 2 | ||
* MARK = 3 | ||
* SPACE = 4 | ||
|
||
### Stop bit | ||
|
||
* Stop_1 = 0 | ||
* Stop_2 = 1 | ||
|
||
### Data bits | ||
|
||
* Data_5 = 0 | ||
* Data_6 = 1 | ||
* Data_7 = 2 | ||
* Data_8 = 3 | ||
|
||
## Tag attributes | ||
|
||
* READ = 0x01 | ||
|
||
* WRITE = 0x02 | ||
|
||
* SUBSCRIBE = 0x04 | ||
|
||
## Node | ||
|
||
### Node type | ||
|
||
* DRIVER = 1 | ||
* APP = 2 | ||
|
||
### Node control | ||
|
||
* START = 0 | ||
* STOP = 1 | ||
|
||
### Node status | ||
|
||
* INIT = 1 | ||
* READY = 2 | ||
* RUNNING = 3 | ||
* STOPPED = 4 | ||
|
||
### Node connection status | ||
|
||
* DISCONNECTED = 0 | ||
* CONNECTED = 1 | ||
|
||
## Plugin type | ||
|
||
* STATIC = 0 | ||
* SYSTEM = 1 | ||
* CUSTOM = 2 |
Oops, something went wrong.