Date   

Re: Xrit2pic problem

R. Alblas
 

Hi, Pat.
I think you are trying to convert a metop EARS picture with an older version of xrit2pic.
METOP EARS is supported in version 2010.03 of xrit2pic and v1.6 of weview.

Regards,
Rob Alblas

xrit2pic mailing list:
http://tech.groups.yahoo.com/group/xrit2pic

pat0691 schreef:

I'm usig Xrit2pic only in AVHRR mode.
In the preview of NOAA image there is this message and I don't see any image:

Translating picture failed (pic2str)!
Ricture format: Z
Error: Can't oper file write.
(note: nessage generating one time)

What is the problem?
Excuse me for my english.
Pat





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

Unsure what a term means? Check the Glossary at: http://www.satsignal.eu/wxsat/glossary.htm
Yahoo! Groups Links





Xrit2pic problem

pat0691
 

I'm usig Xrit2pic only in AVHRR mode.
In the preview of NOAA image there is this message and I don't see any image:

Translating picture failed (pic2str)!
Ricture format: Z
Error: Can't oper file write.
(note: nessage generating one time)

What is the problem?
Excuse me for my english.
Pat


Re: Strange outage

David J Taylor GM8ARV ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ ๐Ÿ‡ช๐Ÿ‡บ
 

Sorry I worded my last mail rather badly. Tellique closed down and
re-opened with a " 0 " fsy file and my RAMdisk which is set to 350 MB ( temp
and tellique writing to RAMdisk ) also restarted with 350 MB presumably as
both fsy files were deleted.
Understood.

Yes it will be interesting to see the new Tellicast client. I am a little
surprised that you were not involved with testing, unless it is the long
overdue version from a couple of years ago. Hopefully as you have indicated
we can still put the \received\ directory on to RAMdisk as it does appear to
give some benefit to 1 computer systems where other uses are made of the
computer.

Regards
Ian.
I expect we will be testing the new version soon, Ian - maybe you'll get an invite as well (as with the section packing and packet size tests earlier this year). The documentation is still to be done, I hear, and it sounds as if EUMETSAT have already done testing already. It may well be that there have been a number of intermediate releases (the last we tested was 2.5.3) and that EUMETSAT have waited until they had one they were happy with before rolling it out.

One of the fundamental limits of the TelliCast system is that it's UDP - which is by nature not a reliable message delivery service, but faster than TCP. However, anything which interrupts polling to too long can disrupt the packet. The new client does allow for some performance improvement by using a RAMdisk.

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


Re: Strange outage

James Brown
 

In message <3914D684D4034AADB974640DE1E436F6@IanPC>, Ian Deans <iandeans142@btinternet.com> writes
Yesterday I too had an E-token error which I have never seen before. It
forced the closure of Tellique which was then automatically restarted with a
0 fsy file and the RAMdisk " full "

The message was " E-Token transaction timeout " and " critical dongle error
restarting child "

No losses since then so all now OK.

Regards
Ian.
Hello Ian,

thanks for the report.

It is probably co-incidental, but just in case there is some reprogramming of the e-token that is taking place, I guess it is worth looking out for.

Interested to know that the new Tellique client may be rolled out before too long,

PS Loch Lomond is looking good;-)

Cheers

James
--
James Brown


Re: Strange outage

Ian Deans
 

Sorry I worded my last mail rather badly. Tellique closed down and re-opened with a " 0 " fsy file and my RAMdisk which is set to 350 MB ( temp and tellique writing to RAMdisk ) also restarted with 350 MB presumably as both fsy files were deleted.

Yes it will be interesting to see the new Tellicast client. I am a little surprised that you were not involved with testing, unless it is the long overdue version from a couple of years ago. Hopefully as you have indicated we can still put the &#92;received&#92; directory on to RAMdisk as it does appear to give some benefit to 1 computer systems where other uses are made of the computer.

Regards
Ian.

--------------------------------------------------
From: "David J Taylor" <gm8arv@yahoo.co.uk>
Sent: Saturday, July 10, 2010 2:56 PM
To: <MSG-1@yahoogroups.com>
Subject: Re: [MSG-1] Strange outage


