Date   

msg-2

hcwit <hcwit@...>
 

hallo i have a qestion how mus /can i update the software from msg-1
to msg-2 i dont no

gr hans


Re: Updates

James Brown
 

Just to comment that the main problem here was that in my use of the ramdisk I had put both the received and receiving folders onto the ramdisk - which works just fine - but when the 0.fsy increased to over 30Mb that plus the received updates killed the processing as it exceeded the ramdisk level. Now that I have increased that to 150Mb all is fine - though I don't know if the fsy will ever return to the previous low levels.

Cheers
James
--
James Brown


Re: AVHRR NOAA 17

Ian Deans <isdeans1.-_@...>
 

Thanks to all who replied --- appreciated. It would appear that the
missing NOAA 17 AVHRR segment was not a problem at this end, which is good
news. I will continue to monitor the occasional segment loss from Met-8 and
FSD.

Regards
Ian.

----- Original Message -----
From: "nigel heasman" <nigel_heasman@yahoo.co.uk>
To: <MSG-1@yahoogroups.com>
Sent: Sunday, May 21, 2006 1:18 PM
Subject: Re: [MSG-1] AVHRR NOAA 17


Hi Ian,
I didn't receive segments 7 AND 9 of that pass - but
the early morning NOAA18 (03:26 nominal time) pass was
complete as was every other pass since I did the
upgrade on the evening of the 19th. So, it looks (for
my setup at least) as if that was a problem further up
the line?
I will keep a close eye on the next few passes to see
if the problem repeats itself though.
regards
Nigel


Re: AVHRR NOAA 17

nigel heasman <nigel_heasman@...>
 

--- Ian Deans <isdeans1.-_@tiscali.co.uk> wrote:
Did anyone else see a missing segment on the first
NOAA 17 pass this morning
from Maspalomas ( the pass started at about 10.08 UTC)

I am monitoring my system at the moment as since
loading the new Tellique software and e token run time
I am seeing a small amount of segment loss,
something which has never been an issue before even
although I am only using 1 computer. I don't use a
ramdisk ( more trouble than they are worth.).

Regards
Ian.
--------------------------------------------------
Hi Ian,
I didn't receive segments 7 AND 9 of that pass - but
the early morning NOAA18 (03:26 nominal time) pass was
complete as was every other pass since I did the
upgrade on the evening of the 19th. So, it looks (for
my setup at least) as if that was a problem further up
the line?
I will keep a close eye on the next few passes to see
if the problem repeats itself though.
regards
Nigel


Re: AVHRR NOAA 17

Herman Vijlbrief <h.vijlbrief@...>
 

Ian,

I also have one missing segment.

Herman


Ian Deans schreef:

Did anyone else see a missing segment on the first NOAA 17 pass this morning from Maspalomas ( the pass started at about 10.08 UTC)

I am monitoring my system at the moment as since loading the new Tellique software and e token run time I am seeing a small amount of segment loss, something which has never been an issue before even although I am only using 1 computer. I don't use a ramdisk ( more trouble than they are worth.).

Regards
Ian.




Unsure what a term means? Check the Glossary at: http://www.david-taylor.myby.co.uk/wxsat/glossary.htm

Yahoo! Groups Links









Re: AVHRR NOAA 17

seggins2000 <seggins@...>
 

Ian,
Segment 9 of that pass was missing.
John Say

--- In MSG-1@yahoogroups.com, "Ian Deans" <isdeans1.-_@...> wrote:

Did anyone else see a missing segment on the first NOAA 17 pass
this morning
from Maspalomas ( the pass started at about 10.08 UTC)

I am monitoring my system at the moment as since loading the new
Tellique
software and e token run time I am seeing a small amount of segment
loss,
something which has never been an issue before even although I am
only using
1 computer. I don't use a ramdisk ( more trouble than they are
worth.).

Regards
Ian.


Re: Looking at the logs...

Ulrich G. Kliegis
 

On 21 May 2006 at 11:34, Ulrich G. Kliegis wrote:
Hope to be able to post some closing remarks
Unfortunately, not yet. BIOS, drivers, EKU and Eumetcast software
updated, but no difference. As a last resort with that mobo, I'll get a
separate USB PCI board tomorrow and will try that. If that doesn't work
then, the mobo will have to find a new home.

It seems that the mobo manufacturer stopped the development of new
Bioses for this specific board in 2001. Bad sign.

Cheers etc.,

U.


AVHRR NOAA 17

Ian Deans <isdeans1.-_@...>
 

Did anyone else see a missing segment on the first NOAA 17 pass this morning from Maspalomas ( the pass started at about 10.08 UTC)

