Date   

Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Markus,

Your low Signal, low C/N and bursts of coninuity errors all direct to your frontend.
You should test the receiver with a *direct* connection to the antenna. Maybe
szap-s2 or driver module stv090x  has a problem with your Diseqc switching.

Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

btw, this is the output of dvb-fe-tools --femon. I have not observed such unstable behaviour looking at the BDADataEx display.

Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Carrier(0x03) Signal= -41,00dBm
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 163x10^-21
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 15,6x10^15
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 3,97x10^-3
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 14,8x10^-3
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 4,14x10^-3
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 8,98x10^-3
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 150x10^-3
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 48,5x10^15
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 146x10^-3
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 1,00
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 133x10^15
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 325x10^-21
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 163x10^-21
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 651x10^-21
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 1,00
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 329x10^15
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,70dB postBER= 186x10^15
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 976x10^-21
Carrier(0x03) Signal= -41,00dBm
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 1,00
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 1,08x10^-3
Viterbi(0x07) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 1,00
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 1,00
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Carrier(0x03) Signal= -41,00dBm
Carrier(0x03) Signal= -41,00dBm
Carrier(0x03) Signal= -41,00dBm
Carrier(0x03) Signal= -41,00dBm
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 6,28x10^-3
Carrier(0x03) Signal= -41,00dBm
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 1,36x10^-18
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 150x10^-3
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 6,02x10^15
Lock (0x1f) Signal= -41,00dBm C/N= 9,60dB postBER= 0
Lock (0x1f) Signal= -41,00dBm C/N= 9,50dB postBER= 0


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

Hi Ernst, Christian,
had the chance late last evening to reboot and change the BIOS settings (disabled Intel Speedstep, disabled all C-States, btw. the NAS is a standard PC based on an ASROCK J4105 MB, with 8GB RAM, in a special NAS case with 1 SSD and 4 harddisks). Unfortunately same results (1-3% packet loss, missing files, missing keys, etc.)
A bit frustrated I plugged the TBS5925 and EKU back into my desktop PC (running WIN10 v1909) to check the HW again.
After 1000000 received packets I had 13 missed packets, 13 recovered packets and no error/warning messages and no missing files, keys). This works beautifully.
I rebooted my desktop PC (I have a dual boot config) into Ubuntu 19.09 and followed my own and Ernst's advice installing the DVB, EKU and Tellicast sw. This time, the change of the udev rule file was not necessary, the EKU was recognized with lsusb immediately. I used the dvb-eumetsat-setup script and configured everything.
To my agony, the exact same behavior can be observed (1-3% packet loss, missing files, missing keys, etc.)
The problem is not related to the HW used but a Linux SW problem.
What I have tried already:
- changed CPU governor to powersave, ondemand, performance -> no change observed
- raised the priority (renice) of szap-s2 and tc-client -> no change observed
- disabled most other services (NFS, SMB, etc.) -> no change observed
- unplugged all other USB devices -> no change observed
- changed data/tmp directories from SSD to a harddisk -> no change observed

- tried the echo 1 > /sys/module/dvb_core/parameters/dvb_demux_tscheck option
I get many errors in bursts every few seconds!!!
openmediavault kernel: [51564.517475] dvb_demux: dvb_dmx_swfilter_packet: TS packet counter mismatch. PID=0x1f4 expected 0x2 got 0xc
Maybe I will try the v2016 version of the DVB TBS drivers this evening.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Markus,

After disabling C-States in the BIOS completely (if possible) you
have to know whether this is a driver or a TelliCast problem. You
should have Manu Abrahams famous demodulator driver module stv090x
with CrazyCat's special trick parameter ts_nosync (on) loaded.

You can check for continuity and TEI errors in module dvb_core

# echo 1 > /sys/module/dvb_core/parameters/dvb_demux_tscheck

should report these errors in the kernel log. After some
normal initial errors there should be none. Go back with

# echo 0 > /sys/module/dvb_core/parameters/dvb_demux_tscheck

The second culprit might be your hdd. If this is a NAS you
should not listen music and watch movies from the same hdd.
If possible use a dedicated fast SATA data hdd for TelliCast.
This disk should not fall asleep if TelliCast has some pause.
Tmp directories + channel data must be on the same partition.


Ernst

P.S. I'v never had a NAS and cannot comment on your hardware.


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Christian Peters
 

Markus,

as Ernst wrote: did you look at the Bios and the C-States?! It's solves the problems here with my two 5925 USB devices under Linux.

Regards,

Christian

Am 13.02.20 um 17:18 schrieb Markus Kempf:

I was too optimistic, still the old behaviour, sometimes it works flawlessly for up to 30min and then it starts loosing packets and throwing errors/warnings for a few minutes, gets calm again and the pattern repeats.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

