consumes gpsd as datasource and pushes location to kuksa.val server.
The gpsd_feeder.ini contains kuksa.val and gpsd configuration.
Before starting the gps feeder, you need to start kuksa.val server/databroker (for this have a look at KUKSA.val server and KUKSA.val databroker). You have to start an instance of gpsd by running:
gpsd -S <gpsd port> -N <gps device>
If you do not have a gps device, you can use your cellphone to forward gps data to gpsd. For example gpsd-forward is an open source android app. You can start gpsd with the following command to receive data from the app:
gpsd -N udp://0.0.0.0:29998
usage: gpsd_feeder.py [-h] [--host [HOST]] [--port [PORT]] [--protocol [PROTOCOL]] [--insecure [INSECURE]] [--certificate [CERTIFICATE]] [--cacertificate [CACERTIFICATE]] [--token [TOKEN]] [--file [FILE]] [--gpsd_host [GPSD_HOST]] [--gpsd_port [GPSD_PORT]] [--interval [INTERVAL]]
options:
-h, --help show this help message and exit
--host [HOST] Specify the host where too look for KUKSA.val server/databroker; default: 127.0.0.1
--port [PORT] Specify the port where too look for KUKSA.val server/databroker; default: 8090
--protocol [PROTOCOL] If you want to connect to KUKSA.val server specify ws. If you want to connect to KUKSA.val databroker specify grpc; default: ws
--insecure [INSECURE] For KUKSA.val server specify False, for KUKSA.val databroker there is currently no security so specify True; default: False
--certificate [CERTIFICATE] Specify the path to your Client.pem file; default: Client.pem
--cacertificate [CACERTIFICATE] Specify the path to your CA.pem; default: CA.pem
--token [TOKEN] Specify the path to your JWT token; default: all-read-write.json
--file [FILE] Specify the path to your config file; default: config/gpsd_feeder.ini
--gpsd_host [GPSD_HOST] Specify the host for gpsd to start on; default: 127.0.0.1
--gpsd_port [GPSD_PORT] Specify the port for gpsd to start on; default: 2948
--interval [INTERVAL] Specify the interval time for feeding gps data; default: 1
pip install -r requirements.txt
python gpsd_feeder.py
You can also use docker to execute the feeder platform independently.
To build a docker image:
docker build -t gpsd_feeder .
You can also download docker images from our container registry.
To run:
docker run -it -p 29998:29998/udp -v $PWD/config:/config gpsd_feeder
The container contains an internal gpsd daemon and the exposed UDP port can be used to feed NMEA data e.g. with gpsd-forward from an Android phone. If you already have a configured GPSd, just modify the config file to point to it.
Keep in mind, that GPSd normally only listens on localhost/loopback interface. To connect it from another interface start gpsd with the -D option
You can also use gpsfake to playback a gps logs in e.g. nmea format.
To install gpsfake, follow the command in this link.
After installation, run the following command to simulate a gps device as datasource:
gpsfake -P 2947 simplelog_example.nmea
Note: You need to use the gpsfake with the same version like the installed gpsd.
There are several tools for generating nmea log files:
If you see a gpsfake error message similar to this one after the feeder connected:
gpsfake: log cycle of simplelog_example.nmea begins.
gpsd:ERROR: SER: device open of /dev/pts/8 failed: Permission denied - retrying read-only
gpsd:ERROR: SER: read-only device open of /dev/pts/8 failed: Permission denied
gpsd:ERROR: /dev/pts/8: device activation failed, freeing device.
This might be due to a an overly restrictive apparmor configuration. On Ubuuntu edit the file /etc/apparmor.d/usr.sbin.gpsd
search for a section looking like this
# common serial paths to GPS devices
/dev/tty{,S,USB,AMA,ACM}[0-9]* rw,
/sys/dev/char r,
/sys/dev/char/** r,
And add a line for pts device so that it looks like
# common serial paths to GPS devices
/dev/tty{,S,USB,AMA,ACM}[0-9]* rw,
/dev/pts/[0-9]* rw,
/sys/dev/char r,
/sys/dev/char/** r,
Restart apparmor
sudo systemctl restart apparmor
and try again