Topics

Getting HVS Transponder 2 channel data

Peter Chiu - UKRI STFC
 

Dear all,

 

We have recently set up our receiving station to collect data from the High Volume Service

Transponder 1 channels such as E1H-EPS-1, EPS-2, EPS-5, etc.  This has been working fine.

 

However, when we try to do the same set up for the channels on HVS-2, such as

E2H-S3A-01, E2H-S3A-02, etc, we are having problems.  We cannot establish the connection

to the announcement channel on TSL-HVS-2: using the address: 224.223.224.223:4711

as described in:

https://www.eumetsat.int/website/home/Data/DataDelivery/EUMETCast/ReceptionStationSetup/ChannelsandPIDs/index.html

 

 

High Volume Service Transponder 2: Current multicast channels and PIDs

Channel Name

PID (Decimal)

Multicast Address

Max Multicast Data Rate (kbps)

Remark

TSL-HVS-2

610

224.223.224.223:4711

100

Announcement Channel

E2H-S3A-01

610

224.223.224.10

45000

S3A OLCI Level 1 Full Resolution

 

I have attached the log file below.

 

I wonder if we have missed out something in our set-up, as

we have used the similar set up as with HVS-1.  I have also

changed the Ayecak SR1 DVB-S2 receiver MODCOD from

H0041000 to %H1FFFFFFF, but that makes no difference.

 

Any advice will be much appreciated.

 

Regards,

Peter

 

Log File

Lvl:Date       Time (UTC)  :Message

MSG:2019-07-11 14:07:30.572:Program started =============

MSG:2019-07-11 14:07:30.572:Watchdog starting... [325]

MSG:2019-07-11 14:07:30.572:Watchdog started [325].

MSG:2019-07-11 14:07:34.742:Starting new child...

MSG:2019-07-11 14:07:34.742:Started new child [377].

MSG:2019-07-11 14:07:37.792:Log level is "normal".

MSG:2019-07-11 14:07:37.793:tc-cast-client starting... [377]

MSG:2019-07-11 14:07:37.793:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-11 14:07:37.795:License check succeeded

MSG:2019-07-11 14:07:37.798:tc-cast-client running [377].

MSG:2019-07-11 14:10:53.253:Watchdog received signal: Initiating child shutdown

MSG:2019-07-11 14:10:53.253:Watchdog shutting down ... [325]

ERR:2019-07-11 14:09:37.809:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-11 14:10:53.253:tc-cast-client shutting down... [377]

MSG:2019-07-11 14:10:53.654:tc-cast-client stopped [377].

MSG:2019-07-11 14:10:53.656:Watchdog child quits properly. Shutting down.

MSG:2019-07-11 14:10:53.656:Watchdog stopped [325].

MSG:2019-07-11 14:10:59.473:Program started =============

MSG:2019-07-11 14:10:59.473:Watchdog starting... [2177]

MSG:2019-07-11 14:10:59.473:Watchdog started [2177].

MSG:2019-07-11 14:11:02.185:Starting new child...

MSG:2019-07-11 14:11:02.185:Started new child [2217].

MSG:2019-07-11 14:11:05.797:Log level is "normal".

MSG:2019-07-11 14:11:05.798:tc-cast-client starting... [2217]

MSG:2019-07-11 14:11:05.798:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-11 14:11:05.799:License check succeeded

MSG:2019-07-11 14:11:05.803:tc-cast-client running [2217].

ERR:2019-07-11 14:13:05.814:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-11 15:30:13.200:Watchdog received signal: Initiating child shutdown

MSG:2019-07-11 15:30:13.200:Watchdog shutting down ... [2177]

MSG:2019-07-11 15:30:13.200:tc-cast-client shutting down... [2217]

MSG:2019-07-11 15:30:13.601:tc-cast-client stopped [2217].

MSG:2019-07-11 15:30:13.602:Watchdog child quits properly. Shutting down.

MSG:2019-07-11 15:30:13.602:Watchdog stopped [2177].

MSG:2019-07-11 15:30:19.415:Program started =============

MSG:2019-07-11 15:30:19.415:Watchdog starting... [32049]

MSG:2019-07-11 15:30:19.415:Watchdog started [32049].

MSG:2019-07-11 15:30:22.742:Starting new child...

MSG:2019-07-11 15:30:22.742:Started new child [32089].

MSG:2019-07-11 15:30:25.814:Log level is "normal".

