meteohub.de

Posted: **Tue Apr 12, 2011 4:19 pm**

time sync still working with 4.7e, because my meteohub clock is completely accurate.
I guess not all ntp requests are logged into ntp.log, because even with versions earlier than 4.7e, there are time gaps of 2 or 5 days

25 Mar 01:34:25 ntpdate[2209]: step time server 192.53.103.108 offset 0.000649 sec
25 Mar 01:34:26 ntpd[2211]: frequency initialized -3.857 PPM from /data/log/ntp.drift
25 Mar 01:38:45 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 01:38:45 ntpd[2211]: kernel time sync enabled 0001
25 Mar 02:15:30 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 02:44:02 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 02:50:46 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 03:06:54 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 03:42:19 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 03:49:52 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 03:58:27 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 04:01:42 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 04:14:42 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 04:46:54 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 04:53:23 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 05:17:10 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 05:25:47 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 05:29:02 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 05:41:41 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 06:05:32 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 06:17:16 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 06:25:52 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 06:36:31 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 06:40:56 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 06:52:37 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 06:56:58 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 07:13:02 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 07:36:46 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 07:58:03 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 08:10:52 ntpd[2211]: time reset -0.225385 s
25 Mar 08:15:14 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 08:27:09 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 08:27:09 ntpd[2211]: time reset +0.225892 s
25 Mar 08:31:41 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 09:30:31 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 09:36:55 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 12:31:17 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 13:22:31 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
25 Mar 23:03:09 ntpd[2211]: synchronized to 87.106.176.225, stratum 2
25 Mar 23:57:21 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
1 Apr 01:34:24 ntpdate[2211]: step time server 192.53.103.108 offset 0.023273 sec
1 Apr 01:34:25 ntpd[2215]: frequency initialized -1.025 PPM from /data/log/ntp.drift
1 Apr 01:38:44 ntpd[2215]: synchronized to 204.9.54.119, stratum 1
1 Apr 01:38:44 ntpd[2215]: kernel time sync enabled 0001
5 Apr 15:58:37 ntpdate[2423]: step time server 192.53.103.108 offset -0.003369 sec
5 Apr 15:58:38 ntpd[2428]: frequency initialized 6.893 PPM from /data/log/ntp.drift
5 Apr 16:02:59 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 16:02:59 ntpd[2428]: kernel time sync enabled 0001
5 Apr 17:14:46 ntpd[2428]: time reset -0.149337 s
5 Apr 17:19:37 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 17:33:37 ntpd[2428]: synchronized to 85.214.230.247, stratum 2
5 Apr 17:48:33 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 18:48:31 ntpd[2428]: synchronized to 85.214.230.247, stratum 2
5 Apr 18:48:31 ntpd[2428]: time reset -0.138044 s
5 Apr 18:53:29 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 18:58:05 ntpd[2428]: synchronized to 85.214.230.247, stratum 2
5 Apr 19:04:16 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 19:11:00 ntpd[2428]: synchronized to 85.214.230.247, stratum 2
5 Apr 19:21:41 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 19:46:04 ntpd[2428]: synchronized to 85.214.230.247, stratum 2
5 Apr 19:53:57 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 22:04:59 ntpd[2428]: synchronized to 85.214.230.247, stratum 2
5 Apr 22:12:09 ntpd[2428]: synchronized to 212.18.3.19, stratum 2
5 Apr 22:28:40 ntpd[2428]: synchronized to 85.214.230.247, stratum 2
8 Apr 01:34:21 ntpdate[2209]: step time server 178.26.105.100 offset -0.002532 sec
8 Apr 01:34:22 ntpd[2211]: frequency initialized -61.239 PPM from /data/log/ntp.drift
8 Apr 01:38:41 ntpd[2211]: synchronized to 72.18.205.156, stratum 3
8 Apr 01:38:41 ntpd[2211]: kernel time sync enabled 0001
8 Apr 01:43:02 ntpd[2211]: synchronized to 46.4.54.78, stratum 2
10 Apr 06:27:25 ntpdate[2270]: step time server 131.234.137.24 offset -0.006224 sec
10 Apr 06:27:25 ntpd[2272]: frequency initialized -21.648 PPM from /data/log/ntp.drift
10 Apr 06:31:41 ntpd[2272]: synchronized to 188.40.77.71, stratum 2
10 Apr 06:31:41 ntpd[2272]: kernel time sync enabled 0001
10 Apr 06:38:16 ntpd[2272]: synchronized to 188.193.207.174, stratum 2
10 Apr 10:21:33 ntpd[2272]: time reset -0.160701 s
10 Apr 10:25:55 ntpd[2272]: synchronized to 188.40.77.71, stratum 2
10 Apr 10:31:19 ntpd[2272]: synchronized to 188.193.207.174, stratum 2
10 Apr 21:35:00 ntpd[2272]: synchronized to 188.40.77.71, stratum 2
10 Apr 22:34:13 ntpd[2272]: synchronized to 188.193.207.174, stratum 2

