Date   
not yet perfect, but...

Ulrich G. Kliegis
 

... at least something visible..
pls have a look at

http://eumetmon.rummelecke.de/

I'll change the 2.columns-design to single and will apply a few more touches
- also including your suggestions.

I'd like to add a link to David's page - what would be the optimal link
address, David? You should - if you haven't already, provide a ready-2-
implant banner that people using your software could add to their pages and
linklists... Maybe, if you find the time... :)

Cheers, and again thanks to all who were actively or just mentally engaged
:)

U.

Re: not yet perfect, but...

David J Taylor
 

... at least something visible..
pls have a look at

http://eumetmon.rummelecke.de/

I'll change the 2.columns-design to single and will apply a few more touches
- also including your suggestions.
That's great, Ulrich. That page is entirely under your control and can reflect the personality of your system.

I'd like to add a link to David's page - what would be the optimal link
address, David? You should - if you haven't already, provide a ready-2-
implant banner that people using your software could add to their pages and
linklists... Maybe, if you find the time... :)

Cheers, and again thanks to all who were actively or just mentally engaged
:)

U.
I'd like to know your dish size, Ulrich, so that I can ensure that the information I'm just editing can be accurate.

Yes, it would be nice to have a "Powered by SatSignal Software" logo or something!

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Mon, 28 Feb 2011 13:24:59 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

I'd like to know your dish size, Ulrich, so that I can ensure that the
information I'm just editing can be accurate.
It's the Wavefrontier T90 toroidal monster (the one with not only the smallest
waf, but even minimum rofaf (rest of family acceptance factor)), but i like the
dBs :) . Nominally 90 cm diameter. It looks larger, though.

The signal quality and strength could become even more robust - I did not
feel like readjusting it after the gales we had her some weeks ago. EB9 is
back (it's in the center position) (see my earlier posting on that), but the TV
progs from Astra and Hotbird are not yet, so I guess it's a degree or one and
a half that it is still off it's peak level. Persisting ice and snow kept me off
readjusting it.

Cheers,
U.

Re: not yet perfect, but...

David J Taylor
 

It's the Wavefrontier T90 toroidal monster (the one with not only the smallest
waf, but even minimum rofaf (rest of family acceptance factor)), but i like the
dBs :) . Nominally 90 cm diameter. It looks larger, though.
Thanks, I've updated that.

The signal quality and strength could become even more robust - I did not
feel like readjusting it after the gales we had her some weeks ago. EB9 is
back (it's in the center position) (see my earlier posting on that), but the TV
progs from Astra and Hotbird are not yet, so I guess it's a degree or one and
a half that it is still off it's peak level. Persisting ice and snow kept me off
readjusting it.

Cheers,
U.
I hope you will be able to tweak it when the weather is better - today would be an ideal day here, glorious sunshine and all of +6C outside!

I've added your data to these pages:

http://www.satsignal.eu/mrtg/performance_eumetcast-europe.php
http://www.satsignal.eu/mrtg/EumetcastEurope_throughput.php

Could I ask that the throughput graphs be made 600 pixels wide, by setting XSize=500:

http://eumetmon.rummelecke.de/windbuedel_dvb.html

I found the easiest way to ensure consistency is with include files, using the common setting for time zone and number of points - so in mrtg.cfg, for example:

___________________________________________
.
.
# These are default values
XSize[_]: 500
Timezone[_]: GMT
.
.
Include: cpu.inc
Include: eumetcast.inc
Include: disk.inc
.
.
___________________________________________


Thanks,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Mon, 28 Feb 2011 15:44:06 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

Could I ask that the throughput graphs be made 600 pixels wide, by
setting XSize=500:
David, the graphs should be 600 pixels wide now. There seem to be two
ways to achieve that: a), as you mentioned, setting xsize (100 less than the
desired width) b) there is an CLI option for the perl - indexmaker program
contained in the package that allows to set the width as well - whereas I am
not sure if that would just rescale the png file.

So, please check the new size now. As you see, I also arranged them in one
column now.

I was irritated by the short SNR reduction at 11:40 UT today, then saw that
others had registered that too, but those farther in the south to a lesser til no
extent. Sun-colinearity with EB9?

BTW, I started mrtg with wperl instead of perl now, one window less, and no
accidental killing of the monitoring.

