Chengdu Ebyte Electronic Technology Co., Ltd
E104-BT10-IPX User Manual
Copyright ©2012–2019
,
C
hengdu Ebyte Electronic Technology Co., Ltd
4-13
4.2.4 Network exception and processing
There are two failure scenarios. Type one: fail to assign netkey; Type two: fail to bind APPkey.
The solution to assign netkey failure is as follows:
To deal with the failure to assign netkey, user needs to repeat the above networking process.
The solution to the failure to bind APPkey is as follows:
Method 1. If the user knows which E104_BT10N device is used, directly restore the E104_BT10N device to the
factory (see details from 3.1.17) and repeat the above networking process again.
Method 2: The serial port reads the next networking address “A” of E104_BT10G (see details from 3.1.6), and then
uses the SIGmesh command to delete the device whose node address is “A minus 3” (see details from3.2 SIG message),
and the above networking process is repeated again.
4.2.5 Remove nodes
The instruction to delete a node can only be sent by E104_BT10G of the current network, and it returns. If it is not
deleted, it is not returned.
See the manual (3.2 SIG message) for instructions and usage details.
4.3 Data format
All data exchanged by the serial port, including parameter configuration, network control, and data transparent
transmission, meet the following format requirements. Any remaining data will be considered invalid and the module will
not respond. The parameter configuration is used for parameter configuration of the current module, the SIG message is a
standard mesh control message defined by sig, and the transparent transmission message is defined by Ebyte.
Length
(
1byte HEX
)
Effective load
(
N byte HEX
)
N
Parameter configuration
SIG message
Transparent transmission message
4.3.1Parameter configuration
The configuration data is used to read and write various parameter information of the module and the device access
operation. The format is as follows:
command
(
1byte
)
Operation code
(
1
byte
)
Data
(
N byte
)
Transmitting
0xC0
0~255
Request data
Receiving
0x40
0~255
Respond data
Notes: The correct configuration operation gets the corresponding response data. If the configuration error returns
an error code, as follows
Error code
Explain
0xFF
Invalid parameter
0xFE
Busy operation