Posted: **Tue Apr 12, 2011 4:26 pm**

Thanks for that update, I guess it is a logging problem rather than an NTP problem.

Posted: **Thu Apr 14, 2011 2:59 pm**

Hi Boris

Further to my recent post regarding SeaLevel / Altitude Pressure reporting in APRS / CWOP
I have done some more research and have found

It's a "Can of Worms" with people taking sides

APRS does not appear to mandate either setting
CWOP expects altitude pressure but a check of 40 CWOP stations in Northern England
shows 100% indicating SeaLevel pressure

Some "other" WX station softwares allow for this by providing a simple "Send Altitude Pressure"
Checkbox within the program and leaving the decision to the user

For the Altitude Pressure to be of use the Station Altitude needs to be sent
The APRS spec allows for sending the Altitiude using the format /A=xxxxxx where xxxxxx is the station
altitude (in FEET)
Meteohub already has this info as an attribute of the Weather Station

This information would be also be useful to other users (and me) when comparing temperatures and windspeeds
from distant stations

Below are a couple of packets from APRS showing stations using the format /A=

2E1ICB-9>APRS,TCPIP*,qAC,T2TEXAS:@301021z5322.89N/00000.77Wv169/030/A=000127 www.truckcam.tv
G8KDM>APDPRS,DSTAR*,qAR,GB7SF-C:!5317.52N/00117.31Wp042/000 ALAN /A=000491

These packets are correctly decoded and displayed by sites such as aprs.fi

Just my two pfennigs worth

Cheers

GREBO

Posted: **Fri Apr 15, 2011 10:36 pm**

On 4.7e my Meteohub uses two (2) IP adresses

It's configured to use static 192.168.1.15 but it also responds "nicely" on 192.168.1.77. I can login, see all webpages, ping it and so on on both addresses.

Posted: **Sat Apr 16, 2011 12:37 am**

Having 2 IPs is normal behavior. Meteohub is always avail at 192.168.1.77 beside the IP you have given to it.
This is a feature Linux gives to you, so don't be worried.

Posted: **Sat Apr 16, 2011 10:49 am**

Despite it being normal, is it possible to disable the .77 address? It's visually/mentally annoying to have two IP addresses for the same device when it's not needed.

What is the reason for the .77 address?

Posted: **Sat Apr 16, 2011 3:39 pm**

When you misconfigure your IP, you can always login at 192.168.1.77.
This has been proven to be very useful in various situations.

Posted: **Thu May 19, 2011 3:27 pm**

Mr Pasternak:

Thank you for changing the CWOP data push from sea-level pressure to altimeter pressure. It took about four weeks for the erroneous data to completely age-out of the MADIS system, then another two weeks to get a green check mark and one green "thumbs up". If I don't get a second green "thumbs up", I suspect it will be due to my weather station's non-standard siting. Thanks again!

meteohub.de

Update 4.7e

Re: Update 4.7e

Re: Update 4.7e

Re: Update 4.7e - APRS Pressure

Re: Update 4.7e

Re: Update 4.7e

Re: Update 4.7e

Re: Update 4.7e

Re: Update 4.7e