PRO Tutorial

From meteobridge
Jump to: navigation, search

This page lines out some Meteobridge PRO specific how-tows

Optimize RF Reception

Meteobridge PRO (red cap model) has a RF receiver included to directly pick-up data from Davis outdoor sensors. Compared to a Davis console where only very little computing stuff is happening, we have a high density of sensors, computing modules, Ethernet circuitry and even a WiFi module all together in a very compact housing.

To keep RF noise away from the reading Davis sensor data, we designed an external antenna. The antenna shipped with Meteobridge PRO is quite good in RF operation and picks up about 5 db more signal strength than the wire antenna of Meteostick does. However, if your sensors are far away some tweaking of RF reception might be necessary.

This section of the tutorial explains what you can do if you need improved RF sensitivity.

Turn the Meteobridge PRO into an RF strength meter and find a good place to rest

Before you start experimenting how to improve RF reach we recommend to run through the following steps:

  1. Configure your Meteobridge PRO to connect via WiFi with your network. As you might want to move the Meteobridge PRO and test for various locations, having an Ethernet cable hanging around will be annoying.
  2. Mbpro-tutorial-1.png
    Configure your Meteobridge PRO to make use of the internal RF functions and configure "Meteostick:Vantage" option according to your needs. Set correct transmitter ID, set bandwidth to "small" and set sensitivity to "-90db" to start with. Picture on the right gives an example how your settings might look like.
  3. Power your Meteobridge PRO temporarily with a USB power bank. I assume you have some 5V rechargeable battery with USB plug to feed the Meteobridge PRO laying around. Any cheap power bank for your mobile phone will do. You will need a USB cable that fits into the micro USB power socket of the Meteobridge PRO, but I am sure you have that somewhere in your household. Being on battery and WiFi you have total freedom in checking for a good place for the Meteobridge PRO to rest.
  4. Mbpro-tutorial-2.png
    Define a display service on "Services" tab that shows RF data from the outdoor sensors on the integrated display and updates the display every 5 seconds. To do so, define a new service of type "Display" and select "Periodical" as it's event type. Press "Add Service Event" and a new event will be added to the list of already defined events. Then specify "every 5 seconds" as interval and select "Meteostick RF Analysis" from the list of pre-defined standard messages. Settings for this service should look like shown on the right picture. Don't be confused by the message text that is automatically inserted. If you want to understand how this works, please have a look at page PRO_Display. For the moment you don't need to know the details ;-)

Having done so the Meteobridge PRO display will show data like this:

Mbpro-tutorial-4.png Mbpro-tutorial-3.png

Picture on the left shows reception when Meteobridge PRO is directly sitting on my desk with a lamp, some metal enclosures and the metal corpus underneath my desk in direct neighborhood. Values around -70db are not great, but still no problem to receive. When it reaches the -90 db reception will get tough. By moving the Meteobridge less than a meter away to a higher position on a shelf, reception situation improves significantly. You see that on the right picture. Signal strength in the mid -50db is much better and will allow the sensors to go further away without having the connection dropped. By the way, the display is white but my camera makes it look blue sometimes. If you like watching the numbers change, this 30 second movie might be of interest to you (moving black bars on display are just camera artifacts).

No one can tell you what best position will be in your location, but you are highly invited to check out yourself.

Change Antenna

RF antenna on the back panel of the Meteobridge PRO can be unmounted and replaced by a larger and more capable model. Meteobridge PRO offers a standard SMA plug, where any antenna suitable for the RF band your Davis sensors operate in (915 MHz for US, 868 MHz for EU) will fit, as long as it has a male SMA plug. What you can do in principle is going three ways:
  1. replace small antenna by a larger one that better fits to the wave length of your sensors signals.
  2. connect an antenna that is not directly mounted to the connector but has some cable to bring the antenna further away from the RF noise the Meteobridge PRO is inevitable producing and by that giving the RF signals more head room by reducing the noise floor.
  3. connect to an antenna with some directional characteristic, which can be a small yagi or other form factors. This might be an option to consider when extreme reach needs to be achieved and if you can mount the antenna outdoors as a directional yagi antenna might not fit well to your indoor living style ;-)