I was too optimistic, still the old behaviour, sometimes it works flawlessly for up to 30min and then it starts loosing packets and throwing errors/warnings for a few minutes, gets calm again and the pattern repeats.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

ok, strange, btw. the creation of the dvb0_* and dummy0 devices worked for me. I use the backport 5.4 kernel.

The smcrouted -c 0 option drastically reduced the number of errors/warnings in the log (0 for the last 30min) . Looks much better now!!!

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Hi Markus,

lsusb shows
...
Bus 003 Device 002: ID 0529:0514 Aladdin Knowledge Systems eToken Pro v4.2.5.4
...
I have had my own multitransponder capable dvb-eumetcast script long before different
people at EUMETSAT began to touch what Anthony Patchett originally wrote in 2008.

Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

Hi Ernst,

has your EKU ProdID 514 like mine? I had to change the udev rule.
I have changed the /etc/init.d/dvb-eutmetcast script on my system yesterday evening, mainly because I noticed that the status did not work right.
1) changed smcroute -d to smcrouted
2) added a smcroute -k before the new start because for unknown reasons the smcroute -k in the stop procedure does not always work reliably
3) changed the grep MTU to grep mtu because the output of ifconfig is now lowercase
4) changed the multicast route inquiry to smcroutectl route
5) changed the mtu size of the dummy interface to 4096 = mtu size of the dvb0 interfaces

I still have lots of missed packets. Will try your C-states tip.
If I can find some time, I will write a real systemd dvb-eumetcast service description.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Markus, George and potential GNU/Linuxers

Concerning the first post I can add my experience of installing TelliCast on Debian 10 amd64 (Buster).
My receivers are headless command line systems managed via ssh. Keyboard and monitor is only used
during the base install. I downloaded and burnt on CD the latest 343MB debian-10.3-amd64-netinst.iso.
All the following refers to a fully 64bit receiver system including TC client and latest EKU software.

The base install on an old Fujitsu/Siemens P7935 (Intel Core2 Duo 3.33GHz, 8GB RAM) takes 1/2 hour.

1) Device driver
   TBS-6903 device drivers are the reason I had to change back to Debian with systemd. The latest
   GIT media driver tree from TBS does not compile anymore on Devuan ASCII 2.0 or 2.1 which still
   has kernel 4.9. It's a pity Devuan does not seem to have the manpower to follow other distros.
   I'am still convinced that a systemd free GNU/Linux OS is more suited for a TC receiver only PC.
   But it's probably true: UNIX is dead and Linux goes the way of a modern desktop/mobile OS where
   you constantly plug in or connect to all kinds of things that have to be handled automatically.

2) EKU software
   I had no problem to get my eToken Pro v4.2.5.4 EKU working. I did *not* add any udev eToken rule.
   I faced the problems I reported before: I had to install gtk2.0.0 as the SavenetAuthenticationClient
   has been developped and linked to graphic stuff not found on my Debian 10 CLI only receiver system.
   I had to add the missing link: ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /lib/libcrypto.so

3) Diseqc switching
   Something I do not use. But I use my own version of szap-s2 compiled from CrazyCat sources.

4) smcroute
   This is where systemd begins to interfere. The EUMETSAT distributed SysV init scripts originate
   from the old days of DVB-S and do not fit well in a systemd handled GNU/Linux. I also had to:

   systemctl disable smcroute
   systemctl disable smcroute-helper

   There is more: systemd comes with its own ntp client service. This is normally disabled when
   you install a full featured ntpd. But when you sync your clock with TelliCast (as EUMETSAT
   proposes) you better check that your RTC is not pushed back and forth beween TC and systemd.

   I use my own versions of dvb-eumetcast and tellicast-client scripts outside of /etc/init.d

   The EUMETSAT distributed script dvb-eumetcast still relies on old ifconfig which is not there
   unless you apt-get install net-tools. Even then it failed to configure my dummy0, dummy1, dummy2
   multicast interfaces. This is new to me: In older Linux kernels with module dummy loaded you
   could just type "ifconfig dummy0 192.168.1.1 multicast" and you had your new dummy0 configured.
   in Debian 10 with kernel 4.19.0-8-amd64 I had to create my 3 dummies first with utility ip:

   ip link add dummy0 type dummy  
   ip link add dummy1 type dummy
   ip link add dummy2 type dummy

   Then I could configure them with ifconfig. I will rewrite my dvb-eumetcast script to
   only use ip instead of ancient ifconfig and probably drop EUMETSAT a note about that.

   There is more problems with smcroute. This used to be one executable in /usr/sbin.
   The version 2.4.2-4 distributed with Debian 10 is now called with smcrouted and
   smcroutectl (sounds like systemctl :-) and smcroute is actually a "compatibility
   wrapper for users with old startup scripts" in /usr/sbin. It's obvious that this
   can go wrong with the EUMETSAT distributed dvb-eumetcast script. As a new feature
   the daemon flushes "unused dynamic" multicast routes after a default delay of 60s.
   This feature deserves more study. It drops routes for channels that have not been
   active recently. When TelliCast announces data in such a channel it usually fails
   with: "WRN: ... Failed to open data channel ... address ... No data received from
   sender". Starting the daemon smcrouted with "smcroute -d -c 0" did the trick !