Cheers,
U.

Re: not yet perfect, but...

David J Taylor
 

David, the graphs should be 600 pixels wide now. There seem to be two
ways to achieve that: a), as you mentioned, setting xsize (100 less than the
desired width) b) there is an CLI option for the perl - indexmaker program
contained in the package that allows to set the width as well - whereas I am
not sure if that would just rescale the png file.

So, please check the new size now. As you see, I also arranged them in one
column now.
Yes, that's fine. Using the XSize means that that actual image will be 600 pixels, and it's not rescaled from 500 pixels. I haven't used the indexmaker program you mention. It would be nice if you could let the throughput graph rescale automatically, though. Here's the essence of what I have:

_____________________________________________
Target[Alta_DVB]: 15:public@Alta
MaxBytes[Alta_DVB]: 12500000
Options[Alta_DVB]: unknaszero, growright, noo
.
._____________________________________________


I was irritated by the short SNR reduction at 11:40 UT today, then saw that
others had registered that too, but those farther in the south to a lesser til no
extent. Sun-colinearity with EB9?

BTW, I started mrtg with wperl instead of perl now, one window less, and no
accidental killing of the monitoring.

Cheers,
U.
Yes, that's co-linearity at your end with EB9. You could even compare the times and the depths to track the sun across Europe!

I set the taskbar to auto-hide, so I don't normally see the MRTG window. I set the icon to be the MRTG icon rather than the command-prompt icon, to further reduce the chance of closing the wrong window.

I'm sure others will find your monitoring useful, as you are now the only station in Germany. I was surprised to find you so far north, actually! We pass through the Kiel Kanal in later May, overnight and not stopping unfortunately, but will will give you a wave!

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Mon, 28 Feb 2011 21:40:18 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

We pass through the Kiel Kanal in later May, overnight and not
stopping unfortunately, but will will give you a wave!
Just give me a shout in time, a view of the locks is 5 minutes walk from
here.
I just finished doing the re-scaling and re-labeling work, should match your
preferences now too.

My maxbytes is set to 5.000.000 now, which is 40 Mbits/s. Average values
seem to be far from that.

The "unscaled" command seems to do just the opposite, or am I logically
mirrored? My understanding was that "scaled" would refer to the maxbytes
value, uncaled to no fixed value. It works just the other way round, I think.
But I never understood sys admins, so, don't worry... :)

I have to apologize too for getting behind in the updating of the german
versions. Let's communicate that in PMs please in the next time...

Who said too many ideas too little time here some hours ago?

;)
Cheers,
U.

Re: not yet perfect, but...

David J Taylor
 

Just give me a shout in time, a view of the locks is 5 minutes walk from
here.
I'll let you know nearer the time.

I just finished doing the re-scaling and re-labeling work, should match your
preferences now too.

My maxbytes is set to 5.000.000 now, which is 40 Mbits/s. Average values
seem to be far from that.

The "unscaled" command seems to do just the opposite, or am I logically
mirrored? My understanding was that "scaled" would refer to the maxbytes
value, uncaled to no fixed value. It works just the other way round, I think.
But I never understood sys admins, so, don't worry... :)

I have to apologize too for getting behind in the updating of the german
versions. Let's communicate that in PMs please in the next time...

Who said too many ideas too little time here some hours ago?

;)
Cheers,
U.
May I ask, Ulrich, that you revert to bytes per second? Whilst I agree that bits/second may be a more logical unit in this case, as virtually all the other graphs are in bytes, having your in bytes as well makes for an easier comparison. Don't worry about the scaling, as it's now OK.

"Unscaled" - means "don't alter the scaling to match the data", so "AGC off" if you like.

When you have time to update the German translations, just get in touch, but there haven't been any major changes, as far as I know, just a few extra words and phrases.

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Tue, 1 Mar 2011 08:03:13 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

May I ask, Ulrich, that you revert to bytes per second? Whilst I
agree that bits/second may be a more logical unit in this case, as
virtually all the other graphs are in bytes, having your in bytes as
well makes for an easier comparison.
No problem - I'll look at it in the afternoon. I guess I'll just have to pluck the
"bits" out of the option parameters, right?

Cheers,
U.

Re: not yet perfect, but...