Picture on the right shows how the Meteobridge RF SMA female connector looks like and how the antenna SMA male plug is formed. When the antenna plug is a bit too thick to have the power connector inserted underneath, you can cut 1 mm off the white plastic from the micro-USB power plug. Please watch out not to cut too deep. While testing with alternative antennas this works rather uncomplicated. Please realize, that you do this at your own risk and it will void your warranty, so better to choose an antenna with a fitting plug.

We conducted some antenna comparisons for you. We choose a not so good reception position and swapped through different kinds of antennas while checking RF reception level.

Mbpro-ant1.jpg Mbpro-ant2.jpg Mbpro-ant3.jpg

On the left you see the Meteobridge PRO with stock antenna, next to it with a 868 MHz "H-Tronic" HT110A antenna and on the right with a multi-band GSM/UMTS antenna 88414 from "delock" which has a rather thick SMA plug and therefore needs the white power plug underneath remodeled a bit with a knife (cutting off 1 mm went fine). As you see these antennas are very close to each other, with the multi-band antenna loosing some ground. From that perspective changing stock antenna with a larger one of the same kind does not make too much of a difference, at least in our test setup.

What can change the game is an antenna that can be mounted away from the Meteobridge PRO. We tested the "H-Tronic" HT250A for the 868MHz band. It comes with a serious 5 meter cable to allow easy positioning far away. We were a bit worried how much antenna gain might be lost by a long cable and indeed it seems to have some impact when you look at the numbers in the picture below. While the HT250A does not seem to be a great performer sitting next to your Meteobridge on your desk (where the other antennas perform better), it is worth considering, when you have a great spot to position the antenna, but you don't want to have to Meteobridge PRO being there (on the top of your book shelf, for example).


Console Retransmits

When nothing else helps, you can always ask your Davis console to retransmit packets and to let Meteobridge PRO sniff data from there. As packet retransmits mostly have a lager frequency drift, you need to change the Meteostick settings on "Weather Station" tab regarding bandwidth from "small" to "normal". Furthermore, you have to select the transmitter ID the Console is using for the retransmits. Having the console just a few meters away from the Meteobridge PRO even the worst antenna will do ;-)

FTP Upload of CSV Exports

There have been may requests to upload data of a day or month in some CSV like notation onto a server via FTP. Meteobridge PRO has the building blocks (export function and FTP upload capability) to make this reality. This section explains how to set this up:

Define CSV Schema

The structure of CSV exports is defined by export templates that are user-defined and can be found in PC network share "templates". Export templates have extension ".exp" while the generated exports are stored in "export" folder and have extension ".txt". We start with pre-defined standard template "standard-iso.exp". This template defines a schema where columns show date, time, temperature, humidity, dew point, pressure, wind speed, wind gust, wind direction, rain fall holds these data the following.

# Standard CSV template with data in metric units
@# date, time, temperature[C], humidity[%], dew point[C], sealevel pressure[hPa], avg wind speed[m/s], gust speed[m/s], winddir, rainfall[mm]<BR>

Meteobridge PRO also allows for some pragmas to control how data is inserted:

  • "#pragma fillgap=nn" automatically fills gaps up to nn seconds to avoid empty columns when there is no data within that specific minute. Default is 300 seconds.
  • "#pragma emptyline=y" does even printout rows, when it is completely empty, which means it has no data. "emptyline=n" does not print out empty lines.

When you want to insert some header or footer lines into the output, these lines need to be start with a "$" or "@", where the "$" is omitted in the output text and output text is subject to conditional expressions and template replacement, while "@" is also omitted but followon text remains unchanged. Any other line starting with "#" is not reflected in the output and just handled as a comment.

Schedule Generation of Exports

Exports can be easily generated with "Export" service on "Services" tab. Example on the right starts at the beginning of a day an export job that generates data for yesterday in resolution of minutes. Template "standard-iso" is used for data generation and a file like this results from it. Time slots where some of the data is missing does show empty values, as defined by the default settings in the template.

Define Upload Service