MSG:2019-07-11 15:30:25.815:tc-cast-client starting... [32089]

MSG:2019-07-11 15:30:25.815:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-11 15:30:25.816:License check succeeded

MSG:2019-07-11 15:30:25.820:tc-cast-client running [32089].

ERR:2019-07-11 15:32:25.831:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-12 08:49:49.911:Watchdog received signal: Initiating child shutdown

MSG:2019-07-12 08:49:49.911:Watchdog shutting down ... [32049]

MSG:2019-07-12 08:49:49.911:tc-cast-client shutting down... [32089]

MSG:2019-07-12 08:49:50.312:tc-cast-client stopped [32089].

MSG:2019-07-12 08:49:50.313:Watchdog child quits properly. Shutting down.

MSG:2019-07-12 08:49:50.313:Watchdog stopped [32049].

MSG:2019-07-12 08:49:56.141:Program started =============

MSG:2019-07-12 08:49:56.141:Watchdog starting... [24828]

MSG:2019-07-12 08:49:56.141:Watchdog started [24828].

MSG:2019-07-12 08:49:58.529:Starting new child...

MSG:2019-07-12 08:49:58.529:Started new child [24862].

MSG:2019-07-12 08:50:01.335:Log level is "normal".

MSG:2019-07-12 08:50:01.346:tc-cast-client starting... [24862]

MSG:2019-07-12 08:50:01.346:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-12 08:50:01.357:License check succeeded

MSG:2019-07-12 08:50:01.373:tc-cast-client running [24862].

MSG:2019-07-12 09:08:30.529:Watchdog received signal: Initiating child shutdown

ERR:2019-07-12 08:52:01.385:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-12 09:08:30.529:Watchdog shutting down ... [24828]

MSG:2019-07-12 09:08:30.529:tc-cast-client shutting down... [24862]

