David, Yes of course, and I have always used this WXtrack function. But, even with a 1 m dish I find that the co-lin begins before the 'begin' in the list noted and lasts longer than the end

David, Yes of course, and I have always used this WXtrack function. But, even with a 1 m dish I find that the co-lin begins before the 'begin' in the list noted and lasts longer than the end

Nice one, John! For those with registered WXtrack, you can get the results in a tabular format. https://www.satsignal.eu/software/wxtrack.htm Cheers, David -- SatSignal Software - Quality

All, My spring outage period has started and I've found this realtime map of the 'outage area.' It updates on a timescale that you select and shows the outage area crossing 'your' location. In our

hi all just lined my 90cm dish up with my sat meter to 10 e and got the optimum signal(meter shows video of one of the channels on 10e so i know its the right sat),when i connect it to my pci card it

hi just a quick question,when i post a new topic is there a delay before it is posted thanks [Members' first posts are moderated. David, owner]

hi all just lined my 90cm dish up with my sat meter to 10 e and got the optimum signal(meter shows video of one of the channels on 10e so i know its the right sat),when i connect it to my pci card it

Markus, Your NAS GNU/Linux receiver seems to work perfectly now. I attach what my 11 years old Fujitsu/Siemens CoreDuo receiver io did when I tested the TBS-6925 two days ago. I also attach the

# service tellicast-client status|grep Memory: Memory: 2.3G # grep VmPeak /proc/4679/status VmPeak: 185332 kB the peak allocated virtual memory value increases, the allocated memory for the

Ernst, I can observe an increase in memory usage. Right now the service allocates 5.1GB of memory: root@openmediavault:~# service tellicast-client status|grep Memory: Memory: 5.1G the main

Markus, Here I have to change the driver stv090x.c in ./media as described. The point probably is that this only works if the the patched driver copy is newer than the replaced one. This is because

Ernst, total success. For unknown reasons, my CN dropped to 10,0 - 10,2 since about 4 UTC and I had the errors again. Compiled and copied your versions, rebooted, run setmc and everything is perfect

Markus, Let's take the shortcut. Here is the Igor M. Liplianin, CrazyCat enhanzed szap-s2 version you better use. All you have to do is add in channel.conf behind :hS1 more stuff: It should then

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

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

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

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

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

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

---------------------------------------------------------------- Roland all is working fine with me, both Data Manager and the Tellicast client. As there has been no changes to either of these