|
@@ -0,0 +1,386 @@
|
|
1
|
+
|
|
2
|
+# 设备连接和设置
|
|
3
|
+
|
|
4
|
+- 把所有设备通过网线**连接到局域网**
|
|
5
|
+- 通过服务器、路由管理器或者IP工具**获取局域网内设备ip**
|
|
6
|
+- **登录设备**:在浏览器输入设备ip和端口号:192.168.0.131:82, 用户名是root, 密码是abc123。
|
|
7
|
+- **设置服务器指向**:在设备界面点击"网络"--“服务器管理”, 输入`mandun_url`,设置服务器指向为`192.168.0.252:8080/ebx-bishop/data/carry`
|
|
8
|
+- **重启服务器**:点击"系统"--"重启"--"执行重启"
|
|
9
|
+
|
|
10
|
+# 宿主环境
|
|
11
|
+
|
|
12
|
+- **安装NetCore2.0.5的服务器宿主环境**:双击`dd-env`目录下`NetCore`目录下的`DotNetCore.2.0.5-WindowsHosting.exe`文件
|
|
13
|
+
|
|
14
|
+# MySQL数据库
|
|
15
|
+
|
|
16
|
+- **安装mysql服务**:双击`dd-env`目录下`mysql`目录下的`NT-mysql-Install.bat`文件。会在服务中多出一个`MysqlServer`服务。
|
|
17
|
+- **修改mysql的配置文件**:打开`dd-env`目录下`mysql`目录下的`my.ini`文件。
|
|
18
|
+```
|
|
19
|
+bind-address=0.0.0.0
|
|
20
|
+port=3306
|
|
21
|
+skip_grant_tables
|
|
22
|
+```
|
|
23
|
+- **启动mysql服务**:双击`dd-env`目录下`mysql`目录下的`NT-mysql-Start.bat`文件。会在进程中多出一个`mysqld.exe`进程。
|
|
24
|
+- **安装Navicat客户端**:双击`dd-tools`下`Navicat Premium_11.2.7简体中文版`目录下的`navicat112_premium_cs_x64.exe`文件,安装完毕再双击`PatchNavicat.exe`文件。
|
|
25
|
+- **连接mysql数据库**:依次点击"连接"、"MySQL",在界面上填写如下:
|
|
26
|
+```
|
|
27
|
+连接名:自定义
|
|
28
|
+主机名或IP地址:localhost
|
|
29
|
+端口:3306
|
|
30
|
+用户名:root
|
|
31
|
+密码:lcDb_!@34%^_Mantunsci
|
|
32
|
+勾选"保存密码"
|
|
33
|
+```
|
|
34
|
+点击"连接测试"。如果连接成功,点击"确定"按钮。
|
|
35
|
+
|
|
36
|
+# Redis缓存数据库
|
|
37
|
+
|
|
38
|
+- **安装redis服务**:双击`dd-env`目录下的`redis`目录下的`NT-redis-Install.bat`文件。会在服务中多处一个`redis-server`服务。
|
|
39
|
+- **启动redis服务**:双击`dd-env`目录下的`redis`目录下的`NT-redis-Start.bat`文件。会在进程中多处一个`redis-server.exe`进程。
|
|
40
|
+- **安装redis客户端**:双击`dd-tools`目录下的`Redis`目录下的`redis-desktop-manager-0.9.3.817.exe`文件。
|
|
41
|
+- **连接redis服务器**:点击`连接到Redis服务器`
|
|
42
|
+```
|
|
43
|
+名字:自定义
|
|
44
|
+地址:127.0.0.1
|
|
45
|
+端口:6321
|
|
46
|
+验证:_ebx_cnto_r_srv
|
|
47
|
+安全:无
|
|
48
|
+```
|
|
49
|
+点击"好"按钮。
|
|
50
|
+
|
|
51
|
+# 创建主数据库teche
|
|
52
|
+
|
|
53
|
+```
|
|
54
|
+数据库名:teche
|
|
55
|
+字符集:utf8mb4--UTF-8 Unicode
|
|
56
|
+排序规则:utf8mbs_general_ci
|
|
57
|
+```
|
|
58
|
+
|
|
59
|
+# 创建用户数据库techeuser
|
|
60
|
+
|
|
61
|
+```
|
|
62
|
+数据库名:techeusr
|
|
63
|
+字符集:utf8mb4--UTF-8 Unicode
|
|
64
|
+排序规则:utf8mbs_general_ci
|
|
65
|
+```
|
|
66
|
+
|
|
67
|
+# 创建定时任务数据库quartznet
|
|
68
|
+
|
|
69
|
+- 创建数据库
|
|
70
|
+```
|
|
71
|
+数据库名:quartznet
|
|
72
|
+字符集:utf8mb4--UTF-8 Unicode
|
|
73
|
+排序规则:utf8mbs_general_ci
|
|
74
|
+```
|
|
75
|
+
|
|
76
|
+- 执行语句
|
|
77
|
+
|
|
78
|
+```
|
|
79
|
+# By: Ron Cordell - roncordell
|
|
80
|
+# I didn't see this anywhere, so I thought I'd post it here. This is the script from Quartz to create the tables in a MySQL database, modified to use INNODB instead of MYISAM.
|
|
81
|
+
|
|
82
|
+
|
|
83
|
+# make sure you have UTF-8 collaction for best .NET interoperability
|
|
84
|
+# CREATE DATABASE quartznet CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
|
|
85
|
+
|
|
86
|
+DROP TABLE IF EXISTS QRTZ_FIRED_TRIGGERS;
|
|
87
|
+DROP TABLE IF EXISTS QRTZ_PAUSED_TRIGGER_GRPS;
|
|
88
|
+DROP TABLE IF EXISTS QRTZ_SCHEDULER_STATE;
|
|
89
|
+DROP TABLE IF EXISTS QRTZ_LOCKS;
|
|
90
|
+DROP TABLE IF EXISTS QRTZ_SIMPLE_TRIGGERS;
|
|
91
|
+DROP TABLE IF EXISTS QRTZ_SIMPROP_TRIGGERS;
|
|
92
|
+DROP TABLE IF EXISTS QRTZ_CRON_TRIGGERS;
|
|
93
|
+DROP TABLE IF EXISTS QRTZ_BLOB_TRIGGERS;
|
|
94
|
+DROP TABLE IF EXISTS QRTZ_TRIGGERS;
|
|
95
|
+DROP TABLE IF EXISTS QRTZ_JOB_DETAILS;
|
|
96
|
+DROP TABLE IF EXISTS QRTZ_CALENDARS;
|
|
97
|
+
|
|
98
|
+CREATE TABLE QRTZ_JOB_DETAILS(
|
|
99
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
100
|
+JOB_NAME VARCHAR(60) NOT NULL,
|
|
101
|
+JOB_GROUP VARCHAR(60) NOT NULL,
|
|
102
|
+DESCRIPTION VARCHAR(250) NULL,
|
|
103
|
+JOB_CLASS_NAME VARCHAR(250) NOT NULL,
|
|
104
|
+IS_DURABLE BOOLEAN NOT NULL,
|
|
105
|
+IS_NONCONCURRENT BOOLEAN NOT NULL,
|
|
106
|
+IS_UPDATE_DATA BOOLEAN NOT NULL,
|
|
107
|
+REQUESTS_RECOVERY BOOLEAN NOT NULL,
|
|
108
|
+JOB_DATA BLOB NULL,
|
|
109
|
+PRIMARY KEY (SCHED_NAME,JOB_NAME,JOB_GROUP))
|
|
110
|
+ENGINE=InnoDB;
|
|
111
|
+
|
|
112
|
+CREATE TABLE QRTZ_TRIGGERS (
|
|
113
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
114
|
+TRIGGER_NAME VARCHAR(60) NOT NULL,
|
|
115
|
+TRIGGER_GROUP VARCHAR(60) NOT NULL,
|
|
116
|
+JOB_NAME VARCHAR(60) NOT NULL,
|
|
117
|
+JOB_GROUP VARCHAR(60) NOT NULL,
|
|
118
|
+DESCRIPTION VARCHAR(250) NULL,
|
|
119
|
+NEXT_FIRE_TIME BIGINT(19) NULL,
|
|
120
|
+PREV_FIRE_TIME BIGINT(19) NULL,
|
|
121
|
+PRIORITY INTEGER NULL,
|
|
122
|
+TRIGGER_STATE VARCHAR(16) NOT NULL,
|
|
123
|
+TRIGGER_TYPE VARCHAR(8) NOT NULL,
|
|
124
|
+START_TIME BIGINT(19) NOT NULL,
|
|
125
|
+END_TIME BIGINT(19) NULL,
|
|
126
|
+CALENDAR_NAME VARCHAR(60) NULL,
|
|
127
|
+MISFIRE_INSTR SMALLINT(2) NULL,
|
|
128
|
+JOB_DATA BLOB NULL,
|
|
129
|
+PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
|
|
130
|
+FOREIGN KEY (SCHED_NAME,JOB_NAME,JOB_GROUP)
|
|
131
|
+REFERENCES QRTZ_JOB_DETAILS(SCHED_NAME,JOB_NAME,JOB_GROUP))
|
|
132
|
+ENGINE=InnoDB;
|
|
133
|
+
|
|
134
|
+CREATE TABLE QRTZ_SIMPLE_TRIGGERS (
|
|
135
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
136
|
+TRIGGER_NAME VARCHAR(60) NOT NULL,
|
|
137
|
+TRIGGER_GROUP VARCHAR(60) NOT NULL,
|
|
138
|
+REPEAT_COUNT BIGINT(7) NOT NULL,
|
|
139
|
+REPEAT_INTERVAL BIGINT(12) NOT NULL,
|
|
140
|
+TIMES_TRIGGERED BIGINT(10) NOT NULL,
|
|
141
|
+PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
|
|
142
|
+FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
|
|
143
|
+REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
|
|
144
|
+ENGINE=InnoDB;
|
|
145
|
+
|
|
146
|
+CREATE TABLE QRTZ_CRON_TRIGGERS (
|
|
147
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
148
|
+TRIGGER_NAME VARCHAR(60) NOT NULL,
|
|
149
|
+TRIGGER_GROUP VARCHAR(60) NOT NULL,
|
|
150
|
+CRON_EXPRESSION VARCHAR(120) NOT NULL,
|
|
151
|
+TIME_ZONE_ID VARCHAR(80),
|
|
152
|
+PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
|
|
153
|
+FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
|
|
154
|
+REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
|
|
155
|
+ENGINE=InnoDB;
|
|
156
|
+
|
|
157
|
+CREATE TABLE QRTZ_SIMPROP_TRIGGERS
|
|
158
|
+ (
|
|
159
|
+ SCHED_NAME VARCHAR(60) NOT NULL,
|
|
160
|
+ TRIGGER_NAME VARCHAR(60) NOT NULL,
|
|
161
|
+ TRIGGER_GROUP VARCHAR(60) NOT NULL,
|
|
162
|
+ STR_PROP_1 VARCHAR(512) NULL,
|
|
163
|
+ STR_PROP_2 VARCHAR(512) NULL,
|
|
164
|
+ STR_PROP_3 VARCHAR(512) NULL,
|
|
165
|
+ INT_PROP_1 INT NULL,
|
|
166
|
+ INT_PROP_2 INT NULL,
|
|
167
|
+ LONG_PROP_1 BIGINT NULL,
|
|
168
|
+ LONG_PROP_2 BIGINT NULL,
|
|
169
|
+ DEC_PROP_1 NUMERIC(13,4) NULL,
|
|
170
|
+ DEC_PROP_2 NUMERIC(13,4) NULL,
|
|
171
|
+ BOOL_PROP_1 BOOLEAN NULL,
|
|
172
|
+ BOOL_PROP_2 BOOLEAN NULL,
|
|
173
|
+ TIME_ZONE_ID VARCHAR(80) NULL,
|
|
174
|
+ PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
|
|
175
|
+ FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
|
|
176
|
+ REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
|
|
177
|
+ENGINE=InnoDB;
|
|
178
|
+
|
|
179
|
+CREATE TABLE QRTZ_BLOB_TRIGGERS (
|
|
180
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
181
|
+TRIGGER_NAME VARCHAR(60) NOT NULL,
|
|
182
|
+TRIGGER_GROUP VARCHAR(60) NOT NULL,
|
|
183
|
+BLOB_DATA BLOB NULL,
|
|
184
|
+PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
|
|
185
|
+INDEX (SCHED_NAME,TRIGGER_NAME, TRIGGER_GROUP),
|
|
186
|
+FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
|
|
187
|
+REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
|
|
188
|
+ENGINE=InnoDB;
|
|
189
|
+
|
|
190
|
+CREATE TABLE QRTZ_CALENDARS (
|
|
191
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
192
|
+CALENDAR_NAME VARCHAR(60) NOT NULL,
|
|
193
|
+CALENDAR BLOB NOT NULL,
|
|
194
|
+PRIMARY KEY (SCHED_NAME,CALENDAR_NAME))
|
|
195
|
+ENGINE=InnoDB;
|
|
196
|
+
|
|
197
|
+CREATE TABLE QRTZ_PAUSED_TRIGGER_GRPS (
|
|
198
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
199
|
+TRIGGER_GROUP VARCHAR(60) NOT NULL,
|
|
200
|
+PRIMARY KEY (SCHED_NAME,TRIGGER_GROUP))
|
|
201
|
+ENGINE=InnoDB;
|
|
202
|
+
|
|
203
|
+CREATE TABLE QRTZ_FIRED_TRIGGERS (
|
|
204
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
205
|
+ENTRY_ID VARCHAR(140) NOT NULL,
|
|
206
|
+TRIGGER_NAME VARCHAR(60) NOT NULL,
|
|
207
|
+TRIGGER_GROUP VARCHAR(60) NOT NULL,
|
|
208
|
+INSTANCE_NAME VARCHAR(60) NOT NULL,
|
|
209
|
+FIRED_TIME BIGINT(19) NOT NULL,
|
|
210
|
+SCHED_TIME BIGINT(19) NOT NULL,
|
|
211
|
+PRIORITY INTEGER NOT NULL,
|
|
212
|
+STATE VARCHAR(16) NOT NULL,
|
|
213
|
+JOB_NAME VARCHAR(60) NULL,
|
|
214
|
+JOB_GROUP VARCHAR(60) NULL,
|
|
215
|
+IS_NONCONCURRENT BOOLEAN NULL,
|
|
216
|
+REQUESTS_RECOVERY BOOLEAN NULL,
|
|
217
|
+PRIMARY KEY (SCHED_NAME,ENTRY_ID))
|
|
218
|
+ENGINE=InnoDB;
|
|
219
|
+
|
|
220
|
+CREATE TABLE QRTZ_SCHEDULER_STATE (
|
|
221
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
222
|
+INSTANCE_NAME VARCHAR(60) NOT NULL,
|
|
223
|
+LAST_CHECKIN_TIME BIGINT(19) NOT NULL,
|
|
224
|
+CHECKIN_INTERVAL BIGINT(19) NOT NULL,
|
|
225
|
+PRIMARY KEY (SCHED_NAME,INSTANCE_NAME))
|
|
226
|
+ENGINE=InnoDB;
|
|
227
|
+
|
|
228
|
+CREATE TABLE QRTZ_LOCKS (
|
|
229
|
+SCHED_NAME VARCHAR(60) NOT NULL,
|
|
230
|
+LOCK_NAME VARCHAR(40) NOT NULL,
|
|
231
|
+PRIMARY KEY (SCHED_NAME,LOCK_NAME))
|
|
232
|
+ENGINE=InnoDB;
|
|
233
|
+
|
|
234
|
+CREATE INDEX IDX_QRTZ_J_REQ_RECOVERY ON QRTZ_JOB_DETAILS(SCHED_NAME,REQUESTS_RECOVERY);
|
|
235
|
+CREATE INDEX IDX_QRTZ_J_GRP ON QRTZ_JOB_DETAILS(SCHED_NAME,JOB_GROUP);
|
|
236
|
+
|
|
237
|
+CREATE INDEX IDX_QRTZ_T_J ON QRTZ_TRIGGERS(SCHED_NAME,JOB_NAME,JOB_GROUP);
|
|
238
|
+CREATE INDEX IDX_QRTZ_T_JG ON QRTZ_TRIGGERS(SCHED_NAME,JOB_GROUP);
|
|
239
|
+CREATE INDEX IDX_QRTZ_T_C ON QRTZ_TRIGGERS(SCHED_NAME,CALENDAR_NAME);
|
|
240
|
+CREATE INDEX IDX_QRTZ_T_G ON QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_GROUP);
|
|
241
|
+CREATE INDEX IDX_QRTZ_T_STATE ON QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_STATE);
|
|
242
|
+CREATE INDEX IDX_QRTZ_T_N_STATE ON QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP,TRIGGER_STATE);
|
|
243
|
+CREATE INDEX IDX_QRTZ_T_N_G_STATE ON QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_GROUP,TRIGGER_STATE);
|
|
244
|
+CREATE INDEX IDX_QRTZ_T_NEXT_FIRE_TIME ON QRTZ_TRIGGERS(SCHED_NAME,NEXT_FIRE_TIME);
|
|
245
|
+CREATE INDEX IDX_QRTZ_T_NFT_ST ON QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_STATE,NEXT_FIRE_TIME);
|
|
246
|
+CREATE INDEX IDX_QRTZ_T_NFT_MISFIRE ON QRTZ_TRIGGERS(SCHED_NAME,MISFIRE_INSTR,NEXT_FIRE_TIME);
|
|
247
|
+CREATE INDEX IDX_QRTZ_T_NFT_ST_MISFIRE ON QRTZ_TRIGGERS(SCHED_NAME,MISFIRE_INSTR,NEXT_FIRE_TIME,TRIGGER_STATE);
|
|
248
|
+CREATE INDEX IDX_QRTZ_T_NFT_ST_MISFIRE_GRP ON QRTZ_TRIGGERS(SCHED_NAME,MISFIRE_INSTR,NEXT_FIRE_TIME,TRIGGER_GROUP,TRIGGER_STATE);
|
|
249
|
+
|
|
250
|
+CREATE INDEX IDX_QRTZ_FT_TRIG_INST_NAME ON QRTZ_FIRED_TRIGGERS(SCHED_NAME,INSTANCE_NAME);
|
|
251
|
+CREATE INDEX IDX_QRTZ_FT_INST_JOB_REQ_RCVRY ON QRTZ_FIRED_TRIGGERS(SCHED_NAME,INSTANCE_NAME,REQUESTS_RECOVERY);
|
|
252
|
+CREATE INDEX IDX_QRTZ_FT_J_G ON QRTZ_FIRED_TRIGGERS(SCHED_NAME,JOB_NAME,JOB_GROUP);
|
|
253
|
+CREATE INDEX IDX_QRTZ_FT_JG ON QRTZ_FIRED_TRIGGERS(SCHED_NAME,JOB_GROUP);
|
|
254
|
+CREATE INDEX IDX_QRTZ_FT_T_G ON QRTZ_FIRED_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP);
|
|
255
|
+CREATE INDEX IDX_QRTZ_FT_TG ON QRTZ_FIRED_TRIGGERS(SCHED_NAME,TRIGGER_GROUP);
|
|
256
|
+
|
|
257
|
+commit;
|
|
258
|
+```
|
|
259
|
+
|
|
260
|
+# 网站配置
|
|
261
|
+
|
|
262
|
+- **查看服务器IP**:比如是:`192.168.0.252`
|
|
263
|
+- **设置appsettings.json文件**:在`dd-dev_版本号`目录下的`appsettings.json`文件中修改如下:
|
|
264
|
+```
|
|
265
|
+{
|
|
266
|
+ "ConnectionStrings": {
|
|
267
|
+ "IDENTITY_CONN": "server=192.168.0.252;port=3306;database=techeusr;user=root;password=lcDb_!@34%^_Mantunsci;SslMode=none",
|
|
268
|
+ "TaiHe_CONN": "server=192.168.0.252;port=3306;database=teche;user=root;password=lcDb_!@34%^_Mantunsci;SslMode=none;default command timeout=180",
|
|
269
|
+ "CJ_CONN": "server=192.168.0.252;port=3306;database=ebx;user=root;password=lcDb_!@34%^_Mantunsci;SslMode=none"
|
|
270
|
+ },
|
|
271
|
+ "Logging": {
|
|
272
|
+ "IncludeScopes": false,
|
|
273
|
+ "Debug": {
|
|
274
|
+ "LogLevel": {
|
|
275
|
+ "Default": "Warning"
|
|
276
|
+ }
|
|
277
|
+ },
|
|
278
|
+ "Console": {
|
|
279
|
+ "LogLevel": {
|
|
280
|
+ "Default": "Warning"
|
|
281
|
+ }
|
|
282
|
+ }
|
|
283
|
+ },
|
|
284
|
+ "App": {
|
|
285
|
+ "ip": "192.168.0.252:8080",
|
|
286
|
+ "server": "192.168.0.252",
|
|
287
|
+ "cjapi": "http://192.168.0.252:8080/api/",
|
|
288
|
+ "xmapi": "http://192.168.0.252:8080/api/",
|
|
289
|
+ "bjInterval": 180 //计算报警的频率,按每秒钟队列保守处理4个回路
|
|
290
|
+ },
|
|
291
|
+ "AllowedHosts": "*"
|
|
292
|
+}
|
|
293
|
+```
|
|
294
|
+
|
|
295
|
+# 网站运行
|
|
296
|
+
|
|
297
|
+- **确保mysql已经启动**:在服务中的名称是`MysqlServer`
|
|
298
|
+- **确保redis已经启动**:在服务中的名称是`redis-server`
|
|
299
|
+- **运行网站**: 在`dd-dev_版本号`目录下,按住`shift+右键`,点击`在此处打开命令窗口`,在控制台输入`dotnet.exe TaiHe.Electricity.Web.dll`
|
|
300
|
+- **确保teche数据库中已经有了所有表**
|
|
301
|
+- **确保techeuser数据库中已经有了所有表**
|
|
302
|
+- **往teche的kaiguanapplication添加一条记录**。
|
|
303
|
+```
|
|
304
|
+INSERT INTO kaiguanapplication(NAME, DelFlag) VALUES('照明',0)
|
|
305
|
+```
|
|
306
|
+- **登录**:打开网站`192.168.8.131:8080`,输入用户名`TecheFwd2018`,点击"登录"按钮
|
|
307
|
+
|
|
308
|
+# 项目管理
|
|
309
|
+
|
|
310
|
+点击左侧"工作人员"-"项目管理"。
|
|
311
|
+```
|
|
312
|
+项目名称:
|
|
313
|
+管理员用户名:
|
|
314
|
+密码:
|
|
315
|
+姓名:
|
|
316
|
+手机号:
|
|
317
|
+```
|
|
318
|
+
|
|
319
|
+# 楼层管理
|
|
320
|
+
|
|
321
|
+点击左侧"工作人员"-"楼层管理",右侧在相应项目行点击“编辑”按钮,点击左上角"添加楼层"按钮。
|
|
322
|
+```
|
|
323
|
+楼层名称:
|
|
324
|
+排序:
|
|
325
|
+```
|
|
326
|
+
|
|
327
|
+# 区域管理
|
|
328
|
+
|
|
329
|
+点击左侧"工作人员"-"区域管理",右侧在相应楼层行点击“编辑”按钮,点击左上角"添加区域"按钮。
|
|
330
|
+```
|
|
331
|
+区域名称:
|
|
332
|
+排序:
|
|
333
|
+```
|
|
334
|
+
|
|
335
|
+# 电箱管理
|
|
336
|
+
|
|
337
|
+点击左侧"工作人员"-"区域管理",点击左上角"添加电箱"按钮。
|
|
338
|
+
|
|
339
|
+```
|
|
340
|
+电箱名称:
|
|
341
|
+添加至:区域
|
|
342
|
+选择项目:
|
|
343
|
+选择楼层:
|
|
344
|
+选择区域:
|
|
345
|
+```
|
|
346
|
+
|
|
347
|
+# 模块管理
|
|
348
|
+
|
|
349
|
+点击左侧"工作人员"-"模块管理"。这里呈现所有向服务器发送数据的模块,如果有模块不在本地局域网内,可删除。
|
|
350
|
+
|
|
351
|
+# 开关管理
|
|
352
|
+
|
|
353
|
+点击左侧"工作人员"-"开关管理"。点击左上角"添加"按钮,点击"选择电箱"按钮,找到对应的电箱选择"选择" 按钮。
|
|
354
|
+
|
|
355
|
+```
|
|
356
|
+选择电箱:
|
|
357
|
+模块类型:回路模块
|
|
358
|
+是否有三相:没有三相
|
|
359
|
+模块MAC:
|
|
360
|
+排序:
|
|
361
|
+备注:
|
|
362
|
+```
|
|
363
|
+
|
|
364
|
+# 菜单管理
|
|
365
|
+
|
|
366
|
+点击左侧"权限管理"-"菜单管理",点击"同步菜单"按钮。
|
|
367
|
+```
|
|
368
|
+电工
|
|
369
|
+ 可视化管理
|
|
370
|
+ 当前报警
|
|
371
|
+ 开关报警
|
|
372
|
+设备管理
|
|
373
|
+ 可视化管理
|
|
374
|
+ 电工管理
|
|
375
|
+ 报警设置
|
|
376
|
+ 当前报警
|
|
377
|
+ 定时管理
|
|
378
|
+ 场景管理
|
|
379
|
+ 回路管理
|
|
380
|
+ 报警策略
|
|
381
|
+ 开关报警
|
|
382
|
+```
|
|
383
|
+
|
|
384
|
+# 可视化管理
|
|
385
|
+
|
|
386
|
+点击左侧"可视化管理",点击"查看楼层",点击区域图片。点击界面上某个按钮尝试。
|