MSG:2019-07-12 09:08:30.529:Disconnect from announcement channel `TSL-HVS-2', address 224.223.224.223:4711 completed (shutdown)

MSG:2019-07-12 09:08:30.930:tc-cast-client stopped [24862].

MSG:2019-07-12 09:08:30.931:Watchdog child quits properly. Shutting down.

MSG:2019-07-12 09:08:30.931:Watchdog stopped [24828].

MSG:2019-07-12 09:08:36.766:Program started =============

MSG:2019-07-12 09:08:36.766:Watchdog starting... [31681]

MSG:2019-07-12 09:08:36.766:Watchdog started [31681].

MSG:2019-07-12 09:08:40.432:Starting new child...

MSG:2019-07-12 09:08:40.432:Started new child [31730].

MSG:2019-07-12 09:08:44.128:Log level is "normal".

MSG:2019-07-12 09:08:44.129:tc-cast-client starting... [31730]

MSG:2019-07-12 09:08:44.129:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-12 09:08:44.130:License check succeeded

MSG:2019-07-12 09:08:44.134:tc-cast-client running [31730].

 

Cornish Man
 

Hi

I have never been able to connect to HVS 2 and only been able to get 1 or 2 channels for HVS 1
Maybe I need a bigger dish

Cheers

On Monday, 15 July 2019, 08:56:58 BST, Peter Chiu - UKRI STFC <peter.chiu@...> wrote:


Dear all,

 

We have recently set up our receiving station to collect data from the High Volume Service

Transponder 1 channels such as E1H-EPS-1, EPS-2, EPS-5, etc.  This has been working fine.

 

However, when we try to do the same set up for the channels on HVS-2, such as

E2H-S3A-01, E2H-S3A-02, etc, we are having problems.  We cannot establish the connection

to the announcement channel on TSL-HVS-2: using the address: 224.223.224.223:4711

as described in:

https://www.eumetsat.int/website/home/Data/DataDelivery/EUMETCast/ReceptionStationSetup/ChannelsandPIDs/index.html

 

 

High Volume Service Transponder 2: Current multicast channels and PIDs

Channel Name

PID (Decimal)

Multicast Address

Max Multicast Data Rate (kbps)

Remark

TSL-HVS-2

610

224.223.224.223:4711

100

Announcement Channel

E2H-S3A-01

610

224.223.224.10

45000

S3A OLCI Level 1 Full Resolution

 

I have attached the log file below.

 

I wonder if we have missed out something in our set-up, as

we have used the similar set up as with HVS-1.  I have also

changed the Ayecak SR1 DVB-S2 receiver MODCOD from

H0041000 to %H1FFFFFFF, but that makes no difference.

 

Any advice will be much appreciated.

 

Regards,

Peter

 

Log File

Lvl:Date       Time (UTC)  :Message

MSG:2019-07-11 14:07:30.572:Program started =============

MSG:2019-07-11 14:07:30.572:Watchdog starting... [325]

MSG:2019-07-11 14:07:30.572:Watchdog started [325].

MSG:2019-07-11 14:07:34.742:Starting new child...

MSG:2019-07-11 14:07:34.742:Started new child [377].

MSG:2019-07-11 14:07:37.792:Log level is "normal".

MSG:2019-07-11 14:07:37.793:tc-cast-client starting... [377]

MSG:2019-07-11 14:07:37.793:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-11 14:07:37.795:License check succeeded

MSG:2019-07-11 14:07:37.798:tc-cast-client running [377].

MSG:2019-07-11 14:10:53.253:Watchdog received signal: Initiating child shutdown

MSG:2019-07-11 14:10:53.253:Watchdog shutting down ... [325]

ERR:2019-07-11 14:09:37.809:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-11 14:10:53.253:tc-cast-client shutting down... [377]

MSG:2019-07-11 14:10:53.654:tc-cast-client stopped [377].

MSG:2019-07-11 14:10:53.656:Watchdog child quits properly. Shutting down.

MSG:2019-07-11 14:10:53.656:Watchdog stopped [325].

MSG:2019-07-11 14:10:59.473:Program started =============

MSG:2019-07-11 14:10:59.473:Watchdog starting... [2177]

MSG:2019-07-11 14:10:59.473:Watchdog started [2177].

MSG:2019-07-11 14:11:02.185:Starting new child...

MSG:2019-07-11 14:11:02.185:Started new child [2217].

MSG:2019-07-11 14:11:05.797:Log level is "normal".

MSG:2019-07-11 14:11:05.798:tc-cast-client starting... [2217]

MSG:2019-07-11 14:11:05.798:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-11 14:11:05.799:License check succeeded

MSG:2019-07-11 14:11:05.803:tc-cast-client running [2217].

ERR:2019-07-11 14:13:05.814:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-11 15:30:13.200:Watchdog received signal: Initiating child shutdown

MSG:2019-07-11 15:30:13.200:Watchdog shutting down ... [2177]

MSG:2019-07-11 15:30:13.200:tc-cast-client shutting down... [2217]

MSG:2019-07-11 15:30:13.601:tc-cast-client stopped [2217].

MSG:2019-07-11 15:30:13.602:Watchdog child quits properly. Shutting down.

MSG:2019-07-11 15:30:13.602:Watchdog stopped [2177].

MSG:2019-07-11 15:30:19.415:Program started =============

MSG:2019-07-11 15:30:19.415:Watchdog starting... [32049]

MSG:2019-07-11 15:30:19.415:Watchdog started [32049].

MSG:2019-07-11 15:30:22.742:Starting new child...

MSG:2019-07-11 15:30:22.742:Started new child [32089].

MSG:2019-07-11 15:30:25.814:Log level is "normal".

MSG:2019-07-11 15:30:25.815:tc-cast-client starting... [32089]

MSG:2019-07-11 15:30:25.815:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-11 15:30:25.816:License check succeeded

MSG:2019-07-11 15:30:25.820:tc-cast-client running [32089].

ERR:2019-07-11 15:32:25.831:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-12 08:49:49.911:Watchdog received signal: Initiating child shutdown

MSG:2019-07-12 08:49:49.911:Watchdog shutting down ... [32049]

MSG:2019-07-12 08:49:49.911:tc-cast-client shutting down... [32089]

MSG:2019-07-12 08:49:50.312:tc-cast-client stopped [32089].

MSG:2019-07-12 08:49:50.313:Watchdog child quits properly. Shutting down.

MSG:2019-07-12 08:49:50.313:Watchdog stopped [32049].

MSG:2019-07-12 08:49:56.141:Program started =============

MSG:2019-07-12 08:49:56.141:Watchdog starting... [24828]

MSG:2019-07-12 08:49:56.141:Watchdog started [24828].

MSG:2019-07-12 08:49:58.529:Starting new child...

MSG:2019-07-12 08:49:58.529:Started new child [24862].

MSG:2019-07-12 08:50:01.335:Log level is "normal".

MSG:2019-07-12 08:50:01.346:tc-cast-client starting... [24862]

MSG:2019-07-12 08:50:01.346:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-12 08:50:01.357:License check succeeded

MSG:2019-07-12 08:50:01.373:tc-cast-client running [24862].

MSG:2019-07-12 09:08:30.529:Watchdog received signal: Initiating child shutdown

ERR:2019-07-12 08:52:01.385:Failed to open announcement channel `TSL-HVS-2', address 224.223.224.223:4711 (Connect failed)

