Well, USB-COM converter I've bought on e-bay. Like this: http://cgi.ebay.com/FTDI-USB-RS232-TTL-Converter-FT232-FT232RL-3-3V-/120648223859?pt=Vintage_Electronics_R2&hash=item1c1731cc73
$15. Good price compared to DataLogger :)
Windows 7 x64, driver for virtual COM port - no problem.
I use this terminal program: http://realterm.sourceforge.net/rss.xml
Very customizable, I like it best of all I've seen.
And now I've flashed new 2.14 firmware and tested WeatherView32 software - everything works SUPERB! YESSS!
One thing I haven't bothered looking in to yet is seeing how much data if any the console buffers.
Thank you DeKay!! I also have success using your discovery. I have my vue up and running on VWS with this setup. Works great!!!
I started out with a USB weatherlink and then "upgraded" to the WLIP "logger". Needless to say they both shipped with the exact same software CD, which of course I no longer have the need for.
Here is the Envoy manual (http://www.davisnet.com/product_documents/weather/manuals/envoy_manual.pdf). Looks to me that the same solution applies, looking at Page 4 of the document.
af4ex: It looks like Digikey has a few headers in stock now (6) for the outrageous price of $5.13. Look here (http://search.digikey.com/scripts/DkSearch/dksus.dll?WT.z_header=search_go&lang=en&site=us&keywords=ESQT-110-02-G-D-760-ND&x=0&y=0).
I'm not sure what an Envoy is,
@mmorris
> If you got WeatherLink data logger all ready you could integrate that into
> sending that data wireless also,...
I don't plan on buying a WeatherLink. That was the motivation for building this replacement. I could write my own logger I guess. Right now I'm letting APRS/CWOP do my logging. I suppose that will change as I learn more about these personal weather stations.
:grin:
Says here the Wireless Weather Envoy has been discontinued. Is there a replacment?
http://www.davisnet.com/weather/products/weather_product.asp?pnum=06314
In the other hand, another doubt is, what are TxD1 and RxD1 (in the console port) for? Can we use them for something special.
Yes, it's correct, but I should have clarified more that the labels 'RXD0' and TXD0' refer to the _destination_ pins on the 20-pin connector.
I don't know what they are for. They don't spit out anything during a console reset, and they don't respond like TxD0 and RxD0 do. It could be they are there for factory testing and that there is some hidden command to wake it up. Or maybe they were brought out to the expansion port "just in case" but never used. It would probably take a deep dive into the firmware to figure it out. Nothing I'd be interested in, because all the good stuff you'd ever need is already on TxD0 / RxD0.
Using them for "something special" would mean you'd have to change the firmware to make it happen. Not impossible, but pretty hard without the actual Davis code.
@mmorrisI have a weatherlink with serial output. As I understand it you are eliminating the weatherlink from the equation, which is cool. However, I'd like to retain it for its logging capabilities should the WXPC go down.
> If you got WeatherLink data logger all ready you could integrate that into
> sending that data wireless also,...
I don't plan on buying a WeatherLink. That was the motivation for building this replacement. I could write my own logger I guess. Right now I'm letting APRS/CWOP do my logging. I suppose that will change as I learn more about these personal weather stations.
:grin:
@SpartanWX
> Methinks that they're not going to be to keen on me slapping a weather station in the side yard.
> I plan on finding a surrogate house in the area to foster my setup.
You face a problem common to ham radio operators, who are similarly restricted on setting up antennas. (But we're pretty good at constructing antennas that look like flag poles, or out of nearly invisible magnet wire) :grin:
Digi makes higher power XBee chips, which SparkFun says have a range "up to 15 miles". But they don't mention you'd have to set up an outdoor antenna system to get that range. It's still only 100 milliwatts, less than those 1/2 watt Citizen Service walkie talkies.
http://www.sparkfun.com/products/9085
A more practical solution would be to pipe the data over the internet. It's only 19.2K baud so a regular high-speed cable should have the bandwidth. There's probably remote logging software available to do that or you could write your own. Conceptually very simple, just set up a two-way socket (IP address + port number) and read and write to it like a file.
Or if you would settle for 'near real-time' performance, just spool the data to a file, and do a file transfer several times a day.
I finally got Cumulus working, so have switched to that from WUHU. It seems to have some logging capabilities. At some point though, I'll start writing my own software, once I figure out what I want to do with the data.
John/af4ex
It's actually small enough to squeeze into the plugin compartment at the bottom (which I'm guessing is comparable to the VP2), but that might cut the range down a bit. Haven't tried it yet. (Get an XBee with the "chip antenna" (same price) for the console side, which has a smaller footprint and would be easier to cram into the plugin compartment.)
@SpartanWXSo if I understand correctly...
> I need to transmit the data from the serial connection on the logger at the console, wirelessly to the serial connection on a PC
> which will be connected to the internet.
In that case, the homemade XBee wireless serial interface (as described in this post) would be a good (and inexpensive) solution. No different than a wired serial connection once it is initially configured. The 1-milliwatt model should easily transmit from one room to any other in a normal-sized house, i.e., from the console in some open area, to a computer tucked away in a closet somewhere etc.
I've got my VUE console in the family room and have strapped the XBee adapter to the rear stand, out of sight. It's actually small enough to squeeze into the plugin compartment at the bottom (which I'm guessing is comparable to the VP2), but that might cut the range down a bit. Haven't tried it yet. (Get an XBee with the "chip antenna" (same price) for the console side, which has a smaller footprint and would be easier to cram into the plugin compartment.)
Now the console-side transceiver. Good news: it will be cheaper because we'll build it from inexpensive parts, plus another $22 XBee Modem. But it will of course be more difficult to put together. Don't attempt this unless you have a fine-tipped soldering iron and some building experience.
We'll use the SparkFun XBee breakout board ($3) and a pair of 2mm header sockets ($1 each) which need to be soldered to the breakout board for mounting the XBee transceiver ($22, same as above). Buy an extra header socket, which will be cut up to make the console connector cable (details in previous Phase I posting).
http://www.sparkfun.com/products/8276
http://www.sparkfun.com/products/10030
You'll also need some 0.1" spacing PC board (PCB) and a six-pin 0.1" header for the console connector. I had some of these pieces laying around, but you can get them at SparkFun or Radio Shack. Typically you buy oversized pieces and cut them to size. Shouldn't cost more than a few bucks I would guess.
@SpartanWXAt the console side, I already have the WeatherLink datalogger (serial version, currently going to WXPC via Serial->USB converter). Wouldn't I just plug the XBee Explorer Serial into the serial output of the WeathLink datalogger (after I configure it of course)?
> So if I understand correctly.
You got WXPC parts correctly (basically a USB XBee dongle), but wrong on the console side. Reread page 2 of this post:QuoteNow the console-side transceiver. Good news: it will be cheaper because we'll build it from inexpensive parts, plus another $22 XBee Modem. But it will of course be more difficult to put together. Don't attempt this unless you have a fine-tipped soldering iron and some building experience.
We'll use the SparkFun XBee breakout board ($3) and a pair of 2mm header sockets ($1 each) which need to be soldered to the breakout board for mounting the XBee transceiver ($22, same as above). Buy an extra header socket, which will be cut up to make the console connector cable (details in previous Phase I posting).
http://www.sparkfun.com/products/8276
http://www.sparkfun.com/products/10030
You'll also need some 0.1" spacing PC board (PCB) and a six-pin 0.1" header for the console connector. I had some of these pieces laying around, but you can get them at SparkFun or Radio Shack. Typically you buy oversized pieces and cut them to size. Shouldn't cost more than a few bucks I would guess.
So you will have to build an ad-hoc XBee dongle on the console side to plug into the 20-pin connector. You'll need some PC Board and header strips, with 0.1" inch space holes too, which you'll cut to fit. (Radio Shack sells this for a few bucks).
Mostly importantly, you'll need a fine-tipped soldering iron and some experience with circuitry like this. Novices typically apply too much heat and melt the plastic or too much solder, which bridges and shorts everything out.
That said, it is a rather simple circuit. Only four wires to jumper on the back of the PCB. The trickiest part is making those 2mm plugs. (Or plunk down $15 to get the Samtec 2x10 header receptacle, which will make it a bit easier to plug into the console).
Forget about transmitting 15 miles. A bare wire antenna at 100mw will only get out a thousand feet or so. You'll need an external antenna system with very high-gain antennas (30dB or so, and very precisely aimed) to get out 15 miles. And it would probably only work in fair weather, rain/snow/wind would cause some serious attenuation (and that's probably exactly the kind of rotten weather you'd be interested in monitoring). :-|
Hope that helps,
John/af4ex
At the console side, I already have the WeatherLink datalogger (serial version, currently going to WXPC via Serial->USB converter). Wouldn't I just plug the XBee Explorer Serial into the serial output of the WeathLink datalogger (after I configure it of course)?
I've got a soldering iron... but it's the monster pistol-grip melts stuff variety.
For someone who wants to learn how to solder, the following would be a good investment:
http://store.cs-sales.net/nelsokitwist.html
Includes soldering iron, tools, a practice project, and excellent instructions.
DeKay, any words of wisdom for Mr. SpartanWX before he goes and orders all of these parts? What about levels? Does WL use standard RS-232 voltages (+/- 15v etc)?
Well, SpartanWX, we think it should work, but no guarantee until you try it.DeKay, any words of wisdom for Mr. SpartanWX before he goes and orders all of these parts? What about levels? Does WL use standard RS-232 voltages (+/- 15v etc)?
WL is designed to connect directly to a standard serial port, so it must use standard RS-232 voltages (if there is such a thing). I was about to add what you followed up with, af4ex. Just pay attention to the gender of your connectors, and buy a null modem adapter whether you need one or not. In my experience, you will always need one when you don't have one, and vice versa.
I like where this thread is going. More people seem to be catching the bug and giving this a shot.
Well, SpartanWX, we think it should work, but no guarantee until you try it.DeKay, any words of wisdom for Mr. SpartanWX before he goes and orders all of these parts? What about levels? Does WL use standard RS-232 voltages (+/- 15v etc)?
WL is designed to connect directly to a standard serial port, so it must use standard RS-232 voltages (if there is such a thing). I was about to add what you followed up with, af4ex. Just pay attention to the gender of your connectors, and buy a null modem adapter whether you need one or not. In my experience, you will always need one when you don't have one, and vice versa.
I like where this thread is going. More people seem to be catching the bug and giving this a shot.
Go forth and connect, wirelessly!
:grin:
Cost is partly the culprit. I balked at paying $180 for WeatherLink features I don't need, which would only get me a serial connect, Still more $$$ to get wireless. So for less than $100 I get both. (I still think Davis should provide "low cost" solutions for simple serial connections).
Cost is partly the culprit. I balked at paying $180 for WeatherLink features I don't need, which would only get me a serial connectNo, as above, I understand your motivation for wanting to bypass the Davis logger, but it was specifically the wireless part of your set-up that I was commenting on.
If you look at my Cumulus web page I seem to be getting the full spectrum of weather information, just using my simple serial link. What am I missing? www.qsl.net/af4ex/wx Also I am transmitting my info to APRS/CWOP. Again, they're getting all the data they need. http://www.findu.com/cgi-bin/wxpage.cgi?call=AF4EX [Ironically, that data glitch you see on 12 March was caused by the flakey WiFi in my laptop. The XBee's haven't dropped a single bit. I now use CAT-5, to hook the the laptop to the Internet]
But weather is only one of my interests. I have other environmental sensors that I want to monitor. I have a VLF antenna in my back yard that I use for detecting whistlers and other kinds of electromagnetic pulse signals. Also interested in geomagnetism, solar physics and "climate change" issues, so I'm developing my own generic data channels for this purpose. So eventually will have a sensor farm, and a web page, for detecting and analyzing interesting signals from nature.
Interestingly (to me, any way...) is that I've been doing a bunch of Python work lately so I'm itching to try this on a PC. Can't see what it would not work.
@Bushman
> I think you are going to need some extra work to get it to interface.
Are you talking about the WL/WiFi interface, or XBee? For XBee it should be as simple as installing the Linux drivers for the FTDI serial2USB chip.
>... I've been doing a bunch of Python work lately so I'm itching to try this
> on a PC.
The author claims weewx is "unix only" and hasn't been ported to Windows yet. Might not be a trivial port.
"Unix only. I haven't tried porting to Microsoft Windows, but given the portability of Python it is likely to be a large, but not mammoth, project."
Probably not, but I think it's a universal solution, equivalent to a serial connection. How would you share that over WiFi?Well I was just assuming using a standard serial/WiFi device server like:
I don't really know how WeatherLink connects to applications using WiFi. Doesn't that lock you into WeatherLink? How do you get the serial connection on the remote-side computer?Just run standard Redirector software that presents the serial data stream to the application on a virtual com port.
I have my console downstairs, but I can connect to it upstairs wirelessly as COM5 through the USB port. How does that work with your WL/WiFi combo? Would I still have serial access to the signals?Yes - as above.
If I understand correctly I would need these these gadgets to make your solution work:
WeatherLink $180 (for logging)
Actually, I don't need it, but I understand others think it is essential.
Revised BOM:
Wireless Weather Envoy $195
WeatherLink $180 (OPTIONAL, for logging)
Wifi-2-Serial $150 http://aaxeon.com/s.nl/sc.7/category.903/.f
So we're still looking at > $300, still "pricey" IMHO. :-k
Total price of "only" $235. Not cheap, but a reliable, weather logging solution with a Davis warranty.
Actually, I don't need it, but I understand others think it is essential.
Revised BOM:
Wireless Weather Envoy $195
WeatherLink $180 (OPTIONAL, for logging)
Wifi-2-Serial $150 http://aaxeon.com/s.nl/sc.7/category.903/.f
So we're still looking at > $300, still "pricey" IMHO. :-k
Your experiments are interesting and certainly appreciated for their potential for new types of connections, but you are using strawman MSRP costs.
Best price BOM:
Wireless Weather Envoy $126
WeatherLink $109 (OPTIONAL, for logging)Wifi-2-Serial $150Delete the need for a wireless serial interface as the Envoy is intended to be placed near a computer and the ISS to Envoy wireless connection substitutes for the WiFi.
Total price of "only" $235. Not cheap, but a reliable, weather logging solution with a Davis warranty.
How do you get the serial connection on the remote-side computer?
This Xbee concept has merit though.Actually, I don't need it, but I understand others think it is essential.
Revised BOM:
Wireless Weather Envoy $195
WeatherLink $180 (OPTIONAL, for logging)
Wifi-2-Serial $150 http://aaxeon.com/s.nl/sc.7/category.903/.f
So we're still looking at > $300, still "pricey" IMHO. :-k
Your experiments are interesting and certainly appreciated for their potential for new types of connections, but you are using strawman MSRP costs.
Best price BOM:
Wireless Weather Envoy $126
WeatherLink $109 (OPTIONAL, for logging)Wifi-2-Serial $150Delete the need for a wireless serial interface as the Envoy is intended to be placed near a computer and the ISS to Envoy wireless connection substitutes for the WiFi.
Total price of "only" $235. Not cheap, but a reliable, weather logging solution with a Davis warranty.
Do you know of anything else that is competitive with this?
I have a VP2 and a logger (serial) already. I need to locate the VP2 console in a different area of my house from were the WXPC is. I need a wireless means (economical) of communication between the VP2 console/logger and the WXPC.
Do you know of anything else that is competitive with this?
And, of course, sometimes it's "because it's cool"...
AUTHOR/SOLUTION | Wireless? | Self-powered? | Reliable? | EasyToImplement? | Cost |
(Davis)WL/Envoy | yes | no | yes | yes | ~$235 ("school" solution) |
DeKay*,USB2COM | no | yes | yes | no, need expertise | ~$15 (connects to 20-pin socket) |
AF4EX,XBee | yes | yes | yes[so far] | no, need expertise | <$100 (connects to 20-pin socket) |
SpartanWX, RS-232 | yes | partly | Probably | yes | ~$80(needs WeatherLink/serial) |
johnd, WiFi-to-Serial | yes | no | Probably | yes | ~$100(needs WeatherLink/serial) |
d_l,MAX233 | no | yes | Yes | no, need expertise | ~$20 (connects to 20-pin socket) |
2. WiFi (proposed by johnd) cost is fuzzy, because I don't know if it needs WeatherLink, or not.
Not to change the subject, but do you think a Max233 adapter work with the appropriate connectors attached to it as a serial output connection? More specifically the A232DBH3v version offered as a fully assembled unit with hood kit for $20 here: http://www.compsys1.com/workbench/On_top_of_the_Bench/Max233_Adapter/max233_adapter.html I've previously used these as console interfaces for DSL modems.
You are essentially taking the serial output of the Davis console and converting it to WiFi, where it will appear as a virtual COM port anywhere within WiFi range. Correct? ... and all you need (in addition to serial output) is a little serial2wifi box, having a cost on the order of $100 US. Right?Yes that would be the proposition. I'm not specially promoting this as a solution, more just wanting to clarify that once you have serial output from the console pins then - given the universality of serial data links - there are a whole bunch of different ways of getting the data to a PC, from a simple cable to various wireless options. XBee is one wireless option but there are others and all with pros/cons.
The only 'caveat' that I see is that you'll need some kind of serial output from your Davis console. So that would require:
...2. A DeKay-style, USB2COM interface. But that's not standard RS-232, so an additional "level-shifter" might be required, depending on the wifi box specs.
Another and maybe the cheapest solution , if you do not care about the data logger and want serial out, is to mount and wire an RJ11 or RJ45 female chassis connector to the data logger access panel door. Wire the connector to a header and connect it to the pins. According the data logger manual the max distance is 48 feet of 4 conductor serial cable . Run your cable to a remote computing device with the proper male connectors at both ends. Attach a RJ11 or RJ45 to DB9 adapter (properly wired) and you should be good to go. If you do not have serial port use serial to USB adapter.
Of course, if I got this all wrong and there needs to be conversion of the raw data from the pins before interfacing with a serial port on a computing device, we may need to through in a conversion circuit with a MAX232 or similar IC.
Dave
Oops, just remembered that DeKay is making USB signals, so your idea is different, making RS-232. But you'll have to figure out a way to connect to that 20-pin socket in the console (see page 1 of this post for the way I did it, sort of a "kluge", but it works).Not to change the subject, but do you think a Max233 adapter work with the appropriate connectors attached to it as a serial output connection? More specifically the A232DBH3v version offered as a fully assembled unit with hood kit for $20 here: http://www.compsys1.com/workbench/On_top_of_the_Bench/Max233_Adapter/max233_adapter.html I've previously used these as console interfaces for DSL modems.
I've never used these, but I think they're the standard for "level-shifting" 3/5 volt logic to RS-232 (two-way). So, yes, add that to DeKay's FTDI design (3v logic) and then I believe you will have a real, wired "RS-232" interface for less than $50, comparable to WeatherLink, but without the fancy logger of course.
I'll add it to the table.
John/af4ex
Another and maybe the cheapest solution , if you do not care about the data logger and want serial out, is to mount and wire an RJ11 or RJ45 female chassis connector to the data logger access panel door. Wire the connector to a header and connect it to the pins. According the data logger manual the max distance is 48 feet of 4 conductor serial cable . Run your cable to a remote computing device with the proper male connectors at both ends. Attach a RJ11 or RJ45 to DB9 adapter (properly wired) and you should be good to go. If you do not have serial port use serial to USB adapter.
Of course, if I got this all wrong and there needs to be conversion of the raw data from the pins before interfacing with a serial port on a computing device, we may need to through in a conversion circuit with a MAX232 or similar IC.
Dave
Not to change the subject, but do you think a Max233 adapter work with the appropriate connectors attached to it as a serial output connection? More specifically the A232DBH3v version offered as a fully assembled unit with hood kit for $20 here: http://www.compsys1.com/workbench/On_top_of_the_Bench/Max233_Adapter/max233_adapter.html I've previously used these as console interfaces for DSL modems.
Hi, af4ex,
could you tell me how to configure the XBEE connected to the Davis and the one connected to the PC?
I´m trying to use X-CTU but i don´t know how to configure both XBEEs.
X-CTU: Whenn i push the buttom "Read" X-CTU says that is XB24.ZB and un the function set says: "ZIGBEE ROUTER AT"
Both XBEEs are configured to 19200 baud.
Range test give me always errors (Time out waiting for data)
Thank´s in advance.
atdb says 0
atbd is correct (4 = 19.2K baud)
Nothing happens. Cumulus couldn´t read nothing. Give me an error that says it couldn´t initialize the station. Cumulus run perfectly wuit the FTDI interface via USB but not with the XBEE´s ](*,) ](*,) ](*,)
No good news. I tried everything you said but nothing. Check connections. Every thing seems OK ... #-o #-o but nothing ...
No good news. I tried everything you said but nothing. Check connections. Every thing seems OK ... #-o #-o but nothing ...
What is your interface on the Davis side? Are you using the design from page 2? Did you use heat-shrink wrapping on the wires? If you have a voltmeter make sure the 3volts is getting to the XBee.
The most likely problem (if you're using the page 2 design) is that you're not connecting reliably to the 20-pin socket. (Remember I said it was a 'kluge', but it does work if you're careful about the construction and installation).
Recheck the wiring.
The XBee's seem to be very robust. I plugged both of them backwards on my first attempt (right after my eye surgery) and they survived! :roll:
A more rellable connector can be constructed, using the Samtec part I mentioned. Also, SLOweather has found a part that seems to work. Waiting for him to respond on exactly which Digikey part he used (I couldn't find it using the nomenclature he had in his post).
Don't give up. You'll get it working eventually. (And perhaps learn more about circuit construction and troubleshooting than you anticipated).
No good news. I tried everything you said but nothing. Check connections. Every thing seems OK ... #-o #-o but nothing ...
What is your interface on the Davis side? Are you using the design from page 2? Did you use heat-shrink wrapping on the wires? If you have a voltmeter make sure the 3volts is getting to the XBee.
The most likely problem (if you're using the page 2 design) is that you're not connecting reliably to the 20-pin socket. (Remember I said it was a 'kluge', but it does work if you're careful about the construction and installation).
Recheck the wiring.
The XBee's seem to be very robust. I plugged both of them backwards on my first attempt (right after my eye surgery) and they survived! :roll:
A more rellable connector can be constructed, using the Samtec part I mentioned. Also, SLOweather has found a part that seems to work. Waiting for him to respond on exactly which Digikey part he used (I couldn't find it using the nomenclature he had in his post).
Don't give up. You'll get it working eventually. (And perhaps learn more about circuit construction and troubleshooting than you anticipated).
I think everything you comment is correct in my system. Everything is the same. Both XBEE responds correct if i put them in the SPARKFUN USB EXPLORER.
3 VOlts to XBEE correct.
Heat-shrink wrapping on the wires
The wires are the same for the serial cable version and its OK but when i connect the XBEE nothing happens, they don´t see one to each other.
Can you provide a link for that Digikey "2mm 20 pin solder tail/PC mount female connector" part?
Can you provide a link for that Digikey "2mm 20 pin solder tail/PC mount female connector" part?
http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=952-1361-5-nd
I bought 20.
Do the solder pins protrude above the console casing when plugged in, such that they could be attached to a printed circuit board (for making a "custom dongle")?
And since they are kits, I may have made an assembly error or something.
Okay... now for the "Dummies 101" question.
Is this a way to have your Davis Pro2 console and USB logger in one room and transmit the data to your PC in another room without a physical connection?
I just wanted to point out that Sparkfun also sells the RS232 Shifter as a fully assembled and tested unit for those that might have difficulty soldering all the components due to lack of fine motor skills like me. This part is somewhat difficult to find on the Sparkfun site unless you are specifically looking for it. All that would be needed is to solder wires to the PCB. RS232 Shifter SMD (http://www.sparkfun.com/products/449)
Prior to purchasing the kits, I had heard from one of the engineers here at work that they had tried these for an engineering project with less than satisfactory results. I'm not surprised that it doesn't work on my interface.
I'll bring one to work and try it on a real PC serial port, just for completeness.
Do the solder pins protrude above the console casing when plugged in, such that they could be attached to a printed circuit board (for making a "custom dongle")?
Yup. Been working on that. ExpressPCB doesn't seem to have a premade 2mm connector component. I guess I'll have to make one.
BTW, I found these $2.70 PCBs which seem to have 2mm pitch.
(deletia...)
(What could possibly go wrong? :) )
BTW, I found these $2.70 PCBs which seem to have 2mm pitch.
(deletia...)
(What could possibly go wrong? :) )
From the web page...
Hole Pitch: 0.1 in – (2.54 mm)
We need 2mm (0.079") pitch...
For my application, in ExpressPCB, I successfully modified the 20 pin 0.1" connector to 2mm spacing. It took just a few minutes.
ShapeLock -- "Shape-then-lock" Design Plastic
Build your invention now -- without machine tools. Create super-strong custom parts, prototypes, molds, servo brackets, robot housings, sculptures, science projects, and more.
Space-age plastic melts in a microwave or hot water at 160°F, then remains safely moldable by hand until locking rigidly at room temperature. Simply reheat in order to re-shape as often as you like.
This easy-to-use material is non-toxic, lightweight, machine-able, and paint-able -- plus it can be dyed with hobby-shop pigments. Full instructions are included, in addition to email support and online information at www.ShapeLock.com
Hey guys,
If you look in Eagle, libraries, con-molex.lbr, 87758-2016, 20 Pin - 2mm Dual Row Single Wafer, Vertical T/H HDR.
Source: http://www.molex.com/pdm_docs/sd/877580616_sd.pdf
Is that what you need??
George
If you are referring to the "alpha rev. proof-of-concept A232DB to 2mm connector Davis serial adapter", then, no. This is a way to spend about $30 to connect your Davis console (VP, VP2, Vue Envoy) to a computer or other device via RS232 serial, rather than spending $120 or so on a Davis serial WeatherLink.
...I am guessing that if you can assemble the kit of parts for the Console Connector to the Serial Adapter as described above, then you should have a functioning interface that can allow the weather software on your PC to read the data from the Console......correct? Am I correct to assume you do not need to supply any power via this interface and that the 4 wire connections on the serial interface will handle all the actions needed? I really do not want to fry my console.
Hi Dennis, welcome to the Davis wxforum!
Yes, your assumptions are all correct. The methods in this posting allow you to construct a relatively inexpensive, wireless, self-powered serial interface. Even cheaper if you just use the USB2COM chips without the XBee's.
The trickiest part of the construction is the connection to the back of the console socket. It's a kluge, but it will work if you follow the instructions carefully.
I'm working on a more reliable customized PCB interface for this circuit, but have been sidetracked by other issues, so will still be awhile before anything is available for testing.
I've been using my wireless XBee interface now since March, which has performed flawlessly. The problems I experience in keeping the station reports flowing are always in my Internet connection and household WIFi. The XBee circuits have never dropped any data. Totally solid.
Keep us informed on your progress, when you get your parts.
John/af4ex
There are some Digi-Key links but they are broken and I am not sure either that Digi-Key sells in Europe where I am based.
Hi Everybody,
...
Maybe something like this could also work: http://www.robotshop.com/eu/netmedia-10inch-jumper-wires.html
What do you think?
...
Actually, I would recommend using SLOweather's Digikey connector, the simplest way to make this connection.
Yup .. the Digi-key link works. I don't know how I checked it before.
Do you know if it is also possible to get the cable and connector that goes into the FTDI basic breakout 3.3V?
Thanks,
Jordi.
Thanks,Yes, it appears that this SFE cable is identical to the Adafruit cable, and a few bucks cheaper, because SFE considers the 5v power to be a 'mistake'.
I understand that this is the same item as the one in sparkfun:
http://www.sparkfun.com/products/9717
5V power and 3.3V I/O. That's right because we are not going to use the power, right?
Jordi.
Admitted noob here. I have followed all the directions to create the cable from the console to the FTDI from Sparkfun and got the VCP to recognize the FTDI on my Mac, but since I am not much of a comm expert, I am running into problems getting any software to recognize the console. Do I need to pass some other information to the console through my terminal in order for the software to recognize it? I am trying to use Lightsoft Weather Center and it sees the usb to serial connection, but does not find the Vantage Vue. Am I missing something? I am not interested in using the XBee option as this will be connected to a computer directly.
Admitted noob here. I have followed all the directions to create the cable from the console to the FTDI from Sparkfun and got the VCP to recognize the FTDI on my Mac, but since I am not much of a comm expert, I am running into problems getting any software to recognize the console. Do I need to pass some other information to the console through my terminal in order for the software to recognize it? I am trying to use Lightsoft Weather Center and it sees the usb to serial connection, but does not find the Vantage Vue. Am I missing something? I am not interested in using the XBee option as this will be connected to a computer directly.
@neulos
> I used "sudo minicom -s" in Linux with 19200 8N1 configuration. I didn't get any reply.
Hmm, that is strange. I suspect it might be minicom. I've had similar issues with it. Try another Linux terminal program, such as "screen", which converts your xterm window into a serial comm window.
:-|
First of all I would like to thank DeKay for his excellent work.
I made my solution in such a way, that it does WiFy: this little small excellent module
Looking like a Wi-Fi replacement for the 928MHz FHSS transmitter. Maybe an upgrade for the VP1 weak ISS?
I think I see a Davis ISS replacement in the works! ;)
I think I see a Davis ISS replacement in the works! ;)
To be honest, I though about that as well ;)
At the end, the quality of a weather station is 99% the sensors, and mostly the ones with the best sensors are not the best ones IT wise. If one could find out which analog signal these sensors are producing, it would be about time to hook them up to something else than the ISS to transmit these values to something else than a Davis console.
First of all I would like to thank DeKay for his excellent work.
The wireing I did using these
(http://www.kabel-center.de/descr_artikel/C/C-IDE-599/IDE-Kabel-2-5-Zoll-Stecker_gross.jpg)
They have the 2.0mm pitch and you only need to remove the little nose at the side and it fits quite well.
Looks to me like a regular hard drive ribbon cable. Cool idea.
At the end, the quality of a weather station is 99% the sensors, and mostly the ones with the best sensors are not the best ones IT wise. If one could find out which analog signal these sensors are producing, it would be about time to hook them up to something else than the ISS to transmit these values to something else than a Davis console.
Looks to me like a regular hard drive ribbon cable. Cool idea.
An HD cable won't work, at least not directly. The HD cable is standard 0.10" pin spacing, the Vue and VP spacing is 2mm. The OP mentions that it is 2mm spacing
Analog comes down to the wind direction (a 20K potentiometer)...
DeKay: If you look closely at your sensor picture you can see some writing in the upper right corner of the module. Looks like M5535C or one of its siblings. http://www.meas-spec.com/product/t_product.aspx?id=5029
Alan
There is less analog than you'd think. It is a digital interface to the temperature / humidity sensor (some details here (http://madscientistlabs.blogspot.com/2011/02/busy-weekend-coming-up.html)). The wind speed and rain bucket are reed switches. Analog comes down to the wind direction (a 20K potentiometer (http://www.wxforum.net/index.php?topic=7651.msg73374#msg73374)) and the pressure sensor. The latter is the only thing I've been able to find much detail about. The one in my console is unmarked, but maybe wxtech has been able to dig up some details on this thing?
It's a standard serial connection, so it's possible. The problem would be that the DavisTalk protocol is not publicly documented, so there is no easy way to decode the data.
I would like to start off by apologizing. I'm not sure if it's the appropriate place for this post. I am new to this forum. I have spent the last 3 days reading all your members post and I Would Like Thank Everyone for all the trial and errors and sacrifices you made so we can better understand things. Ok, I'll make it brief. I just purchased Davis Vantage VUE and absolutely love it. Wife was not so happy about the price. Anyway, I am a huge electronics fan and know a lot about functions and features of electronics,but I have no clue about the inner workings of such sophisticated equipment. I do not want to spend $150 for the data logger if I don't have to. I would rather use optional software. I read on one of the post that some one might start making some and selling them. Do you know of anyone? I'm wanting to expand all the capabilities of this unit for a fraction of the price of course. Thanks For Your Time. I'm looking forward to keep reading on. Just getting into the hobby.
I wonder if WL software can decipher this DavisTalk when hooked directly to the ISS. I might try this when I get home in a week.
I read on one of the post that some one might start making some and selling them. Do you know of anyone?
@DeKay
> WiFi XBees ...
Yes, very nifty, much greater bandwidth and same board footprint. But how does that help us in interfacing with the 19kb Davis boxes? Which the regular XBees seem to handle perfectly.
When operating in transparent mode, the modules act as a serial line replacement. All
UART data received is queued up for RF transmission. When RF data is received, the
data is sent out through the UART.
@DeKay
> WiFi XBees ...
Yes, very nifty, much greater bandwidth and same board footprint. But how does that help us in interfacing with the 19kb Davis boxes? Which the regular XBees seem to handle perfectly.
I was wondering if this would basically work as a serial to wifi adapter, much like the USB to serial converter. One XBee on the console end and just a computer on the other, communicating through a wireless router. The XBee seems to take care of bundling the serial bits into TCP/IP packets in its transparent mode. Page 25 of the product manual (http://ftp1.digi.com/support/documentation/90002124_B.pdf) says...QuoteWhen operating in transparent mode, the modules act as a serial line replacement. All
UART data received is queued up for RF transmission. When RF data is received, the
data is sent out through the UART.
WiFi XBees! (http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/point-multipoint-rfmodules/xbee-wi-fi.jsp#overview)
These just came out.
Yes, it can provide the same serial 'transparency' as the regular XBee's, but with much greater bandwidth, way above 1Mbps as I recall. But since the Davis boxes communicate at a meager 19kb, this extra bandwidth capability would be wasted. Right?
@johnd
> ... aren't these effectively just another WiFi device server. Or am I missing something?
I'm not sure what Digi's market goal is for these devices. They apparently default to transparent UART mode, just like we're using the regular XBee's. But they have other programmable modes too, so perhaps intended for inclusion in WiFi-enabled products as OEM parts. Or perhaps serve as an Internet bridge to link XBee-Pro networks to wider area networks.
And you'd probably need some minimal processor (Atmel maybe) running in the background to set it up and provide control.
Hi All, new member to forum here. I'm just about to bite the bullet and purchase a Vantage Vue from Amazon (they have a sale going on!) and have been reading this thread with great interest. If I'm interested in a simple, USB connection to my PC and start gathering data in Cumulus, from what I've gathered, I would need
http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=952-1361-5-nd
and
http://www.sparkfun.com/products/9717
Is this correct? Thanks!
Thank you...will do.
I think I may need a little clarification on the connection to the console though. Once I receive the connector from Digikey and the modified cable from Sparkfun...what exactly do I do with it to connect it to the console? I apologize if this is detailed in a prior post, but it seems that there were several different methods posted in this thread using different equipment, and I want to make sure I don't fry my console!
WiFi XBees! (http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/point-multipoint-rfmodules/xbee-wi-fi.jsp#overview)
These just came out. Looks like you can get connectivity between the console and a wireless router for $49. This is comparable to the price of two serial point-point XBees and much more flexible. These modules support b/g/n, have their own built in wireless stack, and also have the same LVTTL serial interface as the other XBees.
If, like the current XBee solution, the link is essentially transparent, then wouldn't any current software (such as Weatherlink or Cumulus) that supports a TCP/IP interface "just work"???
I gotta get me one of these...
WiFi XBees! (http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/point-multipoint-rfmodules/xbee-wi-fi.jsp#overview)
These just came out. Looks like you can get connectivity between the console and a wireless router for $49. This is comparable to the price of two serial point-point XBees and much more flexible. These modules support b/g/n, have their own built in wireless stack, and also have the same LVTTL serial interface as the other XBees.
If, like the current XBee solution, the link is essentially transparent, then wouldn't any current software (such as Weatherlink or Cumulus) that supports a TCP/IP interface "just work"???
I gotta get me one of these...
Did I miss something or do these need to be set up first (baud rate etc) via something like the Development Kit via USB and the X-CTU software? Or is an Ethernet configuration possible? If the Ethernet configuration is acceptable then this module sure seems great and easy for anyone with a WiFI connection/device.
First of all I would like to thank DeKay for his excellent work.
I made my solution in such a way, that it does WiFy: this little small excellent module
(http://www.rovingnetworks.com/images/rn-174.png)
called RN-174 (http://www.rovingnetworks.com/rn-174.php) is happy if you connect GND, 3.3V, RX an TX. Setup is a little tricky (you need to make an Adhoc connection to config the SSID and 19200 Baud Rate) but then it works like a charm. The Eval-Kit should resell in the US at around $80 (I am fom Germany, so no clue about your prices ...) and the module itself for something like 30$. So if any of you folks around are good in designing & manufacturing a PCB, go ahead.
snip
I may have missed this (Ya I did darn it but seeing Sparkfun has it as a module and better price is new) another less expensive WiFI option may be http://www.sparkfun.com/products/10822
which is a RN-XV module by Roving Networks. It apparently has the same footprint as XBees and is less expensive than the other wireless modules/options. Currently out of stock but at 35$ each I may experiment with one after I get my Vantage Vue2 up and running in a week or two.
Have you tested the range yet? I see Sparkfun has the RN-XV module listed for 35$ so I may try one.
Yes, it's expensive, but I believe nothing is 'overpriced' if the company makes money selling it. I'm all for American ingenuity and enterprise (which must be motivated partly by profits, else we wouldn't have jobs).
I did pickup a cheap laptop IDE cable to make up a connector for the back of the Vantage (someone else noted it has the correct pin spacing). One laptop IDE cable can make up 4 connectors for the expansion connector so plenty to practice with and cheap too (a spare or Ebay).
Good work, gwynethh, and just in time, Sparkfun is sold out of these RN-XV WIFI units again :-|
I'm still trying to understand how the serial connection works with these gadgets.
Some questions:
1) Would it be possible to establish a connection on a remote computer, miles away away from the console?
2) Is the connection 'broadcast' to everyone or just to a specific IP address?
3) What software do you need to connect on the client side?
Outstanding job, gwynethh! It would be interesting to see if multiple PCs trying to access the console at the same time cause any problems. If the messages back and forth are short enough, I'm theorizing that it just might work: the RN-XV's TCP-IP stack might keep everything straight. But what I know about networking could fit on the head of a pin.
... not sure on this but as far as i can tell so far, the RN-XV acts just like any client on a wireless
... not sure on this but as far as i can tell so far, the RN-XV acts just like any client on a wireless
Looking at the data sheet and user manual (http://www.sparkfun.com/products/10822) I see that this is a bit different than I imagined. Instead of setting up a web server on port 80 (needing a client-side piece to communicate with) it merely sets itself up as a client on its own WiFi network at 169.254.1.1 port 2000.
Outstanding job, gwynethh! It would be interesting to see if multiple PCs trying to access the console at the same time cause any problems. If the messages back and forth are short enough, I'm theorizing that it just might work: the RN-XV's TCP-IP stack might keep everything straight. But what I know about networking could fit on the head of a pin.
No luck with multiple PCs accessing the base at the same time. The second instance will not connect and will cause the first instance to error out. Maybe someone with more wireless router savvy could cure this but a no go for us.
Update. By playing with the "Discon Period" and restart settings in Cumulus we got two instances of Cumulus running on different PCs though they might cause a restart of each other if the data requests overlap/collide.
I want to thank Dekay for the information you provided the world free of charge. A thanks to af4ex for the pictures to help us along. A thanks to everyone else for their stories of struggle and success. I would also like to thank Jax for his young hands - he is a great kid and has some neat projects at - http://www.jax184.com (the least I can do for him).
My next post will outline my work with Free and Open Source software to do something with all this data. Hopefully I will have a link to share for my live web feed of my weather station data.
A couple of months ago, and thanks to this forum, I was able to connect my Davis without a data logger to a computer... It is been working now since 25th September flawlessly.
I would like to point out at this time that the home made versions we are building here do not have an archive buffer between the console and a computer as the Davis part does. This buffer as far as I understand from poking around is what a piece of software like wview uses to build its archive data from.
I can confirm that wfrog works with this type of setup. I am one of wfrog project leaders and I've got a Davis connected to a Alix 3D2 board using a FTDI cable and running voyage linux and wfrog (see the link below). wfrog only expects Davis basic events (every two seconds) so it doesn't need the datalogger.
I understand that you might not like the default html setup. With good knowledge of html it shouldn't be difficult to change (it is based in cheetah templates).
I have a working logger clone with archive facitilty that should work with the Davis Vue.
I would like to point out at this time that the home made versions we are building here do not have an archive buffer between the console and a computer as the Davis part does. This buffer as far as I understand from poking around is what a piece of software like wview uses to build its archive data from.
I have a working logger clone with archive facitilty that should work with the Davis Vue.
here is an image of the prototype
(http://farm7.staticflickr.com/6098/6376489793_108e2ff966.jpg) (http://www.flickr.com/photos/77614806@N00/6376489793/)
Logger MkII (http://www.flickr.com/photos/77614806@N00/6376489793/) by belfryboy (http://www.flickr.com/people/77614806@N00/), on Flickr
If the wireless module is simply a serial interface then of course. It would just need to connect to the RX and TX lines. I could have a look at this if anyone wants it.
Is it possible to somehow get the logging and wireless capability together?
I was just looking at what Gwynethh was doing and also John/af4x, but the units they were building had no logging capability correct? The wireless looks good to me as I want my console upstairs, and our only computer is in the basement, but I dont want to run it 24/7.If the wireless module is simply a serial interface then of course. It would just need to connect to the RX and TX lines. I could have a look at this if anyone wants it.
Is it possible to somehow get the logging and wireless capability together?
Let's pretend Santa leaves a Data Logger in my sock, what parts do I need to stream the data from upstairs to downstairs using the xbees?
My mistake, I should have clarified a Davis weather logger in my sock, as there is the possibility of that occuring.Let's pretend Santa leaves a Data Logger in my sock, what parts do I need to stream the data from upstairs to downstairs using the xbees?
Nothing, besides a cable to connect between the xbee header and the terminal block shown on belfryboy's logger. Look at this post (http://www.wxforum.net/index.php?topic=10721.msg104689#msg104689) to see how af4ex made the connection to the xbee on the console side.
The logger and the interface are two totally separate functions. That is why we can have one, the other, or both. belfryboy's design is the logger plus a terminal block connected to the consoles Tx / Rx lines that makes it easy to connect up the computer interface. Like he said: very simple.
but what would be needed to get the davis data logger to connect to another xbee? the same as what would plug into the destination computer? Dont have a Davis logger so I dont know what end is on it
He used a Linksys WRT54G, which already has an internal serial interface at compatible voltage levels to the console. Many other routers have a similar connection inside. This part I figured would be straightforward, and it was. The tricky part is the software. He looks to have that nailed and has made the script available in the public domain. Check it out at this link (http://blog.ancient-workshop.com/post/2011/12/10/Weather-Station-Hacking) and start voiding another warranty!
I thought there might be a few people out there interested in a very cool hack. A reader of my blog has figured out how to directly hook up a Davis console to his router and upload the data directly to wunderground. No interface PC required.
He used a Linksys WRT54G, which already has an internal serial interface at compatible voltage levels to the console. Many other routers have a similar connection inside. This part I figured would be straightforward, and it was. The tricky part is the software. He looks to have that nailed and has made the script available in the public domain. Check it out at this link (http://blog.ancient-workshop.com/post/2011/12/10/Weather-Station-Hacking) and start voiding another warranty!
I bought the FTDI cable from sparkfun and the sockets from digikey. I notice neulos only connected ground, tx, and rx. No VCC (voltage-collector-to-collector).
What is the purpose of VCC? Should I hook it up? I'm thinking it's the positive voltage reference but I could be wrong.
Thanks,
Jeff
I have just ordered the first batch of my boards (20) I have even added an option for a serial interface now, just for those that want it. PM me if you are interested. Remember, this board does have the datalogging option, but will not work with Weatherlink. I have successfully tested it with cumulus and Weather Display on Windows XP.
Davis logger for around $60 - Bargain!
Somebody sometime should really dig into why Weatherlink doesn't work when everything else does. This nags at me, but I'm busy playing with something else right now to spend the time on it.
Most likely because it uses the DMPAFT cmd and it doesn't get a valid response.
Most likely because it uses the DMPAFT cmd and it doesn't get a valid response.
That should mean that if I have both my DIY logger and my DIY interface hooked up, it should work. Correct? I think belfryboy has already tried this with no luck, but I'll give it another shot and see.
By option for a serial interface, do you mean that your design includes a USB to serial adapter? Is that mounted to the board, or do you include a separate adapter that plugs into your board? Or do you mean an RS-232 serial to LVTTL serial adapter?
Thanks DeKay and af4ex =D>... This is a wonderful :grin:! Everything worked without any trouble and right now I have Cumulus running. Since the terminal program running, I am planning to write a simple c code to communicate with console on COM5, download/update data every 2 second and write it to a file for linux.
Question: Am I wasting time "reinventing the wheel" by writing this code :? !
I would suggest sending the DMPAFT cmd and examining the response. Will probably have to capture it, as the response will be binary. Should get an ACK (0x06) in response, then sending an ESC will abort the cmd. The next step would be to send a date/time, but that needs a CRC or it will be ignored.
Maybe tomorrow I'll put the 1Mbit version in there and see if there is different behavior.
We'll use the SparkFun XBee breakout board ($3) and a pair of 2mm header sockets ($1 each) which need to be soldered to the breakout board for mounting the XBee transceiver ($22, same as above). Buy an extra header socket, which will be cut up to make the console connector cable (details in previous Phase I posting).
http://www.sparkfun.com/products/8276
http://www.sparkfun.com/products/10030
Ideally I’d like to have a wireless connection on my wireless console to connect to my home network
I've seen a number of posts that have created some sort of wireless connection to a computer but haven't found anything that will post the data without the computer running.
Is there an issue following the steps laid out on http://madscientistlabs.blogspot.com/2011/01/davis-weatherlink-software-not-required.html if you have a new unit? http://wx.sloweather.com/dsi-01.php
Million dollar question....
Does the XBee solution still work?
I can report that the SLOweather DSI-01 Does work with this firmware release! =D>
VP2 Wireless FW 1.9 > 3.12, update was done on WeatherLinkIP that I believe is Green dot, mfg code F10112A54
According to this, it should. This topic reply was in another thread:now that I think about it they don't have an update yet for the Vue which is what I am purchasing I have the VP2 at home this will be at the cabin.... :-(I can report that the SLOweather DSI-01 Does work with this firmware release! =D>
VP2 Wireless FW 1.9 > 3.12, update was done on WeatherLinkIP that I believe is Green dot, mfg code F10112A54
http://www.wxforum.net/index.php?topic=18391.0
The issue is not the firmware revision per se (so don't let answers confuse you which relate to the firmware revision but in older consoles), but the console hardware.
Rather, it's a combination of the v. 3.xx firmware *and* that little something which indicates that the unit is a "new" console.
Maybe. But the one single factor that defines whether a console will work eg with an XBee or not is whether it's a console hardware revision earlier than Rev 'M' or not. So why not focus on that specific point?
Will knowing that specific point contribute to making a workaround to this problem?
I've got a Davis 6250 on the way and have spent hours reading these threads to connect the console to a Windows 7 PC in a closet 30 ft away. Running some form of data logging software, internet viewing, and weather station availability.
Just when I though I had a grasp on things I see things changes with the new revisions.
Could someone please be so kind as to redirect me to a solution that works with the new revision 6250?
Thank you very much!
I've got a Davis 6250 on the way and have spent hours reading these threads to connect the console to a Windows 7 PC in a closet 30 ft away. Running some form of data logging software, internet viewing, and weather station availability.
Just when I though I had a grasp on things I see things changes with the new revisions.
Could someone please be so kind as to redirect me to a solution that works with the new revision 6250?
Thank you very much!
Off-topic, but: http://www.davisnet.com/weather/products/weather_product.asp?pnum=06510SER
The problem:
connected to pins 5 & 6 of the Vantage, I can get no response back at all. Have tried sending TEST many times and per Davis a hex '0A'. I get nothing. I see no configuration setting on the Vantage in the menu. From ground to either pin 5 or six I measure an open voltage of 3v. I can send photos of my set up if needed. Anyone have any ideas what I did wrong?
Keshka
I am currently on Rev 1.90 and have NO intentions on upgrading unless I am forced to. If I do upgrade, I assume I will have to either buy a new logger or build one!
Thank you for responding DeKay. I have connected xBee "b" the same as this post:
http://www.wxforum.net/index.php?topic=10721.msg104689#msg104689 (http://www.wxforum.net/index.php?topic=10721.msg104689#msg104689)
Is it correct that this Hirose connector will connect without modification?Nuts, I didn't see this before I did my own digging around for the connector part. Yes, the Hirose DF11-series connectors appear to be exactly correct, or at least form/fit/function-compatible (including keying). As I commented yesterday (http://madscientistlabs.blogspot.com/2011/01/davis-weatherlink-software-not-required.html?showComment=1613596140688#c6720811408339741712) on DeKay's old blog post, a Hirose DF11-20DS-2C connector housing (https://www.hirose.com/product/p/CL0543-0509-7-00) and some DigiKey-assembled wires (https://www.digikey.ca/en/products/detail/H3BXG-10112-W4/H3BXG-10112-W4-ND/312645) are an easy way to get connected “nicely”. It's not much to look at because it fits so well.
http://octopart.com/df11-20ds-2dsa%2805%29-hirose-260412 (http://octopart.com/df11-20ds-2dsa%2805%29-hirose-260412)