I have installed rtldavis as advised
here https://github.com/lheijst/rtldavis and also took care of compiling my
own librtlsdr as advised
here https://groups.google.com/g/weewx-development/c/L5Lt8x87I_s/m/PP5AdFnQAQAJ.
After doing that I don't get anymore the message "Allocating 1 zero-copy
is indeed working.
I'm indeed in the EU so the frequency should be good (the ISS is also the
EU version).
*Guido Cioni*
On Tue, Jul 19, 2022 at 1:56 PM Greg Troxel wrote:
>
> [I'm answering here, but really this belongs on -users!]
>
> Guido Cioni writes:
>
> > I ha
, July 19, 2022 at 2:31:18 PM UTC+2 Guido Cioni wrote:
> I also tried to do a quick scan with the dongle and I can indeed see the
> transmission from the ISS, only rtldavis is not able to get it
>
> here is the waterfall from the dongle
>
> [image: Screen Shot 2022-07-
>From what I understand weewx uses sqlite because of the default, and with
sqlite the only possibility is to dump the whole database every time
(https://github.com/glennmckechnie/weewx-sqlbackup/wiki/SQLBackup-README),
which is obviously time consuming.
With Pandas you can get around that by
s so little amount of
> data each day.
>
> Just my $0.02
>
> DDJ
>
> On Thu, Jul 28, 2022 at 10:27 AM Guido Cioni wrote:
>
>> From what I understand weewx uses sqlite because of the default, and with
>> sqlite the only possibility is to dump the whole dat
So, I finally got it. After using a constant frequency shift of 5 Hz
(with the option -fc) I was able to receive all the packages. It seems not
to miss any measurement which is really good!
On Thursday, July 21, 2022 at 12:38:01 PM UTC+2 Guido Cioni wrote:
> Ok I've solved the issue by
Been using weewx-rtldavis for a few weeks now and I'm super happy with the
performance.
I receive the data from a Davis Vantage Vue ISS only.
However, there are a few things that I cannot figure out
- The fraction of missed packages/good packages is not saved into the
database:
I've been looking for a solution to backup my db directly inside weewx
without calling external cronjobs. The backup will be done on a SQL
database running on another server.
For this reason I don't want to make a physical copy of the DB but instead
copy only the rows that are not on the remote
Well...space and bandwidth may be an issue in remote installations, like
the one that I have, where everything get through a metered connection.
That's why I'm trying to find a way to transmit only the data that I have
to transmit every time to backup: this way I could backup more frequently.
