WD Stopped getting Data (got better info now)

Brian,

The pause that I have been talking about for so long (worse on Mojave and WD64) - it happened while I was in front of my mac.

This time your cronjob kept trying every 2 mins but was failing. I captured screen shots of the various logs.

Program event log shows a bunch of “bad descriptor at time xx” along with “Inappropriate ioctl for device at time/date xx”

I also tried to go into control panel to make sure the com port was open. The first time I did that it tried to open a bluetooth port. I tried again and
it went to the right SLAB to USBUart - but still wouldn’t pull data.

Then I unplugged the USB port and put it back in. WD appeared to be getting the data. However, i was getting it from a day ago yet the screen shot shows it was trying to get from
a few mins ago. I let this run to completion and then WD started back as normal.

I’m hoping this new info will help you out. Again I know you have your hands full with Catalina. But curious what you think

I had to compress al the screen shots and will send via email

Thanks !!!

Do u have the latest silicon labs driver
This a driver issue
But also could simply be an issue with the
Power supply to the Davis console
I.e not enough juice to run the USB data logger at times

Yes i’m on the latest silicon driver

I would tend to agree with you regarding driver issue.

Davis logger. Not sure what to check. VP console is literally on the other side of a wall as my computer. I think the cable
is 6’ - but would have to check.

I did post something on the Silabs forum but doubt I will get any response there. I can try to open a ticket with t hem but suspect they will shoot me down (think they did way back when)

Anything I can do to narrow this down?

I checked the VP console. From the logger there is a connector that goes to the USB cable which goes through the wall into my mac (total length is maybe 3’ or so. I could shut down WD unplug that
connector and re-connect it, but it seemed snug

Btw i went into console and saw a bunch of these from yesterday (see screen shot)


Paul$ kextstat | grep silabs
130 0 0xffffff7f80f1b000 0x9000 0x9000 com.silabs.driver.CP210xVCPDriver (5.2.2) 79BD054F-7A71-34DE-9763-59D44DAC0615 <65 23 5 3>
tests-iMac:~ Paul$

5.2.2 is the latest version

I would change the power supply adapter to the davis console (use one with more output)

Brian, thanks. NOT sure how to do that (will google). This is one plug from the Davis to an outlet. I could try a different outlet.

From the other thread, I will try the new version as well

The other thing I will try when I’m home is uninstalling the latest Silabs driver and going back 2-3 revs to what I was using on High Sierra (it is possible their latest version to make it work for Catalina broke something)

I also posted in their forum (not hopeful of a reply). I posted a tech support ticket. However, since i’m not a developer I suspect they won’t respond or just close it.

WD is almost completely un-usable to me. I can’t get anything to work. IF I do, its a brief working situation

If this doesn’t work, I will boot up my High Sierra Imac and just run WD on that.

Many thanks !!!

Brian

I grabbed the version you told me to get.

The VP import worked perfectly (as it did before). But then when the “live” data part comes it does nothing.

Then when your restart kicked in, the live data was fine.

VERY ODD

If a driver problem I would expect the VP import to not go as smoothly

see how it works going forward

You know I will :smiley:

Btw I saw a newer version. Should I have grabbed that. I grabbed the one you told me to get

Btw so far data is coming in fine. WAY too early to tell

I submitted a ticket with Silabs. I’m NOT hopeful of a reply there. The data logger is ONE cable from CP to Mac. I could see if Davis would send me a new one. Who knows maybe I have a bad cable. Why it got worse with the update i haven’t a clue

Many thanks for all your help

Silabs actually responded. They asked me:

Which USB Bridge device does this system use? You’ve listed CP2102N-QFN20…is this accurate and do you know which revision (ordering part number)?
Can you provide the serial port configuration? baud rate, data bits, flow control, etc.
Would you be able to provide USB logs using a USB protocol sniffer such as the Ellisys USB Explorer 200 or Wireshark’s software version - CaptureSetup/USB - Wireshark Wiki?

For the second question I looked in WD and found the baud rate of 19200. But not sure where I get the other data. Is there a way to get this OR is off the Davis VP console?

just see how this update goes for now rather than going off on tangents

Thats fair… So far its still chugging along

I got another reply from them pushing it back to you LOL (you have way too much on your plate right now)

Hello Paul,

Is the developer able to reproduce the issue? Silicon Labs sells CP21xx USB bridge devices to product manufacturers for use in end-customer products. Silicon Labs provides reference drivers primarily for development purposes, and the reference driver is not intended for use for the end customer. Product manufacturers are expected to customize/productize the CP21xx device and reference driver for their product.

It will likely be most helpful if the developer opens up a customer support ticket with us (as you have) so that we can support this issue from the development side, and also provide a solution that they can supply to all of their customers. Would you mind suggesting to the developer to contact us please?

Thanks,
Austin

as I say, rather go off on tangents like this, see how this new update of WD goes as I did change something that might help

also make sure u do not have the Mac screen saver in use, as that does not play nice with WD

thanks I DO have the screen saver on., will shut off

Here is a screen shot from over night.

You can see the gaps in data where it stopped and started etc

I exited WD, edited WDISPLAY.ini and changed the download to 00:05 - which got any missing data back.

Since Wundground is not working I couldn’t check the status (nice to get the table view to see all the time intervals)

When I got home the graph looks great - no data interruptions. I can tell from a record count that it had dropped off (since I wasn’t home I can’t tell how many times.

Curious what you changed to make it better?

Btw that workaround you put in a year ago - think you made it 2 minutes. Would it be worth it to go for 1 minute?

So I would say it is better for sure
p.s. I wrote this at 5am but forgot to hit submit


Here is a graph from just now… Looks way better


but wunderground is working with the latest update
the screen saver uses a lot of cpu (graphic GPU actually)
so turning that off will help a lot
it could simply have been that

Brian

I have the screen saver off and still getting the disconnects.

I hear what you are saying but…

  1. New Imac with a super awesome graphics card - thus I would think this shouldn’t be an issue
  2. While the issue has always occurred it was very intermittent until I went to new mac, new os and new wd oh and new silabs driver

I tend to agree with you driver. Good luck getting Silabs and Davis to work together. Cable would require a new logger (its one cable). It is VERY pricey. Unless I can
get Davis to ship me one and return the other. I may give Davis a call and run this past them and see if they will send me a loaner Logger-Cable

As always I greatly appreciate all your help

have you looked into using a different power supply to your Davis console