Hi Andrew Thanks for reply and help, you may just have given me the information I need to debug this issue.
Yes I do indeed realise that Thomas is 'Mr Weewx' and yes I love this application too, that's why I went down the Weewx path. I looked at the amount of support folks were given when they struck hiccups and went 'wow' this is definitely what I'm looking for. So I meant absolutely no disrespect in my reply, perhaps it was tinged with a days debug frustration. I think what you've said about running Weewx from the command line is exactly what I needed to know. The more information I can get for the WeatherDuino folk the faster they can fix any problem, so any logs etc from the Vantage driver will be a huge help. I had already gone back to the vanilla Weewx, in fact I may do a complete rebuild tomorrow to see if that helps. At the moment I just want to get good data flowing then I can move onto the glossy stuff. Many thanks again Andrew, hopefully Thomas hasn't written me off just yet! Cheers Colin On Mon, 29 Oct 2018, 22:22 Andrew Milner, <[email protected]> wrote: > Colin > FYI Thomas IS mr weewx - it is HIS creation and HIS design. If you are > going to continue with weewx you'd be well advised to listen to what Thomas > says!!!! > > Have you tried setting the debug options to gain further information?? > > The simulator does not use any hardware, does not obtain timestamps from > anywhere other than the host machine - this could be why a new db with > simulator works. The vantage driver has many years of successful operation > with Davis hardware - whilst your Davis lookalike appears to generate > archive types and timestamps which would not come from a real Davis device. > > Have you run from the command line rather than as a background daemon?? > This then gives Loop and Rec data as received - see the weewx user > documentation for more information. > > Since the hardware appears to be 'under development' I would recommend > using only the standard weewx software - as downloaded from weewx > repository, using the standard skin (not Belchertown) until such time as > you have got everything working correctly - and then, and only then, start > to use other skins. The standard weewx uses much less cpu processing power > than some of the other skins such as forecasts, Belchertown etc. Slowly > but surely is the best way to sort out new hardware and software - and you > would appear to have both involved here!! > > weewx is great, it is very stable, and it just works straight out of the > box. It rarely has bugs and very rarely has issues even. It is flexible, > versatile, adaptable, extendable - how many more adjectives do you > need??!! However - whilst the standard weewx is well proven the same is > not necessarily true for user supplied add-ons and enhancements. > > > > > > > On Monday, 29 October 2018 06:05:45 UTC+2, Colin Larsen wrote: >> >> Hi Thomas >> >> While I may agree with you that it's a station hardware problem I do find >> that a particularly unhelpful statement. >> >> When you say "clearly" where do you see that in my information and what >> could I pass to them to help debug the issue please? Is there a way to >> capture the information being sent to Weewx via the driver? >> >> Interestingly if I create a new Weewx db file, start weewx with simulator >> and then swap to the vantage driver it seems to work ok. >> >> I went the Weewx route because I saw that the help from the developers >> and users was fantastic. Unfortunately your blanket and somewhat unhelpful >> statement dims that a little. I hope this isn't starting to shape up as 'he >> said, she said' problem >> >> I really like this software so hopefully there is a solution here >> somewhere :) >> >> Cheers >> Colin >> >> On Monday, 29 October 2018 14:57:48 UTC+13, Thomas Keffer wrote: >>> >>> Why don't you ask the WeatherDuino people about this? Clearly, your >>> instrument is emitting some strange timestamps and archive types... >>> >>> -tk >>> >>> On Sun, Oct 28, 2018 at 6:43 PM Colin Larsen <[email protected]> >>> wrote: >>> >>>> I wonder if the Pi I'm using is a little cranky now - so many confusing >>>> problems popping up. >>>> >>>> Just saw this one in the log - another time anomaly though - >>>> 27392398.74 seconds fast ???? >>>> >>>> Oct 29 14:37:01 raspberrypi weewx[10296]: engine: Starting up weewx >>>> version 3.8.2 >>>> >>>> Oct 29 14:37:01 raspberrypi weewx[10296]: engine: Clock error is >>>> 27392398.74 seconds (positive is fast) >>>> >>>> Oct 29 14:37:02 raspberrypi weewx[10296]: vantage: Clock set to >>>> 2018-10-29 14:37:02 NZDT (1540777022) >>>> >>>> Oct 29 14:37:02 raspberrypi weewx[10296]: manager: Unable to add record >>>> 2018-10-29 14:35:00 NZDT (1540776900) to database 'weewx.sdb': UNIQUE >>>> constraint failed: archive.dateTime >>>> >>>> Oct 29 14:37:02 raspberrypi weewx[10296]: engine: Internal error >>>> detected. Catchup abandoned >>>> >>>> Oct 29 14:37:02 raspberrypi weewx[10296]: **** Unknown archive type = >>>> 0x7a >>>> >>>> Oct 29 14:37:02 raspberrypi weewx[10296]: engine: Starting main packet >>>> loop. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "weewx-user" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