I am monitoring my system at the moment as since loading the new Tellique software and e token run time I am seeing a small amount of segment loss, something which has never been an issue before even although I am only using 1 computer. I don't use a ramdisk ( more trouble than they are worth.).

Regards
Ian.


Re: Looking at the logs...

Ulrich G. Kliegis
 

On 20 May 2006 at 20:20, a_van_belle wrote:

Unfortunately I did have some problems years ago with 2 VIA mainboards
that almost drove me crazy. But once you have the latest BIOS and
found the correct chipset driver (and install sequence) it should not
be a problem. But make sure you do not install a Soundblaster Live in
a mobo with VIA 686 southbridge !
http://www.realworldtech.com/page.cfm?ArticleID=RWT042501034500
Arne,
again, thanks for that help that pointed me directly to the (most
probable) reason for that system's misbehaviour. I finally identified the
mobo as a DFI AK74-SC. Bios update and driver installation will
happen today (I've made it a habit to not touch relevant system parts at
night after some mishaps...)

The reception on the 'good' machine worked all night, got the complete
update files, installed them on the good machine in just a few minutes
(most time used up in rebooting).

BTW, running the reception for *.* (i.e. all files sent by Eumetcast),
resulted in 10 Gbytes from midnight until 11 am.

Hope to be able to post some closing remarks on this topic real soon
now. And I'll summarize these experiences for the friendly people in
Darmstadt, so maybe someone else can benefit from it.

Again, thanks,

and tot zien, ciao, cheers, tschüß

U.


Re: rec-vchannelss.ini and new data.....

Geoff Morris <user.group@...>
 

Just got back from week in the sun, wonderful. On reading mails for week I see talk about new data and recv-channels .ini

I am working on, or to be precise my son in law who knows how to do these things is, a utility that will rewrite the file so that you just get the data you want. It should be a matter of ticking the box for the data channels you want and saveing the file. Hope to have it in a couple of weeks.

Geoff Morris
gw3atz@btopenworld.com


update

Frits Muus <ftm.muus@...>
 

Today updat installed and 15 minutes later all works fine.
Frits


Re: Looking at the logs...

a_van_belle
 

Hello Ulrich,

Cheers in Dutch is "Tot ziens" !

Currently we have a full gale with heavy winds and occasional thunder
over here, not a good time to work on antennas.

Unfortunately I did have some problems years ago with 2 VIA mainboards
that almost drove me crazy. But once you have the latest BIOS and
found the correct chipset driver (and install sequence) it should not
be a problem. But make sure you do not install a Soundblaster Live in
a mobo with VIA 686 southbridge !
http://www.realworldtech.com/page.cfm?ArticleID=RWT042501034500

Good luck,
Arne van Belle

--- In MSG-1@yahoogroups.com, "Ulrich G. Kliegis" <Ulrich.Kliegis@...>
wrote:

Short report between some other tasks: The 'good' machine receives
and receives and receives.... at least the txt part of the update has
arrived already too.


Arne, you seem to have psychic abilities :) The chipset is VIA KT133
(northbridge) and something8269 or so on the south. At least, I could
identify the manufacturer, the model, and yes, they have some drivers
and, even better, some much later BIOS (mine is from 18/11/00, their
latest s from 2002).

So here is the clue, what flashing a BIOS has to do with weather
observation...


Re: Looking at the logs...

Ulrich G. Kliegis
 

Short report between some other tasks: The 'good' machine receives
and receives and receives.... at least the txt part of the update has
arrived already too.


Arne, you seem to have psychic abilities :) The chipset is VIA KT133
(northbridge) and something8269 or so on the south. At least, I could
identify the manufacturer, the model, and yes, they have some drivers
and, even better, some much later BIOS (mine is from 18/11/00, their
latest s from 2002).

So here is the clue, what flashing a BIOS has to do with weather
observation...


On 20 May 2006 at 17:54, a_van_belle wrote:

Some mainboards (especially the early VIA boards) need their own
special chipset driver loaded directly after Windows is installed. If
you do not apply this chipset driver you may have bad performance or
unpredictable errors. Try starting another "CPU intensive" program
instead of MDM to see what happens.
Thundering cheers :)

U.


R: Re: Looking at the logs...

Giuseppe Cico
 

Arne,
I am the one who's using extended USB, at the moment.... it's not Ulrich...
:-)
In past days I've gone crazy for some reception stop...
I was wondering about MSG-2 data, then about receiving wide-sized update
files, then about applying updates...
Then I had a look at FAQ and moved EKU... maybe weakened contacts, maybe
thermal problems since back USB is near to warm cooling out...
Now it's working with extension, and according to Murphy's law I keep for a
while... if it works don't change...
Ciao
Giuseppe
-----Messaggio originale-----
Da: MSG-1@yahoogroups.com [mailto:MSG-1@yahoogroups.com]Per conto di
a_van_belle
Inviato: sabato 20 maggio 2006 19.55
A: MSG-1@yahoogroups.com
Oggetto: [MSG-1] Re: Looking at the logs...


