I'm under way

[Werk_AG]

Hi, uncle_bob
At first look at the picture of your board, my first thought was: But where do I have published this photo?
Is so similar to mine, even has the same type of connectors. Looks great.

I make a couple of substitutions:
I only could find a 20K pot for R8 (15K).
And a 360R for R1 (380R).

No problem at all.
R8 - must be adjusted to 10K, or as close as you can. As the wind direction is done by an analog read, this pot is there just in case we need to do an inicial fine adjust (I never had to do any adjustment, after setting it to 10K)
R1 - Your green led will be fine with it.

I see you have used a yellow led instead of a blue, no problem with that, they can be any color you like. Just calculate R1 and R2 so that the current through the LED is appropriate.
Note that the leds are powered from the 9V voltage regulator.
For a yellow led, perhaps you must raise R2 to... anything from 360R to 470R will be fine. I know you understand what I'm saying.

Edit: It's OK, I just tried the VirtualWire-1.27 version and it compiled ok. Werk, please let me know if this library isn't the right one.

I completely forgot to include the VirtualWire library. I will fix it immediately.
I have been using version 1.20 of the VirtualWire library, but since I read your post, I've been doing some testing with version 1.27 and it seems to work perfectly (also it saves some precious bytes). I'll continue my tests for a few more hours and if I find no errors, this version of the library will be added to the WeatherDuino Pro2 software package.
So I think you can stay with version 1.27
Does your TX (green) led blink?

PS: As soon as I can I will start study the new Radiohead library.

[Werk_AG]

After some hours testing VirtualWire 1.27 with the WeatherDuino Pro2 system, I don't found any problem.
WeatherDuino Pro2 software package has been updated, now it includes the missing VirtualWire library, and some changes on the RX software (internationalization).

Thanks uncle_bob

[uncle_bob]

Does your TX (green) led blink?

Hi Werk,
No it doesn't, the only sign of life is the red nano LED.
EDIT:Hmm I wonder if the 2N7000 got cooked when I soldered it in.
It must be doing something though as when I tried to see any coming out the serial port, the IDE always says Com Port in use.

I'm curious as to how I would re-upload any software to the Nano now?

Cheers UB

[Werk_AG]

Does your TX (green) led blink?

Hi Werk,
No it doesn't, the only sign of life is the red nano LED.
EDIT:Hmm I wonder if the 2N7000 got cooked when I soldered it in.

I forget to say. The TX Led can only blink when the system is powered from the 12V power connector.

It must be doing something though as when I tried to see any coming out the serial port, the IDE always says Cmm Port in use.

Are you using the Arduino IDE Serial Monitor to monitor the output, or any other tool? If any other tool, close it, it my be blocking the serial port.

To see something out from the serial port you must enable Local_TestMode:

Uncoment the line:
#define Local_TestMode

to see debug data for the DHT22 you can also uncomment this line
#define DebugID1

After debuging don't forget to comment those lines again.

I'm curious as to how I would re-upload any software to the Nano now?

Just do it as the first time, compile the code and upload it again. You can do it many many times.

Cheers Werk_AG

[uncle_bob]

I forget to say. The TX Led can only blink when the system is powered from the 12V power connector.

Yes, it's being powered via the 12V headers.
Looking with a multimeter, I can see a pulsing output on D7.
I'm at work now, but will test the FET later today.

[uncle_bob]

Great news Werk,

I replaced the LED and now it's flashing! So it looks like either I cooked the LED (likely) or it was broken.
It's blinking once about every five seconds.
Note: It is blinking when only being powered from the USB. I don't know if this is good or bad.

Also I turned the debug on and are getting lines likes this (copied from Serial monitor)..

