Changes for page 01 Lua Functions

Last modified by Theodore Xu on 2023/10/26 10:51

From version 5.12
edited by Stone Wu
on 2022/07/12 09:40
Change comment: (Autosaved)
To version 5.10
edited by Stone Wu
on 2022/07/12 09:30
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -958,17 +958,20 @@
958 958  
959 959  Parameter:
960 960  
961 -* //Topic//, topic name
962 -* //Message//, content
961 +//Topic//, topic name
963 963  
964 -**2."arrived" is published by publish, this function will be called after the publication arrives**
963 +//Message//, content
965 965  
965 +**2.**"arrived" is published by publish, this function will be called after the publication arrives
966 +
966 966  //Callback// prototype~:// function ()//
967 967  
968 -Parameter: None
969 +Parameter:
969 969  
970 -**3.This function will be called after the "offline" connection is lost**
971 +None
971 971  
973 +**3.**This function will be called after the "offline" connection is lost
974 +
972 972  //Callback// prototype~:// function (string cause)//
973 973  
974 974  Parameter:
... ... @@ -982,13 +982,17 @@
982 982  Failed: multi
983 983  
984 984  (((
985 -== **mqtt:setup_cfg()** ==
988 +== **4.11 mqtt:setup_cfg()** ==
986 986  )))
987 987  
988 -**Function:** Cloud mode interface, to obtain MQTT information configured by the cloud platform
991 +**Function:**
989 989  
990 -**Parameters:** None
993 +Cloud mode interface, to obtain MQTT information configured by the cloud platform
991 991  
995 +**Parameters:**
996 +
997 +None
998 +
992 992  **Return:**
993 993  
994 994  //serverurl, clientid, conn, lwt, cart //(5 returns, respectively, server address, client ID, connection table, last word table, certificate table)
... ... @@ -1006,27 +1006,39 @@
1006 1006  Lua only has a table data structure, so all arrays and key-value objects of json will be returned as a table.
1007 1007  
1008 1008  (((
1009 -== **json.encode( lua_object )** ==
1016 +== **5.1 json.encode( lua_object )** ==
1010 1010  )))
1011 1011  
1012 -**Function: **Convert lua data type to json string
1019 +**Function:**
1013 1013  
1014 -**Parameters: **Lua data type (including boolean, number, string, table)
1021 +Convert lua data type to json string
1015 1015  
1016 -**Return:** Json format string
1023 +**Parameters:**
1017 1017  
1025 +Lua data type (including boolean, number, string, table)
1026 +
1027 +**Return:**
1028 +
1029 +Json format string
1030 +
1018 1018  (((
1019 -== **json.decode(string json_string)** ==
1032 +== **5.2 json.decode(string json_string)** ==
1020 1020  )))
1021 1021  
1022 -**Function:** Convert json string to lua data type
1035 +**Function:**
1023 1023  
1024 -**Parameters: **//json_string//, string of json data structure
1037 +Convert json string to lua data type
1025 1025  
1026 -**Return: **Lua data type
1039 +**Parameters:**
1027 1027  
1041 +//json_string//, string of json data structure
1042 +
1043 +**Return:**
1044 +
1045 +Lua data type
1046 +
1028 1028  (((
1029 -== **json.null** ==
1048 +== **5.3 json.null** ==
1030 1030  )))
1031 1031  
1032 1032  **Function:**
... ... @@ -1033,24 +1033,32 @@
1033 1033  
1034 1034  This method is used when assembling json data, which is equivalent to null in json. If the user directly uses json.null() to return the address of the function, it must be valid with the use of encode.
1035 1035  
1036 -**Parameters:** None
1055 +**Parameters:**
1037 1037  
1038 -**Return: **None
1057 +None
1039 1039  
1059 +**Return:**
1060 +
1061 +None
1062 +
1040 1040  = **6 Cloud mode** =
1041 1041  
1042 1042  The cloud interface is only used in cloud mode, and V-NET mode is not available.
1043 1043  
1044 1044  (((
1045 -== **bns_get_alldata()** ==
1068 +== **6.1 bns_get_alldata()** ==
1046 1046  )))
1047 1047  
1048 -**Function:** Obtain all monitoring points (point table) data configured by the end user
1071 +**Function:**
1049 1049  
1050 -**✎Note: **Assuming there are timing scripts A and B with a period of 1 second, if this function is called in script A, the data will not be obtained if called in script B
1073 +Obtain all monitoring points (point table) data configured by the end user
1051 1051  
1052 -**Parameters:** None
1075 +Note: Assuming there are timing scripts A and B with a period of 1 second, if this function is called in script A, the data will not be obtained if called in script B
1053 1053  
1077 +**Parameters:**
1078 +
1079 +None
1080 +
1054 1054  **Return:**
1055 1055  
1056 1056  Succeed: table two-dimensional array, the structure is as follows
... ... @@ -1080,11 +1080,13 @@
1080 1080  Failed: //table// empty table
1081 1081  
1082 1082  (((
1083 -== **bns_get_config(string from)** ==
1110 +== **6.2 bns_get_config(string from)** ==
1084 1084  )))
1085 1085  
1086 -**Function:** Obtain custom configuration parameters with the specified from type
1113 +**Function:**
1087 1087  
1115 +Obtain custom configuration parameters with the specified from type
1116 +
1088 1088  **parameter:**
1089 1089  
1090 1090  from type, there are the following two categories, the string must be all lowercase
... ... @@ -1102,11 +1102,13 @@
1102 1102  Failed~:// table// empty table
1103 1103  
1104 1104  (((
1105 -== **bns_get_data(string name, string data)** ==
1134 +== **6.3 bns_get_data(string name, string data)** ==
1106 1106  )))
1107 1107  
1108 -**Function:**write data to the name of the monitoring point
1137 +**Function:**
1109 1109  
1139 +write data to the name of the monitoring point
1140 +
1110 1110  **parameter:**
1111 1111  
1112 1112  //name //The name of the monitoring point
... ... @@ -1120,7 +1120,7 @@
1120 1120  Failed: nil
1121 1121  
1122 1122  (((
1123 -== **bns_get_data(string name)** ==
1154 +== **6.4 bns_get_data(string name)** ==
1124 1124  )))
1125 1125  
1126 1126  **Function:**
... ... @@ -1138,13 +1138,17 @@
1138 1138  Failed: nil
1139 1139  
1140 1140  (((
1141 -== **bns_get_datadesc()** ==
1172 +== **6.5 bns_get_datadesc()** ==
1142 1142  )))
1143 1143  
1144 -**Function: **Obtain all configured communication ports and monitoring point information
1175 +**Function:**
1145 1145  
1146 -**Parameters:** None
1177 +Obtain all configured communication ports and monitoring point information
1147 1147  
1179 +**Parameters:**
1180 +
1181 +None
1182 +
1148 1148  **Return:**
1149 1149  
1150 1150  Succeed: table three-dimensional array, the structure is as follows
... ... @@ -1197,13 +1197,17 @@
1197 1197  Failed~:// table// empty table
1198 1198  
1199 1199  (((
1200 -== **bns_get_machineinfo()** ==
1235 +== **6.6 bns_get_machineinfo()** ==
1201 1201  )))
1202 1202  
1203 -**Function:** get machine information
1238 +**Function:**
1204 1204  
1205 -**Parameters:** None
1240 +get machine information
1206 1206  
1242 +**Parameters:**
1243 +
1244 +None
1245 +
1207 1207  **Return:**
1208 1208  
1209 1209  Succeed: 3 string type results (model, machine code, software version)
... ... @@ -1211,11 +1211,13 @@
1211 1211  Failed: nil
1212 1212  
1213 1213  (((
1214 -== **bns_get_groupdata(string name)** ==
1253 +== **6.7 bns_get_groupdata(string name)** ==
1215 1215  )))
1216 1216  
1217 -**Function:** Get all monitoring point data under the specified group name
1256 +**Function:**
1218 1218  
1258 +Get all monitoring point data under the specified group name
1259 +
1219 1219  **parameter:**
1220 1220  
1221 1221  //Name  // group name
... ... @@ -1227,13 +1227,17 @@
1227 1227  Failed: //table// empty table
1228 1228  
1229 1229  (((
1230 -== **bns_get_groupdesc()** ==
1271 +== **6.8 bns_get_groupdesc()** ==
1231 1231  )))
1232 1232  
1233 -**Function:** Get all group information
1274 +**Function:**
1234 1234  
1235 -**Parameters:** None
1276 +Get all group information
1236 1236  
1278 +**Parameters:**
1279 +
1280 +None
1281 +
1237 1237  **Return:**
1238 1238  
1239 1239  Succeed: //table// two-dimensional array, the structure is as follows
... ... @@ -1247,13 +1247,17 @@
1247 1247  Failed: //table  // empty table
1248 1248  
1249 1249  (((
1250 -== **bns_get_onecache(string msg)** ==
1295 +== **6.9 bns_get_onecache(string msg)** ==
1251 1251  )))
1252 1252  
1253 -**Function:** Save a message to the cache file, which can be stored after power failure. Store up to 2000 items, delete the old and save the new in a rolling manner when it is full.
1298 +**Function:**
1254 1254  
1255 -**Parameters: **//msg// String
1300 +Save a message to the cache file, which can be stored after power failure. Store up to 2000 items, delete the old and save the new in a rolling manner when it is full.
1256 1256  
1302 +**Parameters:**
1303 +
1304 +//msg// String
1305 +
1257 1257  **Return:**
1258 1258  
1259 1259  Succeed: true
... ... @@ -1261,13 +1261,17 @@
1261 1261  Failed: nil
1262 1262  
1263 1263  (((
1264 -== **bns_get_allcache()** ==
1313 +== **6.10 bns_get_allcache()** ==
1265 1265  )))
1266 1266  
1267 -**Function:** Get all the cached content (once the internal cache file will be emptied)
1316 +**Function:**
1268 1268  
1269 -**Parameters:** None
1318 +Get all the cached content (once the internal cache file will be emptied)
1270 1270  
1320 +**Parameters:**
1321 +
1322 +None
1323 +
1271 1271  **Return:**
1272 1272  
1273 1273  Succeed: //table// one-dimensional array
... ... @@ -1295,57 +1295,11 @@
1295 1295  Network communication includes Http request interface, this document does not provide interface description, please refer to the online document for how to use it.
1296 1296  
1297 1297  (((
1298 -== **http request** ==
1351 +== **7.1 http request** ==
1299 1299  )))
1300 1300  
1301 1301  [[http:~~/~~/w3.impa.br/~~~~diego/software/luasocket/http.html#request>>url:http://w3.impa.br/~~diego/software/luasocket/http.html#request]]
1302 1302  
1303 -== **https request** ==
1304 -
1305 -Example:
1306 -
1307 -{{code language="LUA"}}
1308 -local json = require("json")
1309 -
1310 -local https = require("https")
1311 -
1312 -functions https_demo.main()
1313 -
1314 -local url = "https://XXXXXXXXXXXXXXXXXXXXXXXXXX"
1315 -
1316 -local body = {}
1317 -
1318 -body["XXXXXX"] = "XXXXX"
1319 -
1320 -body["XXXXXXX"] = "XXXXXXXXXXX"
1321 -
1322 -local bodyJson = json.encode(body)
1323 -
1324 -local header = {}
1325 -
1326 -header["content-type"] = "application/json"
1327 -
1328 -local result_table, code, headers, status = https.request(url,
1329 -
1330 -bodyJson)
1331 -
1332 -if code == 200 then
1333 -
1334 -print("https suc")
1335 -
1336 -return true
1337 -
1338 -else
1339 -
1340 -print("https fail")
1341 -
1342 -return nil
1343 -
1344 -end
1345 -
1346 -end
1347 -{{/code}}
1348 -
1349 1349  (((
1350 1350  = **8 Internal register** =
1351 1351  )))
... ... @@ -1352,32 +1352,32 @@
1352 1352  
1353 1353  The internal registers of the box are divided into bit addresses and word addresses, which can be accessed in two ways (taking HDW as an example):
1354 1354  
1355 -**Access by word, prefix @W_HDW.**
1362 +**~1. **Access by word, prefix @W_HDW,
1356 1356  
1357 1357  For example: @W_HDW0 represents the first word of the system data area, @W_HDW1 represents the second word of the system data area.
1358 1358  
1359 -**Access in bit mode, the prefix is @B_HDX, the number in front of "." indicates the number of the word, and the number behind is the bit number of the word.**
1366 +**2. **Access in bit mode, the prefix is @B_HDX, the number in front of "." indicates the number of the word, and the number behind is the bit number of the word.
1360 1360  
1361 1361  For example: @B_HDX1020.12, its meaning is to access the system data area in bit mode, the specific location is the 13th bit of the 1020th word.
1362 1362  
1363 -(% class="box errormessage" %)
1364 -(((
1365 1365  **✎Note: **
1366 -)))
1367 1367  
1368 -* The address in @B_HDX is taken from the word in @W_HDW, so pay special attention when using the address.
1369 -** For example, @B_HDX1020.12 is to access the 13th bit of the 1020th word. The value of this bit is the same as the word obtained by @W_HDW001020. The 13th bit of this word is actually the same bit as @B_HDX1020.12.
1370 -* The address of the bit address @B_HDX has a decimal point, while the word address is an integer.
1372 +**~1. **The address in @B_HDX is taken from the word in @W_HDW, so pay special attention when using the address.
1371 1371  
1374 +For example, @B_HDX1020.12 is to access the 13th bit of the 1020th word. The value of this bit is the same as the word obtained by @W_HDW001020. The 13th bit of this word is actually the same bit as @B_HDX1020.12.
1375 +
1376 +**2.**The address of the bit address @B_HDX has a decimal point, while the word address is an integer.
1377 +
1372 1372  (((
1373 -== **Data storage area(HDW/HDX)** ==
1379 +== **8.1 Data storage area(HDW/HDX)** ==
1374 1374  )))
1375 1375  
1376 1376  The system storage area (HDW) of the V-BOX is used to store temporary data:
1377 1377  
1378 -1. Access by word, the number range is: "@W_HDW0"-"@W_HDW299999".
1379 -1. Access in bit mode, the number range is: "@B_HDX0.0"-"@B_HDX299999.15".
1384 +~1. Access by word, the number range is: "@W_HDW0"-"@W_HDW299999".
1380 1380  
1386 +2. Access in bit mode, the number range is: "@B_HDX0.0"-"@B_HDX299999.15".
1387 +
1381 1381  (((
1382 1382  == **8.2 Special data area (HSW/HSX)** ==
1383 1383  )))