Development

Simulator Setup

In order to effectively develop the tools for the David Packard (and Rachel Carson), we have a physical simulator running in Kevin's office. It consists of a computer that is generating simulated signals that are then made available in the same manner as data streams are on the ships. The streams are then consumed by the navproc and logging systems.

Physical Diagram

--- title: Navproc/Logging Classes --- flowchart LR richnuc3[RichNUC 3-Windows 10]

Signal Routes

| Device | RichNUC3 Process | Protocol/COM Port | Baud Rate | Parity |

Random Notes

1. Looked into OpenRVDAS, but in the documentation, they mention that the visualization tools they have on top of their database is pretty rudimentary and if you want professional dashboards, you should use InfluxDB with Grafana on top. If one was to go that route, you are basically using OpenRVDAS to provide instrument parsers and loaders for InfluxDB. Since we already have our own parsers, we really would need to just write the data loaders. Also, I am thinking TimescaleDB might be a better choice as it has really proven replication tools and if we build a large data store on shore, we could use replication to copy all the ship data to shore.