0, 0, 0, 0, 43, 0, 50, 20, 0, 0.0, 0, 0, 0, 1000.00, 0.00, 0, 0.00, 0, 0, W, 0, 0, 0, 0.00, 0, 0, 0, 19660.50, 0, 82,
0, 0, 0, 0, 46, 0, 50, 20, 0, 0.0, 0, 0, 0, 1000.00, 0.00, 0, 0.00, 0, 0, W, 0, 0, 0, 0.00, 0, 0, 0, 19660.50, 0, 124,
0, 0, 0, 0, 49, 0, 50, 20, 0, 0.0, 0, 0, 0, 1000.00, 0.00, 0, 0.00, 0, 0, W, 0, 0, 0, 0.00, 0, 0, 0, 19660.50, 0, 124,
0, 0, 0, 0, 52, 0, 50, 20, 0, 0.0, 0, 0, 0, 1000.00, 0.00, 0, 0.00, 0, 0, W, 0, 0, 0, 0.00, 0, 0, 0, 19660.50, 0, 124,
Sending...
DataPacket ID1: 161,1,218,326,0
Temp: 2.18 Hum: 3.26

0, 0, 0, 0, 55, 0, 50, 20, 3, 2.2, 0, 0, 0, 1000.00, 0.00, 0, 0.00, 0, 0, W, 0, 0, 0, 0.00, 0, 0, 0, 19660.50, 0, 124,
0, 0, 0, 0, 58, 0, 50, 20, 3, 2.2, 0, 0, 0, 1000.00, 0.00, 0, 0.00, 0, 0, W, 0, 0, 0, 0.00, 0, 0, 0, 19660.50, 0, 124,
0, 0, 0, 0, 61, 0, 50, 20, 3, 2.2, 0, 0, 0, 1000.00, 0.00, 0, 0.00, 0, 0, W, 0, 0, 0, 0.00, 0, 0, 0, 19660.50, 0, 166,

[Werk_AG]

Also I turned the debug on and are getting lines likes this (copied from Serial monitor)..

Certainly, when you are doing tests with the receiver, we'll talk more about the meaning of data in these lines.

For now, I think it's important to say to everyone: Anyone who wants to build the system, do not have to worry about meaning of these data, however knowing what they are, also does not hurt ...
This data structure follows the EasyWeatherPlus format, commonly used in Fine Offset weather stations. It is used on the TX unit only for debug purposes.

Sending...
DataPacket ID1: 161,1,218,326,0
Temp: 2.18 Hum: 3.26

Taking the opportunity to add a little more information ...

What is really sent by the TX unit, is the content of several Datapacket's like the one above.
Each ID corresponds to a type of sensor or information. If you are not using a particular type of sensor supported by the TX unit, you should disable it by commenting out the respective line in the source code (see this topic for more info about this subject)

uncle_bob, did you have your old Fine Offset rain gauge or wind vane at hand? (I know, the bird takes the anemometer cups )
Try connecting them to the board. Or better, you could start with the DHT22 sensor...

Cheers Werk_AG

PS: Sometimes I reply to your posts as if I'm talking to everyone and not just with you. Sorry, I think you understand why.

[uncle_bob]

Try connecting them to the board. Or better, you could start with the DHT22 sensor...

Hi Werk_AG,

I'll try connecting Fine Offset stuff a little later, as I won't be allowed to drag it into the house

BTW, The DHT22 is connected and is reading but the decimal point seems to be in the wrong spot
Temp: 2.18 Hum: 3.26 = Temp: 21.8 Hum =32.6 (I was thinking that the RX board converted these values)

PS: Sometimes I reply to your posts as if I'm talking to everyone and not just with you. Sorry, I think you understand why.

hehe, no worries.

[Werk_AG]

BTW, The DHT22 is connected and is reading but the decimal point seems to be in the wrong spot
Temp: 2.18 Hum: 3.26 = Temp: 21.8 Hum =32.6 (I was thinking that the RX board converted these values)

Oh no... There is a bug in debug!!!

You are right. The Datapacket it's ok, and the values will be converted to the right values at the receiver.
I think you have noted that all data is sent as integers.

The bug in the DebugID1 code will be corrected on next release.

EDIT: New version has been published !

[uncle_bob]

We have success!
I'll post up drawings later on once I'm finished