Hello Ulrich,

To narrow the search, did this system ever received without problems ?

Your description makes me think it has nothing to do with MDM but the
USB communication to your EKU is failing whenever the CPU has to work !

Some mainboards (especially the early VIA boards) need their own
special chipset driver loaded directly after Windows is installed.
If you do not apply this chipset driver you may have bad performance
or unpredictable errors.
Try starting another "CPU intensive" program instead of MDM to see
what happens.

Using an extension cord is normally not a problem but it is an extra
contact and extra part, increasing the theoretical chance on a failure
! (murphy's law ?)
In some cases I have seen a too low voltage on the USB device when
using a cheap extension cord.

Good luck,
Arne van Belle


Re: Looking at the logs...

Ulrich G. Kliegis
 

On 20 May 2006 at 17:54, a_van_belle wrote:

To narrow the search, did this system ever received without problems ?
Nope, gut the mainboard only last week from a friend.


Your description makes me think it has nothing to do with MDM but the
USB communication to your EKU is failing whenever the CPU has to work
That's what I am thinking about now too. Less the chipset driver (the
device manager in win2k doesn't complain) than the BIOS settings for
the iterrupts. I'll cast an eye on those.

Some mainboards (especially the early VIA boards) need their own
special chipset driver loaded directly after Windows is installed.
I'll have to find out if there is a special driver set for that exotic
motherboard. Looks like one of those minimal sets sold through some
discounter chain.

If
you do not apply this chipset driver you may have bad performance or
unpredictable errors. Try starting another "CPU intensive" program
instead of MDM to see what happens.
What speaks for your theory is this: I played with the priority parameter
in rec-channels.ini today. Lowering it to 300 led to an increased up-time
(949 files comprinsing 649 Mbyte collected on an HDD), until tellicast
went belly-up (no pun intended!) 8^/ :-)))).

Increasing the parameter to 700 let the machine stop after about 200
files (all without MDM or anything else running, screen savers etc. off.)

I am right now testing it on my most powerful machine. Receiving all.all
- In the meantime, I'll search for some drivers.


Using an extension cord is normally not a problem but it is an extra
contact and extra part, increasing the theoretical chance on a failure
! (murphy's law ?) In some cases I have seen a too low voltage on the
USB device when using a cheap extension cord.
As mentioned before, I don't use an extension cord. And the whole
machine does _not_ look like it has lived on the shores of the North
Sea, iow, probably not a contact problem, rather some interupt timing
or conflict.


Thanks again. Normally its my job to try remote diagnoses... and
therapy attempts :)

Hope to be able to give something back in time.

And, what is cheers or tschüß in Neederlands?

Cheers,
U.


Re: Looking at the logs...

a_van_belle
 

Hello Ulrich,

To narrow the search, did this system ever received without problems ?

Your description makes me think it has nothing to do with MDM but the
USB communication to your EKU is failing whenever the CPU has to work !

Some mainboards (especially the early VIA boards) need their own
special chipset driver loaded directly after Windows is installed.
If you do not apply this chipset driver you may have bad performance
or unpredictable errors.
Try starting another "CPU intensive" program instead of MDM to see
what happens.

