1.edgexfoundry/device-rest-go
解析：EdgeX device service for REST protocol.
2.go-mod-configuration
解析：Configuration client library for use by Go implementation of EdgeX micro services. This project contains the abstract Configuration API and an implementation for Consul. The API initializes a connection to the Configuration service and push/pull configuration values to/from the Configuration service.
[1]Initialize connection to a Configuration service
[2]Push a service’s configuration in to the Configuration
[3]Pull service’s configuration from the Configuration service into its configuration struct
[4]Listen for configuration updates
3.go-mod-core-contracts
解析：
[1]This module contains the contract models used to describe data as it is passed via Request/Response between various EdgeX Foundry services. It also contains service clients for each service within the edgex-go repository. The definition of the various models and clients can be found in their respective top-level directories.
[2]The default encoding for the models is JSON, although in at least one case – DeviceProfile – YAML encoding is also supported since a device profile is defined as a YAML document.
4.go-mod-messaging
解析：Messaging client library for use by Go implementation of EdgeX micro services. This project contains the abstract Message Bus interface and an implementation for ZeroMQ, and MQTT. These interface functions connect, publish, subscribe and disconnect to/from the Message Bus.
[1]Create new MessageClient
[2]Commit to the Message Bus
[3]Public messages to the Message Bus
[4]Subscribe to and receives messages from the Messsage Bus
[5]Disconnect from the Message Bus
5.Docker EdgeX Consul
解析：This repo contains code necessary for building the Consul docker image to be used in Fuji and later releases.
6.go-mod-bootstrap
解析：This module contains the common bootstrap and dependency injection container originally implemented in the edgex-go repository and extracted here for reuse.
7.go-mod-registry
解析：Registry client library for use by Go implementation of EdgeX micro services. This project contains the abstract Registry interface and an implementation for Consul. These interface functions initialize a connection to the Registry service, register the service for discovery and health checks and request service endpoint and status.
[1]Initialize connection to a Registry service
[2]Register the service with the Registry service for discovery and the health check callback
[3]Pull service endpoint information from the Registry for dependent services
[4]Check the health status of dependent services via the Registry service
8.libzmq没装
解析：sudo apt-get install libzmq3-dev
9.Sync包
解析：Sync包同步提供基本的同步原语，比如互斥锁。
10.为EdgeX写一个设备服务
解析：通过EdgeX Device Service SDK，开发人员可以专注于通过设备协议与设备通信所特有的代码。
11.device-gps
解析：This repository contains a GPS device service for EdgeX Foundry 1.0. It was built using the EdgeX Device SDK Go provided by the EdgeX community. Once up and running, the device service will automatically push the location, aka the Geographical Coordinates from a USB GPS receiver to EdgeX, more specifically to the core-data microservice. This repository also contains a file with mock GPS data to allow users to test a GPS based application without recourse to a real GPS receiver.
12.edgex-kubernetes-support
解析：This repository contains supporting files to run various current and historical versions of EdgeX in Kubernetes (including K3s).
13.NMEA-0183
解析：NMEA 0183是美国国家海洋电子协会[National Marine Electronics Association]为海用电子设备制定的标准格式。目前已成了GPS导航设备统一的RTCM[Radio Technical Commission for Maritime services]标准协议。
14.OpenWRT
解析：OpenWRT是一个高度模块化、高度自动化的嵌入式Linux系统，拥有强大的网络组件和扩展性，常常被用于工控设备、电话、小型机器人、智能家居、路由器以及VOIP设备中。同时，它还提供了100多个已编译好的软件，而且数量还在不断增加，而OpenWrt SDK更简化了开发软件的工序。
15.OpenWrt路由器操作系统
解析：OpenWrt不同于其它许多用于路由器的发行版[主流路由器固件有DD-WRT，Tomato，OpenWrt三类]，它是一个从零开始编写的、功能齐全的、容易修改的路由器操作系统。
16.CoAP
解析：由于物联网中的很多设备都是资源受限型的，即只有少量的内存空间和有限的计算能力，所以传统的HTTP协议应用在物联网上就显得过于庞大而不适用。IETF的CoRE工作组提出了一种基于REST架构的CoAP协议。CoAP是6LowPAN协议栈中的应用层协议。
17.LWM2M定义三个逻辑实体
解析：
[1]LWM2M Server服务器
[2]LWM2M client客户端：负责执行服务器的命令和上报执行结果
[3]LWM2M引导服务器：Bootstrap server负责配置LWM2M客户端
18.LWM2M协议
解析：LWM2M协议是OMA组织制定的轻量化的M2M协议，主要面向基于蜂窝的窄带物联网[Narrow Band Internet of Things，NB-IoT]场景下物联网应用，聚焦于低功耗广覆盖[LPWA]物联网[IoT]市场，是一种可在全球范围内广泛应用的新兴技术。具有覆盖广、连接多、速率低、成本低、功耗低、架构优等特点。
说明：移动OneNET平台采用的是基于NB-IOT的LWM2M协议和CoAP协议实现UE与平台的通信，其中LWM2M协议为应用层协议，CoAP协议为传输层协议。
19.RTU
解析：远程终端单元[Remote Terminal Unit，RTU]，一种针对通信距离较长和工业现场环境恶劣而设计的具有模块化结构的、特殊的计算机测控单元。
20.温湿度传感器
解析：
[1]无线zigbee温湿度传感器
[2]无线射频温湿度传感器
[3]开关量信号输出温湿度传感器
[4]无线gprs温湿度传感器
21.上位机和下位机
解析：
[1]上位机是指可以直接发出操控命令的计算机，一般是PC/host computer/master computer/upper computer，屏幕上显示各种信号变化[液压，水位，温度等]。
[2]下位机是直接控制设备获取设备状况的计算机，一般是PLC/单片机single chip microcomputer/slave computer/lower computer之类的。
[3]上位机发出的命令首先给下位机，下位机再根据此命令解释成相应时序信号直接控制相应设备。下位机不时读取设备状态数据[一般为模拟量]，转换成数字信号反馈给上位机。
[4]在概念上，控制者和提供服务者是上位机，被控制者和被服务者是下位机，也可以理解为主机和从机的关系，但上位机和下位机是可以转换的。
22.dmesg命令
解析：Linux dmesg命令用于显示开机信息。kernel会将开机信息存储在ring buffer中。若是开机时来不及查看信息，可利用dmesg来查看。开机信息亦保存在/var/log目录中，名称为dmesg的文件里。
23.串口
解析：串行接口简称串口，也称串行通信接口或串行通讯接口[通常指COM接口]，是采用串行通信方式的扩展接口。串行接口 [Serial Interface]是指数据一位一位地顺序传送。其特点是通信线路简单，只要一对传输线就可以实现双向通信[可以直接利用电话线作为传输线]，从而大大降低了成本，特别适用于远距离通信，但传送速度较慢。
24.串行接口按电气标准及协议划分
解析：串行接口按电气标准及协议来分包括RS-232-C、RS-422、RS485等。RS-232-C、RS-422与RS-485标准只对接口的电气特性做出规定，不涉及接插件、电缆或协议。
25.电脑主板串口
解析：进行串行传输的接口，它一次只能传输1Bit。串行端口可以用于连接外置调制解调器、绘图仪或串行打印机。它也可以控制台连接的方式连接网络设备，例如路由器和交换机，主要用来配置它们。
参考文献：
[1]edgeX安装使用全系列：https://eiger.me/post/iot/edgex/