While time controlled FTP upload services are very standard to Meteobridge, the Meteobridge PRO can also trigger uploads as follow-on events of other events. In our situation we are generating an export file time controlled and the execution of the export event then triggers an upload event that pushes the just generated file onto your server. Definition is done as usual as an "FTP" service, but "Event Type" this time is "Trigger by Event". Example on the right shows that the FTP upload event is directly triggered by the export event. The file to be used for upload is specified as "export:lastexport" which automatically addresses the last generated export file. Target file name makes use of template variables [YYYY], [MM], [DD] which are replaced by year, month and day. Here the beginning of the data in the export file and not the current data when doing the upload is used. This takes care that the file will have a proper name on your server which matches the data in the file.

Doing Data Backups

The Meteobridge PRO stores incoming sensor data in the internal 1 GB USB storage. But what if the Meteobridge PRO fails or the USB data store fails or if data is lost there for any reason? As storing backups of the data onto the internal USB storage does not make too much sense we decided to support inserting an external USB stick to one of the USB connectors and to use that for backups. Meteobridge PRO allows you to automatically store data on the external USB stick as long as it is inserted. When capacity is filled up, oldest backups on the stick are automatically erased to make room for new backups. So you don't have to take care about how to keep free storage on the Backup USB stick.

Backups can be initiated immediately with the "Backup" button on "system" tab or can be programmed as a service as follows.

Picture on the right shows a typical backup definition. Backups are realized as a special script service, that can be typically activated each day or each month. When a micro USB stick is used, this can even stay plugged into the front panel USB connector without blocking display view.

All backuop operations will be logged in messages section of "system" tab.


Restore from an inserted USB stick can be simply done by using the drop-down list "Restore from..." on "system tab. Operation will also be logged in messages section of "system" tab.

Cleanup of History Data

While Meteobridge just stores average, minimum and maximum values for the current day, yesterday, current month, current year and all time, the new Meteobridge PRO does store data from sensors in a per minute resolution from when you started using Meteobridge PRO. The "History" tab gives you access to all this data and allows you to change, create or delete data on this per minute time resolution. To make yo familiar with how to work with this data, we will run through the use case "How to delete a spike in rain fall caused by cleaning the rain sensors funnel by pouring water through it?".

Find Data to be Corrected

We still remember that rain funnel cleaning was done in December 2015, but not exact day and time. When looking at the year view on rain data (sensor "rain0total") we see that December indeed has a bit high rain readings (abt 60mm).


So we drill down into December 2015 and can see that December 7 has a peak with nearly 50 mm rain fall. Looks like this was the day the rain funnel was washed with water.


Next drill-down is on the hours of December 7 shows that we have a peak at 14h.


When reaching details of an hours all the minutes are listed as values to allow editing. Here we see that the false reading incident was at 14:33 (marked in orange when moving the mouse over it) and 14:34.


Edit Data Set

Editing is easy. Just click onto the value field you like to edit and you see a dialog opening where you can insert the right values. If you don't add a unit to your input, metric/ISO units are assumed. If you want to insert in imperial units, please add "in", "F", "inhg", "mph" to it. Meteobridge will then convert automatically. When you want the data to be displayed in imperial units as well, please set the "Use Imperial Units" mark on top of the "Edit Data" field. We decide to enter "0" for 14:33 into this dialog.

When having inserted "0" and having pressed enter the screen updates and applies your correction. As you see, rain value has changed to "0.0mm" on 14:33.


As we are bored to repeat that with the false reading next to it (14:34) we decide just to delete this reading. Deletion can be done by clicking onto the time stamp. When moving the mouse over it a balloon help is shown.


After clicking the time stamp this dialog appears to prevent you from deleting data by accident.


When this is done, false reading for December 7 is corrected and monthly rain report looks like this.


New "Large" Weather Data Screens

Meteobridge PRO can make use of its display to show weather data. Yes, you know that, but I think you might be interested in the new, just rolled-out templates "BIG-scroll-IMP" and "BIG-scroll-ISO", which show data with larger digits. Video to the right shows a full run-through of the screens. Please ignore the flickering, which is a camera artifact only. This time we made a bit more used of the graphical capabilities of the display. Wind direction is illustrated by an oriented line in a circle. You might ask, when first temp curves show up? We'll see ;-) As you might expect having these 8 screens defined is not done before breakfast, but it is also no rocket science. When you are keen for all the details, please have a look at the wiki section "PRO Display". Code below shows the definition of one screen you see on the right.

