Date   
Re: Confused about data types

geojohnt@...
 

Thomas,

Just to add, having had HD constipation, when I added HVS-1 to BS, I agree with David.
You really need to limit the data you receive.
Both in the data you have ticked in your EUMETCast account, and via your cast-client-channels_hvs-1.ini and cast-client-channels_bas.ini.

Gone are the days when you could receive 'everything' disseminated by EUMETCast.

I think I'm right in saying that some 'wanted data streams' also include data that you do not want - 'DARMSTADT sounding data' for instance in my case, which filled my HD, along with other not wanted data, which one/two of David's SatSignal processing programmes deletes - again, I think I'm right in saying.

Yes, as we say, "you can't see the wood for the trees."

Best wishes,
John.

++++++++++++++++ 

In a message dated 13/11/2019 19:26:53 GMT Standard Time, gm8arv@... writes:

Hi guys,

today my hvs1 and hvs2 data has been activated by eumetsat.

I am flashed about the the huge different kind of data packets and i wonder
how to process them an which software i should use.
[]
By the way is Msg-data-manager able to process Goes images?
[]
We say in german that we can't see the forest because of lot of trees ????

Regards
Thomas
=================================

Thomas,

Yes, the first need for most users is to limit the data you get, and the
processed data you want to keep!  Incoming data is 250+ GB/day on BS/HVS-1
and ~400 GB/day on HVS-2.

For GOES-15 I have free software:

  https://www.satsignal.eu/software/goes-15-netcdf-manager.html

and for GOES-16/17 too:

  https://www.satsignal.eu/software/GOES-ABI-Manager.html

I've done that rather than tagging yet another satellite with yet another
protocol onto the MSG Data Manager.

Cheers,
David

Re: The user day presentations are available

geojohnt@...
 

David,

Thanks for the link.
Some interesting information in the PPT presentations.

Regards,
John.

++++++++++++++++++++

In a message dated 14/11/2019 14:36:42 GMT Standard Time, gm8arv@... writes:

From EUMETSAT:

The user day presentations are available now on the below link


Click on Agenda.  Read what's planned for the future!

Cheers,
David

The user day presentations are available

David J Taylor
 

From EUMETSAT:

The user day presentations are available now on the below link

https://www.eventsforce.net/eumetsat/frontend/reg/tAgendaWebsite.csp?pageID=2939&ef_sel_menu=58&eventID=8&mode=

Click on Agenda. Read what's planned for the future!

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

Re: EUMETCastView on GNU/Linux

Ernst Lobsiger
 

Ho Oliver and Christoph

This is a common problem with 3D functions in Linux card drivers.
Windows drivers are normally provided by manufacturers while
Linux drivers are often reverse engineered. When I started to
make the 3D globe work I finally had to buy a cheap vNidia card
and go with the proprietary nVidia X-driver (that's normally not
done a on a Debian box). If you have an AMD card supported by
the amdgpu (not the older radeon) driver it might run out of
the box. Intel GPU (on board) graphics is well supported too.

Bottom line:

- nVidia: forget the nouveau driver, go propretary
- AMD: give open source and MESA a try
- Intel: try open source and hope for the best

As I have asked before: Please report working combinatione here.

My latest working HW combination out of the box:
- Debian 10 amd64 / MESA / amdgpu
- ATI FirePro W5000 2048MB
as usual on old I7 PCs that other people threw away.

Cheers,
Ernst

Re: Confused about data types

David J Taylor
 

Hi guys,

today my hvs1 and hvs2 data has been activated by eumetsat.

I am flashed about the the huge different kind of data packets and i wonder
how to process them an which software i should use.
[]
By the way is Msg-data-manager able to process Goes images?
[]
We say in german that we can't see the forest because of lot of trees ????

Regards
Thomas
=================================

Thomas,

Yes, the first need for most users is to limit the data you get, and the processed data you want to keep! Incoming data is 250+ GB/day on BS/HVS-1 and ~400 GB/day on HVS-2.

For GOES-15 I have free software:

https://www.satsignal.eu/software/goes-15-netcdf-manager.html

and for GOES-16/17 too:

https://www.satsignal.eu/software/GOES-ABI-Manager.html

I've done that rather than tagging yet another satellite with yet another protocol onto the MSG Data Manager.

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

Confused about data types

