Date   
Re: msg data manager defect ??

David J Taylor
 

Hello,
May I just add that I use Windows 10 home, 64bits.
When trying to re-install the MSG D.M. I receive the message:
error 126, WaveletDLL.dll.
I must have lost this WaveletDLL somehow and I guess that this is the origin of my MSG data manager not functioning any longer.
Could you assist me please by telling me where I can find this DLL in order to put it into
the MSG file ?
Thanks in advance.
Regards,
Roland
================================

Roland,

That DLL is only included in the full install, so close all instances of the MSG Data Manager, install the full release (not the beta), and then install any beta updates you wish to run.

I echo Ian's remarks that if something worked yesterday but not today, as there have been no changes in the software or the data, it must be something you did on your computer. I can't help you with that!

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

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

Ernst Lobsiger
 

Markus,

I just tested with dvb-fe-tool that my version of szap-s2 correctly sets

STREAM_ID = 1
ROLLOFF = 20

So this might be a last problem. I never understood, why EUMETSAT
distributes an szap-s2 that apparently cannot set the STREAM_ID.

MODULATION = QPSK
is returned by dvb-fe-tool if you are in VCM (as far as I remember).

I'll make some more tests and possibly send you my szap-s2 source
tomorrow. I will have to UPDATE my own szap-HOWTO somewhat too.

Cheers,
Ernst



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

Ernst Lobsiger
 

Markus,

If you are in Germany even a C/N = 12dB should be possible with your 80cm dish.

Here is my stv090x.c driver with 3 snipplets patched in for easy MODCOD setting.
I tested it in many ways with one of my old TBS-6925 last night and this afternoon.

Have fun
Ernst

msg data manager defect ??

Roland Fechter
 

Hello,
May I just add that I use Windows 10 home, 64bits.
When trying to re-install the MSG D.M. I receive the message:
error 126, WaveletDLL.dll.
I must have lost this WaveletDLL  somehow and I guess that this is the origin of my MSG data manager not functioning any longer.
Could you assist me please by telling me where I can find this DLL in order to put it into
the MSG file ?
Thanks in advance.
Regards,
Roland 

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

Markus Kempf
 

Ernst you are my hero, like my physics teacher 40 years ago in my Gymnasium. I switched on Modcode All in BDADataEx and immediately the error rate went up and looked almost as bad as with the linux setup. Thanks to the warm and beautiful weather today, I went outside, climbed on my roof and fixed not only my ADSB antenna (was lying almost horizontally because of the storm) but also my sat dish. With a slight movement to the east, the signal level was up to 10.6 dB. Now I'm back at solid zeros for the missing packet count with modcode All. Will go back to my NAS system soon.
I had a look at the stv090x.c code and it has provisions for setting and filtering MODCODs and PIDs. I would definitely be interested in your patch and the other szap-s2 version.
Thank you very much again.

Markus

Re: msg data manager defect ??

Roland Fechter
 

Thank you for your kind prompt advise !
I do receive images from the Metop manager and Goes 16 ABI - still the Msg manager refuses to cooperate !
Perhaps David the creator of D.M. could more closely look into this ?
Regards,
Roland

Re: msg data manager defect ??

Ian Deans
 

On 15/02/2020 12:12, Roland Fechter wrote:
Hallo,
I run version 3.1.13.1309 with Multicast 2.1.4.2.5 client.
Basic & HSV-1 come in but are not opened by the MSG D.M.
Normal correct function until this morning, i.e. yesterday everything was still o.k.
There must be something "wrong" with either Multicast - perhaps some changes to it ? and/or
the MSG D.M. - update ?
Please could you look into this and advise remedy ?
Thanks in advance,
Regards,
Roland
----------------------------------------------------------------

Roland all is working fine with me, both Data Manager and the Tellicast client.
As there has been no changes to either of these programs since yesterday when you say they were working fine, then the problem must be with your computer and or its settings. That is where you need to look.

Regards
Ian.

msg data manager defect ??

Roland Fechter
 

Hallo,
I run version 3.1.13.1309 with Multicast 2.1.4.2.5 client.
Basic & HSV-1 come in but are not opened by the MSG D.M.
Normal correct function until this morning, i.e. yesterday everything was still o.k.
There must be something "wrong" with either Multicast - perhaps some changes to it ? and/or
the MSG D.M. - update ?
Please could you look into this and advise remedy ?
Thanks in advance,
Regards,
Roland

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