It starts with a clean up of the screen, then "Helvetica 14pt bold" is selected as font, a white rounded box is drawn with black text "WIND" inside and the white text "mph" to the right.

*addloop b3 5 300 \
  #font helvB14\n\
  #color 1\n\
  #rbox 0 0 70 18 5\n\
  #color 0\n\
  #string 8 16 WIND\n\
  #color 1\n\
  #string 85 16 mph\n\
  #font fub30\n\
  #string 0 60 [wind0wind-avg1=mph.1:--]\n\
  #circle 105 43 20\n\
  #if#[wind0avgwind-act.1:0.0]#then##pline 105 43 20 [wind0dir-act.0:0]\n#else##fi##disc 105 43 4

Then font is changed to "Free Universal 30pt bold" (fub30) and average wind speed of last minute is displayed in mph and with one decimal resolution. On the right side of this a circle (center 105/43, radius 20) is drawn. If average wind speed of last minute is not zero then a line starting from the center of the circle with length 20 is drawn oriented by the current wind direction. The last step draws a small filled disc into the center of the circle. How #if# #then# #else# #fi# statements operate is explained at the end of "Templates" section of the wiki.

Data Import

Meteobridge PRO and NANO SD allow to import data in various formats. In order to import data it needs you the locate the files in the PC network folder "import" on the Meteobridge. This is needed as the import can take quite some time and the browser session will not be able to feed the data for longer time periods.

An easy way to upload the import file onto the Meteobridge might be to browse to "http://ip-of-your-meteobridge/upload.html". Being there you can do the upload to the "import" folder with a few clicks in your browser.

Meteohub Raw

this options allows to import the monthly raw data files from your Meteohub system to be imported. You find the files in the folder "/Data/weather/YYYYMM" folder, where YYYY defines the year and MM the month. Inside the folder you find a file named "raw" which holds the data for the selected month.

Meteoplug Export

On the "Inspect Data" tab of your Meteoplug account you have the option to export the data for a given month. The downloaded file can directly be imported into the Meteobridge.


Beside predefined special formats Meteobridge also supports a generic format named "direct" that takes a file where each line is in the following format
<epoch time stamp> <sensor name> <sensor value>

As an example, the line "1546326000 wind0wind 13.5" tells Meteobridge that wind speed was 13.5 m/s at Jan 1, 2019 on 8:00 AM local time in Germany (which is 7:00 AM GMT). Epoch time stamp is Unix convention and should be easy to produce from any local time stamp. Sensor name is as explained in template section and you also see these names on "Live Data" tab. The sensor value is in metric units (°C, mm, mm/h, hPa, m/s). Each line needs to be delimited by a line feed character (0x0A).


1546326000 wind0wind 13.5
1546326000 wind0dir 238
1546326000 wind0avgwind 5.4
1546326000 wind0chill 5.6
1546326005 th0temp 8.2
1546326005 th0hum 38
1546326005 th0dew -5.3
1546326010 thb0temp 25.6
1546326010 thb0hum 50
1546326010 thb0dew 14.4
1546326010 thb0press 1008.5
1546326010 thb0seapress 1010.3
1546326015 rain0rate 2.3
1546326015 rain0total 4.5
1546326020 uv0index 1.6
1546326025 sol0rad 355


Cumulus imports are expected to be a sql dump format like

