Posts: 1,505
Threads: 143
Joined: May 2007
I updated the driver in the first post so that you can select "Inches of Mercury" or "Millibars" at initialization. The conversion I used was 1 inch of Mercury = 33.86389 Millibars.
Let me know if this is what you were interested in.
Posts: 475
Threads: 68
Joined: May 2015
Yup - this is just what I looking for. Thanks for the quick response!
Posts: 440
Threads: 49
Joined: Apr 2007
I installed the driver on a Win10 box with CQC version 6.07 and I get the following error.
CIDOrb_ClientBase.cpp.984, Failed/Timeout, Error: 1008/0/0
The server at fe80::b022:3389:5949:c547%16:13507 did not reply within the requested time. Proxy class=TCQCSrvAdminClientProxy
<CQCAdmin> CQCKit_CQCSrvAdminClientProxy.cpp - 1864
<CQCAdmin> CQCTreeBrws_DevicesBrws.cpp - 2414
Driver just won't connect and I have it configured properly with the API key and the lat/long info. Any ideas?
Posts: 1,505
Threads: 143
Joined: May 2007
(02-21-2023, 11:46 AM)Bugman Wrote: I installed the driver on a Win10 box with CQC version 6.07 and I get the following error.
CIDOrb_ClientBase.cpp.984, Failed/Timeout, Error: 1008/0/0
The server at fe80::b022:3389:5949:c547%16:13507 did not reply within the requested time. Proxy class=TCQCSrvAdminClientProxy
<CQCAdmin> CQCKit_CQCSrvAdminClientProxy.cpp - 1864
<CQCAdmin> CQCTreeBrws_DevicesBrws.cpp - 2414
Driver just won't connect and I have it configured properly with the API key and the lat/long info. Any ideas
Just looking at the message, it seems that the driver is not connecting to the
13507, which is the CQCServer port. I am still running it without any problems. It may be an issue similar to what we have seen in the RainMachine Driver where we had to increase the time to get the request. I will be happy to update driver with an added timeout like was done with the RainMachine driver.