dongle, so it can feed an active antenna (see #77)
The activation is done by adding
SignalSource.osmosdr_args=rtl,bias=1
to the configuration file, if using gr-osmosdr >= 0.1.4-13
For older versions of gr-osmosdr, you can use
https://github.com/rtlsdrblog/rtl_biast
GNSS-SDR.internal_fs_sps
The old name was misleading, since the units are samples per second and
not Hertz.
Backward compatibility is kept, so this change does not break any
existing configuration.
This commit Integrates RTKLIB positioning libraries in a universal PVT
block implementation called RTKLIB_PVT. This results in an improved
positioning accuracy and precision with a wide range of options
(including Precise Point Positioning and ionospheric/troposphreic
models).
Not all the RTKLIB features have been ported. Some of them will be
progressively added. The ported options and how to configure them have
been documented in the website, see
http://gnss-sdr.org/docs/sp-blocks/pvt/
This commit also introduces a multi-band, multi system Observables block
implementation.
Relevant architectural changes that reduce latency and makes
multi-system, multi band signal handling easier.
Redundant blocks have been deleted. Old configurations are automatically
redirected to the new blocks for Observables and PVT, so the commit does
not break any existing configuration. The user should just notice a
relevant improvement in positioning performance.
# Conflicts:
# src/core/receiver/gnss_flowgraph.cc
Added information on how to retrieve SUPL parameters, and indicators to
userd on where to point to their own file or IP address. Removed unused
parameter wait_for_flowgraph.
Old configurations folder removed. Names ending by "short" but reading
files of interleaved data have been renamed to "ishort". Some spare
fixes. Added examples of configuring the period and port of RTCM
messages.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