INSERT INTO `Monthly` (`LogDateTime`, `Temp`, `Humidity`, `Dewpoint`, `Windspeed`, `Windgust`, `Windbearing`, `RainRate`, `TodayRainSoFar`, `Pressure`, `Raincounter`, `InsideTemp`, `InsideHumidity`, `LatestWindGust`, `WindChill`, `HeatIndex`, `UVindex`, `SolarRad`, `Evapotrans`, `AnnualEvapTran`, `ApparentTemp`, `MaxSolarRad`, `HrsSunShine`, `CurrWindBearing`, `RG11rain`, `RainSinceMidnight`, `WindbearingSym`, `CurrWindBearingSym`) VALUES
('2018-11-30 22:45:00', '4.3', '86', '2.1', '4.0', '8.0', '223', '0.0', '1.2', '1001.66', '553.0', '21.2', '42', '2.0', '2.7', '4.3', '0.0', '0.0', '0.6', '560.4', '1.4', '0.0', '2.1', '213', '0.0', '1.2', 'SW', 'SSW'),
('2018-11-30 22:40:00', '4.3', '86', '2.1', '5.0', '12.0', '227', '0.0', '1.2', '1001.73', '553.0', '21.3', '42', '5.0', '2.3', '4.3', '0.0', '0.0', '0.6', '560.4', '1.1', '0.0', '2.1', '230', '0.0', '1.2', 'SW', 'SW'),
('2018-11-30 22:35:00', '4.3', '86', '2.1', '5.0', '12.0', '224', '0.0', '1.2', '1001.66', '553.0', '21.3', '42', '4.0', '2.3', '4.3', '0.0', '0.0', '0.6', '560.4', '1.1', '0.0', '2.1', '217', '0.0', '1.2', 'SW', 'SW'),
('2018-11-30 22:30:00', '4.3', '86', '2.1', '5.0', '12.0', '221', '0.0', '1.2', '1001.52', '553.0', '21.4', '42', '9.0', '2.3', '4.3', '0.0', '0.0', '0.6', '560.4', '1.1', '0.0', '2.1', '244', '0.0', '1.2', 'SW', 'WSW'),
('2018-11-30 22:25:00', '4.2', '86', '2.1', '5.0', '12.0', '218', '0.0', '1.2', '1001.56', '553.0', '21.5', '42', '3.0', '2.2', '4.2', '0.0', '0.0', '0.6', '560.4', '1.0', '0.0', '2.1', '250', '0.0', '1.2', 'SW', 'WSW'),
('2018-11-30 22:20:00', '4.1', '87', '2.1', '5.0', '12.0', '213', '0.0', '1.2', '1001.59', '553.0', '21.6', '42', '6.0', '2.1', '4.1', '0.0', '0.0', '0.6', '560.4', '0.9', '0.0', '2.1', '168', '0.0', '1.2', 'SSW', 'SSE'),
('2018-11-30 22:15:00', '4.1', '87', '2.1', '5.0', '12.0', '217', '0.0', '1.2', '1001.49', '553.0', '21.7', '41', '6.0', '2.1', '4.1', '0.0', '0.0', '0.6', '560.4', '0.9', '0.0', '2.1', '179', '0.0', '1.2', 'SW', 'S'),
('2018-11-30 22:10:00', '4.1', '86', '2.0', '4.0', '12.0', '218', '0.0', '1.2', '1001.52', '553.0', '21.7', '41', '2.0', '2.6', '4.1', '0.0', '0.0', '0.6', '560.4', '1.2', '0.0', '2.1', '248', '0.0', '1.2', 'SW', 'WSW')

or in a quoted export format like this:

"2016-04-20 23:15:00","6.6","89","4.9","0.0","1.0","254","0.0","0.0","1027.40","397.4","25.2","41","1.0","6.6","6.6","0.0","0.0","0.0","0.0","5.5","0.0","0.0","257","0.0","0.0","WSW","WSW"
"2016-04-20 23:20:00","6.4","89","4.8","0.0","1.0","256","0.0","0.0","1027.43","397.4","25.2","41","1.0","6.4","6.4","0.0","0.0","0.0","0.0","5.3","0.0","0.0","255","0.0","0.0","WSW","WSW"
"2016-04-20 23:25:00","6.3","89","4.7","0.0","1.0","256","0.0","0.0","1027.53","397.4","25.2","41","0.0","6.3","6.3","0.0","0.0","0.0","0.0","5.1","0.0","0.0","256","0.0","0.0","WSW","WSW"
"2016-04-20 23:30:00","6.3","89","4.6","0.0","2.0","259","0.0","0.0","1027.53","397.4","25.2","41","0.0","6.3","6.3","0.0","0.0","0.0","0.0","5.1","0.0","0.0","264","0.0","0.0","W","W"
"2016-04-20 23:35:00","6.2","89","4.5","1.0","2.0","264","0.0","0.0","1027.70","397.4","25.2","41","0.0","6.2","6.2","0.0","0.0","0.0","0.0","4.7","0.0","0.0","273","0.0","0.0","W","W"
"2016-04-20 23:40:00","6.2","89","4.5","1.0","2.0","263","0.0","0.0","1027.74","397.4","25.2","41","2.0","6.2","6.2","0.0","0.0","0.0","0.0","4.6","0.0","0.0","270","0.0","0.0","W","W"
"2016-04-20 23:45:00","6.2","89","4.5","0.0","2.0","260","0.0","0.0","1027.70","397.4","25.2","41","0.0","6.2","6.2","0.0","0.0","0.0","0.0","4.9","0.0","0.0","270","0.0","0.0","W","W"
"2016-04-20 23:50:00","6.2","89","4.5","0.0","2.0","270","0.0","0.0","1027.63","397.4","25.1","41","0.0","6.2","6.2","0.0","0.0","0.0","0.0","4.9","0.0","0.0","270","0.0","0.0","W","W"
"2016-04-20 23:55:00","6.1","89","4.4","0.0","1.0","270","0.0","0.0","1027.67","397.4","25.2","41","0.0","6.1","6.1","0.0","0.0","0.0","0.0","4.9","0.0","0.0","270","0.0","0.0","W","W"
"2016-04-21 00:00:00","6.1","89","4.4","0.0","1.0","270","0.0","0.0","1027.74","397.4","25.1","41","0.0","6.1","6.1","0.0","0.0","0.0","0.0","4.9","0.0","0.0","270","0.0","0.0","W","W"
"2016-04-21 00:05:00","6.1","89","4.4","0.0","1.0","270","0.0","0.0","1027.84","397.4","25.1","40","0.0","6.1","6.1","0.0","0.0","0.0","0.0","4.8","0.0","0.0","270","0.0","0.0","W","W"
"2016-04-21 00:10:00","6.1","89","4.4","0.0","1.0","270","0.0","0.0","1027.87","397.4","25.1","40","0.0","6.1","6.1","0.0","0.0","0.0","0.0","4.8","0.0","0.0","270","0.0","0.0","W","W"
"2016-04-21 00:15:00","5.9","88","4.1","0.0","1.0","270","0.0","0.0","1027.87","397.4","25.1","40","0.0","5.9","5.9","0.0","0.0","0.0","0.0","4.6","0.0","0.0","269","0.0","0.0","W","W"
"2016-04-21 00:20:00","5.8","88","4.0","0.0","0.0","0","0.0","0.0","1027.87","397.4","25.0","40","0.0","5.8","5.8","0.0","0.0","0.0","0.0","4.5","0.0","0.0","270","0.0","0.0","N","W"

Data is to be expected in the comma separated sequence as shown above, no variations are allowed.


Meteotemplate imports are expected to be a sql dump format like

