You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+78Lines changed: 78 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,6 +92,84 @@ All config flows through the `EdgeConfig` dataclass in `config.py`:
92
92
93
93
See `config.py` for the full list. Standalone mode uses env vars and CLI args; IoT Edge mode uses twin desired properties.
94
94
95
+
## Connecting Sensors
96
+
97
+
There are three ingestion paths, depending on how sensors deliver data.
98
+
99
+
### Network Stream (live sensors)
100
+
101
+
Most oceanographic instruments output serial data. A serial-to-TCP converter (e.g. Moxa NPort, Digi Connect, or `ser2net` on Linux) bridges the serial port to a TCP socket.
102
+
103
+
**Server mode** — module listens, sensor/converter connects to it:
104
+
```
105
+
Sensor → Serial → ser2net/Moxa → TCP connect to :9100 → sensorstream
The `filenotifier` module watches raw data directories and sends messages when new files appear:
149
+
```json
150
+
"routes": {
151
+
"sensorNotifyToStream": "FROM /messages/modules/filenotifier/outputs/sensorfileadded INTO BrokeredEndpoint(\"/modules/iotedge-sensorstream/inputs/sensorfileadded\")"
152
+
}
153
+
```
154
+
155
+
### Combining Modes
156
+
157
+
Set `input_mode: "both"` to run file watcher and stream listener simultaneously — e.g. GNSS over TCP stream + CTD .hex files dropped to disk.
0 commit comments