Thomas Scheelen
 

Hi guys,


today my hvs1 and hvs2 data has been activated by eumetsat.


I am flashed about the the huge different kind of data packets and i wonder how to process them an which software i should use.


I already read a lot guides and websites, but it somehow confuses me even more.. 😊


Is there any overview about the filenames and their corresponding products?


Eumetcast-viewer appears to be great for Goes 16/17 and some Sentinel images.
But it can not handle all sentinel data and not that stable and fast.


By the way is Msg-data-manager able to process Goes images?


I receive a lot of different sounding data with "Darmstadt" in their filenames. I know what sounding means, but i wonder if they are useful and how to block them.


I could ask so many more questions, but i don't want to nerve.. 😄


We say in german that we can't see the forest because of lot of trees 😄


Regards
Thomas

Re: EUMETCastView on GNU/Linux

Christoph Neuhaus
 

Dear Olivier,


Furthermore, I tried it on the Intel NUC using Windows 10 and the
latest v1.4.7 .exe, which works fine, including 3D globe. So HW
works.
this indicates a driver issue; the currently installed linux mesa driver does not support the shader language GLSL version 3.30, obviously the windows counter part does.

For the NUC you could give the drivers from
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
a try. They should provide you with the most current version of the mesa and intel drivers, and according to
https://mesamatrix.net/
the GLSL version required by EUMETCastView is supported.

The drivers might even work on your other hardware, although it's always difficult to tell with older nVidia and AMD cards.

Good luck,
Christoph



Am 13.11.19 um 17:29 schrieb hb9erg.kd0hop@...:
Hi all,
thanks for all your valuable information and your EUMETCastView compilation HowTo!
Everything went very well, using EUMETCastView v1.4.7; I successfully compiled the software on Debian 10 and Xubuntu LTS (more details below).
*** BUT: Here's my Problem ***
Unfortunately, I don't get the 3D Globe to work. It will show green text: around "60 paintGL calls / s", and after activation of the ground station info also these "Maspalomas, Lannion" etc etc. It also lets me choose segments, but I have no Globe and no background (corona).
I tried it on different hardware:
- hp pavilion dv7 6c40ez (CPU: Intel Core i7-2670QM, 2,2GHz, 4 cores - GPU: AMD Radeon HD 7470M)
- ASUS K56CB (CPU: Intel Core i7-3537U, 4 cores - GPU: NVIDIA® GeForce® GT 740M)
- Intel NUC D54250WYK (CPU: Intel Core i5-4250U 1.3GHz, 2 cores - GPU: Intel® HD-Grafik 5000)
Furthermore, I tried it on the Intel NUC using Windows 10 and the latest v1.4.7 .exe, which works fine, including 3D globe. So HW works.
Now I'm trying to get it to work on the Intel NUC, using Xubuntu 18.04.3 LTS.
*** Console Outputs (for your information) ***
cat /etc/lsb-release | grep DESC ; uname -a; lscpu | grep "Model name"; glxinfo | grep OpenGL | head -3
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
Linux ops-nuc 5.0.0-35-generic #38~18.04.1-Ubuntu SMP Mon Nov 11 09:16:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.8
glxinfo | grep -i "version"
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Version: 19.0.8
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.8
OpenGL core profile shading language version string: 4.50
OpenGL version string: 3.0 Mesa 19.0.8
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
    GL_EXT_shader_implicit_conversions, GL_EXT_shader_integer_mix,