David J Taylor
 

May I ask, Ulrich, that you revert to bytes per second? Whilst I
agree that bits/second may be a more logical unit in this case, as
virtually all the other graphs are in bytes, having your in bytes as
well makes for an easier comparison.
No problem - I'll look at it in the afternoon. I guess I'll just have to pluck the
"bits" out of the option parameters, right?

Cheers,
U.
Yes, see:

http://oss.oetiker.ch/mrtg/doc/mrtg-reference.en.html

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

Set back to bytes / s.
I think the bits/ s was imported from the helpful cfg example I received from
where the other bit-pit is still visible -

I also purged the ytics=3 in the dvb-section but it stayed like it is.

Cheers,
U.

May I ask, Ulrich, that you revert to bytes per second? Whilst I
agree that bits/second may be a more logical unit in this case, as
virtually all the other graphs are in bytes, having your in bytes as
well makes for an easier comparison. Don't worry about the scaling,
as it's now OK.

Re: not yet perfect, but...

David J Taylor
 

Set back to bytes / s.
I think the bits/ s was imported from the helpful cfg example I received from
where the other bit-pit is still visible -
Yes, I noticed! <G>

I also purged the ytics=3 in the dvb-section but it stayed like it is.

Cheers,
U.
The 3-ticks has gone in most of the graphs, but the yearly graph is only updated once a day, unless you delete the PNG files, and restart MRTG or wait for its next run. I can see that I must update your location, as you've now given it more accurately on the page:

http://eumetmon.rummelecke.de/windbuedel_dvb.html

Many thanks for setting this up. I know that EUMETSAT do look at the pages and take an interest in them.

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Tue, 1 Mar 2011 14:18:23 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

Many thanks for setting this up. I know that EUMETSAT do look at the
pages and take an interest in them.
Glad to be able to feed them something back ;)

It's rewarding to see that something like that can be accomplished and
finished in a few days. If one considers the involved technology down to the
transistor level - surprising that it works, somehow miraculous.

Thanks again for your assistance, and - hey folks, it's fun, we might like to
see some more greens growing.

Cheers,
U.

Re: not yet perfect, but...

James Brown
 

I can see that I must update your location, as
you've now given it more accurately on the page:
David - I notice on your monitoring page there is the option for WX data if there is a home weather station - if you wish you could add the one below to the Porthcawl one - it is updated every 10 minutes and runs 24/7.

Cheers

James

http://www.meteosat.co.uk/Porthcawl/

--
James Brown

Re: not yet perfect, but...

David J Taylor
 

David - I notice on your monitoring page there is the option for WX data
if there is a home weather station - if you wish you could add the one
below to the Porthcawl one - it is updated every 10 minutes and runs
24/7.

Cheers

James

http://www.meteosat.co.uk/Porthcawl/
Added - ISS pass due now!

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

James Brown
 

In message <DC907E03EB364CD0A76FC62CDA375CA7@narvik>, David J Taylor <gm8arv@...> writes
David - I notice on your monitoring page there is the option for WX data
if there is a home weather station - if you wish you could add the one
below to the Porthcawl one - it is updated every 10 minutes and runs
24/7.

Cheers

James

http://www.meteosat.co.uk/Porthcawl/
Added - ISS pass due now!

Cheers,
David
Thanks David - 8 octa's of cloud here :-((

I've also changed the MRTG to read bytes now as per your suggestion .

Thanks again,

James
--
James Brown

cma

duncan
 

Hi From this morning i have just started to recieve CMA and all was well for a couple of hours with no problems until i came back to the pc and noticed that i had a string of red Ts and one pink T all data had stopped so i looked at the ramdisc which i have set at 299mb and it had 260mb left so was not full .i dont know if i have set the file_database_size correct maybe this is the problem i would apreciate the size i need to set if possible.If i take out
[EUMETSAT Data Channel 11]all runs ok again any ideas would be apreciated Best Regards Duncan

Re: cma

Ian Deans
 

Duncan, if you have a RAMdisk of 299 Mb your file_database_size should be no more than 313 Mb and preferably between 310 and 313 Mb.

If your file_database_size is larger than your RAMdisk it will likely shutdown Tellique for a few seconds and start the RAMdisk full again and that will cause some losses. The size of your RAMdisk is actually 299 x 1024 divided by 1000 twice which equals 313.52 Mb.

