NMEA pass-through mode
This commit is contained in:
42
README.md
42
README.md
@@ -42,16 +42,23 @@ cmdline_init: ""
|
||||
vara_mode: false
|
||||
```
|
||||
|
||||
| Variable | Meaning |
|
||||
|-------------------|-----------------------------------------------------------------------------------------------------------------------------|
|
||||
| `device` | Path to the serial device where the modem is connected **or** `tcp://address:port` (useful for Android) |
|
||||
| `baudrate` | baud rate of the modem |
|
||||
| `mycall` | The callsign to be used on HF |
|
||||
| `server_address` | server socket address for the **commands** |
|
||||
| `data_address` | server socket address for the **data** |
|
||||
| `gpsd_address` | **optional** See the chapter about GPS below |
|
||||
Next time ptb will start using the settings in your config file.
|
||||
|
||||
## Settings
|
||||
|
||||
The meaning of the vables in the config file are as follows:
|
||||
|
||||
| Variable | Meaning |
|
||||
|-------------------|----------------------------------------------------------------------------------------------------------------|
|
||||
| `device` | Path to the serial device where the modem is connected **or** `tcp://address:port` (useful for Android) |
|
||||
| `baudrate` | baud rate of the modem |
|
||||
| `mycall` | The callsign to be used on HF |
|
||||
| `server_address` | server socket address for the **commands** |
|
||||
| `data_address` | server socket address for the **data** |
|
||||
| `gpsd_address` | **optional** See the chapter about GPS below |
|
||||
| `nmeapassthrough` | **only when gpsd_address has been set** bool value: if true pass NMEA data trough instead of interpreting them |
|
||||
| `cmdline_init` | extra commands sent to the modem before going into hostmode, separated by semicolons, Ex: `DISP BR 1;DISP A 1;DISP DIMMOFF` |
|
||||
| `vara_mode` | see the chapter about the VARA mode |
|
||||
| `vara_mode` | see the chapter about the VARA mode |
|
||||
|
||||
|
||||
|
||||
@@ -97,7 +104,9 @@ to make your position visible to Pat (or any other gpsd client).
|
||||
|
||||
To configure it you just need to add a line like
|
||||
|
||||
`gpsd_address: 0.0.0.0:2947`
|
||||
```yaml
|
||||
gpsd_address: 0.0.0.0:2947`
|
||||
```
|
||||
|
||||
to the config file. In Pat, a possible counterpart could look like this:
|
||||
|
||||
@@ -110,6 +119,19 @@ to the config file. In Pat, a possible counterpart could look like this:
|
||||
},
|
||||
```
|
||||
|
||||
### NMEA Pass-Through
|
||||
|
||||
If you need the **raw** NMEA data (for example if your GPS is not supported by the built-in mini-gpsd, or you want to
|
||||
run your own gpsd), set `nmeapassthough` to `true`, for example:
|
||||
|
||||
```yaml
|
||||
gpsd_address: 0.0.0.0:8888
|
||||
nmeapassthough: true
|
||||
```
|
||||
|
||||
Note that if you plan to use Pat, you'd need to run `gpsd` to use
|
||||
the position of the GNSS receiver.
|
||||
|
||||
## How to run
|
||||
|
||||
As a rule of thumb, you have to start the PACTOR-TCP-bridge before you want to use
|
||||
|
Reference in New Issue
Block a user