@seeed-studio/solution-cli 0.2.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +111 -46
- package/bin/cli.js +7 -1
- package/catalog/client-config.json +10 -0
- package/catalog/knowledge-core.json +1923 -63
- package/docs/cli-guide.md +277 -0
- package/lib/agent.js +6 -0
- package/lib/downloader.js +85 -21
- package/lib/installer.js +50 -43
- package/lib/knowledge.js +343 -30
- package/package.json +4 -1
- package/skills/sensecraft/SKILL.md +39 -10
- package/skills/sensecraft/references/consult-and-select.md +86 -22
- package/skills/sensecraft/references/device-management.md +126 -0
- package/skills/sensecraft/references/diagnose.md +1 -1
- package/skills/sensecraft/references/hardware-bom.md +16 -16
- package/skills/sensecraft/references/secondary-development.md +84 -0
|
@@ -43,7 +43,39 @@
|
|
|
43
43
|
"smart_warehouse",
|
|
44
44
|
"retail_voice"
|
|
45
45
|
],
|
|
46
|
-
"summary": "用 AI 麦克风采集清晰的声音，在本地盒子上转写、合成语音或运行大模型，开源可部署方案开箱即用。"
|
|
46
|
+
"summary": "用 AI 麦克风采集清晰的声音，在本地盒子上转写、合成语音或运行大模型，开源可部署方案开箱即用。",
|
|
47
|
+
"landing_url": "https://www.seeedstudio.com/solutions/acoustic-audio-ai",
|
|
48
|
+
"repo_url": "",
|
|
49
|
+
"diagnostic_playbook": {
|
|
50
|
+
"domain": "声学与音频 AI / 设备故障听诊",
|
|
51
|
+
"core_dimensions": [
|
|
52
|
+
"被测机械类型与异响特征",
|
|
53
|
+
"声学麦克风 vs 振动声发射传感器",
|
|
54
|
+
"车间环境背景噪音"
|
|
55
|
+
],
|
|
56
|
+
"questions": [
|
|
57
|
+
{
|
|
58
|
+
"dimension": "machine_defect",
|
|
59
|
+
"question": "被监测的机械设备是什么（例如电机、轴承、齿轮箱、还是水泵压缩机）？想捕获的异常特征是什么（异响磨损、撞击声还是高压气体泄漏）？",
|
|
60
|
+
"rationale": "决定选择声学麦克风阵列还是接触式高频振动/声发射探头。"
|
|
61
|
+
},
|
|
62
|
+
{
|
|
63
|
+
"dimension": "ambient_noise",
|
|
64
|
+
"question": "设备周边是否有其他强烈机械运转的背景杂音？",
|
|
65
|
+
"rationale": "强背景杂音需利用端侧硬件 DSP 滤波器及降噪算法将工作主频滤除，突出异常脉冲。"
|
|
66
|
+
},
|
|
67
|
+
{
|
|
68
|
+
"dimension": "alarm_latency",
|
|
69
|
+
"question": "检测到异响异常后，希望在多长时间内告警，并通过何种方式通知维护人员？",
|
|
70
|
+
"rationale": "确定边缘推理实时性要求以及告警输出联动链路（声光/短信/PLC 停机信号）。"
|
|
71
|
+
}
|
|
72
|
+
]
|
|
73
|
+
},
|
|
74
|
+
"published": true,
|
|
75
|
+
"visibility": "production",
|
|
76
|
+
"visibility_en": "production",
|
|
77
|
+
"visibility_ja": "production",
|
|
78
|
+
"visibility_zh_hans": "production"
|
|
47
79
|
},
|
|
48
80
|
{
|
|
49
81
|
"id": "building-energy-retrofit",
|
|
@@ -79,7 +111,39 @@
|
|
|
79
111
|
"smart_space_assistant",
|
|
80
112
|
"multi_protocol_gateway"
|
|
81
113
|
],
|
|
82
|
-
"summary": "LoRaWAN 传感器贴墙安装，一台网关接入 Modbus、BACnet 等既有设备，数据进入开源面板或你自己的平台。"
|
|
114
|
+
"summary": "LoRaWAN 传感器贴墙安装，一台网关接入 Modbus、BACnet 等既有设备，数据进入开源面板或你自己的平台。",
|
|
115
|
+
"landing_url": "https://www.seeedstudio.com/solutions/building-energy-retrofit",
|
|
116
|
+
"repo_url": "",
|
|
117
|
+
"diagnostic_playbook": {
|
|
118
|
+
"domain": "旧建筑节能改造 / 暖通与智能抄表",
|
|
119
|
+
"core_dimensions": [
|
|
120
|
+
"存量表计通信接口",
|
|
121
|
+
"配电间集中 vs 跨楼层分布",
|
|
122
|
+
"纯能耗采集 vs 闭环控制"
|
|
123
|
+
],
|
|
124
|
+
"questions": [
|
|
125
|
+
{
|
|
126
|
+
"dimension": "meter_interface",
|
|
127
|
+
"question": "现场的电表、水表或空调机组目前是什么型号？是否自带 RS485（Modbus RTU / DL/T 645）通信接口，还是老旧机械表？",
|
|
128
|
+
"rationale": "带 485 接口可直接低成本手拉手总线抄表；无通信接口的老旧机械表需更换智能表或加装开口式开口互感器 CT。"
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"dimension": "cable_distribution",
|
|
132
|
+
"question": "表计是集中在配电室/机房，还是分散在各楼层的强电井中？各楼层之间是否有现成弱电网线贯通？",
|
|
133
|
+
"rationale": "集中点位直接用有线网关接总线；跨楼层分散无布线推荐 SenseCAP LoRaWAN 采集器无线回传，大幅削减施工穿墙打洞成本。"
|
|
134
|
+
},
|
|
135
|
+
{
|
|
136
|
+
"dimension": "control_requirement",
|
|
137
|
+
"question": "需求是仅做“能耗监测与数据统计”，还是需要做“闭环节能控制”（如根据峰谷电价或人员在场调节空调回路）？",
|
|
138
|
+
"rationale": "决定是否需要配置带工业继电器与模拟量输出的控制型网关。"
|
|
139
|
+
}
|
|
140
|
+
]
|
|
141
|
+
},
|
|
142
|
+
"published": true,
|
|
143
|
+
"visibility": "production",
|
|
144
|
+
"visibility_en": "production",
|
|
145
|
+
"visibility_ja": "production",
|
|
146
|
+
"visibility_zh_hans": "production"
|
|
83
147
|
},
|
|
84
148
|
{
|
|
85
149
|
"id": "conversational-voice-ai",
|
|
@@ -119,7 +183,39 @@
|
|
|
119
183
|
"conversational_voice_ai",
|
|
120
184
|
"reachy_claw_voice_robot"
|
|
121
185
|
],
|
|
122
|
-
"summary": "给设备加一个可随时打断的语音入口；识别和理解在本地主机上完成，首次装好后可断网运行。"
|
|
186
|
+
"summary": "给设备加一个可随时打断的语音入口；识别和理解在本地主机上完成，首次装好后可断网运行。",
|
|
187
|
+
"landing_url": "https://www.seeedstudio.com/solutions/conversational-voice-ai",
|
|
188
|
+
"repo_url": "",
|
|
189
|
+
"diagnostic_playbook": {
|
|
190
|
+
"domain": "现场语音控制 / 离线语音助手",
|
|
191
|
+
"core_dimensions": [
|
|
192
|
+
"声学噪声与麦克风拾音距离",
|
|
193
|
+
"100% 离线隐私 vs 云端大模型",
|
|
194
|
+
"受控设备联动协议"
|
|
195
|
+
],
|
|
196
|
+
"questions": [
|
|
197
|
+
{
|
|
198
|
+
"dimension": "acoustic_environment",
|
|
199
|
+
"question": "现场使用环境的噪音如何？通常是在安静的室内/会议室，还是存在环境背景噪音（如风扇、空调、人群嘈杂）？拾音距离多远？",
|
|
200
|
+
"rationale": "决定麦克风阵列选型：近场安静可用双麦；远场（3~5米）与嘈杂环境必须使用带硬件 DSP、回声消除 AEC 与波束成形的 ReSpeaker XVF3800 多麦阵列。"
|
|
201
|
+
},
|
|
202
|
+
{
|
|
203
|
+
"dimension": "privacy_connectivity",
|
|
204
|
+
"question": "系统对网络和隐私有什么硬性要求？是必须 100% 纯本地离线断网运行，还是可以联网访问云端大模型？",
|
|
205
|
+
"rationale": "纯离线需配置 Orin NX 等中高算力主机在端侧跑端到端小模型（Whisper + LLM + TTS）；联网混合模式可用轻量主机做前端拾音上云。"
|
|
206
|
+
},
|
|
207
|
+
{
|
|
208
|
+
"dimension": "target_control",
|
|
209
|
+
"question": "语音识别或大模型理解后，主要用来控制什么设备或执行什么业务？",
|
|
210
|
+
"rationale": "明确南向控制接口：是对接 Home Assistant 智能家居、发送 MQTT 报文、还是通过串口/Modbus 控制工业继电器。"
|
|
211
|
+
}
|
|
212
|
+
]
|
|
213
|
+
},
|
|
214
|
+
"published": true,
|
|
215
|
+
"visibility": "production",
|
|
216
|
+
"visibility_en": "production",
|
|
217
|
+
"visibility_ja": "production",
|
|
218
|
+
"visibility_zh_hans": "production"
|
|
123
219
|
},
|
|
124
220
|
{
|
|
125
221
|
"id": "elderly-care-monitoring",
|
|
@@ -150,7 +246,39 @@
|
|
|
150
246
|
"reference_designs": [
|
|
151
247
|
"fall_detection"
|
|
152
248
|
],
|
|
153
|
-
"summary": "摄像头在房间里端侧判定跌倒并秒级推送告警；支持接入麦克风阵列实现异常声音与呼救检测。"
|
|
249
|
+
"summary": "摄像头在房间里端侧判定跌倒并秒级推送告警；支持接入麦克风阵列实现异常声音与呼救检测。",
|
|
250
|
+
"landing_url": "https://www.seeedstudio.com/solutions/elderly-care-monitoring",
|
|
251
|
+
"repo_url": "",
|
|
252
|
+
"diagnostic_playbook": {
|
|
253
|
+
"domain": "智慧养老 / 室内监护",
|
|
254
|
+
"core_dimensions": [
|
|
255
|
+
"集中 vs 分散空间分布",
|
|
256
|
+
"存量摄像头利旧",
|
|
257
|
+
"隐私保护与传感器形态"
|
|
258
|
+
],
|
|
259
|
+
"questions": [
|
|
260
|
+
{
|
|
261
|
+
"dimension": "topology",
|
|
262
|
+
"question": "老人房间和公共区域是在同一层/同一楼栋比较集中，还是分散在多栋楼或较远区域？",
|
|
263
|
+
"rationale": "集中分布可用 1 台 reComputer 主机拉多路 RTSP 流摊薄成本；分散点位推荐每间房独立 reCamera 一体机免拉长线。"
|
|
264
|
+
},
|
|
265
|
+
{
|
|
266
|
+
"dimension": "asset_reuse",
|
|
267
|
+
"question": "现场是否已经安装了支持 RTSP/ONVIF 协议的监控摄像头（如海康、大华等）？",
|
|
268
|
+
"rationale": "已有摄像头可直接复用利旧，只需采购边缘算力盒，省去镜头重购成本；无摄像头则推荐成套硬件。"
|
|
269
|
+
},
|
|
270
|
+
{
|
|
271
|
+
"dimension": "privacy_boundary",
|
|
272
|
+
"question": "卫生间、卧室等高隐私区域是否对纯光学摄像头有顾虑，是否需要无视觉隐私的毫米波雷达方案？",
|
|
273
|
+
"rationale": "私密区域用 60GHz 毫米波雷达替代光学镜头，既可精确检测跌倒卧床，又彻底消除侵犯隐私争议。"
|
|
274
|
+
}
|
|
275
|
+
]
|
|
276
|
+
},
|
|
277
|
+
"published": true,
|
|
278
|
+
"visibility": "staging",
|
|
279
|
+
"visibility_en": "staging",
|
|
280
|
+
"visibility_ja": "staging",
|
|
281
|
+
"visibility_zh_hans": "staging"
|
|
154
282
|
},
|
|
155
283
|
{
|
|
156
284
|
"id": "environment-monitoring",
|
|
@@ -194,7 +322,39 @@
|
|
|
194
322
|
"smart_hvac_control",
|
|
195
323
|
"agri_env_monitor"
|
|
196
324
|
],
|
|
197
|
-
"summary": "现场设备免布线长效续航，既有工业探头加采集器即可利旧接入。"
|
|
325
|
+
"summary": "现场设备免布线长效续航，既有工业探头加采集器即可利旧接入。",
|
|
326
|
+
"landing_url": "https://www.seeedstudio.com/solutions/environment-monitoring",
|
|
327
|
+
"repo_url": "",
|
|
328
|
+
"diagnostic_playbook": {
|
|
329
|
+
"domain": "智慧农业 / 环境监测与微气象",
|
|
330
|
+
"core_dimensions": [
|
|
331
|
+
"集中大棚 vs 广域农田",
|
|
332
|
+
"市电 vs 太阳能/电池供电",
|
|
333
|
+
"监测指标与探头深度"
|
|
334
|
+
],
|
|
335
|
+
"questions": [
|
|
336
|
+
{
|
|
337
|
+
"dimension": "topology",
|
|
338
|
+
"question": "监测区域是集中式连栋温室大棚（百米级），还是大面积户外大田/果园（数公里级）？",
|
|
339
|
+
"rationale": "大棚内百米级可采用 RS485 有线总线集中组网；广域大田推荐 LoRaWAN 远距离低功耗无线传输，配合 SenseCAP M2 网关。"
|
|
340
|
+
},
|
|
341
|
+
{
|
|
342
|
+
"dimension": "power",
|
|
343
|
+
"question": "现场测点是否有 220V 市电供电，还是需要野外太阳能板/锂电池长续航供电？",
|
|
344
|
+
"rationale": "市电可支持持续高频数据上报；无市电需要选用带内置超大锂电池、支持休眠唤醒的低功耗无线传感器（如 S2100/S210x）。"
|
|
345
|
+
},
|
|
346
|
+
{
|
|
347
|
+
"dimension": "sensing_depth",
|
|
348
|
+
"question": "需要监测哪些核心环境指标？仅是空气温湿度/光照/CO2，还是包括土壤剖面墒情（深层水分/EC/pH）或气象风速风向？",
|
|
349
|
+
"rationale": "决定是配置一体化多合一微气象站（如 S700/S2120），还是选配工业级土壤三参数/水肥专用探针与变送器。"
|
|
350
|
+
}
|
|
351
|
+
]
|
|
352
|
+
},
|
|
353
|
+
"published": true,
|
|
354
|
+
"visibility": "production",
|
|
355
|
+
"visibility_en": "production",
|
|
356
|
+
"visibility_ja": "production",
|
|
357
|
+
"visibility_zh_hans": "production"
|
|
198
358
|
},
|
|
199
359
|
{
|
|
200
360
|
"id": "home-building-automation",
|
|
@@ -228,7 +388,15 @@
|
|
|
228
388
|
"smart_space_assistant",
|
|
229
389
|
"multi_protocol_gateway"
|
|
230
390
|
],
|
|
231
|
-
"summary": "传感器与电表数据汇入边缘网关，同一套点位模型接入 OPC UA、Modbus、BACnet 设备，应用可本地运行或接入你的平台。"
|
|
391
|
+
"summary": "传感器与电表数据汇入边缘网关，同一套点位模型接入 OPC UA、Modbus、BACnet 设备，应用可本地运行或接入你的平台。",
|
|
392
|
+
"landing_url": "https://www.seeedstudio.com/solutions/home-building-automation",
|
|
393
|
+
"repo_url": "",
|
|
394
|
+
"diagnostic_playbook": null,
|
|
395
|
+
"published": true,
|
|
396
|
+
"visibility": "production",
|
|
397
|
+
"visibility_en": "production",
|
|
398
|
+
"visibility_ja": "production",
|
|
399
|
+
"visibility_zh_hans": "production"
|
|
232
400
|
},
|
|
233
401
|
{
|
|
234
402
|
"id": "in-person-conversation-intelligence",
|
|
@@ -257,7 +425,15 @@
|
|
|
257
425
|
"retail_voice",
|
|
258
426
|
"smart-badge-voice-transcription"
|
|
259
427
|
],
|
|
260
|
-
"summary": "转写可放在云端，也可放在企业自有主机上；固定柜台、窗口的拾音见「门店与柜台服务质检」。"
|
|
428
|
+
"summary": "转写可放在云端，也可放在企业自有主机上；固定柜台、窗口的拾音见「门店与柜台服务质检」。",
|
|
429
|
+
"landing_url": "https://www.seeedstudio.com/solutions/in-person-conversation-intelligence",
|
|
430
|
+
"repo_url": "",
|
|
431
|
+
"diagnostic_playbook": null,
|
|
432
|
+
"published": true,
|
|
433
|
+
"visibility": "staging",
|
|
434
|
+
"visibility_en": "staging",
|
|
435
|
+
"visibility_ja": "staging",
|
|
436
|
+
"visibility_zh_hans": "staging"
|
|
261
437
|
},
|
|
262
438
|
{
|
|
263
439
|
"id": "indoor-outdoor-positioning",
|
|
@@ -284,7 +460,39 @@
|
|
|
284
460
|
"reference_designs": [
|
|
285
461
|
"indoor_positioning_ble_lorawan"
|
|
286
462
|
],
|
|
287
|
-
"summary": "室内BLE信标与室外GNSS无缝融合定位，但地下金属密闭空间需加密布设基站以防信号屏蔽。"
|
|
463
|
+
"summary": "室内BLE信标与室外GNSS无缝融合定位，但地下金属密闭空间需加密布设基站以防信号屏蔽。",
|
|
464
|
+
"landing_url": "https://www.seeedstudio.com/solutions/indoor-outdoor-positioning",
|
|
465
|
+
"repo_url": "",
|
|
466
|
+
"diagnostic_playbook": {
|
|
467
|
+
"domain": "室内外定位 / 资产与人员追踪",
|
|
468
|
+
"core_dimensions": [
|
|
469
|
+
"纯室内 vs 室内外混合",
|
|
470
|
+
"定位精度期望（米级 vs 区域级）",
|
|
471
|
+
"佩戴形式与免维护续航"
|
|
472
|
+
],
|
|
473
|
+
"questions": [
|
|
474
|
+
{
|
|
475
|
+
"dimension": "spatial_scope",
|
|
476
|
+
"question": "定位场景是纯室内（厂房/展厅/仓库），还是室内外混合（比如仓库到室外堆场，甚至货物长途运输）？",
|
|
477
|
+
"rationale": "纯室内基于 BLE 信标定位；室内外混合推荐 SenseCAP T1000 追踪器，室内切蓝牙/Wi-Fi 定位，室外切 GPS/北斗。"
|
|
478
|
+
},
|
|
479
|
+
{
|
|
480
|
+
"dimension": "accuracy_budget",
|
|
481
|
+
"question": "对定位精度的期望是怎样的？是需要精确到米级的具体坐标，还是只要知道人在哪间房/资产在哪个货架区域即可？",
|
|
482
|
+
"rationale": "米级需部署高密度蓝牙基站；区域级可大幅减少基站数量，极大节约硬件成本与施工布线。"
|
|
483
|
+
},
|
|
484
|
+
{
|
|
485
|
+
"dimension": "form_battery",
|
|
486
|
+
"question": "被追踪对象的形态是什么（人员佩戴胸卡工牌，还是贴在货物托盘/设备上）？期望续航时间是多久？",
|
|
487
|
+
"rationale": "决定选用超薄卡片型轻量 Tracker 还是超长续航工业 Tracker。"
|
|
488
|
+
}
|
|
489
|
+
]
|
|
490
|
+
},
|
|
491
|
+
"published": true,
|
|
492
|
+
"visibility": "production",
|
|
493
|
+
"visibility_en": "production",
|
|
494
|
+
"visibility_ja": "production",
|
|
495
|
+
"visibility_zh_hans": "production"
|
|
288
496
|
},
|
|
289
497
|
{
|
|
290
498
|
"id": "industrial-control-automation",
|
|
@@ -316,7 +524,39 @@
|
|
|
316
524
|
"multi_protocol_gateway",
|
|
317
525
|
"smart_hvac_control"
|
|
318
526
|
],
|
|
319
|
-
"summary": "采集、联动和看板在本地网关上运行；触屏终端可装在设备旁直接操作。"
|
|
527
|
+
"summary": "采集、联动和看板在本地网关上运行；触屏终端可装在设备旁直接操作。",
|
|
528
|
+
"landing_url": "https://www.seeedstudio.com/solutions/industrial-control-automation",
|
|
529
|
+
"repo_url": "",
|
|
530
|
+
"diagnostic_playbook": {
|
|
531
|
+
"domain": "现场控制与自动化 / PLC 边缘互联",
|
|
532
|
+
"core_dimensions": [
|
|
533
|
+
"工控总线协议种类",
|
|
534
|
+
"导轨安装与供电环境",
|
|
535
|
+
"边缘计算与控制响应周期"
|
|
536
|
+
],
|
|
537
|
+
"questions": [
|
|
538
|
+
{
|
|
539
|
+
"dimension": "bus_protocol",
|
|
540
|
+
"question": "现场下位机设备主要采用什么总线和通信协议（如 Modbus TCP/RTU、CANopen、PROFINET、EtherNet/IP）？",
|
|
541
|
+
"rationale": "决定边缘网关的物理接口（隔离 RS485、双网口、CAN 接口）以及协议转换中间件配置。"
|
|
542
|
+
},
|
|
543
|
+
{
|
|
544
|
+
"dimension": "cabinet_power",
|
|
545
|
+
"question": "设备是安装在标准工业电控柜导轨上吗？现场供电是直流 24V DC 还是交流 220V？",
|
|
546
|
+
"rationale": "确认机型是否支持 DIN 导轨卡扣安装，以及宽压 DC 9~36V 输入。"
|
|
547
|
+
},
|
|
548
|
+
{
|
|
549
|
+
"dimension": "control_cycle",
|
|
550
|
+
"question": "业务需要做实时控制闭环（毫秒级控制周期），还是做上层数据采集与边缘分析诊断（秒级/分级）？",
|
|
551
|
+
"rationale": "实时控制需要带实时补丁（PREEMPT_RT）的边缘控制器；数据采集与分析常规工业边缘电脑即可满足。"
|
|
552
|
+
}
|
|
553
|
+
]
|
|
554
|
+
},
|
|
555
|
+
"published": true,
|
|
556
|
+
"visibility": "staging",
|
|
557
|
+
"visibility_en": "staging",
|
|
558
|
+
"visibility_ja": "staging",
|
|
559
|
+
"visibility_zh_hans": "staging"
|
|
320
560
|
},
|
|
321
561
|
{
|
|
322
562
|
"id": "industrial-visual-inspection",
|
|
@@ -345,7 +585,39 @@
|
|
|
345
585
|
"edge_inspection_surface",
|
|
346
586
|
"edge_inspection_assembly"
|
|
347
587
|
],
|
|
348
|
-
"summary": "工位边缘工控机就地完成实时质检判定且原图不出厂，但高检出率依赖产线真实缺陷样本重训与现场标定。"
|
|
588
|
+
"summary": "工位边缘工控机就地完成实时质检判定且原图不出厂，但高检出率依赖产线真实缺陷样本重训与现场标定。",
|
|
589
|
+
"landing_url": "https://www.seeedstudio.com/solutions/industrial-visual-inspection",
|
|
590
|
+
"repo_url": "",
|
|
591
|
+
"diagnostic_playbook": {
|
|
592
|
+
"domain": "工业视觉质检 / 表面缺陷与装配复检",
|
|
593
|
+
"core_dimensions": [
|
|
594
|
+
"产线生产节拍与相机快门",
|
|
595
|
+
"工件材质反光与照明",
|
|
596
|
+
"剔除执行与 PLC 信号闭环"
|
|
597
|
+
],
|
|
598
|
+
"questions": [
|
|
599
|
+
{
|
|
600
|
+
"dimension": "line_speed",
|
|
601
|
+
"question": "现场流水线的生产节拍是怎样的（每分钟过检多少件产品，工件是静止拍照还是运动中飞拍）？",
|
|
602
|
+
"rationale": "决定相机曝光类型（运动飞拍必须全局快门 Global Shutter），以及端侧推理帧率与 Jetson 算力等级（Orin Nano vs Orin NX）。"
|
|
603
|
+
},
|
|
604
|
+
{
|
|
605
|
+
"dimension": "materials_lighting",
|
|
606
|
+
"question": "被测工件表面是什么材质（反光金属、高光塑料还是普通漫反射包装）？缺陷尺寸大概在什么毫米级别？",
|
|
607
|
+
"rationale": "反光表面需定制特殊工业光源（如偏光环形光、同轴光）消除眩光；缺陷精度决定工业相机分辨率与镜头焦距。"
|
|
608
|
+
},
|
|
609
|
+
{
|
|
610
|
+
"dimension": "plc_integration",
|
|
611
|
+
"question": "检测出不良品后，边缘设备是否需要直接向现场 PLC 或气缸发送剔除信号？",
|
|
612
|
+
"rationale": "决定是否需要选择带工业隔离数字量 I/O 的工控机型（如 reComputer Industrial 系列），并配置现场总线。"
|
|
613
|
+
}
|
|
614
|
+
]
|
|
615
|
+
},
|
|
616
|
+
"published": true,
|
|
617
|
+
"visibility": "staging",
|
|
618
|
+
"visibility_en": "staging",
|
|
619
|
+
"visibility_ja": "staging",
|
|
620
|
+
"visibility_zh_hans": "staging"
|
|
349
621
|
},
|
|
350
622
|
{
|
|
351
623
|
"id": "intelligent-video-analytics",
|
|
@@ -389,7 +661,39 @@
|
|
|
389
661
|
"edge_retail_recognition",
|
|
390
662
|
"edge_waste_sorting"
|
|
391
663
|
],
|
|
392
|
-
"summary": "视频在 AI 摄像头或边缘盒子上本地分析，已有的网络摄像头也能接入。"
|
|
664
|
+
"summary": "视频在 AI 摄像头或边缘盒子上本地分析，已有的网络摄像头也能接入。",
|
|
665
|
+
"landing_url": "https://www.seeedstudio.com/solutions/intelligent-video-analytics",
|
|
666
|
+
"repo_url": "",
|
|
667
|
+
"diagnostic_playbook": {
|
|
668
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
669
|
+
"core_dimensions": [
|
|
670
|
+
"分析目标与算法类型",
|
|
671
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
672
|
+
"夜间与恶劣环境"
|
|
673
|
+
],
|
|
674
|
+
"questions": [
|
|
675
|
+
{
|
|
676
|
+
"dimension": "analytics_target",
|
|
677
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
678
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
679
|
+
},
|
|
680
|
+
{
|
|
681
|
+
"dimension": "stream_architecture",
|
|
682
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
683
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
684
|
+
},
|
|
685
|
+
{
|
|
686
|
+
"dimension": "environment_lighting",
|
|
687
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
688
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
689
|
+
}
|
|
690
|
+
]
|
|
691
|
+
},
|
|
692
|
+
"published": true,
|
|
693
|
+
"visibility": "production",
|
|
694
|
+
"visibility_en": "production",
|
|
695
|
+
"visibility_ja": "production",
|
|
696
|
+
"visibility_zh_hans": "production"
|
|
393
697
|
},
|
|
394
698
|
{
|
|
395
699
|
"id": "off-grid-mesh-communication",
|
|
@@ -416,7 +720,39 @@
|
|
|
416
720
|
"sensecap_t1000_tracker"
|
|
417
721
|
],
|
|
418
722
|
"reference_designs": [],
|
|
419
|
-
"summary": "LoRa Mesh 节点之间远距离中继消息，定位工牌发送位置与 SOS，手机 APP 查看；需要接云平台时可另配 LoRaWAN 网关。"
|
|
723
|
+
"summary": "LoRa Mesh 节点之间远距离中继消息，定位工牌发送位置与 SOS，手机 APP 查看；需要接云平台时可另配 LoRaWAN 网关。",
|
|
724
|
+
"landing_url": "https://www.seeedstudio.com/solutions/off-grid-mesh-communication",
|
|
725
|
+
"repo_url": "",
|
|
726
|
+
"diagnostic_playbook": {
|
|
727
|
+
"domain": "离网与自组网通信 / 应急 Mesh",
|
|
728
|
+
"core_dimensions": [
|
|
729
|
+
"地形遮挡与视距",
|
|
730
|
+
"便携手持 vs 高点中继基站",
|
|
731
|
+
"地区无线电免许可频段"
|
|
732
|
+
],
|
|
733
|
+
"questions": [
|
|
734
|
+
{
|
|
735
|
+
"dimension": "terrain_los",
|
|
736
|
+
"question": "应急通信的使用环境是在城市建筑物密集区域，还是在无手机信号的野外山区、森林或野营开阔地？",
|
|
737
|
+
"rationale": "开阔地视距传输可达十几公里；建筑物阻隔多需要规划高点固定中继节点。"
|
|
738
|
+
},
|
|
739
|
+
{
|
|
740
|
+
"dimension": "node_roles",
|
|
741
|
+
"question": "组网节点主要是人员移动随身携带（如佩戴小巧终端配合手机发文字/位置），还是需要搭建固定的高位信号中继站？",
|
|
742
|
+
"rationale": "固定高位站需配置大功率玻璃钢天线与太阳能充电套件；随身节点强调便携长续航。"
|
|
743
|
+
},
|
|
744
|
+
{
|
|
745
|
+
"dimension": "rf_frequency",
|
|
746
|
+
"question": "项目部署在哪个国家或地区？",
|
|
747
|
+
"rationale": "确认合法的 LoRa 免许可频段，如中国 CN470、欧洲 EU868 或北美 US915，确保无线电合规。"
|
|
748
|
+
}
|
|
749
|
+
]
|
|
750
|
+
},
|
|
751
|
+
"published": true,
|
|
752
|
+
"visibility": "production",
|
|
753
|
+
"visibility_en": "production",
|
|
754
|
+
"visibility_ja": "production",
|
|
755
|
+
"visibility_zh_hans": "production"
|
|
420
756
|
},
|
|
421
757
|
{
|
|
422
758
|
"id": "parking-traffic-vision",
|
|
@@ -448,7 +784,39 @@
|
|
|
448
784
|
"edge-anpr-plate-recognition",
|
|
449
785
|
"parking-space-occupancy-detection"
|
|
450
786
|
],
|
|
451
|
-
"summary": "车位检测在端侧相机本地闭环免中心服务器，多路出入口通过边缘主机利旧既有监控且视频不出场。"
|
|
787
|
+
"summary": "车位检测在端侧相机本地闭环免中心服务器，多路出入口通过边缘主机利旧既有监控且视频不出场。",
|
|
788
|
+
"landing_url": "https://www.seeedstudio.com/solutions/parking-traffic-vision",
|
|
789
|
+
"repo_url": "",
|
|
790
|
+
"diagnostic_playbook": {
|
|
791
|
+
"domain": "智慧交通 / 园区道闸与车牌识别",
|
|
792
|
+
"core_dimensions": [
|
|
793
|
+
"道闸卡口 vs 主干道抓拍",
|
|
794
|
+
"夜间补光与逆光条件",
|
|
795
|
+
"继电器开闸联动链路"
|
|
796
|
+
],
|
|
797
|
+
"questions": [
|
|
798
|
+
{
|
|
799
|
+
"dimension": "traffic_speed",
|
|
800
|
+
"question": "抓拍点位是出入口道闸（低速停车抓拍，1~2 车道），还是园区/厂区主干道（车辆行驶中抓拍）？",
|
|
801
|
+
"rationale": "道闸场景普通高帧率相机即可胜任；行驶干道需全局快门与快速连续跟踪推理算法支持。"
|
|
802
|
+
},
|
|
803
|
+
{
|
|
804
|
+
"dimension": "lighting_condition",
|
|
805
|
+
"question": "夜间或逆光环境如何？安装点是否有充足照明，还是需要相机自带或外接强光抑制爆闪补光灯？",
|
|
806
|
+
"rationale": "车牌反光与大灯直射在出入口很常见，强光抑制与补光同步触发至关重要。"
|
|
807
|
+
},
|
|
808
|
+
{
|
|
809
|
+
"dimension": "gate_control",
|
|
810
|
+
"question": "车牌识别成功后，是需要边缘主机直接通过板载继电器/IO 接口控制道闸开杆，还是仅需通过网络上报给您现有的停车计费系统？",
|
|
811
|
+
"rationale": "决定是否需要硬件级隔离继电器控制配件，以及是否需要本地脱机白名单离线放行能力。"
|
|
812
|
+
}
|
|
813
|
+
]
|
|
814
|
+
},
|
|
815
|
+
"published": true,
|
|
816
|
+
"visibility": "staging",
|
|
817
|
+
"visibility_en": "staging",
|
|
818
|
+
"visibility_ja": "staging",
|
|
819
|
+
"visibility_zh_hans": "staging"
|
|
452
820
|
},
|
|
453
821
|
{
|
|
454
822
|
"id": "smart-restaurant",
|
|
@@ -476,7 +844,15 @@
|
|
|
476
844
|
"xiao_esp32s3"
|
|
477
845
|
],
|
|
478
846
|
"reference_designs": [],
|
|
479
|
-
"summary": "餐桌侧的交互在桌面上完成：麦克风阵列听顾客点单，订单直接到后厨；电子纸桌牌显示座位、账单和二维码菜单，断电不丢画面；手势和投影让顾客完全不碰屏幕。算力放在店里，数据不出店。"
|
|
847
|
+
"summary": "餐桌侧的交互在桌面上完成：麦克风阵列听顾客点单，订单直接到后厨；电子纸桌牌显示座位、账单和二维码菜单，断电不丢画面；手势和投影让顾客完全不碰屏幕。算力放在店里，数据不出店。",
|
|
848
|
+
"landing_url": "https://www.seeedstudio.com/solutions/smart-restaurant",
|
|
849
|
+
"repo_url": "",
|
|
850
|
+
"diagnostic_playbook": null,
|
|
851
|
+
"published": true,
|
|
852
|
+
"visibility": "staging",
|
|
853
|
+
"visibility_en": "staging",
|
|
854
|
+
"visibility_ja": "staging",
|
|
855
|
+
"visibility_zh_hans": "staging"
|
|
480
856
|
},
|
|
481
857
|
{
|
|
482
858
|
"id": "smart-retail-store",
|
|
@@ -504,8 +880,44 @@
|
|
|
504
880
|
"recomputer_j30",
|
|
505
881
|
"recomputer_r11"
|
|
506
882
|
],
|
|
507
|
-
"reference_designs": [
|
|
508
|
-
|
|
883
|
+
"reference_designs": [
|
|
884
|
+
"recamera_heatmap_grafana",
|
|
885
|
+
"edge_retail_recognition",
|
|
886
|
+
"unmanned_store_access"
|
|
887
|
+
],
|
|
888
|
+
"summary": "专为商超与便利店设计的端侧 AI 视觉硬件：就地完成客流热力与货架盘点且视频不出店，断网仍可刷脸门禁。",
|
|
889
|
+
"landing_url": "https://www.seeedstudio.com/solutions/smart-retail-store",
|
|
890
|
+
"repo_url": "",
|
|
891
|
+
"diagnostic_playbook": {
|
|
892
|
+
"domain": "智慧零售门店 / 客流统计与货架动线",
|
|
893
|
+
"core_dimensions": [
|
|
894
|
+
"进出店客流计数 vs 店内热力动线",
|
|
895
|
+
"门头吊顶施工布线",
|
|
896
|
+
"多门店数据汇聚方式"
|
|
897
|
+
],
|
|
898
|
+
"questions": [
|
|
899
|
+
{
|
|
900
|
+
"dimension": "analytics_scope",
|
|
901
|
+
"question": "统计的主要诉求是“出入口进店人数/客流双向计数”，还是“店内各货架区域的顾客停留时长与热力分布”？",
|
|
902
|
+
"rationale": "出入口仅需门头单台垂直俯视 AI 相机；货架热力需广角全景相机或多机拼接。"
|
|
903
|
+
},
|
|
904
|
+
{
|
|
905
|
+
"dimension": "ceiling_cabling",
|
|
906
|
+
"question": "现场安装点位（通常在门头吊顶或天花板）是否预留了网线和供电？",
|
|
907
|
+
"rationale": "支持 PoE 供电只需一根网线即可完成供电与通信，最利于商铺免破坏装修快速施工。"
|
|
908
|
+
},
|
|
909
|
+
{
|
|
910
|
+
"dimension": "data_aggregation",
|
|
911
|
+
"question": "连锁门店的数据汇总方式是怎样的？是单店本地显示，还是需要将多店客流数据自动上传到您的总部云端或 ERP 系统？",
|
|
912
|
+
"rationale": "确认网络上报协议（MQTT/HTTP REST）及离线断网本地缓存需求。"
|
|
913
|
+
}
|
|
914
|
+
]
|
|
915
|
+
},
|
|
916
|
+
"published": true,
|
|
917
|
+
"visibility": "staging",
|
|
918
|
+
"visibility_en": "staging",
|
|
919
|
+
"visibility_ja": "staging",
|
|
920
|
+
"visibility_zh_hans": "staging"
|
|
509
921
|
},
|
|
510
922
|
{
|
|
511
923
|
"id": "smart-warehouse-management",
|
|
@@ -534,7 +946,39 @@
|
|
|
534
946
|
"reference_designs": [
|
|
535
947
|
"smart_warehouse"
|
|
536
948
|
],
|
|
537
|
-
"summary": "Watcher 听懂指令并识别操作人，结果写入内置仓管系统或已有 ERP / WMS；可选云端、本地主机或完全离线部署。"
|
|
949
|
+
"summary": "Watcher 听懂指令并识别操作人，结果写入内置仓管系统或已有 ERP / WMS；可选云端、本地主机或完全离线部署。",
|
|
950
|
+
"landing_url": "https://www.seeedstudio.com/solutions/smart-warehouse-management",
|
|
951
|
+
"repo_url": "",
|
|
952
|
+
"diagnostic_playbook": {
|
|
953
|
+
"domain": "智慧仓库管理 / 货位状态与托盘盘点",
|
|
954
|
+
"core_dimensions": [
|
|
955
|
+
"货架结构与无线遮挡",
|
|
956
|
+
"货位占空感知 vs 条码盘点",
|
|
957
|
+
"库区网络覆盖"
|
|
958
|
+
],
|
|
959
|
+
"questions": [
|
|
960
|
+
{
|
|
961
|
+
"dimension": "rack_structure",
|
|
962
|
+
"question": "仓库的货物存储形式是托盘平库、高位重型货架还是自动化立体仓？货架高度大概多高？",
|
|
963
|
+
"rationale": "高位货架钢结构遮挡严重，需针对性设计相机俯视视角或工业无线天线布设。"
|
|
964
|
+
},
|
|
965
|
+
{
|
|
966
|
+
"dimension": "perception_mode",
|
|
967
|
+
"question": "核心诉求是“货位占用与空闲状态检测”（有货/无货），还是“具体托盘/货物条码精准盘点”？",
|
|
968
|
+
"rationale": "货位空闲检测推荐边缘视觉一体机俯视感知；托盘精准身份盘点需结合 RFID 或蓝牙 Asset Tag。"
|
|
969
|
+
},
|
|
970
|
+
{
|
|
971
|
+
"dimension": "network_coverage",
|
|
972
|
+
"question": "库区内是否具备完整的有线网络或 Wi-Fi 覆盖？",
|
|
973
|
+
"rationale": "无网络覆盖时需要配置长距离 LoRaWAN 或 4G 无线网关回传数据。"
|
|
974
|
+
}
|
|
975
|
+
]
|
|
976
|
+
},
|
|
977
|
+
"published": true,
|
|
978
|
+
"visibility": "production",
|
|
979
|
+
"visibility_en": "production",
|
|
980
|
+
"visibility_ja": "production",
|
|
981
|
+
"visibility_zh_hans": "production"
|
|
538
982
|
},
|
|
539
983
|
{
|
|
540
984
|
"id": "voicecollectionanalysis",
|
|
@@ -566,7 +1010,15 @@
|
|
|
566
1010
|
"reference_designs": [
|
|
567
1011
|
"retail_voice"
|
|
568
1012
|
],
|
|
569
|
-
"summary": "固定点位对话在端侧直接转成结构化文本，音频不出店。员工随身佩戴录音的场景见「线下客户对话分析」。"
|
|
1013
|
+
"summary": "固定点位对话在端侧直接转成结构化文本，音频不出店。员工随身佩戴录音的场景见「线下客户对话分析」。",
|
|
1014
|
+
"landing_url": "https://www.seeedstudio.com/solutions/voicecollectionanalysis",
|
|
1015
|
+
"repo_url": "",
|
|
1016
|
+
"diagnostic_playbook": null,
|
|
1017
|
+
"published": true,
|
|
1018
|
+
"visibility": "production",
|
|
1019
|
+
"visibility_en": "production",
|
|
1020
|
+
"visibility_ja": "production",
|
|
1021
|
+
"visibility_zh_hans": "production"
|
|
570
1022
|
},
|
|
571
1023
|
{
|
|
572
1024
|
"id": "whole-home-smart-living",
|
|
@@ -608,7 +1060,15 @@
|
|
|
608
1060
|
"edge_security",
|
|
609
1061
|
"home-assistant-local-voice-hub"
|
|
610
1062
|
],
|
|
611
|
-
"summary": "所有设备接入同一台本地 Home Assistant 主机，自动化规则在本地运行。"
|
|
1063
|
+
"summary": "所有设备接入同一台本地 Home Assistant 主机，自动化规则在本地运行。",
|
|
1064
|
+
"landing_url": "https://www.seeedstudio.com/solutions/whole-home-smart-living",
|
|
1065
|
+
"repo_url": "",
|
|
1066
|
+
"diagnostic_playbook": null,
|
|
1067
|
+
"published": true,
|
|
1068
|
+
"visibility": "staging",
|
|
1069
|
+
"visibility_en": "staging",
|
|
1070
|
+
"visibility_ja": "staging",
|
|
1071
|
+
"visibility_zh_hans": "staging"
|
|
612
1072
|
}
|
|
613
1073
|
],
|
|
614
1074
|
"reference_designs": [
|
|
@@ -623,11 +1083,40 @@
|
|
|
623
1083
|
"en": "Put SenseCAP soil and air sensors on a Home Assistant dashboard — through the SenseCAP cloud, or through a LoRaWAN network server you run yourself with no internet at all."
|
|
624
1084
|
},
|
|
625
1085
|
"wiki_url": "",
|
|
1086
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/agri_env_monitor",
|
|
1087
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/agri_env_monitor",
|
|
626
1088
|
"presets": [
|
|
627
1089
|
"cloud",
|
|
628
1090
|
"tts_local",
|
|
629
1091
|
"chirpstack_local"
|
|
630
|
-
]
|
|
1092
|
+
],
|
|
1093
|
+
"diagnostic_playbook": {
|
|
1094
|
+
"domain": "智慧农业 / 环境监测与微气象",
|
|
1095
|
+
"core_dimensions": [
|
|
1096
|
+
"集中大棚 vs 广域农田",
|
|
1097
|
+
"市电 vs 太阳能/电池供电",
|
|
1098
|
+
"监测指标与探头深度"
|
|
1099
|
+
],
|
|
1100
|
+
"questions": [
|
|
1101
|
+
{
|
|
1102
|
+
"dimension": "topology",
|
|
1103
|
+
"question": "监测区域是集中式连栋温室大棚（百米级），还是大面积户外大田/果园（数公里级）？",
|
|
1104
|
+
"rationale": "大棚内百米级可采用 RS485 有线总线集中组网；广域大田推荐 LoRaWAN 远距离低功耗无线传输，配合 SenseCAP M2 网关。"
|
|
1105
|
+
},
|
|
1106
|
+
{
|
|
1107
|
+
"dimension": "power",
|
|
1108
|
+
"question": "现场测点是否有 220V 市电供电，还是需要野外太阳能板/锂电池长续航供电？",
|
|
1109
|
+
"rationale": "市电可支持持续高频数据上报；无市电需要选用带内置超大锂电池、支持休眠唤醒的低功耗无线传感器（如 S2100/S210x）。"
|
|
1110
|
+
},
|
|
1111
|
+
{
|
|
1112
|
+
"dimension": "sensing_depth",
|
|
1113
|
+
"question": "需要监测哪些核心环境指标？仅是空气温湿度/光照/CO2，还是包括土壤剖面墒情（深层水分/EC/pH）或气象风速风向？",
|
|
1114
|
+
"rationale": "决定是配置一体化多合一微气象站（如 S700/S2120），还是选配工业级土壤三参数/水肥专用探针与变送器。"
|
|
1115
|
+
}
|
|
1116
|
+
]
|
|
1117
|
+
},
|
|
1118
|
+
"published": false,
|
|
1119
|
+
"visibility": "staging"
|
|
631
1120
|
},
|
|
632
1121
|
{
|
|
633
1122
|
"id": "ai_lab",
|
|
@@ -640,11 +1129,16 @@
|
|
|
640
1129
|
"en": "## What This Reference Design Is\n\n**Three kinds of AI model to try on one Rockchip box.**\n\nObject detection, text chat and image Q&A all run on the built-in NPU.\n\nPick a preset, deploy with one click, and call the API. Detection is REST; chat is OpenAI-compatible.\n\nAll three presets can share one RK3576 box. Existing cameras, NVRs or chat apps connect by changing an address.\n\nImages and conversations stay on the device, and it runs offline after deployment.\n\n**Limits:** chat and vision chat need the reComputer RK3576 Series. 7B chat and vision chat need 8GB of RAM or more.\n"
|
|
641
1130
|
},
|
|
642
1131
|
"wiki_url": "",
|
|
1132
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/ai_lab",
|
|
1133
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/ai_lab",
|
|
643
1134
|
"presets": [
|
|
644
1135
|
"object_detection",
|
|
645
1136
|
"llm_chat",
|
|
646
1137
|
"vlm_chat"
|
|
647
|
-
]
|
|
1138
|
+
],
|
|
1139
|
+
"diagnostic_playbook": null,
|
|
1140
|
+
"published": true,
|
|
1141
|
+
"visibility": "production"
|
|
648
1142
|
},
|
|
649
1143
|
{
|
|
650
1144
|
"id": "conversational_voice_ai",
|
|
@@ -657,10 +1151,39 @@
|
|
|
657
1151
|
"en": "A voice terminal that answers on the device and can be interrupted mid-answer. Listening and speaking stay local; the conversation model is either your own cloud endpoint or on-device. Runs on a reComputer RK, a reComputer J30 / J40 (Orin) or a reComputer R2000 series, with the conversation language fixed at deploy time."
|
|
658
1152
|
},
|
|
659
1153
|
"wiki_url": "https://wiki.seeedstudio.com/solutions/conversational-voice-ai/",
|
|
1154
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/conversational_voice_ai",
|
|
1155
|
+
"repo_url": "https://github.com/suharvest/openvoicestream",
|
|
660
1156
|
"presets": [
|
|
661
1157
|
"cloud_llm",
|
|
662
1158
|
"local_llm"
|
|
663
|
-
]
|
|
1159
|
+
],
|
|
1160
|
+
"diagnostic_playbook": {
|
|
1161
|
+
"domain": "声学与音频 AI / 设备故障听诊",
|
|
1162
|
+
"core_dimensions": [
|
|
1163
|
+
"被测机械类型与异响特征",
|
|
1164
|
+
"声学麦克风 vs 振动声发射传感器",
|
|
1165
|
+
"车间环境背景噪音"
|
|
1166
|
+
],
|
|
1167
|
+
"questions": [
|
|
1168
|
+
{
|
|
1169
|
+
"dimension": "machine_defect",
|
|
1170
|
+
"question": "被监测的机械设备是什么（例如电机、轴承、齿轮箱、还是水泵压缩机）？想捕获的异常特征是什么（异响磨损、撞击声还是高压气体泄漏）？",
|
|
1171
|
+
"rationale": "决定选择声学麦克风阵列还是接触式高频振动/声发射探头。"
|
|
1172
|
+
},
|
|
1173
|
+
{
|
|
1174
|
+
"dimension": "ambient_noise",
|
|
1175
|
+
"question": "设备周边是否有其他强烈机械运转的背景杂音？",
|
|
1176
|
+
"rationale": "强背景杂音需利用端侧硬件 DSP 滤波器及降噪算法将工作主频滤除，突出异常脉冲。"
|
|
1177
|
+
},
|
|
1178
|
+
{
|
|
1179
|
+
"dimension": "alarm_latency",
|
|
1180
|
+
"question": "检测到异响异常后，希望在多长时间内告警，并通过何种方式通知维护人员？",
|
|
1181
|
+
"rationale": "确定边缘推理实时性要求以及告警输出联动链路（声光/短信/PLC 停机信号）。"
|
|
1182
|
+
}
|
|
1183
|
+
]
|
|
1184
|
+
},
|
|
1185
|
+
"published": true,
|
|
1186
|
+
"visibility": "production"
|
|
664
1187
|
},
|
|
665
1188
|
{
|
|
666
1189
|
"id": "depth_anything_v3",
|
|
@@ -673,9 +1196,14 @@
|
|
|
673
1196
|
"en": "## What This Reference Design Is\n\n**Distance estimates from an ordinary USB camera.** The depth model runs on the Jetson GPU.\n\nThe output is one video stream showing the original picture, a colour depth map and a 3D point cloud together. Any RTSP player or the platform preview can show it.\n\nDeployment is one click over SSH. The first deploy builds the inference engine on the device; restarts reuse it.\n\nThe stream stays on the LAN, and it runs offline after deployment.\n\n**Limits:** depth is estimated by a single-camera model. It suits prototypes and demos, not lidar-grade ranging.\n"
|
|
674
1197
|
},
|
|
675
1198
|
"wiki_url": "",
|
|
1199
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/depth_anything_v3",
|
|
1200
|
+
"repo_url": "https://github.com/Seeed-Projects/jetson-examples",
|
|
676
1201
|
"presets": [
|
|
677
1202
|
"jetson_depth"
|
|
678
|
-
]
|
|
1203
|
+
],
|
|
1204
|
+
"diagnostic_playbook": null,
|
|
1205
|
+
"published": true,
|
|
1206
|
+
"visibility": "production"
|
|
679
1207
|
},
|
|
680
1208
|
{
|
|
681
1209
|
"id": "edge-anpr-plate-recognition",
|
|
@@ -688,7 +1216,36 @@
|
|
|
688
1216
|
"en": ""
|
|
689
1217
|
},
|
|
690
1218
|
"wiki_url": "",
|
|
691
|
-
"
|
|
1219
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/edge-anpr-plate-recognition",
|
|
1220
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_plate_recognition",
|
|
1221
|
+
"presets": [],
|
|
1222
|
+
"diagnostic_playbook": {
|
|
1223
|
+
"domain": "智慧交通 / 园区道闸与车牌识别",
|
|
1224
|
+
"core_dimensions": [
|
|
1225
|
+
"道闸卡口 vs 主干道抓拍",
|
|
1226
|
+
"夜间补光与逆光条件",
|
|
1227
|
+
"继电器开闸联动链路"
|
|
1228
|
+
],
|
|
1229
|
+
"questions": [
|
|
1230
|
+
{
|
|
1231
|
+
"dimension": "traffic_speed",
|
|
1232
|
+
"question": "抓拍点位是出入口道闸（低速停车抓拍，1~2 车道），还是园区/厂区主干道（车辆行驶中抓拍）？",
|
|
1233
|
+
"rationale": "道闸场景普通高帧率相机即可胜任；行驶干道需全局快门与快速连续跟踪推理算法支持。"
|
|
1234
|
+
},
|
|
1235
|
+
{
|
|
1236
|
+
"dimension": "lighting_condition",
|
|
1237
|
+
"question": "夜间或逆光环境如何？安装点是否有充足照明，还是需要相机自带或外接强光抑制爆闪补光灯？",
|
|
1238
|
+
"rationale": "车牌反光与大灯直射在出入口很常见，强光抑制与补光同步触发至关重要。"
|
|
1239
|
+
},
|
|
1240
|
+
{
|
|
1241
|
+
"dimension": "gate_control",
|
|
1242
|
+
"question": "车牌识别成功后，是需要边缘主机直接通过板载继电器/IO 接口控制道闸开杆，还是仅需通过网络上报给您现有的停车计费系统？",
|
|
1243
|
+
"rationale": "决定是否需要硬件级隔离继电器控制配件，以及是否需要本地脱机白名单离线放行能力。"
|
|
1244
|
+
}
|
|
1245
|
+
]
|
|
1246
|
+
},
|
|
1247
|
+
"published": true,
|
|
1248
|
+
"visibility": "staging"
|
|
692
1249
|
},
|
|
693
1250
|
{
|
|
694
1251
|
"id": "edge_inspection_assembly",
|
|
@@ -701,11 +1258,40 @@
|
|
|
701
1258
|
"en": "Missing-part and dimension inspection on the edge device. One fixed camera per station checks the expected items and the measured sizes, and merges them into a single OK/NG verdict that reaches the PLC and the MES at the same time. Runs on a reComputer J30 / J40 (Orin) or on a reComputer R2000 Series with the Hailo-8 option (R2035-12)."
|
|
702
1259
|
},
|
|
703
1260
|
"wiki_url": "",
|
|
1261
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/edge_inspection_assembly",
|
|
1262
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_inspection_assembly",
|
|
704
1263
|
"presets": [
|
|
705
1264
|
"jetson",
|
|
706
1265
|
"hailo",
|
|
707
1266
|
"recamera_pro"
|
|
708
|
-
]
|
|
1267
|
+
],
|
|
1268
|
+
"diagnostic_playbook": {
|
|
1269
|
+
"domain": "工业视觉质检 / 表面缺陷与装配复检",
|
|
1270
|
+
"core_dimensions": [
|
|
1271
|
+
"产线生产节拍与相机快门",
|
|
1272
|
+
"工件材质反光与照明",
|
|
1273
|
+
"剔除执行与 PLC 信号闭环"
|
|
1274
|
+
],
|
|
1275
|
+
"questions": [
|
|
1276
|
+
{
|
|
1277
|
+
"dimension": "line_speed",
|
|
1278
|
+
"question": "现场流水线的生产节拍是怎样的（每分钟过检多少件产品，工件是静止拍照还是运动中飞拍）？",
|
|
1279
|
+
"rationale": "决定相机曝光类型（运动飞拍必须全局快门 Global Shutter），以及端侧推理帧率与 Jetson 算力等级（Orin Nano vs Orin NX）。"
|
|
1280
|
+
},
|
|
1281
|
+
{
|
|
1282
|
+
"dimension": "materials_lighting",
|
|
1283
|
+
"question": "被测工件表面是什么材质（反光金属、高光塑料还是普通漫反射包装）？缺陷尺寸大概在什么毫米级别？",
|
|
1284
|
+
"rationale": "反光表面需定制特殊工业光源（如偏光环形光、同轴光）消除眩光；缺陷精度决定工业相机分辨率与镜头焦距。"
|
|
1285
|
+
},
|
|
1286
|
+
{
|
|
1287
|
+
"dimension": "plc_integration",
|
|
1288
|
+
"question": "检测出不良品后，边缘设备是否需要直接向现场 PLC 或气缸发送剔除信号？",
|
|
1289
|
+
"rationale": "决定是否需要选择带工业隔离数字量 I/O 的工控机型（如 reComputer Industrial 系列），并配置现场总线。"
|
|
1290
|
+
}
|
|
1291
|
+
]
|
|
1292
|
+
},
|
|
1293
|
+
"published": false,
|
|
1294
|
+
"visibility": "staging"
|
|
709
1295
|
},
|
|
710
1296
|
{
|
|
711
1297
|
"id": "edge_inspection_surface",
|
|
@@ -718,10 +1304,39 @@
|
|
|
718
1304
|
"en": "Steel surface defect inspection that runs on the edge device: a fixed camera on the strip or the part, one OK/NG verdict per frame, delivered to the PLC and to the MES at the same time. Runs on a reComputer J30 / J40 (Orin) or on a reComputer R2000 Series with the Hailo-8 option (R2035-12)."
|
|
719
1305
|
},
|
|
720
1306
|
"wiki_url": "",
|
|
1307
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/edge_inspection_surface",
|
|
1308
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_inspection_surface",
|
|
721
1309
|
"presets": [
|
|
722
1310
|
"orin",
|
|
723
1311
|
"pi_hailo"
|
|
724
|
-
]
|
|
1312
|
+
],
|
|
1313
|
+
"diagnostic_playbook": {
|
|
1314
|
+
"domain": "工业视觉质检 / 表面缺陷与装配复检",
|
|
1315
|
+
"core_dimensions": [
|
|
1316
|
+
"产线生产节拍与相机快门",
|
|
1317
|
+
"工件材质反光与照明",
|
|
1318
|
+
"剔除执行与 PLC 信号闭环"
|
|
1319
|
+
],
|
|
1320
|
+
"questions": [
|
|
1321
|
+
{
|
|
1322
|
+
"dimension": "line_speed",
|
|
1323
|
+
"question": "现场流水线的生产节拍是怎样的（每分钟过检多少件产品，工件是静止拍照还是运动中飞拍）？",
|
|
1324
|
+
"rationale": "决定相机曝光类型（运动飞拍必须全局快门 Global Shutter），以及端侧推理帧率与 Jetson 算力等级（Orin Nano vs Orin NX）。"
|
|
1325
|
+
},
|
|
1326
|
+
{
|
|
1327
|
+
"dimension": "materials_lighting",
|
|
1328
|
+
"question": "被测工件表面是什么材质（反光金属、高光塑料还是普通漫反射包装）？缺陷尺寸大概在什么毫米级别？",
|
|
1329
|
+
"rationale": "反光表面需定制特殊工业光源（如偏光环形光、同轴光）消除眩光；缺陷精度决定工业相机分辨率与镜头焦距。"
|
|
1330
|
+
},
|
|
1331
|
+
{
|
|
1332
|
+
"dimension": "plc_integration",
|
|
1333
|
+
"question": "检测出不良品后，边缘设备是否需要直接向现场 PLC 或气缸发送剔除信号？",
|
|
1334
|
+
"rationale": "决定是否需要选择带工业隔离数字量 I/O 的工控机型（如 reComputer Industrial 系列），并配置现场总线。"
|
|
1335
|
+
}
|
|
1336
|
+
]
|
|
1337
|
+
},
|
|
1338
|
+
"published": false,
|
|
1339
|
+
"visibility": "staging"
|
|
725
1340
|
},
|
|
726
1341
|
{
|
|
727
1342
|
"id": "edge_retail_recognition",
|
|
@@ -734,11 +1349,40 @@
|
|
|
734
1349
|
"en": "## What This Reference Design Is\n\n**A camera reads the products on a shelf or a checkout belt.**\n\nIt boxes every item, then looks each one up in a product library to see which it is.\n\nAt the checkout each item is counted once. On the shelf every slot is reported as ok, empty, wrong item or unknown.\n\nAdding a product needs no retraining: photograph it 3 to 8 times and upload.\n\n**Limits:** an item has to be fully visible — occluded or stacked goods are missed. Each SKU needs at least three enrolment photos.\n\nChanging the embedding model rebuilds the whole library. The shipped weights are licensed for non-commercial use only.\n"
|
|
735
1350
|
},
|
|
736
1351
|
"wiki_url": "https://wiki.seeedstudio.com/solutions/edge-product-recognition/",
|
|
1352
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/edge_retail_recognition",
|
|
1353
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_retail_recognition",
|
|
737
1354
|
"presets": [
|
|
738
1355
|
"p1_rockchip",
|
|
739
1356
|
"p2_pi5_hailo",
|
|
740
1357
|
"p3_jetson_orin"
|
|
741
|
-
]
|
|
1358
|
+
],
|
|
1359
|
+
"diagnostic_playbook": {
|
|
1360
|
+
"domain": "智慧零售门店 / 客流统计与货架动线",
|
|
1361
|
+
"core_dimensions": [
|
|
1362
|
+
"进出店客流计数 vs 店内热力动线",
|
|
1363
|
+
"门头吊顶施工布线",
|
|
1364
|
+
"多门店数据汇聚方式"
|
|
1365
|
+
],
|
|
1366
|
+
"questions": [
|
|
1367
|
+
{
|
|
1368
|
+
"dimension": "analytics_scope",
|
|
1369
|
+
"question": "统计的主要诉求是“出入口进店人数/客流双向计数”，还是“店内各货架区域的顾客停留时长与热力分布”？",
|
|
1370
|
+
"rationale": "出入口仅需门头单台垂直俯视 AI 相机；货架热力需广角全景相机或多机拼接。"
|
|
1371
|
+
},
|
|
1372
|
+
{
|
|
1373
|
+
"dimension": "ceiling_cabling",
|
|
1374
|
+
"question": "现场安装点位（通常在门头吊顶或天花板）是否预留了网线和供电？",
|
|
1375
|
+
"rationale": "支持 PoE 供电只需一根网线即可完成供电与通信，最利于商铺免破坏装修快速施工。"
|
|
1376
|
+
},
|
|
1377
|
+
{
|
|
1378
|
+
"dimension": "data_aggregation",
|
|
1379
|
+
"question": "连锁门店的数据汇总方式是怎样的？是单店本地显示，还是需要将多店客流数据自动上传到您的总部云端或 ERP 系统？",
|
|
1380
|
+
"rationale": "确认网络上报协议（MQTT/HTTP REST）及离线断网本地缓存需求。"
|
|
1381
|
+
}
|
|
1382
|
+
]
|
|
1383
|
+
},
|
|
1384
|
+
"published": true,
|
|
1385
|
+
"visibility": "production"
|
|
742
1386
|
},
|
|
743
1387
|
{
|
|
744
1388
|
"id": "edge_security",
|
|
@@ -751,12 +1395,41 @@
|
|
|
751
1395
|
"en": "Restricted-zone, line-crossing and loitering alerts judged on the edge box itself. Draw rules in a browser, watch the wall, clear alerts. Video stays on site."
|
|
752
1396
|
},
|
|
753
1397
|
"wiki_url": "",
|
|
1398
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/edge_security",
|
|
1399
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_security",
|
|
754
1400
|
"presets": [
|
|
755
1401
|
"jetson_hub",
|
|
756
1402
|
"rk3588",
|
|
757
1403
|
"hailo",
|
|
758
1404
|
"hub_only"
|
|
759
|
-
]
|
|
1405
|
+
],
|
|
1406
|
+
"diagnostic_playbook": {
|
|
1407
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
1408
|
+
"core_dimensions": [
|
|
1409
|
+
"分析目标与算法类型",
|
|
1410
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
1411
|
+
"夜间与恶劣环境"
|
|
1412
|
+
],
|
|
1413
|
+
"questions": [
|
|
1414
|
+
{
|
|
1415
|
+
"dimension": "analytics_target",
|
|
1416
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
1417
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
1418
|
+
},
|
|
1419
|
+
{
|
|
1420
|
+
"dimension": "stream_architecture",
|
|
1421
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
1422
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
1423
|
+
},
|
|
1424
|
+
{
|
|
1425
|
+
"dimension": "environment_lighting",
|
|
1426
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
1427
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
1428
|
+
}
|
|
1429
|
+
]
|
|
1430
|
+
},
|
|
1431
|
+
"published": false,
|
|
1432
|
+
"visibility": "staging"
|
|
760
1433
|
},
|
|
761
1434
|
{
|
|
762
1435
|
"id": "edge_waste_sorting",
|
|
@@ -769,13 +1442,42 @@
|
|
|
769
1442
|
"en": "Trigger a shot at the bin and get back what the item is made of and which of the four Chinese municipal waste streams it belongs in — one MQTT message per item, decided on the device, plus a GPIO output for a flap or a lane indicator."
|
|
770
1443
|
},
|
|
771
1444
|
"wiki_url": "https://wiki.seeedstudio.com/solutions/edge-waste-sorting/",
|
|
1445
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/edge_waste_sorting",
|
|
1446
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_waste_sorting",
|
|
772
1447
|
"presets": [
|
|
773
1448
|
"orin",
|
|
774
1449
|
"recomputer_r20",
|
|
775
1450
|
"recamera",
|
|
776
1451
|
"recamera_pro",
|
|
777
1452
|
"recomputer_rk3588"
|
|
778
|
-
]
|
|
1453
|
+
],
|
|
1454
|
+
"diagnostic_playbook": {
|
|
1455
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
1456
|
+
"core_dimensions": [
|
|
1457
|
+
"分析目标与算法类型",
|
|
1458
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
1459
|
+
"夜间与恶劣环境"
|
|
1460
|
+
],
|
|
1461
|
+
"questions": [
|
|
1462
|
+
{
|
|
1463
|
+
"dimension": "analytics_target",
|
|
1464
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
1465
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
1466
|
+
},
|
|
1467
|
+
{
|
|
1468
|
+
"dimension": "stream_architecture",
|
|
1469
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
1470
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
1471
|
+
},
|
|
1472
|
+
{
|
|
1473
|
+
"dimension": "environment_lighting",
|
|
1474
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
1475
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
1476
|
+
}
|
|
1477
|
+
]
|
|
1478
|
+
},
|
|
1479
|
+
"published": true,
|
|
1480
|
+
"visibility": "production"
|
|
779
1481
|
},
|
|
780
1482
|
{
|
|
781
1483
|
"id": "fall_detection",
|
|
@@ -788,13 +1490,42 @@
|
|
|
788
1490
|
"en": "On-device fall detection — pose estimation, a per-person temporal state machine and one MQTT event, all local. All-in-one camera, or your existing RTSP cameras on a Jetson, Rockchip NPU or Hailo-8 host."
|
|
789
1491
|
},
|
|
790
1492
|
"wiki_url": "https://wiki.seeedstudio.com/solutions/edge-fall-detection/",
|
|
1493
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/fall_detection",
|
|
1494
|
+
"repo_url": "https://github.com/suharvest/edgefallkit",
|
|
791
1495
|
"presets": [
|
|
792
1496
|
"recamera",
|
|
793
1497
|
"recamera_pro",
|
|
794
1498
|
"jetson",
|
|
795
1499
|
"rk",
|
|
796
1500
|
"hailo"
|
|
797
|
-
]
|
|
1501
|
+
],
|
|
1502
|
+
"diagnostic_playbook": {
|
|
1503
|
+
"domain": "智慧养老 / 室内监护",
|
|
1504
|
+
"core_dimensions": [
|
|
1505
|
+
"集中 vs 分散空间分布",
|
|
1506
|
+
"存量摄像头利旧",
|
|
1507
|
+
"隐私保护与传感器形态"
|
|
1508
|
+
],
|
|
1509
|
+
"questions": [
|
|
1510
|
+
{
|
|
1511
|
+
"dimension": "topology",
|
|
1512
|
+
"question": "老人房间和公共区域是在同一层/同一楼栋比较集中，还是分散在多栋楼或较远区域？",
|
|
1513
|
+
"rationale": "集中分布可用 1 台 reComputer 主机拉多路 RTSP 流摊薄成本；分散点位推荐每间房独立 reCamera 一体机免拉长线。"
|
|
1514
|
+
},
|
|
1515
|
+
{
|
|
1516
|
+
"dimension": "asset_reuse",
|
|
1517
|
+
"question": "现场是否已经安装了支持 RTSP/ONVIF 协议的监控摄像头（如海康、大华等）？",
|
|
1518
|
+
"rationale": "已有摄像头可直接复用利旧，只需采购边缘算力盒，省去镜头重购成本；无摄像头则推荐成套硬件。"
|
|
1519
|
+
},
|
|
1520
|
+
{
|
|
1521
|
+
"dimension": "privacy_boundary",
|
|
1522
|
+
"question": "卫生间、卧室等高隐私区域是否对纯光学摄像头有顾虑，是否需要无视觉隐私的毫米波雷达方案？",
|
|
1523
|
+
"rationale": "私密区域用 60GHz 毫米波雷达替代光学镜头，既可精确检测跌倒卧床，又彻底消除侵犯隐私争议。"
|
|
1524
|
+
}
|
|
1525
|
+
]
|
|
1526
|
+
},
|
|
1527
|
+
"published": true,
|
|
1528
|
+
"visibility": "production"
|
|
798
1529
|
},
|
|
799
1530
|
{
|
|
800
1531
|
"id": "gpt_oss_20b",
|
|
@@ -807,9 +1538,14 @@
|
|
|
807
1538
|
"en": "## What This Reference Design Is\n\n**A 20-billion-parameter chat model on one Jetson.** No cloud and no cloud API key.\n\nDeployment opens an OpenAI-compatible API. Existing SDKs, chat apps or the OpenClaw gateway connect by changing an address.\n\nConversations travel only between your app and the device, and it runs offline after deployment.\n\nContext length and GPU layers are deploy-time settings.\n\n**Limits:** it needs the Orin NX 16GB module. The default context is 1024 tokens, and the first request after deployment warms up for a few minutes.\n"
|
|
808
1539
|
},
|
|
809
1540
|
"wiki_url": "",
|
|
1541
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/gpt_oss_20b",
|
|
1542
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/gpt_oss_20b",
|
|
810
1543
|
"presets": [
|
|
811
1544
|
"jetson_got_oss"
|
|
812
|
-
]
|
|
1545
|
+
],
|
|
1546
|
+
"diagnostic_playbook": null,
|
|
1547
|
+
"published": true,
|
|
1548
|
+
"visibility": "production"
|
|
813
1549
|
},
|
|
814
1550
|
{
|
|
815
1551
|
"id": "gun_detection_frigate",
|
|
@@ -822,10 +1558,39 @@
|
|
|
822
1558
|
"en": "## What This Reference Design Is\n\n**Gun detection for the IP cameras you already have.** One edge AI host checks every frame. It raises an alert when a gun appears.\n\nEach detection saves a clip and a snapshot. Events play back in the web dashboard.\n\nAlerts go out over MQTT, so alarm and automation systems can subscribe.\n\nVideo is processed and stored on a host inside your network, not in the cloud. The host is a Jetson or a Hailo box.\n\n**Limits:** detection depends on how large and visible the gun is in the frame. This is an assistive alert, not a certified security product.\n"
|
|
823
1559
|
},
|
|
824
1560
|
"wiki_url": "",
|
|
1561
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/gun_detection_frigate",
|
|
1562
|
+
"repo_url": "https://github.com/Seeed-Studio/frigate-on-jetson",
|
|
825
1563
|
"presets": [
|
|
826
1564
|
"jetson",
|
|
827
1565
|
"r2000_hailo"
|
|
828
|
-
]
|
|
1566
|
+
],
|
|
1567
|
+
"diagnostic_playbook": {
|
|
1568
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
1569
|
+
"core_dimensions": [
|
|
1570
|
+
"分析目标与算法类型",
|
|
1571
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
1572
|
+
"夜间与恶劣环境"
|
|
1573
|
+
],
|
|
1574
|
+
"questions": [
|
|
1575
|
+
{
|
|
1576
|
+
"dimension": "analytics_target",
|
|
1577
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
1578
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
1579
|
+
},
|
|
1580
|
+
{
|
|
1581
|
+
"dimension": "stream_architecture",
|
|
1582
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
1583
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
1584
|
+
},
|
|
1585
|
+
{
|
|
1586
|
+
"dimension": "environment_lighting",
|
|
1587
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
1588
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
1589
|
+
}
|
|
1590
|
+
]
|
|
1591
|
+
},
|
|
1592
|
+
"published": true,
|
|
1593
|
+
"visibility": "production"
|
|
829
1594
|
},
|
|
830
1595
|
{
|
|
831
1596
|
"id": "home-assistant-local-voice-hub",
|
|
@@ -838,9 +1603,14 @@
|
|
|
838
1603
|
"en": ""
|
|
839
1604
|
},
|
|
840
1605
|
"wiki_url": "",
|
|
1606
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/home-assistant-local-voice-hub",
|
|
1607
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/home_assistant_whole_home",
|
|
841
1608
|
"presets": [
|
|
842
1609
|
"rpi_jetson"
|
|
843
|
-
]
|
|
1610
|
+
],
|
|
1611
|
+
"diagnostic_playbook": null,
|
|
1612
|
+
"published": true,
|
|
1613
|
+
"visibility": "staging"
|
|
844
1614
|
},
|
|
845
1615
|
{
|
|
846
1616
|
"id": "indoor_positioning_ble_lorawan",
|
|
@@ -853,11 +1623,40 @@
|
|
|
853
1623
|
"en": "Track assets and people indoors and outdoors on one map — BLE beacons inside, GNSS outside, with floor-plan georeferencing, geofence alarms and an offline basemap option."
|
|
854
1624
|
},
|
|
855
1625
|
"wiki_url": "",
|
|
1626
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/indoor_positioning_ble_lorawan",
|
|
1627
|
+
"repo_url": "https://github.com/Seeed-Solution/Solution_IndoorPositioning_H5",
|
|
856
1628
|
"presets": [
|
|
857
1629
|
"starter",
|
|
858
1630
|
"standard",
|
|
859
1631
|
"enterprise"
|
|
860
|
-
]
|
|
1632
|
+
],
|
|
1633
|
+
"diagnostic_playbook": {
|
|
1634
|
+
"domain": "室内外定位 / 资产与人员追踪",
|
|
1635
|
+
"core_dimensions": [
|
|
1636
|
+
"纯室内 vs 室内外混合",
|
|
1637
|
+
"定位精度期望（米级 vs 区域级）",
|
|
1638
|
+
"佩戴形式与免维护续航"
|
|
1639
|
+
],
|
|
1640
|
+
"questions": [
|
|
1641
|
+
{
|
|
1642
|
+
"dimension": "spatial_scope",
|
|
1643
|
+
"question": "定位场景是纯室内（厂房/展厅/仓库），还是室内外混合（比如仓库到室外堆场，甚至货物长途运输）？",
|
|
1644
|
+
"rationale": "纯室内基于 BLE 信标定位；室内外混合推荐 SenseCAP T1000 追踪器，室内切蓝牙/Wi-Fi 定位，室外切 GPS/北斗。"
|
|
1645
|
+
},
|
|
1646
|
+
{
|
|
1647
|
+
"dimension": "accuracy_budget",
|
|
1648
|
+
"question": "对定位精度的期望是怎样的？是需要精确到米级的具体坐标，还是只要知道人在哪间房/资产在哪个货架区域即可？",
|
|
1649
|
+
"rationale": "米级需部署高密度蓝牙基站；区域级可大幅减少基站数量，极大节约硬件成本与施工布线。"
|
|
1650
|
+
},
|
|
1651
|
+
{
|
|
1652
|
+
"dimension": "form_battery",
|
|
1653
|
+
"question": "被追踪对象的形态是什么（人员佩戴胸卡工牌，还是贴在货物托盘/设备上）？期望续航时间是多久？",
|
|
1654
|
+
"rationale": "决定选用超薄卡片型轻量 Tracker 还是超长续航工业 Tracker。"
|
|
1655
|
+
}
|
|
1656
|
+
]
|
|
1657
|
+
},
|
|
1658
|
+
"published": true,
|
|
1659
|
+
"visibility": "production"
|
|
861
1660
|
},
|
|
862
1661
|
{
|
|
863
1662
|
"id": "jetson_voice_assistant",
|
|
@@ -870,9 +1669,14 @@
|
|
|
870
1669
|
"en": "A local speech service for your own application — send audio in and get text back, send text in and get speech back. Runs on reComputer J40 / J30, reComputer RK3588 / RK3576 or Pi 5, offline after the first deployment."
|
|
871
1670
|
},
|
|
872
1671
|
"wiki_url": "",
|
|
1672
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/jetson_voice_assistant",
|
|
1673
|
+
"repo_url": "https://github.com/suharvest/openvoicestream",
|
|
873
1674
|
"presets": [
|
|
874
1675
|
"default"
|
|
875
|
-
]
|
|
1676
|
+
],
|
|
1677
|
+
"diagnostic_playbook": null,
|
|
1678
|
+
"published": true,
|
|
1679
|
+
"visibility": "production"
|
|
876
1680
|
},
|
|
877
1681
|
{
|
|
878
1682
|
"id": "multi_protocol_gateway",
|
|
@@ -885,9 +1689,38 @@
|
|
|
885
1689
|
"en": "## What This Reference Design Is\n\n**It merges four field protocols into one interface.**\n\nThe gateway talks to OPC UA, Modbus, BACnet and MQTT devices at once. The system above integrates once, not once per controller.\n\nSite differences become configuration: scan for devices, confirm which readings you want, then expose them. It manages up to 2,000 readings, 50 of them writable.\n\nEvery write is traceable: what was sent, what the device answered, and when it finished.\n\n**Limits:** a point the scan finds is confirmed on site before it is exposed. Serial devices need a different deployment profile, and production writes stay disabled until commissioning passes.\n"
|
|
886
1690
|
},
|
|
887
1691
|
"wiki_url": "",
|
|
1692
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/multi_protocol_gateway",
|
|
1693
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/multi_protocol_gateway",
|
|
888
1694
|
"presets": [
|
|
889
1695
|
"standard"
|
|
890
|
-
]
|
|
1696
|
+
],
|
|
1697
|
+
"diagnostic_playbook": {
|
|
1698
|
+
"domain": "现场控制与自动化 / PLC 边缘互联",
|
|
1699
|
+
"core_dimensions": [
|
|
1700
|
+
"工控总线协议种类",
|
|
1701
|
+
"导轨安装与供电环境",
|
|
1702
|
+
"边缘计算与控制响应周期"
|
|
1703
|
+
],
|
|
1704
|
+
"questions": [
|
|
1705
|
+
{
|
|
1706
|
+
"dimension": "bus_protocol",
|
|
1707
|
+
"question": "现场下位机设备主要采用什么总线和通信协议（如 Modbus TCP/RTU、CANopen、PROFINET、EtherNet/IP）？",
|
|
1708
|
+
"rationale": "决定边缘网关的物理接口（隔离 RS485、双网口、CAN 接口）以及协议转换中间件配置。"
|
|
1709
|
+
},
|
|
1710
|
+
{
|
|
1711
|
+
"dimension": "cabinet_power",
|
|
1712
|
+
"question": "设备是安装在标准工业电控柜导轨上吗？现场供电是直流 24V DC 还是交流 220V？",
|
|
1713
|
+
"rationale": "确认机型是否支持 DIN 导轨卡扣安装，以及宽压 DC 9~36V 输入。"
|
|
1714
|
+
},
|
|
1715
|
+
{
|
|
1716
|
+
"dimension": "control_cycle",
|
|
1717
|
+
"question": "业务需要做实时控制闭环（毫秒级控制周期），还是做上层数据采集与边缘分析诊断（秒级/分级）？",
|
|
1718
|
+
"rationale": "实时控制需要带实时补丁（PREEMPT_RT）的边缘控制器；数据采集与分析常规工业边缘电脑即可满足。"
|
|
1719
|
+
}
|
|
1720
|
+
]
|
|
1721
|
+
},
|
|
1722
|
+
"published": true,
|
|
1723
|
+
"visibility": "production"
|
|
891
1724
|
},
|
|
892
1725
|
{
|
|
893
1726
|
"id": "openclaw_deploy",
|
|
@@ -900,10 +1733,15 @@
|
|
|
900
1733
|
"en": "## What This Reference Design Is\n\n**One AI assistant shared by more than 20 chat platforms.** WeChat, Telegram, Slack, DingTalk and Feishu all connect.\n\nThe gateway runs on your own reComputer. There is one integration to maintain; models and platforms change in the gateway.\n\nTwo routes are available. A Jetson runs the model locally, so message content is not sent to an AI provider. A lightweight host uses cloud models, paid per call.\n\n**Limits:** local models are small, 2B to 4B. On the cloud route, message content goes to the provider you configure.\n"
|
|
901
1734
|
},
|
|
902
1735
|
"wiki_url": "",
|
|
1736
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/openclaw_deploy",
|
|
1737
|
+
"repo_url": "https://github.com/openclaw/openclaw",
|
|
903
1738
|
"presets": [
|
|
904
1739
|
"openclaw_basic",
|
|
905
1740
|
"openclaw_recomputer_r"
|
|
906
|
-
]
|
|
1741
|
+
],
|
|
1742
|
+
"diagnostic_playbook": null,
|
|
1743
|
+
"published": true,
|
|
1744
|
+
"visibility": "production"
|
|
907
1745
|
},
|
|
908
1746
|
{
|
|
909
1747
|
"id": "parking-entry-exit-counting",
|
|
@@ -916,9 +1754,38 @@
|
|
|
916
1754
|
"en": ""
|
|
917
1755
|
},
|
|
918
1756
|
"wiki_url": "",
|
|
1757
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/parking-entry-exit-counting",
|
|
1758
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_parking_counting",
|
|
919
1759
|
"presets": [
|
|
920
1760
|
"ip_camera_box"
|
|
921
|
-
]
|
|
1761
|
+
],
|
|
1762
|
+
"diagnostic_playbook": {
|
|
1763
|
+
"domain": "智慧交通 / 园区道闸与车牌识别",
|
|
1764
|
+
"core_dimensions": [
|
|
1765
|
+
"道闸卡口 vs 主干道抓拍",
|
|
1766
|
+
"夜间补光与逆光条件",
|
|
1767
|
+
"继电器开闸联动链路"
|
|
1768
|
+
],
|
|
1769
|
+
"questions": [
|
|
1770
|
+
{
|
|
1771
|
+
"dimension": "traffic_speed",
|
|
1772
|
+
"question": "抓拍点位是出入口道闸（低速停车抓拍，1~2 车道），还是园区/厂区主干道（车辆行驶中抓拍）？",
|
|
1773
|
+
"rationale": "道闸场景普通高帧率相机即可胜任；行驶干道需全局快门与快速连续跟踪推理算法支持。"
|
|
1774
|
+
},
|
|
1775
|
+
{
|
|
1776
|
+
"dimension": "lighting_condition",
|
|
1777
|
+
"question": "夜间或逆光环境如何？安装点是否有充足照明，还是需要相机自带或外接强光抑制爆闪补光灯？",
|
|
1778
|
+
"rationale": "车牌反光与大灯直射在出入口很常见，强光抑制与补光同步触发至关重要。"
|
|
1779
|
+
},
|
|
1780
|
+
{
|
|
1781
|
+
"dimension": "gate_control",
|
|
1782
|
+
"question": "车牌识别成功后，是需要边缘主机直接通过板载继电器/IO 接口控制道闸开杆，还是仅需通过网络上报给您现有的停车计费系统？",
|
|
1783
|
+
"rationale": "决定是否需要硬件级隔离继电器控制配件，以及是否需要本地脱机白名单离线放行能力。"
|
|
1784
|
+
}
|
|
1785
|
+
]
|
|
1786
|
+
},
|
|
1787
|
+
"published": true,
|
|
1788
|
+
"visibility": "staging"
|
|
922
1789
|
},
|
|
923
1790
|
{
|
|
924
1791
|
"id": "parking-space-occupancy-detection",
|
|
@@ -931,9 +1798,38 @@
|
|
|
931
1798
|
"en": ""
|
|
932
1799
|
},
|
|
933
1800
|
"wiki_url": "",
|
|
1801
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/parking-space-occupancy-detection",
|
|
1802
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/edge_parking_occupancy",
|
|
934
1803
|
"presets": [
|
|
935
1804
|
"ip_camera_box"
|
|
936
|
-
]
|
|
1805
|
+
],
|
|
1806
|
+
"diagnostic_playbook": {
|
|
1807
|
+
"domain": "智慧交通 / 园区道闸与车牌识别",
|
|
1808
|
+
"core_dimensions": [
|
|
1809
|
+
"道闸卡口 vs 主干道抓拍",
|
|
1810
|
+
"夜间补光与逆光条件",
|
|
1811
|
+
"继电器开闸联动链路"
|
|
1812
|
+
],
|
|
1813
|
+
"questions": [
|
|
1814
|
+
{
|
|
1815
|
+
"dimension": "traffic_speed",
|
|
1816
|
+
"question": "抓拍点位是出入口道闸（低速停车抓拍，1~2 车道），还是园区/厂区主干道（车辆行驶中抓拍）？",
|
|
1817
|
+
"rationale": "道闸场景普通高帧率相机即可胜任；行驶干道需全局快门与快速连续跟踪推理算法支持。"
|
|
1818
|
+
},
|
|
1819
|
+
{
|
|
1820
|
+
"dimension": "lighting_condition",
|
|
1821
|
+
"question": "夜间或逆光环境如何？安装点是否有充足照明，还是需要相机自带或外接强光抑制爆闪补光灯？",
|
|
1822
|
+
"rationale": "车牌反光与大灯直射在出入口很常见，强光抑制与补光同步触发至关重要。"
|
|
1823
|
+
},
|
|
1824
|
+
{
|
|
1825
|
+
"dimension": "gate_control",
|
|
1826
|
+
"question": "车牌识别成功后，是需要边缘主机直接通过板载继电器/IO 接口控制道闸开杆，还是仅需通过网络上报给您现有的停车计费系统？",
|
|
1827
|
+
"rationale": "决定是否需要硬件级隔离继电器控制配件，以及是否需要本地脱机白名单离线放行能力。"
|
|
1828
|
+
}
|
|
1829
|
+
]
|
|
1830
|
+
},
|
|
1831
|
+
"published": true,
|
|
1832
|
+
"visibility": "staging"
|
|
937
1833
|
},
|
|
938
1834
|
{
|
|
939
1835
|
"id": "people_counting",
|
|
@@ -946,7 +1842,12 @@
|
|
|
946
1842
|
"en": ""
|
|
947
1843
|
},
|
|
948
1844
|
"wiki_url": "",
|
|
949
|
-
"
|
|
1845
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/people_counting",
|
|
1846
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/people_counting",
|
|
1847
|
+
"presets": [],
|
|
1848
|
+
"diagnostic_playbook": null,
|
|
1849
|
+
"published": false,
|
|
1850
|
+
"visibility": "staging"
|
|
950
1851
|
},
|
|
951
1852
|
{
|
|
952
1853
|
"id": "reachy_claw_voice_robot",
|
|
@@ -959,11 +1860,40 @@
|
|
|
959
1860
|
"en": "## What This Reference Design Is\n\n**A Reachy Mini desktop robot that listens, replies and moves with emotion.**\n\nSpeech recognition, speech synthesis and the conversation model run on a Jetson. While replying, the robot shows 14 emotions through head motion and antenna poses.\n\nWhen nobody speaks, monologue mode has it talk to itself, for trade-show demos.\n\nAfter deployment it runs offline. Voice, camera frames and the conversation do not pass through a cloud service.\n\n**Limits:** replies come from a local 4B-class model with narrower knowledge than a cloud model. It is not suited to customer commitments, medical or safety questions.\n"
|
|
960
1861
|
},
|
|
961
1862
|
"wiki_url": "",
|
|
1863
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/reachy_claw_voice_robot",
|
|
1864
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/reachy_claw_voice_robot",
|
|
962
1865
|
"presets": [
|
|
963
1866
|
"jetson",
|
|
964
1867
|
"r2000_hailo",
|
|
965
1868
|
"cm4"
|
|
966
|
-
]
|
|
1869
|
+
],
|
|
1870
|
+
"diagnostic_playbook": {
|
|
1871
|
+
"domain": "声学与音频 AI / 设备故障听诊",
|
|
1872
|
+
"core_dimensions": [
|
|
1873
|
+
"被测机械类型与异响特征",
|
|
1874
|
+
"声学麦克风 vs 振动声发射传感器",
|
|
1875
|
+
"车间环境背景噪音"
|
|
1876
|
+
],
|
|
1877
|
+
"questions": [
|
|
1878
|
+
{
|
|
1879
|
+
"dimension": "machine_defect",
|
|
1880
|
+
"question": "被监测的机械设备是什么（例如电机、轴承、齿轮箱、还是水泵压缩机）？想捕获的异常特征是什么（异响磨损、撞击声还是高压气体泄漏）？",
|
|
1881
|
+
"rationale": "决定选择声学麦克风阵列还是接触式高频振动/声发射探头。"
|
|
1882
|
+
},
|
|
1883
|
+
{
|
|
1884
|
+
"dimension": "ambient_noise",
|
|
1885
|
+
"question": "设备周边是否有其他强烈机械运转的背景杂音？",
|
|
1886
|
+
"rationale": "强背景杂音需利用端侧硬件 DSP 滤波器及降噪算法将工作主频滤除，突出异常脉冲。"
|
|
1887
|
+
},
|
|
1888
|
+
{
|
|
1889
|
+
"dimension": "alarm_latency",
|
|
1890
|
+
"question": "检测到异响异常后，希望在多长时间内告警，并通过何种方式通知维护人员？",
|
|
1891
|
+
"rationale": "确定边缘推理实时性要求以及告警输出联动链路（声光/短信/PLC 停机信号）。"
|
|
1892
|
+
}
|
|
1893
|
+
]
|
|
1894
|
+
},
|
|
1895
|
+
"published": true,
|
|
1896
|
+
"visibility": "production"
|
|
967
1897
|
},
|
|
968
1898
|
{
|
|
969
1899
|
"id": "recamera_depth_estimation",
|
|
@@ -976,9 +1906,14 @@
|
|
|
976
1906
|
"en": ""
|
|
977
1907
|
},
|
|
978
1908
|
"wiki_url": "",
|
|
1909
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/recamera_depth_estimation",
|
|
1910
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/recamera_depth_estimation",
|
|
979
1911
|
"presets": [
|
|
980
1912
|
"default"
|
|
981
|
-
]
|
|
1913
|
+
],
|
|
1914
|
+
"diagnostic_playbook": null,
|
|
1915
|
+
"published": false,
|
|
1916
|
+
"visibility": "staging"
|
|
982
1917
|
},
|
|
983
1918
|
{
|
|
984
1919
|
"id": "recamera_ecosystem",
|
|
@@ -991,10 +1926,39 @@
|
|
|
991
1926
|
"en": "## What This Reference Design Is\n\n**One AI camera; apps install and switch in the browser.**\n\nThe gallery has 9 apps, including object detection, text reading and fall detection.\n\nInference runs on the camera, and video and results stay on the local network.\n\nDetections are published over MQTT, and entities appear in Home Assistant on their own. Video goes out over RTSP to an NVR or player.\n\nYour computer downloads the apps; the camera itself needs no internet.\n\n**Limits:** one camera runs one app at a time. Detection quality depends on placement, light and distance; check it on the live preview before going live.\n"
|
|
992
1927
|
},
|
|
993
1928
|
"wiki_url": "",
|
|
1929
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/recamera_ecosystem",
|
|
1930
|
+
"repo_url": "https://github.com/suharvest/sscma-example-sg200x",
|
|
994
1931
|
"presets": [
|
|
995
1932
|
"recamera",
|
|
996
1933
|
"recamera_pro"
|
|
997
|
-
]
|
|
1934
|
+
],
|
|
1935
|
+
"diagnostic_playbook": {
|
|
1936
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
1937
|
+
"core_dimensions": [
|
|
1938
|
+
"分析目标与算法类型",
|
|
1939
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
1940
|
+
"夜间与恶劣环境"
|
|
1941
|
+
],
|
|
1942
|
+
"questions": [
|
|
1943
|
+
{
|
|
1944
|
+
"dimension": "analytics_target",
|
|
1945
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
1946
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
1947
|
+
},
|
|
1948
|
+
{
|
|
1949
|
+
"dimension": "stream_architecture",
|
|
1950
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
1951
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
1952
|
+
},
|
|
1953
|
+
{
|
|
1954
|
+
"dimension": "environment_lighting",
|
|
1955
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
1956
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
1957
|
+
}
|
|
1958
|
+
]
|
|
1959
|
+
},
|
|
1960
|
+
"published": true,
|
|
1961
|
+
"visibility": "production"
|
|
998
1962
|
},
|
|
999
1963
|
{
|
|
1000
1964
|
"id": "recamera_heatmap_grafana",
|
|
@@ -1007,13 +1971,42 @@
|
|
|
1007
1971
|
"en": "## What This Reference Design Is\n\n**A people-flow heatmap for your store.** Cameras locate shoppers, showing which shelves draw people and which aisles stay empty.\n\nDwell states and entry and exit counts are recorded too. Trends are kept by hour, day and week on a dashboard.\n\nThe heatmap can sit on your floor plan, with several cameras sharing one plan.\n\nUse a single reCamera, or keep existing IP cameras and add one AI host. Video is processed on site; the backend stores numbers only.\n\n**Limits:** cameras must be mounted high, looking down. The heatmap shows where people are, not who they are.\n"
|
|
1008
1972
|
},
|
|
1009
1973
|
"wiki_url": "",
|
|
1974
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/recamera_heatmap_grafana",
|
|
1975
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/recamera_heatmap_grafana",
|
|
1010
1976
|
"presets": [
|
|
1011
1977
|
"recamera",
|
|
1012
1978
|
"recamera_pro",
|
|
1013
1979
|
"rk",
|
|
1014
1980
|
"hailo",
|
|
1015
1981
|
"jetson"
|
|
1016
|
-
]
|
|
1982
|
+
],
|
|
1983
|
+
"diagnostic_playbook": {
|
|
1984
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
1985
|
+
"core_dimensions": [
|
|
1986
|
+
"分析目标与算法类型",
|
|
1987
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
1988
|
+
"夜间与恶劣环境"
|
|
1989
|
+
],
|
|
1990
|
+
"questions": [
|
|
1991
|
+
{
|
|
1992
|
+
"dimension": "analytics_target",
|
|
1993
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
1994
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
1995
|
+
},
|
|
1996
|
+
{
|
|
1997
|
+
"dimension": "stream_architecture",
|
|
1998
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
1999
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
2000
|
+
},
|
|
2001
|
+
{
|
|
2002
|
+
"dimension": "environment_lighting",
|
|
2003
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
2004
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
2005
|
+
}
|
|
2006
|
+
]
|
|
2007
|
+
},
|
|
2008
|
+
"published": true,
|
|
2009
|
+
"visibility": "production"
|
|
1017
2010
|
},
|
|
1018
2011
|
{
|
|
1019
2012
|
"id": "recamera_onvif_nvr",
|
|
@@ -1026,9 +2019,14 @@
|
|
|
1026
2019
|
"en": ""
|
|
1027
2020
|
},
|
|
1028
2021
|
"wiki_url": "",
|
|
2022
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/recamera_onvif_nvr",
|
|
2023
|
+
"repo_url": "https://github.com/yyling0101-a11y/reCamera_2002w_sdk",
|
|
1029
2024
|
"presets": [
|
|
1030
2025
|
"recamera_2002"
|
|
1031
|
-
]
|
|
2026
|
+
],
|
|
2027
|
+
"diagnostic_playbook": null,
|
|
2028
|
+
"published": false,
|
|
2029
|
+
"visibility": "staging"
|
|
1032
2030
|
},
|
|
1033
2031
|
{
|
|
1034
2032
|
"id": "recamera_parking_monitor",
|
|
@@ -1041,9 +2039,14 @@
|
|
|
1041
2039
|
"en": "## What This Reference Design Is\n\n**One reCamera watching a row of parking spots.** It shows live which spots are free and which are taken.\n\nNo sensor per spot is needed. Free spots show green, taken spots red, with a free-spot count.\n\nA spot changes state only after 15 frames agree, so passers-by and shadows do not trigger it.\n\nDetection and the dashboard run on the camera, with no server. Any phone or laptop on the same network opens it in a browser.\n\n**Limits:** designed for three adjacent spots per camera in a front view. Works best in good light.\n"
|
|
1042
2040
|
},
|
|
1043
2041
|
"wiki_url": "",
|
|
2042
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/recamera_parking_monitor",
|
|
2043
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/recamera_parking_monitor",
|
|
1044
2044
|
"presets": [
|
|
1045
2045
|
"default"
|
|
1046
|
-
]
|
|
2046
|
+
],
|
|
2047
|
+
"diagnostic_playbook": null,
|
|
2048
|
+
"published": true,
|
|
2049
|
+
"visibility": "production"
|
|
1047
2050
|
},
|
|
1048
2051
|
{
|
|
1049
2052
|
"id": "recamera_sheep_counter_lora",
|
|
@@ -1056,9 +2059,14 @@
|
|
|
1056
2059
|
"en": "## What This Reference Design Is\n\n**Automatic sheep counting at the paddock gate.** A reCamera counts sheep going in and out. It keeps IN, OUT and INSIDE totals.\n\nCounts travel over LoRa radio, so the gate needs no WiFi or mobile signal.\n\nA gateway at the farmhouse feeds a Home Assistant dashboard with 24-hour history. The phone app can notify on each crossing.\n\nAfter a radio gap, a heartbeat every 15 minutes brings the totals back in sync.\n\n**Limits:** sheep must cross the count line in view; a tight bunch can be undercounted. Radio distance varies with terrain.\n"
|
|
1057
2060
|
},
|
|
1058
2061
|
"wiki_url": "",
|
|
2062
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/recamera_sheep_counter_lora",
|
|
2063
|
+
"repo_url": "https://github.com/biancayoung/recamera-sheep-counter-lora",
|
|
1059
2064
|
"presets": [
|
|
1060
2065
|
"lora_gateway"
|
|
1061
|
-
]
|
|
2066
|
+
],
|
|
2067
|
+
"diagnostic_playbook": null,
|
|
2068
|
+
"published": true,
|
|
2069
|
+
"visibility": "production"
|
|
1062
2070
|
},
|
|
1063
2071
|
{
|
|
1064
2072
|
"id": "respeaker_flex_soarm",
|
|
@@ -1071,9 +2079,14 @@
|
|
|
1071
2079
|
"en": "Talk to a SO-ARM101 robotic arm. Say the wake word and a command; the arm replies through a speaker and performs the matching gesture. Speech, the language model and arm control all run on one reComputer J40 (Orin NX 16GB), with no cloud API."
|
|
1072
2080
|
},
|
|
1073
2081
|
"wiki_url": "",
|
|
2082
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/respeaker_flex_soarm",
|
|
2083
|
+
"repo_url": "https://github.com/Seeed-Projects/Seeed_RoboController",
|
|
1074
2084
|
"presets": [
|
|
1075
2085
|
"default"
|
|
1076
|
-
]
|
|
2086
|
+
],
|
|
2087
|
+
"diagnostic_playbook": null,
|
|
2088
|
+
"published": true,
|
|
2089
|
+
"visibility": "production"
|
|
1077
2090
|
},
|
|
1078
2091
|
{
|
|
1079
2092
|
"id": "retail_voice",
|
|
@@ -1086,10 +2099,39 @@
|
|
|
1086
2099
|
"en": "Store, meeting, consultation speech becomes back-office text. Mic array and on-site transcriber, or reSpeaker Clip and phone. Names, numbers masked before storage, deletable on request."
|
|
1087
2100
|
},
|
|
1088
2101
|
"wiki_url": "",
|
|
2102
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/retail_voice",
|
|
2103
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/retail_voice",
|
|
1089
2104
|
"presets": [
|
|
1090
2105
|
"local_transcribe",
|
|
1091
2106
|
"cloud_stack"
|
|
1092
|
-
]
|
|
2107
|
+
],
|
|
2108
|
+
"diagnostic_playbook": {
|
|
2109
|
+
"domain": "现场语音控制 / 离线语音助手",
|
|
2110
|
+
"core_dimensions": [
|
|
2111
|
+
"声学噪声与麦克风拾音距离",
|
|
2112
|
+
"100% 离线隐私 vs 云端大模型",
|
|
2113
|
+
"受控设备联动协议"
|
|
2114
|
+
],
|
|
2115
|
+
"questions": [
|
|
2116
|
+
{
|
|
2117
|
+
"dimension": "acoustic_environment",
|
|
2118
|
+
"question": "现场使用环境的噪音如何？通常是在安静的室内/会议室，还是存在环境背景噪音（如风扇、空调、人群嘈杂）？拾音距离多远？",
|
|
2119
|
+
"rationale": "决定麦克风阵列选型：近场安静可用双麦；远场（3~5米）与嘈杂环境必须使用带硬件 DSP、回声消除 AEC 与波束成形的 ReSpeaker XVF3800 多麦阵列。"
|
|
2120
|
+
},
|
|
2121
|
+
{
|
|
2122
|
+
"dimension": "privacy_connectivity",
|
|
2123
|
+
"question": "系统对网络和隐私有什么硬性要求？是必须 100% 纯本地离线断网运行，还是可以联网访问云端大模型？",
|
|
2124
|
+
"rationale": "纯离线需配置 Orin NX 等中高算力主机在端侧跑端到端小模型（Whisper + LLM + TTS）；联网混合模式可用轻量主机做前端拾音上云。"
|
|
2125
|
+
},
|
|
2126
|
+
{
|
|
2127
|
+
"dimension": "target_control",
|
|
2128
|
+
"question": "语音识别或大模型理解后，主要用来控制什么设备或执行什么业务？",
|
|
2129
|
+
"rationale": "明确南向控制接口：是对接 Home Assistant 智能家居、发送 MQTT 报文、还是通过串口/Modbus 控制工业继电器。"
|
|
2130
|
+
}
|
|
2131
|
+
]
|
|
2132
|
+
},
|
|
2133
|
+
"published": true,
|
|
2134
|
+
"visibility": "production"
|
|
1093
2135
|
},
|
|
1094
2136
|
{
|
|
1095
2137
|
"id": "sensecraft_data_mcp",
|
|
@@ -1102,9 +2144,14 @@
|
|
|
1102
2144
|
"en": "## What This Reference Design Is\n\n**Ask out loud and hear how your SenseCAP devices are doing.** No app and no dashboard.\n\nAsk for an overview and hear who is offline or low on battery first. Name a device and hear its current readings.\n\nAn always-on Docker host runs the bridge, reads from the platform and dials out to a XiaoZhi voice assistant. Any MCP-capable AI also works.\n\nThe bridge opens no port, and credentials are entered only at deployment.\n\n**Limits:** devices must already report to the SenseCAP platform, and the host needs internet access.\n"
|
|
1103
2145
|
},
|
|
1104
2146
|
"wiki_url": "",
|
|
2147
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/sensecraft_data_mcp",
|
|
2148
|
+
"repo_url": "https://github.com/Love4yzp/sensecraft-data-mcp",
|
|
1105
2149
|
"presets": [
|
|
1106
2150
|
"default"
|
|
1107
|
-
]
|
|
2151
|
+
],
|
|
2152
|
+
"diagnostic_playbook": null,
|
|
2153
|
+
"published": true,
|
|
2154
|
+
"visibility": "production"
|
|
1108
2155
|
},
|
|
1109
2156
|
{
|
|
1110
2157
|
"id": "smart-badge-voice-transcription",
|
|
@@ -1117,9 +2164,14 @@
|
|
|
1117
2164
|
"en": ""
|
|
1118
2165
|
},
|
|
1119
2166
|
"wiki_url": "",
|
|
2167
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/smart-badge-voice-transcription",
|
|
2168
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/clip_private_transcription",
|
|
1120
2169
|
"presets": [
|
|
1121
2170
|
"clip_edge_box"
|
|
1122
|
-
]
|
|
2171
|
+
],
|
|
2172
|
+
"diagnostic_playbook": null,
|
|
2173
|
+
"published": true,
|
|
2174
|
+
"visibility": "staging"
|
|
1123
2175
|
},
|
|
1124
2176
|
{
|
|
1125
2177
|
"id": "smart_hvac_control",
|
|
@@ -1132,9 +2184,38 @@
|
|
|
1132
2184
|
"en": "Bring HVAC controller points and an energy meter into one point model, predict setpoints from the building's own history, and write them back only after a readback from the field matches — with rollback and alarms when it does not."
|
|
1133
2185
|
},
|
|
1134
2186
|
"wiki_url": "https://wiki.seeedstudio.com/solutions/hvac-setpoint-control/",
|
|
2187
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/smart_hvac_control",
|
|
2188
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/smart_hvac_control",
|
|
1135
2189
|
"presets": [
|
|
1136
2190
|
"default"
|
|
1137
|
-
]
|
|
2191
|
+
],
|
|
2192
|
+
"diagnostic_playbook": {
|
|
2193
|
+
"domain": "旧建筑节能改造 / 暖通与智能抄表",
|
|
2194
|
+
"core_dimensions": [
|
|
2195
|
+
"存量表计通信接口",
|
|
2196
|
+
"配电间集中 vs 跨楼层分布",
|
|
2197
|
+
"纯能耗采集 vs 闭环控制"
|
|
2198
|
+
],
|
|
2199
|
+
"questions": [
|
|
2200
|
+
{
|
|
2201
|
+
"dimension": "meter_interface",
|
|
2202
|
+
"question": "现场的电表、水表或空调机组目前是什么型号？是否自带 RS485（Modbus RTU / DL/T 645）通信接口，还是老旧机械表？",
|
|
2203
|
+
"rationale": "带 485 接口可直接低成本手拉手总线抄表；无通信接口的老旧机械表需更换智能表或加装开口式开口互感器 CT。"
|
|
2204
|
+
},
|
|
2205
|
+
{
|
|
2206
|
+
"dimension": "cable_distribution",
|
|
2207
|
+
"question": "表计是集中在配电室/机房，还是分散在各楼层的强电井中？各楼层之间是否有现成弱电网线贯通？",
|
|
2208
|
+
"rationale": "集中点位直接用有线网关接总线；跨楼层分散无布线推荐 SenseCAP LoRaWAN 采集器无线回传，大幅削减施工穿墙打洞成本。"
|
|
2209
|
+
},
|
|
2210
|
+
{
|
|
2211
|
+
"dimension": "control_requirement",
|
|
2212
|
+
"question": "需求是仅做“能耗监测与数据统计”，还是需要做“闭环节能控制”（如根据峰谷电价或人员在场调节空调回路）？",
|
|
2213
|
+
"rationale": "决定是否需要配置带工业继电器与模拟量输出的控制型网关。"
|
|
2214
|
+
}
|
|
2215
|
+
]
|
|
2216
|
+
},
|
|
2217
|
+
"published": true,
|
|
2218
|
+
"visibility": "production"
|
|
1138
2219
|
},
|
|
1139
2220
|
{
|
|
1140
2221
|
"id": "smart_space_assistant",
|
|
@@ -1147,11 +2228,40 @@
|
|
|
1147
2228
|
"en": "## What This Reference Design Is\n\n**A Xiaozhi voice assistant that recognises people and shows the conversation on a large screen.**\n\nThe terminal's camera recognises registered people and greets them by name. Recognition runs inside the terminal, and the face list of up to 20 people stays on the device.\n\nA display service on a host in the local network shows the conversation live on an HDMI TV or monitor.\n\nFace recognition and display casting install separately and do not affect each other.\n\n**Limits:** it works best in normal indoor light with a frontal face. No field accuracy test is part of this design, so it is not suited to access control or attendance.\n"
|
|
1148
2229
|
},
|
|
1149
2230
|
"wiki_url": "",
|
|
2231
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/smart_space_assistant",
|
|
2232
|
+
"repo_url": "https://github.com/78/xiaozhi-esp32",
|
|
1150
2233
|
"presets": [
|
|
1151
2234
|
"reterminal_d1001",
|
|
1152
2235
|
"display_cast",
|
|
1153
2236
|
"face_recognition"
|
|
1154
|
-
]
|
|
2237
|
+
],
|
|
2238
|
+
"diagnostic_playbook": {
|
|
2239
|
+
"domain": "旧建筑节能改造 / 暖通与智能抄表",
|
|
2240
|
+
"core_dimensions": [
|
|
2241
|
+
"存量表计通信接口",
|
|
2242
|
+
"配电间集中 vs 跨楼层分布",
|
|
2243
|
+
"纯能耗采集 vs 闭环控制"
|
|
2244
|
+
],
|
|
2245
|
+
"questions": [
|
|
2246
|
+
{
|
|
2247
|
+
"dimension": "meter_interface",
|
|
2248
|
+
"question": "现场的电表、水表或空调机组目前是什么型号？是否自带 RS485（Modbus RTU / DL/T 645）通信接口，还是老旧机械表？",
|
|
2249
|
+
"rationale": "带 485 接口可直接低成本手拉手总线抄表；无通信接口的老旧机械表需更换智能表或加装开口式开口互感器 CT。"
|
|
2250
|
+
},
|
|
2251
|
+
{
|
|
2252
|
+
"dimension": "cable_distribution",
|
|
2253
|
+
"question": "表计是集中在配电室/机房，还是分散在各楼层的强电井中？各楼层之间是否有现成弱电网线贯通？",
|
|
2254
|
+
"rationale": "集中点位直接用有线网关接总线；跨楼层分散无布线推荐 SenseCAP LoRaWAN 采集器无线回传，大幅削减施工穿墙打洞成本。"
|
|
2255
|
+
},
|
|
2256
|
+
{
|
|
2257
|
+
"dimension": "control_requirement",
|
|
2258
|
+
"question": "需求是仅做“能耗监测与数据统计”，还是需要做“闭环节能控制”（如根据峰谷电价或人员在场调节空调回路）？",
|
|
2259
|
+
"rationale": "决定是否需要配置带工业继电器与模拟量输出的控制型网关。"
|
|
2260
|
+
}
|
|
2261
|
+
]
|
|
2262
|
+
},
|
|
2263
|
+
"published": true,
|
|
2264
|
+
"visibility": "production"
|
|
1155
2265
|
},
|
|
1156
2266
|
{
|
|
1157
2267
|
"id": "smart_warehouse",
|
|
@@ -1164,13 +2274,42 @@
|
|
|
1164
2274
|
"en": "Voice-controlled warehouse management on edge hardware — speak the transaction, MCP writes it to inventory. Five tiers, from cloud trial to a fully offline Jetson deployment."
|
|
1165
2275
|
},
|
|
1166
2276
|
"wiki_url": "",
|
|
2277
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/smart_warehouse",
|
|
2278
|
+
"repo_url": "https://github.com/suharvest/warehouse_system",
|
|
1167
2279
|
"presets": [
|
|
1168
2280
|
"trial",
|
|
1169
2281
|
"sensecraft_cloud",
|
|
1170
2282
|
"private_cloud",
|
|
1171
2283
|
"private_cloud_multi",
|
|
1172
2284
|
"edge_computing"
|
|
1173
|
-
]
|
|
2285
|
+
],
|
|
2286
|
+
"diagnostic_playbook": {
|
|
2287
|
+
"domain": "智慧仓库管理 / 货位状态与托盘盘点",
|
|
2288
|
+
"core_dimensions": [
|
|
2289
|
+
"货架结构与无线遮挡",
|
|
2290
|
+
"货位占空感知 vs 条码盘点",
|
|
2291
|
+
"库区网络覆盖"
|
|
2292
|
+
],
|
|
2293
|
+
"questions": [
|
|
2294
|
+
{
|
|
2295
|
+
"dimension": "rack_structure",
|
|
2296
|
+
"question": "仓库的货物存储形式是托盘平库、高位重型货架还是自动化立体仓？货架高度大概多高？",
|
|
2297
|
+
"rationale": "高位货架钢结构遮挡严重，需针对性设计相机俯视视角或工业无线天线布设。"
|
|
2298
|
+
},
|
|
2299
|
+
{
|
|
2300
|
+
"dimension": "perception_mode",
|
|
2301
|
+
"question": "核心诉求是“货位占用与空闲状态检测”（有货/无货），还是“具体托盘/货物条码精准盘点”？",
|
|
2302
|
+
"rationale": "货位空闲检测推荐边缘视觉一体机俯视感知；托盘精准身份盘点需结合 RFID 或蓝牙 Asset Tag。"
|
|
2303
|
+
},
|
|
2304
|
+
{
|
|
2305
|
+
"dimension": "network_coverage",
|
|
2306
|
+
"question": "库区内是否具备完整的有线网络或 Wi-Fi 覆盖？",
|
|
2307
|
+
"rationale": "无网络覆盖时需要配置长距离 LoRaWAN 或 4G 无线网关回传数据。"
|
|
2308
|
+
}
|
|
2309
|
+
]
|
|
2310
|
+
},
|
|
2311
|
+
"published": true,
|
|
2312
|
+
"visibility": "production"
|
|
1174
2313
|
},
|
|
1175
2314
|
{
|
|
1176
2315
|
"id": "unmanned_store_access",
|
|
@@ -1182,12 +2321,41 @@
|
|
|
1182
2321
|
"zh": "刷脸开门，防照片和屏幕翻拍，断网照常开门。人脸库云端统一管理，每次开门都有记录。",
|
|
1183
2322
|
"en": "## What This Reference Design Is\n\n**Face access control for a door nobody stands behind.**\n\nThe camera recognises a face and checks it is a real person, not a photo. It then checks the roster and the time window before opening.\n\nEvery entry and refusal is recorded and cannot be altered.\n\nThe face list is edited in the cloud and fetched by the device. A failed fetch keeps the old list, so the door still opens offline.\n\nRecognition and liveness accuracy follow the face model you deploy, so measure them on your own site.\n\n**Limits:** the person faces the camera within its working distance, and a mask or strong backlight leads to a refusal. This is a base to build on, not a certified security product.\n"
|
|
1184
2323
|
},
|
|
1185
|
-
"wiki_url": "https://wiki.seeedstudio.com/solutions/unmanned-store-face-access/",
|
|
1186
|
-
"
|
|
1187
|
-
|
|
1188
|
-
|
|
1189
|
-
"
|
|
1190
|
-
|
|
2324
|
+
"wiki_url": "https://wiki.seeedstudio.com/solutions/unmanned-store-face-access/",
|
|
2325
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/unmanned_store_access",
|
|
2326
|
+
"repo_url": "https://github.com/suharvest/sensecraft-solutions/tree/main/solutions/unmanned_store_access",
|
|
2327
|
+
"presets": [
|
|
2328
|
+
"a_ai_camera",
|
|
2329
|
+
"a_recamera_std",
|
|
2330
|
+
"b_ai_host"
|
|
2331
|
+
],
|
|
2332
|
+
"diagnostic_playbook": {
|
|
2333
|
+
"domain": "智慧零售门店 / 客流统计与货架动线",
|
|
2334
|
+
"core_dimensions": [
|
|
2335
|
+
"进出店客流计数 vs 店内热力动线",
|
|
2336
|
+
"门头吊顶施工布线",
|
|
2337
|
+
"多门店数据汇聚方式"
|
|
2338
|
+
],
|
|
2339
|
+
"questions": [
|
|
2340
|
+
{
|
|
2341
|
+
"dimension": "analytics_scope",
|
|
2342
|
+
"question": "统计的主要诉求是“出入口进店人数/客流双向计数”，还是“店内各货架区域的顾客停留时长与热力分布”？",
|
|
2343
|
+
"rationale": "出入口仅需门头单台垂直俯视 AI 相机；货架热力需广角全景相机或多机拼接。"
|
|
2344
|
+
},
|
|
2345
|
+
{
|
|
2346
|
+
"dimension": "ceiling_cabling",
|
|
2347
|
+
"question": "现场安装点位（通常在门头吊顶或天花板）是否预留了网线和供电？",
|
|
2348
|
+
"rationale": "支持 PoE 供电只需一根网线即可完成供电与通信，最利于商铺免破坏装修快速施工。"
|
|
2349
|
+
},
|
|
2350
|
+
{
|
|
2351
|
+
"dimension": "data_aggregation",
|
|
2352
|
+
"question": "连锁门店的数据汇总方式是怎样的？是单店本地显示，还是需要将多店客流数据自动上传到您的总部云端或 ERP 系统？",
|
|
2353
|
+
"rationale": "确认网络上报协议（MQTT/HTTP REST）及离线断网本地缓存需求。"
|
|
2354
|
+
}
|
|
2355
|
+
]
|
|
2356
|
+
},
|
|
2357
|
+
"published": true,
|
|
2358
|
+
"visibility": "production"
|
|
1191
2359
|
},
|
|
1192
2360
|
{
|
|
1193
2361
|
"id": "voice_rebot_arm",
|
|
@@ -1200,9 +2368,14 @@
|
|
|
1200
2368
|
"en": "Say \"Hey Jarvis, grab the water bottle\" and a reBot B601-DM arm finds the object with its wrist depth camera, picks it up and brings it back in about 11 seconds. Speech, the language model, detection and grasp planning all run on one reComputer J40 (Orin NX 16GB), with no cloud API."
|
|
1201
2369
|
},
|
|
1202
2370
|
"wiki_url": "",
|
|
2371
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/voice_rebot_arm",
|
|
2372
|
+
"repo_url": "https://github.com/suharvest/openvoicestream",
|
|
1203
2373
|
"presets": [
|
|
1204
2374
|
"default"
|
|
1205
|
-
]
|
|
2375
|
+
],
|
|
2376
|
+
"diagnostic_playbook": null,
|
|
2377
|
+
"published": true,
|
|
2378
|
+
"visibility": "production"
|
|
1206
2379
|
},
|
|
1207
2380
|
{
|
|
1208
2381
|
"id": "voice_robot_lekiwi",
|
|
@@ -1215,9 +2388,14 @@
|
|
|
1215
2388
|
"en": "Drive a three-wheeled LeKiwi robot by voice. Say \"Hey Jarvis\" and a command in English; the robot replies and moves forward, back, sideways or turns. Speech recognition, the language model and the voice reply run on Groq's cloud API, so the robot needs internet."
|
|
1216
2389
|
},
|
|
1217
2390
|
"wiki_url": "",
|
|
2391
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/voice_robot_lekiwi",
|
|
2392
|
+
"repo_url": "https://github.com/KasunThushara/Lekiwi-voice",
|
|
1218
2393
|
"presets": [
|
|
1219
2394
|
"default"
|
|
1220
|
-
]
|
|
2395
|
+
],
|
|
2396
|
+
"diagnostic_playbook": null,
|
|
2397
|
+
"published": true,
|
|
2398
|
+
"visibility": "production"
|
|
1221
2399
|
},
|
|
1222
2400
|
{
|
|
1223
2401
|
"id": "z_image_turbo",
|
|
@@ -1230,9 +2408,14 @@
|
|
|
1230
2408
|
"en": "## What This Reference Design Is\n\n**Image generation on one Jetson.**\n\nSend a description and get a PNG, or add a prompt to a reference image to edit it.\n\nOn Orin NX 16GB, a 512px image takes about 100 s. One request runs at a time; the rest queue.\n\nApps call the HTTP API over the LAN. Prompts and images stay on the device, fully offline after deployment.\n\n**Limits:** generation is not real time. The first deploy downloads about 20GB of weights and about 12GB of inference engine.\n"
|
|
1231
2409
|
},
|
|
1232
2410
|
"wiki_url": "",
|
|
2411
|
+
"landing_url": "https://www.seeedstudio.com/solutions/reference-designs/z_image_turbo",
|
|
2412
|
+
"repo_url": "https://github.com/suharvest/z-image-turbo-tensorrt-jetson",
|
|
1233
2413
|
"presets": [
|
|
1234
2414
|
"jetson_image_gen"
|
|
1235
|
-
]
|
|
2415
|
+
],
|
|
2416
|
+
"diagnostic_playbook": null,
|
|
2417
|
+
"published": true,
|
|
2418
|
+
"visibility": "production"
|
|
1236
2419
|
}
|
|
1237
2420
|
],
|
|
1238
2421
|
"product_families": {
|
|
@@ -7966,5 +9149,682 @@
|
|
|
7966
9149
|
},
|
|
7967
9150
|
"audio_interface": "USB Audio Class 1.0 / 2.0, 4-mic linear array"
|
|
7968
9151
|
}
|
|
9152
|
+
},
|
|
9153
|
+
"diagnostic_playbooks": {
|
|
9154
|
+
"elderly-care-monitoring": {
|
|
9155
|
+
"domain": "智慧养老 / 室内监护",
|
|
9156
|
+
"core_dimensions": [
|
|
9157
|
+
"集中 vs 分散空间分布",
|
|
9158
|
+
"存量摄像头利旧",
|
|
9159
|
+
"隐私保护与传感器形态"
|
|
9160
|
+
],
|
|
9161
|
+
"questions": [
|
|
9162
|
+
{
|
|
9163
|
+
"dimension": "topology",
|
|
9164
|
+
"question": "老人房间和公共区域是在同一层/同一楼栋比较集中，还是分散在多栋楼或较远区域？",
|
|
9165
|
+
"rationale": "集中分布可用 1 台 reComputer 主机拉多路 RTSP 流摊薄成本；分散点位推荐每间房独立 reCamera 一体机免拉长线。"
|
|
9166
|
+
},
|
|
9167
|
+
{
|
|
9168
|
+
"dimension": "asset_reuse",
|
|
9169
|
+
"question": "现场是否已经安装了支持 RTSP/ONVIF 协议的监控摄像头（如海康、大华等）？",
|
|
9170
|
+
"rationale": "已有摄像头可直接复用利旧，只需采购边缘算力盒，省去镜头重购成本；无摄像头则推荐成套硬件。"
|
|
9171
|
+
},
|
|
9172
|
+
{
|
|
9173
|
+
"dimension": "privacy_boundary",
|
|
9174
|
+
"question": "卫生间、卧室等高隐私区域是否对纯光学摄像头有顾虑，是否需要无视觉隐私的毫米波雷达方案？",
|
|
9175
|
+
"rationale": "私密区域用 60GHz 毫米波雷达替代光学镜头，既可精确检测跌倒卧床，又彻底消除侵犯隐私争议。"
|
|
9176
|
+
}
|
|
9177
|
+
]
|
|
9178
|
+
},
|
|
9179
|
+
"environment-monitoring": {
|
|
9180
|
+
"domain": "智慧农业 / 环境监测与微气象",
|
|
9181
|
+
"core_dimensions": [
|
|
9182
|
+
"集中大棚 vs 广域农田",
|
|
9183
|
+
"市电 vs 太阳能/电池供电",
|
|
9184
|
+
"监测指标与探头深度"
|
|
9185
|
+
],
|
|
9186
|
+
"questions": [
|
|
9187
|
+
{
|
|
9188
|
+
"dimension": "topology",
|
|
9189
|
+
"question": "监测区域是集中式连栋温室大棚（百米级），还是大面积户外大田/果园（数公里级）？",
|
|
9190
|
+
"rationale": "大棚内百米级可采用 RS485 有线总线集中组网；广域大田推荐 LoRaWAN 远距离低功耗无线传输，配合 SenseCAP M2 网关。"
|
|
9191
|
+
},
|
|
9192
|
+
{
|
|
9193
|
+
"dimension": "power",
|
|
9194
|
+
"question": "现场测点是否有 220V 市电供电，还是需要野外太阳能板/锂电池长续航供电？",
|
|
9195
|
+
"rationale": "市电可支持持续高频数据上报；无市电需要选用带内置超大锂电池、支持休眠唤醒的低功耗无线传感器（如 S2100/S210x）。"
|
|
9196
|
+
},
|
|
9197
|
+
{
|
|
9198
|
+
"dimension": "sensing_depth",
|
|
9199
|
+
"question": "需要监测哪些核心环境指标？仅是空气温湿度/光照/CO2，还是包括土壤剖面墒情（深层水分/EC/pH）或气象风速风向？",
|
|
9200
|
+
"rationale": "决定是配置一体化多合一微气象站（如 S700/S2120），还是选配工业级土壤三参数/水肥专用探针与变送器。"
|
|
9201
|
+
}
|
|
9202
|
+
]
|
|
9203
|
+
},
|
|
9204
|
+
"industrial-visual-inspection": {
|
|
9205
|
+
"domain": "工业视觉质检 / 表面缺陷与装配复检",
|
|
9206
|
+
"core_dimensions": [
|
|
9207
|
+
"产线生产节拍与相机快门",
|
|
9208
|
+
"工件材质反光与照明",
|
|
9209
|
+
"剔除执行与 PLC 信号闭环"
|
|
9210
|
+
],
|
|
9211
|
+
"questions": [
|
|
9212
|
+
{
|
|
9213
|
+
"dimension": "line_speed",
|
|
9214
|
+
"question": "现场流水线的生产节拍是怎样的（每分钟过检多少件产品，工件是静止拍照还是运动中飞拍）？",
|
|
9215
|
+
"rationale": "决定相机曝光类型（运动飞拍必须全局快门 Global Shutter），以及端侧推理帧率与 Jetson 算力等级（Orin Nano vs Orin NX）。"
|
|
9216
|
+
},
|
|
9217
|
+
{
|
|
9218
|
+
"dimension": "materials_lighting",
|
|
9219
|
+
"question": "被测工件表面是什么材质（反光金属、高光塑料还是普通漫反射包装）？缺陷尺寸大概在什么毫米级别？",
|
|
9220
|
+
"rationale": "反光表面需定制特殊工业光源（如偏光环形光、同轴光）消除眩光；缺陷精度决定工业相机分辨率与镜头焦距。"
|
|
9221
|
+
},
|
|
9222
|
+
{
|
|
9223
|
+
"dimension": "plc_integration",
|
|
9224
|
+
"question": "检测出不良品后，边缘设备是否需要直接向现场 PLC 或气缸发送剔除信号？",
|
|
9225
|
+
"rationale": "决定是否需要选择带工业隔离数字量 I/O 的工控机型（如 reComputer Industrial 系列），并配置现场总线。"
|
|
9226
|
+
}
|
|
9227
|
+
]
|
|
9228
|
+
},
|
|
9229
|
+
"parking-traffic-vision": {
|
|
9230
|
+
"domain": "智慧交通 / 园区道闸与车牌识别",
|
|
9231
|
+
"core_dimensions": [
|
|
9232
|
+
"道闸卡口 vs 主干道抓拍",
|
|
9233
|
+
"夜间补光与逆光条件",
|
|
9234
|
+
"继电器开闸联动链路"
|
|
9235
|
+
],
|
|
9236
|
+
"questions": [
|
|
9237
|
+
{
|
|
9238
|
+
"dimension": "traffic_speed",
|
|
9239
|
+
"question": "抓拍点位是出入口道闸（低速停车抓拍，1~2 车道），还是园区/厂区主干道（车辆行驶中抓拍）？",
|
|
9240
|
+
"rationale": "道闸场景普通高帧率相机即可胜任；行驶干道需全局快门与快速连续跟踪推理算法支持。"
|
|
9241
|
+
},
|
|
9242
|
+
{
|
|
9243
|
+
"dimension": "lighting_condition",
|
|
9244
|
+
"question": "夜间或逆光环境如何？安装点是否有充足照明，还是需要相机自带或外接强光抑制爆闪补光灯？",
|
|
9245
|
+
"rationale": "车牌反光与大灯直射在出入口很常见，强光抑制与补光同步触发至关重要。"
|
|
9246
|
+
},
|
|
9247
|
+
{
|
|
9248
|
+
"dimension": "gate_control",
|
|
9249
|
+
"question": "车牌识别成功后，是需要边缘主机直接通过板载继电器/IO 接口控制道闸开杆，还是仅需通过网络上报给您现有的停车计费系统？",
|
|
9250
|
+
"rationale": "决定是否需要硬件级隔离继电器控制配件，以及是否需要本地脱机白名单离线放行能力。"
|
|
9251
|
+
}
|
|
9252
|
+
]
|
|
9253
|
+
},
|
|
9254
|
+
"conversational-voice-ai": {
|
|
9255
|
+
"domain": "现场语音控制 / 离线语音助手",
|
|
9256
|
+
"core_dimensions": [
|
|
9257
|
+
"声学噪声与麦克风拾音距离",
|
|
9258
|
+
"100% 离线隐私 vs 云端大模型",
|
|
9259
|
+
"受控设备联动协议"
|
|
9260
|
+
],
|
|
9261
|
+
"questions": [
|
|
9262
|
+
{
|
|
9263
|
+
"dimension": "acoustic_environment",
|
|
9264
|
+
"question": "现场使用环境的噪音如何？通常是在安静的室内/会议室，还是存在环境背景噪音（如风扇、空调、人群嘈杂）？拾音距离多远？",
|
|
9265
|
+
"rationale": "决定麦克风阵列选型：近场安静可用双麦；远场（3~5米）与嘈杂环境必须使用带硬件 DSP、回声消除 AEC 与波束成形的 ReSpeaker XVF3800 多麦阵列。"
|
|
9266
|
+
},
|
|
9267
|
+
{
|
|
9268
|
+
"dimension": "privacy_connectivity",
|
|
9269
|
+
"question": "系统对网络和隐私有什么硬性要求？是必须 100% 纯本地离线断网运行，还是可以联网访问云端大模型？",
|
|
9270
|
+
"rationale": "纯离线需配置 Orin NX 等中高算力主机在端侧跑端到端小模型（Whisper + LLM + TTS）；联网混合模式可用轻量主机做前端拾音上云。"
|
|
9271
|
+
},
|
|
9272
|
+
{
|
|
9273
|
+
"dimension": "target_control",
|
|
9274
|
+
"question": "语音识别或大模型理解后，主要用来控制什么设备或执行什么业务？",
|
|
9275
|
+
"rationale": "明确南向控制接口：是对接 Home Assistant 智能家居、发送 MQTT 报文、还是通过串口/Modbus 控制工业继电器。"
|
|
9276
|
+
}
|
|
9277
|
+
]
|
|
9278
|
+
},
|
|
9279
|
+
"building-energy-retrofit": {
|
|
9280
|
+
"domain": "旧建筑节能改造 / 暖通与智能抄表",
|
|
9281
|
+
"core_dimensions": [
|
|
9282
|
+
"存量表计通信接口",
|
|
9283
|
+
"配电间集中 vs 跨楼层分布",
|
|
9284
|
+
"纯能耗采集 vs 闭环控制"
|
|
9285
|
+
],
|
|
9286
|
+
"questions": [
|
|
9287
|
+
{
|
|
9288
|
+
"dimension": "meter_interface",
|
|
9289
|
+
"question": "现场的电表、水表或空调机组目前是什么型号？是否自带 RS485（Modbus RTU / DL/T 645）通信接口，还是老旧机械表？",
|
|
9290
|
+
"rationale": "带 485 接口可直接低成本手拉手总线抄表；无通信接口的老旧机械表需更换智能表或加装开口式开口互感器 CT。"
|
|
9291
|
+
},
|
|
9292
|
+
{
|
|
9293
|
+
"dimension": "cable_distribution",
|
|
9294
|
+
"question": "表计是集中在配电室/机房，还是分散在各楼层的强电井中？各楼层之间是否有现成弱电网线贯通？",
|
|
9295
|
+
"rationale": "集中点位直接用有线网关接总线；跨楼层分散无布线推荐 SenseCAP LoRaWAN 采集器无线回传，大幅削减施工穿墙打洞成本。"
|
|
9296
|
+
},
|
|
9297
|
+
{
|
|
9298
|
+
"dimension": "control_requirement",
|
|
9299
|
+
"question": "需求是仅做“能耗监测与数据统计”，还是需要做“闭环节能控制”（如根据峰谷电价或人员在场调节空调回路）？",
|
|
9300
|
+
"rationale": "决定是否需要配置带工业继电器与模拟量输出的控制型网关。"
|
|
9301
|
+
}
|
|
9302
|
+
]
|
|
9303
|
+
},
|
|
9304
|
+
"indoor-outdoor-positioning": {
|
|
9305
|
+
"domain": "室内外定位 / 资产与人员追踪",
|
|
9306
|
+
"core_dimensions": [
|
|
9307
|
+
"纯室内 vs 室内外混合",
|
|
9308
|
+
"定位精度期望（米级 vs 区域级）",
|
|
9309
|
+
"佩戴形式与免维护续航"
|
|
9310
|
+
],
|
|
9311
|
+
"questions": [
|
|
9312
|
+
{
|
|
9313
|
+
"dimension": "spatial_scope",
|
|
9314
|
+
"question": "定位场景是纯室内（厂房/展厅/仓库），还是室内外混合（比如仓库到室外堆场，甚至货物长途运输）？",
|
|
9315
|
+
"rationale": "纯室内基于 BLE 信标定位；室内外混合推荐 SenseCAP T1000 追踪器，室内切蓝牙/Wi-Fi 定位，室外切 GPS/北斗。"
|
|
9316
|
+
},
|
|
9317
|
+
{
|
|
9318
|
+
"dimension": "accuracy_budget",
|
|
9319
|
+
"question": "对定位精度的期望是怎样的？是需要精确到米级的具体坐标，还是只要知道人在哪间房/资产在哪个货架区域即可？",
|
|
9320
|
+
"rationale": "米级需部署高密度蓝牙基站；区域级可大幅减少基站数量，极大节约硬件成本与施工布线。"
|
|
9321
|
+
},
|
|
9322
|
+
{
|
|
9323
|
+
"dimension": "form_battery",
|
|
9324
|
+
"question": "被追踪对象的形态是什么（人员佩戴胸卡工牌，还是贴在货物托盘/设备上）？期望续航时间是多久？",
|
|
9325
|
+
"rationale": "决定选用超薄卡片型轻量 Tracker 还是超长续航工业 Tracker。"
|
|
9326
|
+
}
|
|
9327
|
+
]
|
|
9328
|
+
},
|
|
9329
|
+
"industrial-control-automation": {
|
|
9330
|
+
"domain": "现场控制与自动化 / PLC 边缘互联",
|
|
9331
|
+
"core_dimensions": [
|
|
9332
|
+
"工控总线协议种类",
|
|
9333
|
+
"导轨安装与供电环境",
|
|
9334
|
+
"边缘计算与控制响应周期"
|
|
9335
|
+
],
|
|
9336
|
+
"questions": [
|
|
9337
|
+
{
|
|
9338
|
+
"dimension": "bus_protocol",
|
|
9339
|
+
"question": "现场下位机设备主要采用什么总线和通信协议（如 Modbus TCP/RTU、CANopen、PROFINET、EtherNet/IP）？",
|
|
9340
|
+
"rationale": "决定边缘网关的物理接口（隔离 RS485、双网口、CAN 接口）以及协议转换中间件配置。"
|
|
9341
|
+
},
|
|
9342
|
+
{
|
|
9343
|
+
"dimension": "cabinet_power",
|
|
9344
|
+
"question": "设备是安装在标准工业电控柜导轨上吗？现场供电是直流 24V DC 还是交流 220V？",
|
|
9345
|
+
"rationale": "确认机型是否支持 DIN 导轨卡扣安装，以及宽压 DC 9~36V 输入。"
|
|
9346
|
+
},
|
|
9347
|
+
{
|
|
9348
|
+
"dimension": "control_cycle",
|
|
9349
|
+
"question": "业务需要做实时控制闭环（毫秒级控制周期），还是做上层数据采集与边缘分析诊断（秒级/分级）？",
|
|
9350
|
+
"rationale": "实时控制需要带实时补丁（PREEMPT_RT）的边缘控制器；数据采集与分析常规工业边缘电脑即可满足。"
|
|
9351
|
+
}
|
|
9352
|
+
]
|
|
9353
|
+
},
|
|
9354
|
+
"smart-warehouse-management": {
|
|
9355
|
+
"domain": "智慧仓库管理 / 货位状态与托盘盘点",
|
|
9356
|
+
"core_dimensions": [
|
|
9357
|
+
"货架结构与无线遮挡",
|
|
9358
|
+
"货位占空感知 vs 条码盘点",
|
|
9359
|
+
"库区网络覆盖"
|
|
9360
|
+
],
|
|
9361
|
+
"questions": [
|
|
9362
|
+
{
|
|
9363
|
+
"dimension": "rack_structure",
|
|
9364
|
+
"question": "仓库的货物存储形式是托盘平库、高位重型货架还是自动化立体仓？货架高度大概多高？",
|
|
9365
|
+
"rationale": "高位货架钢结构遮挡严重，需针对性设计相机俯视视角或工业无线天线布设。"
|
|
9366
|
+
},
|
|
9367
|
+
{
|
|
9368
|
+
"dimension": "perception_mode",
|
|
9369
|
+
"question": "核心诉求是“货位占用与空闲状态检测”（有货/无货），还是“具体托盘/货物条码精准盘点”？",
|
|
9370
|
+
"rationale": "货位空闲检测推荐边缘视觉一体机俯视感知；托盘精准身份盘点需结合 RFID 或蓝牙 Asset Tag。"
|
|
9371
|
+
},
|
|
9372
|
+
{
|
|
9373
|
+
"dimension": "network_coverage",
|
|
9374
|
+
"question": "库区内是否具备完整的有线网络或 Wi-Fi 覆盖？",
|
|
9375
|
+
"rationale": "无网络覆盖时需要配置长距离 LoRaWAN 或 4G 无线网关回传数据。"
|
|
9376
|
+
}
|
|
9377
|
+
]
|
|
9378
|
+
},
|
|
9379
|
+
"smart-retail-store": {
|
|
9380
|
+
"domain": "智慧零售门店 / 客流统计与货架动线",
|
|
9381
|
+
"core_dimensions": [
|
|
9382
|
+
"进出店客流计数 vs 店内热力动线",
|
|
9383
|
+
"门头吊顶施工布线",
|
|
9384
|
+
"多门店数据汇聚方式"
|
|
9385
|
+
],
|
|
9386
|
+
"questions": [
|
|
9387
|
+
{
|
|
9388
|
+
"dimension": "analytics_scope",
|
|
9389
|
+
"question": "统计的主要诉求是“出入口进店人数/客流双向计数”，还是“店内各货架区域的顾客停留时长与热力分布”？",
|
|
9390
|
+
"rationale": "出入口仅需门头单台垂直俯视 AI 相机；货架热力需广角全景相机或多机拼接。"
|
|
9391
|
+
},
|
|
9392
|
+
{
|
|
9393
|
+
"dimension": "ceiling_cabling",
|
|
9394
|
+
"question": "现场安装点位（通常在门头吊顶或天花板）是否预留了网线和供电？",
|
|
9395
|
+
"rationale": "支持 PoE 供电只需一根网线即可完成供电与通信，最利于商铺免破坏装修快速施工。"
|
|
9396
|
+
},
|
|
9397
|
+
{
|
|
9398
|
+
"dimension": "data_aggregation",
|
|
9399
|
+
"question": "连锁门店的数据汇总方式是怎样的？是单店本地显示，还是需要将多店客流数据自动上传到您的总部云端或 ERP 系统？",
|
|
9400
|
+
"rationale": "确认网络上报协议（MQTT/HTTP REST）及离线断网本地缓存需求。"
|
|
9401
|
+
}
|
|
9402
|
+
]
|
|
9403
|
+
},
|
|
9404
|
+
"off-grid-mesh-communication": {
|
|
9405
|
+
"domain": "离网与自组网通信 / 应急 Mesh",
|
|
9406
|
+
"core_dimensions": [
|
|
9407
|
+
"地形遮挡与视距",
|
|
9408
|
+
"便携手持 vs 高点中继基站",
|
|
9409
|
+
"地区无线电免许可频段"
|
|
9410
|
+
],
|
|
9411
|
+
"questions": [
|
|
9412
|
+
{
|
|
9413
|
+
"dimension": "terrain_los",
|
|
9414
|
+
"question": "应急通信的使用环境是在城市建筑物密集区域，还是在无手机信号的野外山区、森林或野营开阔地？",
|
|
9415
|
+
"rationale": "开阔地视距传输可达十几公里；建筑物阻隔多需要规划高点固定中继节点。"
|
|
9416
|
+
},
|
|
9417
|
+
{
|
|
9418
|
+
"dimension": "node_roles",
|
|
9419
|
+
"question": "组网节点主要是人员移动随身携带（如佩戴小巧终端配合手机发文字/位置），还是需要搭建固定的高位信号中继站？",
|
|
9420
|
+
"rationale": "固定高位站需配置大功率玻璃钢天线与太阳能充电套件；随身节点强调便携长续航。"
|
|
9421
|
+
},
|
|
9422
|
+
{
|
|
9423
|
+
"dimension": "rf_frequency",
|
|
9424
|
+
"question": "项目部署在哪个国家或地区？",
|
|
9425
|
+
"rationale": "确认合法的 LoRa 免许可频段，如中国 CN470、欧洲 EU868 或北美 US915，确保无线电合规。"
|
|
9426
|
+
}
|
|
9427
|
+
]
|
|
9428
|
+
},
|
|
9429
|
+
"acoustic-audio-ai": {
|
|
9430
|
+
"domain": "声学与音频 AI / 设备故障听诊",
|
|
9431
|
+
"core_dimensions": [
|
|
9432
|
+
"被测机械类型与异响特征",
|
|
9433
|
+
"声学麦克风 vs 振动声发射传感器",
|
|
9434
|
+
"车间环境背景噪音"
|
|
9435
|
+
],
|
|
9436
|
+
"questions": [
|
|
9437
|
+
{
|
|
9438
|
+
"dimension": "machine_defect",
|
|
9439
|
+
"question": "被监测的机械设备是什么（例如电机、轴承、齿轮箱、还是水泵压缩机）？想捕获的异常特征是什么（异响磨损、撞击声还是高压气体泄漏）？",
|
|
9440
|
+
"rationale": "决定选择声学麦克风阵列还是接触式高频振动/声发射探头。"
|
|
9441
|
+
},
|
|
9442
|
+
{
|
|
9443
|
+
"dimension": "ambient_noise",
|
|
9444
|
+
"question": "设备周边是否有其他强烈机械运转的背景杂音？",
|
|
9445
|
+
"rationale": "强背景杂音需利用端侧硬件 DSP 滤波器及降噪算法将工作主频滤除，突出异常脉冲。"
|
|
9446
|
+
},
|
|
9447
|
+
{
|
|
9448
|
+
"dimension": "alarm_latency",
|
|
9449
|
+
"question": "检测到异响异常后，希望在多长时间内告警，并通过何种方式通知维护人员？",
|
|
9450
|
+
"rationale": "确定边缘推理实时性要求以及告警输出联动链路（声光/短信/PLC 停机信号）。"
|
|
9451
|
+
}
|
|
9452
|
+
]
|
|
9453
|
+
},
|
|
9454
|
+
"intelligent-video-analytics": {
|
|
9455
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
9456
|
+
"core_dimensions": [
|
|
9457
|
+
"分析目标与算法类型",
|
|
9458
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
9459
|
+
"夜间与恶劣环境"
|
|
9460
|
+
],
|
|
9461
|
+
"questions": [
|
|
9462
|
+
{
|
|
9463
|
+
"dimension": "analytics_target",
|
|
9464
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
9465
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
9466
|
+
},
|
|
9467
|
+
{
|
|
9468
|
+
"dimension": "stream_architecture",
|
|
9469
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
9470
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
9471
|
+
},
|
|
9472
|
+
{
|
|
9473
|
+
"dimension": "environment_lighting",
|
|
9474
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
9475
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
9476
|
+
}
|
|
9477
|
+
]
|
|
9478
|
+
},
|
|
9479
|
+
"smart-agriculture-sensing": {
|
|
9480
|
+
"domain": "智慧农业 / 环境监测与微气象",
|
|
9481
|
+
"core_dimensions": [
|
|
9482
|
+
"集中大棚 vs 广域农田",
|
|
9483
|
+
"市电 vs 太阳能/电池供电",
|
|
9484
|
+
"监测指标与探头深度"
|
|
9485
|
+
],
|
|
9486
|
+
"questions": [
|
|
9487
|
+
{
|
|
9488
|
+
"dimension": "topology",
|
|
9489
|
+
"question": "监测区域是集中式连栋温室大棚（百米级），还是大面积户外大田/果园（数公里级）？",
|
|
9490
|
+
"rationale": "大棚内百米级可采用 RS485 有线总线集中组网；广域大田推荐 LoRaWAN 远距离低功耗无线传输，配合 SenseCAP M2 网关。"
|
|
9491
|
+
},
|
|
9492
|
+
{
|
|
9493
|
+
"dimension": "power",
|
|
9494
|
+
"question": "现场测点是否有 220V 市电供电，还是需要野外太阳能板/锂电池长续航供电？",
|
|
9495
|
+
"rationale": "市电可支持持续高频数据上报；无市电需要选用带内置超大锂电池、支持休眠唤醒的低功耗无线传感器（如 S2100/S210x）。"
|
|
9496
|
+
},
|
|
9497
|
+
{
|
|
9498
|
+
"dimension": "sensing_depth",
|
|
9499
|
+
"question": "需要监测哪些核心环境指标？仅是空气温湿度/光照/CO2，还是包括土壤剖面墒情（深层水分/EC/pH）或气象风速风向？",
|
|
9500
|
+
"rationale": "决定是配置一体化多合一微气象站（如 S700/S2120），还是选配工业级土壤三参数/水肥专用探针与变送器。"
|
|
9501
|
+
}
|
|
9502
|
+
]
|
|
9503
|
+
},
|
|
9504
|
+
"agri_env_monitor": {
|
|
9505
|
+
"domain": "智慧农业 / 环境监测与微气象",
|
|
9506
|
+
"core_dimensions": [
|
|
9507
|
+
"集中大棚 vs 广域农田",
|
|
9508
|
+
"市电 vs 太阳能/电池供电",
|
|
9509
|
+
"监测指标与探头深度"
|
|
9510
|
+
],
|
|
9511
|
+
"questions": [
|
|
9512
|
+
{
|
|
9513
|
+
"dimension": "topology",
|
|
9514
|
+
"question": "监测区域是集中式连栋温室大棚（百米级），还是大面积户外大田/果园（数公里级）？",
|
|
9515
|
+
"rationale": "大棚内百米级可采用 RS485 有线总线集中组网；广域大田推荐 LoRaWAN 远距离低功耗无线传输，配合 SenseCAP M2 网关。"
|
|
9516
|
+
},
|
|
9517
|
+
{
|
|
9518
|
+
"dimension": "power",
|
|
9519
|
+
"question": "现场测点是否有 220V 市电供电，还是需要野外太阳能板/锂电池长续航供电？",
|
|
9520
|
+
"rationale": "市电可支持持续高频数据上报；无市电需要选用带内置超大锂电池、支持休眠唤醒的低功耗无线传感器（如 S2100/S210x）。"
|
|
9521
|
+
},
|
|
9522
|
+
{
|
|
9523
|
+
"dimension": "sensing_depth",
|
|
9524
|
+
"question": "需要监测哪些核心环境指标？仅是空气温湿度/光照/CO2，还是包括土壤剖面墒情（深层水分/EC/pH）或气象风速风向？",
|
|
9525
|
+
"rationale": "决定是配置一体化多合一微气象站（如 S700/S2120），还是选配工业级土壤三参数/水肥专用探针与变送器。"
|
|
9526
|
+
}
|
|
9527
|
+
]
|
|
9528
|
+
},
|
|
9529
|
+
"fall_detection": {
|
|
9530
|
+
"domain": "智慧养老 / 室内监护",
|
|
9531
|
+
"core_dimensions": [
|
|
9532
|
+
"集中 vs 分散空间分布",
|
|
9533
|
+
"存量摄像头利旧",
|
|
9534
|
+
"隐私保护与传感器形态"
|
|
9535
|
+
],
|
|
9536
|
+
"questions": [
|
|
9537
|
+
{
|
|
9538
|
+
"dimension": "topology",
|
|
9539
|
+
"question": "老人房间和公共区域是在同一层/同一楼栋比较集中，还是分散在多栋楼或较远区域？",
|
|
9540
|
+
"rationale": "集中分布可用 1 台 reComputer 主机拉多路 RTSP 流摊薄成本；分散点位推荐每间房独立 reCamera 一体机免拉长线。"
|
|
9541
|
+
},
|
|
9542
|
+
{
|
|
9543
|
+
"dimension": "asset_reuse",
|
|
9544
|
+
"question": "现场是否已经安装了支持 RTSP/ONVIF 协议的监控摄像头（如海康、大华等）？",
|
|
9545
|
+
"rationale": "已有摄像头可直接复用利旧，只需采购边缘算力盒，省去镜头重购成本；无摄像头则推荐成套硬件。"
|
|
9546
|
+
},
|
|
9547
|
+
{
|
|
9548
|
+
"dimension": "privacy_boundary",
|
|
9549
|
+
"question": "卫生间、卧室等高隐私区域是否对纯光学摄像头有顾虑，是否需要无视觉隐私的毫米波雷达方案？",
|
|
9550
|
+
"rationale": "私密区域用 60GHz 毫米波雷达替代光学镜头，既可精确检测跌倒卧床，又彻底消除侵犯隐私争议。"
|
|
9551
|
+
}
|
|
9552
|
+
]
|
|
9553
|
+
},
|
|
9554
|
+
"smart_warehouse": {
|
|
9555
|
+
"domain": "智慧仓库管理 / 货位状态与托盘盘点",
|
|
9556
|
+
"core_dimensions": [
|
|
9557
|
+
"货架结构与无线遮挡",
|
|
9558
|
+
"货位占空感知 vs 条码盘点",
|
|
9559
|
+
"库区网络覆盖"
|
|
9560
|
+
],
|
|
9561
|
+
"questions": [
|
|
9562
|
+
{
|
|
9563
|
+
"dimension": "rack_structure",
|
|
9564
|
+
"question": "仓库的货物存储形式是托盘平库、高位重型货架还是自动化立体仓？货架高度大概多高？",
|
|
9565
|
+
"rationale": "高位货架钢结构遮挡严重，需针对性设计相机俯视视角或工业无线天线布设。"
|
|
9566
|
+
},
|
|
9567
|
+
{
|
|
9568
|
+
"dimension": "perception_mode",
|
|
9569
|
+
"question": "核心诉求是“货位占用与空闲状态检测”（有货/无货），还是“具体托盘/货物条码精准盘点”？",
|
|
9570
|
+
"rationale": "货位空闲检测推荐边缘视觉一体机俯视感知；托盘精准身份盘点需结合 RFID 或蓝牙 Asset Tag。"
|
|
9571
|
+
},
|
|
9572
|
+
{
|
|
9573
|
+
"dimension": "network_coverage",
|
|
9574
|
+
"question": "库区内是否具备完整的有线网络或 Wi-Fi 覆盖？",
|
|
9575
|
+
"rationale": "无网络覆盖时需要配置长距离 LoRaWAN 或 4G 无线网关回传数据。"
|
|
9576
|
+
}
|
|
9577
|
+
]
|
|
9578
|
+
},
|
|
9579
|
+
"retail_voice": {
|
|
9580
|
+
"domain": "现场语音控制 / 离线语音助手",
|
|
9581
|
+
"core_dimensions": [
|
|
9582
|
+
"声学噪声与麦克风拾音距离",
|
|
9583
|
+
"100% 离线隐私 vs 云端大模型",
|
|
9584
|
+
"受控设备联动协议"
|
|
9585
|
+
],
|
|
9586
|
+
"questions": [
|
|
9587
|
+
{
|
|
9588
|
+
"dimension": "acoustic_environment",
|
|
9589
|
+
"question": "现场使用环境的噪音如何？通常是在安静的室内/会议室，还是存在环境背景噪音（如风扇、空调、人群嘈杂）？拾音距离多远？",
|
|
9590
|
+
"rationale": "决定麦克风阵列选型：近场安静可用双麦；远场（3~5米）与嘈杂环境必须使用带硬件 DSP、回声消除 AEC 与波束成形的 ReSpeaker XVF3800 多麦阵列。"
|
|
9591
|
+
},
|
|
9592
|
+
{
|
|
9593
|
+
"dimension": "privacy_connectivity",
|
|
9594
|
+
"question": "系统对网络和隐私有什么硬性要求？是必须 100% 纯本地离线断网运行，还是可以联网访问云端大模型？",
|
|
9595
|
+
"rationale": "纯离线需配置 Orin NX 等中高算力主机在端侧跑端到端小模型（Whisper + LLM + TTS）；联网混合模式可用轻量主机做前端拾音上云。"
|
|
9596
|
+
},
|
|
9597
|
+
{
|
|
9598
|
+
"dimension": "target_control",
|
|
9599
|
+
"question": "语音识别或大模型理解后，主要用来控制什么设备或执行什么业务？",
|
|
9600
|
+
"rationale": "明确南向控制接口：是对接 Home Assistant 智能家居、发送 MQTT 报文、还是通过串口/Modbus 控制工业继电器。"
|
|
9601
|
+
}
|
|
9602
|
+
]
|
|
9603
|
+
},
|
|
9604
|
+
"recamera_heatmap_grafana": {
|
|
9605
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
9606
|
+
"core_dimensions": [
|
|
9607
|
+
"分析目标与算法类型",
|
|
9608
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
9609
|
+
"夜间与恶劣环境"
|
|
9610
|
+
],
|
|
9611
|
+
"questions": [
|
|
9612
|
+
{
|
|
9613
|
+
"dimension": "analytics_target",
|
|
9614
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
9615
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
9616
|
+
},
|
|
9617
|
+
{
|
|
9618
|
+
"dimension": "stream_architecture",
|
|
9619
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
9620
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
9621
|
+
},
|
|
9622
|
+
{
|
|
9623
|
+
"dimension": "environment_lighting",
|
|
9624
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
9625
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
9626
|
+
}
|
|
9627
|
+
]
|
|
9628
|
+
},
|
|
9629
|
+
"smart_hvac_control": {
|
|
9630
|
+
"domain": "旧建筑节能改造 / 暖通与智能抄表",
|
|
9631
|
+
"core_dimensions": [
|
|
9632
|
+
"存量表计通信接口",
|
|
9633
|
+
"配电间集中 vs 跨楼层分布",
|
|
9634
|
+
"纯能耗采集 vs 闭环控制"
|
|
9635
|
+
],
|
|
9636
|
+
"questions": [
|
|
9637
|
+
{
|
|
9638
|
+
"dimension": "meter_interface",
|
|
9639
|
+
"question": "现场的电表、水表或空调机组目前是什么型号？是否自带 RS485（Modbus RTU / DL/T 645）通信接口，还是老旧机械表？",
|
|
9640
|
+
"rationale": "带 485 接口可直接低成本手拉手总线抄表；无通信接口的老旧机械表需更换智能表或加装开口式开口互感器 CT。"
|
|
9641
|
+
},
|
|
9642
|
+
{
|
|
9643
|
+
"dimension": "cable_distribution",
|
|
9644
|
+
"question": "表计是集中在配电室/机房，还是分散在各楼层的强电井中？各楼层之间是否有现成弱电网线贯通？",
|
|
9645
|
+
"rationale": "集中点位直接用有线网关接总线；跨楼层分散无布线推荐 SenseCAP LoRaWAN 采集器无线回传，大幅削减施工穿墙打洞成本。"
|
|
9646
|
+
},
|
|
9647
|
+
{
|
|
9648
|
+
"dimension": "control_requirement",
|
|
9649
|
+
"question": "需求是仅做“能耗监测与数据统计”，还是需要做“闭环节能控制”（如根据峰谷电价或人员在场调节空调回路）？",
|
|
9650
|
+
"rationale": "决定是否需要配置带工业继电器与模拟量输出的控制型网关。"
|
|
9651
|
+
}
|
|
9652
|
+
]
|
|
9653
|
+
},
|
|
9654
|
+
"indoor_positioning_ble_lorawan": {
|
|
9655
|
+
"domain": "室内外定位 / 资产与人员追踪",
|
|
9656
|
+
"core_dimensions": [
|
|
9657
|
+
"纯室内 vs 室内外混合",
|
|
9658
|
+
"定位精度期望（米级 vs 区域级）",
|
|
9659
|
+
"佩戴形式与免维护续航"
|
|
9660
|
+
],
|
|
9661
|
+
"questions": [
|
|
9662
|
+
{
|
|
9663
|
+
"dimension": "spatial_scope",
|
|
9664
|
+
"question": "定位场景是纯室内（厂房/展厅/仓库），还是室内外混合（比如仓库到室外堆场，甚至货物长途运输）？",
|
|
9665
|
+
"rationale": "纯室内基于 BLE 信标定位；室内外混合推荐 SenseCAP T1000 追踪器，室内切蓝牙/Wi-Fi 定位，室外切 GPS/北斗。"
|
|
9666
|
+
},
|
|
9667
|
+
{
|
|
9668
|
+
"dimension": "accuracy_budget",
|
|
9669
|
+
"question": "对定位精度的期望是怎样的？是需要精确到米级的具体坐标，还是只要知道人在哪间房/资产在哪个货架区域即可？",
|
|
9670
|
+
"rationale": "米级需部署高密度蓝牙基站；区域级可大幅减少基站数量，极大节约硬件成本与施工布线。"
|
|
9671
|
+
},
|
|
9672
|
+
{
|
|
9673
|
+
"dimension": "form_battery",
|
|
9674
|
+
"question": "被追踪对象的形态是什么（人员佩戴胸卡工牌，还是贴在货物托盘/设备上）？期望续航时间是多久？",
|
|
9675
|
+
"rationale": "决定选用超薄卡片型轻量 Tracker 还是超长续航工业 Tracker。"
|
|
9676
|
+
}
|
|
9677
|
+
]
|
|
9678
|
+
},
|
|
9679
|
+
"multi_protocol_gateway": {
|
|
9680
|
+
"domain": "现场控制与自动化 / PLC 边缘互联",
|
|
9681
|
+
"core_dimensions": [
|
|
9682
|
+
"工控总线协议种类",
|
|
9683
|
+
"导轨安装与供电环境",
|
|
9684
|
+
"边缘计算与控制响应周期"
|
|
9685
|
+
],
|
|
9686
|
+
"questions": [
|
|
9687
|
+
{
|
|
9688
|
+
"dimension": "bus_protocol",
|
|
9689
|
+
"question": "现场下位机设备主要采用什么总线和通信协议（如 Modbus TCP/RTU、CANopen、PROFINET、EtherNet/IP）？",
|
|
9690
|
+
"rationale": "决定边缘网关的物理接口（隔离 RS485、双网口、CAN 接口）以及协议转换中间件配置。"
|
|
9691
|
+
},
|
|
9692
|
+
{
|
|
9693
|
+
"dimension": "cabinet_power",
|
|
9694
|
+
"question": "设备是安装在标准工业电控柜导轨上吗？现场供电是直流 24V DC 还是交流 220V？",
|
|
9695
|
+
"rationale": "确认机型是否支持 DIN 导轨卡扣安装，以及宽压 DC 9~36V 输入。"
|
|
9696
|
+
},
|
|
9697
|
+
{
|
|
9698
|
+
"dimension": "control_cycle",
|
|
9699
|
+
"question": "业务需要做实时控制闭环（毫秒级控制周期），还是做上层数据采集与边缘分析诊断（秒级/分级）？",
|
|
9700
|
+
"rationale": "实时控制需要带实时补丁（PREEMPT_RT）的边缘控制器；数据采集与分析常规工业边缘电脑即可满足。"
|
|
9701
|
+
}
|
|
9702
|
+
]
|
|
9703
|
+
},
|
|
9704
|
+
"edge_inspection_surface": {
|
|
9705
|
+
"domain": "工业视觉质检 / 表面缺陷与装配复检",
|
|
9706
|
+
"core_dimensions": [
|
|
9707
|
+
"产线生产节拍与相机快门",
|
|
9708
|
+
"工件材质反光与照明",
|
|
9709
|
+
"剔除执行与 PLC 信号闭环"
|
|
9710
|
+
],
|
|
9711
|
+
"questions": [
|
|
9712
|
+
{
|
|
9713
|
+
"dimension": "line_speed",
|
|
9714
|
+
"question": "现场流水线的生产节拍是怎样的（每分钟过检多少件产品，工件是静止拍照还是运动中飞拍）？",
|
|
9715
|
+
"rationale": "决定相机曝光类型（运动飞拍必须全局快门 Global Shutter），以及端侧推理帧率与 Jetson 算力等级（Orin Nano vs Orin NX）。"
|
|
9716
|
+
},
|
|
9717
|
+
{
|
|
9718
|
+
"dimension": "materials_lighting",
|
|
9719
|
+
"question": "被测工件表面是什么材质（反光金属、高光塑料还是普通漫反射包装）？缺陷尺寸大概在什么毫米级别？",
|
|
9720
|
+
"rationale": "反光表面需定制特殊工业光源（如偏光环形光、同轴光）消除眩光；缺陷精度决定工业相机分辨率与镜头焦距。"
|
|
9721
|
+
},
|
|
9722
|
+
{
|
|
9723
|
+
"dimension": "plc_integration",
|
|
9724
|
+
"question": "检测出不良品后，边缘设备是否需要直接向现场 PLC 或气缸发送剔除信号？",
|
|
9725
|
+
"rationale": "决定是否需要选择带工业隔离数字量 I/O 的工控机型（如 reComputer Industrial 系列），并配置现场总线。"
|
|
9726
|
+
}
|
|
9727
|
+
]
|
|
9728
|
+
},
|
|
9729
|
+
"edge_waste_sorting": {
|
|
9730
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
9731
|
+
"core_dimensions": [
|
|
9732
|
+
"分析目标与算法类型",
|
|
9733
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
9734
|
+
"夜间与恶劣环境"
|
|
9735
|
+
],
|
|
9736
|
+
"questions": [
|
|
9737
|
+
{
|
|
9738
|
+
"dimension": "analytics_target",
|
|
9739
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
9740
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
9741
|
+
},
|
|
9742
|
+
{
|
|
9743
|
+
"dimension": "stream_architecture",
|
|
9744
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
9745
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
9746
|
+
},
|
|
9747
|
+
{
|
|
9748
|
+
"dimension": "environment_lighting",
|
|
9749
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
9750
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
9751
|
+
}
|
|
9752
|
+
]
|
|
9753
|
+
},
|
|
9754
|
+
"edge_retail_recognition": {
|
|
9755
|
+
"domain": "智慧零售门店 / 客流统计与货架动线",
|
|
9756
|
+
"core_dimensions": [
|
|
9757
|
+
"进出店客流计数 vs 店内热力动线",
|
|
9758
|
+
"门头吊顶施工布线",
|
|
9759
|
+
"多门店数据汇聚方式"
|
|
9760
|
+
],
|
|
9761
|
+
"questions": [
|
|
9762
|
+
{
|
|
9763
|
+
"dimension": "analytics_scope",
|
|
9764
|
+
"question": "统计的主要诉求是“出入口进店人数/客流双向计数”，还是“店内各货架区域的顾客停留时长与热力分布”？",
|
|
9765
|
+
"rationale": "出入口仅需门头单台垂直俯视 AI 相机；货架热力需广角全景相机或多机拼接。"
|
|
9766
|
+
},
|
|
9767
|
+
{
|
|
9768
|
+
"dimension": "ceiling_cabling",
|
|
9769
|
+
"question": "现场安装点位（通常在门头吊顶或天花板）是否预留了网线和供电？",
|
|
9770
|
+
"rationale": "支持 PoE 供电只需一根网线即可完成供电与通信，最利于商铺免破坏装修快速施工。"
|
|
9771
|
+
},
|
|
9772
|
+
{
|
|
9773
|
+
"dimension": "data_aggregation",
|
|
9774
|
+
"question": "连锁门店的数据汇总方式是怎样的？是单店本地显示，还是需要将多店客流数据自动上传到您的总部云端或 ERP 系统？",
|
|
9775
|
+
"rationale": "确认网络上报协议（MQTT/HTTP REST）及离线断网本地缓存需求。"
|
|
9776
|
+
}
|
|
9777
|
+
]
|
|
9778
|
+
},
|
|
9779
|
+
"edge_security": {
|
|
9780
|
+
"domain": "视觉与视频智能 / 通用边缘分析",
|
|
9781
|
+
"core_dimensions": [
|
|
9782
|
+
"分析目标与算法类型",
|
|
9783
|
+
"多路 RTSP 汇聚 vs 独立一体机",
|
|
9784
|
+
"夜间与恶劣环境"
|
|
9785
|
+
],
|
|
9786
|
+
"questions": [
|
|
9787
|
+
{
|
|
9788
|
+
"dimension": "analytics_target",
|
|
9789
|
+
"question": "主要需要检测什么目标与事件（如人员入侵、未戴安全帽反光衣、车辆违停、还是越界徘徊）？",
|
|
9790
|
+
"rationale": "确定所需模型组合（检测 + 跟踪 + 属性识别）以及对 Jetson 算力大小的要求。"
|
|
9791
|
+
},
|
|
9792
|
+
{
|
|
9793
|
+
"dimension": "stream_architecture",
|
|
9794
|
+
"question": "现场是汇聚已有的多路网络监控摄像头（RTSP 流），还是需要在特定点位新装一体化 AI 相机？",
|
|
9795
|
+
"rationale": "多路集中拉流推荐 reComputer J4012 (Orin NX)，支持 8~16 路视频流实时分析；单点分散推荐一体化智能相机。"
|
|
9796
|
+
},
|
|
9797
|
+
{
|
|
9798
|
+
"dimension": "environment_lighting",
|
|
9799
|
+
"question": "监控场景是否位于室外？夜间是否有照明，还是需要红外夜视/补光灯？",
|
|
9800
|
+
"rationale": "室外点位需确认机壳防护等级（IP66 防水防尘）与低照度夜视传感器支持。"
|
|
9801
|
+
}
|
|
9802
|
+
]
|
|
9803
|
+
},
|
|
9804
|
+
"unmanned_store_access": {
|
|
9805
|
+
"domain": "智慧零售门店 / 客流统计与货架动线",
|
|
9806
|
+
"core_dimensions": [
|
|
9807
|
+
"进出店客流计数 vs 店内热力动线",
|
|
9808
|
+
"门头吊顶施工布线",
|
|
9809
|
+
"多门店数据汇聚方式"
|
|
9810
|
+
],
|
|
9811
|
+
"questions": [
|
|
9812
|
+
{
|
|
9813
|
+
"dimension": "analytics_scope",
|
|
9814
|
+
"question": "统计的主要诉求是“出入口进店人数/客流双向计数”，还是“店内各货架区域的顾客停留时长与热力分布”？",
|
|
9815
|
+
"rationale": "出入口仅需门头单台垂直俯视 AI 相机；货架热力需广角全景相机或多机拼接。"
|
|
9816
|
+
},
|
|
9817
|
+
{
|
|
9818
|
+
"dimension": "ceiling_cabling",
|
|
9819
|
+
"question": "现场安装点位（通常在门头吊顶或天花板）是否预留了网线和供电？",
|
|
9820
|
+
"rationale": "支持 PoE 供电只需一根网线即可完成供电与通信，最利于商铺免破坏装修快速施工。"
|
|
9821
|
+
},
|
|
9822
|
+
{
|
|
9823
|
+
"dimension": "data_aggregation",
|
|
9824
|
+
"question": "连锁门店的数据汇总方式是怎样的？是单店本地显示，还是需要将多店客流数据自动上传到您的总部云端或 ERP 系统？",
|
|
9825
|
+
"rationale": "确认网络上报协议（MQTT/HTTP REST）及离线断网本地缓存需求。"
|
|
9826
|
+
}
|
|
9827
|
+
]
|
|
9828
|
+
}
|
|
7969
9829
|
}
|
|
7970
9830
|
}
|