Date   

Re: Eumetcast on Debian Linux, using TBS 6903 car

Nick Norman <nick@...>
 

Ernst,

On 02/11/18 17:21, Ernst Lobsiger wrote:
Nick,

IIRC it's some time back you started your GNU/Linux receiver
project. There have been a couple of changes during the year.
OLCI e.g. is now on T2. EUMETSAT (K.-P.) has adapted the
/etc/init.d/dvb-eumetcast script for multi transponder setups.
This also came with a new format of eumetcast-channels.cfg.
Yes, indeed a while ago - been distracted with RL :-(

Yes I've updated & installed all the new versions the cast client is
version 2.14.4

Can you confirm that you use the latest setup files?
If so your eumetcast-channels.cfg schould begin with:

#
# The EUMETCast channels configuration file
# Version 4
# updated 02 Aug 2018
# by K.-P. Renner
...
Yes it does,

Otherwise you might lack some multicast routes.
You can check unresolved multicast routes with:

# ip mroute show
<code>
(192.168.1.2, 224.223.223.11) Iif: dvb0_6 Oifs: dummy0 State:
resolved
(192.168.1.2, 224.223.223.10) Iif: dvb0_6 Oifs: dummy0 State:
resolved
(192.168.1.2, 224.223.223.3) Iif: dvb0_6 Oifs: dummy0 State:
resolved
(192.168.1.2, 224.223.223.2) Iif: dvb0_6 Oifs: dummy0 State:
resolved
(192.168.1.2, 224.223.223.12) Iif: dvb0_5 Oifs: dummy0 State:
resolved
(192.168.1.2, 224.223.223.223) Iif: dvb0_5 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.250) Iif: dvb0_4 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.249) Iif: dvb0_4 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.248) Iif: dvb0_4 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.254) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.247) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.246) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.245) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.244) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.243) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.242) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.241) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.240) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.239) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.238) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.237) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.236) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.235) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.234) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.233) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.232) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.231) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.230) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.229) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.228) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.41) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.30) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.29) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.28) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.27) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.25) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.22) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.3) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.2) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.1) Iif: dvb0_3 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.251) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.227) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.39) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.38) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.35) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.33) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.26) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.24) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.23) Iif: dvb0_2 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.253) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.252) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.226) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.100) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.37) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.32) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.31) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.21) Iif: dvb0_1 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.40) Iif: dvb0_0 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.36) Iif: dvb0_0 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.34) Iif: dvb0_0 Oifs: dummy0 State:
resolved
(192.168.1.1, 224.223.222.223) Iif: dvb0_0 Oifs: dummy0 State:
resolved
(10.90.43.121, 224.223.223.32) Iif: unresolved State: resolved

</code>

OK the only thing I see id that the second adapter is not listed but
ifconfig suggests it is working and passing data

<code>
dvb1_0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 4096
inet 192.168.240.238 netmask 255.255.255.0 broadcast
192.168.240.255
ether 00:22:ab:f0:be:63 txqueuelen 1000 (Ethernet)
RX packets 2521 bytes 455202 (444.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device base 0x262
</code>

So I am almost there but ...

Not quite.

Very many thanks for all you help

Nick
--
The thing about iron is that you generally don't have to think fast in
dealing with it.
(Lords and Ladies)
18:35:01 up 6 days, 6:06, 10 users, load average: 1.02, 0.95, 0.63


Re: Eumetcast on Debian Linux, using TBS 6903 car

Ernst Lobsiger
 

Nigel,

I found out why it didn't work with
EUMETCAST_SERVICE_IDENTIFIER="E1B E1H"

In the Debian/Ubuntu readme that comes along with
the client K.-P. writes "for information only"

"
/etc/dvb-eumetcast.cfg

Defines the transponder service to be started, first
service is adapter 0, second service atapter 1, etc.
...
"

So the above line tried to tune adapter 1 and setup
hvs-1 the multicast routes there. So it's a "feature" :-).


Regards,
Ernst

 


Re: Eumetcast on Debian Linux, using TBS 6903 car

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Nigel,

Good to hear it's working now!

[]
On E1H-TPG-1 you get the GOES-16 files. AFAIK David
has a free (?) special ABI-manager for these files.

Regards,
Ernst
============================

Yes, it's free, and should handle GOES-17 too.

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

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


Re: Eumetcast on Debian Linux, using TBS 6903 car

Ernst Lobsiger
 

Nick,

IIRC it's some time back you started your GNU/Linux receiver
project. There have been a couple of changes during the year.
OLCI e.g. is now on T2. EUMETSAT (K.-P.) has adapted the
/etc/init.d/dvb-eumetcast script for multi transponder setups.
This also came with a new format of eumetcast-channels.cfg.

Can you confirm that you use the latest setup files?
If so your eumetcast-channels.cfg schould begin with:

#
# The EUMETCast channels configuration file
# Version 4
# updated 02 Aug 2018
# by K.-P. Renner
...

Otherwise you might lack some multicast routes.
You can check unresolved multicast routes with:

# ip mroute show

Regards
Ernst


P.S. Do you have an entry

[channel]
name=E1H-TPG-1
target_directory=data/eumetcast/hvs-1/E1H-TPG-1

in /etc/cast-client-channels_hvs-1.ini  ??

 


Re: Eumetcast on Debian Linux, using TBS 6903 car

Nick Norman <nick@...>
 

On 02/11/18 15:27, Ernst Lobsiger wrote:
Nigel,

Good to hear it's working now!
<snip>

On E1H-TPG-1 you get the GOES-16 files. AFAIK David
has a free (?) special ABI-manager for these files.
All I've been following along and getting my Linux system running -
finally got to the task :-)