Yes, I've seen one instance of that on the main PC within the past three
or four months. If there are FSY file(s) when TelliCast restarts it will
attempt to use them, and that would be the case with FSY files either on a
RAMdisk or hard disk. How was the RAMdisk full? BTW: it seems that the
new TelliCast client is due soon, but how it compares to the new client
from a couple of years back (never released) we have yet to find out.
Putting the &#92;received&#92; directory on RAMdisk should still be possible, and
with the previous new client you simply entered:

[locations]
file_database_directory=<memory>

to have the FSY data in RAM.

Cheers,
David


Re: Strange outage

David J Taylor GM8ARV ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ ๐Ÿ‡ช๐Ÿ‡บ
 

Yesterday I too had an E-token error which I have never seen before. It
forced the closure of Tellique which was then automatically restarted with a
0 fsy file and the RAMdisk " full "

The message was " E-Token transaction timeout " and " critical dongle error
restarting child "

No losses since then so all now OK.

Regards
Ian.
Yes, I've seen one instance of that on the main PC within the past three or four months. If there are FSY file(s) when TelliCast restarts it will attempt to use them, and that would be the case with FSY files either on a RAMdisk or hard disk. How was the RAMdisk full? BTW: it seems that the new TelliCast client is due soon, but how it compares to the new client from a couple of years back (never released) we have yet to find out. Putting the &#92;received&#92; directory on RAMdisk should still be possible, and with the previous new client you simply entered:

[locations]
file_database_directory=<memory>

to have the FSY data in RAM.

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


Re: Strange outage

David J Taylor GM8ARV ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ ๐Ÿ‡ช๐Ÿ‡บ
 

I usually stop the programs for house-keeping (like removing FSY etc) but this time I thought I would run RemoveFsy with system running as suggested by Fred - perhaps it just kept on running and deleting everything as it came in, but I couldn't find it running when I looked at the Rx PC. Probably a bit over-zealous too - the Z: drive was only running at half full. Silly me.

Robert
As the size of the FSY files is limited by the recv.ini entry, I'm not clear what it achieves - that's what I'm asking. Is there evidence that under some conditions such as really heavy packet loss the FSY files can become corrupted? Were that the case, then I can see that stopping TelliCast and removing the files could make sense.

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


Re: Strange outage

Ian Deans
 

Yesterday I too had an E-token error which I have never seen before. It
forced the closure of Tellique which was then automatically restarted with a
0 fsy file and the RAMdisk " full "

The message was " E-Token transaction timeout " and " critical dongle error
restarting child "

No losses since then so all now OK.

Regards
Ian.

--------------------------------------------------
From: "David J Taylor" <gm8arv@yahoo.co.uk>
Sent: Saturday, July 10, 2010 11:44 AM
To: <MSG-1@yahoogroups.com>
Subject: Re: [MSG-1] Strange outage


I do see very occasional eToken errors, so I think your explanation is
likely correct. Was the eToken still glowing? Might be worth making sure
it's properly pushed in. You know how connections can deteriorate over
time, and the scraping from pushing connections or re-seating RAM can
clean off a thin layer of oxide (or whatever).