Ernst Lobsiger
 

Markus,

We get closer to the point:

1) SNR 9.6 dB is low even for an 80cm dish. I'am quite sure you can do better.

2) Link Margins (LM) are (3-4 dB is recommended!)
   BAS      8PSK 3/5 :   LM = SNR or C/N - 5.9 dB
   HVS-1  16APSK 2/3 :   LM = SNR or C/N - 9.3 dB

3) THE REST IS HISTORY:
   When we had to change to DVB-S2 EUMETSAT promised that ACM/VCM receivers would
   solve all problems. People with smaller antennas would still receive BAS while
   people with big antennas could receive BAS + HVS-1 (only T1 in use at that time).
   EUMETSAT was WRONG. As far as I remember even the rather expensive SR1 could not
   handle DVB-S2 EUMETCast properly at the beginning. The problem was (and still is!)
   that as soon as HVS-1 falls to low link margins this affects BAS as well. The SR1
   has the very same STV0900 Advanced kind of demodulator that is soldered in your
   TBS-5925. This ST chip allows for MODCOD filtering under DVB-S2. As far as I
   remember MODCOD filtering came with a later firmware update for the SR1. And it
   seems that you can activate it under WINDOWS with CrazyCats BDADataEx on your
   TBS-5925 (I never had a Windows EUMETCast setup here).

4) szap-s2 floats around the net in different versions. I use a CrazyCat version
   which originally stemms from Igor M. Liplianin. It needs the source and some
   googling to find out how to transmit all kind of stuff to the driver. My version
   lets you also set stream IDs while the EUMETSAT distibuted version has no such
   parameter. AFAIK the stream ID should be 1 not what your dvb-fe-tool returns.
   # szap-s2 -q usually shows you all possible parameters you can set with command
   switches. There is a hidden compressed format directly with the channel entries.
   I had to write my own szap-s2 HOWTO to learn how to send all these parameters.

   But I finally found out that some Linux drivers ignore the majority of those
   parameters and find out themselves what they think is right. You can actually
   ask for modulation+fec (MODCOD) and rolloff but it might have no effect at all.

5) The TBS-6925 did not work to begin with while the SR1 with the same chips worked.
   It was again CrazyCat that found under Windows a solution with the FIFO parameter.
   Konstantin dropped me a Mail and I had the first working PCI card by simply setting
   1 single bit in the plenthora of ST0900 registers. That's why I know stv090x.c a bit.

6) At about the same time the SR1 received MODCOD filtering I added my own homebrew
   MODCOD filtering to the TBS-6925 driver. Christian tried it out on a TBS-5925
   later as well. If you reduce an SR1 or TBS-59/6925 on BAS only it means that you
   payed a lot of money for a ACM/VCM capable device and use it in a way a 30 Euro
   SkyStar 2 eXpress HD from eBay can work as well. EUMETSAT said it would never work
   but praise CrazyCat who made it happen again. Also praise Georgios Potiriadis
   at EUMETSAT who finally wrote a couple of HOWTOs for the use of PCI cards in
   EUMETCast receivers even if some of these manuals are slightly outdated now.

7) When the TBS-6983 appeared (I still have two hand made prototypes here!) the SR1
   was outperformed. The new ST chip allowed to receive at the same time T1 + T2 while
   this asked for a second SR1. There was quite a bit of FUD on the forum concerning
   this promise of the new PCIe card but it all came true. Arne van Belle demonstrated
   with some help of me that he could receive 2 times (BAS + HVS-1) on a TBS-6983 and
   keep up with all this data on a moderate powered PC even before T2 was in the air.

8) I'am no software ingeneer and I wrote my homebrew MODCOD filter in 2014 simply by
   looking at Manu Abrahams and Konstantin Dimitrovs code of the stv090x driver. Technical
   ST documentation asks for receiving and signing an NDA. I still have some TBS-6925 and
   SkyStar 2 eXpress HD cards here and I guess my patch still works in the stv090x distributed
   by TBS today. But this is now a 2020 in-tree version adapted by CrazyCat that is used by
   TBS-59/6925 (CHIP STV0900 Advanced) but also works with a SkyStar 2 eXpress HD (CHIP STV0903).


BOTTOM LINE AND WHERE TO GO FROM HERE:
--------------------------------------