I (think) I've got it set as described but I see no E1H-TPG-1 directory
nor files, there is a E1H-TPG-2 in the hvs-1 subdirectory of the
~/data/eumetcast directory - so ... I mist check the portal and see if I
ticked the right box, might try the OLCI stuff as well for a giggle.

My directory structure looks like this

<code>
./eumetcast:
bas
hvs-1

./eumetcast/bas:
E1B-GEO-1
EPS-10
EPS-15
EUMETSAT_Data_Channel_1
EUMETSAT_Data_Channel_12
EUMETSAT_Data_Channel_2
EUMETSAT_Data_Channel_3
EUMETSAT_Data_Channel_4
Images
Info-Channel-1
Info-Channel-2
NPP-2

./eumetcast/hvs-1:
E1H-TPG-2
</code>

Dish pointing needs sorting but nice weather needed for that & some time
- delivering an Advanced Radio Amateur Radio licence course tomorrow (Tx
& Tx interference - wish me luck) so will have to await nice warm sunny
weather or ...

So any thoughts would be welcome

Regards to all

Nick
M0HGU

--
The only reason for walking into the jaws of Death is so's you can steal
His gold teeth.
(Colour of Magic)
16:30:01 up 6 days, 4:01, 10 users, load average: 0.17, 0.32, 0.34


Re: Eumetcast on Debian Linux, using TBS 6903 car

Ernst Lobsiger
 

Nigel,

Good to hear it's working now!

To be honest I don't know why
EUMETCAST_SERVICE_IDENTIFIER="E1B E1H"
should not work the same way as
EUMETCAST_SERVICE_IDENTIFIER="E1"

-maybe a bug or "feature" of K.-P.'s script?
-maybe the script tries to tune the adapter0 twice?

The EUMETCAST_SERVICE_IDENTIFIER determines how the
multicast routes are setup and how your adapter(s)
are tuned. If you make changes there (and you don't
want to reboot) you have to stop the service first:

#/etc/init.d/dvb-eumetcast stop
make changes to /etc/dvb-eumetcast.cfg
#/etc/init.d/dvb-eumetcast start

If you have the service running with configration A,
change that configuration to B and then stop the service
you might end up with smcroute error messages and may have
to "#kill `pgrep smcroute`" and "#kill `pgrep szap-s2`"
if you still don't want to reboot. After that you can
start with configuration B normally:
#/etc/init.d/dvb-eumetcast start

The same applies to the client configuration files
/etc/tellicast-client.cfg
/etc/cast-client_bas.ini
/etc/cast-client_hvs-1.ini
/etc/cast-client_hvs-2.ini
If you make changes there you should first stop the TC
#/etc/init.d/tellicast-client stop
then make your changes and
#/etc/init.d/tellicast-client start

On the other hand you can always make changes to
/etc/cast-client-channels_bas.ini
/etc/cast-client-channels_hvs-1.ini
/etc/cast-client-channels_hvs-2.ini
while the tellicast clients are running. These
files are reread periodically by running clients.

On E1H-TPG-1 you get the GOES-16 files. AFAIK David
has a free (?) special ABI-manager for these files.


Regards,
Ernst

P.S. Not sure you even have to use systemctl to
stop/start EUMETCast services. I do not like systemd
on EUMETCast receivers and run Devuan 2.0 (ASCII) that
lets me work with my scripts the good old UNIX way.