ops@ops-nuc:~$ glxinfo | grep -i "OpenGL"
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.8
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 19.0.8
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
*** But Here's The Problem.... ***
When I start EUMETCastView from the terminal, choose the 3D globe menu, it outputs:
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Warning: QOpenGLShader::compile(Vertex): 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES
Release Warning: *** Problematic Vertex shader source code ***
#version 330
#define lowp
#define mediump
#define highp
#line 1
layout(location=0) in vec3 VertexPosition;
uniform mat4 MVP;
uniform mat3 NormalMatrix;
uniform vec4 outcolor;
out vec3 Normal;
void main()
{
    Normal = normalize(NormalMatrix * VertexPosition);
    gl_Position = MVP * vec4(VertexPosition,1.0);
}
***
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Warning: QOpenGLShader::compile(Vertex): 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES
Release Warning: *** Problematic Vertex shader source code ***
#version 330
#define lowp
#define mediump
#define highp
#line 1
layout(location=0) in vec3 VertexPosition;
uniform mat4 MVP;
uniform mat3 NormalMatrix;
out vec3 Normal;
out float angle;
void main()
{
    Normal = normalize(NormalMatrix * VertexPosition);
    angle = 1 / MVP[3].w;
    gl_Position = MVP * vec4(VertexPosition,1.0);
}
***
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Warning: QOpenGLShader::compile(Vertex): 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES
Release Warning: *** Problematic Vertex shader source code ***
#version 330
#define lowp
#define mediump
#define highp
#line 1
//layout(location=0) in vec2 VertexPosition;
//layout(location=1) in float VertexTexCoord;
in vec2 VertexPosition;
in float VertexTexCoord;
out float texCoord;
void main()
{
    gl_Position = vec4(VertexPosition, 0.0, 1.0);
    texCoord = VertexTexCoord;
}
***
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "gshhsdata positions.size() = 0"
Release Debug: "gshhsdata totalverts = 0"
Release Debug: SkyBox::loadCubemap x loaded
Release Debug: SkyBox::loadCubemap _x loaded
Release Debug: SkyBox::loadCubemap y loaded
Release Debug: SkyBox::loadCubemap _y loaded
Release Debug: SkyBox::loadCubemap z loaded
Release Debug: SkyBox::loadCubemap _z loaded
Release Debug: "ID cubemapTexture = 2"
Release Debug: "setCylOrGlobe = 1"
Release Debug: "na setCylOrGlobe = 1"
*** May you help me? ***
On the ASUS laptop, I tried to install other Linux graphics drivers using (in dir. /usr/bin):
wget -Nc smxi.org/sgfxi && chmod +x sgfxi && sgfxi
Do I need to change something in the source code, so that it will let me use the GLSL 3.30?
Thank you a lot in advance for your assistance, it's very much appreciated!
Greetings from Olivier, HB9ERG - Basel, Switzerland

--
____________________________________________

University of Bern
Remote Sensing Research Group

Christoph Neuhaus
ICT expert

Hallerstrasse 12
3012 Bern - Switzerland

e-mail: christoph.neuhaus@...
skype: nihil14
___________________________________________

Re: EUMETCastView on GNU/Linux

hb9erg.kd0hop@...
 

Hi all,

thanks for all your valuable information and your EUMETCastView compilation HowTo!

Everything went very well, using EUMETCastView v1.4.7; I successfully compiled the software on Debian 10 and Xubuntu LTS (more details below).

*** BUT: Here's my Problem ***
Unfortunately, I don't get the 3D Globe to work. It will show green text: around "60 paintGL calls / s", and after activation of the ground station info also these "Maspalomas, Lannion" etc etc. It also lets me choose segments, but I have no Globe and no background (corona).

I tried it on different hardware:
- hp pavilion dv7 6c40ez (CPU: Intel Core i7-2670QM, 2,2GHz, 4 cores - GPU: AMD Radeon HD 7470M)
- ASUS K56CB (CPU: Intel Core i7-3537U, 4 cores - GPU: NVIDIA® GeForce® GT 740M)
- Intel NUC D54250WYK (CPU: Intel Core i5-4250U 1.3GHz, 2 cores - GPU: Intel® HD-Grafik 5000)

Furthermore, I tried it on the Intel NUC using Windows 10 and the latest v1.4.7 .exe, which works fine, including 3D globe. So HW works.

Now I'm trying to get it to work on the Intel NUC, using Xubuntu 18.04.3 LTS.

*** Console Outputs (for your information) ***

cat /etc/lsb-release | grep DESC ; uname -a; lscpu | grep "Model name"; glxinfo | grep OpenGL | head -3

DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
Linux ops-nuc 5.0.0-35-generic #38~18.04.1-Ubuntu SMP Mon Nov 11 09:16:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.8

glxinfo | grep -i "version"
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Version: 19.0.8
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.8
OpenGL core profile shading language version string: 4.50
OpenGL version string: 3.0 Mesa 19.0.8
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
    GL_EXT_shader_implicit_conversions, GL_EXT_shader_integer_mix,

ops@ops-nuc:~$ glxinfo | grep -i "OpenGL"
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.8
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 19.0.8
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:




