Date   
missing key - complete data stall :(

Ulrich G. Kliegis
 

Last night at 22:50 UTC, all receptions on my receiver came to a grinding
halt. The recv.log file shows thousands of lines looking like these:


ERR:2011-02-06 10:49:35.997:Could not join channel "EUMETSAT Data
Channel 6": Missing key 55565.
ERR:2011-02-06 10:50:02.235:Could not join channel "EUMETSAT Data
Channel 5": Missing key 55594.
ERR:2011-02-06 10:50:03.166:Could not join channel "EPS-6": Missing key
55597.
ERR:2011-02-06 10:50:31.757:Could not join channel "EUMETSAT Data
Channel 5": Missing key 55622.
ERR:2011-02-06 10:51:24.463:Could not join channel "EPS-10": Missing
key 55659.
ERR:2011-02-06 10:51:29.320:Could not join channel "EPS-8": Missing key
55663.
ERR:2011-02-06 10:51:31.684:Could not join channel "EPS-13": Missing
key 55669.
ERR:2011-02-06 10:51:42.099:Could not join channel "EPS-17": Missing
key 55676.
ERR:2011-02-06 10:52:07.275:Could not join channel "EUMETSAT Data
Channel 4": Missing key 55693.
ERR:2011-02-06 10:52:11.351:Could not join channel "EPS-6": Missing key
55699.
ERR:2011-02-06 10:52:58.238:Could not join channel "EPS-17": Missing
key 55732.
ERR:2011-02-06 10:53:45.706:Could not join channel "EPS-13": Missing
key 55759.
ERR:2011-02-06 10:53:49.962:Could not join channel "EPS-16": Missing
key 55763.
ERR:2011-02-06 10:53:56.051:Could not join channel "EPS-8": Missing key
55773.
ERR:2011-02-06 10:54:19.575:Could not join channel "EPS-2": Missing key
55783.
ERR:2011-02-06 10:54:40.846:Could not join channel "EUMETSAT Data
Channel 12": Missing key 55810.
ERR:2011-02-06 10:55:31.378:Could not join channel "EUMETSAT Data
Channel 5": Missing key 55861.
ERR:2011-02-06 10:55:46.160:Could not join channel "EUMETSAT Data
Channel 3": Missing key 55876.
ERR:2011-02-06 10:56:19.247:Could not join channel "EUMETSAT Data
Channel 1": Missing key 55900.
MSG:2011-02-06 10:58:24.841:Log level is "quiet".
ERR:2011-02-06 10:59:12.629:Could not join channel "EPS-Global":
Missing key 56067.
ERR:2011-02-06 10:59:29.574:Could not join channel "EPS-13": Missing
key 56087.
ERR:2011-02-06 10:59:33.529:Could not join channel "EUMETSAT Data
Channel 5": Missing key 56092.
ERR:2011-02-06 10:59:51.395:Could not join channel "EUMETSAT Data
Channel 3": Missing key 56108.
ERR:2011-02-06 10:59:53.258:Could not join channel "EPS-15": Missing
key 56107.
ERR:2011-02-06 11:00:03.002:Could not join channel "EPS-3": Missing key
56115.
ERR:2011-02-06 11:00:03.072:Could not join channel "EPS-Africa": Missing
key 56127.
ERR:2011-02-06 11:00:23.892:Could not join channel "DEVCOCAST-1":
Missing key 56143.
ERR:2011-02-06 11:00:56.118:Could not join channel "EPS-8": Missing key
56175.
ERR:2011-02-06 11:00:58.411:Could not join channel "EPS-15": Missing
key 56177.
ERR:2011-02-06 11:01:50.376:Could not join channel "EPS-16": Missing
key 56234.
ERR:2011-02-06 11:01:54.442:Could not join channel "EUMETSAT Data
Channel 3": Missing key 56235.
ERR:2011-02-06 11:03:07.607:Could not join channel "EPS-16": Missing
key 56317.
ERR:2011-02-06 11:03:19.735:Could not join channel "EPS-15": Missing
key 56326.
ERR:2011-02-06 11:03:20.876:Could not join channel "EUMETSAT Data
Channel 4": Missing key 56327.
ERR:2011-02-06 11:03:25.323:Could not join channel "EPS-8": Missing key
56329.
ERR:2011-02-06 11:04:01.034:Could not join channel "EPS-13": Missing
key 56363.
ERR:2011-02-06 11:04:04.108:Could not join channel "EPS-6": Missing key
56372.
ERR:2011-02-06 11:04:14.934:Could not join channel "EPS-16": Missing
key 56378.
ERR:2011-02-06 11:04:32.639:Could not join channel "EPS-15": Missing
key 56398.
ERR:2011-02-06 11:04:35.393:Could not join channel "EPS-5": Missing key
56400.
ERR:2011-02-06 11:05:00.820:Could not join channel "EPS-Global":
Missing key 56435.
ERR:2011-02-06 11:05:12.707:Could not join channel "EPS-Africa": Missing
key 56460.
ERR:2011-02-06 11:05:36.952:Could not join channel "EPS-8": Missing key
56478.
ERR:2011-02-06 11:05:38.494:Could not join channel "EPS-15": Missing
key 56480.
ERR:2011-02-06 11:05:53.956:Could not join channel "EPS-13": Missing
key 56495.
ERR:2011-02-06 11:06:00.506:Could not join channel "EPS-11": Missing
key 56502.
ERR:2011-02-06 11:06:04.231:Could not join channel "EPS-2": Missing key
56506.
ERR:2011-02-06 11:06:07.846:Could not join channel "EPS-Global":
Missing key 56510.
ERR:2011-02-06 11:06:15.527:Could not join channel "EPS-6": Missing key
56516.
ERR:2011-02-06 11:06:36.818:Could not join channel "EPS-6": Missing key
56534.
ERR:2011-02-06 11:06:48.054:Could not join channel "EPS-13": Missing
key 56545.
ERR:2011-02-06 11:06:58.049:Could not join channel "EUMETSAT Data
Channel 3": Missing key 56553.
ERR:2011-02-06 11:07:25.999:Could not join channel "EPS-17": Missing
key 56578.
ERR:2011-02-06 11:08:17.673:Could not join channel "EPS-11": Missing
key 56611.
ERR:2011-02-06 11:08:34.097:Could not join channel "EPS-Global":
Missing key 56621.
ERR:2011-02-06 11:09:04.701:Could not join channel "EPS-13": Missing
key 56650.
ERR:2011-02-06 11:09:12.912:Could not join channel "EPS-17": Missing
key 56660.
ERR:2011-02-06 11:09:53.731:Could not join channel "DWDSAT": Missing
key 56703.
ERR:2011-02-06 11:10:24.305:Could not join channel "EPS-13": Missing
key 56729.
ERR:2011-02-06 11:10:43.292:Could not join channel "EPS-11": Missing
key 56746.
ERR:2011-02-06 11:10:52.926:Could not join channel "EPS-8": Missing key
56751.
ERR:2011-02-06 11:10:57.333:Could not join channel "EUMETSAT Data
Channel 4": Missing key 56757.
ERR:2011-02-06 11:11:18.954:Could not join channel "EPS-16": Missing
key 56773.
ERR:2011-02-06 11:11:37.090:Could not join channel "EUMETSAT Data
Channel 5": Missing key 56779.
ERR:2011-02-06 11:11:38.552:Could not join channel "EPS-17": Missing
key 56782.
ERR:2011-02-06 11:12:28.053:Could not join channel "EPS-13": Missing
key 56825.
ERR:2011-02-06 11:13:08.001:Could not join channel "EPS-15": Missing
key 56860.
ERR:2011-02-06 11:13:09.693:Could not join channel "EPS-11": Missing
key 56864.
ERR:2011-02-06 11:13:33.267:Could not join channel "EPS-16": Missing
key 56883.
ERR:2011-02-06 11:13:34.018:Could not join channel "EPS-Global":
Missing key 56882.
ERR:2011-02-06 11:13:39.536:Could not join channel "EPS-2": Missing key
56889.
ERR:2011-02-06 11:13:40.898:Could not join channel "EPS-17": Missing
key 56892.
ERR:2011-02-06 11:13:58.173:Could not join channel "EPS-15": Missing
key 56904.
ERR:2011-02-06 11:14:20.855:Could not join channel "EPS-13": Missing
key 56926.
ERR:2011-02-06 11:15:08.484:Could not join channel "EPS-15": Missing
key 56972.
ERR:2011-02-06 11:15:16.085:Could not join channel "EPS-Global":
Missing key 56985.
ERR:2011-02-06 11:15:24.797:Could not join channel "DEVCOCAST-1":
Missing key 56991.
ERR:2011-02-06 11:15:26.730:Could not join channel "EUMETSAT Data
Channel 2": Missing key 56992.
ERR:2011-02-06 11:15:41.792:Could not join channel "EPS-8": Missing key
57002.
ERR:2011-02-06 11:16:21.278:Could not join channel "EUMETSAT Data
Channel 4": Missing key 57039.
ERR:2011-02-06 11:16:42.569:Could not join channel "EUMETSAT Data
Channel 2": Missing key 57048.
ERR:2011-02-06 11:16:47.066:Could not join channel "EPS-15": Missing
key 57060.
ERR:2011-02-06 11:16:55.157:Could not join channel "EPS-13": Missing
key 57066.
ERR:2011-02-06 11:16:57.931:Could not join channel "EPS-17": Missing
key 57072.
ERR:2011-02-06 11:16:58.662:Could not join channel "EUMETSAT Data
Channel 1": Missing key 57073.
ERR:2011-02-06 11:17:59.900:Could not join channel "EPS-13": Missing
key 57123.
ERR:2011-02-06 11:18:06.570:Could not join channel "EPS-16": Missing
key 57137.
ERR:2011-02-06 11:18:10.726:Could not join channel "EPS-8": Missing key
57141.
ERR:2011-02-06 11:18:21.481:Could not join channel "EPS-Global":
Missing key 57151.
ERR:2011-02-06 11:18:34.290:Could not join channel "EPS-10": Missing
key 57159.
ERR:2011-02-06 11:18:36.222:Could not join channel "EUMETSAT Data
Channel 4": Missing key 57160.
ERR:2011-02-06 11:18:38.776:Could not join channel "EPS-2": Missing key
57161.
ERR:2011-02-06 11:18:57.253:Could not join channel "EPS-Global":
Missing key 57182.
ERR:2011-02-06 11:19:56.378:Could not join channel "EPS-15": Missing
key 57252.
ERR:2011-02-06 11:20:04.780:Could not join channel "EUMETSAT Data
Channel 5": Missing key 57262.
ERR:2011-02-06 11:21:00.730:Could not join channel "EPS-15": Missing
key 57299.
ERR:2011-02-06 11:21:48.759:Could not join channel "EPS-17": Missing
key 57334.
ERR:2011-02-06 11:23:09.485:Could not join channel "Americas-CH1":
Missing key 57380.
ERR:2011-02-06 11:23:38.617:Could not join channel "EPS-Global":
Missing key 57400.
ERR:2011-02-06 11:25:05.853:Could not join channel "EUMETSAT Data
Channel 5": Missing key 57482.
ERR:2011-02-06 11:25:44.659:Could not join channel "EPS-15": Missing
key 57508.
ERR:2011-02-06 11:33:32.912:Could not join channel "EUMETSAT Data
Channel 2": Missing key 57832.
ERR:2011-02-06 11:39:06.451:Could not join channel "DWDSAT": Missing
key 58019.
ERR:2011-02-06 11:40:04.485:Could not join channel "EPS-3": Missing key
58073.
ERR:2011-02-06 11:40:09.001:Could not join channel "DWDSAT": Missing
key 58074.
ERR:2011-02-06 11:40:28.740:Could not join channel "EPS-8": Missing key
58087.
ERR:2011-02-06 11:40:48.418:Could not join channel "EUMETSAT Data
Channel 6": Missing key 58096.
ERR:2011-02-06 11:41:34.845:Could not join channel "EPS-7": Missing key
58120.
ERR:2011-02-06 11:41:58.248:Could not join channel "EUMETSAT Data
Channel 1": Missing key 58129.
ERR:2011-02-06 11:42:28.121:Could not join channel "EUMETSAT Data
Channel 3": Missing key 58149.
ERR:2011-02-06 11:42:47.559:Could not join channel "EUMETSAT Data
Channel 3": Missing key 58156.
ERR:2011-02-06 11:42:48.371:Could not join channel "EPS-8": Missing key
58158.
ERR:2011-02-06 11:43:02.891:Could not join channel "EUMETSAT Data
Channel 1": Missing key 58167.
ERR:2011-02-06 11:43:17.963:Could not join channel "EPS-2": Missing key
58181.
ERR:2011-02-06 11:44:05.852:Could not join channel "EUMETSAT Data
Channel 12": Missing key 58209.


Yesterday, one of the HDDs had become full, after clearing a few GOME
folders (presently useless to me anyway due to not having a reader for them
yet...), the box was up and running again.

I have no faint idea of where to start looking for a solution - any helpful
hints? Thanks!

Cheers,
U. (seeing it rain outside also without sat assistance...)

Re: missing key - complete data stall :(

David J Taylor
 

Last night at 22:50 UTC, all receptions on my receiver came to a grinding
halt. The recv.log file shows thousands of lines looking like these:


ERR:2011-02-06 10:49:35.997:Could not join channel "EUMETSAT Data
Channel 6": Missing key 55565.
ERR:2011-02-06 10:50:02.235:Could not join channel "EUMETSAT Data
Channel 5": Missing key 55594.
[]
Yesterday, one of the HDDs had become full, after clearing a few GOME
folders (presently useless to me anyway due to not having a reader for them
yet...), the box was up and running again.

I have no faint idea of where to start looking for a solution - any helpful
hints? Thanks!

Cheers,
U. (seeing it rain outside also without sat assistance...)
Ulrich,

Sorry to hear about your problems. Suggestion, check that your eToken is still working. It may be worth pulling it out and back in again - you can do this "live", but if you are in any doubt, you can reboot.

As to the GOME data, simply comment out [EPS-5] in your recv-channels.ini, or use the Auto-clean function in the MSG Data Manager to remove unprocessed files from the EUMETCast \received\ directory tree every so often (e.g. 24 hours), or schedule a nightly run of my TrimTree program.

If the GOME data is in BUFR format, perhaps Francis Breame's reader (described in the GEO Quarterly) can help?

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

Re: missing key - complete data stall :(

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Sun, 6 Feb 2011 12:52:48 -0000
Betreff: Re: [MSG-1] missing key - complete data stall :(
Antwort an: MSG-1@...

Sorry to hear about your problems. Suggestion, check that your eToken
is still working. It may be worth pulling it out and back in again -
you can do this "live", but if you are in any doubt, you can reboot.
David, thanks for the immediate reply. The pink T is pink, and the data are
streaming in 5 Mbit/s, according to the Tellicast monitor. Is this located
before or behind the Token Check? I checked my Eumetcast account some
weeks ago, and it looked good for two more years or so, just re-checked,
good through March 2013.

I powered the receiver completely down and restarted it after a few minutes,
no avail.

Wouldn't the T tunr un-pink if there was a problem with the etoken?

Oooops - I was out in the afternoon, and just see - it started working again
somewhen at around 4 p.m. UTC. So, another unsolved mystery remains in
history.

Strange, very strange.

I'll report if any new phenomena emerge.

Thanks for your telepathetological assistance - the only rational
explanation... THEY read this list too, I guess... :)))

Cheers,
U.

Re: missing key - complete data stall :(

R. Alblas
 

Ulrich G. Kliegis schreef:
...

Wouldn't the T tunr un-pink if there was a problem with the etoken?
Ulrich,
There is just one 'source' changing the colour of the T: the message channel (PID nr. 100).
If no message channel comes in (because of no sat signal, or because of no receiver connected at all, or because of no PID 100 set) then colour is red.
If a message channel is received but not from Eumetcast then it is yellow.
If a message channel is received from Eumetcast then T is purple.
Etoken has nothing to do with that.

Today I got a question from a Eumetcast user "suffering" from yellow T. The cause: The wind did blow his disc to SKY at 13 east.
Etoken can not change the colour of your T, but the wind can...

Rob.

Re: missing key - complete data stall :(

Ulrich G. Kliegis
 

Today I got a question from a Eumetcast user "suffering" from yellow
T. The cause: The wind did blow his disc to SKY at 13 east. Etoken can
not change the colour of your T, but the wind can...
Rob,
thanks for that comment. A few hours after my last message, data got stuck
again and still are.
Yes, we had some pretty fast air here too, but the failure occured many
hours after the gusts and squalls settled. I'll check the etokens seat in its
socket in the afternoon.

Cheers,
U.

Re: missing key - complete data stall :( - BUFR files

fbreame
 

--- In MSG-1@..., "David J Taylor" <gm8arv@...> wrote:

If the GOME data is in BUFR format, perhaps Francis Breame's reader
(described in the GEO Quarterly) can help?

Cheers,
David
Some of the GOME stuff is in BUFR, and is to be found under the SAF directory produced by David's MSG Data Manager, with names like

S-O3M_GOME_O3-NO2_L2_20110207051755_003_METOPA_22326_DLR_02.BUFR
S-O3M_GOME_NOP_02_M02_20110207063555Z_20110207063855Z_N_O_20110207083422Z.bufr

However, the METOP level 1B files produced by Metop Manager in the GOME directory are apparently in some native format which I can't help with.

If anyone wants to try, my BUFRdisplay program is available on

http://www.vf0123.btinternet.co.uk

In case anyone is interested, I am also working on a new experimental feature which will translate synop and upper-air in BUFR format into the traditional text (5-digit) format. This has needed quite a few changes, but I hope to have an initial version up within a couple of weeks, if not sooner, once I have finished testing.

Francis Breame

New file uploaded to MSG-1

MSG-1@...
 

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the MSG-1
group.

File : /TClogSummary091.zip
Uploaded by : gm8arv <gm8arv@...>
Description : TClogSummary Version 0.91 from Ernst Lobsiger is a Windows CMD script under the GPL. It analyzes TelliCast Client log files from EUMETCast receivers. No additional software is needed. The script has been run on Windows XP/Vista/7 machines (not Windows 2000), and please note it may be quite CPU-intensive. Support via the MSG-1 Yahoo group. 0.91 is a minor update.

You can access this file at the URL:
http://groups.yahoo.com/group/MSG-1/files/TClogSummary091.zip

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/l/us/yahoo/groups/original/members/web/index.html
Regards,

gm8arv <gm8arv@...>

Hourly FSD

geoffreygee90
 

David.
I have checked with Eumetsat that I should be receiving these transmissions
but I am still only getting the 6 hr ones . Where have I gone wrong as I
can see nothing in "set up " that refers to this. and I am running the
latest versions of the programmes.

Regards...........Geoffrey

Re: Hourly FSD

David J Taylor
 

David.
I have checked with Eumetsat that I should be receiving these transmissions
but I am still only getting the 6 hr ones . Where have I gone wrong as I
can see nothing in "set up " that refers to this. and I am running the
latest versions of the programmes.

Regards...........Geoffrey

Geoffrey,

The hourly FSD is sent on a different data stream - "EUMETSAT Data Channel 4", so you will need to ensure that your recv-channels.ini includes that data as well as any other data you take. In the example below, the two lines including "Channel 4" were added to get the hourly FSD:

______________________________________________
[EUMETSAT Data Channel 1]
target_directory=received&#92;Data Channel 1

[EUMETSAT Data Channel 2]
target_directory=received&#92;Data Channel 2

[EUMETSAT Data Channel 3]
target_directory=received&#92;Data Channel 3

[EUMETSAT Data Channel 4]
target_directory=received&#92;Data Channel 4
______________________________________________


In the MSG Data Manager itself, you would need to visit: Setup, Channel Selection, FSD, and ensure that the "Hourly FSD" box is checked. I would also suggest checking the "Generic naming" box. In any case, the FSD should be three hourly, not six hourly.

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

Alps

Alan Banks <alan@...>
 

Hi All,
Very clear over the alps this morning. Should be good for some of the Polar orbiters later.
For the first time I note some Von Karman Vortices south of Elba ans an interesting little circulation east of Menorca.
See
http://www.alanbanks.org.uk/imageofmonth.html
Cheers

Alan

Re: Alps

James Brown
 

In message <4D5261B5.40001@...>, Alan Banks <alan@...> writes
Hi All,
Very clear over the alps this morning. Should be good for some of the
Polar orbiters later.
For the first time I note some Von Karman Vortices south of Elba ans an
interesting little circulation east of Menorca.
See
http://www.alanbanks.org.uk/imageofmonth.html
Cheers

Alan
That's excellent Alan - I haven't seen the Von Karman vortices in that area before - now disintegrating a little.

Many thanks for sharing
James
--
James Brown

Hourly FSD

geoffreygee90
 

David

Many thanks for you quick reply. I have carried out your instructions, including checking the MSG Manager Set Up and still do not receive the hourly FSD................. 3 hourly coming in as usual

I attach a copy of my received.ini file which I have never edited before and is as loaded when I first started ussing the programme years ago.

There seem to be a lot of lines I do not understand. Is there a conflict somewhere ?

Further help requested.

Regards...............Geoffrey

`# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver Configuration File


# additional files: see license.ini, recv-channels.ini (optional)
# for more information on file format use help menu in Tellicast shell
#
# 2-4-3 10-10-2005
#

[EUMETSAT DATA Channel 1 ]
target_directory=received&#92;Data Channel 1

[EUMETSAT DATA Channel 4 ]
target_directory=received&#92;Data Channel 4 ]


[recipient]
user_name=GeoffreyGee
user_key_crypt=a20m-nwn7-p66p-a0db


[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=30
log_level=normal

[locations]
#file_database_directory=receiving/tmp
log_file=>>recv.log
license_file=C:&#92;Program Files&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Program Files&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
#file_database_size=262144000
#file_delivery_counter=50
file_delivery_speed=20000000

Re: Hourly FSD

David J Taylor
 

David

Many thanks for you quick reply. I have carried out your instructions, including checking the MSG Manager Set Up and still do not receive the hourly FSD................. 3 hourly coming in as usual

I attach a copy of my received.ini file which I have never edited before and is as loaded when I first started ussing the programme years ago.

There seem to be a lot of lines I do not understand. Is there a conflict somewhere ?

Further help requested.

Regards...............Geoffrey

Geoffrey,

These lines:

[EUMETSAT DATA Channel 1 ]
target_directory=received&#92;Data Channel 1

[EUMETSAT DATA Channel 4 ]
target_directory=received&#92;Data Channel 4 ]

need to be in the recv-channels.ini file, not the recv.ini file. Obviously, you should match any directory specifications with those you already have for the other channels.

One other point - you need PID 500 decimal, 0x01F4 hex, enabled in your DVB World or SkyStar setup.

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

Re: Hourly FSD

David J Taylor
 

These lines:

[EUMETSAT DATA Channel 1 ]
target_directory=received&#92;Data Channel 1

[EUMETSAT DATA Channel 4 ]
target_directory=received&#92;Data Channel 4 ]
Oh, and I now see that you have added extra spaces before the "]" in the first lines of the pair, and and extra "]" in the second line of the second pair. What I suggested was:

______________________________________________________
[EUMETSAT Data Channel 1]
target_directory=received&#92;Data Channel 1

[EUMETSAT Data Channel 2]
target_directory=received&#92;Data Channel 2

[EUMETSAT Data Channel 3]
target_directory=received&#92;Data Channel 3

[EUMETSAT Data Channel 4]
target_directory=received&#92;Data Channel 4
______________________________________________________


Perhaps the lines you reported had typing errors, but please check carefully.

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

Lost Images

e.macgurk@...
 

Hi.

I have been using the MGS data manager for about 5 weeks and have just noticed i no longer have any new images being sent to the MSG1/images folder, iv only realised this as i have just started using the MSG animator and this is where it gets the images from to animate, i have checked in MSG data manager set up, and all looks fine there sending data to image folder, but the folder is empty, i think it is creating a new folder each day but remaines empty.

Eric.

Re: Lost Images

David J Taylor
 

Hi.

I have been using the MGS data manager for about 5 weeks and have just noticed i no longer have any new images being sent to the MSG1/images folder, iv only realised this as i have just started using the MSG animator and this is where it gets the images from to animate, i have checked in MSG data manager set up, and all looks fine there sending data to image folder, but the folder is empty, i think it is creating a new folder each day but remaines empty.

Eric.
Eric,

I can only guess that you are, perhaps, looking at the LRIT directory rather than the HRIT directory. LRIT MSG-2 image data over EUMETCast has now stopped, and only HRIT is sent.

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

Re: Lost Images

Terence O'Hanlon Smith
 

Or perhaps, if you have only been receiving RSS, the monthly maintenance offline period may be the cause?

FSD Hourly

geoffreygee90
 

David up

Thanks again for help, I regret that I can still not get the hourly FSD.
I have rechecked again including the PID. 0x01F4 appears in the Techni Sat active PID list and in MSGM set up.

Copy of my rec-channels.ini below...............................what next ?.................Regards.......Geoffrey

# recv-channels.ini - TelliCast+TelliVision Client channel configuration file
#
# 2-4-3 10-10-2005
#

[EUMETSAT DATA Channel 1]
target_directory=C:&#92;received&#92;data Channel 1

[EUMETSAT DATA Channel 4]
target_directory=C:&#92;received&#92;data Channel 4



[EUMETSAT Data Channel 2]
target_directory=C:&#92;received&#92;Data Channel 2

[EUMETSAT Data Channel 3]
target_directory=C:&#92;received&#92;Data Channel 3


# 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

Re: FSD Hourly

Douglas Deans
 

-----Original Message-----
From: Geoffrey Gee
Sent: Thursday, February 10, 2011 3:33 PM
To: MSG-1@...
Subject: [MSG-1] FSD Hourly

David up

Thanks again for help, I regret that I can still not get the hourly FSD.
I have rechecked again including the PID. 0x01F4 appears in the Techni Sat
active PID list and in MSGM set up.

Copy of my rec-channels.ini below...............................what next
?.................Regards.......Geoffrey



Hello Geoffrey,

I assume you have actually applied for the data.
The additional FSD data to add to the 3 hourly is on a different channel and
you need to request it from Eumetsat (can be done on-line).

Regards
Douglas.

Re: FSD Hourly

geoffreygee90
 

Hello Douglas

Many thanks for your assistance. I have already checked with Eumaetsat that I am registered for the 1 huorly service. See below.

Regards.............Geoffrey



Dear Geoffrey,

I'm afraid that you are already receiving the most frequent GOES & MT-SAT data which we disseminate (i.e. 1-hourly).

Please have a look at your EO Portal account to check which data you are receiving (https://eoportal.eumetsat.int/userMgmt/login.faces, your userID is "GEOGEE").
You can request additional data via your EO Portal account.

More details on our products can also be found in the Product Navigator:
http://www.eumetsat.int/Home/Main/DataProducts/ProductNavigator/index.htm

Please let me know if you have further questions.

Kind regards,


Inse Warich

EUMETSAT User Service Helpdesk
Eumetsat-Allee 1
64295 Darmstadt
GERMANY

Tel. +49 6151 807 377
Fax. +49 6151 807 379
www.eumetsat.int

-----Original Message-----
From: Geoffrey Gee [mailto:no-reply@...]
Sent: Monday, February 07, 2011 5:46 PM
To: e-mail OPS
Subject: Subject: Web Feedback (OPS)


As a regular user I obtain both MSG and FSD data I would like to obtain the latter at more frequent hourly intervals. Is this possible and how do I procede.

Thank you............Geoffrey

Title : Mr.
Family Name : Gee
First Name : Geoffrey
Company :
Street : 34 Andrews Lodge Tylers Close
Post code : SO41 9AX
City : Lymingtin
Country : UK
Telephone : +1590674803
Fax :
Email : geogee@...

Refering URL*: http://www.eumetsat.int/Home/Main/DataAccess/HelpdeskService/index.htm