Date   

Re: SUVI

Roby <pa0038@...>
 

hi, I already know that page, after all it was obvious to visit the Eumetsat portal, but the example of files that are already in my possession does not help much. It's the visualization software I need. roberto


Re: SUVI

Ernst Lobsiger
 


SUVI

Roby <pa0038@...>
 

Hello everyone and happy new year.
I have recently resumed reception and I see that in the E1H-TPG-5 folder there are many files OR_SUVI-L1b-He303_G16_xxxxx
Question: are these files valid? And if so, how can the images of the sun be displayed? I've tried with Eumetcastwiev but can't find any options.
thank you

Roberto


Re: Bdadataex

David J Taylor GM8ARV ūüŹīů†Āßů†ĀĘů†Ā≥ů†Ā£ů†Āīů†ĀŅ ūüá™ūüáļ
 

On 09/01/2022 09:57, Aldo via groups.io wrote:
Hi David
Thanks for the reply and the program and advice.
Unfortunately I have a problem with the parabola installed and it does not
receive the HVS-1 channel.
Due to the wind it has moved and receives only eumetcast base and of 80 cm I
have to replace with 100 cm.
thanks 73 aldo ik1rgm
Aldo,

There's a document here with the footprint of the 10A satellite:

https://www.eumetsat.int/eumetcast
https://www-cdn.eumetsat.int/files/2020-04/img_eutelsat_10a_ku_band_cover.jpg

Your 80cm may be OK once it is fixed very well! The 100 cm will get more
signal. but it will also catch more wind, and it will also be more sensitive to
any changes in its pointing. You can't win!

It is also very important to get the dish correctly set:

- azimuth (obvious)
- elevation (obvious)
- skew of the LNB (to minimise reception of the vertically polarised signal)
- focus (move the LNB slightly closer to or further away from the dish)

My apologies if you already know all this, but we are dealing with very weak
and quite wide bandwidth signals. Every extra fraction of a dB is worth the
effort.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: EumetCastViewer crashes

Hugo
 

Harmut,

EUMETCastView is written in the Qt API . The dll's included in the zip file are the ones that are needed to run the software.Do not use dll's that are from an older version.
Use a new directory when you unzip the files. The program will look first for dll's in the working directory.
I tested the program on 3 different systems, but not on a server :). And of course there are other users that installed the latest version on their system ....

grts,

Hugo


Re: EumetCastViewer crashes

Hartmut Schulla
 

Hi Hugo!

OK! But on 2 different Machines with completely different operation systems (WIN10, Server2008r2) and different HW?

As I posted, an ‚Äěancient‚Äú version runs.

Regards

Hartmut

 

Von: MSG-1@groups.io <MSG-1@groups.io> Im Auftrag von Hugo
Gesendet: Sonntag, 9. Jänner 2022 14:59
An: MSG-1@groups.io
Betreff: Re: [MSG-1] EumetCastViewer crashes

 

Hartmut,