However more of a worry is why your RAMdisk is being used up so quickly and you really need to find the reason for this.

Hope that helps.

Regards
Ian.

-----Original Message-----
From: Duncan Edwards
Sent: Wednesday, March 02, 2011 3:15 PM
To: MSG-1@...
Subject: [MSG-1] cma

Hi From this morning i have just started to recieve CMA and all was well for a couple of hours with no problems until i came back to the pc and noticed that i had a string of red Ts and one pink T all data had stopped so i looked at the ramdisc which i have set at 299mb and it had 260mb left so was not full .i dont know if i have set the file_database_size correct maybe this is the problem i would apreciate the size i need to set if possible.If i take out
[EUMETSAT Data Channel 11]all runs ok again any ideas would be apreciated Best Regards Duncan

re- cma

duncan
 

Ian Thanks for the quick reoply.I have set the ramdisk to 3100000. i had set it far to high at 320 so i guess this may cure it The ramdisk is still set at 299mb i have been runing since the lat reset at 3pm and it is now 4 pm the ramdisk shows 258 free of 299 so wee will see i dont think i have done anything out of the normal i like i say asked to have the CMA this morning so i could recieve the FY-2E data and it is working all ok it seems for now . I have never had this before Ian it was a pretty task bar. I will keep an eye on it all i have done is put the [EUMETSAT Data Channel 11]
target_directory=received
in my recv- channels . Thanks again Regards Duncan

re- cma

duncan
 

Just as a precaution here is a copy of my recv-channels. As i only receive a small portion of the data compaired to others i am wondering as Ian said "my ramdisk is filling up fast" if i may after all this time of recieving the data i may have something wrong here any comments would be apreciated. Best Regards Duncan

recv-channels.ini - TelliCast+TelliVision Client channel configuration file
#
# 2-4-3 10-10-2005
#
[EUMETSAT Data Channel 1]
target_directory=received

[EUMETSAT Data Channel 2]
target_directory=received

[EUMETSAT Data Channel 3]
target_directory=received

[EUMETSAT Data Channel 4]
target_directory=received

[EUMETSAT Data Channel 11]
target_directory=received

Metop AVHRR
[EPS-10]
target_directory=received&#92;EPS-10

NOAA 19 GAC
[EPS-15]
target_directory=received&#92;EPS-15



# target_directory: Directory for received files. The target_directory name
# is relative to the current working directory.
# syntax: target_directory=<directory>
# default: received

tmp_directory=receiving/tmp/files
# tmp_directory: If this parameter is given tc-recv will internally
# store/compose all received files within the given directory and
# later move them to the target directory.
# While this option requires an additional move operation it
# guarantees that all files appearing in the target directory are
# fully written to the file system.
# syntax: tmp_directory=<directory>
# default: undefined=off, but default value may be redefined in
# recv.ini




# Section per channel or channel group identified by channel name (wildcard
# "*" allowed at end of name)

#activate_ftp_forwarding=1
# activate_ftp_forwarding: Will activate FTP forwarding for the correctly
# received files according to the recv.ini [ftp_forwarding]
# parameters.
# syntax: activate_ftp_forwarding=<value of range>
# range: 0/1
# default: 0=off

#tmp_directory=receiving/tmp/files
# tmp_directory: If this parameter is given tc-recv will internally
# store/compose all received files within the given directory and
# later move them to the target directory.
# While this option requires an additional move operation it
# guarantees that all files appearing in the target directory are
# fully written to the file system.
# syntax: tmp_directory=<directory>
# default: undefined=off, but default value may be redefined in
# recv.ini

#tmp_prefix=.
# tmp_prefix: Like tmp_directory, but files are composed within the final
# target directories but stored with the given prefix in front of
# the normal filenames until the files are fully written.
# syntax: tmp_prefix=<file name start>
# default: undefined=off, but default value may be redefined in
# recv.ini

#tmp_suffix=.tmp
# tmp_suffix: Like tmp_prefix, but adding a suffix to the normal filenames
# until the files are fully written.
# syntax: tmp_suffix=<file suffix>
# default: undefined=off, but default value may be redefined in
# recv.ini