*** But Here's The Problem.... ***
When I start EUMETCastView from the terminal, choose the 3D globe menu, it outputs:

Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Warning: QOpenGLShader::compile(Vertex): 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES

Release Warning: *** Problematic Vertex shader source code ***
#version 330
#define lowp
#define mediump
#define highp
#line 1

layout(location=0) in vec3 VertexPosition;

uniform mat4 MVP;
uniform mat3 NormalMatrix;
uniform vec4 outcolor;

out vec3 Normal;

void main()
{
    Normal = normalize(NormalMatrix * VertexPosition);
    gl_Position = MVP * vec4(VertexPosition,1.0);
}

***
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Warning: QOpenGLShader::compile(Vertex): 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES

Release Warning: *** Problematic Vertex shader source code ***
#version 330
#define lowp
#define mediump
#define highp
#line 1

layout(location=0) in vec3 VertexPosition;

uniform mat4 MVP;
uniform mat3 NormalMatrix;

out vec3 Normal;
out float angle;

void main()
{
    Normal = normalize(NormalMatrix * VertexPosition);
    angle = 1 / MVP[3].w;
    gl_Position = MVP * vec4(VertexPosition,1.0);
}

***
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Warning: QOpenGLShader::compile(Vertex): 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES

Release Warning: *** Problematic Vertex shader source code ***
#version 330
#define lowp
#define mediump
#define highp
#line 1

//layout(location=0) in vec2 VertexPosition;
//layout(location=1) in float VertexTexCoord;

in vec2 VertexPosition;
in float VertexTexCoord;

out float texCoord;

void main()
{
    gl_Position = vec4(VertexPosition, 0.0, 1.0);
    texCoord = VertexTexCoord;
}

***
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES\n"
Release Debug: "gshhsdata positions.size() = 0"
Release Debug: "gshhsdata totalverts = 0"
Release Debug: SkyBox::loadCubemap x loaded
Release Debug: SkyBox::loadCubemap _x loaded
Release Debug: SkyBox::loadCubemap y loaded
Release Debug: SkyBox::loadCubemap _y loaded
Release Debug: SkyBox::loadCubemap z loaded
Release Debug: SkyBox::loadCubemap _z loaded
Release Debug: "ID cubemapTexture = 2"
Release Debug: "setCylOrGlobe = 1"
Release Debug: "na setCylOrGlobe = 1"




*** May you help me? ***
On the ASUS laptop, I tried to install other Linux graphics drivers using (in dir. /usr/bin):
wget -Nc smxi.org/sgfxi && chmod +x sgfxi && sgfxi

Do I need to change something in the source code, so that it will let me use the GLSL 3.30?

Thank you a lot in advance for your assistance, it's very much appreciated!

Greetings from Olivier, HB9ERG - Basel, Switzerland

Re: TP 1.

David J Taylor
 

Hi all!

Signal drop is caused due to excessive snow fall in Aflenz Austria (Satellite Uplink): 800mm in 24h!

Regards

Hartmut
================================

Thanks for that report, Hartmut.

Interesting that it didn't seem to affect TP2 anything like as much. Perhaps TP2 is being uplinked from Vienna?

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

Re: TP 1.

geojohnt@...
 

Hello Hartmut,

Goodness!

Leise rieselt der Schnee .....

Good news for the upcoming winter sport season and my favourite Ski Sprungen.

SNR slowly creeping up - snowfall easing off, or men out sweeping the dish with brooms?

Best wishes,
John.

++++++++++++++

 In a message dated 13/11/2019 12:37:18 GMT Standard Time, mail@... writes:

Signal drop is caused due to excessive snow fall in Aflenz Austria (Satellite Uplink): 800mm in 24h!

Re: TP 1.

Hartmut Schulla
 

Hi all!

Signal drop is caused due to excessive snow fall in Aflenz Austria (Satellite Uplink): 800mm in 24h!

Regards

Hartmut

 

Von: MSG-1@groups.io [mailto:MSG-1@groups.io] Im Auftrag von geojohnt via Groups.Io
Gesendet: Mittwoch, 13. November 2019 13:34
An: msg-1@groups.io
Betreff: [MSG-1] TP 1.

 

All,


Ah good.

Well, not, really.

 