I found the following on error code 0xc0000005....(https://www.stellarinfo.com/blog/how-to-fix-error-code-0xc0000005-in-windows/)
Probably some missing or corrupted dll's ?

grts,

Hugo


Re: EumetCastViewer crashes

Hugo
 

Hartmut,

I found the following on error code 0xc0000005....(https://www.stellarinfo.com/blog/how-to-fix-error-code-0xc0000005-in-windows/)
Probably some missing or corrupted dll's ?

grts,

Hugo


Re: EumetCastViewer crashes

Hartmut Schulla
 

Hi!

I think, OpenGL ist active, because I use Nvidia Graphics Card.

H.

 

Von: MSG-1@groups.io <MSG-1@groups.io> Im Auftrag von Hugo
Gesendet: Sonntag, 9. Jänner 2022 14:08
An: MSG-1@groups.io
Betreff: Re: [MSG-1] EumetCastViewer crashes

 

Hartmut,

Another thing, the program shouldn't crash for missing the TLE files. Do you have OpenGL on Windows machines ?
grts,

Hugo


Re: EumetCastViewer crashes

Hugo
 

Hartmut,

Another thing, the program shouldn't crash for missing the TLE files. Do you have OpenGL on Windows machines ?
grts,

Hugo


Re: EumetCastViewer crashes

Hugo
 

Hi Hartmut,

Just after the pop-screen "Need the Sentinel-3 TLEs", you can add at least the TLE file "weather.txt" to EUMETCastView. There is already an old "weather.txt" in the distribution.
For that you click the button "Add TLE File" in the "Satellite Setup" screen. It is not necessary to select one of the satellite entries in that file. To update that file just click the "Update TLE's" button.

Regards,

Hugo


Re: Bdadataex

Aldo
 

Hi David
Thanks for the reply and the program and advice.
Unfortunately I have a problem with the parabola installed and it does not receive the HVS-1 channel.
Due to the wind it has moved and receives only eumetcast base and of 80 cm I have to replace with 100 cm.
thanks 73 aldo ik1rgm


EumetCastViewer crashes

Hartmut Schulla
 

Hi folks!

 

I downloaded and installed EumetCastViewer 64Bit from Github on Win10 64bit.

It crashes immediatly after the start on both machines (Server2008r2 64Bit and WIN10 64Bit).

There is one message: ‚ÄěNeed the Sentinel-3 TLEs‚Äú before the crash.

An very early old version runs smoothly.

The Application Error Log shows the following:

 

Name der fehlerhaften Anwendung: EUMETCastView.exe, Version: 0.0.0.0, Zeitstempel: 0x61a8d143

Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000

Ausnahmecode: 0xc0000005

Fehleroffset: 0x0000000000000000

ID des fehlerhaften Prozesses: 0x4858

Startzeit der fehlerhaften Anwendung: 0x01d8053eb30a5d48

Pfad der fehlerhaften Anwendung: D:\Tools\DeployEUMETCastView\EUMETCastView.exe

Pfad des fehlerhaften Moduls: unknown

Berichtskennung: 2ae2e7f7-7132-11ec-b750-ffffffffffff

 

Any idea?

 

Regards

Hartmut

 

 

Von: MSG-1@groups.io <MSG-1@groups.io> Im Auftrag von Philip Robinson
Gesendet: Samstag, 8. Jänner 2022 12:48
An: MSG-1@groups.io
Betreff: Re: [MSG-1] FY-3D

 

Ernst

Please dont give up on me. I have sorted it all out i hope

I have not gone out today to try and get my head around this and it all boiled down to something incredibly simple. i knew it would be.

when i right clicked on my properties icon on all my Tellicast icons the target was still to my C: drive. So obviously I have now altered all the targets  to D:drive. So a lot of  the work i was editing  in my D: drive clients folders was a waste of time.

I then had to go through all my cast-client.ini files and do some very careful editing of them to ensure i had all the correct interfaces and target paths because they were now messed up.

Restarted all my clients again and hey presto EVERYTHING IS WHERE IT SHOULD BE and it works. I am receiving all my HVS-2, HVS-1 and BAS files and the logs are where they should be. Davids programmes seem to be fine.

As Ernst said it was a mess.

I dont want to know what¬†"Wer nicht h√∂ren will muss f√ľhlen!" means but I feel its not pleasant

i am off to a dark room now

regards

Philip

 

Just double checked and all is good. "Those who refuse to follow rules shall feel the consequences". Too right.

 

 

 

 

 

------ Original Message ------

From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>

Sent: 08/01/2022 11:10:00

Subject: Re: [MSG-1] FY-3D

 

On Sat, Jan 8, 2022 at 02:14 AM, Philip Robinson wrote:

Yes, i did restart the tellicast clients 

Philip,

I GIVE UP: You simply tell us the TelliCast client is broken as it is unable to log on D:.
Go on with your own "next step" of deleting all TelliCast stuff on C:. But don't blame
me if things don't work as expected anymore: "Wer nicht h√∂ren will muss f√ľhlen!"

Regards,
Ernst

 

Virus-free. www.avg.com


Re: FY-3D

Philip Robinson
 

Ernst
Please dont give up on me. I have sorted it all out i hope
I have not gone out today to try and get my head around this and it all boiled down to something incredibly simple. i knew it would be.
when i right clicked on my properties icon on all my Tellicast icons the target was still to my C: drive. So obviously I have now altered all the targets  to D:drive. So a lot of  the work i was editing  in my D: drive clients folders was a waste of time.
I then had to go through all my cast-client.ini files and do some very careful editing of them to ensure i had all the correct interfaces and target paths because they were now messed up.
Restarted all my clients again and hey presto EVERYTHING IS WHERE IT SHOULD BE and it works. I am receiving all my HVS-2, HVS-1 and BAS files and the logs are where they should be. Davids programmes seem to be fine.
As Ernst said it was a mess.
I dont want to know what¬†"Wer nicht h√∂ren will muss f√ľhlen!" means but I feel its not pleasant
i am off to a dark room now
regards
Philip

Just double checked and all is good. "Those who refuse to follow rules shall feel the consequences". Too right.





------ Original Message ------
From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>
Sent: 08/01/2022 11:10:00
Subject: Re: [MSG-1] FY-3D

On Sat, Jan 8, 2022 at 02:14 AM, Philip Robinson wrote:
Yes, i did restart the tellicast clients 
Philip,

I GIVE UP: You simply tell us the TelliCast client is broken as it is unable to log on D:.
Go on with your own "next step" of deleting all TelliCast stuff on C:. But don't blame
me if things don't work as expected anymore: "Wer nicht h√∂ren will muss f√ľhlen!"

Regards,
Ernst

Virus-free. www.avg.com


Re: FY-3D

Ernst Lobsiger
 

On Sat, Jan 8, 2022 at 02:14 AM, Philip Robinson wrote:
Yes, i did restart the tellicast clients 
Philip,

I GIVE UP: You simply tell us the TelliCast client is broken as it is unable to log on D:.
Go on with your own "next step" of deleting all TelliCast stuff on C:. But don't blame
me if things don't work as expected anymore: "Wer nicht h√∂ren will muss f√ľhlen!"

Regards,
Ernst


Re: FY-3D

Philip Robinson
 

Ernst
and restarted the client.ini
Philip


------ Original Message ------
From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>
Sent: 08/01/2022 10:08:14
Subject: Re: [MSG-1] FY-3D

On Sat, Jan 8, 2022 at 01:39 AM, Philip Robinson wrote:
I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\
Philip,

after you make changes in the client.ini you have to restart the client. At least you say now "you are sure you TRIED". But if you actually DID the change and restarted the client and it still does not log on D: (whether with or whitout the ">>"), then you are telling us BS again ...

Ernst

Virus-free. www.avg.com


Re: FY-3D

Philip Robinson
 

Ernst
Just saw your post after i sent mine.
Yes, i did restart the tellicast clients 
regards
Philip

------ Original Message ------
From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>
Sent: 08/01/2022 10:08:14
Subject: Re: [MSG-1] FY-3D

On Sat, Jan 8, 2022 at 01:39 AM, Philip Robinson wrote:
I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\
Philip,

after you make changes in the client.ini you have to restart the client. At least you say now "you are sure you TRIED". But if you actually DID the change and restarted the client and it still does not log on D: (whether with or whitout the ">>"), then you are telling us BS again ...

Ernst

Virus-free. www.avg.com


Re: FY-3D

Philip Robinson
 

Thorsten,
I spoke too soon
The logs are still going in to my C:\Logs folder
Oh well, everything else works. That will do for me for now , may be i will find out why that is at some time in the future.
tnx
Philip


------ Original Message ------
From: "Philip Robinson" <philip57@...>
Sent: 08/01/2022 09:39:41
Subject: Re: [MSG-1] FY-3D

Ernst/Thorsten
My running clients are all on Drive D: and all my target paths point there ( as i tried unfailing to explain). I should therefore not need any of those C: EUMETCast clients, folders  etc etc now that I have all my EUMETCast running clients , folders etc are on DRIVE D: 
However I was getting the strange part that my logs were being directed  to my C:drive Logs folder.
I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\
Of course if that works i will do the same for the bas and hvs-2 log paths
I will try later
thanks
Philip





------ Original Message ------
From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>
Sent: 08/01/2022 08:29:35
Subject: Re: [MSG-1] FY-3D

On Fri, Jan 7, 2022 at 11:12 AM, Philip Robinson wrote:
My next job will to be delete all my  EUMETCast folders on my C:Drive so I do not get in such a mess. Also let OPS know that I am all sorted now. Then to sort out getting my FY3D data in to EUMETCastview.
Philip,

it seems you still don't know whether your clients are on drive C: or drive D: as you installed them on both drives (that's what you said).
If what Thorsten just posted works for you, then the running client is probably started on C:. In this case your next job will complete your mess ...
Be careful.

Ernst

Virus-free. www.avg.com


Re: FY-3D

Ernst Lobsiger
 

On Sat, Jan 8, 2022 at 01:39 AM, Philip Robinson wrote:
I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\
Philip,

after you make changes in the client.ini you have to restart the client. At least you say now "you are sure you TRIED". But if you actually DID the change and restarted the client and it still does not log on D: (whether with or whitout the ">>"), then you are telling us BS again ...

Ernst


Re: FY-3D

Philip Robinson
 

Thorsten,
 I thought i would try that before i go out and it was just those two missing forward arrows.
I think it was because the two lines below that log_file line ( that is the license_file and channels_file)did not have the >> in front of the D:\.   And  the license_file and channels_file worked perfectly. I was then under the impression that the target path for my log file must also start just with D:\.  Obviously not i see.
My lack of script knowledge let me down. i had no idea what >> really meant in the scripting world. 
Note to myself  "must learn more about scripting"
Have a good day
thanks
Philip 
PS are you Danish or Swedish... your English is excellent and the same applies to Ernst.


------ Original Message ------
From: "Philip Robinson" <philip57@...>
Sent: 08/01/2022 09:39:41
Subject: Re: [MSG-1] FY-3D

Ernst/Thorsten
My running clients are all on Drive D: and all my target paths point there ( as i tried unfailing to explain). I should therefore not need any of those C: EUMETCast clients, folders  etc etc now that I have all my EUMETCast running clients , folders etc are on DRIVE D: 
However I was getting the strange part that my logs were being directed  to my C:drive Logs folder.
I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\
Of course if that works i will do the same for the bas and hvs-2 log paths
I will try later
thanks
Philip





------ Original Message ------
From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>
Sent: 08/01/2022 08:29:35
Subject: Re: [MSG-1] FY-3D

On Fri, Jan 7, 2022 at 11:12 AM, Philip Robinson wrote:
My next job will to be delete all my  EUMETCast folders on my C:Drive so I do not get in such a mess. Also let OPS know that I am all sorted now. Then to sort out getting my FY3D data in to EUMETCastview.
Philip,

it seems you still don't know whether your clients are on drive C: or drive D: as you installed them on both drives (that's what you said).
If what Thorsten just posted works for you, then the running client is probably started on C:. In this case your next job will complete your mess ...
Be careful.

Ernst

Virus-free. www.avg.com


Re: FY-3D

Philip Robinson
 

Ernst/Thorsten
My running clients are all on Drive D: and all my target paths point there ( as i tried unfailing to explain). I should therefore not need any of those C: EUMETCast clients, folders  etc etc now that I have all my EUMETCast running clients , folders etc are on DRIVE D: 
However I was getting the strange part that my logs were being directed  to my C:drive Logs folder.
I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\
Of course if that works i will do the same for the bas and hvs-2 log paths
I will try later
thanks
Philip





------ Original Message ------
From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>
Sent: 08/01/2022 08:29:35
Subject: Re: [MSG-1] FY-3D

On Fri, Jan 7, 2022 at 11:12 AM, Philip Robinson wrote:
My next job will to be delete all my  EUMETCast folders on my C:Drive so I do not get in such a mess. Also let OPS know that I am all sorted now. Then to sort out getting my FY3D data in to EUMETCastview.
Philip,

it seems you still don't know whether your clients are on drive C: or drive D: as you installed them on both drives (that's what you said).
If what Thorsten just posted works for you, then the running client is probably started on C:. In this case your next job will complete your mess ...
Be careful.

Ernst

Virus-free. www.avg.com

841 - 860 of 33410