signalk
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| signalk [2024/01/16 14:20] – created river | signalk [2024/03/10 13:03] (current) – river | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== SignalK ====== | ====== SignalK ====== | ||
| - | ===== TCP ===== | + | ==== Connections |
| + | |||
| + | == TCP == | ||
| Port '' | Port '' | ||
| Line 7: | Line 9: | ||
| Deltas sent over tcp must be entirely on one line, and terminated by '' | Deltas sent over tcp must be entirely on one line, and terminated by '' | ||
| + | == Websockets == | ||
| + | |||
| + | Seems to be it's preferred transport. Port as configured web interface, default '' | ||
| + | |||
| + | == NMEA 0183 == | ||
| + | |||
| + | TCP port '' | ||
| + | |||
| + | == NMEA2000 == | ||
| + | |||
| + | It can use a SocketCAN adapter, e.g. CANable/ | ||
| + | |||
| + | NMEA 2000 Source: '' | ||
| + | Interface: '' | ||
| + | |||
| + | See also: [[can_interfaces|CAN Interfaces]] | ||
| + | |||
| + | === OpenCPN === | ||
| + | |||
| + | Recently OpenCPN has added SignalK support. It will connect to a SignalK server using the websockets protocol on (default) **port '' | ||
| + | |||
| + | ===== Documentation ===== | ||
| + | |||
| + | SignalK has pretensions to being a reïmplementable standard, and so has two sets of documentation. | ||
| + | |||
| + | * [[https:// | ||
| + | * [[http:// | ||
| + | **N.B.** The specification is not entirely implemented in the server, and the server docs don't tell what doesn' | ||
signalk.1705414801.txt.gz · Last modified: by river