5) SUCCESS
   It took me 5 hours too. Next install will be with CloneZilla in 10 minutes.

6) Tune as usual
   I have very little missed packets as usual. As posted several times before I
   recommend to disable C-States in BIOS and to pin busiest interrupts to cores.

Bottom line: Yes, installing a GNU/Linux TC receiver is not for the faint of heart.
But if you are willing to google, read posts and man pages it can easily be done.
A couple of people on this list have done it before in different ways and are willing
to help. Please keep in mind that EUMETSAT pushed routers from the very beginning
of DVB-S2 transmission and that they do not have the manpower to keep up with
all that's going on around PCIe DVB-S2 cards and the many GNU/Linux distros.


Best regards,
Ernst


Re: MSG Animator - no receive.

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

-----Original Message-----
From: Heinz Meschnark
Sent: Wednesday, February 12, 2020 8:51 PM
To: MSG-1@groups.io
Subject: [MSG-1] MSG Animator - no receive.

Hello!
I will using MSG Animator and I have installed MSG Data Manager and MSG Animator in the same folder.
the licence is valid.
I beginning with EumetCastBas, after "Start MSG Data Manager". When I enter Msg Animator, then I can see
the notice "Reminder and the request - name and licence code.
After entering the valid code .
There is no reaction after the code has been entered and no receive of pictures.
Please, can you help.
Thank you in advance,
73!
.

Attachments:


Screen Shot 02-11-20 at 10.39 PM.PNG
Screen Shot 02-02-20 at 03.32 PM.PNG
Screen Shot 02-02-20 at 03.41 PM.PNG
Screen Shot 02-02-20 at 03.50 PM.PNG
Screen Shot 02-11-20 at 10.07 PM.PNG
Screen Shot 02-11-20 at 10.09 PM.PNG
====================================================

Heinz,

Thanks for the screenshots. Sorry to hear of your problem. This topic is more suited to the SatSignal group:

https://groups.io/g/SatSignal

- From the MSG Data Manager screenshot it seems you have not yet installed the licence. Is the licence not staying set? Remember that when you do that you need to run the program with right-click, Run as Administrator.

- For an IR animation you need channel 09, 10.8 um.

- In the MSG Animator, right-click the icon which is in the Notification Area (what I call the system tray). Options, Set image data path, and ensure that it is at the top of the image tree, such as:

C:\MSG-1\Images (in your system, guessing from the screenshots).
D:\MSG\Images (in my system)

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


MSG Animator - no receive.

Heinz Meschnark
 

Hello!
I will using MSG Animator and I have installed MSG Data Manager and MSG Animator in the same folder.
the licence is valid.
I beginning with EumetCastBas, after "Start MSG Data Manager". When I enter Msg Animator, then I can see
the notice "Reminder and the request - name and licence code.
After entering the valid code .
There is no reaction after the code has been entered and no receive of pictures.
Please, can you help.
Thank you in advance,
73!
.


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

George,

Yes, dB is what I have used from the very beginning. Again from my first patch of the stv090x driver
up to now there has been much change. In Konstantins TBS drivers there was a module parameter
to select % or dB(m). Below is what I have used for 3 years now. As a result of this thread I wanted
to compile the latest OS drivers from TBS. No way with Devuan 2.0 or 2.1 because some modules
asked for a newer kernel. So I just installed Debian 10 amd64 and will double check my stuff again.

Meanwhile play with the bash files attached. They should still work for TBS-6983/08/03 ...

Cheers,
Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

George Sz
 

Ernst,

Thanks for posting the module option again, I did not know of this due to lack of documentation. Googling this option will direct you back to this forum.

Anyway, I removed the splitter and the input levels increased, SNR didn't change however. Btw, is there any way to force the 6903 drivers to return dB instead of percentage?

Regards,
George


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Markus,

That's a long story. TBS is basically a HW manufacturer. The USB box TBS-5925
has the same first generation ST demodulator chip as the TBS-6925 and the SR1.
No way to receive 2 ACM/VCM transponders at the same time as with a TBS-6903.