Re: Project dish heating

Thorsten Miglus
 

Hi all,

Mounting has finished. It is a lot of work to stick the heating cable. Time will tell if this is a reliable solution.

Cheers,
Thorsten


Re: Project dish heating

Thorsten Miglus
 

Hi Ferdinand,

at my location in Germany, 540 m over sea level, snow is very common. I did dish cleaning by hand in the past but I also observed some losses. I was looking for a solution that is not too expensive. It is worth a try.

Cheers,
Thorsten


On Fri, Nov 2, 2018 at 01:29 PM, Ferdinand Valk wrote:

Hi Thorsten,

 

Good to see that you prepare yourself for the snow this winter. I had purchased my dish with built-in heating some years  ago and did not regret it for a moment. We don’t have snow too frequently in our country with its maritime climate but it is the sticky wet snow that blocks the satellite signal best. Having the dish inaccessible makes heating a must for reliable operation. The attached image shows how the dish is clean whereas the molten snow refreezes at the edges as icicles.

Good luck with the works.

Ferdinand


Re: Eumetcast on Debian Linux, using TBS 6903 car

nigel
 

Hi Ernst, thanks very much for your reply.
Yes, I had done as you suggested, and am now very happy to report that hvs-1 is coming in well!
My problem was with the EUMETCAST_SERVICE_IDENTIFIER line in /etc/ dvb-eumetcast.cfg file.
I had started off with just "=E1B"at the end of that line and when I got the basic service working, I added  a space and E1H to try and get the hvs-1 service going as well. BUT, it appears that doesn' t work! When I changed it to just E1 this morning, both services jumped into life!
So, thanks again for your help - much appreciated.
Regards
Nigel

Sent with AquaMail for Android
http://www.aqua-mail.com

On 1 November 2018 21:34:33 "Ernst Lobsiger" <ernst.lobsiger@...> wrote:

Nigel,

Have you done what I told you in message 27249 October 9th and rebooted?

https://groups.io/g/MSG-1/message/27249

Have you told /etc/dvb-eumetcast.cfg to tune both T1 and T2?
And have you told the /etc/tellicast-client.cfg to start 2 clients (I think so)?

With "#dvbtraffic -a0" or simply "#dvbtraffic" you see the Basic PIDs from adapter0.
What does "#dvbtraffic -a1" say ? This should show the HVS-1 traffic!


Cheers,
Ernst


Re: Project dish heating

Ferdinand Valk
 

Hi Thorsten,

 

Good to see that you prepare yourself for the snow this winter. I had purchased my dish with built-in heating some years  ago and did not regret it for a moment. We don’t have snow too frequently in our country with its maritime climate but it is the sticky wet snow that blocks the satellite signal best. Having the dish inaccessible makes heating a must for reliable operation. The attached image shows how the dish is clean whereas the molten snow refreezes at the edges as icicles.

Good luck with the works.

Ferdinand

 

From: MSG-1@groups.io <MSG-1@groups.io> On Behalf Of Thorsten Miglus
Sent: Friday, 02 November, 2018 10:19
To: MSG-1@groups.io
Subject: [MSG-1] Project dish heating

 

Hi all,

my dish heating arrived from Austria. For 184,26 Euro.
Ready for mounting.

Cheers,
Thorsten



my dish heating arrived 


Project dish heating

Thorsten Miglus
 

Hi all,

my dish heating arrived from Austria. For 184,26 Euro.
Ready for mounting.

Cheers,
Thorsten



my dish heating arrived 


Re: Eumetcast on Debian Linux, using TBS 6903 car

Ernst Lobsiger
 

Nigel,

I got ahead of myself: I already spoke about T1 + T2 which is for all three EUMETCast services of course.
And "dvbtraffic -a1" will then of course give the PID of HVS-2 (all my receivers take Basic + HVS-1 + HVS-2).

In the EUMETSAT distributed files  E1 (E1=T1) is set per default for Basic + HVS-1 in /etc/dvb-eumetcast,cfg.
So no change for the moment unless. you have changed that to E1B. It must read:
EUMETCAST_SERVICE_IDENTIFIER="E1"

Just tell tellicast-client.cfg to start 2 instances of the client
INSTANCE_START_ORDER=bas,hvs-1

With the rfsource=1 you get all three Services:

EUMETCAST_SERVICE_IDENTIFIER="E1 E2"

INSTANCE_START_ORDER=bas,hvs-1,hvs-2

Hope this helps.
Ernst

P.S. Not tested as I have my own startup files. Just from looking at K.-P.s files ...