A few days back my test system stopped processing data when it lost
connection to its second hard disk (a SATA device, where the TelliCast
&#92;received&#92; was located). Warm reboot didn't work, but a cold reboot did.
I put this down to one of these "one in a million" controller errors. I
didn't open the system and clean it, but I probably should have done.

Cheers,
David
--


Re: Strange outage

Robert Moore
 

I usually stop the programs for house-keeping (like removing FSY etc) but this time I thought I would run RemoveFsy with system running as suggested by Fred - perhaps it just kept on running and deleting everything as it came in, but I couldn't find it running when I looked at the Rx PC. Probably a bit over-zealous too - the Z: drive was only running at half full. Silly me.

Robert

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

Not sure of the cause - I rarely touch the Rx PC, although last evening
I ran Fred's RemoveFsy manually, but I forget at what time.


Robert
Robert (and anyone). Why run RemoveFsy? Do you stop and restart
TelliCast whist doing so?

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


Re: Strange outage

James Brown
 

I do see very occasional eToken errors, so I think your explanation is
likely correct. Was the eToken still glowing? Might be worth making sure
it's properly pushed in. You know how connections can deteriorate over
time, and the scraping from pushing connections or re-seating RAM can
clean off a thin layer of oxide (or whatever).

A few days back my test system stopped processing data when it lost
connection to its second hard disk (a SATA device, where the TelliCast
&#92;received&#92; was located). Warm reboot didn't work, but a cold reboot did.
I put this down to one of these "one in a million" controller errors. I
didn't open the system and clean it, but I probably should have done.

Cheers,
David
Thanks David,
I didn't have a chance to look at the e-token - it's round the back of the machine and would need a bit of careful manoeuvring! I am not overly concerned, but outages without a cause bring out the 'detective' element in me.

I think the suggestion for an in/out of the e-token with the machine off might be a good idea.

Cheers

James
--
James Brown


Re: Strange outage

David J Taylor GM8ARV ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ ๐Ÿ‡ช๐Ÿ‡บ
 

Not sure of the cause - I rarely touch the Rx PC, although last evening I ran Fred's RemoveFsy manually, but I forget at what time.


Robert
Robert (and anyone). Why run RemoveFsy? Do you stop and restart TelliCast whist doing so?

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


Re: Strange outage

David J Taylor GM8ARV ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ ๐Ÿ‡ช๐Ÿ‡บ
 

Here's a new oddity for me.

Sometime around 3:45AM the system stopped decoding files. I say stopped
decoding because the log file shows many messages which all say: Cannot
join channel 'X' failed to decode key 'x'.
[]
I closed the Tellicast component ( it was still showing a pink 'T') -
restarted the prog, and data once again started flowing.

I wonder if anyone has experienced anything similar? I just wonder if
for some presently unknown reason it lost contact with the dongle?

Mystified.

Cheers

James
I do see very occasional eToken errors, so I think your explanation is likely correct. Was the eToken still glowing? Might be worth making sure it's properly pushed in. You know how connections can deteriorate over time, and the scraping from pushing connections or re-seating RAM can clean off a thin layer of oxide (or whatever).

A few days back my test system stopped processing data when it lost connection to its second hard disk (a SATA device, where the TelliCast &#92;received&#92; was located). Warm reboot didn't work, but a cold reboot did. I put this down to one of these "one in a million" controller errors. I didn't open the system and clean it, but I probably should have done.

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


Re: Strange outage

Robert Moore
 

This morning I found that I had stopped processing at 2000 yesterday. The only '10' folder I had was where the bracknell files automatically downloaded. In cases like this I usually assume I've missed a message - but it couldn't have been the case this time with such a comprehensive loss of data.
Anyhow, Rx PC reboot fixed it.
Not sure of the cause - I rarely touch the Rx PC, although last evening I ran Fred's RemoveFsy manually, but I forget at what time.


Robert


Telephone and fax: 44 (0) 1352 714456


Strange outage

James Brown
 

Here's a new oddity for me.

Sometime around 3:45AM the system stopped decoding files. I say stopped decoding because the log file shows many messages which all say: Cannot join channel 'X' failed to decode key 'x'.

It shows up here:

http://www.meteosat.co.uk/mrtg/satellite_19.html

There were no files clogging up the ram drive, the computer continued to function fine as the log reports, MRTG etc show. Reception of the signal remained at the usual strength - no BER's or tellicast packet loss. No thunderstorms here.

I closed the Tellicast component ( it was still showing a pink 'T') - restarted the prog, and data once again started flowing.

I wonder if anyone has experienced anything similar? I just wonder if for some presently unknown reason it lost contact with the dongle?

Mystified.

Cheers

James


--
James Brown


Re: installing Eumetsat software on OS Windows Vista home

David J Taylor GM8ARV ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ ๐Ÿ‡ช๐Ÿ‡บ
 

Hello,
As my main PC with XP professional definitely refuses to process the Eumetsat software the only choice I have is to try to have it run on my second PC with Windows Vista home Premium
What is the general experience here with Eumetsat on Windows Vista ?
Are there any tricks/traps affecting installation of the Eumetsat software on this O.S. ?
Would you kindly let me know.
Thanks in advance.
Regards,
Roland
My own Vista experiences are described here:

http://www.satsignal.eu/wxsat/Dexatek/index.htm

This is with the Dexatek (DVB World) USB box, so not directly relevant to a SkyStar card, but perhaps there will be one or two hints and tips which may help you.

BTW: I had two PCs running XP (one Home and one Professional), and they ran the TelliCast software without problems. Sorry to hear that you couldn't get it working.

Good luck,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk


installing Eumetsat software on OS Windows Vista home

Roland Fechter
 

Hello,
As my main PC with XP professional definitely refuses to process the Eumetsat software the only choice I have is to try to have it run on my second PC with Windows Vista home Premium
What is the general experience here with Eumetsat on Windows Vista ?
Are there any tricks/traps affecting installation of the Eumetsat software on this O.S. ?
Would you kindly let me know.
Thanks in advance.
Regards,
Roland


Re: Technotrend TT-connect S-2400 USB box

Guillermo Marraco <guillermo.marraco@...>
 

On Fri, Jul 2, 2010 at 7:22 AM, Roland Fechter
<roland-fechter@t-online.de> wrote:



Hello,
I have heard that the above USB box allows, too, reception and operation of the Eumetsat data, using the original Eumetsat software v. 5.5. plus David`s software, eg MSG Data Manager.
My OS is Vista home.
Does anyone of you run the lot trouble-free with this USB box ?
If so, any special hints to observe & consider ?
Any hidden snags ?
That is a piece of garbage.

I tried lots of drivers, and even desperate ones as a Russian mixing
of different versions.

I had problems with all.

The web page of the manufacturers was one of the worst ever I said.

My advice: get other.

....
--
Saludos,

Guillermo Marraco
__________________
Si no eres parte de la soluciรณn, eres parte del precipitado.


Re: Technotrend TT-connect S-2400 USB box

HarryArends.NL <h.arends@...>
 

Hi Roland,

I am not opperating MSG on a 24/7 basis but i am using the same box.
The only problem that could occour is installing the basic drivers of this
card.

About a year ago when i dit the install i had to install and deinstall the
drivers several time before the worked fine.
During opperation i have no [problem with this unit.

Harry

_____

From: MSG-1@yahoogroups.com [mailto:MSG-1@yahoogroups.com] On Behalf Of
Roland Fechter
Sent: Friday, July 02, 2010 12:23 PM
To: MSG-1@yahoogroups.com
Subject: [MSG-1] Technotrend TT-connect S-2400 USB box




Hello,
I have heard that the above USB box allows, too, reception and operation of
the Eumetsat data, using the original Eumetsat software v. 5.5. plus David`s
software, eg MSG Data Manager.
My OS is Vista home.
Does anyone of you run the lot trouble-free with this USB box ?
If so, any special hints to observe & consider ?
Any hidden snags ?
Thanks in advance.
Regards,
Roland


Technotrend TT-connect S-2400 USB box

Roland Fechter
 

Hello,
I have heard that the above USB box allows, too, reception and operation of the Eumetsat data, using the original Eumetsat software v. 5.5. plus David`s software, eg MSG Data Manager.
My OS is Vista home.
Does anyone of you run the lot trouble-free with this USB box ?
If so, any special hints to observe & consider ?
Any hidden snags ?
Thanks in advance.
Regards,
Roland


MTSAT 1 => 2

fvalk <fvalk@...>
 

David,



Now that EUMETCast only disseminates MTSAT-2 files and no more MT1, I
encounter some problems.



Although

- The new MSG Data Manager works fine

- The latest GeoSatSignal version remaps OK

I cannot use the background option as GeoSatSignal doesn't recognize the
satellite name (mt-2) yet, defaulting to "background.bmp". I also cannot
create an alternative "background-msg-mts.bmp" file because this remapping
option doesn't yet exist in MapTo Geo and anyway I wouldn't know which
naming convention you would use.



There is a slight pressure on this as production (Asia/Australia) has
temporarily halted.



Cheers,

Ferdinand

16541 - 16560 of 31098