I've just accessed David's EUMETCast Europe reporting page and found that everyone is experiencing 'dropped' SNR.

Mine was down to 9.7 dB earlier which caused HVS-1 to lose lock.

 

I'm back up to 11.3/4 at 12:30 UTC - where it should be 13.0 dB.

 

Regards,

John T.

 

 

 

 

TP 1.

geojohnt@...
 

All,

Ah good.
Well, not, really.

I've just accessed David's EUMETCast Europe reporting page and found that everyone is experiencing 'dropped' SNR.
Mine was down to 9.7 dB earlier which caused HVS-1 to lose lock.

I'm back up to 11.3/4 at 12:30 UTC - where it should be 13.0 dB.

Regards,
John T.




Re: Strange Fading effects

geojohnt@...
 

Thomas,

We have a saying in English:

if it ain’t brokedon’t fix it

    1. Leave something alone; avoid attempting to correctfix, or improve what is already sufficient (often with an implication that the attempted improvement is risky and might backfire).
      I know it’s an ugly-looking antenna, but you know what they say: If it ain’t broke, don’t fix it.

I quite often find when suffering, what I think is, slightly reduced signal levels that 'giving the dish a bit of a tweak,' makes things worse.

Best wishes,
John.

+++++++++++++++++

In a message dated 13/11/2019 07:49:35 GMT Standard Time, privat@... writes:

Ernst,

i agree. It was just a short thought.
Now i got a steady signal and someone told me..... never change a running system.. 😄

Regards
Thomas

Re: Strange Fading effects

geojohnt@...
 

Hello Thomas,

Sorry for the delay in responding.
I've been visiting my Belgian relations attending the WW1 Armistice ceremonies in Ypres.

You are right.
The accuracy of motor driven dishes is good enough for EUMETCast use.
OK for satellite TV where signals are mostly stronger and where accurate dish alignment is not so critical.

Best wishes,
John.
 
++++++++++++++++++++

In a message dated 09/11/2019 22:04:11 GMT Standard Time, privat@... writes:

By the way... is it a good idea to mount the new dish on a diseqc motor? Could imagine that the repeat accuracy is not precise enough.

Re: Strange Fading effects

Thomas Scheelen
 

Ernst, 

i agree. It was just a short thought. 
Now i got a steady signal and someone told me..... never change a running system.. 😄 

Regards 
Thomas 

Am 12. November 2019 21:01:47 schrieb "Ernst Lobsiger" <ernst.lobsiger@...>:

Thomas,

I'd guess a diseq motor  mount is not for EUMETCast with a 1.2m dish.
I'm quite sure you will run into mechanical precision problems and
also problems to feed the motor with current via your TBS-5927.

Regards
Ernst

Re: Strange Fading effects

Cornish Man
 

I am using a Stab HH120 with my 110cm dish, It's rated for  120cm through

But i was thinking to just go with the dish setup alone as I don't move the dish anyway

Got a TBS 6903 card which I can move the dish with if I want

Cheers

Jan

On Tuesday, 12 November 2019, 20:01:23 GMT, Ernst Lobsiger <ernst.lobsiger@...> wrote:


Thomas,

I'd guess a diseq motor  mount is not for EUMETCast with a 1.2m dish.
I'm quite sure you will run into mechanical precision problems and
also problems to feed the motor with current via your TBS-5927.

Regards
Ernst

Re: Strange Fading effects

Ernst Lobsiger
 

Thomas,

I'd guess a diseq motor  mount is not for EUMETCast with a 1.2m dish.
I'm quite sure you will run into mechanical precision problems and
also problems to feed the motor with current via your TBS-5927.

Regards
Ernst

Re: Hvs

Ferdinand Valk
 

Hi Thomas,

 

The Sentinel data on HVS-2 is indeed used for more specialized applications. Much of the data can also be had via the Internet and thus the effort and expense the required to receive and decode is most likely not in proportion to its use for many of the amateur users.

 

Modis data comes from the Aqua and Terra satellites. If you are interested in these, you should also have a look at the VIIRS data from Suomi NPP and NOAA20, which is the follow-up of Modis.

 

Ferdinand

 

From: MSG-1@groups.io On Behalf Of Thomas Scheelen
Sent: Saturday, 09 November, 2019 21:52
To: MSG-1@groups.io
Subject: Re: [MSG-1] Hvs

 