MSG:2019-07-12 09:08:30.529:Watchdog shutting down ... [24828]

MSG:2019-07-12 09:08:30.529:tc-cast-client shutting down... [24862]

MSG:2019-07-12 09:08:30.529:Disconnect from announcement channel `TSL-HVS-2', address 224.223.224.223:4711 completed (shutdown)

MSG:2019-07-12 09:08:30.930:tc-cast-client stopped [24862].

MSG:2019-07-12 09:08:30.931:Watchdog child quits properly. Shutting down.

MSG:2019-07-12 09:08:30.931:Watchdog stopped [24828].

MSG:2019-07-12 09:08:36.766:Program started =============

MSG:2019-07-12 09:08:36.766:Watchdog starting... [31681]

MSG:2019-07-12 09:08:36.766:Watchdog started [31681].

MSG:2019-07-12 09:08:40.432:Starting new child...

MSG:2019-07-12 09:08:40.432:Started new child [31730].

MSG:2019-07-12 09:08:44.128:Log level is "normal".

MSG:2019-07-12 09:08:44.129:tc-cast-client starting... [31730]

MSG:2019-07-12 09:08:44.129:tc-cast-client version is 2.12.1 (201403101226668) revision 6419b5403b33 linux2.6_deb4.0-i86pc release  (Linux 2.6.32-696.18.7.el6.x86_64 on a 4-processor (GenuineIntel, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz (Model 94, Stepping 3)) system)

MSG:2019-07-12 09:08:44.130:License check succeeded

MSG:2019-07-12 09:08:44.134:tc-cast-client running [31730].

 

Hugo
 

Hello Peter and Cornish man,

I see that both of you are using version 2.12.1. Could that be the problem ?

Kind regards,

Hugo

Peter Chiu - UKRI STFC
 

Thanks all,

 

I have received a reply from Pamela.  She told me that we

need a second receiver to read data from the 2nd transponder.

 

I shall try to contact Ayecka as we may have hit an awkward situation

that we have exhausted the (two) Ethernet ports on the server host.

 

Regards,

Peter

 

From: MSG-1@groups.io <MSG-1@groups.io> On Behalf Of Hugo
Sent: 15 July 2019 10:17
To: MSG-1@groups.io
Subject: Re: [MSG-1] Getting HVS Transponder 2 channel data

 

Hello Peter and Cornish man,

I see that both of you are using version 2.12.1. Could that be the problem ?

Kind regards,

Hugo

Cornish Man
 

HI Hugo

i am using client 2.14.4

And my card is a TBS 6903

On Monday, 15 July 2019, 10:29:52 BST, Peter Chiu - UKRI STFC <peter.chiu@...> wrote:


Thanks all,

 

I have received a reply from Pamela.  She told me that we

need a second receiver to read data from the 2nd transponder.

 

I shall try to contact Ayecka as we may have hit an awkward situation

that we have exhausted the (two) Ethernet ports on the server host.

 

Regards,

Peter

 

From: MSG-1@groups.io <MSG-1@groups.io> On Behalf Of Hugo
Sent: 15 July 2019 10:17
To: MSG-1@groups.io
Subject: Re: [MSG-1] Getting HVS Transponder 2 channel data

 

Hello Peter and Cornish man,

I see that both of you are using version 2.12.1. Could that be the problem ?

Kind regards,

Hugo

David J Taylor
 

HI Hugo

i am using client 2.14.4

And my card is a TBS 6903
============================================

What SNR do you have? I'm using the BDADataEx software (not the TBS software as it has crashed the PC in the past), and I see an SNR of 10.5 dB at this instant, which is just enough for HVS-2 but with little margin for bad weather etc. With that card you can receive both transponders.

You can either use the "single cable" method described by "Crazy Cat":

https://www.satsignal.eu/wxsat/dvb-s2/T1-T2.html#single-cable

or use the two receivers on that card with the inputs from a single LNB and a satellite TV splitter (and I would put a DC block in one leg).

Here are comparison screen-shots with the single-cable method:

https://www.satsignal.eu/wxsat/dvb-s2/T1-T2.html#full-t2

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

Hugo
 

Yes the screen shots where from Peter ...
Sorry.

Hugo

> i am using client 2.14.4

Cornish Man
 

Hi

Getting 11.2db on 11263 and 10.5db on 11387 using the TBS Data services, using a dual Octangon PLL LNB

Cheers

Jan

On Monday, 15 July 2019, 11:43:34 BST, Hugo <hvanruys@...> wrote:


Yes the screen shots where from Peter ...
Sorry.

Hugo

> i am using client 2.14.4

Peter Chiu - UKRI STFC
 

Thank you all for all your replies.

I suspect we may be using a different hardware from David's.
The Ayecka DVB-S2 receiver converts the data coming down the antenna into Ethernet format.
The data then flow through the RJ45 Traffic port on the receiver to the Ethernet port on the Linux server.

So I have raised a query to Ayecka to see what advice they can offer.

But thanks a lot again for your replies.

Regards,
Peter

-----Original Message-----
From: MSG-1@groups.io <MSG-1@groups.io> On Behalf Of David J Taylor via Groups.Io
Sent: 15 July 2019 11:34
To: MSG-1@groups.io
Subject: Re: [MSG-1] Getting HVS Transponder 2 channel data

HI Hugo

i am using client 2.14.4

And my card is a TBS 6903
============================================

What SNR do you have? I'm using the BDADataEx software (not the TBS software as it has crashed the PC in the past), and I see an SNR of 10.5 dB at this instant, which is just enough for HVS-2 but with little margin for bad weather etc. With that card you can receive both transponders.

You can either use the "single cable" method described by "Crazy Cat":

https://www.satsignal.eu/wxsat/dvb-s2/T1-T2.html#single-cable

or use the two receivers on that card with the inputs from a single LNB and a satellite TV splitter (and I would put a DC block in one leg).

Here are comparison screen-shots with the single-cable method:

https://www.satsignal.eu/wxsat/dvb-s2/T1-T2.html#full-t2

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

David J Taylor
 

Hi

Getting 11.2db on 11263 and 10.5db on 11387 using the TBS Data services, using a dual Octangon PLL LNB

Cheers
Jan
===========================================

Jan,

Whilst the SNR is lower than I would have expected, there should be no problem getting HVS-2 on that system in good weather (assuming the correct PID mask is set - that's 16APSK 2/3). Note that receiving BS and HVS-1 will mean that low HVS-1 signals causing drop-outs may also cause BS drop-outs.

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

David J Taylor
 

Thank you all for all your replies.

I suspect we may be using a different hardware from David's.
The Ayecka DVB-S2 receiver converts the data coming down the antenna into Ethernet format.
The data then flow through the RJ45 Traffic port on the receiver to the Ethernet port on the Linux server.

So I have raised a query to Ayecka to see what advice they can offer.

But thanks a lot again for your replies.

Regards,
Peter
=================================

Peter,

I also have an Ayecka SR1 taking HVS-2 with no problems, although the Ethernet cable is connected to a Windows box. If you're getting data from the SR1 (I monitor with MRTG, available for Linux) the the issues must be with your Linux setup, and I can't help with that.

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

Hugo
 

David,

I think that Peter only needs a second SR1 for receiving hvs-2 ....

Hugo


On Mon, Jul 15, 2019 at 07:52 AM, David J Taylor wrote:
Thank you all for all your replies.

I suspect we may be using a different hardware from David's.
The Ayecka DVB-S2 receiver converts the data coming down the antenna into
Ethernet format.
The data then flow through the RJ45 Traffic port on the receiver to the
Ethernet port on the Linux server.

So I have raised a query to Ayecka to see what advice they can offer.

But thanks a lot again for your replies.

Regards,
Peter
=================================

Peter,

I also have an Ayecka SR1 taking HVS-2 with no problems, although the
Ethernet cable is connected to a Windows box. If you're getting data from
the SR1 (I monitor with MRTG, available for Linux) the the issues must be
with your Linux setup, and I can't help with that.

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

David J Taylor
 

David,

I think that Peter only needs a second SR1 for receiving hvs-2 ....

Hugo
==============================

Hugo,

Even better, use his present SR1 for the Basic Service /only/, and install a TBS6903 for both HVS-1 and HVS-2. That way the reliability of the BS is improved, and it's cheaper. Many ways to get both EUMETCast transponders.

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