INSERT INTO `alldata` (`DateTime`, `T`, `Tmax`, `Tmin`, `H`, `D`, `W`, `G`, `B`, `RR`, `R`, `P`, `S`, `A`) VALUES
('2010-01-01 00:04:00', '-0.4', '-0.4', '-0.4', '81.0', '-3.3', '9.7', '9.7', '269.0', '0.000', '0.000', '1005.600', '0.0', '-4.7'),
('2010-01-01 00:09:00', '-0.6', '-0.6', '-0.6', '81.0', '-3.5', '16.7', '16.7', '265.0', '0.000', '0.000', '1006.000', '0.0', '-6.3'),
('2010-01-01 00:14:00', '-0.6', '-0.6', '-0.6', '82.0', '-3.3', '16.7', '16.7', '262.0', '0.000', '0.000', '1006.000', '0.0', '-6.3'),
('2010-01-01 00:19:00', '-0.7', '-0.7', '-0.7', '82.0', '-3.4', '13.0', '13.0', '262.0', '0.000', '0.000', '1006.000', '0.0', '-5.7'),
('2010-01-01 00:24:00', '-0.7', '-0.7', '-0.7', '83.0', '-3.3', '14.8', '14.8', '262.0', '0.000', '0.000', '1006.000', '0.0', '-6.0'),
('2010-01-01 00:29:00', '-0.7', '-0.7', '-0.7', '83.0', '-3.3', '16.7', '16.7', '261.0', '0.000', '0.000', '1006.000', '0.0', '-6.4'),
('2010-01-01 00:34:00', '-0.7', '-0.7', '-0.7', '83.0', '-3.3', '11.1', '11.1', '261.0', '0.000', '0.000', '1005.600', '0.0', '-5.3'),
('2010-01-01 00:39:00', '-0.7', '-0.7', '-0.7', '83.0', '-3.3', '13.0', '13.0', '261.0', '0.000', '0.000', '1005.600', '0.0', '-5.6'),
('2010-01-01 00:44:00', '-0.7', '-0.7', '-0.7', '83.0', '-3.3', '9.7', '9.7', '261.0', '0.000', '0.000', '1005.600', '0.0', '-5.0'),
('2010-01-01 00:49:00', '-0.7', '-0.7', '-0.7', '83.0', '-3.3', '9.7', '9.7', '261.0', '0.000', '0.000', '1005.600', '0.0', '-5.0')

or in a quoted export format like this:

"2010-01-01 00:04:00","-0.4","-0.4","-0.4","81.0","-3.3","9.7","9.7","269.0","0.000","0.000","1005.600","0.0","-4.7"
"2010-01-01 00:09:00","-0.6","-0.6","-0.6","81.0","-3.5","16.7","16.7","265.0","0.000","0.000","1006.000","0.0","-6.3"
"2010-01-01 00:14:00","-0.6","-0.6","-0.6","82.0","-3.3","16.7","16.7","262.0","0.000","0.000","1006.000","0.0","-6.3"
"2010-01-01 00:19:00","-0.7","-0.7","-0.7","82.0","-3.4","13.0","13.0","262.0","0.000","0.000","1006.000","0.0","-5.7"
"2010-01-01 00:24:00","-0.7","-0.7","-0.7","83.0","-3.3","14.8","14.8","262.0","0.000","0.000","1006.000","0.0","-6.0"
"2010-01-01 00:29:00","-0.7","-0.7","-0.7","83.0","-3.3","16.7","16.7","261.0","0.000","0.000","1006.000","0.0","-6.4"
"2010-01-01 00:34:00","-0.7","-0.7","-0.7","83.0","-3.3","11.1","11.1","261.0","0.000","0.000","1005.600","0.0","-5.3"

Data is to be expected in the comma separated sequence as shown above, no variations are allowed.


Weewx imports are expected to be in this format



WSWIN imports are expected to be in this format

Datum;Zeit;Temp. I.;Außentemp.;Temp. A. min;Temp. A. max;BodenTemp;Feuchte I.;Feuchte A.;Luftdruck;Niederschl.;Wind;Richtung;Sonnenschein;ET;UV;Solar;Windböen;Empfang;GWD;W0;W1
#Calibrate=1.000 #Regen0=0mm #Location=411/411m #Baro_correction=48hPa #Station=Envoy

or in this format

Datum,Zeit,Temp. I.,Temp. A.,Temp. 2,Temp. 3,Temp. 4,Temp. A. min,Temp. A. max,Temp. 7,Bl.Temp 1,Bl.Temp 2,BodenTemp 1,BodenTemp 2,BodenTemp 3,BodenTemp 4,Feuchte I.,Feuchte A.,Feuchte 2,Feuchte 3,Feuchte 4,Feuchte 5,Feuchte 6,Feuchte 7,BlattFeu 1,BlattFeu 2,Bod.Feucht 1,Bod.Feucht 2,Bod.Feucht 3,Bod.Feucht 4,Luftdruck,Regen,Wind,Richtung,Sonnenschein,ET,UV,Solar,Windböen,Empfang,GWD,W0,W1
#Calibrate=1.000 #Regen0=0mm #Location=-301/-301m #Baro_correction=0hPa #Station=VantageProPlus

Placing values to the right sensor type is controlled by the type identification line directly preceding the data lines.