Has anyone here used the xmitter that allows you to extend the anemometer further from the ISS? If so, does it work reliably and how well does the solar charger/power unit work? Thinking about getting one, and want some 1st hand info on how it “really” works in the field.
Can I clarify one thing first: The 6332 Anemometer Transmitter (which I assume is what you’re talking about) doesn’t extend the distance between anemometer and ISS. The 6332 is a separate standard Davis VP2 transmitter and, like all such transmitters, transmits its wind data directly back to the console on a different wireless channel from that in use for the other ISS data. The console is then able to collate the data coming from the two transmitters and integrate them into its display.
The net result is the same, ie the ISS and anemometer become completely independent of one another and can be placed wherever you wish, just provided that there’s an acceptable signal path back to the console for each transmitter.
The 6332 transmitter works fine (provided you’ve allowed a reasonable signal path from 6332-to-console in the same way that you will have done for ISS-to-console). It’s powered in exactly the same way as the ISS, ie a small solar panel, a supercap and a lithium battery and, provided the solar panel is reasonably well exposed to the sun, will give the same battery life as in the ISS, eg around 18 months.
Well actually it does extend the distance from the ISS, as in a normal configuration it is tethered to the ISS by a 40ft cable…By using a stand alone transmitter it is farther (than the 40ft allowed by cable) from the ISS if you so choose, just so long as it is in a receivable distance from the console. I didn’t mean that the ISS was acting as a repeater of the data from the anemometer in the stand alone xmitter config. Basically, I just want to know if anyone has had any probs with the unit.
OK, sorry. (But a surprising number of people do think that the 6332 data does have to be relayed by the ISS in the first instance, which isn’t an obviously wrong conclusion since the ISS handles the wind data in the standard configuration and so it could make sense to think that it still continues to do this when using the 6332 also.)
PRovided you respect the normal rules for VP2 wireless transmission (range, no major obstacles or any sheet metal in the signal path etc) then the 6332 unit works very well. The standard advice is to have the 6332 on channel #1 and move the ISS to eg #2 or another channel, in order that the most frequently updating transmitter (ie the 6332) is on the lowest channel number, but this only makes a small difference AIUI.
I have never heard this before. Where did you get this information from. It doesn’t appear to be in the manual or any FAQ that I’ve seen from Davis regarding transmitters.
Not every detail of how to get the most out of Davis stations is explicitly in the public domain 
Actually, it’s not confidential in any sense whatsoever - I think it’s simply that Davis don’t update their FAQs as often as they might these days. There are various little pieces of minor but helpful information that just don’t get collated and publicised very often (and may not even be recognised by front-line support, especially any newcomers). But I can guarantee you that the info comes from a senior technical level from within Davis.
I don’t pretend to understand the exact details for the suggestion, but I think it’s to do with the separation of the different channels in the time domain and the priority that’s assigned to each channel whenever there might be competition in the console firmware code for servicing a data handling request. AIUI the lowest channel numbers (eg #1) get top priority under these circumstances and hence it makes sense for them to be assigned the most frequently changing data - ie wind speed/direction. But I suspect that it only makes a difference at the margin and it might have been more important for VP1 than VP2. But even so, there’s nothing to lose and potentially some modest gain from moving the 6332 to #1.
It is in the VP2 console manual:
Update Interval . . . . . . . . . . . . . . . . . . . . .
Varies with sensor - see individual sensor specs. Also varies with transmitter ID code - 1 = shortest, 8 = longest.
The one I have works just great. Sends the data to the console and the Envoy just fine. No probs.
Bill.>>>>>>>>>>>>> 
Bill:
Is that a camera on a rotor halfway up your mast?
Steve
Yes it is.
Its a Panasonic BB-HCM371A Pro.
Hear is a photo it took the other night after the storms.
Bill.>>>>>>>>>>>> 
I have been using a 6332 with a VP2 for 2 years without incident - it works great. Using the 6332 I was able to place my anemometer on the roof and my ISS (moved) out to our shed so it is much farther away from the house (heat source).
I originally had it on channel 2 but swapped it to channel 1 (ISS to Ch2) several months ago per Prodata’s suggestion. I did not notice any difference between the channels and both gave me reception of 97%+.