[Wizza]

User Options - Soil / Leaf Sensor

In the interest of optimising code execution and processor performance, if you are "not" connecting a Soil / Leaf Sensor to the transmitter station then we should set this options to 0 for Not Used and Disabled by inserting '9's in the lower setup matrix.  

// --------------------------------------------------------------------------------------
//   Soil / Leaf Interface Settings and Sensors Mapping
//   (The mapping logic is the same than used with the Extra Sensors)
// --------------------------------------------------------------------------------------
// 0 = Soil Leaf Interface not used
// 1 = Soil Leaf Interface connected to a TX unit
#define SoilLeaf_Interface  0   // 0, 1,

// ---- For Soil & Leaf data from SoilLeaf_Interface wired to a TX unit, use TX Unit number as source
// ---- For BIOS Soil Temp / Moisture use 7 as source
// ---- To disable use 9 in both fields
//                                 S1    S2    S3    S4
#define SoilTempSensors_Source  { {9,9},{9,9},{9,9},{9,9} }
#define LeafTempSensors_Source  { {9,9},{9,9},{9,9},{9,9} }
#define SoilMoistSensors_Source { {9,9},{9,9},{9,9},{9,9} }
#define LeafWetSensors_Source   { {9,9},{9,9},{9,9},{9,9} }

[Wizza]

User Options - Internet and Station Time

If you are going to connect your Weather Station to WeatherUnderground then you will need to configure a wireless Internet Connection.  This is a new feature in the Pro2PLUS and eliminates the need to connect either a RaspberryPI or a dedicated computer.  To configure your Pro2PLUS to connect to your wireless Internet connection you need to ensure that the wireless option is enabled with a "1" in the "#define Enable_Internet" field and then enter your SSID and SSID password password details.

Network Time Protocol (NTP) is a standard Internet protocol that give your Pro2PLUS the ability to 'automatically' set its time (clock) and keep it in perfect sync with GMT.  The software will use your TimeZone settings from above to translate and display the time relevant to your local timezone.  Ensure that NTP is enabled with a "1" in the "#define Enable_NTP" field, and enter a valid NTP server IP address in the #define timeServer field.  

If you do not have a preferred NTP server or you are unsure of what IP address to use, then a couple of options are listed in the examples.  You can use 80.96.196.58 or 193.79.237.14.

If you would like to select an NTP server that is close to your region of the Internet, Mr. Google can always help you out.  I frequently have to enter NTP server details for router and server configurations, and I find that Google is a quick and easy reference when I'm onsite.  Most countries will either have an NTP pool assigned to them, or be part of a region NTP pool for that area or region.  Within Australia, I typically enter a quick Google search for "ntp pool au" and look for the Australian NTP pool, which is "au.pool.ntp.org".  I then perform a PING on this DNS name and select one of the IP addresses within this pool.  Note that as it is a pool, with redundancy, if you PING the pool domain name "au.pool.ntp.org" a few times over, you may get varying IP addresses returned.  This is ok and is simply some of the "pool" of NTP servers for the region being displayed and you can generally use any of the IP addresses returned.

// --------------------------------------------------------------------------------------
//   Internet Settings 
// --------------------------------------------------------------------------------------
#define Enable_Internet     1                       // 1= Enable Internet connection, 0= Disable

#define SSID        "EnterYourSSIDinHere"
#define PASSWORD    "SSID_password"


#define Enable_NTP          1                        // 1= Enable Sync time with NTP servers, 0= Disable
// NTP Servers:
#define timeServer "104.156.232.174"                    // One of the NTP servers within au.pool.ntp.org
//#define timeServer "80.96.196.58"                  // timp.mcsi.ro
//#define timeServer "193.79.237.14"                 // ntp1.nl.net NTP server

[Wizza]

User Options - Weather Underground

Connecting your Pro2PLUS to WeatherUnderground is now super simple to setup, thanks to Werk's hard effort and extensive coding in the new Pro2PLUS.  Now all you need to do is go up to WeatherUnderground, create a new account, and enter the details into the user options.  Provided that you have completed the Internet (wifi) connection details as outlined above, your Pro2PLUS should connect and start uploading after setting a few simple options as outlined below.

My WeatherUnderground station -->  https://www.wunderground.com/personal-we...UEENSL1115

The first option "#define Enable_WUupload" is pretty self explanatory and simply needs to be set to option "1" to enable the feature.  Next you define your upload period, in minutes.  I would suggest starting with a value of about 3 to 5 minutes.  I've had my Pro2 station running at 3 minute intervals for over a year now with no issue.  The data upload is very "skinny" and will not chew up much bandwidth at all.  Optionally you can also select to upload your inside Temperature and humidity as well, however I choose to simply send my outside environmental readings and choose not too.


#define Enable_WUupload     1                        // 1= Enable upload to Wunderground,     0= Disable
#define WUupload_period     3                        // Period in minutes between uploads to WU (avoid use less than 3 minutes)
#define WUupload_InTemp     0                        // 1= Enable upload of Inside Temperature / Humidity, 0= Disable


