meteohub.de

DEUTSCH:

Update V4.5 (NSLU2, x86 und SheevaPlug) enthält die folgenden Änderungen gegenüber V4.4:

* Erweitert die Nutzungsperiode als Demoversion auf den 31.10.2009.
* Verbessert die Anzeige für niedrigen Batterieladestand einiger Sensoren in Verbindung mit RFXCOM Emfängern.
* Beseitigt einen Fehler bei der Übernahme von NSLU2 Einstellungen auf SheevaPlug.
* Senkt die Abnutzung des Flash-Speichers durch Reduktion von Schreibzyklen:
- Rohdaten werden intern gepuffert und nur noch alle 3 Minuten auf das Speichermedium geschrieben.
- Der minütliche watchdog-heartbeat wird auf die RAM-Disk anstelle des Flash-Speichers gerichtet.
* Auf der leistungsschwachen NSLU2 werden WD-Live Grafikdaten mit minütlicher Auflösung nur noch alle 3 Minuten erzeugt (betrifft nur die Grafikdaten).
* Beseitigt einen mit 4.4 eingeführten Fehler bei der Berechnung von Regentagen.
* Beseitigt einen Fehler in der Funktion "Grafiken hochladen" bei mehr als 128 Dateien im Ordner "/data/graphs/".
* Beseitigt einen Fehler bei der Auswertung des Regenfalls an WH-1080 Stationen.
* Verbessert die Erkennung von reinen Temp-Sensoren bei der WMR-200.
* Verlagert einige temporäre Dateien auf RAM-Disk, um die Schreibzyklen gegen den Flash-Speicher zu reduzieren.
* Reduziert das Logging im "system log" erheblich. CRON und THTTPD wird auf x86/SheevaPlug nicht mehr geloggt, auf NSLU2 wird der System log 5 Minuten nach dem Boot deaktiviert (Einschränkung der Dienste hier nicht möglich).
* Fügt für SheevaPlug eine optische Signalisierung der IP hinzu (blaue LED).
* Fügt für SheevaPlug Unterstützung für einige USB WLAN-Adapter hinzu (zd1211, rtl8187b, rt73).

--------------------------------------------
ENGLISH:

Update to Meteohub V4.5 (NSLU2, x86 and SheevaPlug) brings these new features compared to V4.4:

* Sets end date for demo period to 31th of October 2009.
* Improves low battery detection for some sensors in combination with RFXCOM receiver.
* Fixes a bug when porting settings from NSLU2 to SheevaPlug.
* Reduces wear of Flash storage by reduction of write cycles:
- raw data gets internally buffered and is written every 3 minutes to flash storage.
- watchdog-heartbeat writing every minute gets directed to RAM disk instead of flash storage.
* Low performing NSLU2 platforms do update WD-Live graphic data in one minute resolution just every 3 minutes (only affects graphic data).
* Fixes a bug in computation of rain days.
* Improves reading data from WH-1080 to avoid illegal rain values.
* Fixes a bug in function "graph uploads" with more than 128 files in folder "/data/graphs/".
* Improves recognition of pure temp sensors at WMR-200.
* Moves some temporary files to RAM disk in order to lower write cycles to flash memory.
* Significantly reduces logging into "system log". On x86 and SheevaPlug CRON und THTTPD are not logged any more, on NSLU2 system log gets disabled 5 minutes after boot (reduction/filter of logging cannot applied here).
* Adds optical signaling of IP to SheevaPlug (via blue LED).
* Adds support for USB WLAN sticks (zd1211, rtl8187b, rt73) on SheevaPlug.

--------------------------------------------

Update Link:
http://www.meteohub.de/joomla/index.php ... &Itemid=29

NSLU2 USB Stick Image 4GB:
http://www.meteohub.de/joomla/index.php ... &Itemid=29

NSLU2 USB Stick Image 2GB:
http://www.meteohub.de/joomla/index.php ... &Itemid=29

X86 Installation USB Stick Image: http://www.meteohub.de/joomla/index.php ... &Itemid=29

SheevaPlug SD card Image 4GB:
http://www.meteohub.de/joomla/index.php ... &Itemid=29

VMware Image 4GB:
http://www.meteohub.de/joomla/index.php ... &Itemid=29

Version 4.5 summarizes all changes since 4.4 and provides fresh images for installation from scratch on NSLU2, x86, SheevaPlug and VMware.

admin wrote:Version 4.5 summarizes all changes since 4.4 and provides fresh images ...

So there's no point (no new features or bug fixes?) in updating if already on 4.4D then?

Right. I made a step to 4.5 mainly to generate a set of new images for fresh meteohub installation with a new demo period (old one has ended 31th August).

I just updated to 4.5 and now every morning at around 4:10MST, meteohub stops updating wunderground. When I log in and take a look everything looks correct. The software did not loose connection with the station and the sensors are still reporting. The only way to get it to start reporting is to do a reboot of meteohub. Any ideas on what change?

Thanks
Dave

strange...
Do you have an internet shut down at the same time? Many providers cut lines every 24h.

Does just rapid fire stop or even regular updates without rapid file?

What platform? NSLU2 can have USB stick problems. I don't want to blame each problem to USB stick failure but 90% of situations where a NSLU2 acts stange USB stick turns out to be the root cause. Any errors in "dmesg" log file?

No even though I have a static IP addy it has not change since day one and that was about 4 years now. I'm always connected.

I have not tried to disable the rapid fire. I will give that a try tonight.

I'm running meteohub as VMware. No USB sticks are involved.

I was doing some troubleshooting today to figure out why it is hanging up at 4:10am and I notice that the clock under the settings was not set correctly. I reset it to the correct time and when it reloaded it show the time had passed almost 10 minutes when it was only a few seconds. Why is the clock speeding up? Again I'm running this on VMware

is NTP not working under VMware?
In that case your recorded data may also suffer from the time shift. Does it?

dcspicer wrote:I was doing some troubleshooting today to figure out why it is hanging up at 4:10am and I notice that the clock under the settings was not set correctly. I reset it to the correct time and when it reloaded it show the time had passed almost 10 minutes when it was only a few seconds. Why is the clock speeding up? Again I'm running this on VMware

I can't remember any detail, but I vaguely recall that are circumstancs where there can be problems associated with a VMware VM trying to maintain its own time independent of the host computer - though I thought that was a "time slows" thing rather than jumping forward? I think a bit of googling may be in order...

Recent VMware software should have this fixed. At least for me this bug was fixed by some updates in VMware about 6 months ago.

What VMware version are you using?

I'm running VMware Workstation ACE Edition version 6.0.5 build 109488. I check for updates and there is none available.

I do not know what I've done with the system but now the time is staying correct and everything is being updated. So for now my problem has been fixed.

I have problem with nslu2.

Scheduled Reboot is set to weekly but still every night at 0:00 it reboots..

Not sure if you are able to login to meteohub using the commandline. If you can issue the following command:
crontab -l |grep shutdown

On my system this gives the following output:
37 2 * * * /usr/bin/test -f /home/meteohub/autoreboot && echo norecompute >/home
/meteohub/norecompute && /sbin/shutdown -r -n now
0 3 1 * * /bin/echo "norecompute" >/home/meteohub/norecompute && /sbin/shutdown
-n -r now
(it might show up as more lines in explorer, but it's really 2 lines).

It's the second line that you are interested in:
0 = minutes of the hour
3 = hour
1 = day of the month
* = Month; every month
* = day of the week; every weekday
The last might be confusing, it says that it doesn't really matter which weekday it is, as long as it is the 1st day of the month.

I know from experience that this was not always working in previous versions; this is version 4.5 output.