.


Re: Eumetcast on Debian Linux, using TBS 6903 car

Ernst Lobsiger
 

Nigel,

Have you done what I told you in message 27249 October 9th and rebooted?

https://groups.io/g/MSG-1/message/27249

Have you told /etc/dvb-eumetcast.cfg to tune both T1 and T2?
And have you told the /etc/tellicast-client.cfg to start 2 clients (I think so)?

With "#dvbtraffic -a0" or simply "#dvbtraffic" you see the Basic PIDs from adapter0.
What does "#dvbtraffic -a1" say ? This should show the HVS-1 traffic!


Cheers,
Ernst


Re: Eumetcast on Debian Linux, using TBS 6903 car

nigel
 

On 01/11/2018 20:17, David J Taylor via Groups.Io wrote:
Hi folks,

I'm still struggling to receive HVS-1 on my Debian 9 machine, using a TBS 6903 card.

A very simple question, please, to anyone using this card - I have a single cable from my LNB to the card and am receiving the Basic Service just fine, the cable being connected to the LNB 0 input.

Do I need to do anything "clever" to the card setup to enable it to receive both Basic and HVS-1 service at the same time?

I suspect I'm missing something very basic but can't see the wood for the trees !

The web interface (http://localhost:8200) is showing a config error for HVS-1 but is that due to a lack of signal or a setup error ??

Thanks for any help !

regards
Nigel
================================

Nigel,

On Windows it's just a matter of setting the multicast PID to 8192.

Cheers,
David
Thank you David - I'll investigate that tomorrow.

Regards

Nigel


Re: Eumetcast on Debian Linux, using TBS 6903 car

nigel
 

Thanks Mike,

I'll await a reply from Ernst.

Regards

Nigel

On 01/11/2018 19:59, stevens312 wrote:
Nigel, that card works on all systems, but the person to ask advice on your OS is Ernst he is top man for Debian Linux. Regards, Mike G4CFZ.



Re: Channels showing in MSG Data Manager

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

David,

Yes, me too - following update to Tellicast V2.14.4.
The accompanying guide suggests it can (be) run in parallel with the old version - why would one want to.
And does it - till you delete the old version.


Oh, if only I had upgraded when everyone else did and the help suggestions were flowing.
I really don't want to start another round of 'how do I's!'

But I'm of the old school - "if it ani't broke ....."

Regards,
John
============================

Yes, the upgrades were some time back, possibly around the time of the DVB-S2 transition. You can't simply run the two in parallel, but I suppose you could use your existing older version for the BS and the newer version for the HVS-1.

As usual, what does the log file say?

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


Re: Eumetcast on Debian Linux, using TBS 6903 car

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Hi folks,

I'm still struggling to receive HVS-1 on my Debian 9 machine, using a TBS 6903 card.

A very simple question, please, to anyone using this card - I have a single cable from my LNB to the card and am receiving the Basic Service just fine, the cable being connected to the LNB 0 input.

Do I need to do anything "clever" to the card setup to enable it to receive both Basic and HVS-1 service at the same time?

I suspect I'm missing something very basic but can't see the wood for the trees !

The web interface (http://localhost:8200) is showing a config error for HVS-1 but is that due to a lack of signal or a setup error ??

Thanks for any help !

regards
Nigel
================================

Nigel,

On Windows it's just a matter of setting the multicast PID to 8192.

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


Re: Eumetcast on Debian Linux, using TBS 6903 car

stevens312
 

Nigel, that card works on all systems, but the person to ask advice on your OS is Ernst he is top man for Debian Linux. Regards, Mike G4CFZ.


Re: Channels showing in MSG Data Manager

geojohnt@...
 

David,

Yes, me too - following update to Tellicast V2.14.4.
The accompanying guide suggests it can (be) run in parallel with the old version - why would one want to.
And does it - till you delete the old version.

Oh, if only I had upgraded when everyone else did and the help suggestions were flowing.
I really don't want to start another round of 'how do I's!'

But I'm of the old school - "if it ani't broke ....."

Regards,
John

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

In a message dated 01/11/2018 16:43:48 GMT Standard Time, gm8arv@... writes:

When you need the CMA Viewer we can sort that out, but I'm more inclined to
see your HVS-1 working first.


Re: SR1 telnet Menu Timeout.

geojohnt@...
 

Hello James,

Just to say I've done it - by (simply) reading the EUMETCast Manual.
Well, via seeing how you change a different parameter and using that as a guide.

Best wishes,
John.

3321 - 3340 of 30993