Lastly you need to enter your WeatherUnderground station ID which is also your user login ID, and your WeatherUnderground login password.

// ---- Wunderground Personal Data
#define WUNDERGROUND_STATION_ID "ILISBO1234"         // Weather Underground station ID
#define WUNDERGROUND_PWD        "wu_password_here"      // Weather Underground password

[Wizza]

User Options - Test Mode

Unless you are specifically performing "tests" ensure that TestMode is disabled by setting the option to "false".


// --------------------------------------------------------------------------------------
//   Test Mode : Never run a live system in test mode
// --------------------------------------------------------------------------------------
#define TestMode    false    // false= Normal working mode, true= Test mode only (no logger, no usb connection)

[Wizza]

Ok, all looking good so its time to upload the code into the new Pro2+. Only points to keep in mind here is to set the programming switch/jumper on the mainboard to "program mode", and then push and hold the reset button on the RX board for 5 seconds before uploading the code into the Arduino. Verify and load, and we're done. The RX board will reboot and if all is well you will see the WeatherDuino 'splash-screen' come up on the LCD display.

All that's left now is building a nice case and giving this new Pro2+ a permanent home. I've got a few ideas in mind, and will post some photos and pictures of what I come up with. So stay tuned...

Mark R

[werk_ag]

... and then push and hold the reset button on the RX board for 5 seconds before uploading the code into the Arduino.  Verify and load, and we're done.  

I really don't see the point of doing a "factory reset" before uploading the code, in fact, after a "factory reset" (which only be needed in rare occasions) the unit must be left running...

A recommendation for all, especially for those that have systems already running live: A "factory reset" is not needed nor recommended, nor before nor after a software upgrade.

[markkkk42]

Hi Werk

I have my units all running well on the bench hooked up to all the Davis sensors and also uploading to Wunderground. I had to add a -15 correction factor to the pressure measurement to get it correct on the BME280 though. One thing I have noticed is the data update rate to the screen. Is the wind speed and wind direction capable of being updated faster? It takes some 20 or 30 sec..I havent measured it but it seems that long. I know wunderground is updated at 3 min intervals but it would be nice to have a bit more "real time" for local usage. Also now the unit is internet capable is there any way to remotely log into it to get to the data as well as watching on Wundergound. Another thing my Davis rain gauge says on the inside 0.01 inch. I take it that is the measurement for rain. In the setup you say to set to 200 which is 0.2mm. This scale is wrong can I change this parameter to make it correct? It would be 245 wouldnt it?

Mark


Mark

[markkkk42]

sorry 254 I meant as 0.01 inch = 0.254 mm

[werk_ag]

Hi Mark

One thing I have noticed is the data update rate to the screen. Is the wind speed and wind direction capable of being updated faster? It takes some 20 or 30 sec..I havent measured it but it seems that long

The wind gust / speed and direction is updated on the screen at each 5 seconds.
Turn ON the relay data function  

Code:

// --------------------------------------------------------------------------------------
//   Broadacasting settings for Wireless Display Units
// --------------------------------------------------------------------------------------
#define Relay_Data       1   // 0= Disables Data Relay, 1= Enables Data Relay

and check if the TX led on your Pro2 PLUS receiver blinks at 5 secs or less intervals. If this don't happen, check if the TX unit is not too close to the receiver unit, also check your antennas.
TX units should always have an antenna attached to the output.

Also now the unit is internet capable is there any way to remotely log into it to get to the data as well as watching on Wundergound

There isn't any remote access capability, the WiFi module is used just to sync time with NTP servers, and optionally upload data to Wunderground.

Code:

Another thing my Davis rain gauge says on the inside 0.01 inch. I take it that is the measurement for rain. In the setup you say to set to 200 which is 0.2mm. This scale is wrong can I change this parameter to make it correct? It would be 245 wouldnt it?

Yes, you should do it in your Config_TX user configurable settings:

Code:

// --------------------------------------------------------------------------------------
//   Define Rain Gauge tip boucket value (mm)
// --------------------------------------------------------------------------------------
/*
 Use 0.300 for standard FineOfset rain gauges (Datasheet value = 0.2794)
 Use 0.200 for standard metric Davis rain gauges
 Use 0.254 for standard imperial Davis rain gauges
*/  
#define COLLECTOR_TYPE  0.254  // Please note: Values must be in metric units. Max. resolution: 3 decimal digits

There is also another important setting that you should configure in Cumulus:

Rainfall settings

Adjust the Cumulus multiplier according to this formula:
Multiplier = Bucket Type / 0.2

So, in your case for an imperial Davis rain gauge:

Multiplier = 0.254 / 0.2 = 1.27

[markkkk42]

I dont use the cumulus software as my unit will be remote...so I gather that should be fine..that setting is not in any of the arduino code is it