GNU/Linux drivers still do not allow for MODCOD filtering. With the C/N you showed
us you have almost 0 dB link margin for HVS-1. If you say it works fine under Windows
with the same Signal and C/N (SNR) it seems you can now really set MODCOD filters with
BDADataEx. Please confirm that by testing EUMETCast Windows reception with all MODCODs.
David Taylor and CrazyCat should certainly be able to shed some light on this point.

A) You should have about 12dB SNR for T1 if you cannot filter MODCODs.
   I had an 80cm dish and I'am afraid your antenna is rather misspointed.

B) If we are sure you have a HVS-1 --> BS interaction reception problem I
   could add my 2014 patch (that I just found somewhere on one of my receivers)
   to the 2020 distributed version of stv090x.c and you can give it a try.

C) I cite from your first post in this thread: "I was quite confident that this would
   work in a short amount of time, given my 35 years of experience working as an engineer
   in the IT industry and beeing a Unix native...". If the patch from a simple Physicist
   and Teacher works for you, then you could give CrazyCat and TBS a hand to integrate it
   properly in stv090x.c but also in the very similar stv091x.c code for TBS-6983/03/08.


Hope this helps

Ernst


P.S. My solution for the nasty HVS-1 --> BAS interaction was a Gibertini 1.25m dish

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

Markus Kempf
 

Ernst,
I have seen a bit higher CN than 9.6 in the past (with my 80cm dish), maybe I need to recheck the pointing after "Sabine", but it is still good enough for Basic Service and that's all I want to receive at the moment. And it works perfectly with Win10 and exactly the same HW. Btw. in BDADataEx I have set the modcod to 8PSK3/5 for BS only. I'm not sure how this can be done with szap-s2.

This is the output of modinfo:

filename: /lib/modules/5.4.0-0.bpo.2-amd64/kernel/drivers/media/dvb-frontends/stv090x.ko
license: GPL
description: STV090x Multi-Std Broadcast frontend
author: Manu Abraham
alias: i2c:stv090x
depends:
retpoline: Y
name: stv090x
vermagic: 5.4.0-0.bpo.2-amd64 SMP mod_unload modversions
parm: ts_nosync:TS FIFO Minimum latence mode (default:on) (int)
parm: verbose:Set Verbosity level (int)

filename: /lib/modules/5.4.0-0.bpo.2-amd64/kernel/drivers/media/usb/dvb-usb/dvb-usb-tbs5925.ko
license: GPL
version: 1.0
description: TurboSight TBS 5925 DVB-S2 driver
author: Konstantin Dimitrov <kosio.dimitrov@...>
srcversion: 533BB7E5866E52F63B9ACCB
alias: usb:v734Cp5925d*dc*dsc*dp*ic*isc*ip*in*
depends: dvb-usb,usbcore,rc-core
retpoline: Y
name: dvb_usb_tbs5925
vermagic: 5.4.0-0.bpo.2-amd64 SMP mod_unload modversions
parm: debug:set debugging level (1=info 2=xfer (or-able)). (int)
parm: adapter_nr:DVB adapter numbers (array of short)

dvb-fe-tool:
Device TurboSight TBS 5925 DVB-S/S2 (/dev/dvb/adapter0/frontend0) capabilities:
CAN_2G_MODULATION
CAN_FEC_AUTO
CAN_INVERSION_AUTO
CAN_MULTISTREAM
CAN_QPSK
DVB API Version 5.11, Current v5 delivery system: DVBS2
Supported delivery systems:
DVBS
[DVBS2]
DSS
Frequency range for the current standard:
From: 950 MHz
To: 2,15 GHz
Symbol rate ranges for the current standard:
From: 1,00 MBauds
To: 45,0 MBauds
SEC: set voltage to OFF

FREQUENCY = 1513000
INVERSION = AUTO
SYMBOL_RATE = 33000000
INNER_FEC = AUTO
MODULATION = QPSK
PILOT = AUTO
ROLLOFF = 35
POLARIZATION = OFF
STREAM_ID = 4294967295
DELIVERY_SYSTEM = DVBS2

Markus

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

Ernst Lobsiger
 

Markus,

Could you also check that you load the right driver module. Maybe something
went wrong when compiling and installing the TBS .../media/.. drivers?

# modinfo stv090x

shold show a first CrazyCat added module parameter

parm:           ts_nosync:TS FIFO Minimum latence mode (default:on)  (int)

Regards,
Ernst

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