Using an extension cord is normally not a problem but it is an extra
contact and extra part, increasing the theoretical chance on a failure
! (murphy's law ?)
In some cases I have seen a too low voltage on the USB device when
using a cheap extension cord.

Good luck,
Arne van Belle

--- In MSG-1@yahoogroups.com, "Ulrich G. Kliegis" <Ulrich.Kliegis@...>
wrote:

On 19 May 2006 at 21:36, a_van_belle wrote:

Hello Ulrich,

You must be hit by two problems I guess.
Maybe it will boil down to one - a problem with or in the dongle. After
the communication last night I first reinstalled the rt3.51 program,
then
ran the tests described in the eumetcast FAQs. It looked like the
dongle is ok, the license information in the tellicast suite looks good
too.
Then I let the eumetcast frontend collect some data in &#92;received before
starting MDM. Disappointingly, the same behaviour: The images that
had collected until the start of MDM were all decoded and stored
correctly, but everything coming after that just caused the yellow REC
''LED' to light up, but was neither decoded nor stored.

Since it was after 0000 local time in the meantime, I decided to catch
some sleep, but looked at the log file (in the t-systems folder) again.


R: R: Re: Looking at the logs...

Giuseppe Cico
 

Hi Nigel,
as I updated in mail 2nd mail now everything's ok WITH extention.
Maybe my EKU is borderline... I'll try again connecting directly to USB in
next days.
Now it's working, so I want to sit and watch at clouds from space...
What a couple of days were past!!!...
Ciao
Giuseppe
-----Messaggio originale-----
Da: MSG-1@yahoogroups.com [mailto:MSG-1@yahoogroups.com]Per conto di nigel
heasman
Inviato: sabato 20 maggio 2006 18.15
A: MSG-1@yahoogroups.com
Oggetto: Re: R: [MSG-1] Re: Looking at the logs...


--- Giuseppe Cico <giuseppe.cico@bcico.com> wrote:
Nigel,
I used an extension yesterday... this morning... it
was midnight local CET...
Until then my EKU is working properly, while I had two
crazy day with it put in back USB after six months of
correct working...I don't know if problem was cooling
fan flow or electrical contacts... but now ot's
working.
Ciao
Giuseppe
---------------------------------------------------
Hi Giuseppe,
that's good news - I have no idea why an extension
cable gives problems but seems as if it is best to
avoid them, for the EKU at least!
Is everything else working OK for you now??
regards
Nigel


Re: R: Re: Looking at the logs...

nigel heasman <nigel_heasman@...>
 

--- Giuseppe Cico <giuseppe.cico@bcico.com> wrote:
Nigel,
I used an extension yesterday... this morning... it
was midnight local CET...
Until then my EKU is working properly, while I had two
crazy day with it put in back USB after six months of
correct working...I don't know if problem was cooling
fan flow or electrical contacts... but now ot's
working.
Ciao
Giuseppe
---------------------------------------------------
Hi Giuseppe,
that's good news - I have no idea why an extension
cable gives problems but seems as if it is best to
avoid them, for the EKU at least!
Is everything else working OK for you now??
regards
Nigel


errata corrige --- R: Re: Looking at the logs...

Giuseppe Cico
 

I'm sorry... "From then my EKU is working..." not "Until..."....
My brain needs some maintanance...
Ciao
Giuseppe

-----Messaggio originale-----
Da: MSG-1@yahoogroups.com [mailto:MSG-1@yahoogroups.com]Per conto di
Giuseppe Cico
Inviato: sabato 20 maggio 2006 17.56
A: MSG-1@yahoogroups.com
Oggetto: R: [MSG-1] Re: Looking at the logs...


Nigel,
I used an extension yesterday... this morning... it was midnight local
CET...
Until then my EKU is working properly, while I had two crazy day with it
put
in back USB after six months of correct working...
I don't know if problem was cooling fan flow or electrical contacts... but
now ot's working.
Ciao
Giuseppe
-----Messaggio originale-----
Da: MSG-1@yahoogroups.com [mailto:MSG-1@yahoogroups.com]Per conto di
nigel
heasman
Inviato: sabato 20 maggio 2006 13.33
A: MSG-1@yahoogroups.com
Oggetto: Re: [MSG-1] Re: Looking at the logs...


--- "Ulrich G. Kliegis" <Ulrich.Kliegis@kliegis.de>
wrote:
---------------------------------
....Maybe it will boil down to one - a problem with or
in the dongle.....
-----------------------------------
Hi Ulrich,
Just a thought - do I remember you saying you had
connected the EKU (dongle) through an extension lead?
If so, that might be the problem as I am sure I've
heard of other folk who tried this, so they could see
it and getting similar errors.
good luck
Nigel


R: Re: Looking at the logs...

Giuseppe Cico
 

Nigel,
I used an extension yesterday... this morning... it was midnight local
CET...
Until then my EKU is working properly, while I had two crazy day with it put
in back USB after six months of correct working...
I don't know if problem was cooling fan flow or electrical contacts... but
now ot's working.
Ciao
Giuseppe
-----Messaggio originale-----
Da: MSG-1@yahoogroups.com [mailto:MSG-1@yahoogroups.com]Per conto di nigel
heasman
Inviato: sabato 20 maggio 2006 13.33
A: MSG-1@yahoogroups.com
Oggetto: Re: [MSG-1] Re: Looking at the logs...


--- "Ulrich G. Kliegis" <Ulrich.Kliegis@kliegis.de>
wrote:
---------------------------------
....Maybe it will boil down to one - a problem with or
in the dongle.....
-----------------------------------
Hi Ulrich,
Just a thought - do I remember you saying you had
connected the EKU (dongle) through an extension lead?
If so, that might be the problem as I am sure I've
heard of other folk who tried this, so they could see
it and getting similar errors.
good luck
Nigel