Years back TBS worked with a driver programmer Konstantin Dimitrov and mostly
produced closed source blobs you had to link in. The driver of the TBS-6925 was an
Open Source exception basically programmed by Manu. Together with Konstantin I was
finally able to get it working for DVBS-2 EUMETCast on a TBS-6925. It seems they
later sacked Konstantin and wanted to go fully Open Source. There was a time TBS
still distributed Konstantins drivers without having the source (!). Some of the
EUMETSAT recommended drivers might still date back to those days and finally
stopped working with newer Linux kernels. The Open Source TBS-6903/08 driver
was loosing interrupts and also had the PCIe-Bridge buffer delay problem with
HVS-2. I was able to fix that with the help of CrazyCat. Ever since CrazyCat
seems to have maintained the Open Source tree of TBS device drivers. So my
recommandation is just to try the latest from the Open Source TBS repo.
But the TBS-5925 driver code has probably not been touched for years now.
If you have a driver problem with latest Linux kernels CrazyCat might fix that.

Here I added a MODCOD filter to this TBS-5925/6925 driver that worked well.
This is useful to stop HVS-1/BAS interaction in rainy weather conditions.
I tried the same with the TBS-6903/08 but have never got it working :-( ...

Cheers,
Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

Ernst,

do you have a link or a writeup of your judgement of the TBS drivers? Which one would be best for the 5925?

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

George,

 Here is the module parameter I was talking about. This is copied in part from my message #27249:

<cite>


And here comes the next trick that makes the 6903 driver shine.
If you want a single cable system that takes T1 + T2 it's easy
again. Edit a file /etc/modprobe.d/stv6120.conf with content:

options stv6120 rfsource=1

The meaning that you might want to write into the file as comment:

#  Parameter rfsource is loaded when booting (cannot be changed in /sys/module/...)
#  0  = you can attach two cables LNB0->adaper0 and LNB1->adapter1 (DEFAULT)
#  1  = connect the cable to LNB0 where you can use adapter0 + adapter1
#  2  = connect the cable to LNB1 where you can use adapter0 + adapter1

Of course 1 and 2 is only possible if T1 and T2 is in the same band and polarisation.
But this is the case for EUMETCast transponders T1 and T2.

Cheers,
Ernst

</cite>


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

thanks for the feedback. I believe the core of the problems is the proprietary and closed source Tellicast client and the authentication requirements. That matches well with another monolithic and proprietary system like Windows but not with the fragmented Linux (Unix) world. But nethertheless the Linux install would be unproblematic with a concise and correct documentation or simply the correction of simple errors. Deb and rpm versions cover 90% of the market already.
1) make the TBS drivers consistent with the mainstream linux kernel or create a DKMS procedure to automatically recompile with every new kernel version
2) update the Safenet Authentication client to v10, maybe the erorr in the DEB file was corrected or build a new DEB for v9 or at least document the possible problems in the README or the general documentation
3) create a quick start guide linking the spread out info

In the long run I would hope for Eumetsat making up their mind and adopting an open access policy comparable to the Copernicus/Sentinel program with p2p access to the data (not Eumetcast Terrestrial with Tellicast/EKU and limited to research networks) .
In 2005 I had a 2Mbs connection to the Internet, now I have 1Gbs. The need for the satellite transmission is diminishing at least in the civilized parts of Europe and the british islands.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

George,

Why do you use a splitter? Inside the tuner chip there is a matrix switch. With a single module parameter you can connect your cable directly to one input and feed both adapter chains of the TBS-6903. That's the way I receive BAS/HVS-1 + HVS-2 with a single cable. This works with the TBS-6983/03/08 cards the same way. Or have you tried that before and found the system works better with the splitter in front of the card? Or is this again a case of missing documentation?

Regards,
Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

George Sz
 

Markus,

Considering how much time I wasted on Debian before, I'm not likely going back to that distro ever again. At one point I decided to switch to Ubuntu Server and in my experience, it's a lot easier to get work done on that distro. Getting Eumetcast to run, as far as I can recall, takes for me about an hour or two, and that includes OS installation. I also perform OS/kernel updates now and then and so far my system has survived all of these adventures. In my experience, the installation process has become a lot more simple over the years. I remember I had to spend days trying to get my dongle working with that old akstre garbage.

While I agree that compiling the TBS drivers is a pain, doing a few compiles will get you the necessary experience. Regarding DiSEqC, when it comes to professional use, it just adds one more point of failure so in the end I'm not surprised about its omission in the docs.

Perhaps my biggest issue so far was the proprietary client software, namely that nasty udev bug that was eventually addressed. I just wish its disk write issue did not require these RAM disk hacks. Sidenote: I still wonder why this is happening, maybe the client is doing a forced cache flush, then perform a hash check to make sure data has been written to disk properly? I mean, the Linux disk cache system could easily take care of fast write spikes.

As for the hardware I'm running, it's an off-lease 4th gen core i5 Lenovo SFF with 8GB of RAM, with a TBS 6903 inside. The dish I'm using is a 1.8m Prodelin with a Russian feedhorn, with a single cable setup, using a splitter to feed both inputs of the card.

Regards,
George

3101 - 3120 of 32213