WXforum.net
Weather Station Hardware => Davis Instruments Weather Stations => Topic started by: SLOweather on July 20, 2011, 12:58:49 PM
-
I have a board design in hand for a straight serial interface and cable (no logger memory) for VPs, VP2s, Vues, and Envoys. Right now I'm looking at the quote from the board house, and pricing out the bill of materials to assemble it.
Please PM or email me if you are interested in testing this new cable for me.
Chris
-
I have a board design in hand for a straight serial interface and cable (no logger memory) for VPs, VP2s, Vues, and Envoys.
I think putting logger memory on it would be pretty straightforward, assuming your design would use the full 20 pin connector to the back of the console. Worth considering for the extra dollar in parts.
-
I think adding logger memory is probably the way to incur Davis' ire faster...
-
My logger was "clogged", the first year I had it. Didnt even know until I tried to troubleshoot something using WL. I guess since I was 24/7 using WD with only short downtimes I didnt even noticed it was "only" doing real time. So a straight through cable would have been fine for me.
Andrew
-
About how much will yours cost? :-)
-
About how much will yours cost? :-)
I don't yet know for sure. I'll probably order parts this week, and build a couple of test units when the parts arrive. There are still some unknowns, such as PC board cost, which depends on how many I order.
-
Have you designed the board yet? What size is the board? I assume 1 or 2 layers. I use ExpessPCB for small projects or design/etch my own with the old Winboard/Windraft or Eagle.
I think the Davis logger is a bargain.
ExpressPCB has a miniboard service that is fast and reasonable.
-
Have you designed the board yet? What size is the board? I assume 1 or 2 layers. I use ExpessPCB for small projects or design/etch my own with the old Winboard/Windraft or Eagle.
I think the Davis logger is a bargain.
ExpressPCB has a miniboard service that is fast and reasonable.
Designed by my board guy, single layer, and I vetted the traces twice against a couple of sources (the chip data sheet and another 3.3v-RS232 converter I tested).
I dunno what program he used. I have a quote in hand from Advanced Circuits for the board, and a BOM for Digi-key for the parts.
It's a little smaller in each direction than the Davis unit to allow for potting.
Having been through this process, I agree with you. The Davis logger with software is a bargain. They put a lot of thought into it, including the molded enclosure, the grab knob for removal, and even the hole drilled through the knob that you can hook with a wire or paper clip if you have to.
The mold for the potting probably cost thousands to make.
-
I have received the parts to produce 20 boards. 100 boards were ordered last Thursday from the board house, and are slated to ship from CO to CA today. I hope to receive the boards sometime later this week.
Upon receipt, I'll build up one unit for my immediate testing, and then a few more to distribute at cost to the original respondents for their testing. After that, we'll see about opening up to sales.
If you sent me an email or PM regarding this thread, I'll get back to you regarding cost and shipping as soon as I'm comfortable that the device functions properly in my testing.
-
I have received the parts to produce 20 boards. 100 boards were ordered last Thursday from the board house, and are slated to ship from CO to CA today. I hope to receive the boards sometime later this week.
Upon receipt, I'll build up one unit for my immediate testing, and then a few more to distribute at cost to the original respondents for their testing. After that, we'll see about opening up to sales.
If you sent me an email or PM regarding this thread, I'll get back to you regarding cost and shipping as soon as I'm comfortable that the device functions properly in my testing.
I am interested in looking at this option as my protype did not work - How much ball park are you looking at for cost of this unit?
Dennis
-
Chris, what advantages does this cable give us over the logger cable?
-
Chris, what advantages does this cable give us over the logger cable?
It will be cheaper, at the cost of not having archive memory.
I'm doing it mainly for my WeatherElement project, (just added another site (http://www.weatherelement.com/missioncollegeprep) this morning!), but, since there's always a clamor here for something cheaper than the WeatherLink logger, I'm planning on selling them to others as well.
-
I hope that I am one of the Lucky Members who will have an opportunity to purchase one of these units. I do not have the tools and was not blessed with the intelligence to work on such sophistication. Although I wish everyday I had what it took cause it is very intriguing. Thanks Again for all your member's help. I just hope I can be patient enough to wait. Please let me know how everything works out and after all the headaches and you will still want to sell one.
-
UPDATE:
After assembling a few boards that didn't work, I've traced the problem to transposed T and R lines from the header connector to the chip. A modified board works, so my board guy is working on a modified design. After I receive and test those, we should be good to go.
-
Thanks for the update. Appreciate your hard work!!
Dennis
-
Woo hoo! The rev 2 boards arrived yesterday, and I built up the first one for testing this morning. It works! I'll be building up a few more today to get the hang of assembly and try out one cable enhancement we added.
Unfortunately, this weekend is consumed with prep for a celebration on Sunday, so I won't start responding to those interested in beta testing until early next week.
-
Woo hoo! The rev 2 boards arrived yesterday, and I built up the first one for testing this morning. It works! I'll be building up a few more today to get the hang of assembly and try out one cable enhancement we added.
Unfortunately, this weekend is consumed with prep for a celebration on Sunday, so I won't start responding to those interested in beta testing until early next week.
Fantastic! \:D/ As soon as you figure out costs and shipping arrangements, please advise. Thanks again for all your hard work!!!
Dennis
-
Here's one installed in one of the VP2 consoles I use for development. It's attached to a 25' cable.
(http://www.sloweather.com/blog/2011/110818SerialboardREV2.jpg)
-
Sorry for the delay. I was occupied with our wedding anniversary last weekend. :)
I've hashed out a connector issue, and ordered cables and DB-9s. I plan on building up a few this weekend for the testers.
-
SLO Does that mean some of the less fortunate that lack the ability to build our own will soon have the opportunity to purchase a serial cable from you?
-
SLO Does that mean some of the less fortunate that lack the ability to build our own will soon have the opportunity to purchase a serial cable from you?
Yup! I have 9 built up to sell to testers.
(http://wx.sloweather.com/images/dsi-01.jpg)
I have PMs from 130db, DanITman, gulfcoast and vince7 indicating interest, so I have a few more to send out.
If you are interested, please post here and I'll PM you the ordering web page.
In order to maximize my efforts, please list what station type you have (Vantage Pro, Pro 2, Vue, or Envoy), and what software or hardware you are connecting to.
If you can test multiple programs, even better!
I'd like to get a variety of test sites before opening up sales to everyone.
-
A technical question for everyone purchasing one. What is the best method for safely removing the plug-in board from the console if it should be necessary without destroying the board? The Davis Weatherlinks have that little projection on their potting that can be grabbed to pull it out. I don't see anything like that on yours so you must have worked out another method in your testing to unplug it.
-
A technical question for everyone purchasing one. What is the best method for safely removing the plug-in board from the console if it should be necessary without destroying the board? The Davis Weatherlinks have that little projection on their potting that can be grabbed to pull it out. I don't see anything like that on yours so you must have worked out another method in your testing to unplug it.
The 3 pin right angle connector on the board works OK as a handle. That's how I pull them out after testing. Actually, it's best to plug the cable into the board and then the board into the expansion port, so the cable plugs helps as a handle.
It's not obvious in the picture, but the 3 pin header on the board is actually bent up about 30 degrees to match the cable exit angle to the notch in the console.
-
Wish I could use one with an Envoy, but I need data logging for sure.... my bad luck.
-
The first two were sent out USPS yesterday afternoon.
I still have a few for sale for testing.
-
Just sent a PM Hopefully we can help test.
Using VP2 and VVP to run WL and WD here so we can hopefully help with a few. Be interesting to see how it behaves.
-
Hi
I take my hat off to you Sloweather in developing this :)
certainly a great alternative to the more costly weatherlink for users who are not needing the history logging capability of weather link
I think this could really take off for you
you could also promote this on the WD forum as well maybe?
one question though, if a user had a new Davis station that was within warranty period, what does Davis say about that warrenty if your hardware is added to that Davis station? (sorry if this has already been covered before)
-
Hi
I take my hat off to you Sloweather in developing this :)
certainly a great alternative to the more costly weatherlink for users who are not needing the history logging capability of weather link
I think this could really take off for you
you could also promote this on the WD forum as well maybe?
one question though, if a user had a new Davis station that was within warranty period, what does Davis say about that warrenty if your hardware is added to that Davis station? (sorry if this has already been covered before)
Before someone launches into a diatribe that includes chapter and verse from the Magnusson-Moss Act, I will weigh in and suggest that if you use this and your station dies, you are SOL. I personally believe that unless it got certified through the "Empowered by Davis" (or similar) that they could make a case that it is an "unauthorized modification", therefore all warranties are null and void.
-
I guess as long as the end user is aware of possible warrenty issues, then go for it I say :)
-
Without the logger or some sort of backup I think the market is extremely limited for this sort of adapter.
-
Without the logger or some sort of backup I think the market is extremely limited for this sort of adapter.
Several famous folks stated that there was only a limited market for mainframe computers. Some of the same folks stated there was only a very small market for home computers.
Cost may be a significant factor.
Time will tell, of course.
-
How many mainframe computers are left? :)
-
How many mainframe computers are left? :)
A heck of a lot of them, in most major industries...
I deal with mainframe software engineers at our clients on a regular basis. It's always a treat trying to convince someone that fixed record files are not the wave of the future. ;-)
-
Right - and that is why Google uses a mainframe. :eek: I am actually a MF consultant and let me tell you, other than the big financial firms they are dying.
I stand by my original proposition that without memory the market is limited. But I am impressed with the adapter NTL.
-
How many mainframe computers are left? :)
Depends a lot on your definition. I was referring to a bunch of computing power housed in one location, and generally devoted to related tasks for a single business.
In my view, the TOP500 list consists of mainframes.
In my view, the mainframe class runs problems that "must run on a single machine" - where machine does not imply a single CPU.
Of course, if your definition is different, your count will be different.
I did not intend to start an argument.
-
The first two were sent out USPS yesterday afternoon.
I still have a few for sale for testing.
Unit arrived this afternoon =D> - installed this evening on my 6152 \:D/ Appears to be working well with Cumulus, however, not playing nice with my WD software. Looks like data is received (as the data light blinks on the control panel but the quality indicator stays red)
I am going to play with a few more configurations in WD and not giving up. I had a post in the WD forum regarding getting data out of the Davis unit to WD without using a datalogger but didn't get a lot of feedback yet.
Stay tuned. Thanks again SLO for all your hard work as well as the others who helped make this possible!!!
Dennis
-
re WD , make sure to have the Revb setting set
and of course the correct baud rate
in the weather station type setup
check those settings maybe
you can also set it to log data for debugging (to a file)
in setup, advanced/misc
-
Just to chime in on the thread.
My intention is to purchase one later. Just do not have the time right now to be among the first.
Bob
-
one other thing, because it does not have any history data capability, I guess it would not respond to requests for that
and so any software would need to make sure not set to get history data on start up?
(i.e. only live data)
-
Got the unit this afternoon, great job Chris! I hooked it up with the semi-dangerous method to a VPro2 console. Started Putty in serial mode, the TEST, VER and LOOP commands work on the XP machine.
Since it is hooked up to my XP machine via COM1 I tested with WeatherLink, no luck. I may need to tweak some more settings since it was setup for the USB logger that is plugged into the Envoy.
I downloaded Cumulus and it is working as expected, minus the archive data of course.
The station that feeds my website is a server version of linux on a laptop running wview with the Envoy and USB logger. I plan to load linux server on another laptop and test it with wview. I'll keep you posted...
David
-
one other thing, because it does not have any history data capability, I guess it would not respond to requests for that
and so any software would need to make sure not set to get history data on start up?
(i.e. only live data)
The only software i tested with was WeatherLink, and when I asked it to download the archive, it just posted that there wasn't any data available.
I spent so much time on research, design, revisions, and assembly, I wanted to get some out for others to test with. I just didn't have the time or resources to test with all of the software out there. It works great with my WeatherElement data hub, which was my main goal, so everything else is a bonus.
-
My earlier posting said I was short on time for now to be involved in your project, however things have changed quite a bit in the last few days, so if the offer is still open I'm ready to jump in.
Software is VWS, Win 7 64 bit and playing with Cumulus. Hardware is VP2.
By an odd quirk of fate I've ended up with 2 VP2 desktop stations and this will let me explore different weather software configurations on a different computer without running the risk of screwing up the data stream for my web site.
Bob
-
I just installed my VP2 wireless. Did not get the "Davis Dongle" as was not aware the station would not come with it or that I even needed it.
This cable GREATLY interests me and would be willing to pay to get one ASAP. I am a truck driver so I have a limited time window each time I get home to get things fixed, updated or installed on my weather station. When home I work diligently and you can imagine my surprise when after I spent a few hours installing my "pride and joy" VP2 in blazing 100°F heat with 89% humidity that all was for naught cause I needed a dongle to interface with the computer. Please feel free to contact me via email with specifics if any cables, boards are still available.
I am old, old school (8088 days etc, seriously), so do absolutely understand baud rate, parity etc. Only problem, as most know, is getting a 9 or 25 pin serial input on new equipment is becoming increasingly rare. My weather machine is running on a late model Toshiba laptop with no Serial inputs other than USB.
Toshiba specs: Intel I5 2.4MHz
3meg memory
Windows 7 Home Premium
USB only type serial inputs
Currently using a Prolific Serial-to-USB cable from LaCrosse WS-2308 to WD
I want to continue to interface with Weather Display (WD).
Obviously: Davis VP2 (6152) Wireless.
Couple of Questions:
1. I see there is no archiving on the cable. What exactly is the purpose of the archiving?
2. Since WD will creates its own archives, would this be an issue?
3. Can the output of the cable be placed through a serial-to-USB cable?
4. Is there any plans on eventually creating a similar cable with a USB input?
-
the lack of history data is no problem at all if you are running software 24/7 :)
-
I will be purchasing the Davis Vantage Vue in the future and would be very interested in the serial cable. My weather station software runs 24/7 so I don't need the history data stored in the logger. A solution that is less expensive than the Davis cable/logger combo would be great!
-
the lack of history data is no problem at all if you are running software 24/7 :)
Excellent, then a history logger is then not a big issue which even makes me more interested in this cable as my station indeed runs 24/7 on a dedicated PC (laptop).
-
the lack of history data is no problem at all if you are running software 24/7 :)
Excellent, then a history logger is then not a big issue which even makes me more interested in this cable as my station indeed runs 24/7 on a dedicated PC (laptop).
Well it could be a issue, If you experience a power outage or if the dedicated PC crashes.
-
Ditto to Avelvold ...on the power off... assuming your not running a laptop with a battery or UPS....
Chris,
My Cable arrived safely Friday, Thanks! Just waiting for the Spare Laptop to arrive so I can load a duplicate Weather Setup and get down to some serious testing.
Should be able to start playing sometime this coming Wednesday.
-
Well it could be a issue, If you experience a power outage or if the dedicated PC crashes.
If power goes out, it is a laptop so the internal battery should maintain up to 5 hours... also have ability to charge if no power.
As for the PC crashing... :???: Well what can be done but to reboot? :-)
-
re WD , make sure to have the Revb setting set
and of course the correct baud rate
in the weather station type setup
check those settings maybe
you can also set it to log data for debugging (to a file)
in setup, advanced/misc
Update -
The unit is working now with my WD software as well as Cumulus. \:D/ I really do prefer the WD (latest update 10.37Qb75) and it appears to be working - I like the archiving in WD and therefore, no need to have the logger function. It took a little while for WD to start seeing the data, but all appears to be reporting (Green quality and Data Indicators). I am also using XPORT to share the data between my station and the Cumulus as well as my WD software. One thing that was a little odd, the current temperature reporting from the station was 63.6 F in Cumulus, while on WD it was 63.7 F - the display indicates only 64 F so no help there.
Again, thanks again to SLO for his hard work as well as the other contributors for the pin-out investigation!
SLO - you got a winner! =D>
Dennis
-
Was just wondering if you are still issuing out the prototype for testing as would be interested... still.
-
Was just wondering if you are still issuing out the prototype for testing as would be interested... still.
Yes I still have a few available. Email sent with purchase link.
-
Again, thanks again to SLO for his hard work as well as the other contributors for the pin-out investigation!
SLO - you got a winner! =D>
Dennis
Thanks Dennis!
-
Thanks Slo...
Will pick this up later this week once we get the money up... should be Friday. Please reserve one for me.
Also, as an inquiry since did not get an answer previous... Can the Serial end be put through to a Serial to USB cable... using the Prolific driver?
-
Can the Serial end be put through to a Serial to USB cable
my 2 cents worth:
that should work OK
-
Thanks Slo...
Will pick this up later this week once we get the money up... should be Friday. Please reserve one for me.
I have lotsa parts. I can always make one. ;) But right now, I think I have 6 kitted up, ready to go.
Also, as an inquiry since did not get an answer previous... Can the Serial end be put through to a Serial to USB cable... using the Prolific driver?
Dunno for sure about the Prolific driver, but I use an ATEN GUC232A Serial-USB adapter for all of my testing of built units. No reason I know of a different one would not work.
-
Testing went well today, VVP ran all night serving data from the VP2 via the Serial Cable interface to Weatherlink 5.83 and Weather Display 10.37Q build 50.
Occasionally on restart Weather display would not autostart reading data as it would try to read the data logger. Brian from Weather Display replied:
you should be able to abort the data logger window
then go to control panel, data logger setup
and turn the switch off there
or change the setting direct in the wdisplay.ini file
[Extract the vp data at startup]
use=
Once I changed the INI file WD worked without a hitch.
change that to no
and save that settings file
(when WD is not running)
After Two days of testing I don't find anything (other than the lack of memory) that differs from the Davis logger vs Chris' new Serial prototype!
I even queried the console via weatherlink for the Alarm status and battery condition it worked perfectly. Well Done Chris!
-
Thanks for the detailed report BigD! I'll have to make a FAQ/Support page for the unit and include that info.
I sent out 3 yesterday, including 2 overseas, and one today to a dealer for critique. After K3JAE's purchase and any others this week, I'll close tester sales, review the comments and suggestions, and see about opening real sales.
-
Testing Update...
Ran my test station setup, Startwatch/VVP/WeatherLink 5.83/Weather Display 10.37Q Build 50 for the last two days, everything seemed fine except...
I Noticed the Monthly Rain and Yearly rain is not registering on the Weather Link weather bulletin? Rain amounts show up fine in the weather data when browsing the station just not on the bulletin screen.
Not sure why this is happening..but another forum member believes the WL data logger may have something to do with updating the bulletin, something for other testers to look out for maybe?
-
And now it is my turn to provide testing data.
Like some others I'm testing the product on a different computer than is used for my everyday weather needs.
This one is a homebuilt Win 7 64 bit system, without a serial port.
The USB to Serial port cable I'm using is from ATEN
http://www.aten-usa.com/?product&cat=795&Item=UC232A (http://www.aten-usa.com/?product&cat=795&Item=UC232A)
Now oddly enough neither the VWS and Cumulus software had any problems with station recognition or the data feed. However the Weatherlink software turned into being the odd man out.
Not really any sort of a big deal as the cable I'm using is now so old I no longer can recall when I purchased it. Also at the time of its purchase it was for the programming of a handheld police scanner as I was out of available serial ports. And it still works with the scanner and related software.
In going back to the WL software it sort of thinks something is there but can't quite resolve the problem, If I do the Autoscan routine it will stop on the right port for quite some time and then decide there isn't something there afterall, and if do the Test routine it runs all the way to the end of the timeout period before giving up.
I've tried 2 different USB ports as sometimes that can make a difference.
In any event the product is a winner and the above information is as much as anything to let others know that it is probably best to avoid that particular ATEN cable, which is still in production.
Bob
-
Slo...
Payment sent... now eagerly awaiting the item!!!!
-
After installing a long ago retired serial card (made by Lava) it now seems as though the Weatherlink software is the problem, not the cable.
With the serial card installed once again both Cumulus & VWS work with nary a problem, with Weatherlink (Version 5.93) still not wanting to cooperate.
I've unistalled WL and then reinstalled it via the Admin option, which only eliminated that as the problem. So best guess at this point is that the Davis product does not like to play along with 64 bit systems, or at least mine anyway.
On the outside chance it was version 5.93 that was the culprit I removed it and tried to install an older version of WL, however something somewhere is telling the install package that the newer one is still in place and it will not let me downgrade.
Most of this now is veering way off the original topic, but wanted to clear things up on ATEN cable being a potential problem with this product.
Bob
-
WL runs fine on WIn 7 32 AND 64 bit. At least on my machines.
-
WL runs fine on Win 7 32 AND 64 bit. At least on my machines.
And I figured someone would tell me that.
Did you do anything out of the ordinary when you installed WL, as to where the folders landed....or some other oddness rather than a straight install.
And are you on the latest version of WL or some previous one.
-
I'd like to thank all of the testers for their work and notes on the operation of the serial adapter I developed.
I'd also like to go on record as saying that if it doesn't work with WeatherLink, that's about the one program I can't try to support. Davis has their own interface and logger, and they are generally sold as a unit. I don't want to encourage the piracy or unauthorized use of WeatherLink by means of using this device, and thereby incur the wrath of Davis.
Chris
-
Slo...
Payment sent... now eagerly awaiting the item!!!!
It'll be shipped USPS tomorrow, Monday. Thanks!
-
WL runs fine on Win 7 32 AND 64 bit. At least on my machines.
And I figured someone would tell me that.
Did you do anything out of the ordinary when you installed WL, as to where the folders landed....or some other oddness rather than a straight install.
And are you on the latest version of WL or some previous one.
Tried it with 5.8.3 and 5.9.n Installs at root with Admin on Win 7 64 bit Home premium and pro. So nothing fancy.
-
Same install here.
Wonder if it has something to do that I'm trying to do the initial setup without using the Datalogger.
One would not think so, however when two other pieces of similar software function without a problem, and only this one is really expecting to see that particular piece of hardware/firmware as part of the overall initial setup perhaps there is some sort of special handshake initially involved among the three pieces of equipment that would make up the data train.
I'll have to carve out some time to move some hardware around and see if that changes the results. Although I'm not quite sure why I'm spending time on this problem as I rarely use WL for anything anyway and if needed it does work on the other system which has a VP2 console with the logger in place.
-
are you not able to set WL to the needed port type and data logger type and then set it to work with those settings?
(i.e skip the auto detect)?
-
No problem setting the port, and have verified the 4 different ports I've taken a run at are active and have the ability to receive data from both VWS & Cumulus. Ports tried at this point are 2,6,7,& 8.
The software tries hard to find the station, but eventually times out.
Then if I do use the auto detect routine the software will stop on port(s) where I've earlier confirmed the station to be, but will then just time out.
Parity & Bits in the port setup area are all at defaults, although I vaguely recall that at one time WL wanted to see something else, but I think that was back in the old Weather Monitor 2 days so I'm guessing those sort of oddities have long since been resolved.
As I said this is not any particularly big deal for me. Mostly it is just curiosity on why it won't work, when in theory it certainly should...hence my earlier comment about wondering if WL needs to see the Datalogger when it is first configured.
-
I've fired up WL and used .wlk files to simulate a connection. I do not think the logger has to be installed.
-
Did give me an idea to try, which was to copy the entire file structure from a known good install to this computer. Alas though the result was the same, which I guess was to be expected as no registery entries would come along for the ride.
-
Slo...
Payment sent... now eagerly awaiting the item!!!!
It'll be shipped USPS tomorrow, Monday. Thanks!
Got USPS notification of shipment. \:D/ ~watering at the mouth awaiting the new toy to arrive...~ :-&
-
For those still following along on this thread I guess I have an update.
After trying a dozen or so combinations and permutations and still not being able to access a com port when using WL...even though VWS, Cumulus & HWthr would work I cranked up my favorite search engine and hit the web.
After about 15 minutes I came across the below, which dates back to late 2008.
Hello
Weatherlink should work well with Windows Vista 32-bit. We have only recently tested the current Weatherlink version in a 64-bit environment. The Weatherlink software works well in Windows Vista 64-bit. However, this was done using a dual core 32-bit processor and chip set.
We are fairly confident that the Weatherlink software will not work in a true 64-bit environment, with a 64-bit processor and a 64-bit version of windows. Davis Instruments has no plans to create a 64-bit version of Weatherlink at this time.
Our conclusion is that the requests for such an upgrade to Weatherlink would not justify the cost of development. The real issue is the USB driver. You can download and install a 64-bit version of the driver at www.silabs.com and try it. NO guarantees though.
Rex Knapps
Davis Instruments Technical Support
And this information certainly fits the hardware/software I'm running, which is a 64 bit Intel CPU with an 8 thread capability, along with a board that supports a native 64 bit enviorment, with Win 7 holding it all together.
Now perhaps something in WL has changed since that information was published and it really does now support a full blown 64 bit system. If that is the case then I'm still endeavoring to figure out why mine won't.
Bob
-
Which version of W7? And have you tried to run WL in compatibility mode on your PC? LOTS of folks are running WL on W7.
-
I'm using Win 7 Home Premium in 64 bit mode which does not offer a compability mode....that is only available in the Pro version.
And from the information in what I picked up it isn't Win 7 64 bit that is the problem, it is the higher end 64 bit CPU's and the related hardware that goes with it.
I have another unit that I do have WL installed on which is a Win 7 unit which has a dual core CPU however it only runs in 32 bit mode and it runs quite well there.
-
I've run it on dual and quad core Intel and AMD in 64 bit procs and it works. I dunno...
-
is it a driver problem then for the connection?
(via the vantage.dll file)
-
The only part (well sort of) that does not work is for the software not being able to verify that there is a station on the other end of the cable, and then in turn be able to access the data feed. The port selection is not grayed out so that isn't the difficulty.
I've tried changing the port numbers within the OS to 1,2 6,7 & 8 in the event the software was being particularly picky about what it wants to see, which accomplished nothing except eliminating that as part of the problem.
I can pull over all the data from my other WL install and all the graphs come up and files can be found, so no problems there.
And I guess it could always be that I'm using a very old serial port add in card from the days when XP ruled the world. The drivers are current or at least 7 let them be installed with only a bit of a fuss, however I suspect there could still be something not quite right between a new high end system and an rather old piece of hardware put into it.
Although there were a few others pieces of software I did have to upgrade which plain would not work on a unit like this.
In any case this isn't a big deal, more of an exercise in trying to figure out why something doesn't perform quite right. So perhaps the next time Newegg runs a promo on new serial cards I'll pull out some plastic.
Bob
-
maybe try getting hold of a USB to serial driver and install and use that?
-
Chris;
Received the interface today, plugged it in, set up WD and before I could even reboot Weather Display data began coming in. \:D/
So obviously the anticipated issues either with the console fighting with WD or itself, never reeared its head and absolutely nothing went bonkers and was pulling data well inside 5 minutes of connection and set-up in WD.
The entire process of installing the module, setting WD up for the Davis was absolutely painless and was completed, as stated above in under 5 minutes. That made me extremely happy!!! All data lights green, steadily flashing where supposed to be and reading almost simultaneously as soon as wind changes WD is quick to display it.
Just to update on setup:
Toshiba Satellite laptop with a
Intel dual core 2.00GHz processor
3Gig of memory
Running Weather Display software v73 (I just noticed v75 is out and will update later this date)
Interfaced via a PROLIFIC SERIAL-to-USB driver
Running on COM4 8-N-1
Baud 19200
Only issue I see right now is the VP2 station is reporting an outside humidity of 64% yet WD is showing 66% therefore showing online as 66%. I am not sure why that is the case as all other reading are mirror images of the Davis console. Any thoughts, ideas on that? 2% is not a real major issue so will not lose sleep over it but still something that I noticed.
-
check to se if you have a humidity offset set in WD
-
WL runs fine on WIn 7 32 AND 64 bit. At least on my machines.
In general or with Chris's homemade cable? I was not able to get WL to work with his cable.
-Dan
-
check to se if you have a humidity offset set in WD
Good call Brian... that was it as I forgot I had to offset for the POS LaCrosse station.
Another interesting development... After I rebooted the machine, when WD loaded, I saw the blue DataLogger box come up then just hung for a bit then went away... Then WD hung with no update/refresh from the WDISPLAY.ini and no data received.
I rebooted again and "Aborted" the DataLogger retrieval and WD loaded and ran normally then brought data. QUESTION: Should I still have the DataLogger item checked? If so which one? The only option for station type is VP2 /w DataLogger, when in reality I do not have a DataLogger, with memory that is. What appears to be happening is that WD is attempting to pull info from the DataLogger memory, cannot find anything then just finally hangs. This seems to be a bit of a problem. Or is there a setting to bypass the DataLogger info retrieval? I have since checked the "older" DataLogger option in the hopes it will bypass memory retrieval.
DataLogger issue resolved... I needed to turn off the DataLogger setup in WD under Control Panel.
-
make sure the switch is off in control panel, data logger setup
-
I have tried to get Chris's serial interface to work on a startech pci to serial port with the correct drivers. The current serial ports work fine with my vp2pro in win7 home premium environment. I haven't had any luck with WL 5.8.2 software. Has anyone had any success in vws,cumulus or virtualvp. I would like to get this thing working.
Update: I just hooked it up again with no luck in vws or in virtualvp.
2nd update: I'm still not able to run in older version of vvp or cumuls.
Running the comports just the way they are suppose to be. 19,200,8,1,no flow control.
Thanks,
Tim
-
I have tried to get Chris's serial interface to work on a startech pci to serial port with the correct drivers. The current serial ports work fine with my vp2pro in win7 home premium environment. I haven't had any luck with WL 5.8.2 software. Has anyone had any success in vws,cumulus or virtualvp. I would like to get this thing working.
Update: I just hooked it up again with no luck in vws or in virtualvp.
Thanks,
Tim
Hey Tweatherman,
I had the prototype working with VirtualVP, I ran WeatherLink and Weather Display off the feed BUT I ran it on a old IBM 386 laptop under XP with the OEM Serial port!
I did adjust port specs per instructions (19200 baud No flow Control etc..)
I also used the older version of VVP that mirrors the data to disk so it acts like a logger and weatherlink reads the VVP archive as if it's a data logger (cool).
-
I'm interested in one of the cables, too.
-
Just updating after having the cable installed now 3+ days.
Very easy... No problems, WD playing very nicely with the information being received. Weather Display has not locked up and Data appears to be very accurate and constantly incoming in with no packet losses.
Definitely a winner and definitely worth marketing as an alternate to the gouging cost of Davis' dongle. Very happy with the results.
Again, as a reminder of my setup (updated a bit):
Toshiba Satellite laptop with a
Intel dual core 2.00GHz processor
3Gig of memory
Now running Weather Display software v10.37Q-b78
Interfaced via a PROLIFIC SERIAL-to-USB driver
Running on COM4 8-N-1
Baud rate: 19200
-
EDIT: I'm going to update this post as new info comes in, rather than post replies.
UPDATE:
OK, it's been a few weeks, and based on user comments, I've compiled a list of software and compatibility for the Serial Interface For Davis Weather Stations
Please review this list and post, PM, or email me any corrections or additions.
Everyone seems to be testing on VP2s, I couldn't find any mention of Vues or Envoys. One did test on an original VP which didn't work, perhaps due to problems with the VP itself.
Cumulus- Works OK
VWS- Works OK
Weather Display- Works OK, may need to turn off Data Logger in the WD Control Panel.
WeatherLink- May or may not work. No universal work-around, and not supported by me due to WeatherLink being a Davis product sold with their logger.
Virtual VP- Works OK.
VPLive- Doesn't work.
PROLIFIC SERIAL-to-USB driver- Works OK
ATEN GUC232 Serial-USB- Works OK
Ubuntu 11.04 server and wview 5.19.0. on a laptop with only USB ports.
Two lines in the wview source code had to be modified and recompiled for the program to generate historical charts. Without the recompile it would only generate the current condition graphics, due to the lack of archive memory. The program maintainer plans to update the package to add an option for "Davis Logger" or "Other" data cable.
One user with Win 7 Home Premium/Startech PCI Express Serial card has not been able to get either of 2 of these to work, even though the Davis logger works fine.
It doesn't yet work with my WeatherElement data hub. I'll be working with the programmers and maybe PORTMON to figure out why.
EDIT: See an update post for the reason, and how I fixed it. It now works with my hardware hub, and the fix will be applied to all future units.
I also verified that the Davis logger caused the console to beep 3 times on booting, my interface beeps only 3 times.
UPDATE 3 October 2011
I just successfully used the DSI-01 serial interface to update a VP2 cabled console from 1.7 firmware to 1.9 firmware.
Any other input is appreciated, regarding installation, verification of console beeps, etc.
Chris
-
Chris, I'm using a original vantagepro here on my end.
Tim
-
You can add Linux and wview to the list.
Details:
Ubuntu 11.04 server
wview 5.19.0
Toshiba Satellite 1115 laptop, 1.5GHz Mobile Celeron, 512MB RAM with only USB ports
BAFO BF-810 USB to Serial (DB-9) Adapter - Linux loads the native Prolific PL2303 driver.
http://www.bafo.com/products_bf-810_F.asp (http://www.bafo.com/products_bf-810_F.asp)
Davis VPro2+ with Console 6312
Two lines in the wview source code had to be modified and recompiled for the program to generate historical charts. Without the recompile it would only generate the current condition graphics, due to the lack of archive memory. The program maintainer plans to update the package to add an option for "Davis Logger" or "Other" data cable.
The setup works well with Cumulus on an XP desktop with either direct serial or the USB to Serial adapter. I had to install the driver that came with the USB to Serial adapter on XP, Prolific version 2.0.13.130.
No luck with WeatherLink on XP but it does not matter to me.
Good Job SLOweather! =D>
David
-
The interface wouldn't work with my own WeatherElement data hub, which was the main reason I developed it. I did some thinking about it and realized that there was one more difference between my unit and the Davis one. The blue Davis DB9 connector has some jumpers in it across some of the handshaking pins. The software programs that work apparently don't read those pins.
I added one jumper to one of my connectors this morning, and now my WeatherElement hub works.
It's seems like I have heard from 2 testers that they had trouble with VP1s using my interface. I'll be sending out a couple of modified connectors to them to see if that fixed it.
Has anyone gotten it to work with a VP1?
-
I had a question from a user about extending the cable. It can be done with a straight-through 4 pin modular male/female telephone extension cable. Radio Shack used to carry them, but I couldn't find one on their web site.
I can also make longer ones, and will probably make that an option when I open official sales.
-
The interface wouldn't work with my own WeatherElement data hub, which was the main reason I developed it. I did some thinking about it and realized that there was one more difference between my unit and the Davis one. The blue Davis DB9 connector has some jumpers in it across some of the handshaking pins. The software programs that work apparently don't read those pins.
I added one jumper to one of my connectors this morning, and now my WeatherElement hub works.
Back in the "olden days" when RS232 was the only thing going, this was a common symptom. The cure was well known: connect DTR, DSR, DCD, and CTS together. That turns out to be pins 4, 6, 8, and 20 on a 25-pin connector; or 1, 4, 6, and 8 on a 9-pin connector.
-
Back in the "olden days" when RS232 was the only thing going, this was a common symptom. The cure was well known: connect DTR, DSR, DCD, and CTS together. That turns out to be pins 4, 6, 8, and 20 on a 25-pin connector; or 1, 4, 6, and 8 on a 9-pin connector.
Yeah, I spent a lot of time working with RS-232,422, and 485 at my last job. That's what made me think about handshaking jumpers. 7-8 are the pins that made it work. Davis also has 1-4-6 jumpered, plus connected to the yellow wire from the console. Dunno what's up with that. There's about a volt between 1 and 5 when the console is fired up.
Back in the dark ages of the 80s, we had a buried 5000' 2 pair RS-485 circuit at work. During those rare central coast thunderstorms, the line driver or receiver chips would regularly blow out from induced EMF. I know one strike was 8 miles away because I saw it hit, and when I went back in the building, comms were down. Before I finally figured out how to build my own suppressors with Tranzorbs, I just kept tubes of replacement chips around.
-
Yeah, some of that depends on which end is the "data terminal" and which end is the "modem".
-
Cumulus- Works OK
I've been using the cable for some time now and for some reason Cumulus will often give me an error 32701 and I have to restart cumulus to make it work. It works fine on VWS and Weather Display but I can't seem to get Cumulus to run 24 hrs without throwing an error.
-Dan
-
UPDATE 3 October 2011
I just successfully used the DSI-01 serial interface to update a VP2 cabled console from 1.7 firmware to 1.9 firmware.
-
Chris, do you have any more of the adapters for the Vue still available? Do I understand correctly that people are having good luck using your serial adapter with a serial to usb adapter cable and Cumulus people are finding "it just works"? thanks.
Has anybody considered packaging the serial to usb along with this mechanical adapter?
-
Chris, do you have any more of the adapters for the Vue still available? Do I understand correctly that people are having good luck using your serial adapter with a serial to usb adapter cable and Cumulus people are finding "it just works"? thanks.
Yes and yes. :) I just sent a PM with the ordering link if you are interested.
For anyone else reading and interested, I have lots of blank boards, enough that I'll be surprised (and happy) if I ever run out. All I need to do is have enough other parts on-hand (which I do) to build them up for stock or to order.
Has anybody considered packaging the serial to usb along with this mechanical adapter?
Nope. Well, not me anyway. That would just add a layer of complexity to my process. I should add a link or 2 for these to the sales page when I officially launch. I'll talk to the dealer who will probably sell these for me and see if he'd be interested.
Chris
-
OK, Chris, I understand. Can you provide a link to a 3.3v serial to usb adapter that is known to work? this should then give a 2 device adaption to usb, yes?
something that kind of bugs me that Davis went proprietary on. i almost didn't order the Davis vue because of this.
Paul
-
Gents,
This is a little off the topic.
It's way off topic. Please start an entirely new topic with your question.
-
I need help. I got my cable in and can not get it to work. The vp2 console i am using was set up for serial and working fine. One thing i noticed is i do not see the baud rate set up on the console, though it is set up for 19200 with the other davis cable. I have the data logger switched turned off on the control panel. The green data light is flashing but no quality or data shows. What can i do next? I am using wd.
-
Just a follow up i loaded up on cumulous and it is working fine. Started right up and varified com port 1 ok.
-
A follow up to the follow up lol. It is now working with wd, i do not know why but after working with cumulous i went back to wd and it loaded fine. =D> =D> =D>
-
I shut down wd and restarted and it came back just fine, however i have one question still on my brain and when i go into setup on the console i still do not see the baud rate setting. I know you do not get that setting if using usb cable, no baud rate needed, but how would you set it if it is not showing? Do any of you with the vp2 show the baud rate setting?
-
Just remembered the default for davis is 19200 so no need to set it as long as the software is set up to automatically use the default setting. I guess the only time you need the settings is if your serial would not support 19200 for some reason or another or the software would not allow it.
-
Really cool to see such enthusiasm!
-
Chris,
Just to let you know the connector you sent me works great with my original vp station.
Thanks,
Tim
-
Curiosity has me wondering how this might work with a 6318 console. All the extra memory here is in the console itself so I'm left wondering what the logger does beyond providing an interface to the PC. Could it be that you can transfer archive data from a 6318 to a PC without the logger? Speculation I know. If I can make time - hopefully sometime soon - and steel myself to risk the experiment maybe I'll take a look.
-
Could it be that you can transfer archive data from a 6318 to a PC without the logger?
Now that would be interesting! But presumably wouldn't the data be structured differently from archival data structure of the regular loggers? So maybe you would still need some sort of import program to bring the data into WL?
-
Now that would be interesting! But presumably wouldn't the data be structured differently from archival data structure of the regular loggers? So maybe you would still need some sort of import program to bring the data into WL?
Well yes but that would be the WDTU software that comes with the 6318 console. If you wanted to pass the data into WL then you would need to use the WL export facility of WDTU. Of course the 6318 is no good for real-time (Loop) data - it doesn't have that capability(unless you classify archive data with a 10sec interval, which the 6318 can do, as real-time).
I guess what I was really thinking was that with a non-6318 VP2 console then you need the logger if want any sort of archive storage capability. But even this benefit probably doesn't apply to a 6318 console.
-
Just to let you know the cable i got from you has been working great, no problems at all. The only thing i found out was when i was messing with my wd program and did a restart it would not connect and i found i had to have the restart com port checked in the com port settings and it loads fine after a restart.
-
which version/build of WD is that with?
-
build 84
-
I have done some work recently on the VP history data routine...so I would use the latest version...
-
Can I also get the link to the sales page for this adapter?
Tia
David
-
I sent you a PM, but, just want to say, I think there is a market out for these. Buying the Davis Vue and the software were just too far out of my comfort zone concerning price. I don't need a logger, I just want to be able to see if it has rained. LOL
So, yes, please, send me a link to purchase....oh, are you going to do the longer cable?
Ginny
-
I agree that there is probably a market for these. I'm reluctant to make too broad of an announcement until I get some stock made up, lest it be TOO popular. :)
I do have longer cables made up, just not a way to purchase them yet. I'll include one in your order.
-
Just got mine today. So far, it works great in VP-1 into WIN7 Ultimate with VWS and Cumulus.
Gotta say thanks!
-
Just a quick question...
I have had absolutely ZERO issues with this cable for now almost 2 months.
My only question is if and when a new firmware update is sent out by Davis will this cable be able to flash the ROM without any issues via the computer connection?
I certainly do not want to buy anything from Davis just so I can update firmware. Would be interested if this cable will be able to do this.
-
Hey SLOweather, just got a Davis Vantage Vue for Christmas and was dismayed at the price of the weatherlink adaptor. Would love to get some more info on youor custom solution that is so popular!
-
New guy late to the party. Are any of these still available?
Don Stephens
-
New guy late to the party. Are any of these still available?
Don Stephens
No. Check out forum member belfryboy for a clone logger.
-
Thanks.
-
SLOweather, is the cabled interface still available for order? I'm still thinking of buying an Envoy, and I'm going to need one for it.
-
I do have these available in both serial and USB version, PM me for details.
-
Sorry, the question was misdirected it seems. Alright, thanks, I'll contact you if I have a device.
-
Yeah, best if you go with Belfryboy. The fact that you said
I'm still thinking of buying an Envoy, and I'm going to need one for it.
says my interface won't be compatible with it, being newer firmware/hardware.
-
I do have these available in both serial and USB version, PM me for details.
Belfryboy, is your offer still valid? I've sent you a PM a few days ago.
-
PM sent
-
Maybe some of you might have some experience. I'm deciding over which cable to get, serial or USB. Serial might be better for me as I'll prolly need to tie the Envoy to a router to pass the signals into my wifi network (the ideal placement of the device is pretty far from my home server). I can hook it up to my TP-Link MR3020 (a very small wifi device capable of running OpenWRT) for example on its builtin serial header and install a serial-ip driver. Does the serial version have TTL signals, or PC-compatible +-12V one? Anyone ever did something similar?
-
Hi
If you buy the serial version, you can always use a usb to serial converter if you ever need to... (But use a good one based on ftdi chipset)
You could also convert rs232 to rs485 for long cable runs.
With the usb version, you can't convert usb back to serial, so are more limited IMHO.
The voltage will be standard rs232, like a PC.
-
Yeah, thanks. Though I think it's serial over USB, just like the original Davis one.
-
Someone let me know if I should start a new thread.
I have a VP2 with a 6152C and not going to pay Davis anything. I've been looking over ALL of these posts and have all this knowledge but no mental picture of where to start.
Here's what I have so far. I had this FT232RL FTDI Mini USB to TTL Serial Converter Adapter https://tinyurl.com/yb9g7rpp (https://tinyurl.com/yb9g7rpp) laying around and according Dekay's instructions https://tinyurl.com/yc5rdvyv (https://tinyurl.com/yc5rdvyv), connected TX to RX pins (IE: VP2-TXD0 to USB RXI & VP2-TXD0 to USB RXD0 to TXO).
I could not connect the GND's together as it would cause some type of power issue with the VP2. I also did not know what to do with the VP2 #18 (DC in) since I couldn't locate a reason nor what voltage.
So, here I am...Hyperterm'd up and nowhere to go! :shock:
Yea, I don't let the smoke outta-da-box!
Any suggestions or guidance would be GREAT!
-
IDK
I have been trying to get data out of a logger without having all the original connection parts (sort of wanted the data storage on it) but no luck so far.
https://www.wxforum.net/index.php?topic=25351.0
I had a look at Dekay's blog. Wiring looked easy (I have lots of connector hardware kicking around) but I never looked at the software end of it.
You are talking to it through Terminal? I guess load up some software on a PC or RPi or something and see if it does anything.
-
davidmc36,
Yea, using HyperTerm (19,200/8N0).
Speaking on the Dekay's blog, did you connect anything to:
VP2
#18 (DC in)
#16 to #15
#14 to #13
and #15 to USB adapter GND?
When I connect that #15 to my USB adapter then plug my USB cable into my PC, I get some (not good) power issues on the VP2.
-
I have connected nothing to the console pins.
I figured it would be basically easy and may give it a shot at some point but have been trying to get the Davis Serial Logger working.
-
Update,
As mentioned above, I connected the TX & RX on VP2 and USB to Serial adapter (IE: VP2 Tx to Adapter Rx and VP2 Rx to Adapter Tx) and when I started up Cumulus it states "Connected to station" but it's not pulling data. That's a start but, what I'm wondering is, the "connected" message due to Cumulus seeing the connection to the adapter or actually seeing connection to the VP2?
For me, WIN10 "Device Mangler" is seeing the Serial to USB adapter as being on COM5 which I have that setup in Cumulus and HyperTerm. In HyperTerm (19,200 / 8N0) it shows "connected" but I am not getting any type of VP2 response (IE: TEST, VER, STRMON).
If I connect the GND from the VP2 to the Serial Adapter then I get some type of power issue on the VP2 so...yea, like "crossing the streams!"
Update to the Update on the particular HiLetGo SERIAL to USB adapter that I'm chose, "This adapter is not genuine FTDI chip because it's based on so cheap a price, so it will be automatically bricked by the latest FTDI drivers in Windows." well, well...you get what you pay for! :shock:
The fix is to ensure that you use the older version of the FTDI drivers (2.8.3) on windows or use only with Linux or OS X. If you've already bricked it, please follow these instructions at below link (requires a Debian based Linux) **DEAD LINK** http://www.minipwner.com/index.php/unbrickftdi000
Drivers/Support: http://www.ftdichip.com/FTDrivers.htm
Besides giving me grief for my cheap purchase does anyone have suggestions, thoughts?
-
Just a question to make sure I didn't miss something but, unless I want to archive or look at historical data, then I should be able to connect my Serial to USB adapter (https://tinyurl.com/yb9g7rpp) to the Tx & Rx pins on my AP2 and I "should" get some data in Cumulus, correct? Cause I AIN'T GITIN' NUTTIN!! :roll:
I'm just trying to put the pieces together and this is obviously not my area on expertise. #-o
I am seeing traffic via the Tx & Rx lights on my Serial/USB adapter & the adapter looks good in WIN10 Device Manager. ](*,)