WXforum.net
Weather Station Hardware => Davis Instruments Weather Stations => Topic started by: Bashy on April 07, 2017, 04:26:28 AM
-
Hi folks
I have a Davis VP2 Plus with extra temp for night cloud and Leaf wetness for rain duration
using weatherlink USB I also have an OS 968 running with 3 extra sensors for similar to the
Davis setup again on USB. Both stations are on the same PC running separate instances of
WD.
The issue i am having is that the Davis will, at random and normally once a day or other day
flatline in WD.
I have, for now shut down the OS WD and removed the USB to serial from the PC.
Do you think that its possible that the OS station USB could be causing the Weatherlink
USB to stop receiving data? I wish i had gone serial now and that will be changing very soon
as i want the Weatherlink 6544 Alarm output. In the mean time though, it would be interesting
to try to figure out what is actually going on, oh and the pc USB is set not to shut down too
Any thoughts please?
-
Power saving enabled on your USB ports/hubs?
-
Hi Mark, no, that's turned off, I am using maximum performance too.. Wouldn't be so bad if it was as specific times, I could possibly narrow it down, when it happened last night, it was just after I had turned off the monitors and went to bed, I just so happened to check it after I finished reading and it had flatlined, had to get up and go sort it, that's when I pulled the plug on the OS.
PS just literally checked the USB ports in device manager too, they are all set to
off re power management
-
I have had the flatline-issue with Davis-VirtualVP-WD for years and have never figured out what cause it. For me do it happen maybe twice a month. The most disturbing thing with it is that while WeatherLink stops/resuming receiving data OK during those cases do WD just flatline what mess up the data in WD.
As result do i seriously think about putting WD in junk-bin and go the Raspberry+WeeWX-route instead.
-
I wont bin WD, albeit it is a pain having to modify the data before restarting WD, its not really
a WD fault perse' its pain not knowing why weatherlink stops talking to the USB, i believe that
its also random as to who has the issue too, as not everyone with a USB WL has this issue?
I will end up getting the serial alarm version, just hope that it dont do it with the serial to USB
is this possible that it might still do it?
Is it possible that its because i have the OS running alongside it?
-
I wont bin WD, albeit it is a pain having to modify the data before restarting WD, its not really
a WD fault perse
Not me either but its handling of flatlines are just crap vs Weatherlink what handles it correct (stops receiving data). Btw. i have serial-USB-extender and i have tryed multiple ones. The last one with drivers from the manfacturer.
-
Ah poo, so you have the serial WL?
-
Ah poo, so you have the serial WL?
Yep.
-
Dammit, i was hoping that would resolve things, Is there such as thing as a PCI card that has serial?
-
Forget that, yes there are, i thought so, perhaps this would be a better way to go?
-
I don't know.
-
For £15 i think its worth the risk, its either that or buy the serial to USB and i now know
that too is an issue, i will order one when it get the new WL, thanks for the twoing and frowing :
-
Did you look in the event viewer for windows to see if there are any corresponding events logged at the same time that your station flatlines? Have you tried running the computer in safemode with networking or using a modified start up with minimum drivers installed?
-
No, no and nope, didnt even think to think it could be a windows issue, thats a good point, if and when it does do it again
i will have a look in the event viewer and see whats what, as for safe mode, that woudlnt work would it due to minimal
drivers being loaded? i fear that the USB drivers for WL wont load?
Anyhoo, thats a good idea re' event viewer, thanks, will report back if and when i know more :)
-
WD does now detect a flat line for the OS WMR200 station and so then stops logging data, so that on restart it will add the missed history data correctly on to that stop
that could be done for the Davis VP
No one has suggested it though
-
One thing I ran into with the Davis USB logger: I had a florescent desk lamp and whenever I turned it on the USB connection would disconnect.
A real PITA when I'm trying to develop software...
Aside from replacing the lamp, I never really tried to figure out what specifically about it was causing the issue. My best guess, it was an RFI (Radio Frequency Interference) spike generated by the light igniting which was enough to mess up the logger's USB to Serial chip. That RFI could have been carried back through the power cables, or picked up wirelessly via the USB cable.
You may have something similar going. As a starting point, here's a list of some common sources of RFI: http://www.naic.edu/~sondy/rfi.html (http://www.naic.edu/~sondy/rfi.html)
One way to help fix RFI problems, utilize snap-on ferrite chokes for power and\or data carrying cables such as the USB cable.
Just a few thoughts.
-
WD does now detect a flat line for the OS WMR200 station and so then stops logging data, so that on restart it will add the missed history data correctly on to that stop
that could be done for the Davis VP
No one has suggested it though
That would be a great thing indeed.
-
So, I'm confused - is the problem with the Davis hardware? Or with the WD software? Or can you tell?
-
there are not many users of the software with this particular problem
so I would be inclined to go with Josiah
-
Hi Josiah,
I am going to rule out RFI at this point due to this
Wireless (turn wireless off on your computer and phone so they do not transmit)
Bluetooth
Cordless telephones
Remote mice and slide advancers
Mobile phones: Edge, 3G, 4G, LTE...
This was the 1st section in the list from the link ya posted, all of the above are involved, i.e. the PC has a bluetooth speaker,
i have my cordless phone off its cradle and lays where the pc is, the PC has Wifi for connection, although, just switched to
those powerline networking things (last few days so not that either) Mouse and keyboard is bluetooth and my Galaxy Note 3
sits on the desk a lot throughout the day so, if its one of those things, it would be happening all the time, wouldnt it?
I will not rule out ferrite choke thingys though, open to all trials :) To add, there is no set time of day that this happens, it is totally
random but, its mostly been during the daytime, happen once at night shortly after i closed down the monitors, its not those either
cause when its happened during the day, ive not touched the monitors, they are on from dusk till dawn basically (solar panels on the house, so i can :D )
dalecoy, i dont think its a WD issue, but, what i havent tried is closing WD and seeing if it still flatlines in WL too, that would rule out WD
Oh and i dont use virtualVP either, just direct. USB
Sods law, it aint done it since i started this thread, it normally does it when i am away from it, and its died for at least an hour....
-
WD does now detect a flat line for the OS WMR200 station and so then stops logging data, so that on restart it will add the missed history data correctly on to that stop
that could be done for the Davis VP
No one has suggested it though
That would be a great thing indeed.
sadly i cannot ask over there as one got himself banned for life......
-
So, I'm confused - is the problem with the Davis hardware? Or with the WD software? Or can you tell?
I would say its not a problem with WD itself as also WL stops getting data but WD should handle flatlines better. That should be core thing for any software what collects data.
-
Ah, no need to test WL now then....
-
It's not just an issue with the USB version, the IP version (on a Vue) would flatline too. That would force me to reboot the Davis console to get it working again. I finally bought the Belfreboy logger and haven't had any problems for a month.
-
Not good, so not really worth me buying the serial version then? I really wanted the alarm output too :(
-
So, I'm confused - is the problem with the Davis hardware? Or with the WD software? Or can you tell?
I would say its not a problem with WD itself as also WL stops getting data but WD should handle flatlines better. That should be core thing for any software what collects data.
Well, now I am really confused!
1. Are both WD and WL software running at the same time on the same USB port?
2. I thought this was Bashy's system? And I didn't see where Bashy had tested this. In fact, as I see, "dalecoy, i dont think its a WD issue, but, what i havent tried is closing WD and seeing if it still flatlines in WL too, that would rule out WD"
3. Or, weatherc, where am I missing the point here? How do you know that WL would not get data?
I'm not suggesting that this is a problem only with WD - I'm just asking if it's been confirmed that it is a Davis hardware problem.
-
Hi Dalecoy, sorry for any confusion, weatherc has the same issue by the sounds of it, I only have wd running, the reason I haven't tested yet us because it's not flatlines as yet, still waiting, also, as weatherc said that it still does it with WL o just thought there's was no need for me to test it, but, I will now, just waiting for it to happen again.... There was a time when it didn't do it for a good while, I. E. Perhaps over a week, just lately it's been either every day or every other day..
-
Hi Dalecoy, sorry for any confusion, weatherc has the same issue by the sounds of it,
Weatherc does not have the same system you have. Period.
.... the reason I haven't tested yet us because it's not flatlines as yet, still waiting,
Understood. You may find you have the same symptoms as weatherc - but perhaps not. And you have just made some significant changes to your system, too.
-
1. Are both WD and WL software running at the same time on the same USB port?
3. Or, weatherc, where am I missing the point here? How do you know that WL would not get data?
1. How about reading the earlier messages where i stated i use Virtual VP?
3. Because it stops generating those small graphs and once data is resumed do it download all the missing data (lots of packets).
Weatherc does not have the same system you have. Period.
Not same system but same problem, data stops coming and WD goes flatline. Peroid.
-
Yes, i agree, exact same issue..
OK, its still not done it but i have checked all the logs in the event viewer, this only things that show up at around the time the last flatline occurred are these
These errors occur every 30 minutes, so i think they are sommat to do with what i have running in WD but NOT the cause of the flatlines
Log Name: Application
Source: Microsoft-Windows-Perflib
Date: 06/04/2017 20:03:02
Event ID: 1008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Weather
Description:
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
<EventID Qualifiers="49152">1008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-06T19:03:02.071529700Z" />
<EventRecordID>48129</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Weather</Computer>
<Security />
</System>
<UserData>
<EventXML xmlns="Perflib">
<param1>BITS</param1>
<param2>C:\Windows\System32\bitsperf.dll</param2>
<binaryDataSize>8</binaryDataSize>
<binaryData>0500000000000000</binaryData>
</EventXML>
</UserData>
</Event>
Log Name: Application
Source: Microsoft-Windows-Perflib
Date: 06/04/2017 20:03:02
Event ID: 1008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Weather
Description:
The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
<EventID Qualifiers="49152">1008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-06T19:03:02.074530300Z" />
<EventRecordID>48130</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Weather</Computer>
<Security />
</System>
<UserData>
<EventXML xmlns="Perflib">
<param1>ESENT</param1>
<param2>C:\WINDOWS\system32\esentprf.dll</param2>
<binaryDataSize>8</binaryDataSize>
<binaryData>0500000000000000</binaryData>
</EventXML>
</UserData>
</Event>
Log Name: Application
Source: Microsoft-Windows-Perflib
Date: 06/04/2017 20:03:02
Event ID: 1008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Weather
Description:
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
<EventID Qualifiers="49152">1008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-06T19:03:02.076530500Z" />
<EventRecordID>48131</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Weather</Computer>
<Security />
</System>
<UserData>
<EventXML xmlns="Perflib">
<param1>Lsa</param1>
<param2>C:\Windows\System32\Secur32.dll</param2>
<binaryDataSize>8</binaryDataSize>
<binaryData>0500000000000000</binaryData>
</EventXML>
</UserData>
</Event>
Log Name: Application
Source: Microsoft-Windows-Perflib
Date: 06/04/2017 20:03:02
Event ID: 1008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Weather
Description:
The Open Procedure for service "MSDTC" in DLL "C:\WINDOWS\system32\msdtcuiu.DLL" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
<EventID Qualifiers="49152">1008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-06T19:03:02.086531400Z" />
<EventRecordID>48132</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Weather</Computer>
<Security />
</System>
<UserData>
<EventXML xmlns="Perflib">
<param1>MSDTC</param1>
<param2>C:\WINDOWS\system32\msdtcuiu.DLL</param2>
<binaryDataSize>8</binaryDataSize>
<binaryData>0200078000000000</binaryData>
</EventXML>
</UserData>
</Event>
Log Name: Application
Source: Microsoft-Windows-PerfNet
Date: 06/04/2017 20:03:02
Event ID: 2004
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Weather
Description:
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-PerfNet" Guid="{CAB2B8A5-49B9-4EEC-B1B0-FAC21DA05A3B}" EventSourceName="PerfNet" />
<EventID Qualifiers="49152">2004</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-06T19:03:02.100532800Z" />
<EventRecordID>48133</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Weather</Computer>
<Security />
</System>
<EventData>
<Binary>220000C0</Binary>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-Windows-Perflib
Date: 06/04/2017 20:03:02
Event ID: 1008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Weather
Description:
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
<EventID Qualifiers="49152">1008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-06T19:03:02.175535900Z" />
<EventRecordID>48134</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Weather</Computer>
<Security />
</System>
<UserData>
<EventXML xmlns="Perflib">
<param1>WmiApRpl</param1>
<param2>C:\WINDOWS\system32\wbem\wmiaprpl.dll</param2>
<binaryDataSize>8</binaryDataSize>
<binaryData>1500000000000000</binaryData>
</EventXML>
</UserData>
</Event>
No warnings at the time, just those few small errors and theres nothing to show what may cause the usb to stop receiving data that i can tell
-
To further add, i do not know if this is a coincidence or not but, since changing from WIFI dongle
to powerline adapter, been no flatlines...... will update further if needs be
-
Still nothing to report, now makes me think it WAS the wifi dongle that was causing this,
been 6 days now since that last flatline....
-
Too early to say for sure - but see my Reply #27 above.
-
Noted, thanks.....
-
Prob be the last update on this one, no flatline since i removed the WIFI dongle.
This makes me beleive it was the dongle causing the issue, another reason why
i think this is because, when the dongle was plugged in direct to the PC USB it
flatlined but no where near as often, then i remembered about moving to an external
USB hub and put it up on the shelf just about the Envoy to get a better signal, it was at
this point when the flatines became more frequent. I then changed to powerline adapters
but left in the dongle and it still flatlined, i thine decided for no reason to remove the
WIFI dongle and since then no flatlines at all. going out on a limb here and say that
the WIFI dongle was the cause....
-
Hi Dalecoy, sorry for any confusion, weatherc has the same issue by the sounds of it,
Weatherc does not have the same system you have. Period.
-
Hi, not sure why you have said that again?
But, when i said that, i was referring to the issue at hand, WD flatlining with Davis
Regardless of the system, both have/had the same issue. Mine is now resolved, i do not know how weatherc is doing mind and i do not know if he is using a wifi dongle?
-
The point is - although the symptoms may seem identical, the fix may be entirely different.
So, as you pointed out, weatherc may not be able to fix his/her symptom by getting rid of a wifi dongle.
-
Yes, for sure, his may well be some other interference, but still, he has the same issue of his Davis flatlines in wd, that is the point of the whole thread regardless of what the cause is.
-
.... Davis flatlines in wd, ....
Assuming that your fix is correct on your system, the issue was with your computer hardware or computer operating system. [Or perhaps with the wd software]. There's no indication that the wifi dongle had any effect on anything "Davis".
Please note that I'm not trying to defend Davis. Just trying to point out that there's more to this than "Davis flatlines in wd".
Anyhow, glad your computer problem seems to be fixed.
-
I have left it long enough and there been nothing since removing the dongle, I can always put it back in to test this, I will do it tomorrow whilst I am in front of the pc most of the day.
There's not really much more to it other than an item interfering with the Davis usb, in effect, the issue is with Davis seen as no other hardware is affected by the wifi dongle, the dongle is at least 8 years old and this is the 1st time any issue like this has occurred....
-
The point is - although the symptoms may seem identical, the fix may be entirely different.
So, as you pointed out, weatherc may not be able to fix his/her symptom by getting rid of a wifi dongle.
I agree on that. I have no dongle connected to the wx-pc, only Davis, interweb are connected by pipeline :)
Close to the pc are a wifi-router + 4G dongle tought.
-
Have you tried moving the 4g away from the pc?
I was lucky, I found my cause purely by accident...
-
Have you tried moving the 4g away from the pc?
I was lucky, I found my cause purely by accident...
Not yet, but it could be worth a try.
-
How often do you get them? When my dongle was about 5ft away I would get a flat line perhaps once or twice a week, but when I moved it higher and closer (not knowing) just to get a better signal it would happen around once a day, it was about 8inches away from the envoy...
-
There's not really much more to it other than an item interfering with the Davis usb, in effect, the issue is with Davis seen as no other hardware is affected by the wifi dongle, the dongle is at least 8 years old and this is the 1st time any issue like this has occurred....
Just curious - do you have any other USB devices in use, other than the Davis logger? [And the wifi dongle when it's connected]
-
Hi, yes, I have the logitech pro 9000 webcam, the OS WMR 968 and a Bluetooth speaker and a wireless keyboard and mouse, all of the above run on USB oh and my note 3 when I Connect it to charge
-
Hi, yes, I have the logitech pro 9000 webcam, the OS WMR 968 and a Bluetooth speaker and a wireless keyboard and mouse, all of the above run on USB oh and my note 3 when I Connect it to charge
I presume those were all working OK when you stopped getting data from the Davis system.
Did you ever look at the Console Diagnostics when the problem happened?
-
Yeah, everything else worked OK, and erm, diagnostics?
Didn't know there was any thing like that, only had a Davis since February,plus its the envoy that's attached not the console....
-
....plus its the envoy that's attached not the console....
I missed that detail. [but you only mentioned the envoy today].
Yes, "console diagnostics" (see the manual) only work on a console, not on an envoy.
-
Just to be sure on the event viewer logs, open a command prompt with admin rights and run SFC /SCANNOW
-
Thanks, will run the scan in a bit
-
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.