Hi Ferdinand, 

 

Thx for the explanation. 

 

I already filled the form, but i was pretty flashed about all the new stuff in there. 

 

The HVS on transpoder2 is still a little mystery, because does anybody of the enthusiastic users working with those data? 

 

First i thought sentinel data offers a eay for much higher resolution and better quality, but i guess those data are only usable for analyzes. I am happy if iam wrong... 😄 

 

Another new (old) thing i discovered is modis-l1 data. No idea why i never looked deeper into this. The images are quite impressive. 

 

But which satellite does transmit modis-l1 data? Hopefully it is not an obsolete feature... 

 

Many questions.... 😄 

 

@David 

 

I thank you for the information about the upgrades. How about the other tools which not in the tool packages? 

 

Kind Regards 

Thomas 

 

Am 8. November 2019 08:13:38 schrieb "Ferdinand Valk" <fvalk@...>:

Hi Thomas,

 

You do not need to request HVS as such but you must make sure you have requested/selected the items in the EO portal such as Third Party Data Services for Goes East and West, Himawari etc. which are delivered via HVS-1 and the Copernicus entries if you are looking for HVS-2.

 

Cheers,

Ferdinand

 

From: MSG-1@groups.io On Behalf Of Thomas Scheelen
Sent: Thursday, 07 November, 2019 22:01
To: MSG-1@groups.io
Subject: [MSG-1] Hvs

 

I wonder if i need to fill a separate registration request for HVS reception.

 

I already have pid 600 + 601 activ, but no hvs data yet.

 

Regards 

Thomas 

 

Re: Strange Fading effects

Thomas Scheelen
 

John, 

unfortunately i had no time yet to install the new dish. The basic service is very stable indeed.Even in heavy cloud conditions with rain the s/n dropped just 0,5 db. 

By the way... is it a good idea to mount the new dish on a diseqc motor? Could imagine that the repeat accuracy is not precise enough. 

Regards 

Am 8. November 2019 16:10:39 schrieb "geojohnt via Groups.Io" <geojohnt@...>:

Hello Thomas,

With a 120 cm dish you 'should' get around 2 dB better SNR with a correctly aligned dish.
Very important for HVS-1 services which have a much lower link margin level than BS.
Rain/snow signal attenuation reduces SNR but BS with its higher link margin level is not as badly effected as HVS-1 if the signal attenuation is high.

Best wishes,
John.

++++++++++++++++++++++++++++++

In a message dated 08/11/2019 10:46:32 GMT Standard Time, gm8arv@... writes:

now i got the 5927 and what shall I say? Everything is fine, even with the
85cm dish.
I have 11DB s/n and almost no errors or lost of packets.

I am curious how the 120cm dish will improve the whole thing.

Re: Hvs

Thomas Scheelen
 

Hi Ferdinand, 

Thx for the explanation. 

I already filled the form, but i was pretty flashed about all the new stuff in there. 

The HVS on transpoder2 is still a little mystery, because does anybody of the enthusiastic users working with those data? 

First i thought sentinel data offers a eay for much higher resolution and better quality, but i guess those data are only usable for analyzes. I am happy if iam wrong... 😄 

Another new (old) thing i discovered is modis-l1 data. No idea why i never looked deeper into this. The images are quite impressive. 

But which satellite does transmit modis-l1 data? Hopefully it is not an obsolete feature... 

Many questions.... 😄 

@David 

I thank you for the information about the upgrades. How about the other tools which not in the tool packages? 

Kind Regards 
Thomas 

Am 8. November 2019 08:13:38 schrieb "Ferdinand Valk" <fvalk@...>:

Hi Thomas,

 

You do not need to request HVS as such but you must make sure you have requested/selected the items in the EO portal such as Third Party Data Services for Goes East and West, Himawari etc. which are delivered via HVS-1 and the Copernicus entries if you are looking for HVS-2.

 

Cheers,

Ferdinand

 

From: MSG-1@groups.io On Behalf Of Thomas Scheelen
Sent: Thursday, 07 November, 2019 22:01
To: MSG-1@groups.io
Subject: [MSG-1] Hvs

 

I wonder if i need to fill a separate registration request for HVS reception.

 

I already have pid 600 + 601 activ, but no hvs data yet.

 

Regards 

Thomas